Journal attached. journalctl -b-1 > prevjournal.txt Specifying boot ID or boot offset has no effect, no persistent journal was found.
In /var/crash: -rw-r----- 1 alan whoopsie 70481294 Oct 9 14:29 _usr_bin_gnome- shell.1000.crash When I run ubuntu-bug I get the pop up But, I don't get a link to a bug report. How do I find my machine's whoopsie id? My search fu did not return a way, and the help option on whoopsie doesn't indicate as such. -rw-r----- 1 alan whoopsie 18845753 Oct 2 12:57 _opt_Mattermost_mattermost-desktop.1000.crash -rw-r--r-- 1 alan whoopsie 0 Oct 2 12:57 _opt_Mattermost_mattermost- desktop.1000.upload -rw------- 1 whoopsie whoopsie 37 Oct 2 12:57 _opt_Mattermost_mattermost-desktop.1000.uploaded -rw-r----- 1 alan whoopsie 72148708 Oct 6 17:47 _opt_Signal_signal- desktop.1000.crash -rw-r--r-- 1 alan whoopsie 0 Oct 6 17:47 _opt_Signal_signal- desktop.1000.upload -rw------- 1 whoopsie whoopsie 37 Oct 6 17:47 _opt_Signal_signal- desktop.1000.uploaded -rw-r----- 1 alan whoopsie 70481294 Oct 9 14:29 _usr_bin_gnome- shell.1000.crash -rw-r--r-- 1 alan whoopsie 0 Oct 9 14:29 _usr_bin_gnome- shell.1000.upload -rw------- 1 whoopsie whoopsie 37 Oct 9 14:29 _usr_bin_gnome- shell.1000.uploaded -rw-r----- 1 alan whoopsie 1858014 Oct 4 11:20 _usr_libexec_tracker- extract-3.1000.crash -rw-r--r-- 1 alan whoopsie 0 Oct 4 11:20 _usr_libexec_tracker-extract- 3.1000.upload -rw------- 1 whoopsie whoopsie 37 Oct 4 11:22 _usr_libexec_tracker- extract-3.1000.uploaded Alan On Fri, 2025-10-10 at 05:45 +0000, Daniel van Vugt wrote: > This used to be a common problem so we probably just need to figure > out > *which* crash this is... > > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It sounds like some part of the system has crashed. To > help us find the cause of the crash please follow these steps: > > 1. Run these commands: > journalctl -b0 > journal.txt > journalctl -b-1 > prevjournal.txt > and attach the resulting text files here. > > 2. Look in /var/crash for crash files and if found run: > ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. > > 3. If step 2 failed then look at > https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the > machine. > Do you find any links to recent problems on that page? If so then > please > send the links to us. > > Please take care to avoid attaching .crash files to bugs as we are > unable to process them as file attachments. It would also be a > security > risk for yourself. > > ** Changed in: mutter (Ubuntu) > Status: New => Incomplete > > ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) > ** Attachment added: "Image-ACSBE3.png" https://bugs.launchpad.net/bugs/2127204/+attachment/5916807/+files/Image-ACSBE3.png ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/2127204/+attachment/5916808/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2127204 Title: When unplugging external monitors (USB C or HDMI) Desktop reports an error occurred and forces a logout of the user session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2127204/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
