Launchpad has imported 17 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1511681.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2017-11-09T20:49:38+00:00 Michael wrote: Version-Release number of selected component: xorg-x11-server-Xwayland-1.19.3-4.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /home/mcatanzaro/Projects/GNOME/install/bin/Xwayland :1 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6 crash_function: xwl_read_events executable: /usr/bin/Xwayland journald_cursor: s=ca44c691f28b4a3fa6affd95ab5151f5;i=1b36b7;b=1bb81d6006b3438f9124fe2aa5b58740;m=a0fe9fcbc;t=55ce29a097191;x=9b45217435b11c67 kernel: 4.13.9-200.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/0 ------------------------------------------------------------------------ On 2017-11-09T20:49:46+00:00 Michael wrote: Created attachment 1350099 File: backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/1 ------------------------------------------------------------------------ On 2017-11-09T20:49:47+00:00 Michael wrote: Created attachment 1350100 File: cgroup Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/2 ------------------------------------------------------------------------ On 2017-11-09T20:49:48+00:00 Michael wrote: Created attachment 1350101 File: core_backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/3 ------------------------------------------------------------------------ On 2017-11-09T20:49:49+00:00 Michael wrote: Created attachment 1350102 File: cpuinfo Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/4 ------------------------------------------------------------------------ On 2017-11-09T20:49:50+00:00 Michael wrote: Created attachment 1350103 File: dso_list Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/5 ------------------------------------------------------------------------ On 2017-11-09T20:49:51+00:00 Michael wrote: Created attachment 1350104 File: environ Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/6 ------------------------------------------------------------------------ On 2017-11-09T20:49:52+00:00 Michael wrote: Created attachment 1350105 File: limits Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/7 ------------------------------------------------------------------------ On 2017-11-09T20:49:53+00:00 Michael wrote: Created attachment 1350106 File: maps Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/8 ------------------------------------------------------------------------ On 2017-11-09T20:49:55+00:00 Michael wrote: Created attachment 1350107 File: open_fds Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/9 ------------------------------------------------------------------------ On 2017-11-09T20:49:56+00:00 Michael wrote: Created attachment 1350108 File: proc_pid_status Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/10 ------------------------------------------------------------------------ On 2017-11-09T20:49:57+00:00 Michael wrote: Created attachment 1350109 File: var_log_messages Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/11 ------------------------------------------------------------------------ On 2017-11-10T09:26:11+00:00 Olivier wrote: Same as bug 1510078, this is a abort() because Xwayland (Wayland client) cannot read events from the Wayland compositor (gnome-shell.mutter, presumably) which is most likely a crash in gnome-shell/mutter in the first place. xwl_read_events() aborts in two cases, either it fails to read the events (wl_display_read_events) or it fails to dispatch the events (wl_display_dispatch_pending), in both cases it's a communication issue with the Wayland compositor. Can you quickly check in the logs at the time of the crash if gnome- shell/mutter had crashed or failed to start (I've seen this happening as well at startup, gnome-shell starts, spawns Xwayland, then fails, and Xwayland aborts in xwl_read_events()) Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/12 ------------------------------------------------------------------------ On 2017-11-18T06:51:36+00:00 Justin wrote: I am also experiencing this on Fedora 27, 4.14.0-1, Nouveau, t I think you're right Olivier, this is likely from a crash in mutter: I see in the logs: gnome-shell: segfault at ... in libmutter-1.so.0.0.0... gnome-logs: Error reading events from display: Connection reset by peer kernel: (EE) Xwayland: ANOM_ABEND ... gnome-session-b: gnome-session-binary: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 (stack trace...) systemd:coredum: Process 2515 (gnome-shell) of user 1000 dumped core. The stack trace has: #0 and #1 in libc.so.6 #2 OsAbort (Xwayland) #3 AbortServer (Xwayland) #4 FatalError (Xwayland) #5 xwl_read_events (Xwayland) #6 ospoll_wait (Xwayland) I haven't been able to determine if some user action causes this. It seems to happen when I have the screen off (perhaps a notification triggers this crash? or turning the screen on, which activates the Displayport link, triggers the crash?) I have mutter and gnome-shell at 3.26.2-1, and gnome-session(-xsession, -wayland-session) at 3.26.1-1. Please let me know what more would be useful. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/20 ------------------------------------------------------------------------ On 2017-12-12T23:25:14+00:00 rugk wrote: Maybe that is related to my issue Bug 1513807 ? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/24 ------------------------------------------------------------------------ On 2017-12-13T05:50:50+00:00 Raymond wrote: I was also experiencing this same problem after fresh install of Fedora 27. The problem is easily and always reproducible. The steps are : 1. login properly 2. power off monitor (or wait until screen saver cause the monitor to auto-sleep) 3. power back on the monitor (or wake-up from monitor sleep mode) It reports "gnome-shell" was crashed and I have to re-login again. I used just an ordinary HDMI full-HD monitor. This always happens, even just after fresh reboot. Should be something when the HDMI connection back on caused something to crash. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/25 ------------------------------------------------------------------------ On 2017-12-13T13:21:09+00:00 Olivier wrote: This is simply Xwayland telling your Wayland compositor (namely gnome- shell/mutter) has died. Basically, gnome-shell (now) runs Xwayland with “-core” which means that *any* FatalError() in Xwayland will dump a core file. xwl_read_events() triggers a FatalError() because the Wayland socket is unusable, and it's unusable because the Wayland compositor (the other side of the socket) has died, i.e. crashed most likely. The Wayland compositor is gnome-shell/mutter, so if you could please look into journalctl and coredumpctl to find a backtrace and/or generate one with coredumpctl and gdb. >From comment 15, this is most likely a dupe of bug 1500325. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1731911/comments/26 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1731911 Title: Xwayland crashed with SIGABRT in OsAbort() Status in X.Org X server: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in xorg-server package in Fedora: Confirmed Bug description: no idea how to reproduce ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Nov 13 13:55:16 2017 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-15-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:1507] InstallationDate: Installed on 2013-09-03 (1531 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=fr_FR.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () ?? () Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1731911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
