gwibber-service crashed with ImportError in __main__: No module named gwibber.microblog.util

Bug #741540 reported by felix.montanez@hotmail.com
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gwibber

tried to do partial upgrade. computer froze so i did a hard reboot..opened in recovery mode and selected repair package. after done, did sudo reboot and gave error as computer was coming up.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gwibber-service 2.91.92-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.38-generic-pae 2.6.38
Uname: Linux 2.6.38-7-generic-pae i686
Architecture: i386
Date: Thu Mar 24 01:38:49 2011
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gwibber-service']
SourcePackage: gwibber
Title: gwibber-service crashed with ImportError in __main__: No module named gwibber.microblog.util
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/gwibber-service", line 33, in <module>
     from gwibber.microblog.util import log
 ImportError: No module named gwibber.microblog.util
UpgradeStatus: Upgraded to natty on 2011-03-24 (0 days ago)
UserGroups: adm admin audio cdrom dialout floppy fuse lpadmin netdev plugdev sambashare tape vboxusers video

Revision history for this message
felix.montanez@hotmail.com (felix-montanez) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #629492, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
visibility: private → public
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.