Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Segmentation fault on qnap #6

Open
SiNaPsEr0x opened this issue Apr 5, 2023 · 10 comments
Open

Segmentation fault on qnap #6

SiNaPsEr0x opened this issue Apr 5, 2023 · 10 comments

Comments

@SiNaPsEr0x
Copy link

SiNaPsEr0x commented Apr 5, 2023 •
edited
Loading

the problem to create fake display:

this error:

/startup.sh: line 62:     8 Aborted                 /usr/bin/Xvfb :0 -screen 0 "${RESOLUTION}x24" -nolisten tcp -nolisten unix
Starting LXDE
** Message: 13:15:03.462: main.vala:101: Session is LXDE
** Message: 13:15:03.462: main.vala:102: DE is LXDE

(lxsession:10): Gtk-WARNING **: 13:15:03.468: cannot open display: :0
Starting x11vnc
05/04/2023 13:15:05 passing arg to libvncserver: -rfbport
05/04/2023 13:15:05 passing arg to libvncserver: 5901
05/04/2023 13:15:05 x11vnc version: 0.9.16 lastmod: 2019-01-05  pid: 21
05/04/2023 13:15:05 XOpenDisplay(":0") failed.
05/04/2023 13:15:05 Trying again with XAUTHLOCALHOSTNAME=localhost ...

05/04/2023 13:15:05 ***************************************
05/04/2023 13:15:05 *** XOpenDisplay failed (:0)

*** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue.
*** There may be "Xlib:" error messages above with details about the failure.

Some tips and guidelines:

** An X server (the one you wish to view) must be running before x11vnc is
   started: x11vnc does not start the X server.  (however, see the -create
   option if that is what you really want).

** You must use -display <disp>, -OR- set and export your $DISPLAY
   environment variable to refer to the display of the desired X server.
 - Usually the display is simply ":0" (in fact x11vnc uses this if you forget
   to specify it), but in some multi-user situations it could be ":1", ":2",
   or even ":137".  Ask your administrator or a guru if you are having
   difficulty determining what your X DISPLAY is.

** Next, you need to have sufficient permissions (Xauthority) 
   to connect to the X DISPLAY.   Here are some Tips:

 - Often, you just need to run x11vnc as the user logged into the X session.
   So make sure to be that user when you type x11vnc.
 - Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE
   file may be accessed.  The cookie file contains the secret key that
   allows x11vnc to connect to the desired X DISPLAY.
 - You can explicitly indicate which MIT-MAGIC-COOKIE file should be used
   by the -auth option, e.g.:
       x11vnc -auth /home/someuser/.Xauthority -display :0
       x11vnc -auth /tmp/.gdmzndVlR -display :0
   you must have read permission for the auth file.
   See also '-auth guess' and '-findauth' discussed below.

** If NO ONE is logged into an X session yet, but there is a greeter login
   program like "gdm", "kdm", "xdm", or "dtlogin" running, you will need
   to find and use the raw display manager MIT-MAGIC-COOKIE file.
   Some examples for various display managers:

     gdm:     -auth /var/gdm/:0.Xauth
              -auth /var/lib/gdm/:0.Xauth
     kdm:     -auth /var/lib/kdm/A:0-crWk72
              -auth /var/run/xauth/A:0-crWk72
     xdm:     -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk
     dtlogin: -auth /var/dt/A:0-UgaaXa

   Sometimes the command "ps wwwwaux | grep auth" can reveal the file location.

   Starting with x11vnc 0.9.9 you can have it try to guess by using:

              -auth guess

   (see also the x11vnc -findauth option.)

   Only root will have read permission for the file, and so x11vnc must be run
   as root (or copy it).  The random characters in the filenames will of course
   change and the directory the cookie file resides in is system dependent.

See also: http://www.karlrunge.com/x11vnc/faq.html
Starting noVNC
WebSocket server settings:
  - Listen on :6901
  - Web server. Web root: /usr/share/novnc
  - No SSL/TLS support (no cert file)
  - proxying from :6901 to 127.0.0.1:5901
192.168.1.20 - - [05/Apr/2023 13:15:42] 192.168.1.20: Plain non-SSL (ws://) WebSocket connection
192.168.1.20 - - [05/Apr/2023 13:15:42] 192.168.1.20: Path: '/websockify'
192.168.1.20 - - [05/Apr/2023 13:15:42] connecting to: 127.0.0.1:5901
192.168.1.20 - - [05/Apr/2023 13:15:42] Failed to connect to 127.0.0.1:5901
@dmotte
Copy link
Owner

dmotte commented Apr 5, 2023

Hey there, thanks for opening this issue and for using this software! May I ask you some more details about the environment (e.g. Docker version, OS) and what is the command / docker-compose file you are using to spin this up?

@SiNaPsEr0x
Copy link
Author

I have qnap with armv7 procs alpine

@dmotte
Copy link
Owner

dmotte commented Apr 6, 2023

Could you please tell me what is the digest of the specific desktainer Docker image you are using?

Thanks :)

@SiNaPsEr0x
Copy link
Author

SiNaPsEr0x commented Apr 13, 2023 •
edited
Loading

Log is missing of supervisor
image

but this is a error log on docker qnap:

Starting Xvfb
(EE) 
(EE) Backtrace:
(EE) 
(EE) Segmentation fault at address 0x6c69615e
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
/startup.sh: line 62:     8 Aborted                 /usr/bin/Xvfb :0 -screen 0 "${RESOLUTION}x24" -nolisten tcp -nolisten unix
Starting LXDE
** Message: 17:19:01.547: main.vala:101: Session is LXDE
** Message: 17:19:01.548: main.vala:102: DE is LXDE

(lxsession:10): Gtk-WARNING **: 17:19:01.552: cannot open display: :0
Starting x11vnc
13/04/2023 17:19:03 passing arg to libvncserver: -rfbport
13/04/2023 17:19:03 passing arg to libvncserver: 5901
13/04/2023 17:19:03 x11vnc version: 0.9.16 lastmod: 2019-01-05  pid: 23
13/04/2023 17:19:03 XOpenDisplay(":0") failed.
13/04/2023 17:19:03 Trying again with XAUTHLOCALHOSTNAME=localhost ...

13/04/2023 17:19:03 ***************************************
13/04/2023 17:19:03 *** XOpenDisplay failed (:0)

*** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue.
*** There may be "Xlib:" error messages above with details about the failure.

Some tips and guidelines:

** An X server (the one you wish to view) must be running before x11vnc is
   started: x11vnc does not start the X server.  (however, see the -create
   option if that is what you really want).

** You must use -display <disp>, -OR- set and export your $DISPLAY
   environment variable to refer to the display of the desired X server.
 - Usually the display is simply ":0" (in fact x11vnc uses this if you forget
   to specify it), but in some multi-user situations it could be ":1", ":2",
   or even ":137".  Ask your administrator or a guru if you are having
   difficulty determining what your X DISPLAY is.

** Next, you need to have sufficient permissions (Xauthority) 
   to connect to the X DISPLAY.   Here are some Tips:

 - Often, you just need to run x11vnc as the user logged into the X session.
   So make sure to be that user when you type x11vnc.
 - Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE
   file may be accessed.  The cookie file contains the secret key that
   allows x11vnc to connect to the desired X DISPLAY.
 - You can explicitly indicate which MIT-MAGIC-COOKIE file should be used
   by the -auth option, e.g.:
       x11vnc -auth /home/someuser/.Xauthority -display :0
       x11vnc -auth /tmp/.gdmzndVlR -display :0
   you must have read permission for the auth file.
   See also '-auth guess' and '-findauth' discussed below.

** If NO ONE is logged into an X session yet, but there is a greeter login
   program like "gdm", "kdm", "xdm", or "dtlogin" running, you will need
   to find and use the raw display manager MIT-MAGIC-COOKIE file.
   Some examples for various display managers:

     gdm:     -auth /var/gdm/:0.Xauth
              -auth /var/lib/gdm/:0.Xauth
     kdm:     -auth /var/lib/kdm/A:0-crWk72
              -auth /var/run/xauth/A:0-crWk72
     xdm:     -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk
     dtlogin: -auth /var/dt/A:0-UgaaXa

   Sometimes the command "ps wwwwaux | grep auth" can reveal the file location.

   Starting with x11vnc 0.9.9 you can have it try to guess by using:

              -auth guess

   (see also the x11vnc -findauth option.)

   Only root will have read permission for the file, and so x11vnc must be run
   as root (or copy it).  The random characters in the filenames will of course
   change and the directory the cookie file resides in is system dependent.

See also: http://www.karlrunge.com/x11vnc/faq.html
Starting noVNC
WebSocket server settings:
  - Listen on :6901
  - Web server. Web root: /usr/share/novnc
  - No SSL/TLS support (no cert file)
  - proxying from :6901 to 127.0.0.1:5901
192.168.1.13 - - [13/Apr/2023 17:20:59] 192.168.1.13: Plain non-SSL (ws://) WebSocket connection
192.168.1.13 - - [13/Apr/2023 17:20:59] 192.168.1.13: Path: '/websockify'
192.168.1.13 - - [13/Apr/2023 17:20:59] connecting to: 127.0.0.1:5901
192.168.1.13 - - [13/Apr/2023 17:20:59] Failed to connect to 127.0.0.1:5901
192.168.1.13 - - [13/Apr/2023 17:21:02] 192.168.1.13: Plain non-SSL (ws://) WebSocket connection
192.168.1.13 - - [13/Apr/2023 17:21:02] 192.168.1.13: Path: '/websockify'
192.168.1.13 - - [13/Apr/2023 17:21:02] connecting to: 127.0.0.1:5901
192.168.1.13 - - [13/Apr/2023 17:21:02] Failed to connect to 127.0.0.1:5901```

@dmotte
Copy link
Owner

dmotte commented Apr 13, 2023

I didn't ask you that. Please read carefully. There is no supervisor running in this Docker image :)

@SiNaPsEr0x
Copy link
Author

Sorry I had tried the same versions and I answered you wrongly about version ahahah anyway this is the mistake it gives me

@dmotte
Copy link
Owner

dmotte commented Apr 13, 2023

Don't worry. Anyway, my question was:

Could you please tell me what is the digest of the specific desktainer Docker image you are using?

If you can tell me what's the digest then maybe I'll be able to try it on some armv7 device

@SiNaPsEr0x
Copy link
Author

Latest

@SiNaPsEr0x
Copy link
Author

SiNaPsEr0x commented Apr 17, 2023 •
edited
Loading

@dmotte do you have a news?
or any info for install to nas same to THIS

@dmotte dmotte changed the title problem with run on NAS Segmentation fault on qnap Apr 18, 2023
@dmotte
Copy link
Owner

dmotte commented Apr 18, 2023

See dmotte/desktainer#7 which is basically the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SiNaPsEr0x @dmotte