bamfdaemon crashed with SIGABRT in g_assertion_message()

Bug #947828 reported by benske on 2012-03-06
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bamf (Ubuntu)
Medium
Unassigned

Bug Description

Programm says it crashed, but I don't know what happend. The systems works just normal.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bamfdaemon 0.2.110-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Mon Mar 5 17:59:57 2012
ExecutablePath: /usr/lib/bamf/bamfdaemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
ProcCmdline: /usr/lib/bamf/bamfdaemon
Signal: 6
SourcePackage: bamf
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_test_init () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: bamfdaemon crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-03-04 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

benske (ben-beuster) wrote :
visibility: private → public

StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x7f9bcc67a9c0 "unregistered", message=0x1aca980 "assertion failed: (vtable != NULL && vtable->method_call != NULL)") at /build/buildd/glib2.0-2.31.20/./glib/gtestutils.c:1858
 g_assertion_message_expr (domain=0x7f9bcc657d01 ")", file=0x421f <Address 0x421f out of bounds>, line=4678, func=0x7f9bcc67a9c0 "unregistered", expr=0x20 <Address 0x20 out of bounds>) at /build/buildd/glib2.0-2.31.20/./glib/gtestutils.c:1869
 ?? ()
 invoke_set_property_in_idle_cb (_data=0x421f) at /build/buildd/glib2.0-2.31.20/./gio/gdbusconnection.c:4075
 ?? ()

Changed in bamf (Ubuntu):
importance: Undecided → Medium
summary: - bamfdaemon crashed with SIGABRT in raise()
+ bamfdaemon crashed with SIGABRT in g_assertion_message()
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers