gwibber-daemon assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.

[Miguel Ruiz]

Binary package hint: gwibber

I'm using Karmic up to date and gwibber suddenly crashed.

Cheers!

ProblemType: Crash
Architecture: i386
AssertionMessage: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
CrashCounter: 1
Date: Sun Sep 27 15:52:26 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gwibber-daemon
InterpreterPath: /usr/bin/python2.6
Package: gwibber 2.0.0~bzr449-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-daemon
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
Signal: 6
SourcePackage: gwibber
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 __assert_fail () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libX11.so.6
Title: gwibber-daemon assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:__kernel_vsyscall ()
*__GI_raise (sig=6)
*__GI_abort () at abort.c:92
*__GI___assert_fail (
process_responses (dpy=0x8589638,

[Alexander Sack (asac)]

feels a bit odd to me why the daemon would process any Xevents

[Omer Akram (om26er)]

Gwibber-daemon crashed twice in an hour but after I install 2.29.1 gwibber-daemon never crashed. Does any one face this issue with gwibber 2.29.xx?

[Victor Vargas (kamus)]

I am not able to reproduce this issue using gwibber 2.29.91~bzr630 (daily ppa version) under Karmic. @mruiz please can you upgrade your gwibber version using daily version from https://launchpad.net/~gwibber-daily/+archive/ppa and check if this problem is still affecting you? Thanks!

[Christoph Korn (c-korn)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

[Victor Vargas (kamus)]

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 or even better if you can check in latest Ubuntu version. To reopen the bug report you can click under the Status column, and change the Status back to "New". Thanks again!