Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 306300 Details for
Bug 447299
bluetooth-properties crashes when trying to pair with bluetooth mouse
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
Backtrace of bluetooth-properties crash
bluetooth-properties-backtrace.txt (text/plain), 4.55 KB, created by
Dawid Lorenz
on 2008-05-21 18:49:04 UTC
(
hide
)
Description:
Backtrace of bluetooth-properties crash
Filename:
MIME Type:
Creator:
Dawid Lorenz
Created:
2008-05-21 18:49:04 UTC
Size:
4.55 KB
patch
obsolete
>[evad@D620 ~]$ gdb /usr/bin/bluetooth-properties >GNU gdb Fedora (6.8-5.fc9) >Copyright (C) 2008 Free Software Foundation, Inc. >License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> >This is free software: you are free to change and redistribute it. >There is NO WARRANTY, to the extent permitted by law. Type "show copying" >and "show warranty" for details. >This GDB was configured as "i386-redhat-linux-gnu"... >(no debugging symbols found) >Missing separate debuginfos, use: debuginfo-install bluez-gnome.i386 >(gdb) run >Starting program: /usr/bin/bluetooth-properties >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >[Thread debugging using libthread_db enabled] >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >[New Thread 0xb7f54710 (LWP 4375)] >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >(no debugging symbols found) >Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkTreeView::odd-row-color' of type `GdkColor' from rc file value "((GString*) 0x912ff00)" of type `GString' >process 4375: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074. >This is normally a bug in some application using the D-Bus library. > D-Bus not built with -rdynamic so unable to print a backtrace > >Program received signal SIGABRT, Aborted. >0x00110416 in __kernel_vsyscall () >(gdb) thread apply all bt > >Thread 1 (Thread 0xb7f54710 (LWP 4375)): >#0 0x00110416 in __kernel_vsyscall () >#1 0x008d1660 in raise () from /lib/libc.so.6 >#2 0x008d3028 in abort () from /lib/libc.so.6 >#3 0x007a8435 in ?? () from /lib/libdbus-1.so.3 >#4 0x007a3fc9 in ?? () from /lib/libdbus-1.so.3 >#5 0x00797b9e in dbus_message_new_method_call () from /lib/libdbus-1.so.3 >#6 0x007f837d in ?? () from /usr/lib/libdbus-glib-1.so.2 >#7 0x007f8726 in ?? () from /usr/lib/libdbus-glib-1.so.2 >#8 0x007f921a in dbus_g_proxy_call () from /usr/lib/libdbus-glib-1.so.2 >#9 0x08053e43 in g_free () >#10 0x007f733f in ?? () from /usr/lib/libdbus-glib-1.so.2 >#11 0x00799b61 in ?? () from /lib/libdbus-1.so.3 >#12 0x00789006 in ?? () from /lib/libdbus-1.so.3 >#13 0x0078ac0c in dbus_connection_dispatch () from /lib/libdbus-1.so.3 >#14 0x007f2fbd in ?? () from /usr/lib/libdbus-glib-1.so.2 >#15 0x00aca098 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 >#16 0x00acd743 in ?? () from /lib/libglib-2.0.so.0 >#17 0x00acdc62 in g_main_loop_run () from /lib/libglib-2.0.so.0 >#18 0x00213439 in gtk_dialog_run () from /usr/lib/libgtk-x11-2.0.so.0 >#19 0x0804cd80 in g_free () >#20 0x08053c12 in g_free () >#21 0x00b988b4 in g_cclosure_marshal_VOID__VOID () from /lib/libgobject-2.0.so.0 >#22 0x00b8b12b in g_closure_invoke () from /lib/libgobject-2.0.so.0 >#23 0x00b9f995 in ?? () from /lib/libgobject-2.0.so.0 >#24 0x00ba0ece in g_signal_emit_valist () from /lib/libgobject-2.0.so.0 >#25 0x00ba1336 in g_signal_emit () from /lib/libgobject-2.0.so.0 >#26 0x001b1961 in gtk_button_clicked () from /usr/lib/libgtk-x11-2.0.so.0 >#27 0x001b2dc2 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 >#28 0x091250c0 in ?? () >#29 0x001b2d7e in ?? () from /usr/lib/libgtk-x11-2.0.so.0 >#30 0xbf86f858 in ?? () >#31 0x00b988b4 in g_cclosure_marshal_VOID__VOID () from /lib/libgobject-2.0.so.0 >Backtrace stopped: frame did not save the PC >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 447299
:
305933
| 306300