I'm sorry - I no longer even have that system
On 17 March 2012 15:37, Robert Schroll rschr...@gmail.com wrote:
So, against what should this bug be filed? GTK/Qt? Vte? Python? All
of them? Something else?
--
You received this bug notification because you are subscribed to a
duplicate
I reported this back in August of '09.
While I commend the dedication to fixing it, don't prod along on my
account - I just kept trying successively newer versions of Ubuntu as
they came out, and got more powerful hardware as well... and the
problems eventually stopped.
Don't ask me which
This was not a hardware specific problem. It may have been a hardware
_class_ problem where somebody ASS-U-MEd something would get done in a
certain amount of time or some other resource level, but the duplicate
count is lengthy. It appears to cover most motherboards for most
brands.
I have no
So, against what should this bug be filed? GTK/Qt? Vte? Python? All
of them? Something else?
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to python-qt4 in Ubuntu.
https://bugs.launchpad.net/bugs/419501
Title:
apport-kde assert
As per my previous message, these types of errors are generally client
problems.
This past week apport got a fix for an xcb threading assert it hits;
possibly this issue is resolved by that.
** Changed in: libxcb (Ubuntu)
Status: Triaged = Won't Fix
** Changed in: libxcb (Ubuntu Lucid)
(As of natty, test code still produces the warning, so setting status to
Triaged. Upstream seems to feel the issue needs to be resolved by
modifying calling clients to limit how multi-threaded processes utilize
the XCB event queue.)
** Changed in: libxcb (Ubuntu)
Status: Confirmed =
I am facing this bug with Exaile 0.3.2 in Maverick.
By the way, you might consider it as duplicate :
https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/510225
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) -
Sorry for double-posting, I meant
https://bugs.launchpad.net/exaile/+bug/596227
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received
** Changed in: libxcb (Ubuntu)
Status: Invalid = Confirmed
** Changed in: python-qt4 (Ubuntu)
Status: Confirmed = Invalid
** Changed in: python-qt4 (Ubuntu Lucid)
Status: New = Invalid
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
This has only ever effected PyQt applications. (though I'm not really
convinced it's a pyqt bug)
** Package changed: qt4-x11 (Ubuntu) = python-qt4 (Ubuntu)
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long)
Not only. This bug affects GTK applications too.
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received this bug notification because
From what I can tell the python program in comment 31 appears to open an
X connection, fork, and then use that X connection from both the child
and the parent. That can't possibly work.
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long)
On 06/30/2010 05:14 AM, Julien Cristau wrote:
From what I can tell the python program in comment 31 appears to open an
X connection, fork, and then use that X connection from both the child
and the parent. That can't possibly work.
And yet it does, in Ubuntu Karmic.
All that the child
** Branch linked: lp:ubuntu/python-gasp
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received this bug notification because you are a
Both would be bugs in the application.
I would like to point out my test case again (comment 31), a simple
pyGTK app that displays the same problem. While it may have a bug
(please point it out if you see it!), I find that unlikely given how
short and simple it is, and because it works
Jamey Sharp, an X.org upstream, has taken a look at this and said:
All those I could find look like one of two cases: Either the app
called Xlib from multiple threads without calling XInitThreads first; or
it opened a Display, fork()ed, and used the Display from both processes.
Both would be bugs
The PPA definitely fixes the “ico -threads 10” testcase for me locally.
I'm not sure about the python testcase; I can't see anything immediately
wrong with it, but I recall an unrelated bug in Lucid with python, glib
and forking which which makes me slightly suspicious of it.
--
apport-kde
OK, I'm not having any problems with ico -threads 10 with the PPA.
BUT: Is there any reason to believe that the problems with ico are the
same as this bug? As far as I can tell, the problem here is that Python
programs using X which execute a fork reliably throw a specific
assertion error.
Chris Halse Rogers wrote:
There has recently been work done upstream to fix these sort of bugs.
I've pushed some testing packages incorporating these fixes to
https://edge.launchpad.net/~raof/+archive/aubergine/+packages.
I've tried installing packages from this PPA, and the test case still
There has recently been work done upstream to fix these sort of bugs.
I've pushed some testing packages incorporating these fixes to
https://edge.launchpad.net/~raof/+archive/aubergine/+packages.
These changes look pretty extensive, so it might not be possible to push
an SRU fixing this, but it
** Branch linked: lp:debian/sid/python-gasp
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received this bug notification because you
** Branch linked: lp:~lfaraone/ubuntu/lucid/python-gasp/lp419501
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received this bug
unsubscribe
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received this bug notification because you are a member of Ubuntu
Bugs,
** Branch linked: lp:ubuntu/python-gasp
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received this bug notification because you are a
This bug was fixed in the package python-gasp - 0.3.3-0ubuntu1
---
python-gasp (0.3.3-0ubuntu1) lucid; urgency=low
* New upstream release. (LP: #419501)
-- Luke Faraone l...@faraone.cc Fri, 12 Mar 2010 09:19:17 -0500
** Changed in: python-gasp (Ubuntu Lucid)
Status: In
** Description changed:
Binary package hint: apport
+
+ TEST CASE:
+ https://bugs.launchpad.net/ubuntu/+source/python-gasp/+bug/419501/comments/31
+
Description: Ubuntu karmic (development branch)
Release: 9.10
ProblemType: Crash
Architecture: amd64
AssertionMessage:
** Changed in: gasp-core
Status: Fix Committed = Fix Released
** Changed in: gasp-core
Assignee: (unassigned) = Luke Faraone (lfaraone)
** Changed in: python-gasp (Ubuntu Lucid)
Assignee: (unassigned) = Luke Faraone (lfaraone)
--
apport-kde assert failure: python:
The testcase still fails on the daily ISO.
** Changed in: libxcb (Ubuntu Lucid)
Status: Incomplete = Confirmed
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
** Also affects: python-gasp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-gasp (Ubuntu Lucid)
Status: New = In Progress
** Changed in: python-gasp (Ubuntu Lucid)
Importance: Undecided = Low
** Changed in: gasp-core
Status: Confirmed = Fix Committed
has anyone tried to reproduce this on lucid?
** Changed in: libxcb (Ubuntu Lucid)
Status: Confirmed = Incomplete
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
On lucid I have the problem with any program I am stopping with an click
on the x. Seems that more programs are sharing the seem process and than
have an collision.
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) -
has anyone tried to reproduce this on lucid?
I just tried the test case and got the same error as before. (Although
now, it's caught by apport, so I have to wait for that think before I
can see the problem. Progress!) This is on a VM image of lucid that is
about 2 weeks old. libxcb isn't
Just remember, the point of spring break is to TAKE A BREAK.
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received this bug
Simple test case for many xcb-based libX11 bugs:
ico -threads 10
You will likely get a deadlock, _XAllocID: Assertion `ret != inval_id'
failed. or the error mentioned here.
Locally we have problems with any X program that uses multi-threading
since the switch to libxcb X11. Sometimes one or two
Hey,
Sorry I haven't had any free time to work on this and it doesn't look
like I'm going to have any time until spring break. That's only a week and
a half away and I should be able to spend a lot of time on this then. I'm
not sure if I'll be back in Arlington or not, but I should have
Pledging and partying are a lot more important. You are only young
once!
On Tuesday 23 February 2010 07:32:34 pm jboisture wrote:
Hey,
Sorry I haven't had any free time to work on this and it doesn't look
like I'm going to have any time until spring break. That's only a week and
a
** Also affects: libxcb (Ubuntu Lucid)
Importance: High
Status: Confirmed
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You
The nominations may not be appropriate. Please investigate and fix as
appropriate.
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You
I don't know if this helps or not, but I've found a work-around for my
test case. The trick is to hold off on importing gtk and vte until
after the child process forks off. I'm guessing that the error is due
to two separate processes holding the same objects. (This affects both
gtk and vte, but
** Changed in: libxcb (Ubuntu)
Assignee: Ubuntu BugSquad (bugsquad) = (unassigned)
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You
I just submitted bug #518269, in which this same error is seen in a
PyGTK application. I don't know if it is the same bug as this one. But
I did manage to put together a rather simple test case. If these turn
out to be the same bug, please mark mine as a duplicate.
--
apport-kde assert
** Changed in: libxcb (Ubuntu)
Assignee: (unassigned) = Ubuntu BugSquad (bugsquad)
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You
Here is the test case that I originally posted in #518269. It is a
PyGTK app with a vte Terminal. It uses forkpty() to create a child
process inside the terminal. That child process dies with this
assertion error when it reaches the raw_input() statement. (Actually,
it seems to need some
** Changed in: libxcb (Ubuntu)
Status: Incomplete = Confirmed
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received this bug
** Attachment added: crash report with more trace info
http://launchpadlibrarian.net/37977510/_usr_share_apport_apport-kde.1000.crash.gz
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) =
** Changed in: gasp-core
Status: New = Confirmed
** Changed in: gasp-core
Importance: Undecided = Critical
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
you need to install libqt4-dbg and get a new backtrace, the current one
is not complete enough.
** Changed in: libxcb (Ubuntu)
Status: Triaged = Incomplete
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) -
bump
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello everybody,
it is hard to give the root cause for this bug.
It appears quite frequently, e.g. after rebooting.
So I suspect it has to do with KDE/plasma startup.
The Device (USB Stick) notification mechanism could be involved as well.
Note: My Kubuntu system was upgraded - not freshly
In the light of that opinion, I'll toss in that plasma frequently
crashes on my system with an error that says something along the lines
of we were being asked to do too much and we lost track of what we
were trying to do, so here's a pair of lips going *plblblblblblblb*.
Also, I thought it was
On Sun, Nov 8, 2009 at 16:18, cparg cp...@gmx.de wrote:
it is hard to give the root cause for this bug.
The root cause for the bug is probably not any hardware issue. This is a bug
that has a very simple testcase and affects multiple applications, and is a
bug in libxcb or one of its
Bryce, Jeff Elkner escalated this bug to me and I think it's worth a
closer look given the widespread impact. Can you comment on the likely
cause? Seems easy to reproduce.
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long)
I have no further information. I have recently updated to everything current
and it appears the work around now is for Apport to absolutely refuse to file
any bug unless you click on Yes you can provide step by step instructions
for reproduction. I have had 9 such crashes in less than 24
That's exactly the string of events that happened to me, minus the
every time I resume bit. It would happen to me for no patterned
reason.
Eric
On Sun, Nov 1, 2009 at 3:45 PM, skierpage i...@skierpage.com wrote:
Me too, Kubuntu Karmic 9.10 on amd64, same as Patrick Dawkins. I get
two or
Me too, Kubuntu Karmic 9.10 on amd64, same as Patrick Dawkins. I get
two or three apport alerts every time I resume from standby that all
request sudo, then I get a bunch more KDESudo alerts, then I kill most
of them because my system is reduced to a crawl with all the Collecting
data windows,
This happened to me in Kubuntu Karmic 9.10 on amd64 after reporting two
other crashes
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You
This bug effects gasp on Fedora 12 as well. Also, it appears to involve
changes other than just libxcb. When libxcd 1.2-4 (the one from Fedora
11, on which gasp runs without problems), is installed on Fedora 12, the
same problem occurs.
--
apport-kde assert failure: python:
I tried to file a bug report on a fatal error in karmic (both amd64 and
i386) for the package python-gasp. The reply came that it is a
duplicate of this bug. To reproduce it:
1. sudo apt-get install python-gasp (from universe)
2. from a python shell:
from gasp import *
begin_graphics()
This
Also have the same problem on Karmic - amd64, but I can give no further
information.
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You
Is it possible that this only affects me when attempting to checkout a
subversion repository in netbeans?
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
I have this problem on amd64.
It occured while a submitting a bug with no debug information (no stacktrace)
on kwin.
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
** Tags added: karmic
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received this bug notification because you are a member of Ubuntu
same problem on i386
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received this bug notification because you are a member of Ubuntu
I am also getting several apport-kde crashes when something else
crashes, the latest one with the message of the title. most make them
unable to send reports in about the crash.
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long)
This is not related to bug 405378. This crash occurs in various other
programs.
** This bug is no longer a duplicate of bug 405378
[karmic] in KDE apport does not open the browser to report a bug
** Package changed: apport (Ubuntu) = libxcb (Ubuntu)
** Changed in: libxcb (Ubuntu)
This bug is also affecting other packages, such as python-gasp (in bug 409001).
The reproduction steps in there are simple, run the following in a python
interpreter:
import gasp
gasp.begin_graphics()
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion
*** This bug is a duplicate of bug 405378 ***
https://bugs.launchpad.net/bugs/405378
Yuriy, indeed, seems that these two are duplicates.
** This bug has been marked a duplicate of bug 405378
[karmic] in KDE apport does not open the browser to report a bug
--
apport-kde assert failure:
Could be related to bug 405378
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received this bug notification because you are a member
** Visibility changed to: Public
** Changed in: apport (Ubuntu)
Status: New = Confirmed
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
This hardly looks like a bug in apport itself, more likely in pyqt or
libxcb. Anyway, do you have a recipe how to reproduce this? What did you
do exactly and how far did you get?
** Changed in: apport (Ubuntu)
Status: Confirmed = Incomplete
--
apport-kde assert failure: python:
This is a daily occurance.
Firefox crashed, apport tried to report the bug and it crashed itself,
leading to around 30 some odd apport-kde instances running. Each
instance consumes 2.6 or 2.7% of 1.5G of ram.
It normally happens about twice a day, though today it's crashed four
times this
This happened to me when some updates were running. Not sure if apport-
kde was among them. Suddenly it apport-kde asked for password twice, at
same time. Following that it got this crash.
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long)
I didn't do anything other than tell KPackageKit to install the 200+ updates
which were waiting (and took all (^)(*)(*ing day to pull down) Part way
through it started gagging. I then used Synaptic to fix the packages
KPackageKit broke (none were broke before the updates started) and apply
** Changed in: apport (Ubuntu)
Status: Incomplete = Confirmed
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy-last_request_read) - (long) (dpy-request)) = 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received this bug
74 matches
Mail list logo
