Public bug reported:
This bug has been persisting since I've bought an external monitor for
my laptop and started using Wayland (first on Ubuntu 20.04) until today
(Ubuntu 21.10).
It isn't consistent, but it occurs about 90% of the time when I'm on
Wayland. On Xorg, this has never occurred.
When
Thanks. The bug report is now attached to this bug.
(Some asides about the bug-uploading process:)
There was already a _usr_bin_gnome-shell.1000.crash.uploaded file,
however I cannot see my bug in errors.ubuntu.com. So I went and tried
doing it manually:
```
$ ubuntu-bug _usr_bin_gnome-shell.10
attached is a log after reproducing the bug, crashing, logging in,
waiting 10 seconds, rebooting, and logging. NOTE: edited for privacy
reasons (names, references to VPN connections)
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+attachm
Hello Daniel, coming over here as requested from the other bug
(1952766).
Two questions:
1. How can you tell from that page that the code change has arrived in
40.1? I can only see when it was merged, but am unable to tell whether
this particular fix is in that version.
2. Since I'm on gnome-she
apport information
** Tags added: apport-collected impish third-party-packages wayland-
session
** Description changed:
This bug has been persisting since I've bought an external monitor for
my laptop and started using Wayland (first on Ubuntu 20.04) until today
(Ubuntu 21.10).
It isn
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1952766/+attachment/5545669/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1952766/+attachment/5545671/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1952766/+attachment/5545670/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
http
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1952766/+attachment/5545673/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1952766/+attachment/5545672/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.lau
Hello Daniel, thanks for your help. Please find the requested
information attached. Two extra points:
- I set the external monitor as my primary monitor, with the dock and title bar
displaying here
- Since 40.1 already contains the fix for the symptoms you quoted from my
report, while they are t
Funnily, after disabling the Ubuntu Dock (have not yet logged out and in
again) and unplugging my cable, there was no crash. Then again, the
crashes are not consistent so I'll try again.
This interferes with my work so much that I cannot test this constantly.
--
You received this bug notificatio
After a few more disconnects with the Ubuntu Dock disabled and no
crashes, it sounds like the culprit may be the Ubuntu Dock. The solution
should be relatively simple then (although I'm a bit shocked that it can
take down mutter)
--
You received this bug notification because you are a member of U
I'm sure the discussion has been held elsewhere, and there's been made a
case against sandboxing them or handling their crashes, as lack of
freedom would defeat the very purpose of these extensions?
At any rate I'm happy to have reached a solution. 3 monitor unplugs
without crashes convinces me th
Public bug reported:
A very annoying GTK bug (which breaks copying and pasting, the computer
user's favourite activity) has been fixed in GTK 3.24.31. Unfortunately,
Ubuntu 21.10 is still stuck on 3.24.30. I'd think that making 3.24.31
available wouldn't break much, but would help a lot of us out.
Public bug reported:
Since a few days, the fingerprint reader won't work anymore (Dell XPS
9300, Goodix Fingerprint reader Ubuntu 21.04, Mutter). Notably it
started happening after kernel 5.11.22 was installed.
$ fprintd-list
Failed to get Fprintd manager: Error calling StartServiceByName for
16 matches
Mail list logo
