python crashes and completely freezes PC upon startup

Bug #219024 reported by integr8e
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: python

I had just rebooted my system only to have it completely freeze on me; I couldn't switch to a shell and Alt+SysRq+RSEIUB didn't do anything. After rebooting manually, I checked /var/crash and /var/log for details, and only found a crash report in /var/crash (I may have missed something in the logs, though). It has been attached; let me know if there's anything else I need to do.

Revision history for this message
integr8e (integr8e) wrote :
Revision history for this message
integr8e (integr8e) wrote :

I might should mention I'm currently running the 64-bit Kubuntu 8.04 beta on a Gateway NX860XL laptop (sorry about that).

Revision history for this message
Andreas Wenning (andreas-wenning) wrote :

That crash has nothing to do with the lock-up of your computer, sorry.

It is probably because the dbus has been restarted, that you received the above crash. I don't know if a dbus restarting can cause your computer to freeze (have never heard about that it could); but in any case you should try to look further at your logfiles and see if you can find the cause there.

Changed in kde-guidance:
status: New → Invalid
status: Invalid → Incomplete
Revision history for this message
integr8e (integr8e) wrote :

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
total 164
-rw------- 1 kubun2 kubun2 38554 2008-04-19 01:33 _usr_bin_desktop-effects-kde4.1000.crash
-rw------- 1 kubun2 kubun2 37589 2008-04-19 14:12 _usr_bin_python2.5.1000.crash
-rw------- 1 kubun2 kubun2 54946 2008-04-12 17:53 _usr_games_pychess.1000.crash
-rw------- 1 kubun2 kubun2 27721 2008-04-11 07:09 _usr_lib_virtualbox_VirtualBox.1000.crash

$ 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?

Revision history for this message
integr8e (integr8e) wrote :

Here's something kinda' interesting from my syslog (please bear with me, I'm still pretty new at this):

Apr 19 14:12:59 kubuntu-laptop NetworkManager: <info> DHCP daemon state is now 4 (reboot) for interface wlan0
Apr 19 14:12:59 kubuntu-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Apr 19 14:12:59 kubuntu-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Apr 19 14:12:59 kubuntu-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.host_name
Apr 19 14:12:59 kubuntu-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.domain_name
Apr 19 14:12:59 kubuntu-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_domain
Apr 19 14:12:59 kubuntu-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_servers
Apr 19 14:12:59 kubuntu-laptop NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon:
Apr 19 14:12:59 kubuntu-laptop NetworkManager: <info> address 10.0.0.6
Apr 19 14:12:59 kubuntu-laptop NetworkManager: <info> netmask 255.255.255.0
Apr 19 14:12:59 kubuntu-laptop NetworkManager: <info> broadcast 10.0.0.255
Apr 19 14:12:59 kubuntu-laptop NetworkManager: <info> gateway 10.0.0.1
Apr 19 14:12:59 kubuntu-laptop NetworkManager: <info> nameserver 10.0.0.1
Apr 19 14:12:59 kubuntu-laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.interface_mtu
Apr 19 14:12:59 kubuntu-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Apr 19 14:12:59 kubuntu-laptop NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Apr 19 14:12:59 kubuntu-laptop NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... $ ls -l /var/crash
total 164
-rw------- 1 kubun2 kubun2 38554 2008-04-19 01:33 _usr_bin_desktop-effects-kde4.1000.crash
-rw------- 1 kubun2 kubun2 37589 2008-04-19 14:12 _usr_bin_python2.5.1000.crash
-rw------- 1 kubun2 kubun2 54946 2008-04-12 17:53 _usr_games_pychess.1000.crash
-rw------- 1 kubun2 kubun2 27721 2008-04-11 07:09 _usr_lib_virtualbox_VirtualBox.1000.crash

Revision history for this message
Jayson Rowe (jayson.rowe) wrote :

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

Revision history for this message
Ralph Janke (txwikinger) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Monkey (monkey-libre) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubuntu:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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