gnome-shell crashed with SIGABRT in g_assertion_message()

Bug #1046486 reported by Colin Keenan
62
This bug affects 14 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I may have somehow messed up my gnome 3 gnome-shell. I can still use gnome classic without extra graphics or whatever it's called.

I was trying to report about gnome-shell using 100% cpu in this bug report I filed earlier about compiz using 100% cpu: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1044060

And, because gnome-shell was using 100% cpu, I had to kill it and restart it from a virtual console. For some reason it didn't occur to me to use "DISPLAY=0: gnome-shell --replace". Because I had just been running a dstack script in that virtual console, I was in super-user mode when I killed and restarted gnome-session.

Now, whenever I try to log into gnome 3, gnome-shell doesn't load. If I run gnome-shell --replace from a terminal window, I get the following error:

JS LOG: Error: Requiring IBus, version none: Typelib file for namespace 'IBus' (any version) not found
p11-kit: duplicate configured module: gnome-keyring.module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so
Window manager warning: Log level 16: g_object_class_override_property: Can't find property to override for 'GTlsCertificateGnutls::certificate-bytes'
Window manager warning: Log level 16: g_object_class_override_property: Can't find property to override for 'GTlsCertificateGnutls::private-key-bytes'
Window manager warning: Log level 16: g_object_get_valist: object class `GTlsCertificateGnutls' has no property named `certificate-bytes'

(gnome-shell:6305): GLib-Net-CRITICAL **: get_der_for_certificate: assertion `bytes' failed

(gnome-shell:6305): GLib-Net-CRITICAL **: load_anchor_file: assertion `der != NULL' failed
**
GLib-Net:ERROR:gtlsbackend-gnutls.c:149:g_tls_backend_gnutls_get_default_database: assertion failed: (result)
Aborted (core dumped)

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-shell 3.5.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic i686
ApportVersion: 2.5.1-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Wed Sep 5 09:55:23 2012
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: gnome-shell
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgiognutls.so
Title: gnome-shell crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-08-23 (12 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Colin Keenan (colinkeenan) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_assertion_message (domain=domain@entry=0xac65afcf "GLib-Net", file=file@entry=0xac65afd8 "gtlsbackend-gnutls.c", line=line@entry=149, func=func@entry=0xac65b020 "g_tls_backend_gnutls_get_default_database", message=0x915fa58 "assertion failed: (result)") at /build/buildd/glib2.0-2.33.12/./glib/gtestutils.c:1877
 g_assertion_message_expr (domain=domain@entry=0xac65afcf "GLib-Net", file=file@entry=0xac65afd8 "gtlsbackend-gnutls.c", line=149, func=0xac65b020 "g_tls_backend_gnutls_get_default_database", expr=0xac65afed "result") at /build/buildd/glib2.0-2.33.12/./glib/gtestutils.c:1888
 g_tls_backend_gnutls_get_default_database (backend=0x913e0c0) at gtlsbackend-gnutls.c:149
 g_tls_backend_get_default_database (backend=0x913e0c0) at /build/buildd/glib2.0-2.33.12/./gio/gtlsbackend.c:142
 ?? () from /tmp/tmpXHS_wh/usr/lib/i386-linux-gnu/libsoup-2.4.so.1

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
summary: - gnome-shell crashed with SIGABRT in raise()
+ gnome-shell crashed with SIGABRT in g_assertion_message()
tags: removed: need-i386-retrace
Revision history for this message
Colin Keenan (colinkeenan) wrote :

This is strange. I logged into Ubuntu under Compiz/Unity, shutdown, and later when I turned on my computer and logged in again, I got a bunch of error messages so went ahead and tried to report them all. One of them was this one again, which it said was a known issue. What's strange about it is that I wasn't running gnome-shell this time or last time.

Jeremy Bícha (jbicha)
visibility: private → public
Revision history for this message
Colin Keenan (colinkeenan) wrote :

I noticed today's updates included updates to gnome. After the updates and re-boot, I was able to log into gnome and gnome-shell loaded fine. That's what I'm using now. Maybe this bug can be marked as fixed released or something. Of course, I don't actually know if the trouble I was having getting gnome-shell to run has anything to do with this bug that was detected by Ubuntu automatically more than once.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for reporting this bug to Ubuntu. Ubuntu 12.10 reached End of Life in 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Please upgrade to Ubuntu 16.04 LTS and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.

I apologize that we are not always to respond to bug reports promptly. Do feel free to report any other bugs you may find.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.