Thanks. Ugh, System Monitor seems to have caused a couple of bugs...
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
system-monitor (Ubuntu)
** Changed in: gnome-shell-extension-system-monitor (Ubuntu)
Status: Invalid => New
** Summary changed:
- gnome-shell crashed
Just for completeness, there have been no more crashes with Removable
Drive Menu enabled, so it is likely that System Monitor was the culprit.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Thanks. Though we don't need to wait for the result of further testing
to believe the bug is not in gnome-shell.
If you find the bug is in an extension that is offered by the Ubuntu
archive then we should reopen it as a task against that extension.
** Changed in: gnome-shell (Ubuntu)
So far there have been no lockups since I disabled those two, so I've
re-enabled Removable Drive Menu to see if that causes the lockups to
return.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
No, the power of gnome-shell's extensibility is also its weakness.
Basically everything in gnome-shell is a global that extensions can
modify directly or indirectly. That's what makes so many extensions
possible, but it also means that they are not isolated. So any bug in an
extension can easily
Ok, I have started by disabling Removable Drive Menu and System Monitor
and so far, so good. (But since it's random, it might take a while to
reproduce anyway.)
So gnome-shell doesn't enforce any sort of timeout for non-responsive
extensions?
--
You received this bug notification because you
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
I don't think there's anything particularly unusual about my home
folder. I formatted the root partition as btrfs instead of ext4 when I
did the installation, so the Ubuntu installer put /home into its own
subvolume. I also asked the installer to encrypt the home folder, so
it's encrypted with
Thanks for doing this.
If the lockup is in gnome-shell then the only slightly suspicious
information I can see relates to:
target_method_name = 0x7fd923379223 "QueryFilesystemInfo"
target_interface_name = 0x55ddc48f43e0 "org.gtk.vfs.Mount"
so something might be stuck querying
