Re: [Bug 419501] Re: apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
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 change solved it, as most every hardware upgrade was accompanied by a fresh install, so it could have been anything. For what it's worth, I think the hardware I had installed in '09 was unstable. I have the motherboard in a box if anyone wants it, I'm not doing anything with it... Dennis On Sun, Mar 18, 2012 at 8:31 AM, passogiau <419...@bugs.launchpad.net> wrote: > I'm sorry - I no longer even have that system > > On 17 March 2012 15:37, Robert Schroll 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 bug report (455029). >> https://bugs.launchpad.net/bugs/419501 >> >> Title: >> apport-kde assert failure: python: ../../src/xcb_io.c:242: >> process_responses: Assertion `(((long) (dpy->last_request_read) - >> (long) (dpy->request)) <= 0)' failed. >> >> Status in GASP Core Code: >> Fix Released >> Status in “libxcb” package in Ubuntu: >> Won't Fix >> Status in “python-gasp” package in Ubuntu: >> Fix Released >> Status in “python-qt4” package in Ubuntu: >> Invalid >> Status in “libxcb” source package in Lucid: >> Won't Fix >> Status in “python-gasp” source package in Lucid: >> Fix Released >> Status in “python-qt4” source package in Lucid: >> Invalid >> >> Bug description: >> 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: python: ../../src/xcb_io.c:242: process_responses: >> Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= >> 0)' failed. >> CrashCounter: 1 >> Date: Wed Aug 26 16:14:40 2009 >> DistroRelease: Ubuntu 9.10 >> ExecutablePath: /usr/share/apport/apport-kde >> InterpreterPath: /usr/bin/python2.6 >> NonfreeKernelModules: nvidia >> Package: apport-kde 1.8-0ubuntu1 >> PackageArchitecture: all >> ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde >> ProcEnviron: >> PATH=(custom, no user) >> LANG=en_US.UTF-8 >> LANGUAGE= >> SHELL=/bin/bash >> ProcVersionSignature: Ubuntu 2.6.31-3.19-generic >> Signal: 6 >> SourcePackage: apport >> StacktraceTop: >> raise () from /lib/libc.so.6 >> abort () from /lib/libc.so.6 >> __assert_fail () from /lib/libc.so.6 >> ?? () from /usr/lib/libX11.so.6 >> _XEventsQueued () from /usr/lib/libX11.so.6 >> Title: apport-kde 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-3-generic x86_64 >> UserGroups: >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/gasp-core/+bug/419501/+subscriptions >> > > > -- > Aaron Stromas > Mobile: +1 703 203 9169 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/419501 > > Title: > apport-kde assert failure: python: ../../src/xcb_io.c:242: > process_responses: Assertion `(((long) (dpy->last_request_read) - > (long) (dpy->request)) <= 0)' failed. > > Status in GASP Core Code: > Fix Released > Status in “libxcb” package in Ubuntu: > Won't Fix > Status in “python-gasp” package in Ubuntu: > Fix Released > Status in “python-qt4” package in Ubuntu: > Invalid > Status in “libxcb” source package in Lucid: > Won't Fix > Status in “python-gasp” source package in Lucid: > Fix Released > Status in “python-qt4” source package in Lucid: > Invalid > > Bug description: > 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: python: ../../src/xcb_io.c:242: process_responses: > Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' > failed. > CrashCounter: 1 > Date: Wed Aug 26 16:14:40 2009 > DistroRelease: Ubuntu 9.10 > ExecutablePath: /usr/share/apport/apport-kde > InterpreterPath: /usr/bin/python2.6 > NonfreeKernelModules: nvidia > Package: apport-kde 1.8-0ubuntu1 > PackageArchitecture: all > ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde > ProcEnviron: > PATH=(custom, no user) > LANG=en_US.UTF-8 > LANGUAGE= > SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.31-3.19-generic > Signal: 6 > SourcePackage: apport > StacktraceTop: > raise () from /lib/libc.so.6 > abort () from /lib/libc.so.6 > __
Re: [Bug 419501] Re: apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
I'm sorry - I no longer even have that system On 17 March 2012 15:37, Robert Schroll 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 bug report (455029). > https://bugs.launchpad.net/bugs/419501 > > Title: > apport-kde assert failure: python: ../../src/xcb_io.c:242: > process_responses: Assertion `(((long) (dpy->last_request_read) - > (long) (dpy->request)) <= 0)' failed. > > Status in GASP Core Code: > Fix Released > Status in “libxcb” package in Ubuntu: > Won't Fix > Status in “python-gasp” package in Ubuntu: > Fix Released > Status in “python-qt4” package in Ubuntu: > Invalid > Status in “libxcb” source package in Lucid: > Won't Fix > Status in “python-gasp” source package in Lucid: > Fix Released > Status in “python-qt4” source package in Lucid: > Invalid > > Bug description: > 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: python: ../../src/xcb_io.c:242: process_responses: > Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= > 0)' failed. > CrashCounter: 1 > Date: Wed Aug 26 16:14:40 2009 > DistroRelease: Ubuntu 9.10 > ExecutablePath: /usr/share/apport/apport-kde > InterpreterPath: /usr/bin/python2.6 > NonfreeKernelModules: nvidia > Package: apport-kde 1.8-0ubuntu1 > PackageArchitecture: all > ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde > ProcEnviron: > PATH=(custom, no user) > LANG=en_US.UTF-8 > LANGUAGE= > SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.31-3.19-generic > Signal: 6 > SourcePackage: apport > StacktraceTop: > raise () from /lib/libc.so.6 > abort () from /lib/libc.so.6 > __assert_fail () from /lib/libc.so.6 > ?? () from /usr/lib/libX11.so.6 > _XEventsQueued () from /usr/lib/libX11.so.6 > Title: apport-kde 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-3-generic x86_64 > UserGroups: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gasp-core/+bug/419501/+subscriptions > -- Aaron Stromas Mobile: +1 703 203 9169 -- 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 failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/gasp-core/+bug/419501/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 419501] Re: apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 419501] Re: apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
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 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 plenty of > time to do my best to fix this by March 15th, when Luke said we needed to > have something done. I hope this is acceptable, I just don't have any time > between school and pledging. > > Jamie > > On Tue, Feb 23, 2010 at 9:05 AM, Michael Babcock wrote: > > 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 bugs will be fixed > > but then others will turn up. We have resorted to maintaining our own > > compile of pre-xcb libX11 in order to make our in-house programs > > reliable. > > > > At this point I think libxcb libX11 is a failed experiment. If the > > threading bugs haven't been fixed after a couple years now, will they > > ever be? Should we simply revert to the old libX11? Last time this was > > suggested the answer was that compiz depended on xcb, but is some > > desktop eye-candy really more important than real applications working > > that people use to get real work done? > > > > Someone found the root cause of another of these bugs recently, so maybe > > there is hope: > > http://lists.freedesktop.org/archives/xcb/2009-October/005102.html > > > > -- > > 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 subscribed to GASP > > Core. > > > > Status in GASP Core Code: Confirmed > > Status in “libxcb” package in Ubuntu: Confirmed > > Status in “libxcb” source package in Lucid: Confirmed > > > > Bug description: > > Binary package hint: apport > > > > Description:Ubuntu karmic (development branch) > > Release:9.10 > > > > ProblemType: Crash > > Architecture: amd64 > > AssertionMessage: python: ../../src/xcb_io.c:242: process_responses: > > Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= > > 0)' failed. > > CrashCounter: 1 > > Date: Wed Aug 26 16:14:40 2009 > > DistroRelease: Ubuntu 9.10 > > ExecutablePath: /usr/share/apport/apport-kde > > InterpreterPath: /usr/bin/python2.6 > > NonfreeKernelModules: nvidia > > Package: apport-kde 1.8-0ubuntu1 > > PackageArchitecture: all > > ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde > > ProcEnviron: > > PATH=(custom, no user) > > LANG=en_US.UTF-8 > > LANGUAGE= > > SHELL=/bin/bash > > ProcVersionSignature: Ubuntu 2.6.31-3.19-generic > > Signal: 6 > > SourcePackage: apport > > StacktraceTop: > > raise () from /lib/libc.so.6 > > abort () from /lib/libc.so.6 > > __assert_fail () from /lib/libc.so.6 > > ?? () from /usr/lib/libX11.so.6 > > _XEventsQueued () from /usr/lib/libX11.so.6 > > Title: apport-kde 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-3-generic x86_64 > > UserGroups: > -- Roland Hughes, President Logikal Solutions (630)-205-1593 (cell) http://www.theminimumyouneedtoknow.com http://www.infiniteexposure.net http://www.logikalsolutions.com -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 419501] Re: apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
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 plenty of time to do my best to fix this by March 15th, when Luke said we needed to have something done. I hope this is acceptable, I just don't have any time between school and pledging. Jamie On Tue, Feb 23, 2010 at 9:05 AM, Michael Babcock wrote: > 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 bugs will be fixed > but then others will turn up. We have resorted to maintaining our own > compile of pre-xcb libX11 in order to make our in-house programs > reliable. > > At this point I think libxcb libX11 is a failed experiment. If the > threading bugs haven't been fixed after a couple years now, will they > ever be? Should we simply revert to the old libX11? Last time this was > suggested the answer was that compiz depended on xcb, but is some > desktop eye-candy really more important than real applications working > that people use to get real work done? > > Someone found the root cause of another of these bugs recently, so maybe > there is hope: > http://lists.freedesktop.org/archives/xcb/2009-October/005102.html > > -- > 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 subscribed to GASP > Core. > > Status in GASP Core Code: Confirmed > Status in “libxcb” package in Ubuntu: Confirmed > Status in “libxcb” source package in Lucid: Confirmed > > Bug description: > Binary package hint: apport > > Description:Ubuntu karmic (development branch) > Release:9.10 > > ProblemType: Crash > Architecture: amd64 > AssertionMessage: python: ../../src/xcb_io.c:242: process_responses: > Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' > failed. > CrashCounter: 1 > Date: Wed Aug 26 16:14:40 2009 > DistroRelease: Ubuntu 9.10 > ExecutablePath: /usr/share/apport/apport-kde > InterpreterPath: /usr/bin/python2.6 > NonfreeKernelModules: nvidia > Package: apport-kde 1.8-0ubuntu1 > PackageArchitecture: all > ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde > ProcEnviron: > PATH=(custom, no user) > LANG=en_US.UTF-8 > LANGUAGE= > SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.31-3.19-generic > Signal: 6 > SourcePackage: apport > StacktraceTop: > raise () from /lib/libc.so.6 > abort () from /lib/libc.so.6 > __assert_fail () from /lib/libc.so.6 > ?? () from /usr/lib/libX11.so.6 > _XEventsQueued () from /usr/lib/libX11.so.6 > Title: apport-kde 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-3-generic x86_64 > UserGroups: > > > -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 419501] Re: apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
On Sun, Nov 8, 2009 at 16:18, cparg 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 dependents. -- Luke Faraone http://luke.faraone.cc -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 419501] Re: apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
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 an unrelated hardware problem, but on infrequent occasions (once a month or so) my system will suddenly stop recognising anything USB. I ignored it as an unrelated hardware problem because one of the reviews for the chassis I have specifically stated "due to the riser slot design and case air flow dynamics, heat tends to build up around the support bar and slowly edges the card out of the slot. This eventually causes a large volume of trash to be tossed out over the PCI bus confusing the USB host enough to make it commit suicide." Granted I don't know exactly which motherboard the guy used, nor even what OS, but I am using a fairly popular motherboard for HTPC systems and it's an HTPC specific case, so the probability we're using the same motherboard is decently high (5 or 8% likely). Habst du ein Guten Tag, Eric On Sun, Nov 8, 2009 at 3:18 PM, cparg wrote: > 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 installed. > > Let me know if I can do anything to further analyze the problem - it's > quite annoying. > > Thanks > > Christian > > > seasoned_geek schrieb: >> 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 hours since the >> upgrade. I only know of _one_ product which was behind such a crash and that >> was Kontact. All of the others were mystery package failures. >> >> >> On Saturday 07 November 2009 04:43:02 pm Mark Shuttleworth wrote: >> >>> 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) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' > failed. > https://bugs.launchpad.net/bugs/419501 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in GASP Core Code: New > Status in “libxcb” package in Ubuntu: Triaged > > Bug description: > Binary package hint: apport > > Description: Ubuntu karmic (development branch) > Release: 9.10 > > ProblemType: Crash > Architecture: amd64 > AssertionMessage: python: ../../src/xcb_io.c:242: process_responses: > Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' > failed. > CrashCounter: 1 > Date: Wed Aug 26 16:14:40 2009 > DistroRelease: Ubuntu 9.10 > ExecutablePath: /usr/share/apport/apport-kde > InterpreterPath: /usr/bin/python2.6 > NonfreeKernelModules: nvidia > Package: apport-kde 1.8-0ubuntu1 > PackageArchitecture: all > ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde > ProcEnviron: > PATH=(custom, no user) > LANG=en_US.UTF-8 > LANGUAGE= > SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.31-3.19-generic > Signal: 6 > SourcePackage: apport > StacktraceTop: > raise () from /lib/libc.so.6 > abort () from /lib/libc.so.6 > __assert_fail () from /lib/libc.so.6 > ?? () from /usr/lib/libX11.so.6 > _XEventsQueued () from /usr/lib/libX11.so.6 > Title: apport-kde 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-3-generic x86_64 > UserGroups: > -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 419501] Re: apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
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 installed. Let me know if I can do anything to further analyze the problem - it's quite annoying. Thanks Christian seasoned_geek schrieb: > 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 hours since the > upgrade. I only know of _one_ product which was behind such a crash and that > was Kontact. All of the others were mystery package failures. > > > On Saturday 07 November 2009 04:43:02 pm Mark Shuttleworth wrote: > >> 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) (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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 419501] Re: 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 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 hours since the upgrade. I only know of _one_ product which was behind such a crash and that was Kontact. All of the others were mystery package failures. On Saturday 07 November 2009 04:43:02 pm Mark Shuttleworth wrote: > 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. > -- Roland Hughes, President Logikal Solutions (630)-205-1593 (cell) http://www.theminimumyouneedtoknow.com http://www.infiniteexposure.net http://www.logikalsolutions.com -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 419501] Re: apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
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 wrote: > 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, finally get to reporting to one of them, but then apport- > kde itself crashes. Agggh. > > And the bugs.launchpad "Yes, this is the bug I'm trying to report" > dialog fails in Konqueror, the green checkmark doesn't do anything. > Aggh. > > -- > 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 direct subscriber > of the bug. > > Status in GASP Core Code: New > Status in “libxcb” package in Ubuntu: Triaged > > Bug description: > Binary package hint: apport > > Description: Ubuntu karmic (development branch) > Release: 9.10 > > ProblemType: Crash > Architecture: amd64 > AssertionMessage: python: ../../src/xcb_io.c:242: process_responses: > Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' > failed. > CrashCounter: 1 > Date: Wed Aug 26 16:14:40 2009 > DistroRelease: Ubuntu 9.10 > ExecutablePath: /usr/share/apport/apport-kde > InterpreterPath: /usr/bin/python2.6 > NonfreeKernelModules: nvidia > Package: apport-kde 1.8-0ubuntu1 > PackageArchitecture: all > ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde > ProcEnviron: > PATH=(custom, no user) > LANG=en_US.UTF-8 > LANGUAGE= > SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.31-3.19-generic > Signal: 6 > SourcePackage: apport > StacktraceTop: > raise () from /lib/libc.so.6 > abort () from /lib/libc.so.6 > __assert_fail () from /lib/libc.so.6 > ?? () from /usr/lib/libX11.so.6 > _XEventsQueued () from /usr/lib/libX11.so.6 > Title: apport-kde 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-3-generic x86_64 > UserGroups: > -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 419501] Re: apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
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 the updates. On Wednesday 02 September 2009 10:52:37 am Martin Pitt wrote: > 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 > -- Roland Hughes, President Logikal Solutions (630)-205-1593 (cell) http://www.theminimumyouneedtoknow.com http://www.infiniteexposure.net http://www.logikalsolutions.com -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 419501] Re: apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
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 morning alone and once required a reboot. All I do is click to send bug reports. Dennis Stout On Wed, Sep 2, 2009 at 10:52 AM, Martin Pitt wrote: > 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: ../../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 direct subscriber > of the bug. > > Status in “apport” package in Ubuntu: Incomplete > > Bug description: > Binary package hint: apport > > Description: Ubuntu karmic (development branch) > Release: 9.10 > > ProblemType: Crash > Architecture: amd64 > AssertionMessage: python: ../../src/xcb_io.c:242: process_responses: > Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' > failed. > CrashCounter: 1 > Date: Wed Aug 26 16:14:40 2009 > DistroRelease: Ubuntu 9.10 > ExecutablePath: /usr/share/apport/apport-kde > InterpreterPath: /usr/bin/python2.6 > NonfreeKernelModules: nvidia > Package: apport-kde 1.8-0ubuntu1 > PackageArchitecture: all > ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde > ProcEnviron: > PATH=(custom, no user) > LANG=en_US.UTF-8 > LANGUAGE= > SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.31-3.19-generic > Signal: 6 > SourcePackage: apport > StacktraceTop: > raise () from /lib/libc.so.6 > abort () from /lib/libc.so.6 > __assert_fail () from /lib/libc.so.6 > ?? () from /usr/lib/libX11.so.6 > _XEventsQueued () from /usr/lib/libX11.so.6 > Title: apport-kde 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-3-generic x86_64 > UserGroups: > -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
