Comment 26 for bug 419501

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 <email address hidden> 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:
>