D-Bus version: 1.2.1 distro: Archlinux uname -a: Linux Bebop 2.6.25-ARCH #1 SMP PREEMPT Sat Jun 14 18:07:19 CEST 2008 i686 Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz GenuineIntel GNU/Linux My laptop tends to have big uptimes, and sometimes, the dbus daemon segfaults with apparently no reason. I can't provide a way to reproduce the error, because I'm not doing anything when it crashes. If I can provide further information in anyway, I'll be happy to, just ask. Programs that can influence the crash: networkmanager 0.6.6 knetworkmanager 0.2.2 glibc 2.8 /var/log/messages of the last crash (after an uptime of 5 days) Jul 3 00:34:56 Bebop NetworkManager: <info> DHCP daemon state is now 3 (renew) for interface wlan0 Jul 3 00:34:56 Bebop dhclient: bound to 192.168.10.185 -- renewal in 16486 seconds. Jul 3 05:09:42 Bebop dhclient: DHCPREQUEST on wlan0 to 192.168.10.1 port 67 Jul 3 05:09:42 Bebop dhclient: DHCPACK from 192.168.10.1 Jul 3 05:09:42 Bebop NetworkManager: <info> DHCP daemon state is now 3 (renew) for interface wlan0 Jul 3 05:09:42 Bebop dhclient: bound to 192.168.10.185 -- renewal in 19066 seconds. Jul 3 10:27:28 Bebop dhclient: DHCPREQUEST on wlan0 to 192.168.10.1 port 67 Jul 3 10:27:28 Bebop dhclient: DHCPACK from 192.168.10.1 Jul 3 10:27:28 Bebop NetworkManager: <info> DHCP daemon state is now 3 (renew) for interface wlan0 Jul 3 10:27:28 Bebop dhclient: bound to 192.168.10.185 -- renewal in 18482 seconds. Jul 3 15:35:30 Bebop dhclient: DHCPREQUEST on wlan0 to 192.168.10.1 port 67 Jul 3 15:35:30 Bebop dhclient: DHCPACK from 192.168.10.1 Jul 3 15:35:30 Bebop NetworkManager: <info> DHCP daemon state is now 3 (renew) for interface wlan0 Jul 3 15:35:31 Bebop dhclient: bound to 192.168.10.185 -- renewal in 16604 seconds. Jul 3 20:12:14 Bebop dhclient: DHCPREQUEST on wlan0 to 192.168.10.1 port 67 Jul 3 20:12:14 Bebop dhclient: DHCPACK from 192.168.10.1 Jul 3 20:12:14 Bebop NetworkManager: <info> DHCP daemon state is now 3 (renew) for interface wlan0 Jul 3 20:12:14 Bebop dhclient: bound to 192.168.10.185 -- renewal in 16617 seconds. Jul 3 20:53:55 Bebop dbus-daemon[3622]: segfault at b8c2f1f0 ip b7f264ca sp bfaa780c error 4 in libc-2.8.so[b7eb4000+13c000] Jul 3 20:53:55 Bebop NetworkManager: <WARN> nm_hal_deinit(): libhal shutdown failed - Connection is closed Jul 3 20:53:55 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:53:55 Bebop hal-ipw-killswitch-linux: error: libhal_ctx_set_dbus_connection: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Jul 3 20:53:58 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:01 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:04 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:07 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:10 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:13 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:16 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:19 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:22 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:25 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:28 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:31 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:34 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:37 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:40 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:43 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:46 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:49 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Jul 3 20:54:52 Bebop NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running!
If this happens consistently, the right way to is to attach to it with gdb and catch the crash, and get a full stack trace. See: http://live.gnome.org/GettingTraces
Does this still happen? Can you provide a stack trace?
Heh, reported on 2008; I don't even remember having reported this bug. Feel free to close it; WORKSFORME right now.
(In reply to comment #3) > Feel free to close it; WORKSFORME right now. Done.
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.