Ubuntu
gwibber package

gwibber crashed with error in connect()

Bug #532460 reported by Sascha Grossenbacher on 2010-03-05

This bug report is a duplicate of: Bug #522538: gwibber-service crashed with error in connect(). Edit Remove

This bug affects 12 people

Affects		Status	Importance	Assigned to	Milestone
	gwibber (Ubuntu)	New	Medium	Unassigned

Bug Description

Binary package hint: gwibber

Just popped up, wasn't doing anything with gwibber

ProblemType: Crash
Architecture: amd64
Date: Fri Mar 5 08:50:13 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: gwibber 2.29.90.1-0ubuntu2
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
LANGUAGE=de_CH:de
PATH=(custom, user)
LANG=de_CH.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with error in connect()
Uname: Linux 2.6.32-15-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare scanner tape video www-data

Tags:

Revision history for this message

Sascha Grossenbacher (berdir) wrote on 2010-03-05:

Dependencies.txt Edit (6.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (83.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (837 bytes, text/plain; charset="utf-8")
Traceback.txt Edit (1.6 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2010-03-05

tags:

removed: need-duplicate-check

Pedro Villavicencio (pedro) on 2010-03-18

visibility:

private → public

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2010-03-18:

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

Alwin Garside (yogarine) wrote on 2010-03-18:

Just also got this while starting up Gwibber 2.29.92.1-0ubuntu1

Pedro Villavicencio (pedro) on 2010-03-23

Changed in gwibber (Ubuntu):
status:	Incomplete → New

Revision history for this message

iPeel (ubuntu-peely) wrote on 2010-03-25:

I got this after a resume on a laptop connected through wireless. I assume because the wireless link had not restored at this point.

Additionally, the crash during resume resulted in my desktop being visible instead of locked. Movement of the mouse brought be to the unlock screen though.