Yeah, I'm not saying that's wrong. It's just the only explanation I can think of because your gnome-shell seems to be stuck in gvfs code querying the (encrypted) home directory. If correct then that's just a bug.
Unfortunately I haven't yet found any other reports of such a hang, but that also would be because we don't get automated hang reports, only automated crash reports. So this might be a common problem and we'd never know. Before going so far as to ask you to test with a non-encrypted directory we need to check the most common cause of bugs first. That is third- party extensions. Please disable all your extensions and let us know if the problem then goes away... b'org.gnome.shell' b'enabled-extensions' b"['openweather- [email protected]', '[email protected]', 'multi- volume@tigersoldier', '[email protected]', '[email protected]', '[email protected]', '[email protected]', '[email protected]', 'AdvancedVolumeMixer_harry.karvonen.gmail.com', 'mconnect_andyholmes.github.io', 'mediaplayer_patapon.info', 'openweather-extension_jenslody.de', 'drive-menu_gnome-shell- extensions.gcampax.github.com', 'ubuntu-dock_ubuntu.com', 'system- monitor_paradoxxx.zero.gmail.com', 'dock-settings@lagrangian', 'dash-to- dock_micxgx.gmail.com', '[email protected]', '[email protected]', '[email protected]', 'drive- [email protected]', 'suspend- button@laserb', 'activities-config@nls1729', 'ubuntu- [email protected]', '[email protected]', 'extension- reloader@nls1729']" Start by disabling drive-related extensions like the drive-menu ones... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1781647 Title: gnome-shell crashed with SIGABRT in __GI___poll() from g_main_context_poll() from g_main_context_iterate() from g_main_loop_run() from g_dbus_connection_send_message_with_reply_sync() from g_dbus_connection_call_sync_internal() Status in gnome-shell package in Ubuntu: Incomplete Bug description: The computer hard-locked up after I did a suspend/resume cycle and entered my password. I generated this via ssh'ing in from a phone and issuing a kill -ABRT command on my gnome-shell session pid. This happens randomly but with annoying frequency and it happens whether I run gnome-shell in X or Wayland. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 Uname: Linux 4.17.5-041705-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 13 18:57:15 2018 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1529538342 InstallationDate: Installed on 2017-08-16 (331 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-shell StacktraceTop: raise (sig=<optimised out>) at ../sysdeps/unix/sysv/linux/raise.c:51 () <signal handler called> () at /lib/x86_64-linux-gnu/libpthread.so.0 __GI___poll (fds=0x55ddc16f8270, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGABRT in raise() UpgradeStatus: Upgraded to bionic on 2017-11-17 (238 days ago) UserGroups: adm bumblebee cdrom dip kvm lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781647/+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
