Bug#1000871: [Pkg-tigervnc-devel] Bug#1000871: tigervnc-standalone-server: server fails to start
Hi All, On 12/1/21 18:49, Celejar wrote: >>> Primarily the segfault, as far as I can tell, tigervnc does not segfault. The problem is that the xfce session segfaults and terminates early. Moreover, default for tigervnc is on session termination to kill the VNC server. Try tigervncserver -autokill no to prevent this. Moreover, try tigervncserver -xstartup /usr/bin/xterm -- to get a simple X terminal going in the VNC server. Note the --. Otherwise /usr/bin/xterm will be started with the session argument, i.e., startxfce4 in your case. By the way, this is not the standard configuration. Someone must have edited some configuration files to specify the xfce session. Best, Joachim
Bug#1000871: [Pkg-tigervnc-devel] Bug#1000871: tigervnc-standalone-server: server fails to start
Hi All, On 12/1/21 18:49, Celejar wrote: >>> Primarily the segfault, as far as I can tell, tigervnc does not segfault. The problem is that the xfce session segfaults and terminates early. Moreover, default for tigervnc is on session termination to kill the VNC server. Try tigervncserver -autokill no to prevent this. Moreover, try tigervncserver -xstartup /usr/bin/xterm -- to get a simple X terminal going in the VNC server. Note the --. Otherwise /usr/bin/xterm will be started with the session argument, i.e., startxfce4 in your case. By the way, this is not the standard configuration. Someone must have edited some configuration files to specify the xfce session. Best, Joachim OpenPGP_signature Description: OpenPGP digital signature
Bug#1000871: [Pkg-tigervnc-devel] Bug#1000871: tigervnc-standalone-server: server fails to start
Thanks for all your work on behalf of Debian. I certainly didn't mean to blame you for the lack of documentation, and I understand that these problems are usually upstream's fault. On Wed, 1 Dec 2021 09:47:37 +0100 Ola Lundqvist wrote: > Hi > > Thank you. > > I guess the main reason for the lack of documentation is that it is not > provided by upstream. This was the case also for tightvnc, vnc4 and vnc(3). > I wrote some documentation for those other packages but I guess it was > never done for tigervnc. > > I do not think you made anything wrong. > > Cheers > > // Ola > > On Wed, 1 Dec 2021 at 00:12, Celejar wrote: > > > Primarily the segfault, although the problem is compounded by the > > absence of documentation, which makes it difficult to know whether I'm > > doing something wrong with my invocation. > > > > On Tue, 30 Nov 2021 23:07:11 +0100 > > Ola Lundqvist wrote: > > > > > Hi > > > > > > Just a check question. Is your bug about the lack of useful documentation > > > or the fact that it segfaults? > > > It should not segfault... > > > > > > // Ola > > > > > > On Tue, 30 Nov 2021 at 15:03, Celejar wrote: > > > > > > > Package: tigervnc-standalone-server > > > > Version: 1.11.0+dfsg-3 > > > > Severity: important > > > > X-Debbugs-Cc: cele...@gmail.com > > > > > > > > This package contains no useful documentation or explanation of how to > > > > start the server in /usr/share/doc. As per 'man tigervncserver', I > > > > tried: > > > > > > > > * > > > > > > > > ~$ tigervncserver > > > > > > > > * > > > > > > > > And the server promptly segfaulted: > > > > > > > > * > > > > > > > > New Xtigervnc server '.:1 ()' on port 5901 for > > > > display :1. > > > > Use xtigervncviewer -SecurityTypes VncAuth -passwd > > > > /home//.vnc/passwd :1 to connect to the VNC server. > > > > > > > > > > > > === tail /home//.vnc/.:5901.log > > > > === > > > > Segmentation fault > > > > X connection to :1 broken (explicit kill or server shutdown). > > > > ComparingUpdateTracker: 0 pixels in / 0 pixels out > > > > ComparingUpdateTracker: (1:-nan ratio) > > > > Killing Xtigervnc process ID 9433... success! > > > > > > > > > > == > > > > > > > > Session startup via '/etc/X11/Xtigervnc-session' 'startxfce4' cleanly > > > > exited too early (< 3 seconds)! > > > > > > > > Maybe try something simple first, e.g., > > > > tigervncserver -xstartup /usr/bin/xterm > > > > The Xtigervnc server cleanly exited! > > > > The X session cleanly exited! > > > > > > > > * > > > > > > > > As per the above output, I tried: > > > > > > > > * > > > > > > > > ~$ tigervncserver -xstartup /usr/bin/xterm > > > > > > > > * > > > > > > > > No segfault, but it still didn't work: > > > > > > > > * > > > > > > > > New Xtigervnc server '.:1 ()' on port 5901 for > > > > display :1. > > > > Use xtigervncviewer -SecurityTypes VncAuth -passwd > > > > /home//.vnc/passwd :1 to connect to the VNC server. > > > > > > > > > > > > === tail /home//.vnc/.:5901.log > > > > === > > > > > > > > > > == > > > > > > > > Session startup via '/usr/bin/xterm' 'startxfce4' cleanly exited too > > early > > > > (< 3 seconds)! > > > > > > > > Maybe try something simple first, e.g., > > > > tigervncserver -xstartup /usr/bin/xterm > > > > The X session cleanly exited! > > > > Killing Xtigervnc process ID 9525... success! > > > > > > > > * > > > > > > > > -- System Information: > > > > Debian Release: bookworm/sid > > > > APT prefers unstable > > > > APT policy: (500, 'unstable') > > > > Architecture: amd64 (x86_64) > > > > Foreign Architectures: i386 > > > > > > > > Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) > > > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > > LANGUAGE > > > > not set > > > > Shell: /bin/sh linked to /usr/bin/dash > > > > Init: systemd (via /run/systemd/system) > > > > LSM: AppArmor: enabled > > > > > > > > Versions of packages tigervnc-standalone-server depends on: > > > > ii libaudit1 1:3.0.6-1+b1 > > > > ii libbsd0 0.11.3-1 > > > > ii libc6 2.32-4 > > > > ii libfile-readbackwards-perl 1.06-1 > > > > ii libgcrypt20 1.9.4-4 > > > > ii libgl1 1.3.4-2+b1 > > > > ii libgnutls30 3.7.2-2 > > > > ii libjpeg62-turbo 1:2.1.2-1 > > > > ii libpam0g1.4.0-10 > > > > ii libpixman-1-0 0.40.0-1 > > > > ii libselinux1 3.3-1+b1 > > > > ii libstdc++6 11.2.0-12 > > > > ii libsystemd0 249.7-1 > > > > ii libunwind8
Bug#1000871: [Pkg-tigervnc-devel] Bug#1000871: tigervnc-standalone-server: server fails to start
Hi Thank you. I guess the main reason for the lack of documentation is that it is not provided by upstream. This was the case also for tightvnc, vnc4 and vnc(3). I wrote some documentation for those other packages but I guess it was never done for tigervnc. I do not think you made anything wrong. Cheers // Ola On Wed, 1 Dec 2021 at 00:12, Celejar wrote: > Primarily the segfault, although the problem is compounded by the > absence of documentation, which makes it difficult to know whether I'm > doing something wrong with my invocation. > > On Tue, 30 Nov 2021 23:07:11 +0100 > Ola Lundqvist wrote: > > > Hi > > > > Just a check question. Is your bug about the lack of useful documentation > > or the fact that it segfaults? > > It should not segfault... > > > > // Ola > > > > On Tue, 30 Nov 2021 at 15:03, Celejar wrote: > > > > > Package: tigervnc-standalone-server > > > Version: 1.11.0+dfsg-3 > > > Severity: important > > > X-Debbugs-Cc: cele...@gmail.com > > > > > > This package contains no useful documentation or explanation of how to > > > start the server in /usr/share/doc. As per 'man tigervncserver', I > > > tried: > > > > > > * > > > > > > ~$ tigervncserver > > > > > > * > > > > > > And the server promptly segfaulted: > > > > > > * > > > > > > New Xtigervnc server '.:1 ()' on port 5901 for > > > display :1. > > > Use xtigervncviewer -SecurityTypes VncAuth -passwd > > > /home//.vnc/passwd :1 to connect to the VNC server. > > > > > > > > > === tail /home//.vnc/.:5901.log > > > === > > > Segmentation fault > > > X connection to :1 broken (explicit kill or server shutdown). > > > ComparingUpdateTracker: 0 pixels in / 0 pixels out > > > ComparingUpdateTracker: (1:-nan ratio) > > > Killing Xtigervnc process ID 9433... success! > > > > > > > == > > > > > > Session startup via '/etc/X11/Xtigervnc-session' 'startxfce4' cleanly > > > exited too early (< 3 seconds)! > > > > > > Maybe try something simple first, e.g., > > > tigervncserver -xstartup /usr/bin/xterm > > > The Xtigervnc server cleanly exited! > > > The X session cleanly exited! > > > > > > * > > > > > > As per the above output, I tried: > > > > > > * > > > > > > ~$ tigervncserver -xstartup /usr/bin/xterm > > > > > > * > > > > > > No segfault, but it still didn't work: > > > > > > * > > > > > > New Xtigervnc server '.:1 ()' on port 5901 for > > > display :1. > > > Use xtigervncviewer -SecurityTypes VncAuth -passwd > > > /home//.vnc/passwd :1 to connect to the VNC server. > > > > > > > > > === tail /home//.vnc/.:5901.log > > > === > > > > > > > == > > > > > > Session startup via '/usr/bin/xterm' 'startxfce4' cleanly exited too > early > > > (< 3 seconds)! > > > > > > Maybe try something simple first, e.g., > > > tigervncserver -xstartup /usr/bin/xterm > > > The X session cleanly exited! > > > Killing Xtigervnc process ID 9525... success! > > > > > > * > > > > > > -- System Information: > > > Debian Release: bookworm/sid > > > APT prefers unstable > > > APT policy: (500, 'unstable') > > > Architecture: amd64 (x86_64) > > > Foreign Architectures: i386 > > > > > > Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) > > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE > > > not set > > > Shell: /bin/sh linked to /usr/bin/dash > > > Init: systemd (via /run/systemd/system) > > > LSM: AppArmor: enabled > > > > > > Versions of packages tigervnc-standalone-server depends on: > > > ii libaudit1 1:3.0.6-1+b1 > > > ii libbsd0 0.11.3-1 > > > ii libc6 2.32-4 > > > ii libfile-readbackwards-perl 1.06-1 > > > ii libgcrypt20 1.9.4-4 > > > ii libgl1 1.3.4-2+b1 > > > ii libgnutls30 3.7.2-2 > > > ii libjpeg62-turbo 1:2.1.2-1 > > > ii libpam0g1.4.0-10 > > > ii libpixman-1-0 0.40.0-1 > > > ii libselinux1 3.3-1+b1 > > > ii libstdc++6 11.2.0-12 > > > ii libsystemd0 249.7-1 > > > ii libunwind8 1.3.2-2 > > > ii libxau6 1:1.0.9-1 > > > ii libxdmcp6 1:1.1.2-3 > > > ii libxfont2 1:2.0.5-1 > > > ii perl5.32.1-6 > > > ii tigervnc-common 1.11.0+dfsg-3 > > > ii x11-xkb-utils 7.7+5 > > > ii xauth 1:1.1-1 > > > ii xkb-data2.33-1 > > > ii zlib1g 1:1.2.11.dfsg-2 > > > > > > Versions of packages tigervnc-standalone-server recommends: > > > ii
Bug#1000871: [Pkg-tigervnc-devel] Bug#1000871: tigervnc-standalone-server: server fails to start
Primarily the segfault, although the problem is compounded by the absence of documentation, which makes it difficult to know whether I'm doing something wrong with my invocation. On Tue, 30 Nov 2021 23:07:11 +0100 Ola Lundqvist wrote: > Hi > > Just a check question. Is your bug about the lack of useful documentation > or the fact that it segfaults? > It should not segfault... > > // Ola > > On Tue, 30 Nov 2021 at 15:03, Celejar wrote: > > > Package: tigervnc-standalone-server > > Version: 1.11.0+dfsg-3 > > Severity: important > > X-Debbugs-Cc: cele...@gmail.com > > > > This package contains no useful documentation or explanation of how to > > start the server in /usr/share/doc. As per 'man tigervncserver', I > > tried: > > > > * > > > > ~$ tigervncserver > > > > * > > > > And the server promptly segfaulted: > > > > * > > > > New Xtigervnc server '.:1 ()' on port 5901 for > > display :1. > > Use xtigervncviewer -SecurityTypes VncAuth -passwd > > /home//.vnc/passwd :1 to connect to the VNC server. > > > > > > === tail /home//.vnc/.:5901.log > > === > > Segmentation fault > > X connection to :1 broken (explicit kill or server shutdown). > > ComparingUpdateTracker: 0 pixels in / 0 pixels out > > ComparingUpdateTracker: (1:-nan ratio) > > Killing Xtigervnc process ID 9433... success! > > > > == > > > > Session startup via '/etc/X11/Xtigervnc-session' 'startxfce4' cleanly > > exited too early (< 3 seconds)! > > > > Maybe try something simple first, e.g., > > tigervncserver -xstartup /usr/bin/xterm > > The Xtigervnc server cleanly exited! > > The X session cleanly exited! > > > > * > > > > As per the above output, I tried: > > > > * > > > > ~$ tigervncserver -xstartup /usr/bin/xterm > > > > * > > > > No segfault, but it still didn't work: > > > > * > > > > New Xtigervnc server '.:1 ()' on port 5901 for > > display :1. > > Use xtigervncviewer -SecurityTypes VncAuth -passwd > > /home//.vnc/passwd :1 to connect to the VNC server. > > > > > > === tail /home//.vnc/.:5901.log > > === > > > > == > > > > Session startup via '/usr/bin/xterm' 'startxfce4' cleanly exited too early > > (< 3 seconds)! > > > > Maybe try something simple first, e.g., > > tigervncserver -xstartup /usr/bin/xterm > > The X session cleanly exited! > > Killing Xtigervnc process ID 9525... success! > > > > * > > > > -- System Information: > > Debian Release: bookworm/sid > > APT prefers unstable > > APT policy: (500, 'unstable') > > Architecture: amd64 (x86_64) > > Foreign Architectures: i386 > > > > Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE > > not set > > Shell: /bin/sh linked to /usr/bin/dash > > Init: systemd (via /run/systemd/system) > > LSM: AppArmor: enabled > > > > Versions of packages tigervnc-standalone-server depends on: > > ii libaudit1 1:3.0.6-1+b1 > > ii libbsd0 0.11.3-1 > > ii libc6 2.32-4 > > ii libfile-readbackwards-perl 1.06-1 > > ii libgcrypt20 1.9.4-4 > > ii libgl1 1.3.4-2+b1 > > ii libgnutls30 3.7.2-2 > > ii libjpeg62-turbo 1:2.1.2-1 > > ii libpam0g1.4.0-10 > > ii libpixman-1-0 0.40.0-1 > > ii libselinux1 3.3-1+b1 > > ii libstdc++6 11.2.0-12 > > ii libsystemd0 249.7-1 > > ii libunwind8 1.3.2-2 > > ii libxau6 1:1.0.9-1 > > ii libxdmcp6 1:1.1.2-3 > > ii libxfont2 1:2.0.5-1 > > ii perl5.32.1-6 > > ii tigervnc-common 1.11.0+dfsg-3 > > ii x11-xkb-utils 7.7+5 > > ii xauth 1:1.1-1 > > ii xkb-data2.33-1 > > ii zlib1g 1:1.2.11.dfsg-2 > > > > Versions of packages tigervnc-standalone-server recommends: > > ii libgl1-mesa-dri21.2.6-1 > > ii x11-xserver-utils 7.7+9 > > ii xfonts-base1:1.0.5 > > > > Versions of packages tigervnc-standalone-server suggests: > > ii xfonts-100dpi1:1.0.4+nmu1.1 > > ii xfonts-75dpi 1:1.0.4+nmu1.1 > > ii xfonts-scalable 1:1.0.3-1.2 > > > > -- no debconf information > > > > ___ > > Pkg-tigervnc-devel mailing list > > pkg-tigervnc-de...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-tigervnc-devel > > > > > -- > - Ola Lundqvist --- > / o...@debian.org
Bug#1000871: [Pkg-tigervnc-devel] Bug#1000871: tigervnc-standalone-server: server fails to start
Hi Just a check question. Is your bug about the lack of useful documentation or the fact that it segfaults? It should not segfault... // Ola On Tue, 30 Nov 2021 at 15:03, Celejar wrote: > Package: tigervnc-standalone-server > Version: 1.11.0+dfsg-3 > Severity: important > X-Debbugs-Cc: cele...@gmail.com > > This package contains no useful documentation or explanation of how to > start the server in /usr/share/doc. As per 'man tigervncserver', I > tried: > > * > > ~$ tigervncserver > > * > > And the server promptly segfaulted: > > * > > New Xtigervnc server '.:1 ()' on port 5901 for > display :1. > Use xtigervncviewer -SecurityTypes VncAuth -passwd > /home//.vnc/passwd :1 to connect to the VNC server. > > > === tail /home//.vnc/.:5901.log > === > Segmentation fault > X connection to :1 broken (explicit kill or server shutdown). > ComparingUpdateTracker: 0 pixels in / 0 pixels out > ComparingUpdateTracker: (1:-nan ratio) > Killing Xtigervnc process ID 9433... success! > > == > > Session startup via '/etc/X11/Xtigervnc-session' 'startxfce4' cleanly > exited too early (< 3 seconds)! > > Maybe try something simple first, e.g., > tigervncserver -xstartup /usr/bin/xterm > The Xtigervnc server cleanly exited! > The X session cleanly exited! > > * > > As per the above output, I tried: > > * > > ~$ tigervncserver -xstartup /usr/bin/xterm > > * > > No segfault, but it still didn't work: > > * > > New Xtigervnc server '.:1 ()' on port 5901 for > display :1. > Use xtigervncviewer -SecurityTypes VncAuth -passwd > /home//.vnc/passwd :1 to connect to the VNC server. > > > === tail /home//.vnc/.:5901.log > === > > == > > Session startup via '/usr/bin/xterm' 'startxfce4' cleanly exited too early > (< 3 seconds)! > > Maybe try something simple first, e.g., > tigervncserver -xstartup /usr/bin/xterm > The X session cleanly exited! > Killing Xtigervnc process ID 9525... success! > > * > > -- System Information: > Debian Release: bookworm/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE > not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages tigervnc-standalone-server depends on: > ii libaudit1 1:3.0.6-1+b1 > ii libbsd0 0.11.3-1 > ii libc6 2.32-4 > ii libfile-readbackwards-perl 1.06-1 > ii libgcrypt20 1.9.4-4 > ii libgl1 1.3.4-2+b1 > ii libgnutls30 3.7.2-2 > ii libjpeg62-turbo 1:2.1.2-1 > ii libpam0g1.4.0-10 > ii libpixman-1-0 0.40.0-1 > ii libselinux1 3.3-1+b1 > ii libstdc++6 11.2.0-12 > ii libsystemd0 249.7-1 > ii libunwind8 1.3.2-2 > ii libxau6 1:1.0.9-1 > ii libxdmcp6 1:1.1.2-3 > ii libxfont2 1:2.0.5-1 > ii perl5.32.1-6 > ii tigervnc-common 1.11.0+dfsg-3 > ii x11-xkb-utils 7.7+5 > ii xauth 1:1.1-1 > ii xkb-data2.33-1 > ii zlib1g 1:1.2.11.dfsg-2 > > Versions of packages tigervnc-standalone-server recommends: > ii libgl1-mesa-dri21.2.6-1 > ii x11-xserver-utils 7.7+9 > ii xfonts-base1:1.0.5 > > Versions of packages tigervnc-standalone-server suggests: > ii xfonts-100dpi1:1.0.4+nmu1.1 > ii xfonts-75dpi 1:1.0.4+nmu1.1 > ii xfonts-scalable 1:1.0.3-1.2 > > -- no debconf information > > ___ > Pkg-tigervnc-devel mailing list > pkg-tigervnc-de...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-tigervnc-devel > -- - Ola Lundqvist --- / o...@debian.org o...@inguza.com \ | http://inguza.com/ +46 (0)70-332 1551 | ---
