You are not logged in.
- Topics: Active | Unanswered
- Index
- » Applications & Desktop Environments
- » GDM crashes at system boot, but starts after gdm.service reboot
Pages: 1
Topic closed
#1 2018-07-06 10:11:36
- SIDS
- Member
- Registered: 2017-04-12
- Posts: 8
GDM crashes at system boot, but starts after gdm.service reboot
I've come across a strange behavior with starting gdm.service at system startup.
After my computer's been rebooted, the gdm.service crashed with a coredump of 'gnome-shell'.
This is journalctl output:
Jul 06 10:43:04 systemd[1]: Starting GNOME Display Manager...
Jul 06 10:43:04 systemd[1]: Started Login Service.
Jul 06 10:43:04 dbus-daemon[409]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jul 06 10:43:04 systemd[1]: Started GNOME Display Manager.
Jul 06 10:43:04 dbus-daemon[409]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.5' (uid=0 pid=430 comm="/usr/bin/gdm ")
Jul 06 10:43:04 systemd[1]: Reached target User and Group Name Lookups.
Jul 06 10:43:04 systemd[1]: Starting Accounts Service...
Jul 06 10:43:06 dbus-daemon[409]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.1' (uid=0 pid=411 comm="/usr/bin/NetworkManager --no-daemon ")
Jul 06 10:43:06 systemd[1]: Starting Authorization Manager...
Jul 06 10:43:08 dbus-daemon[409]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jul 06 10:43:08 systemd[1]: Started Authorization Manager.
Jul 06 10:43:09 accounts-daemon[438]: started daemon version 0.6.49
Jul 06 10:43:09 dbus-daemon[409]: [system] Successfully activated service 'org.freedesktop.Accounts'
Jul 06 10:43:09 systemd[1]: Started Accounts Service.
Jul 06 10:43:09 systemd[1]: Reached target Multi-User System.
Jul 06 10:43:09 systemd[1]: Reached target Graphical Interface.
Jul 06 10:43:09 systemd[1]: Startup finished in 3.894s (kernel) + 15.873s (userspace) = 19.768s.
Jul 06 10:43:09 dbus-daemon[409]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Jul 06 10:43:10 systemd[1]: Created slice User Slice of UID 120.
Jul 06 10:43:10 systemd[1]: Created slice system-user\x2druntime\x2ddir.slice.
Jul 06 10:43:10 systemd[1]: Started /run/user/120 mount wrapper.
Jul 06 10:43:10 systemd[1]: Starting User Manager for UID 120...
Jul 06 10:43:10 systemd-logind[410]: New session c1 of user gdm.
Jul 06 10:43:10 systemd[1]: Started Session c1 of user gdm.
Jul 06 10:43:10 systemd[476]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
Jul 06 10:43:10 systemd[476]: Listening on Sound System.
Jul 06 10:43:10 systemd[476]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jul 06 10:43:10 systemd[476]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 06 10:43:10 systemd[476]: Listening on GnuPG cryptographic agent and passphrase cache.
Jul 06 10:43:10 systemd[476]: Reached target Timers.
Jul 06 10:43:10 systemd[476]: Starting D-Bus User Message Bus Socket.
Jul 06 10:43:10 systemd[476]: Reached target Paths.
Jul 06 10:43:10 systemd[476]: Listening on Multimedia System.
Jul 06 10:43:10 systemd[476]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jul 06 10:43:10 systemd[476]: Listening on GnuPG network certificate management daemon.
Jul 06 10:43:10 systemd[476]: Listening on D-Bus User Message Bus Socket.
Jul 06 10:43:10 systemd[476]: Reached target Sockets.
Jul 06 10:43:10 systemd[476]: Reached target Basic System.
Jul 06 10:43:10 systemd[1]: Started User Manager for UID 120.
Jul 06 10:43:10 systemd[476]: Starting Update XDG user dir configuration...
Jul 06 10:43:10 systemd[476]: Started Update XDG user dir configuration.
Jul 06 10:43:10 systemd[476]: Reached target Default.
Jul 06 10:43:10 systemd[476]: Startup finished in 267ms.
Jul 06 10:43:10 systemd[476]: Started D-Bus User Message Bus.
Jul 06 10:43:14 dbus-daemon[409]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.42' (uid=120 pid=496 comm="/usr/bin/gnome-shell ")
Jul 06 10:43:14 systemd[1]: Starting Daemon for power management...
Jul 06 10:43:14 dbus-daemon[409]: [system] Successfully activated service 'org.freedesktop.UPower'
Jul 06 10:43:14 systemd[1]: Started Daemon for power management.
Jul 06 10:43:14 kernel: gnome-shell[496]: segfault at 20 ip 00007f02361eb7b5 sp 00007ffc06658880 error 4 in libmutter-2.so.0.0.0[7f02360e5000+183000]
Jul 06 10:43:14 systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Jul 06 10:43:14 systemd[1]: Started Process Core Dump (PID 542/UID 0).
Jul 06 10:43:15 gnome-session[487]: gnome-session-binary[487]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Jul 06 10:43:15 gnome-session-binary[487]: Unrecoverable failure in required component org.gnome.Shell.desktop
Jul 06 10:43:15 gnome-session-binary[487]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Jul 06 10:43:15 systemd-logind[410]: Session c1 logged out. Waiting for processes to exit.
Jul 06 10:43:15 systemd-logind[410]: Removed session c1.
Jul 06 10:43:15 gdm[430]: Child process -483 was already dead.
Jul 06 10:43:15 gdm[430]: Child process 469 was already dead.
Jul 06 10:43:15 gdm[430]: Unable to kill session worker process
Jul 06 10:43:15 systemd[1]: user-runtime-dir@120.service: Unit not needed anymore. Stopping.
Jul 06 10:43:15 systemd[1]: Stopping User Manager for UID 120...
Jul 06 10:43:15 systemd[476]: Stopping D-Bus User Message Bus...
Jul 06 10:43:15 systemd[476]: Stopped target Default.
Jul 06 10:43:15 systemd-logind[410]: New session c2 of user gdm.
Jul 06 10:43:15 systemd[1]: Started Session c2 of user gdm.
Jul 06 10:43:15 gdm-launch-environment][546]: pam_systemd(gdm-launch-environment:session): Failed to create session: Start job for unit user-120.slice failed with 'canceled'
Jul 06 10:43:15 systemd[476]: Stopped D-Bus User Message Bus.
Jul 06 10:43:15 systemd[476]: Stopped target Basic System.
Jul 06 10:43:15 systemd[476]: Stopped target Timers.
Jul 06 10:43:15 systemd[476]: Stopped target Paths.
Jul 06 10:43:15 systemd[476]: Stopped target Sockets.
Jul 06 10:43:15 systemd[476]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Jul 06 10:43:15 systemd[476]: Closed Multimedia System.
Jul 06 10:43:15 systemd[476]: Closed GnuPG network certificate management daemon.
Jul 06 10:43:15 systemd[476]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 06 10:43:15 systemd[476]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Jul 06 10:43:15 systemd[476]: Closed Sound System.
Jul 06 10:43:15 systemd[476]: Closed GnuPG cryptographic agent and passphrase cache.
Jul 06 10:43:15 systemd[476]: Closed D-Bus User Message Bus Socket.
Jul 06 10:43:15 systemd[476]: Reached target Shutdown.
Jul 06 10:43:15 systemd[476]: Starting Exit the Session...
Jul 06 10:43:15 systemd[477]: pam_unix(systemd-user:session): session closed for user gdm
Jul 06 10:43:15 systemd[1]: Starting User Manager for UID 120...
Jul 06 10:43:15 systemd[550]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Listening on GnuPG cryptographic agent and passphrase cache.
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Listening on GnuPG network certificate management daemon.
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Reached target Paths.
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Listening on Sound System.
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 06 10:43:15 systemd[550]: Failed to connect to API bus: Connection refused
Jul 06 10:43:15 systemd[550]: Starting D-Bus User Message Bus Socket.
Jul 06 10:43:15 systemd[550]: Reached target Timers.
Jul 06 10:43:15 systemd[550]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jul 06 10:43:15 systemd[550]: Listening on Multimedia System.
Jul 06 10:43:15 systemd[550]: Listening on D-Bus User Message Bus Socket.
Jul 06 10:43:15 systemd[550]: Reached target Sockets.
Jul 06 10:43:15 systemd[550]: Reached target Basic System.
Jul 06 10:43:15 systemd[1]: Started User Manager for UID 120.
Jul 06 10:43:15 systemd[550]: Starting Update XDG user dir configuration...
Jul 06 10:43:15 systemd[550]: Started D-Bus User Message Bus.
Jul 06 10:43:15 systemd[550]: Started Update XDG user dir configuration.
Jul 06 10:43:15 systemd[550]: Reached target Default.
Jul 06 10:43:15 systemd[550]: Startup finished in 32ms.
Jul 06 10:43:15 systemd-logind[410]: Session c2 logged out. Waiting for processes to exit.
Jul 06 10:43:15 systemd-logind[410]: Removed session c2.
Jul 06 10:43:15 systemd[1]: user-runtime-dir@120.service: Unit not needed anymore. Stopping.
Jul 06 10:43:15 systemd[551]: pam_unix(systemd-user:session): session closed for user gdm
Jul 06 10:43:15 systemd[1]: Stopping User Manager for UID 120...
Jul 06 10:43:15 systemd[550]: Stopped target Default.
Jul 06 10:43:15 systemd[550]: Stopping D-Bus User Message Bus...
Jul 06 10:43:15 systemd[550]: Stopped D-Bus User Message Bus.
Jul 06 10:43:15 systemd[550]: Stopped target Basic System.
Jul 06 10:43:15 systemd[550]: Stopped target Sockets.
Jul 06 10:43:15 systemd[550]: Closed Multimedia System.
Jul 06 10:43:15 systemd[550]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Jul 06 10:43:15 systemd[550]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 06 10:43:15 systemd[550]: Closed GnuPG cryptographic agent and passphrase cache.
Jul 06 10:43:15 systemd[550]: Closed GnuPG network certificate management daemon.
Jul 06 10:43:15 systemd[550]: Closed Sound System.
Jul 06 10:43:15 systemd[550]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Jul 06 10:43:15 systemd[550]: Stopped target Paths.
Jul 06 10:43:15 systemd[550]: Stopped target Timers.
Jul 06 10:43:15 systemd[550]: Closed D-Bus User Message Bus Socket.
Jul 06 10:43:15 systemd[550]: Reached target Shutdown.
Jul 06 10:43:15 systemd[550]: Starting Exit the Session...
Jul 06 10:43:15 systemd[1]: user-runtime-dir@120.service: Unit not needed anymore. Stopping.
Jul 06 10:43:15 systemd[1]: Stopped User Manager for UID 120.
Jul 06 10:43:15 systemd[1]: user-runtime-dir@120.service: Unit not needed anymore. Stopping.
Jul 06 10:43:15 systemd[1]: Removed slice User Slice of UID 120.
Jul 06 10:43:15 systemd[1]: Stopping /run/user/120 mount wrapper...
Jul 06 10:43:15 systemd[1]: Stopped /run/user/120 mount wrapper.
Jul 06 10:43:16 systemd-coredump[543]: Process 496 (gnome-shell) of user 120 dumped core.
Stack trace of thread 496:
#0 0x00007f02361eb7b5 meta_gpu_kms_new (libmutter-2.so.0)
#1 0x00007f02361ed0dc n/a (libmutter-2.so.0)
#2 0x00007f023820c121 g_initable_new_valist (libgio-2.0.so.0)
#3 0x00007f023820c1da g_initable_new (libgio-2.0.so.0)
#4 0x00007f023613d62a n/a (libmutter-2.so.0)
#5 0x00007f023613e288 meta_init_backend (libmutter-2.so.0)
#6 0x00007f0236187bf8 meta_init (libmutter-2.so.0)
#7 0x000055d14c867cca n/a (gnome-shell)
#8 0x00007f02389b506b __libc_start_main (libc.so.6)
#9 0x000055d14c86813a n/a (gnome-shell)
Stack trace of thread 505:
#0 0x00007f0238a850f9 syscall (libc.so.6)
#1 0x00007f0237cd452d g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007f0237c5f903 n/a (libglib-2.0.so.0)
#3 0x00007f0237cb6436 n/a (libglib-2.0.so.0)
#4 0x00007f0237cb5a2a n/a (libglib-2.0.so.0)
#5 0x00007f0238d55075 start_thread (libpthread.so.0)
#6 0x00007f0238a8a53f __clone (libc.so.6)
Stack trace of thread 499:
#0 0x00007f0238a7fea9 __poll (libc.so.6)
#1 0x00007f0237c8d523 n/a (libglib-2.0.so.0)
#2 0x00007f0237c8d63e g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f0237c8d692 n/a (libglib-2.0.so.0)
#4 0x00007f0237cb5a2a n/a (libglib-2.0.so.0)
#5 0x00007f0238d55075 start_thread (libpthread.so.0)
#6 0x00007f0238a8a53f __clone (libc.so.6)
Stack trace of thread 501:
#0 0x00007f0238a7fea9 __poll (libc.so.6)
#1 0x00007f0237c8d523 n/a (libglib-2.0.so.0)
#2 0x00007f0237c8d63e g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f0220746f4e n/a (libdconfsettings.so)
#4 0x00007f0237cb5a2a n/a (libglib-2.0.so.0)
#5 0x00007f0238d55075 start_thread (libpthread.so.0)
#6 0x00007f0238a8a53f __clone (libc.so.6)
Stack trace of thread 500:
#0 0x00007f0238a7fea9 __poll (libc.so.6)
#1 0x00007f0237c8d523 n/a (libglib-2.0.so.0)
#2 0x00007f0237c8d8e2 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f023827c348 n/a (libgio-2.0.so.0)
#4 0x00007f0237cb5a2a n/a (libglib-2.0.so.0)
#5 0x00007f0238d55075 start_thread (libpthread.so.0)
#6 0x00007f0238a8a53f __clone (libc.so.6)I switched to tty2, logined as a root and restarted the gdm service.
The 'gnome-shell' crashed again, but a gdm-x-session was started successfully.
This is the journalctl output after gdm.service restarted:
Jul 06 11:15:30 systemd[1]: Stopping GNOME Display Manager...
Jul 06 11:15:30 systemd[1]: Stopped GNOME Display Manager.
Jul 06 11:15:30 gdm[430]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Jul 06 11:15:30 systemd[1]: Starting GNOME Display Manager...
Jul 06 11:15:30 gdm[430]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
Jul 06 11:15:30 systemd[1]: Started GNOME Display Manager.
Jul 06 11:15:30 systemd[1]: Created slice User Slice of UID 120.
Jul 06 11:15:30 systemd[1]: Started /run/user/120 mount wrapper.
Jul 06 11:15:30 systemd[1]: Starting User Manager for UID 120...
Jul 06 11:15:30 systemd-logind[410]: New session c6 of user gdm.
Jul 06 11:15:30 systemd[1]: Started Session c6 of user gdm.
Jul 06 11:15:30 systemd[663]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
Jul 06 11:15:30 systemd[663]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 06 11:15:30 systemd[663]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jul 06 11:15:30 systemd[663]: Listening on Sound System.
Jul 06 11:15:30 systemd[663]: Reached target Timers.
Jul 06 11:15:30 systemd[663]: Listening on GnuPG network certificate management daemon.
Jul 06 11:15:30 systemd[663]: Listening on Multimedia System.
Jul 06 11:15:30 systemd[663]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jul 06 11:15:30 systemd[663]: Listening on GnuPG cryptographic agent and passphrase cache.
Jul 06 11:15:30 systemd[663]: Reached target Paths.
Jul 06 11:15:30 systemd[663]: Starting D-Bus User Message Bus Socket.
Jul 06 11:15:30 systemd[663]: Listening on D-Bus User Message Bus Socket.
Jul 06 11:15:30 systemd[663]: Reached target Sockets.
Jul 06 11:15:30 systemd[663]: Reached target Basic System.
Jul 06 11:15:30 systemd[1]: Started User Manager for UID 120.
Jul 06 11:15:30 systemd[663]: Starting Update XDG user dir configuration...
Jul 06 11:15:30 systemd[663]: Started Update XDG user dir configuration.
Jul 06 11:15:30 systemd[663]: Reached target Default.
Jul 06 11:15:30 systemd[663]: Startup finished in 35ms.
Jul 06 11:15:30 systemd[663]: Started D-Bus User Message Bus.
Jul 06 11:15:31 kernel: gnome-shell[682]: segfault at 20 ip 00007fe25f7187b5 sp 00007ffe6f740e00 error 4 in libmutter-2.so.0.0.0[7fe25f612000+183000]
Jul 06 11:15:31 systemd[1]: Started Process Core Dump (PID 691/UID 0).
Jul 06 11:15:31 gnome-session[675]: gnome-session-binary[675]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Jul 06 11:15:31 gnome-session-binary[675]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Jul 06 11:15:31 gnome-session-binary[675]: Unrecoverable failure in required component org.gnome.Shell.desktop
Jul 06 11:15:31 gdm[654]: GdmDisplay: display lasted 1,087925 seconds
Jul 06 11:15:31 systemd-logind[410]: Session c6 logged out. Waiting for processes to exit.
Jul 06 11:15:31 gdm[654]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Jul 06 11:15:31 systemd-logind[410]: Removed session c6.
Jul 06 11:15:32 systemd[664]: pam_unix(systemd-user:session): session closed for user gdm
Jul 06 11:15:31 systemd[1]: user-runtime-dir@120.service: Unit not needed anymore. Stopping.
Jul 06 11:15:31 systemd[1]: Stopping User Manager for UID 120...
Jul 06 11:15:31 systemd[663]: Stopped target Default.
Jul 06 11:15:32 gdm[654]: Child process -671 was already dead.
Jul 06 11:15:31 systemd[663]: Stopping D-Bus User Message Bus...
Jul 06 11:15:32 gdm[654]: Child process 657 was already dead.
Jul 06 11:15:31 systemd[663]: Stopped D-Bus User Message Bus.
Jul 06 11:15:32 gdm[654]: Unable to kill session worker process
Jul 06 11:15:31 systemd[663]: Stopped target Basic System.
Jul 06 11:15:31 systemd[663]: Stopped target Paths.
Jul 06 11:15:31 systemd[663]: Stopped target Timers.
Jul 06 11:15:31 systemd[663]: Stopped target Sockets.
Jul 06 11:15:31 systemd[663]: Closed Sound System.
Jul 06 11:15:31 systemd[663]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Jul 06 11:15:31 systemd[663]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 06 11:15:31 systemd[663]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Jul 06 11:15:31 systemd[663]: Closed GnuPG cryptographic agent and passphrase cache.
Jul 06 11:15:31 systemd[663]: Closed Multimedia System.
Jul 06 11:15:31 systemd[663]: Closed GnuPG network certificate management daemon.
Jul 06 11:15:31 systemd[663]: Closed D-Bus User Message Bus Socket.
Jul 06 11:15:31 systemd[663]: Reached target Shutdown.
Jul 06 11:15:32 systemd[663]: Starting Exit the Session...
Jul 06 11:15:32 systemd[1]: user-runtime-dir@120.service: Unit not needed anymore. Stopping.
Jul 06 11:15:32 systemd[1]: Stopped User Manager for UID 120.
Jul 06 11:15:32 systemd[1]: user-runtime-dir@120.service: Unit not needed anymore. Stopping.
Jul 06 11:15:32 systemd[1]: Removed slice User Slice of UID 120.
Jul 06 11:15:32 systemd[1]: Stopping /run/user/120 mount wrapper...
Jul 06 11:15:32 systemd[1]: Stopped /run/user/120 mount wrapper.
Jul 06 11:15:32 systemd[1]: Created slice User Slice of UID 120.
Jul 06 11:15:32 systemd[1]: Started /run/user/120 mount wrapper.
Jul 06 11:15:32 systemd[1]: Starting User Manager for UID 120...
Jul 06 11:15:32 systemd-logind[410]: New session c7 of user gdm.
Jul 06 11:15:32 systemd[1]: Started Session c7 of user gdm.
Jul 06 11:15:32 systemd[703]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
Jul 06 11:15:32 systemd[703]: Listening on GnuPG cryptographic agent and passphrase cache.
Jul 06 11:15:32 systemd[703]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jul 06 11:15:32 systemd[703]: Listening on Multimedia System.
Jul 06 11:15:32 systemd[703]: Listening on GnuPG network certificate management daemon.
Jul 06 11:15:32 systemd[703]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jul 06 11:15:32 systemd[703]: Reached target Timers.
Jul 06 11:15:32 systemd[703]: Reached target Paths.
Jul 06 11:15:32 systemd[703]: Starting D-Bus User Message Bus Socket.
Jul 06 11:15:32 systemd[703]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jul 06 11:15:32 systemd[703]: Listening on Sound System.
Jul 06 11:15:32 systemd[703]: Listening on D-Bus User Message Bus Socket.
Jul 06 11:15:32 systemd[703]: Reached target Sockets.
Jul 06 11:15:32 systemd[703]: Reached target Basic System.
Jul 06 11:15:32 systemd[1]: Started User Manager for UID 120.
Jul 06 11:15:32 systemd[703]: Starting Update XDG user dir configuration...
Jul 06 11:15:32 systemd[703]: Started Update XDG user dir configuration.
Jul 06 11:15:32 systemd[703]: Reached target Default.
Jul 06 11:15:32 systemd[703]: Startup finished in 33ms.
Jul 06 11:15:32 systemd-coredump[692]: Process 682 (gnome-shell) of user 120 dumped core.
Stack trace of thread 682:
#0 0x00007fe25f7187b5 meta_gpu_kms_new (libmutter-2.so.0)
#1 0x00007fe25f71a0dc n/a (libmutter-2.so.0)
#2 0x00007fe261739121 g_initable_new_valist (libgio-2.0.so.0)
#3 0x00007fe2617391da g_initable_new (libgio-2.0.so.0)
#4 0x00007fe25f66a62a n/a (libmutter-2.so.0)
#5 0x00007fe25f66b288 meta_init_backend (libmutter-2.so.0)
#6 0x00007fe25f6b4bf8 meta_init (libmutter-2.so.0)
#7 0x00005616a67c0cca n/a (gnome-shell)
#8 0x00007fe261ee206b __libc_start_main (libc.so.6)
#9 0x00005616a67c113a n/a (gnome-shell)
Stack trace of thread 686:
#0 0x00007fe261facea9 __poll (libc.so.6)
#1 0x00007fe2611ba523 n/a (libglib-2.0.so.0)
#2 0x00007fe2611ba8e2 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007fe2617a9348 n/a (libgio-2.0.so.0)
#4 0x00007fe2611e2a2a n/a (libglib-2.0.so.0)
#5 0x00007fe262282075 start_thread (libpthread.so.0)
#6 0x00007fe261fb753f __clone (libc.so.6)
Stack trace of thread 685:
#0 0x00007fe261facea9 __poll (libc.so.6)
#1 0x00007fe2611ba523 n/a (libglib-2.0.so.0)
#2 0x00007fe2611ba63e g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007fe2611ba692 n/a (libglib-2.0.so.0)
#4 0x00007fe2611e2a2a n/a (libglib-2.0.so.0)
#5 0x00007fe262282075 start_thread (libpthread.so.0)
#6 0x00007fe261fb753f __clone (libc.so.6)
Stack trace of thread 687:
#0 0x00007fe261facea9 __poll (libc.so.6)
#1 0x00007fe2611ba523 n/a (libglib-2.0.so.0)
#2 0x00007fe2611ba63e g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007fe249c73f4e n/a (libdconfsettings.so)
#4 0x00007fe2611e2a2a n/a (libglib-2.0.so.0)
#5 0x00007fe262282075 start_thread (libpthread.so.0)
#6 0x00007fe261fb753f __clone (libc.so.6)
Stack trace of thread 690:
#0 0x00007fe261fb20f9 syscall (libc.so.6)
#1 0x00007fe26120152d g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007fe26118c903 n/a (libglib-2.0.so.0)
#3 0x00007fe2611e3436 n/a (libglib-2.0.so.0)
#4 0x00007fe2611e2a2a n/a (libglib-2.0.so.0)
#5 0x00007fe262282075 start_thread (libpthread.so.0)
#6 0x00007fe261fb753f __clone (libc.so.6)
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (--) Log file renamed from "/var/log/Xorg.pid-712.log" to "/var/log/Xorg.0.log"
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (WW) Failed to open protocol names file lib/xorg/protocol.txt
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: X.Org X Server 1.20.0
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: X Protocol Version 11, Revision 0
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: Build Operating System: Linux Arch Linux
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: Current Operating System: Linux sids_home 4.17.3-1-ARCH #1 SMP PREEMPT Tue Jun 26 04:42:36 UTC 2018 x86_64
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=f08491bf-3a4a-4e25-8fe8-f5eb651cbeba rw quiet
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: Build Date: 18 June 2018 03:12:37PM
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]:
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: Current version of pixman: 0.34.0
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: Before reporting problems, check http://wiki.x.org
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: to make sure that you have the latest version.
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: Markers: (--) probed, (**) from config file, (==) default setting,
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (++) from command line, (!!) notice, (II) informational,
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul 6 11:15:32 2018
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (==) No Layout section. Using the first Screen section.
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (==) No screen section available. Using defaults.
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (**) |-->Screen "Default Screen Section" (0)
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (**) | |-->Monitor "<default monitor>"
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (==) No monitor specified for screen "Default Screen Section".
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: Using a default monitor configuration.
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (==) Automatically adding devices
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (==) Automatically enabling devices
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (==) Automatically adding GPU devices
Jul 06 11:15:32 /usr/lib/gdm-x-session[710]: (==) Automatically binding GPU devicesAnd GDM interface appeared.
So, i'm a bit confused. Do you have any thought about the issue?
Offline
#2 2018-07-06 11:35:48
- MasterMax
- Member
- Registered: 2011-11-11
- Posts: 21
Re: GDM crashes at system boot, but starts after gdm.service reboot
I have the same issue since today with identical log messages.
Offline
#3 2018-07-06 13:12:27
- Inglebard
- Member
- Registered: 2016-05-10
- Posts: 33
Re: GDM crashes at system boot, but starts after gdm.service reboot
Hi,
I notice a quite similar behavior.
GDM crash at boot but i am not able to switch tty.
Downgrade libsystemd and systemd "fix" the issue.
[2018-07-06 17:05] [ALPM] downgraded libsystemd (239.0-2 -> 238.133-4)
[2018-07-06 17:05] [ALPM] downgraded systemd (239.0-2 -> 238.133-4)Offline
#4 2018-07-06 13:55:28
- SIDS
- Member
- Registered: 2017-04-12
- Posts: 8
Re: GDM crashes at system boot, but starts after gdm.service reboot
Inglebard wrote:
Hi,
I notice a quite similar behavior.GDM crash at boot but i am not able to switch tty.
Downgrade libsystemd and systemd "fix" the issue.
[2018-07-06 17:05] [ALPM] downgraded libsystemd (239.0-2 -> 238.133-4) [2018-07-06 17:05] [ALPM] downgraded systemd (239.0-2 -> 238.133-4)
Downgrading helped, but in my journalctl there is still a coredump.
It's seems to me, there is no relation between the bug with systemd and the gnome-shell coredumped
Offline
#5 2018-07-06 14:30:12
- zrb77
- Member
- From: Maryland, USA
- Registered: 2018-07-06
- Posts: 4
Re: GDM crashes at system boot, but starts after gdm.service reboot
I seem to be having a similar issue today on my desktop, but had to leave for work before I could do any real troubleshooting, I'll have to look into this when I get home. Thanks.
Offline
#6 2018-07-06 17:24:50
- numasan
- Member
- Registered: 2009-11-13
- Posts: 26
Re: GDM crashes at system boot, but starts after gdm.service reboot
SIDS wrote:
Inglebard wrote:Hi,
I notice a quite similar behavior.GDM crash at boot but i am not able to switch tty.
Downgrade libsystemd and systemd "fix" the issue.
[2018-07-06 17:05] [ALPM] downgraded libsystemd (239.0-2 -> 238.133-4) [2018-07-06 17:05] [ALPM] downgraded systemd (239.0-2 -> 238.133-4)Downgrading helped, but in my journalctl there is still a coredump.
It's seems to me, there is no relation between the bug with systemd and the gnome-shell coredumped
Same here, couldn't switch tty so had to ssh in and downgrade systemd.
The coredump is also still present - issue with 'libmutter-2.so.0' ?
Offline
#7 2018-07-06 17:30:10
- SIDS
- Member
- Registered: 2017-04-12
- Posts: 8
Re: GDM crashes at system boot, but starts after gdm.service reboot
numasan wrote:
Same here, couldn't switch tty so had to ssh in and downgrade systemd.
The coredump is also still present - issue with 'libmutter-2.so.0' ?
Yes, the stacktrace ends with
Stack trace of thread 496:
#0 0x00007f02361eb7b5 meta_gpu_kms_new (libmutter-2.so.0)
#1 0x00007f02361ed0dc n/a (libmutter-2.so.0)Offline
#8 2018-07-06 23:14:36
- Austin17
- Member
- Registered: 2014-11-01
- Posts: 3
Re: GDM crashes at system boot, but starts after gdm.service reboot
Reporting in with the same problem. Seeing the same core dump messages in my logs with gdm never starting. Downgrading systemd back down fixed the problem for now, but I can't seem to figure out what might be going on.
Offline
#9 2018-07-06 23:17:43
- doublez13
- Member
- Registered: 2017-07-29
- Posts: 2
Re: GDM crashes at system boot, but starts after gdm.service reboot
Same issue with me on a fresh install.
The issue only seems to occur with the nvidia or nvidia-dkms packages installed.
Uninstalling these 'resolves' the problem for now.
Reinstalled the nvidia package and just switched to lightdm until the issue with gdm is fixed.
Last edited by doublez13 (2018-07-06 23:19:17)
Offline
#10 2018-07-07 04:51:48
- threeofsix
- Member
- Registered: 2013-08-01
- Posts: 9
Re: GDM crashes at system boot, but starts after gdm.service reboot
Same issue here. Booting with the LTS kernel works around it for me.
Does anyone know if this is reported somewhere?
Offline
#11 2018-07-07 10:14:40
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 23,447
Re: GDM crashes at system boot, but starts after gdm.service reboot
From a glance this reads like a simple race condition, does enabling early KMS help?
Offline
#12 2018-07-07 15:05:49
- MasterMax
- Member
- Registered: 2011-11-11
- Posts: 21
Re: GDM crashes at system boot, but starts after gdm.service reboot
V1del wrote:
From a glance this reads like a simple race condition, does enabling early KMS help?
Thanks for this advice. I just tried that, doesn't solve the problem.
Offline
#13 2018-07-07 22:00:46
- threeofsix
- Member
- Registered: 2013-08-01
- Posts: 9
Re: GDM crashes at system boot, but starts after gdm.service reboot
The recent update to linux 4.17.4-1 and nvidia-dkms 396.24-14 seems to have helped. I can load gdm and log into gnome, but I still see the same core dump messages in the journal.
EDIT: Scratch that. Seems like it doesn't happen at every boot, just usually. Booting with the LTS kernel doesn't solve it either, I just happened to get away with it a couple times earlier.
Last edited by threeofsix (2018-07-08 04:26:01)
Offline
#14 2018-07-08 04:57:04
- litlpoet
- Member
- Registered: 2016-01-26
- Posts: 1
Re: GDM crashes at system boot, but starts after gdm.service reboot
doublez13 wrote:
Reinstalled the nvidia package and just switched to lightdm until the issue with gdm is fixed.
I got the same issue, and could only work around the issue by reinstalling nvidia as well as switching to lightdm from gdm.
Offline
#15 2018-07-08 05:01:18
- ExoDroiD
- Member
- Registered: 2018-01-01
- Posts: 23
Re: GDM crashes at system boot, but starts after gdm.service reboot
I have the same problem but not able to switch TTY. Anybody have a clue on why is that?
Offline
#16 2018-07-08 05:52:34
- tick1020
- Member
- Registered: 2017-04-22
- Posts: 26
Re: GDM crashes at system boot, but starts after gdm.service reboot
Alright so I'm having the same issue, I'm also unable to switch tty. I don't have ssh setup on this machine, I also don't have a disk drive in it anymore, and my laptop is down (for other reasons) so I don't have a machine to create an arch installer with... haha... Any ideas?
I'm about to dig through some older flash drives and hope one has a bootable distro (hopefully arch) on it...
Man, it's been a while since I've had to use installation media to restore my system... I've had the same install on this system for 4 years now since I built this computer...
Offline
#17 2018-07-08 05:55:32
- ExoDroiD
- Member
- Registered: 2018-01-01
- Posts: 23
Re: GDM crashes at system boot, but starts after gdm.service reboot
tick1020 wrote:
Alright so I'm having the same issue, I'm also unable to switch tty. I don't have ssh setup on this machine, I also don't have a disk drive in it anymore, and my laptop is down (for other reasons) so I don't have a machine to create an arch installer with... haha... Any ideas?
I'm about to dig through some older flash drives and hope one has a bootable distro (hopefully arch) on it...
Man, it's been a while since I've had to use installation media to restore my system... I've had the same install on this system for 4 years now since I built this computer...
You should be able to get into a "terminal mode" by adding a kernel parameter at boot, I don't currently remember which one.
Offline
#18 2018-07-08 08:14:17
- Freddie Chopin
- Member
- From: Zawiercie, Poland
- Registered: 2015-08-13
- Posts: 9
- Website
Re: GDM crashes at system boot, but starts after gdm.service reboot
Here's a hint which may help. Edit /etc/gdm/custom.conf and _UNCOMMENT_ the line with "WaylandEnable=false", thus disabling Wayland (which does not work with nvidia drivers anyway). For me this solved the issue of gnome-shell crashing at startup. I yet have to check whether it will still work with most recent systemd/libsystemd - yesterday I had to downgrade to "fix" the problem, so at this very moment I'm using version 238. However my brother (who has almost identical PC with almost identical system) reports no problem when "WaylandEnable=false" line in mentioned file is uncommented.
I've reported this bug yesterday too -> https://bugs.archlinux.org/task/59262 (;
Offline
#19 2018-07-08 09:17:27
- AlonsoLP
- Member
- From: Málaga - Spain
- Registered: 2017-02-14
- Posts: 1
Re: GDM crashes at system boot, but starts after gdm.service reboot
Thanks Freddie! Uncommenting "WaylandEnable=false" works fine for me, and I have installed systemd/libsystemd 239.
... under Linux control since 1995.
Offline
#20 2018-07-08 13:38:03
- zrb77
- Member
- From: Maryland, USA
- Registered: 2018-07-06
- Posts: 4
Re: GDM crashes at system boot, but starts after gdm.service reboot
AlonsoLP wrote:
Thanks Freddie! Uncommenting "WaylandEnable=false" works fine for me, and I have installed systemd/libsystemd 239.
This worked for me too.
Thanks Freddie.
Offline
#21 2018-07-09 17:21:01
- fabrixx
- Member
- From: Italy
- Registered: 2015-06-07
- Posts: 117
Re: GDM crashes at system boot, but starts after gdm.service reboot
Same issue for me. Solved with downgrade of system & libsystemd and uncommenting that line. Thankyou
Offline
#22 2018-07-09 18:24:36
- davidovitch
- Member
- From: Copenhagen
- Registered: 2011-02-02
- Posts: 46
- Website
Re: GDM crashes at system boot, but starts after gdm.service reboot
tick1020 wrote:
Alright so I'm having the same issue, I'm also unable to switch tty. I don't have ssh setup on this machine, I also don't have a disk drive in it anymore, and my laptop is down (for other reasons) so I don't have a machine to create an arch installer with... haha... Any ideas?
I'm about to dig through some older flash drives and hope one has a bootable distro (hopefully arch) on it...
Man, it's been a while since I've had to use installation media to restore my system... I've had the same install on this system for 4 years now since I built this computer...
In case you are using GRUB, make sure GRUB_DISABLE_RECOVERY is set to false in /etc/default/grub to create a recovery mode option in your boot menu. See also the GRUB#Additional_arguments at the wiki.
Offline
#23 2018-07-09 18:33:26
- numasan
- Member
- Registered: 2009-11-13
- Posts: 26
Re: GDM crashes at system boot, but starts after gdm.service reboot
Thanks for finding the issue Freddie!
Offline
#24 2018-07-09 23:59:51
- retalak
- Member
- Registered: 2018-05-19
- Posts: 10
Re: GDM crashes at system boot, but starts after gdm.service reboot
I just had this issue after updating and fixed it with WaylandEnable=false. Thanks Freddie.
Last edited by retalak (2018-07-10 00:00:18)
Offline
#25 2018-07-10 00:48:32
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,424
- Website
Re: GDM crashes at system boot, but starts after gdm.service reboot
Please read the Code and stop bumping this thread with empty posts: https://wiki.archlinux.org/index.php/Co … mpty_posts
Closing
Offline
Pages: 1
Topic closed