gwibber crashed with signal 5 in _XError()

Bug #397710 reported by Billy
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gwibber

 Ubuntu karmic (development branch)
gwibber:
  Installed: 1.2.0~bzr346-0ubuntu1
  Candidate: 1.2.0~bzr346-0ubuntu1
  Version table:
 *** 1.2.0~bzr346-0ubuntu1 0
Gwibber keeps crashing maybe like 5 or more times a day

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Jul 10 02:13:19 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: wl
Package: gwibber 1.2.0~bzr346-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-2.16-generic
Signal: 5
SourcePackage: gwibber
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XEventsQueued () from /usr/lib/libX11.so.6
 XPending () from /usr/lib/libX11.so.6
Tags: ubuntu-unr
Title: gwibber crashed with signal 5 in _XError()
Uname: Linux 2.6.31-2-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev pulse sambashare

Revision history for this message
Billy (catharcyst) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Victor Vargas (kamus) wrote :

Can you try to reproduce this issue in latest version of gwibber? Thanks!

Changed in gwibber (Ubuntu):
status: New → Incomplete
Victor Vargas (kamus)
Changed in gwibber (Ubuntu):
importance: Undecided → Medium
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, as described in the previous comments. 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 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.