bamfdaemon crashed with SIGABRT in raise()

Bug #931798 reported by Jeremiah Njoroge
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bamf (Ubuntu)
New
Undecided
Unassigned

Bug Description

was changing the universal access settings in the System Settings panel when a dialogue reporting the crash popped up

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bamfdaemon 0.2.108-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Feb 13 15:17:29 2012
ExecutablePath: /usr/lib/bamf/bamfdaemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120119)
ProcCmdline: /usr/lib/bamf/bamfdaemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
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
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: bamfdaemon crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Jeremiah Njoroge (jnjoroge) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_test_log_send (buffer=0x7f3b453e82e0 "distribute_method_call", n_bytes=17071776) at /build/buildd/glib2.0-2.31.16/./glib/gtestutils.c:564
 g_test_log (lbit=G_TEST_LOG_NONE, string1=0x7f3b44c501c0 "\200\263\b\001", string2=<optimized out>, n_args=<optimized out>, largs=0xec1c10) at /build/buildd/glib2.0-2.31.16/./glib/gtestutils.c:633
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
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.