bluetooth-applet crashed with signal 5 in g_object_newv() just after login

Bug #631511 reported by Piotr Arłukowicz
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnome-bluetooth

No bluetooth devices were connected and only limited number of USB devices was in use (keyboard, mouse and printer). This was fresh installation of 10.10 test live cd.

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 x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Sep 6 14:05:26 2010
ExecutablePath: /usr/bin/bluetooth-applet
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcCmdline: bluetooth-applet
ProcEnviron:
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
 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 ()
 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:
 (polkit-gnome-authentication-agent-1:1512): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (bluetooth-applet:1504): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
 (nautilus:1510): 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 #631498, 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.