You are not logged in.
Hi, since the upgrade to gnome-shell 3.30, I face this reproducible bug:
Everything works fine until GDM prompts for password
then, once gnome-shell starts
if I have no external display attached, the session opens with success
if I have my external monitors attached, gnome-shell segfaults
any idea?
journalctl extract:
sept. 25 09:32:14 R2D2-X1 org.gnome.Shell.desktop[1992]: glamor: No eglstream capable devices found
sept. 25 09:32:14 R2D2-X1 audit[1992]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=1992 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=11 res=1
sept. 25 09:32:14 R2D2-X1 kernel: gnome-shell[1992]: segfault at 1c ip 00007f66fa6d9280 sp 00007ffe6ac25518 error 4 in libmutter-3.so.0.0.0[7f66fa6ce000+d3000]
sept. 25 09:32:14 R2D2-X1 kernel: Code: 00 c3 0f 1f 84 00 00 00 00 00 f3 0f 10 47 38 c3 66 2e 0f 1f 84 00 00 00 00 00 8b 47 3c c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 <48> 8b 47 1c 48 8b 57 24 c3 0f 1f 80 00 00 00 00 48 8b 47 48 c3 66
sept. 25 09:32:14 R2D2-X1 kernel: audit: type=1701 audit(1537860734.810:114): auid=1000 uid=1000 gid=1000 ses=2 pid=1992 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=11 res=1
sept. 25 09:32:14 R2D2-X1 systemd[1]: Created slice system-systemd\x2dcoredump.slice.
sept. 25 09:32:14 R2D2-X1 systemd[1]: Started Process Core Dump (PID 2020/UID 0).
sept. 25 09:32:14 R2D2-X1 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-2020-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sept. 25 09:32:14 R2D2-X1 kernel: audit: type=1130 audit(1537860734.813:115): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-2020-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sept. 25 09:32:15 R2D2-X1 audit[2019]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=2019 comm="Xwayland" exe="/usr/bin/Xwayland" sig=6 res=1
sept. 25 09:32:15 R2D2-X1 gnome-session-binary[1961]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
sept. 25 09:32:15 R2D2-X1 gnome-session-binary[1961]: Unrecoverable failure in required component org.gnome.Shell.desktop
sept. 25 09:32:16 R2D2-X1 kernel: audit: type=1701 audit(1537860735.193:116): auid=1000 uid=1000 gid=1000 ses=2 pid=2019 comm="Xwayland" exe="/usr/bin/Xwayland" sig=6 res=1
sept. 25 09:32:16 R2D2-X1 kernel: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.
sept. 25 09:32:15 R2D2-X1 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-2020-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sept. 25 09:32:15 R2D2-X1 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@1-2022-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sept. 25 09:32:16 R2D2-X1 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@1-2022-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sept. 25 09:32:16 R2D2-X1 gnome-session[1961]: gnome-session-binary[1961]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
sept. 25 09:32:16 R2D2-X1 org.gnome.Shell.desktop[1992]: (EE)
sept. 25 09:32:16 R2D2-X1 org.gnome.Shell.desktop[1992]: Fatal server error:
sept. 25 09:32:16 R2D2-X1 org.gnome.Shell.desktop[1992]: (EE) Error sending request: Broken pipe
sept. 25 09:32:16 R2D2-X1 org.gnome.Shell.desktop[1992]: (EE)
sept. 25 09:32:16 R2D2-X1 audit[1940]: USER_LOGOUT pid=1940 uid=0 auid=1000 ses=2 msg='uid=1000 exe="/usr/lib/gdm-session-worker" hostname=? addr=? terminal=? res=success'
sept. 25 09:32:15 R2D2-X1 systemd-coredump[2021]: Process 1992 (gnome-shell) of user 1000 dumped core.
Stack trace of thread 1992:
#0 0x00007f66fa6d9280 meta_logical_monitor_get_layout (libmutter-3.so.0)
#1 0x00007f66fa771ef5 n/a (libmutter-3.so.0)
#2 0x00007f66f8c9d1c8 ffi_call_unix64 (libffi.so.6)
#3 0x00007f66f8c9cc2a ffi_call (libffi.so.6)
#4 0x00007f66f5c886ff n/a (libwayland-server.so.0)
#5 0x00007f66f5c850a3 n/a (libwayland-server.so.0)
#6 0x00007f66f5c86702 wl_event_loop_dispatch (libwayland-server.so.0)
#7 0x00007f66fa755da9 n/a (libmutter-3.so.0)
#8 0x00007f66fb29c3cf g_main_context_dispatch (libglib-2.0.so.0)
#9 0x00007f66fb29df89 n/a (libglib-2.0.so.0)
#10 0x00007f66fb29ef62 g_main_loop_run (libglib-2.0.so.0)
#11 0x00007f66fa757054 meta_xwayland_start (libmutter-3.so.0)
#12 0x00007f66fa756433 meta_wayland_init (libmutter-3.so.0)
#13 0x00007f66fa71c229 meta_init (libmutter-3.so.0)
#14 0x000055f71f917138 n/a (gnome-shell)
#15 0x00007f66fb7b5223 __libc_start_main (libc.so.6)
#16 0x000055f71f91750e n/a (gnome-shell)
Stack trace of thread 2018:
#0 0x00007f66fb88740d syscall (libc.so.6)
#1 0x00007f66fb24cf61 g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007f66fb2cacb3 n/a (libglib-2.0.so.0)
#3 0x00007f66fb26ed2b n/a (libglib-2.0.so.0)
#4 0x00007f66fb2673eb n/a (libglib-2.0.so.0)
#5 0x00007f66fb95ca9d start_thread (libpthread.so.0)
#6 0x00007f66fb88ca43 __clone (libc.so.6)
Stack trace of thread 1999:
#0 0x00007f66fb962afc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f66de81217c n/a (i965_dri.so)
#2 0x00007f66de811eb8 n/a (i965_dri.so)
#3 0x00007f66fb95ca9d start_thread (libpthread.so.0)
#4 0x00007f66fb88ca43 __clone (libc.so.6)
Stack trace of thread 1994:
#0 0x00007f66fb881bb1 __poll (libc.so.6)
#1 0x00007f66fb29dee0 n/a (libglib-2.0.so.0)
#2 0x00007f66fb29dfce g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f66fb29e022 n/a (libglib-2.0.so.0)
#4 0x00007f66fb2673eb n/a (libglib-2.0.so.0)
#5 0x00007f66fb95ca9d start_thread (libpthread.so.0)
#6 0x00007f66fb88ca43 __clone (libc.so.6)
Stack trace of thread 1996:
#0 0x00007f66fb88740d syscall (libc.so.6)
#1 0x00007f66fb24cf61 g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007f66fb2cacb3 n/a (libglib-2.0.so.0)
#3 0x00007f66fb26ed2b n/a (libglib-2.0.so.0)
#4 0x00007f66fb2673eb n/a (libglib-2.0.so.0)
#5 0x00007f66fb95ca9d start_thread (libpthread.so.0)
#6 0x00007f66fb88ca43 __clone (libc.so.6)
Stack trace of thread 1995:
#0 0x00007f66fb881bb1 __poll (libc.so.6)
#1 0x00007f66fb29dee0 n/a (libglib-2.0.so.0)
#2 0x00007f66fb29ef62 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f66fb403c28 n/a (libgio-2.0.so.0)
#4 0x00007f66fb2673eb n/a (libglib-2.0.so.0)
#5 0x00007f66fb95ca9d start_thread (libpthread.so.0)
#6 0x00007f66fb88ca43 __clone (libc.so.6)
Stack trace of thread 1997:
#0 0x00007f66fb881bb1 __poll (libc.so.6)
#1 0x00007f66fb29dee0 n/a (libglib-2.0.so.0)
#2 0x00007f66fb29dfce g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f66fb97fbde n/a (libdconfsettings.so)
#4 0x00007f66fb2673eb n/a (libglib-2.0.so.0)
#5 0x00007f66fb95ca9d start_thread (libpthread.so.0)
#6 0x00007f66fb88ca43 __clone (libc.so.6)
sept. 25 09:32:15 R2D2-X1 gdm-password][1940]: pam_unix(gdm-password:session): session closed for user xxx
sept. 25 09:32:15 R2D2-X1 systemd[1]: Started Process Core Dump (PID 2022/UID 0).
sept. 25 09:32:16 R2D2-X1 gdm[512]: GdmDisplay: display lasted 2,285303 seconds
sept. 25 09:32:16 R2D2-X1 systemd-coredump[2026]: Process 2019 (Xwayland) of user 1000 dumped core.
Stack trace of thread 2019:
#0 0x00007f3504445d7f raise (libc.so.6)
#1 0x00007f3504430672 abort (libc.so.6)
#2 0x0000560c41b0305a n/a (Xwayland)
#3 0x0000560c41afb425 n/a (Xwayland)
#4 0x0000560c41c223ec n/a (Xwayland)
#5 0x00007f3503d20f4a n/a (libwayland-client.so.0)
#6 0x00007f3503d1cc98 wl_proxy_marshal_array_constructor_versioned (libwayland-client.so.0)
#7 0x00007f3503d1cf0c wl_proxy_marshal_constructor (libwayland-client.so.0)
#8 0x00007f3503d1dff8 wl_display_roundtrip_queue (libwayland-client.so.0)
#9 0x0000560c41c28c0c n/a (Xwayland)
#10 0x0000560c41ac5d78 n/a (Xwayland)
#11 0x00007f3504432223 __libc_start_main (libc.so.6)
#12 0x0000560c41ac813e n/a (Xwayland)
sept. 25 09:32:16 R2D2-X1 systemd-logind[474]: Session 2 logged out. Waiting for processes to exit.
sept. 25 09:32:16 R2D2-X1 systemd-logind[474]: Removed session 2.
sept. 25 09:32:16 R2D2-X1 systemd[1]: user-runtime-dir@1000.service: Unit not needed anymore. Stopping.
sept. 25 09:32:16 R2D2-X1 systemd[1]: Stopping User Manager for UID 1000...Last edited by CircleCode (2018-10-16 17:35:10)
Offline
I don't have much useful to add other than a "me too." Very similar output and reproducible in the same manner. Have you found any additional details? I feel like I first encountered this about the same time you posted the original report, but I decided to wait it out for a bit to see if updates would fix it (they haven't).
I've got a 2016 Dell 9360, Intel graphics as below:
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) (prog-if 00 [VGA controller])
DeviceName: Onboard IGD
Subsystem: Dell HD Graphics 620
Flags: bus master, fast devsel, latency 0, IRQ 139
Memory at db000000 (64-bit, non-prefetchable) [size=16M]
Memory at 90000000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: [40] Vendor Specific Information: Len=0c <?>
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [100] Process Address Space ID (PASID)
Capabilities: [200] Address Translation Service (ATS)
Capabilities: [300] Page Request Interface (PRI)
Kernel driver in use: i915
Kernel modules: i915Last edited by JeremyT (2018-10-05 13:19:11)
Offline
I am having the same problem with a Thinkpad T420 (Intel graphics). My journalctl output looks very similar to that of the OP. However, the crash only occurs if I log in with GDM when my laptop is closed and the built-in monitor is off. If I open my laptop so that both built-in and external displays are on, I am able to log in without a problem no matter which display is primary. Perhaps this could be a temporary workaround until others provide more insight or a fix is found.
Last edited by nchishol (2018-10-08 16:21:21)
Offline
I am having the same problem with a Thinkpad T420 (Intel graphics). My journalctl output looks very similar to that of the OP. However, the crash only occurs if I log in with GDM when my laptop is closed and the built-in monitor is off. If I open my laptop so that both built-in and external displays are on, I am able to log in without a problem no matter which display is primary. Perhaps this could be a temporary workaround until others provide more insight or a fix is found.
At the time I wrote the post, it was not enough: I had to unplug my dock,open the session, then plug the dock again.
Then after some updates, i had to have the laptop lid open, like you.
Since yesterday, it seems to be fixed (I had several gnome-shell and gdm updates since I wrote this post.
I wait a little bit to see if it persist to work, then I'll mark it as (self-)resolved.
Offline
At the time I wrote the post, it was not enough: I had to unplug my dock,open the session, then plug the dock again.
Then after some updates, i had to have the laptop lid open, like you.
Since yesterday, it seems to be fixed (I had several gnome-shell and gdm updates since I wrote this post.
I wait a little bit to see if it persist to work, then I'll mark it as (self-)resolved.
Just confirming that upgrading my system this morning resolved the issue for me as well. I can now log in with my laptop docked and the lid closed without any apparent segfaults.
Offline
It still works on my side after several upgrades.
I'll mark it as resolved.
Offline