gnome-shell crashed with SIGABRT in meta_bug()

Bug #1787925 reported by Nicolas Göddel
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)

Bug Description

I have not much to say. I just happened without doing anything special. I am working with the virtualbox GUI over SSH and x-forwarding. That's all.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-shell 3.18.5-0ubuntu0.3
ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
Uname: Linux 4.4.0-131-generic x86_64
NonfreeKernelModules: blackmagic_io blackmagic nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Mon Aug 20 12:42:56 2018
DisplayManager: gdm3
InstallationDate: Installed on 2014-04-18 (1584 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to xenial on 2018-06-09 (71 days ago)

Revision history for this message
Nicolas Göddel (ngoeddel) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) 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 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-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Nicolas Göddel (ngoeddel) wrote :

Hi Daniel. I used the command `ubuntu-bug gnome-shell` to send this bug to launchpad. If I try this with the crash file instead it only opens a window with some crash details but there is no possibility to upload anything.
Going to only tells me that I am not logged in. After logging in it says: "No errors have been reported from this system"
Can I upload the 45 MB crash file somewhere else? I don't know if it contains sensible information.

Reproducing the issue seems not to be possible because this was an error I never saw before and it just happened without doing anything spectacular.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If you did use 'ubuntu-bug' to generate this then it has failed somehow. Sorry, that's a bug in 'ubuntu-bug' or such. So maybe try reproducing the problem and run it again on a new crash file to see if you get a bug with more details in it.

"No errors have been reported from this system" is a web site bug :)
Just keep the page open for a few seconds longer and it should change to something more useful.

If you can't reproduce the error then no problem... The bug will automatically close after 60 days of no comments.

Revision history for this message
Nicolas Göddel (ngoeddel) wrote :

I just wanted to help but when the bug reporting system does not work correctly I have no idea what to do. I often get SIGABRTs and similar crashes with gnome-shell but the most time these bugs were already reported and I only click on "This bug affects you". In the past I also created some bug reports but these seem to be fine.

Maybe the bug will be gone when I have updated to Ubuntu 18.04 LTS. I just had no time for this until now.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers