Looking in /var/crash revealed the same crash report as above, at the same time of the system freeze, but the logs don't reveal much. One thing I did notice was that most activity around the time of the crash was networking stuff; I opened KSystemLog and looked at everything around 14:12 (the time of the crash), copied it all to a .txt file, and looked for anything having to do with dbus. This is what I found:
$ cat log.txt | grep dbus
04/19/2008 02:12:32 PM kubuntu-laptop hcid[7124] Created local server at unix:abstract=/var/run/dbus-ohCoRYO1yG,guid=b01996e8fb17a4495e503a63480a3610
04/19/2008 02:12:43 PM kubuntu-laptop dhcdbd message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
04/19/2008 02:12:59 PM kubuntu-laptop dhcdbd message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.domain_name
04/19/2008 02:12:59 PM kubuntu-laptop dhcdbd message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.host_name
04/19/2008 02:12:59 PM kubuntu-laptop dhcdbd message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.interface_mtu
04/19/2008 02:12:59 PM kubuntu-laptop dhcdbd message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_domain
04/19/2008 02:12:59 PM kubuntu-laptop dhcdbd message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_servers
Is it possible something funny's going on with NetworkManager?
It just happened again...
Looking in /var/crash revealed the same crash report as above, at the same time of the system freeze, but the logs don't reveal much. One thing I did notice was that most activity around the time of the crash was networking stuff; I opened KSystemLog and looked at everything around 14:12 (the time of the crash), copied it all to a .txt file, and looked for anything having to do with dbus. This is what I found:
$ ls -l /var/crash desktop- effects- kde4.1000. crash python2. 5.1000. crash pychess. 1000.crash virtualbox_ VirtualBox. 1000.crash
total 164
-rw------- 1 kubun2 kubun2 38554 2008-04-19 01:33 _usr_bin_
-rw------- 1 kubun2 kubun2 37589 2008-04-19 14:12 _usr_bin_
-rw------- 1 kubun2 kubun2 54946 2008-04-12 17:53 _usr_games_
-rw------- 1 kubun2 kubun2 27721 2008-04-11 07:09 _usr_lib_
$ cat log.txt | grep dbus /var/run/ dbus-ohCoRYO1yG ,guid=b01996e8f b17a4495e503a63 480a3610 dhcp/wlan0 for sub-path wlan0.dbus. get.reason dhcp/wlan0 for sub-path wlan0.dbus. get.domain_ name dhcp/wlan0 for sub-path wlan0.dbus. get.host_ name dhcp/wlan0 for sub-path wlan0.dbus. get.interface_ mtu dhcp/wlan0 for sub-path wlan0.dbus. get.nis_ domain dhcp/wlan0 for sub-path wlan0.dbus. get.nis_ servers
04/19/2008 02:12:32 PM kubuntu-laptop hcid[7124] Created local server at unix:abstract=
04/19/2008 02:12:43 PM kubuntu-laptop dhcdbd message_handler: message handler not found under /com/redhat/
04/19/2008 02:12:59 PM kubuntu-laptop dhcdbd message_handler: message handler not found under /com/redhat/
04/19/2008 02:12:59 PM kubuntu-laptop dhcdbd message_handler: message handler not found under /com/redhat/
04/19/2008 02:12:59 PM kubuntu-laptop dhcdbd message_handler: message handler not found under /com/redhat/
04/19/2008 02:12:59 PM kubuntu-laptop dhcdbd message_handler: message handler not found under /com/redhat/
04/19/2008 02:12:59 PM kubuntu-laptop dhcdbd message_handler: message handler not found under /com/redhat/
Is it possible something funny's going on with NetworkManager?