I updated just a few hours ago, so I’m presumably on the latest update. Afterward, I restarted the computer and now I can’t log on. My login screen changed quite a bit, which I think might be related to the update, but is functionally the same, other than the simple fact that it doesn’t work. I can click on my account name and enter a password, but upon successful completion (I’m 100% certain the password is correct), the screen goes blank, at first the same color as the login screen, then entirely black, and then I’m back to the account selection page. No indication of “incorrect password” or any sort of error message, just the account selection screen. I’ve tried literally dozens of times. I only have the one account and I even tried switching back and forth between Gnome on Wayland and Gnome on Xorg on the settings dial in the bottom-right, and both give the same result.
have you installed any gnome extension?
If you open a TTY (e.g CTRL-ALT-F3) can you log in there?
If so try to add a new user and reboot. sudo useradd <username>; sudo passwd <username>; sudo reboot - can you log into Gnome with that new user?
Yes, dash-to-panel, which was working fine before the update. The update also removed a bunch of previously pre-installed gnome extensions IIRC (I haven’t updated in a month or so, which is bad practice, I know).
Yes, I can log in via terminal. That’s just what I was looking for!
Added a new user, rebooted, and the new user cannot login to gnome either.
Doing some more digging, and as per @doct0rHu 's comment, I believe it does have something to do with gnome. Just tried, and I can log in with Weston (whatever that is). I’m not familiar with how it works, but I can launch a terminal. So progress, I guess.
Since I now have access to root shell, I can do some remote debugging or even just a reset of some sort. What do you guys recommend?
try ssh from another machine if you can and run
journalctl -f
attempt local gui login and paste the output from your ssh shell to here.
1 Like
Can’t I just use the ctrl-alt-f3 terminal, or is there a specific reason to ssh?
so that you can follow the journal (from the shell) and attempt the login at the same time.
1 Like
I asked about gnome extension because sometimes an incompatible extension would crash gnome. If you haven’t installed any extensions by yourself, it should be okay.
Log from one login attempt to Gnome on Wayland in full. Replaced the computer’s hostname with ‘hostname’ and my admin username with ‘extremepayne’ but otherwise the log remains unchanged.
-- Logs begin at Mon 2020-05-25 16:33:11 MDT. --
May 26 11:19:16 hostname systemd[785]: Starting D-Bus User Message Bus Socket.
May 26 11:19:16 hostname systemd[785]: Listening on D-Bus User Message Bus Socket.
May 26 11:19:16 hostname systemd[785]: Reached target Sockets.
May 26 11:19:16 hostname systemd[785]: Reached target Basic System.
May 26 11:19:16 hostname systemd[785]: Reached target Main User Target.
May 26 11:19:16 hostname systemd[785]: Startup finished in 74ms.
May 26 11:19:16 hostname systemd[1]: Started User Manager for UID 1000.
May 26 11:19:16 hostname systemd[1]: Started Session 2 of user extremepayne.
May 26 11:19:25 hostname systemd[1]: systemd-localed.service: Succeeded.
May 26 11:19:25 hostname systemd[1]: systemd-hostnamed.service: Succeeded.
May 26 11:19:30 hostname systemd[1]: Condition check resulted in Default Swap File (/var/swapfile) being skipped.
May 26 11:19:30 hostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
May 26 11:19:30 hostname systemd[1]: Condition check resulted in Flush Journal to Persistent Storage being skipped.
May 26 11:19:30 hostname systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
May 26 11:19:30 hostname systemd[1]: Condition check resulted in Load Kernel Modules being skipped.
May 26 11:19:30 hostname systemd[1]: Condition check resulted in Rfkill bluetooth controllers on first boot being skipped.
May 26 11:19:30 hostname systemd[1]: Starting Attempt to start systemd-networkd if no one manages ethernet if...
May 26 11:19:30 hostname systemd[1]: networkd-fallback.service: Succeeded.
May 26 11:19:30 hostname systemd[1]: Finished Attempt to start systemd-networkd if no one manages ethernet if.
May 26 11:19:39 hostname gdm-password][915]: gkr-pam: unable to locate daemon control file
May 26 11:19:39 hostname gdm-password][915]: gkr-pam: stashed password to try later in open session
May 26 11:19:39 hostname gdm-password][915]: pam_unix(gdm-password:session): session opened for user extremepayne by (uid=0)
May 26 11:19:39 hostname systemd-logind[428]: New session 4 of user extremepayne.
May 26 11:19:39 hostname systemd[1]: Started Session 4 of user extremepayne.
May 26 11:19:39 hostname gdm-password][915]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
May 26 11:19:39 hostname kernel: rfkill: input handler enabled
May 26 11:19:39 hostname systemd[785]: Started D-Bus User Message Bus.
May 26 11:19:39 hostname /usr/libexec/gdm-wayland-session[944]: grep: /etc/shells: No such file or directory
May 26 11:19:39 hostname dbus-daemon[941]: [session uid=1000 pid=941] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.2' (uid=1000 pid=945 comm="gsettings get org.gnome.system.locale region ")
May 26 11:19:39 hostname systemd[785]: Starting Virtual filesystem service...
May 26 11:19:40 hostname dbus-daemon[941]: [session uid=1000 pid=941] Successfully activated service 'org.gtk.vfs.Daemon'
May 26 11:19:40 hostname systemd[785]: Started Virtual filesystem service.
May 26 11:19:40 hostname systemd[785]: gnome-session.target: Requested dependency OnFailure=gnome-session-failed.target ignored (target units cannot fail).
May 26 11:19:40 hostname systemd[785]: gnome-session-pre.target: Requested dependency OnFailure=gnome-session-shutdown.target ignored (target units cannot fail).
May 26 11:19:40 hostname systemd[785]: gnome-session-initialized.target: Requested dependency OnFailure=gnome-session-shutdown.target ignored (target units cannot fail).
May 26 11:19:40 hostname systemd[785]: gnome-session@gnome-initial-setup.target: Requested dependency OnFailure=gnome-session-failed.target ignored (target units cannot fail).
May 26 11:19:40 hostname systemd[785]: gnome-session@gnome-login.target: Requested dependency OnFailure=gnome-session-failed.target ignored (target units cannot fail).
May 26 11:19:40 hostname systemd[785]: gnome-session-failed.target: Requested dependency OnFailure=gnome-session-shutdown.target ignored (target units cannot fail).
May 26 11:19:40 hostname systemd[785]: gnome-session-wayland.target: Requested dependency OnFailure=gnome-session-shutdown.target ignored (target units cannot fail).
May 26 11:19:40 hostname systemd[785]: gnome-session@gnome.target: Requested dependency OnFailure=gnome-session-failed.target ignored (target units cannot fail).
May 26 11:19:40 hostname systemd[785]: Created slice gnome\x2dsession\x2dmanager.slice.
May 26 11:19:40 hostname systemd[785]: Reached target Session services which should run early before the graphical session is brought up.
May 26 11:19:40 hostname systemd[785]: Listening on Sound System.
May 26 11:19:40 hostname systemd[785]: Starting Monitor Session leader for GNOME Session...
May 26 11:19:40 hostname systemd[785]: Starting Sound Service...
May 26 11:19:40 hostname gnome-session-c[965]: Error creating FIFO: File exists
May 26 11:19:40 hostname systemd[785]: Started Monitor Session leader for GNOME Session.
May 26 11:19:40 hostname systemd[785]: Reached target Tasks to be run before GNOME Session starts.
May 26 11:19:40 hostname systemd[785]: Starting GNOME Session Manager (session: gnome)...
May 26 11:19:40 hostname gnome-session[968]: _IceTransTransNoListen: unable to find transport: tcp
May 26 11:19:40 hostname gnome-session[968]: gnome-session-binary[968]: WARNING: Could not parse desktop file org.gnome.SettingsDaemon.Wacom.desktop or it references a not found TryExec binary
May 26 11:19:40 hostname gnome-session-binary[968]: WARNING: Could not parse desktop file org.gnome.SettingsDaemon.Wacom.desktop or it references a not found TryExec binary
May 26 11:19:40 hostname gnome-session[968]: gnome-session-binary[968]: WARNING: Could not parse desktop file devilspie.desktop or it references a not found TryExec binary
May 26 11:19:40 hostname gnome-session-binary[968]: WARNING: Could not parse desktop file devilspie.desktop or it references a not found TryExec binary
May 26 11:19:40 hostname gnome-session[968]: gnome-session-binary[968]: WARNING: Could not parse desktop file tracker-extract.desktop or it references a not found TryExec binary
May 26 11:19:40 hostname gnome-session-binary[968]: WARNING: Could not parse desktop file tracker-extract.desktop or it references a not found TryExec binary
May 26 11:19:40 hostname gnome-session[968]: gnome-session-binary[968]: WARNING: Could not parse desktop file tracker-miner-fs.desktop or it references a not found TryExec binary
May 26 11:19:40 hostname gnome-session-binary[968]: WARNING: Could not parse desktop file tracker-miner-fs.desktop or it references a not found TryExec binary
May 26 11:19:40 hostname rtkit-daemon[508]: Successfully made thread 966 of process 966 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
May 26 11:19:40 hostname rtkit-daemon[508]: Supervising 4 threads of 2 processes of 2 users.
May 26 11:19:40 hostname gnome-session[968]: gnome-session-binary[968]: WARNING: Could not parse desktop file org.gnome.SettingsDaemon.Wacom.desktop or it references a not found TryExec binary
May 26 11:19:40 hostname gnome-session-binary[968]: WARNING: Could not parse desktop file org.gnome.SettingsDaemon.Wacom.desktop or it references a not found TryExec binary
May 26 11:19:40 hostname gnome-keyring-ssh.desktop[973]: gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used
May 26 11:19:40 hostname gnome-keyring-secrets.desktop[975]: gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used
May 26 11:19:40 hostname gnome-keyring-pkcs11.desktop[976]: gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used
May 26 11:19:40 hostname rtkit-daemon[508]: Supervising 4 threads of 2 processes of 2 users.
May 26 11:19:40 hostname gnome-keyring-ssh.desktop[977]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May 26 11:19:40 hostname gnome-keyring-secrets.desktop[978]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May 26 11:19:40 hostname gnome-keyring-pkcs11.desktop[980]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
May 26 11:19:40 hostname rtkit-daemon[508]: Successfully made thread 981 of process 966 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
May 26 11:19:40 hostname rtkit-daemon[508]: Supervising 5 threads of 2 processes of 2 users.
May 26 11:19:40 hostname systemd[785]: Started GNOME Session Manager (session: gnome).
May 26 11:19:40 hostname systemd[785]: Reached target GNOME Session Manager is ready.
May 26 11:19:40 hostname systemd[785]: Starting GNOME Shell on Wayland...
May 26 11:19:40 hostname rtkit-daemon[508]: Supervising 5 threads of 2 processes of 2 users.
May 26 11:19:40 hostname rtkit-daemon[508]: Successfully made thread 984 of process 966 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
May 26 11:19:40 hostname rtkit-daemon[508]: Supervising 6 threads of 2 processes of 2 users.
May 26 11:19:40 hostname systemd[785]: Started Sound Service.
May 26 11:19:40 hostname bluetoothd[514]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/A2DPSink/sbc
May 26 11:19:40 hostname bluetoothd[514]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/A2DPSource/sbc
May 26 11:19:40 hostname kernel: calling rfcomm_init+0x0/0xd9 [rfcomm] @ 995
May 26 11:19:40 hostname kernel: Bluetooth: RFCOMM TTY layer initialized
May 26 11:19:40 hostname kernel: Bluetooth: RFCOMM socket layer initialized
May 26 11:19:40 hostname kernel: Bluetooth: RFCOMM ver 1.11
May 26 11:19:40 hostname kernel: initcall rfcomm_init+0x0/0xd9 [rfcomm] returned 0 after 110 usecs
May 26 11:19:40 hostname dbus-daemon[941]: [session uid=1000 pid=941] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.25' (uid=1000 pid=983 comm="/usr/bin/gnome-shell ")
May 26 11:19:40 hostname systemd[785]: Starting Accessibility services bus...
May 26 11:19:40 hostname dbus-daemon[941]: [session uid=1000 pid=941] Successfully activated service 'org.a11y.Bus'
May 26 11:19:40 hostname systemd[785]: Started Accessibility services bus.
May 26 11:19:40 hostname gnome-shell[983]: Could not find cursor. Perhaps set XCURSOR_PATH?
May 26 11:19:40 hostname gnome-shell[983]: == Stack trace for context 0x560fc7dbb480 ==
May 26 11:19:40 hostname systemd[1]: Created slice system-systemd\x2dcoredump.slice.
May 26 11:19:40 hostname systemd[1]: Started Process Core Dump (PID 1013/UID 0).
May 26 11:19:41 hostname systemd[785]: gnome-shell-wayland.service: Main process exited, code=dumped, status=5/TRAP
May 26 11:19:41 hostname systemd[785]: gnome-shell-wayland.service: Failed with result 'core-dump'.
May 26 11:19:41 hostname systemd[785]: Failed to start GNOME Shell on Wayland.
May 26 11:19:41 hostname systemd[785]: Dependency failed for GNOME Shell on Wayland.
May 26 11:19:41 hostname systemd[785]: Dependency failed for GNOME Wayland Session.
May 26 11:19:41 hostname systemd[785]: Dependency failed for GNOME Wayland Session (session: gnome).
May 26 11:19:41 hostname systemd[785]: gnome-session-wayland@gnome.target: Job gnome-session-wayland@gnome.target/start failed with result 'dependency'.
May 26 11:19:41 hostname systemd[785]: gnome-session-wayland.target: Job gnome-session-wayland.target/start failed with result 'dependency'.
May 26 11:19:41 hostname systemd[785]: gnome-shell-wayland.target: Job gnome-shell-wayland.target/start failed with result 'dependency'.
May 26 11:19:41 hostname systemd[785]: gnome-shell-wayland.service: Triggering OnFailure= dependencies.
May 26 11:19:41 hostname systemd[785]: Condition check resulted in Disable GNOME Shell extensions after failure being skipped.
May 26 11:19:41 hostname systemd[785]: Stopped target GNOME Session Manager is ready.
May 26 11:19:41 hostname systemd[785]: Stopping GNOME Session Manager (session: gnome)...
May 26 11:19:41 hostname systemd[785]: gnome-session-manager@gnome.service: Succeeded.
May 26 11:19:41 hostname systemd[785]: Stopped GNOME Session Manager (session: gnome).
May 26 11:19:41 hostname systemd[785]: Stopped target Tasks to be run before GNOME Session starts.
May 26 11:19:41 hostname systemd[785]: Stopped target Session services which should run early before the graphical session is brought up.
May 26 11:19:41 hostname systemd[785]: Reached target Shutdown running GNOME Session.
May 26 11:19:41 hostname systemd[785]: Stopping Monitor Session leader for GNOME Session...
May 26 11:19:41 hostname systemd[785]: Starting Restart DBus after GNOME Session shutdown...
May 26 11:19:41 hostname systemd[785]: Stopped target Shutdown running GNOME Session.
May 26 11:19:41 hostname systemd[785]: Reached target Shutdown running GNOME Session.
May 26 11:19:41 hostname systemd[785]: Stopped target Shutdown running GNOME Session.
May 26 11:19:41 hostname systemd[785]: Started Restart DBus after GNOME Session shutdown.
May 26 11:19:41 hostname systemd[785]: gnome-session-monitor.service: Succeeded.
May 26 11:19:41 hostname systemd[785]: Stopped Monitor Session leader for GNOME Session.
May 26 11:19:41 hostname gdm-password][915]: pam_unix(gdm-password:session): session closed for user extremepayne
May 26 11:19:41 hostname gvfsd[948]: A connection to the bus can't be made
May 26 11:19:41 hostname systemd[785]: Stopping D-Bus User Message Bus...
May 26 11:19:41 hostname systemd[785]: dbus.service: Succeeded.
May 26 11:19:41 hostname systemd[785]: Stopped D-Bus User Message Bus.
May 26 11:19:41 hostname systemd[785]: at-spi-dbus-bus.service: Succeeded.
May 26 11:19:41 hostname systemd[785]: gnome-session-restart-dbus.service: Succeeded.
May 26 11:19:41 hostname systemd[480]: run-user-1000-gvfs.mount: Succeeded.
May 26 11:19:41 hostname systemd[785]: Started D-Bus User Message Bus.
May 26 11:19:41 hostname systemd[785]: run-user-1000-gvfs.mount: Succeeded.
May 26 11:19:41 hostname systemd[785]: gvfs-daemon.service: Succeeded.
May 26 11:19:41 hostname systemd[1]: run-user-1000-gvfs.mount: Succeeded.
May 26 11:19:41 hostname gdm[451]: GdmDisplay: Session never registered, failing
May 26 11:19:41 hostname kernel: rfkill: input handler disabled
May 26 11:19:41 hostname pulseaudio[966]: E: [pulseaudio] stdin-util.c: Unable to read or parse data from client.
May 26 11:19:41 hostname gnome-shell[1027]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 26 11:19:41 hostname gnome-shell[1027]: > Warning: Unsupported maximum keycode 569, clipping.
May 26 11:19:41 hostname gnome-shell[1027]: > X11 cannot support keycodes above 255.
May 26 11:19:41 hostname gnome-shell[1027]: Errors from xkbcomp are not fatal to the X server
May 26 11:19:41 hostname systemd[1]: session-4.scope: Succeeded.
May 26 11:19:41 hostname systemd-logind[428]: Session 4 logged out. Waiting for processes to exit.
May 26 11:19:41 hostname systemd-logind[428]: Removed session 4.
May 26 11:19:41 hostname systemd[1]: Started Clear Linux debuginfo daemon.
May 26 11:19:42 hostname clr_debug_daemon[1062]: ./.build-id/de/6944d3e330b33aadd1f6b983c9c5a6d35397c2.debug
May 26 11:19:42 hostname clr_debug_daemon[1066]: ./.build-id/00/4c9f6721c07ebf243690b031c5d9d86ce41e47.debug
May 26 11:19:43 hostname clr_debug_daemon[1070]: ./.build-id/7c/9496ed86ce738c61a114e97d4727bbdef3f1de.debug
May 26 11:19:44 hostname clr_debug_daemon[1089]: ./.build-id/d4/3a60a7476cfb1ff1288c8c4b7842ea2231b13b.debug
May 26 11:19:44 hostname systemd-coredump[1014]: Process 983 (gnome-shell) of user 1000 dumped core.
Stack trace of thread 983:
#0 0x00007faedc83adc5 __GI_raise (libc.so.6 + 0x41dc5)
#1 0x0000560fc67100dd dump_gjs_stack_on_signal_handler (gnome-shell + 0x30dd)
#2 0x00007faedc83ae70 __restore_rt (libc.so.6 + 0x41e70)
#3 0x00007faedc21854b _g_log_abort (libglib-2.0.so.0 + 0x8a54b)
#4 0x00007faedc218d66 g_log_structured_array (libglib-2.0.so.0 + 0x8ad66)
#5 0x0000560fc670ff9b default_log_handler (gnome-shell + 0x2f9b)
#6 0x00007faedc21d086 g_logv (libglib-2.0.so.0 + 0x8f086)
#7 0x00007faedc21d32f g_log (libglib-2.0.so.0 + 0x8f32f)
#8 0x00007faedb5896ab meta_cursor_sprite_xcursor_realize_texture (libmutter-6.so.0 + 0x5c6ab)
#9 0x00007faedb62e411 meta_cursor_renderer_native_update_cursor (libmutter-6.so.0 + 0x101411)
#10 0x00007faedb58c853 meta_cursor_renderer_update_cursor (libmutter-6.so.0 + 0x5f853)
#11 0x00007faedb58ccd5 sync_cursor.lto_priv.0 (libmutter-6.so.0 + 0x5fcd5)
#12 0x00007faedb5bef63 meta_display_reload_cursor (libmutter-6.so.0 + 0x91f63)
#13 0x00007faedb5d5da7 meta_run (libmutter-6.so.0 + 0xa8da7)
#14 0x0000560fc670f8ad main (gnome-shell + 0x28ad)
#15 0x00007faedc820dbd __libc_start_main (libc.so.6 + 0x27dbd)
#16 0x0000560fc670fabe _start (gnome-shell + 0x2abe)
Stack trace of thread 998:
#0 0x00007faeda891c24 futex_wait_cancelable (libpthread.so.0 + 0x10c24)
#1 0x00007faed4b6e6ab cnd_wait (i965_dri.so + 0x7706ab)
#2 0x00007faed4b6e3d8 impl_thrd_routine (i965_dri.so + 0x7703d8)
#3 0x00007faeda88a81f start_thread (libpthread.so.0 + 0x981f)
#4 0x00007faedc91cf23 __clone (libc.so.6 + 0x123f23)
Stack trace of thread 1008:
#0 0x00007faeda891c24 futex_wait_cancelable (libpthread.so.0 + 0x10c24)
#1 0x00007faed9212c00 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-68.so.0 + 0x91ac00)
#2 0x00007faed8b6cb6f _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-68.so.0 + 0x274b6f)
#3 0x00007faed8b6576f _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE8callMainIJLm0EEEEvSt16integer_sequenceImJXspT_EEE (libmozjs-68.so.0 + 0x26d76f)
#4 0x00007faeda88a81f start_thread (libpthread.so.0 + 0x981f)
#5 0x00007faedc91cf23 __clone (libc.so.6 + 0x123f23)
Stack trace of thread 993:
#0 0x00007faedc917020 syscall (libc.so.6 + 0x11e020)
#1 0x00007faedc1c0054 g_cond_wait_until (libglib-2.0.so.0 + 0x32054)
#2 0x00007faedc263d5e g_cond_wait_until (libglib-2.0.so.0 + 0xd5d5e)
#3 0x00007faedc1f05ee g_async_queue_timeout_pop_unlocked (libglib-2.0.so.0 + 0x625ee)
#4 0x00007faedc1ea98e g_thread_proxy (libglib-2.0.so.0 + 0x5c98e)
#5 0x00007faeda88a81f start_thread (libpthread.so.0 + 0x981f)
#6 0x00007faedc91cf23 __clone (libc.so.6 + 0x123f23)
Stack trace of thread 992:
#0 0x00007faedc910c4f __GI___poll (libc.so.6 + 0x117c4f)
#1 0x00007faedc2242d2 g_main_context_poll (libglib-2.0.so.0 + 0x962d2)
#2 0x00007faedc22440c g_main_context_iteration (libglib-2.0.so.0 + 0x9640c)
#3 0x00007faedc1ea98e g_thread_proxy (libglib-2.0.so.0 + 0x5c98e)
#4 0x00007faeda88a81f start_thread (libpthread.so.0 + 0x981f)
#5 0x00007faedc91cf23 __clone (libc.so.6 + 0x123f23)
Stack trace of thread 996:
#0 0x00007faedc910c4f __GI___poll (libc.so.6 + 0x117c4f)
#1 0x00007faedc2242d2 g_main_context_poll (libglib-2.0.so.0 + 0x962d2)
#2 0x00007faedc2275cb g_main_context_iteration (libglib-2.0.so.0 + 0x995cb)
#3 0x00007faedca015c0 dconf_gdbus_worker_thread (libdconfsettings.so + 0x55c0)
#4 0x00007faedc1ea98e g_thread_proxy (libglib-2.0.so.0 + 0x5c98e)
#5 0x00007faeda88a81f start_thread (libpthread.so.0 + 0x981f)
#6 0x00007faedc91cf23 __clone (libc.so.6 + 0x123f23)
Stack trace of thread 1000:
#0 0x00007faeda891c24 futex_wait_cancelable (libpthread.so.0 + 0x10c24)
#1 0x00007faed4b6e6ab cnd_wait (i965_dri.so + 0x7706ab)
#2 0x00007faed4b6e3d8 impl_thrd_routine (i965_dri.so + 0x7703d8)
#3 0x00007faeda88a81f start_thread (libpthread.so.0 + 0x981f)
#4 0x00007faedc91cf23 __clone (libc.so.6 + 0x123f23)
Stack trace of thread 997:
#0 0x00007faeda891c24 futex_wait_cancelable (libpthread.so.0 + 0x10c24)
#1 0x00007faed4b6e6ab cnd_wait (i965_dri.so + 0x7706ab)
#2 0x00007faed4b6e3d8 impl_thrd_routine (i965_dri.so + 0x7703d8)
#3 0x00007faeda88a81f start_thread (libpthread.so.0 + 0x981f)
#4 0x00007faedc91cf23 __clone (libc.so.6 + 0x123f23)
Stack trace of thread 994:
#0 0x00007faedc910c4f __GI___poll (libc.so.6 + 0x117c4f)
#1 0x00007faedc2242d2 g_main_context_poll (libglib-2.0.so.0 + 0x962d2)
#2 0x00007faedc1ba113 g_main_loop_run (libglib-2.0.so.0 + 0x2c113)
#3 0x00007faedc3ee0de gdbus_shared_thread_func (libgio-2.0.so.0 + 0x970de)
#4 0x00007faedc1ea98e g_thread_proxy (libglib-2.0.so.0 + 0x5c98e)
#5 0x00007faeda88a81f start_thread (libpthread.so.0 + 0x981f)
#6 0x00007faedc91cf23 __clone (libc.so.6 + 0x123f23)
Stack trace of thread 999:
#0 0x00007faeda891c24 futex_wait_cancelable (libpthread.so.0 + 0x10c24)
#1 0x00007faed4b6e6ab cnd_wait (i965_dri.so + 0x7706ab)
#2 0x00007faed4b6e3d8 impl_thrd_routine (i965_dri.so + 0x7703d8)
#3 0x00007faeda88a81f start_thread (libpthread.so.0 + 0x981f)
#4 0x00007faedc91cf23 __clone (libc.so.6 + 0x123f23)
Stack trace of thread 1011:
#0 0x00007faeda891c24 futex_wait_cancelable (libpthread.so.0 + 0x10c24)
#1 0x00007faed9212c00 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-68.so.0 + 0x91ac00)
#2 0x00007faed8b6cb6f _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-68.so.0 + 0x274b6f)
#3 0x00007faed8b6576f _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE8callMainIJLm0EEEEvSt16integer_sequenceImJXspT_EEE (libmozjs-68.so.0 + 0x26d76f)
#4 0x00007faeda88a81f start_thread (libpthread.so.0 + 0x981f)
#5 0x00007faedc91cf23 __clone (libc.so.6 + 0x123f23)
Stack trace of thread 1010:
#0 0x00007faeda891c24 futex_wait_cancelable (libpthread.so.0 + 0x10c24)
#1 0x00007faed9212c00 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-68.so.0 + 0x91ac00)
#2 0x00007faed8b6cb6f _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-68.so.0 + 0x274b6f)
#3 0x00007faed8b6576f _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE8callMainIJLm0EEEEvSt16integer_sequenceImJXspT_EEE (libmozjs-68.so.0 + 0x26d76f)
#4 0x00007faeda88a81f start_thread (libpthread.so.0 + 0x981f)
#5 0x00007faedc91cf23 __clone (libc.so.6 + 0x123f23)
Stack trace of thread 1009:
#0 0x00007faeda891c24 futex_wait_cancelable (libpthread.so.0 + 0x10c24)
#1 0x00007faed9212c00 _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-68.so.0 + 0x91ac00)
#2 0x00007faed8b6cb6f _ZN2js17ConditionVariable8wait_forERNS_9LockGuardINS_5MutexEEERKN7mozilla16BaseTimeDurationINS5_27TimeDurationValueCalculatorEEE (libmozjs-68.so.0 + 0x274b6f)
#3 0x00007faed8b6576f _ZN2js6detail16ThreadTrampolineIRFvPvEJPNS_12HelperThreadEEE8callMainIJLm0EEEEvSt16integer_sequenceImJXspT_EEE (libmozjs-68.so.0 + 0x26d76f)
#4 0x00007faeda88a81f start_thread (libpthread.so.0 + 0x981f)
#5 0x00007faedc91cf23 __clone (libc.so.6 + 0x123f23)
May 26 11:19:44 hostname systemd[1]: systemd-coredump@0-1013-0.service: Succeeded.
May 26 11:19:46 hostname clr_debug_daemon[1098]: ./.build-id/6d/4944767dfd7c6a72b99c651fe41e4c196c38f8.debug
May 26 11:19:50 hostname clr_debug_daemon[1102]: ./.build-id/cd/773d01a6ea130e381bf18685a641088e014b75.debug
May 26 11:19:51 hostname geoclue[604]: Service not used for 60 seconds. Shutting down..
May 26 11:19:51 hostname systemd[1]: geoclue.service: Succeeded.
Do you have a custom cursor theme installed?
May 26 11:19:40 hostname gnome-shell[983]: Could not find cursor. Perhaps set XCURSOR_PATH
I had one of the default ones before the update that removed all theme options from the default packages. I assumed the update would reset my cursor to be one of the new defaults, but I guess not. How might I set my theme to the new default or install the correct cursor theme?
what is the output of
sudo swupd info
and
sudo swupd diagnose --picky
I’m on version 33180 with the default version and content urls (https://cdn.download.clearlinux.org/update).
The diagnosis is taking a while and I want to eat lunch, so I’ll get back with that in a little while.
You might have a bug. You might’ve been using some stuff that now depends on desktop-assets-extras.
running
sudo swupd bundle-add desktops-assets-extras
might solve it but if that’s the case swupd should’ve caught it.
You can file a bug report here and post the above journal output which contains a core dump in the issue.
desktop-assets-extras was my first thought as well, but it’s installed (per sudo swupd bundle-list | grep desktop-assets-extras). It appears the diagnose command is hanging, so I’ll restart it and hopefully get back to you with those results soon.
I’ll go file an issue.
Hi, how did you manage to solve the issue?
I have the same problem now.
Hi all,
I am having the same problem here.
I already erased all my gnome-shell extensions from /home/user/.local/share/gnome-shell/extensions/ and /usr/share/gnome-shell/extensions/ but start a GUI fails for both Wayland and Xorg. I cannot even see the login screen.
My system was working fine today about 9 hours ago.
EDIT:
It seems to be something with Wayland and Gnome Display Manager.
I could start gnome under X11 using lightdm as display manager. I could not start Gnome under Wayland or even Sway under lightdm and I could not also start GDM using X11 as backend.
Any developer has any thoughts on this?
sudo swupd bundle-remove desktop-autostart
This worked for me.
For future users running into the same issue, I never resolved it and ended up installing a different OS on the disk I was using to run Clear Linux. No significant progress was made on the issue or in this thread. Can't log in to Gnome after update · Issue #1993 · clearlinux/distribution · GitHub is the issue. Good luck figuring out similar issues. However, since the computer with the original issue no longer exists, no progress was made, and there’s a good chance you’re facing a superficially similar but ultimately different issue, I would recommend opening a new forum thread or GH Issue if you believe you may be facing the same issue. I doubt posting here will be of use to you.