Bug#814982: [xwayland] Reproducible segmentation fault when pluggin new screen
Sorry guys I didn't have the time to check the patch as it is on my work laptop. I rebuild xwayland from source with the attached patch and so far I haven't been able to reproduce so it seems to fix it indeed. Could this be included in a futur release ? Thanks a lot Cheers Letic On 02/03/16 03:19, Yasushi SHOJI wrote: > On Wed, 02 Mar 2016 08:05:07 +0900, > Julian Andres Klode wrote: >> This could be related / the fix: >> >> https://cgit.freedesktop.org/xorg/xserver/commit/?id=2116f03be04240e961649ca750a7aa5438b8446c > Indeed. The commit fixed the problem on my system. > Thanks, > -- >yashi --- a/hw/xwayland/xwayland-output.c +++ b/hw/xwayland/xwayland-output.c @@ -297,6 +297,7 @@ xwl_output_destroy(struct xwl_output *xwl_output) wl_output_destroy(xwl_output->output); xorg_list_del(_output->link); +RRCrtcDestroy(xwl_output->randr_crtc); RROutputDestroy(xwl_output->randr_output); xorg_list_for_each_entry(it, _screen->output_list, link) --
Bug#814982: [xwayland] Reproducible segmentation fault when pluggin new screen
On Wed, 02 Mar 2016 08:05:07 +0900, Julian Andres Klode wrote: > > This could be related / the fix: > > https://cgit.freedesktop.org/xorg/xserver/commit/?id=2116f03be04240e961649ca750a7aa5438b8446c Indeed. The commit fixed the problem on my system. Thanks, -- yashi
Bug#814982: [xwayland] Reproducible segmentation fault when pluggin new screen
On Wed, Feb 17, 2016 at 11:33:56AM +0100, Anthony Callegaro wrote: > Package: xwayland > Version: 2:1.18.1-1 > Severity: important > > --- Please enter the report below this line. --- > > Hello dear maintainer, > > I have been using sid as my main OS since 2001 and over the last couple > of years there has been so few breakage that I didn't even notice that > gnome-session switched to XWayland :) Great work ! > > I have been experiencing some segmentation faults lately that I thought > were due to Xorg which seems actually linked to the recent upgrade to > XWayland 1.18.1-1. > > When plugging a HDMI screen I get the following segmentation fault : > > (EE) Backtrace: > (EE) 0: /usr/bin/Xwayland (xorg_backtrace+0x4e) [0x55cbedb20b0e] > (EE) 1: /usr/bin/Xwayland (0x55cbed986000+0x19ee99) [0x55cbedb24e99] > (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fa3c5e83000+0x33590) > [0x7fa3c5eb6590] > (EE) 3: /usr/bin/Xwayland (MakeAtom+0x30) [0x55cbedad92f0] > (EE) 4: /usr/bin/Xwayland (0x55cbed986000+0xe7cd8) [0x55cbeda6dcd8] > (EE) 5: /usr/bin/Xwayland (0x55cbed986000+0xe8739) [0x55cbeda6e739] > (EE) 6: /usr/bin/Xwayland (0x55cbed986000+0xe8d5b) [0x55cbeda6ed5b] > (EE) 7: /usr/bin/Xwayland (0x55cbed986000+0x164dcf) [0x55cbedaeadcf] > (EE) 8: /usr/bin/Xwayland (0x55cbed986000+0x168de3) [0x55cbedaeede3] > (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) > [0x7fa3c5ea3870] > (EE) 10: /usr/bin/Xwayland (_start+0x29) [0x55cbed9bf019] > (EE) > (EE) Segmentation fault at address 0x20 > (EE) > Fatal server error: > (EE) Caught signal 11 (Segmentation fault). Server aborting > > I installed libwayland-server0-dbg but it doesn't seems to yield more > information in the backtrace. > > (see attached syslog for full event log there doesn't seems to be more > info in journalctl) > > This is always reproducible by either plugging/unplugging the cable or > hitting the Super+P shortcut to switch through xrandr possibilities. This could be related / the fix: https://cgit.freedesktop.org/xorg/xserver/commit/?id=2116f03be04240e961649ca750a7aa5438b8446c It talks about removal of crtcs only, but maybe that also happens during discovery of new outputs. -- Debian Developer - deb.li/jak | jak-linux.org - free software dev When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to (`inline'). Thank you.
Bug#814982: [xwayland] Reproducible segmentation fault when pluggin new screen
Hi, I experience the same problem. I temporarily fixed it by uncommenting "WaylandEnable=false" in /etc/gdm3/daemon.conf. This prevents the problematic xwayland from even loading up. It hasn't crashed since. Neither have I experienced side effects from using gdm in this "legacy" xserver only mode. So until there is a proper fix this might be more convenient than downgrading the package and putting it on hold. Dave
Bug#814982: [xwayland] Reproducible segmentation fault when pluggin new screen
Package: xwayland Version: 2:1.18.1-1 Severity: important --- Please enter the report below this line. --- Hello dear maintainer, I have been using sid as my main OS since 2001 and over the last couple of years there has been so few breakage that I didn't even notice that gnome-session switched to XWayland :) Great work ! I have been experiencing some segmentation faults lately that I thought were due to Xorg which seems actually linked to the recent upgrade to XWayland 1.18.1-1. When plugging a HDMI screen I get the following segmentation fault : (EE) Backtrace: (EE) 0: /usr/bin/Xwayland (xorg_backtrace+0x4e) [0x55cbedb20b0e] (EE) 1: /usr/bin/Xwayland (0x55cbed986000+0x19ee99) [0x55cbedb24e99] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fa3c5e83000+0x33590) [0x7fa3c5eb6590] (EE) 3: /usr/bin/Xwayland (MakeAtom+0x30) [0x55cbedad92f0] (EE) 4: /usr/bin/Xwayland (0x55cbed986000+0xe7cd8) [0x55cbeda6dcd8] (EE) 5: /usr/bin/Xwayland (0x55cbed986000+0xe8739) [0x55cbeda6e739] (EE) 6: /usr/bin/Xwayland (0x55cbed986000+0xe8d5b) [0x55cbeda6ed5b] (EE) 7: /usr/bin/Xwayland (0x55cbed986000+0x164dcf) [0x55cbedaeadcf] (EE) 8: /usr/bin/Xwayland (0x55cbed986000+0x168de3) [0x55cbedaeede3] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7fa3c5ea3870] (EE) 10: /usr/bin/Xwayland (_start+0x29) [0x55cbed9bf019] (EE) (EE) Segmentation fault at address 0x20 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting I installed libwayland-server0-dbg but it doesn't seems to yield more information in the backtrace. (see attached syslog for full event log there doesn't seems to be more info in journalctl) This is always reproducible by either plugging/unplugging the cable or hitting the Super+P shortcut to switch through xrandr possibilities. I worked around the issue by downgrading xwayland (and only this package) to 1.18.0-3. I also experienced a crash by pluggin an Mini-displayport adapter which resulted in an intel driver exception see syslog.1 (don't know if it's relevant just saying if it can help) Let me know what information you will need to troubelshoot this further. Thanks a lot in advance Cheers LeTic --- System information. --- Architecture: amd64 Kernel: Linux 4.3.0-1-amd64 Debian Release: stretch/sid 600 unstable ftp.ch.debian.org 600 unstable download.jitsi.org 500 testing ftp.ch.debian.org 400 stable download.videolan.org 400 stable dl.google.com 100 trusty-getdeb archive.getdeb.net 1 experimental ftp.ch.debian.org --- Package information. --- Depends (Version) | Installed ==-+- xserver-common (>= 2:1.16.1-1) | 2:1.18.1-1 libaudit1 (>= 1:2.2.1) | 1:2.4.5-1 libc6 (>= 2.17) | libdrm2 (>= 2.3.1) | libegl1-mesa (>= 7.8.1) | OR libegl1-x11 | libepoxy0 (>= 1.0) | libgbm1 (>= 10.2~0) | libgcrypt20 (>= 1.6.1) | libgl1-mesa-glx | OR libgl1 | libpixman-1-0 (>= 0.30.0) | libselinux1 (>= 2.0.82) | libwayland-client0 (>= 1.3.92) | libxau6 | libxdmcp6 | libxfont1 (>= 1:1.4.2) | libxshmfence1 | Package's Recommends field is empty. Package's Suggests field is empty. Feb 17 10:41:48 asusacallegaro gnome-session[10301]: Window manager warning: Failed to read EDID of output eDP34: No such file or directory Feb 17 10:41:48 asusacallegaro gnome-session[10301]: Window manager warning: Failed to read EDID of output eDP34: No such file or directory Feb 17 10:41:48 asusacallegaro gnome-session[10301]: Window manager warning: Failed to read EDID of output eDP34: No such file or directory Feb 17 10:41:48 asusacallegaro /usr/lib/gdm3/gdm-x-session[10421]: (II) intel(0): EDID vendor "PHL", prod id 2283 Feb 17 10:41:48 asusacallegaro /usr/lib/gdm3/gdm-x-session[10421]: (II) intel(0): Using hsync ranges from config file Feb 17 10:41:48 asusacallegaro /usr/lib/gdm3/gdm-x-session[10421]: (II) intel(0): Using vrefresh ranges from config file Feb 17 10:41:48 asusacallegaro /usr/lib/gdm3/gdm-x-session[10421]: (II) intel(0): Printing DDC gathered Modelines: Feb 17 10:41:48 asusacallegaro /usr/lib/gdm3/gdm-x-session[10421]: (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) Feb 17 10:41:48 asusacallegaro /usr/lib/gdm3/gdm-x-session[10421]: (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Feb 17 10:41:48 asusacallegaro /usr/lib/gdm3/gdm-x-session[10421]: (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Feb 17 10:41:48 asusacallegaro /usr/lib/gdm3/gdm-x-session[10421]: (II) intel(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Feb 17 10:41:48 asusacallegaro /usr/lib/gdm3/gdm-x-session[10421]: (II) intel(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Feb 17 10:41:48 asusacallegaro /usr/lib/gdm3/gdm-x-session[10421]: (II) intel(0): Modeline
