Bug 634157 – crash in Bluetooth Manager:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 634157 - crash in Bluetooth Manager:


Summary:	crash in Bluetooth Manager:


Status:	RESOLVED DUPLICATE of bug 632832

Product:	gnome-bluetooth
Classification:	Core
Component:	applet
Version:	2.32.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	gnome-bluetooth-general-maint@gnome.bugs
QA Contact:	gnome-bluetooth-general-maint@gnome.bugs

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-11-06 12:14 UTC by francesco.regazzo
Modified:	2010-11-06 13:08 UTC

See Also:
GNOME target:	---
GNOME version:	2.31/2.32

Description francesco.regazzo 2010-11-06 12:14:22 UTC

Version: 2.32.0

What were you doing when the application crashed?



Distribution: Ubuntu 10.10 (maverick)
Gnome Release: 2.32.0 2010-09-27 (Ubuntu)
BugBuddy Version: 2.31.92

System: Linux 2.6.34-020634rc6-generic #020634rc6 SMP Fri Apr 30 10:09:34 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10900000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Tangerine
GTK+ Modules: gnomesegvhandler, canberra-gtk-module

Memory status: size: 80109568 vsize: 80109568 resident: 10874880 share: 8093696 rss: 10874880 rss_rlim: 18446744073709551615
CPU usage: start_time: 1288981883 rtime: 33 utime: 23 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/bluetooth-applet'

[Thread debugging using libthread_db enabled]
[New Thread 0xb657db70 (LWP 4211)]
0xb7796430 in __kernel_vsyscall ()

+ Trace 224530

Thread 1 (Thread 0xb689c820 (LWP 4192))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_spawn_sync
from /lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomesegvhandler.so
#5 <signal handler called>
#6 ??
from /usr/lib/libgtk-x11-2.0.so.0
#7 ??
from /usr/lib/libgtk-x11-2.0.so.0
#8 ??
from /usr/lib/libgtk-x11-2.0.so.0
#9 ??
from /usr/lib/libgtk-x11-2.0.so.0
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 ??
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_cclosure_marshal_VOID__BOXED
from /usr/lib/libgobject-2.0.so.0
#14 ??
from /usr/lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#16 ??
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#19 ??
from /usr/lib/libgtk-x11-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_widget_size_request
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 g_cclosure_marshal_VOID__BOXED
from /usr/lib/libgobject-2.0.so.0
#24 ??
from /usr/lib/libgobject-2.0.so.0
#25 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#26 ??
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_widget_size_request
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgtk-x11-2.0.so.0
#33 ??
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#36 ??
from /usr/lib/libgobject-2.0.so.0
#37 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#38 ??
from /usr/lib/libgobject-2.0.so.0
#39 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#40 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#41 gtk_container_check_resize
from /usr/lib/libgtk-x11-2.0.so.0
#42 ??
from /usr/lib/libgtk-x11-2.0.so.0
#43 ??
from /usr/lib/libgdk-x11-2.0.so.0
#44 ??
from /lib/libglib-2.0.so.0
#45 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#46 ??
from /lib/libglib-2.0.so.0
#47 g_main_loop_run
from /lib/libglib-2.0.so.0
#48 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#49 main

A debugging session is active.

	Inferior 1 [process 4192] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors ---------------------
** (gnome-session:3424): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (bug-buddy:26536): WARNING **: Couldn't load /usr/share/applications/UninstallMobilePartner.desktop: Permesso negato
** (bug-buddy:26536): WARNING **: Couldn't load /usr/share/applications/MobilePartner.desktop: Permesso negato
** (bug-buddy:26536): WARNING **: Couldn't load /etc/xdg/autostart/HuaweiAutoStart.desktop: Permesso negato
** (gnome-session:3424): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:3424): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:3424): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:3424): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:3424): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:3424): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:3424): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
** (gnome-session:3424): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged
--------------------------------------------------

Comment 1 Akhil Laddha 2010-11-06 13:08:19 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of bug 632832 ***