monitor.py crashed with DBusException in call_blocking()

Bug #441568 reported by jatin sachdeva
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
wicd (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: wicd

Error being automatically reported by apport. I am not sure what I need to enter here.
My system is an x61s, it does not boot correctly after jaunty to karmic beta upgrade. After grub, I get a blinking cursor on a black screen. I need to do a ctrl-alt-del to get to a prompt, then quickly type init 3 to prevent reboot. After this I need to remount the file system as rw and then do a sudo service dbus start, followed by sudo service hal start, sudo service gdm start. This gets me into the gui. This is where I have lots of serious issues reported by apport. Also I have no wireless working and wicd also throws up some errors again picked and reported by apport.

ProblemType: Crash
Architecture: amd64
Date: Sun Oct 4 04:37:56 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/wicd/monitor.py
InterpreterPath: /usr/bin/python2.6
Package: wicd 1.6.1-3ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python -O /usr/share/wicd/monitor.py
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_IN
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
PythonArgs: ['/usr/share/wicd/monitor.py']
SourcePackage: wicd
Title: monitor.py crashed with DBusException in call_blocking()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups:

Revision history for this message
jatin sachdeva (jatin-sachdeva) wrote :
tags: removed: need-duplicate-check
Steve Beattie (sbeattie)
information type: Private → Public
tags: added: karmic
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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