Sebastien, Thanks for your reply. Regarding step 1 below, here is what I did:
stewart@stewart-Ub1904-VB:~$ cd /var/crashstewart@stewart- Ub1904-VB:/var/crash$ ls -ltotal 34024-rw-r----- 1 stewart whoopsie 5069610 Jul 9 13:52 _usr_bin_gnome-control-center.1000.crash-rw-r----- 1 stewart whoopsie 26230098 Jul 9 14:24 _usr_bin_gnome-shell.1000 .crash-rw-r----- 1 stewart whoopsie 1943261 Jul 9 14:34 _usr_bin_seahorse.1000.crash-rw-rw-r-- 1 stewart whoopsie 0 Jul 9 14:34 _usr_bin_seahorse.1000.upload-rw------- 1 whoopsie whoopsie 0 Jul 9 14:34 _usr_bin_seahorse.1000.uploaded-rw-r----- 1 stewart whoopsie 1591095 Jul 9 06:18 _usr_bin_update- notifier.1000.crashstewart@stewart-Ub1904-VB:/var/crash$ ubuntu-bug _usr_bin_gnome-control-center.1000.crashstewart@stewart- Ub1904-VB:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crashstewart @stewart-Ub1904-VB:/var/crash$ ubuntu-bug _usr_bin_seahorse.1000.crash stewart@stewart-Ub1904-VB:/var/crash$ ubuntu-bug _usr_bin_update- notifier.1000.crash stewart@stewart-Ub1904-VB:/var/crash$ In each of the four cases above, I answered "Send To Developer". There was no indication of an "ID of the newly created bug", so I'm not quite sure what you are referring to. Since it's not clear if step 1 passed or failed, regarding step 2, here's the whoopsie-id of my machine: stewart@stewart-Ub1904-VB:/var/crash$ sudo cat /var/lib/whoopsie /whoopsie-id [sudo] password for stewart: 3a7f4eb7089bebcee97e94dfb1aa150f5ebf7ce592f812faba6273cbd267e0e29ef94a0856f9f7f53f0142b1b12318a1b50b6785439ce33a2b4eb9eee771c10dstewart @stewart-Ub1904-VB:/var/crash$ I've attached a screen shot from: https://errors.ubuntu.com/user/3a7f4eb7089bebcee97e94dfb1aa150f5ebf7ce592f812faba6273cbd267e0e29ef94a0856f9f7f53f0142b1b12318a1b50b6785439ce33a2b4eb9eee771c10d When I tried to view that web page, here is the message that appeared: Sorry, you are not a member of a group that is allowed to see the data from error reports. Please fill out this form to request access. Perhaps you are able to view the data from error reports. To summarize: I attempted to follow the instructions provided, but it's not clear to me whether it was successful. Either the instructions weren't clear or I didn't follow them properly. I really would like to assist in solving this issue. However, this is a production system and I'm sorry but I can't be rebooting to recreate bugs especially when it means that I have to restore to a previous image with timeshift after I've updated two packages totalling 1.3MB in size (see the second attachment): stewart@stewart-Ub1904-VB:/var/crash$ sudo apt update[sudo] password for stewart: Hit:1 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InReleaseGet:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Hit:3 http://ca.archive.ubuntu.com/ubuntu bionic InRelease Get:4 http://ca.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Hit:5 http://ppa.launchpad.net/teejee2008/ppa/ubuntu bionic InRelease Get:6 http://security.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 Metadata [24.1 kB] Get:7 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [682 kB]Get:8 http://security.ubuntu.com/ubuntu bionic-security/main DEP-11 48x48 Icons [10.4 kB]Get:9 http://security.ubuntu.com/ubuntu bionic-security/main DEP-11 64x64 Icons [31.7 kB]Get:10 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 Metadata [41.2 kB]Get:11 http://security.ubuntu.com/ubuntu bionic- security/universe DEP-11 48x48 Icons [16.4 kB]Get:12 http://security.ubuntu.com/ubuntu bionic-security/universe DEP-11 64x64 Icons [105 kB] Get:13 http://security.ubuntu.com/ubuntu bionic- security/multiverse amd64 DEP-11 Metadata [2,464 B] Get:14 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages [559 kB]Get:15 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11 Metadata [283 kB]Get:16 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 48x48 Icons [66.6 kB]Get:17 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 64x64 Icons [134 kB]Get:18 http://ca.archive.ubuntu.com/ubuntu bionic- updates/universe amd64 Packages [970 kB]Get:19 http://ca.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages [954 kB]Get:20 http://ca.archive.ubuntu.com/ubuntu bionic- updates/universe amd64 DEP-11 Metadata [250 kB]Get:21 http://ca.archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 48x48 Icons [199 kB]Get:22 http://ca.archive.ubuntu.com/ubuntu bionic- updates/universe DEP-11 64x64 Icons [412 kB]Get:23 http://ca.archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 DEP-11 Metadata [2,464 B]Fetched 4,920 kB in 4s (1,164 kB/s) Reading package lists... DoneBuilding dependency tree Reading state information... Done4 packages can be upgraded. Run 'apt list --upgradable' to see them.stewart@stewart-Ub1904-VB:/var/crash$ sudo apt list --upgradableListing... Donegir1.2-mutter-2/bionic-updates 3.28.4-0ubuntu18.04.1 amd64 [upgradable from: 3.28.3+git20190124-0ubuntu18.04.2]gnome-shell/bionic-updates 3.28.4-0ubuntu18.04.1 amd64 [upgradable from: 3.28.3+git20190124-0ubuntu18.04.2]gnome-shell-common/bionic-updates ,bionic-updates 3.28.4-0ubuntu18.04.1 all [upgradable from: 3.28.3+git20190124-0ubuntu18.04.2]libmutter-2-0/bionic-updates 3.28.4-0ubuntu18.04.1 amd64 [upgradable from: 3.28.3+git20190124-0ubuntu18.04.2]stewart@stewart-Ub1904-VB:/var/crash$ If I can assist further, please provide clear instructions, and I will do my best to follow. ThanksStewart Seidel On Friday, July 12, 2019, 01:40:52 PM PDT, Sebastien Bacher <seb...@ubuntu.com> wrote: 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. 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. 2. If step 1 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. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. 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: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1835936 Title: gnome-control-center crash ubuntu 18.04.2 Status in gnome-control-center package in Ubuntu: Invalid Bug description: Ubuntu 18.04.02 fresh installed on Virtualbox 6.0.8 including Guest Additions on host Mac Pro running 10.14.5 Mojave in April 2019. Ubuntu system has latest patches EXCEPT mutter-2 (which cause login GUI to fail after reboot). crash logs for gnome-control-center, gnome-shell and seahorse attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1835936/+subscriptions ** Attachment added: "Screenshot 2019-07-12 16.17.50.png" https://bugs.launchpad.net/bugs/1835936/+attachment/5276846/+files/Screenshot%202019-07-12%2016.17.50.png ** Attachment added: "Screenshot 2019-07-12 16.30.50.png" https://bugs.launchpad.net/bugs/1835936/+attachment/5276847/+files/Screenshot%202019-07-12%2016.30.50.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1835936 Title: gnome-control-center crash ubuntu 18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1835936/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
