gwibber crashed with OSError in <module>()

Bug #531170 reported by yocmoi82
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gwibber

this appears when I try to launch gwibber the first time

ProblemType: Crash
Architecture: amd64
Date: Wed Mar 3 08:39:16 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100212)
InterpreterPath: /usr/bin/python2.6
Package: gwibber 2.29.90.1-0ubuntu2
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.utf8
ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with OSError in <module>()
Uname: Linux 2.6.32-15-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
yocmoi82 (yoann-berriet) wrote :
tags: removed: need-duplicate-check
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, is this still an issue with latest Gwibber on Lucid?

Changed in gwibber (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Shane (shane-blether) wrote :

On my freshly upgraded system (from Karmic) I could not launch gwibber.

Typing gwibber at the command line showed me:
OSError: [Errno 13] Permission denied: '/home/XXXX/.cache/gwibber'

I don't know how, or for how long the ownership of my .cache was wrong,
but now that I've fixed it I can launch gwibber.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

could you paste the output of 'ls -las /home/user/.cache/gwibber' ? did you run gwibber as a root? if so that's probably why you're having permissions issues there.

Revision history for this message
Victor Vargas (kamus) wrote :

@yocmoi82, any news about this issue? have you tried to run latest command that pedro told you (running latest gwibber release)? Thanks!

Revision history for this message
Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem. Please reopen it if you encounter that this issue is still occurring in latest Ubuntu Lucid version. To reopen the bug report you can click under the Status column, and change the Status back to "New". Thanks again!

Changed in gwibber (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.