bluetooth-applet crashed with signal 5 in g_object_newv()

Bug #631594 reported by Dale
190
This bug affects 44 people
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: gnome-bluetooth

N/A

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-bluetooth 2.31.6-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Date: Mon Sep 6 08:52:13 2010
ExecutablePath: /usr/bin/bluetooth-applet
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100831.2)
ProcCmdline: bluetooth-applet
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-bluetooth
StacktraceTop:
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
 g_object_new () from /usr/lib/libgobject-2.0.so.0
Title: bluetooth-applet crashed with signal 5 in g_object_newv()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (bluetooth-applet:1181): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
 (nautilus:1185): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (polkit-gnome-authentication-agent-1:1184): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Dale (drbeams) wrote :
visibility: private → public
Changed in gnome-bluetooth (Ubuntu):
status: New → Confirmed
Revision history for this message
Laryllan (laryllan) wrote :

I got this after removing a BT dongle. Happend after next reboot.

Revision history for this message
Dale (drbeams) wrote :

Working on a 10.10 test installation VM via virtualbox. May have happened after installation of guest additions. Crash is constant. Host is 10.04, guest is 10.10.

Revision history for this message
Sebastien Bacher (seb128) wrote :

it's probably the same issue than bug #631548

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.