crash on startup

Bug #66595 reported by Brian J. Murrell
96
Affects Status Importance Assigned to Milestone
dbus-glib (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

My desktop session crashed out and when I came back in rhythmbox crashed on restart. I will attach the crash report here. It sucks that you can't attach a crash report to a new bug. :-(

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. Are you other applications working normally? Did you have some dbus issue? Does restarting the session fixes the issue?

debug backtrace generated from the crash:

#0 0xb7b386cc in dbus_g_method_return_error (context=0x0, error=0x8988bbc) at dbus-gobject.c:1996
1996 {
(gdb) bt
#0 0xb7b386cc in dbus_g_method_return_error (context=0x0, error=0x8988bbc) at dbus-gobject.c:1996
#1 0xb6f7a53e in IA__g_slist_find_custom (list=0x87d5e88, data=0x8988bbc, func=0xb7b386b0 <dbus_g_method_return+782>)
    at gslist.c:389
#2 0xb7b3cacc in dbus_g_proxy_set_interface (proxy=0x822fe68, interface_name=0x8232610 "\001") at dbus-gproxy.c:2036
#3 0xb7ae28ce in dbus_connection_dispatch () from /usr/lib/libdbus-1.so.3
#4 0xb7b3451d in watch_toggled (watch=0x82318a0, data=0x0) at dbus-gmain.c:455
#5 0xb6f62802 in IA__g_main_context_dispatch (context=0x820c080) at gmain.c:2045
#6 0xb6f657df in g_main_context_iterate (context=0x820c080, block=1, dispatch=1, self=0x81631c8) at gmain.c:2677
#7 0xb6f65b89 in IA__g_main_loop_run (loop=0x8656d28) at gmain.c:2881
#8 0xb7698574 in IA__gtk_main () at gtkmain.c:1024
#9 0x0806bccf in main ()

The crash happens to dbus-glib, reassigning

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :

No other issues that I am aware of at the moment.

Changed in dbus-glib:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

backtrace from apport-retrace with libdbus debug too

 #0 0xb7b386cc in dbus_g_method_return_error (context=0x0, error=0x8988bbc) at dbus-gobject.c:1996
        reply = (DBusMessage *) 0x896dec0
 #1 0xb6f7a53e in IA__g_slist_find_custom (list=0x87d5e88, data=0x8988bbc, func=0xb7b386b0 <dbus_g_method_return+782>)
     at gslist.c:389
        __PRETTY_FUNCTION__ = "IA__g_slist_find_custom"
 #2 0xb7b3cacc in dbus_g_proxy_set_interface (proxy=0x822fe68, interface_name=0x8232610 "\001") at dbus-gproxy.c:2036
        priv = (DBusGProxyPrivate *) 0x0
 #3 0xb7ae28ce in dbus_connection_dispatch (connection=0x87d5e88) at dbus-connection.c:3779
        filter = (DBusMessageFilter *) 0x8d13e3e
        next = (DBusList *) 0x8988bd4
        message = (DBusMessage *) 0x8232610
        link = <value optimized out>
        filter_list_copy = (DBusList *) 0x822f930
        message_link = (DBusList *) 0x8232908
        result = DBUS_HANDLER_RESULT_NOT_YET_HANDLED
        status = <value optimized out>
        __FUNCTION__ = "dbus_connection_dispatch"
 #4 0xb7b3451d in watch_toggled (watch=0x82318a0, data=0x0) at dbus-gmain.c:455
 No locals.
 #5 0xb6f62802 in IA__g_main_context_dispatch (context=0x820c080) at gmain.c:2045
 No locals.
 #6 0xb6f657df in g_main_context_iterate (context=0x820c080, block=1, dispatch=1, self=0x81631c8) at gmain.c:2677
        got_ownership = <value optimized out>
        max_priority = 0
        timeout = 0
        some_ready = 1
        nfds = <value optimized out>
        allocated_nfds = <value optimized out>
        fds = (GPollFD *) 0x8c9e640
        __PRETTY_FUNCTION__ = "g_main_context_iterate"
 #7 0xb6f65b89 in IA__g_main_loop_run (loop=0x8656d28) at gmain.c:2881
        got_ownership = -1212771360
        self = (GThread *) 0x81631c8
        __PRETTY_FUNCTION__ = "IA__g_main_loop_run"

Revision history for this message
Sebastian Dröge (slomo) wrote :

This should be fixed by dbus-glib 0.72-0ubuntu2 which was uploaded some seconds ago...

Changed in dbus-glib:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.