Dear Michal, thanks for your quick response. On Donnerstag, 2. August 2018 09:15:46 Michal Srb wrote:
On středa 1. srpna 2018 22:22:16 CEST Hans-Peter Jansen wrote:
Dear Stefan, hi list,
Hi,
I am maintainer of tigervnc, I'll be looking into this.
after returning from vacation, I upgraded a tumbleweed installation (zypper dup), but X doesn't start anymore. It boiled down to:
[ 30.576] (EE) [ 30.576] (EE) Backtrace: [ 30.576] (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x79) [0x562f82784949] [ 30.577] (EE) 1: /usr/bin/Xorg (0x562f825d3000+0x1b5619) [0x562f82788619] [ 30.577] (EE) 2: /lib64/libpthread.so.0 (0x7efe94f98000+0x11f70) [0x7efe94fa9f70] [ 30.577] (EE) 3: /usr/lib64/xorg/modules/extensions/libvnc.so (vncRandRGetOutputCount+0x47) [0x7efe92e8add7] [ 30.577] (EE) 4: /usr/lib64/xorg/modules/extensions/libvnc.so (_ZN14XserverDesktop19computeScreenLayoutEv+0xb1) [0x7efe92e8d471] [ 30.577] (EE) 5: /usr/lib64/xorg/modules/extensions/libvnc.so (_ZN14XserverDesktop14setFramebufferEiiPvi+0x93) [0x7efe92e8d913] [ 30.577] (EE) 6: /usr/lib64/xorg/modules/extensions/libvnc.so (_ZN14XserverDesktopC2EiNSt7__cxx114listIPN7network11TcpListenerESaIS4_EEE S6 _PKcRKN3rfb11PixelFormatEiiPvi+0x20f) [0x7efe92e8dc2f] [ 30.577] (EE) 7: /usr/lib64/xorg/modules/extensions/libvnc.so (vncExtensionInit+0x364) [0x7efe92e83bc4] [ 30.577] (EE) 8: /usr/bin/Xorg (InitExtensions+0x89) [0x562f8269be09] [ 30.577] (EE) 9: /usr/bin/Xorg (0x562f825d3000+0x5efeb) [0x562f82631feb] [ 30.577] (EE) 10: /lib64/libc.so.6 (__libc_start_main+0xeb) [0x7efe94bfafeb] [ 30.577] (EE) 11: /usr/bin/Xorg (_start+0x2a) [0x562f8261bf6a] [ 30.577] (EE) [ 30.577] (EE) Segmentation fault at address 0x0 [ 30.577] (EE) Fatal server error: [ 30.577] (EE) Caught signal 11 (Segmentation fault). Server aborting
Deviation from a standard installation:
libvnc is enabled with default parameters (in /etc/X11/xorg.conf.d/10- libvnc.conf), display manager is kdm of course, (since sddm doesn't support XDMCP).
System is using an AMD A6-6400K APU with Radeon(tm) HD Graphics
Reverting to Tumbleweed as of 2 weeks ago (last dup: 10180719 00:48) fixes this problem and makes the system usable again. Disabling VNC makes X work as well, but it is *primary* used via VNC.
Does anything changed with randr (protocol) lately, that tigervnc depends on?
I was able to reproduce it on my Tumbleweed test machine. It is likely caused by some change in X server 1.20.0.
Confirmed: last working setup is using 1.19.6.
Any other ideas? bugzilla?
Please open a bug in bugzilla and let's move the discussion there. I'll need a bug to reference in the end. :-)
Done: bz#1103537 https://bugzilla.opensuse.org/show_bug.cgi?id=1103537
While at it: Identifier "Screen0" in /etc/X11/xorg.conf.d/10-libvnc.conf is missing a closing ". SR?
Good catch. You can make a SR, or I'll submit it together with fix for this.
I attempted to build a tigervnc 1.9.0, based on our 1.8.0, but failed so far. Most patches apply with manual fixes only, some are upstream, but are missing hunks, the cert and autoconf patches aren't applicable easily, and in the end, it failed to compile :-(. Postponed it..
Right, update to 1.9.0 is waiting to be done. And looking at the release notes, it may actually fix the compatibility with X server 1.20.0 as well.
I see, will look into this now. Cheers, Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org