bamfdaemon crashed with SIGABRT in dbus_g_connection_register_g_object()

Bug #758095 reported by Alexey Krivenko
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bamf (Ubuntu)
New
Undecided
Unassigned

Bug Description

bamfdaemon crashed with SIGABRT in dbus_g_connection_register_g_object()

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: bamfdaemon 0.2.84-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
CrashCounter: 1
Date: Tue Apr 12 00:14:11 2011
ExecutablePath: /usr/lib/bamf/bamfdaemon
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/bamf/bamfdaemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=ru_UA:en
 LANG=ru_UA.UTF-8
Signal: 6
SourcePackage: bamf
StacktraceTop:
 dbus_g_connection_register_g_object () from /usr/lib/libdbus-glib-1.so.2
 bamf_view_export_on_bus ()
 ?? ()
 ?? ()
 ?? ()
Title: bamfdaemon crashed with SIGABRT in dbus_g_connection_register_g_object()
UpgradeStatus: Upgraded to natty on 2011-03-30 (12 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (Do:1682): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.
 (nautilus:1660): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #754225, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
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.