sudo cat /var/crash/_usr_bin_gnome-shell.1000*
So I got a crash and it was uploaded. I actually know what caused the crash so I want to add that somewhere. Can I do that?
Add group whoopsie to your user
sudo adduser $USER whoopsie
so (after re-login) you can see the content of the .crash file
and you will find some info about your crash
then go to https://launchpad.net/gnome-shell and check if can find a bug that looks like yours
There is no .crash file, only .upload and .uploaded.
It depends. Not all crash reports turn into bugs. You can manually file a bug, and link to the previously-uploaded crash report. Selected bug triage developers have access to those, but they’re not public. You can find all the crash reports from your current PC by running the following command
xdg-open https://errors.ubuntu.com/user/$(sudo cat /var/lib/whoopsie/whoopsie-id)
For me that opens a web page like this:
Yours will differ of course. But you can see which component needs a bug filing against it, and can link to the url you have under the date field.
@ernstp, the content of the
.uploaded file identifies the crash. So in your case:
$ cat /var/crash/_usr_bin_gnome-shell.1000.uploaded
and then the details page is:
But for everyone’s security, not everyone can view that page. In the case of your crash above, I can tell it is gnome-shell that crashed but there is no bug ID. The relevant section of log says:
gnome-shell: JS ERROR: Error: Source.notify() has been moved to Source.showNotification()this code will break in the future
systemd: org.gnome.Shell@wayland.service: Main process exited, code=dumped, status=6/ABRT
so the first thing you should do is try disabling/uninstalling the gamemode extension.
In future if you want to get a bug ID and more help you should be able to force a new upload with:
sudo rm FILENAME.uploaded
sudo apport-cli FILENAME.crash
If that doesn’t work and you’re desperate for help then please manually create a bug using this page (or similar).
Thanks for the excellent replies!