Bug 5899 - gnome-power-manager crashed in dbus
Summary: gnome-power-manager crashed in dbus
Status: RESOLVED FIXED
Alias: None
Product: dbus
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high critical
Assignee: Havoc Pennington
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-16 04:19 UTC by Kjartan Maraas
Modified: 2006-08-10 14:12 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
sanity checks (405 bytes, patch)
2006-03-17 02:30 UTC, Johan Bilien
Details | Splinter Review

Description Kjartan Maraas 2006-02-16 04:19:25 UTC
This happened when I killed nm-applet for some reason:

#0  0x00abd402 in ?? ()
#1  0x006ad803 in ?? () from /lib/libpthread.so.0
#2  0x03faa086 in libgnomeui_segv_handle (signum=11) at gnome-ui-init.c:792
#3  <signal handler called>
#4  0x00bb046c in find_name_in_info (a=0x0, b=0x8786d34) at dbus-gproxy.c:497
#5  0x00943bee in IA__g_slist_find_custom (list=0x878fac8, data=0x8786d34,
    func=0xbb0450 <find_name_in_info>) at gslist.c:382
#6  0x00bb26cc in dbus_g_proxy_manager_filter (connection=0x873e3d8,
    message=0x87d0998, user_data=0x87cac50) at dbus-gproxy.c:717
#7  0x03d024d6 in dbus_connection_dispatch (connection=0x873e3d8)
    at dbus-connection.c:3629
#8  0x00baaacd in message_queue_dispatch (source=0x873fae8, callback=0,
    user_data=0x0) at dbus-gmain.c:113
#9  0x0092c11d in IA__g_main_context_dispatch (context=0x870d420)
    at gmain.c:1916
#10 0x0092f3af in g_main_context_iterate (context=0x870d420, block=1,
    dispatch=1, self=0x86f3a18) at gmain.c:2547
#11 0x0092f759 in IA__g_main_loop_run (loop=0x8763690) at gmain.c:2751
#12 0x0804f942 in main (argc=1, argv=0x61100cd) at gpm-main.c:407
#13 0x001337a4 in __libc_start_main (main=0x804f2e0 <main>, argc=1,
    ubp_av=0xbfd8a5f4, init=0x805805c <__libc_csu_init>,
    fini=0x8058054 <__libc_csu_fini>, rtld_fini=0x8c2e50 <_dl_fini>,
    stack_end=0xbfd8a5ec) at libc-start.c:231
---Type <return> to continue, or q <return> to quit---
#14 0x0804c0d1 in _start ()
Comment 1 Johan Bilien 2006-03-17 02:30:16 UTC
Created attachment 4968 [details] [review]
sanity checks
Comment 2 Johan Bilien 2006-03-17 02:31:57 UTC
We are experiencing a very similar crash in the maemo framework:

#0  0xb74c1820 in strcmp () from /lib/tls/libc.so.6
#1  0x08153c00 in ?? ()
#2  0xb7439198 in find_name_in_info (a=0x0, b=0x0) at dbus-gproxy.c:496
#3  0xb73b394e in g_slist_find_custom () from /usr/lib/libglib-2.0.so.0
#4  0xb74397cd in dbus_g_proxy_manager_replace_name_owner (manager=0x8185440,
    name=0x81a7974 "com.nokia.osso_chess.startup",
    prev_owner=0x81a7998 ":1.33", new_owner=0x81a79a4 "") at dbus-gproxy.c:718
#5  0xb743a93e in dbus_g_proxy_manager_filter (connection=0x8086498,
    message=0x8158d00, user_data=0x8185440) at dbus-gproxy.c:1173
#6  0xb7408b47 in dbus_connection_dispatch (connection=0x8086498)
    at dbus-connection.c:3629
#7  0xb7433fcd in message_queue_dispatch (source=0x0, callback=0,
    user_data=0x0) at dbus-gmain.c:113
#8  0xb739e682 in g_main_dispatch () from /usr/lib/libglib-2.0.so.0
#9  0xb739f708 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#10 0xb739fa40 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#11 0xb739ffe3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#12 0xb783a223 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#13 0x08050420 in maemo_af_desktop_main (argc=1, argv=0xbfb0abd4)
    at maemo-af-desktop-main.c:327
#14 0x0805052b in main (argc=0, argv=0x0) at maemo-af-desktop-main.c:340

We are using the attached patch as a temporary workaround. I don't think it
solved the root of the problem though, there should not be elements in the
"names" whose data is NULL.
Comment 3 Kjartan Maraas 2006-04-24 19:32:09 UTC
Is there a chance this could be related to
https://bugs.freedesktop.org/show_bug.cgi?id=6433?
Comment 4 John (J5) Palmieri 2006-08-10 14:12:48 UTC
I belive this is fixed in the latest code.  Please reopen if it is not.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.