Version: (using KDE 4.2.0) OS: Linux Installed from: Ubuntu Packages I have just lost several icons in two panels. I was doing nothing in particular (just editing a TeX file and generating the PDF from it) when I happened to look at the panels and see that icons were missing. I shall attach a screenshot showing the problem. The missing icons are: 1. (at the extreme left) the K menu icon 2. Three icons in the quicklaunch plasmoid (see also bug 185651) 3. A dictionary plasmoid icon (in the little panel to the right of the main one). See also bug 185651. I think that that bug is just a special example of this more general one. Bug 185651 appears more frequently than this one, but they appear to be probably two different examples or aspects of the same bug. For reference, I have seen bug 185651 appear several times in the couple of weeks since switching to 4.2. This is the first time I have experienced the bug I am reporting here.
Created attachment 31959 [details] screenshot showing panels with missing icons
I just checked, and clicking where the icons should be still results in the expected behaviour (e.g., clicking on the extreme left of the larger panel does produce the expected menu, even though the icon is absent). So maybe this is a repaint issue? Possibly associated with bug 175087 ???
Mh, strange, what Qt version and graphics drivers/card do you have? Thanks
Qt: 4.4.3 (the latest available from the 64-bit Kubuntu repositories) Graphics: HIS Radeon HD4670 IceQ card. xorg 7.4 Driver: fglrx 8.552 (the latest available from the 64-bit Kubuntu repositories) FWIW, I don't see any obvious display artifacts to make me suspect the driver, despite heavy use.
I was getting a similar problem with KDE 4.2.1, and now with 4.2.2 the problem is more frequent (typically more than once every 24 hours..). Sometimes _all_ icons vanish, including those on the panel. Plasma does not crash, and clicking on the missing icons original position still produces the correct behaviour. KDE version is 4.2.2 (installed from latest Fedora 10 update rpms)
More info (running startkde from a console session) All icons on desktop and panel vanished: QPainter::end: Painter not active, aborted QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setCompositionMode: Painter not active QPainter::end: Painter not active, aborted QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setCompositionMode: Painter not active QPainter::end: Painter not active, aborted QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setCompositionMode: Painter not active QPainter::end: Painter not active, aborted QPainter::end: Painter not active, aborted QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setCompositionMode: Painter not active QPainter::end: Painter not active, aborted kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1431eb1) QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setCompositionMode: Painter not active QPainter::end: Painter not active, aborted QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setCompositionMode: Painter not active QPainter::end: Painter not active, aborted QPainter::begin: Paint device returned engine == 0, (repeated..............) This is occurring - on average - twice in every 12 hours..
@rgadsdon: your issue is likely to be a graphics card/drivers bug.
Nvidia graphics cards do seem to be a common factor in many of these problem reports.. I have found that _unchecking_ the 'Enable direct rendering' and 'Use VSync' tabs under OpenGL Options in System Settings/Desktop/Desktop Effects/Advanced seems - so far - to make the problem go away, and may be an acceptable workaround for the time being..
(In reply to comment #8) > Nvidia graphics cards do seem to be a common factor in many of these problem > reports.. > But not all :-( Maybe the preponderance of nvidia here simply reflects the usage of people with enough savvy to come here to talk about bugs. I am glad that there may be a workaround for people using nvidia, but that doesn't help me :-(
The workaround in Comment #8 has not worked - although it appears to have prolonged the interval between icon disappearances.. Back to the drawing board..
Problem still exists here, although in a modified form, in 4.2.2. The modification is that once this starts to happen, then: 1. All plasmoids disappear from the desktop 2. simply moving a cursor over a plasmoid in the panel will cause the icon or any other graphics associated with that plasmoid to disappear. 3. The various monitor plasmoids (I have a couple in my panel) stop updating. Basically, I think I'm reporting exactly the same behaviour as comment #5. Clicking where plasma icons *should* be still causes them to behave as if they were visible. I have been running 4.2.2 for about three days; this bug just manifested itself for the first time. So it *might* be a bit less frequent, or it may just be that this time I had to wait a bit longer than average for it to manifest itself. We'll see what happens in the coming days. The fact that the behaviour seems to be exactly the same for rgadson and myself, even though he is running (I think) nvidia and Fedora, whereas I am running ATI and Kubuntu does seem to indicate that it's not a driver problem nor a distro-specific problem.
*** This bug has been marked as a duplicate of bug 189430 ***
This cannot be a duplicate of bug 189430, since that has (by some process that is a mystery to me) been determined to be an nvidia bug, and an nvidia bug cannot (as far as I know) affect my ATI card. So I've marked this bug back to UNCONFIRMED. Frankly, I think that the resolution of bug 189430 is an error, as I believe I have made clear there. But right now, as I write this, I have to assume that it's not an error, and that it *is* an nvidia bug. Logically, then, this bug, despite the fact that the symptoms appear to be identical to those in bug 189430, can't be a duplicate of that bug. Really, I think this should be moved back to DUPLICATE, and bug 189430 should not be marked RESOLVED. But in the meantime, I want to be sure that the bug that affects me isn't marked RESOLVED, since no amount of complaining to nvidia is going to fix my problem. (Nor anyone else's, I suspect, because I see no evidence at all that it's an nvidia bug, but maybe you all know something from an offline source that I don't.)
fine, then let me mark it as resolved upstream. i just figured you'd find the information in the other BR useful since it's the same root issue: messed up drivers.
(In reply to comment #14) > fine, then let me mark it as resolved upstream. i just figured you'd find the > information in the other BR useful since it's the same root issue: messed up > drivers. How do you know that? How do you know, for example that it isn't an X bug? (or a KDE bug. Or a qt bug) I'm just trying to be logical here. PLEASE explain to me how you know that both ATI and NVIDIA have effectively the same bug in their drivers. I simply don't understand how you can conclude that given the evidence in the thread. I am pleading for an explanation here. I try really, really hard to file useful bug reports and not waste people's time. I do not appreciate bugs being marked as resolved without a detailed explanation of why that is happening. Please treat me as an adult and EXPLAIN the reason.
It has nothing to do with treating you as an adult or not, and everything to do with how much time I have in the day to spend educating everyone who comes along about the ins and outs of things like this. I wish I had more time, too, but as it is I have more to do than I have hours in the day.
*** Bug 185651 has been marked as a duplicate of this bug. ***
So we still don't get an explanation, or even a pointer to the information that shows how two completely different companies can have exactly the same bug in their drivers. I'm truly sorry that you don't feel that users are worth the time to provide, or even point to, an explanation for such a bizarre situation.
In a case like this I think simply a link to the bug report on the nvidia site would have helped. Has this problem been reported to nvidia? Once I know the bug number I would be more than happy to send emails to nvidia asking them to fix the problem since it makes my whole desktop unusable several times in a work day. As it stands now I can't do much in the way of helping to get this problem fixed as my problem report would sound like "Hey nvidia, my icons and text dissapear. Here is a screenshot and the KDE guys said it's your bug but don't have the time to provide technical details. Have fun!" I am think that you wouldn't enjoy getting the same treatment from your DOWNSTREAMs. I want to help getting this problem fixed.
After a bit more digging around, the problem has already been reported to NVidia: http://www.nvnews.net/vbulletin/showthread.php?t=131864 And there are some interesting links there to discussions on plasma and qt... The suggested workaround - for the time being - is to _disable_ the 'seconds' display in the panel digital clock (which normally enables it by default). I have already done this, and my desktop and panel icons have stayed visible for over 20 hours (and they would previously have vanished at least twice in this period..)
I'm sorry but in my case that workaround doesn't work. In fact I've removed the digital clock plasmoid and replaced it with the binary clock and it still occurs several times a day.
As a point of reference, the workaround appears to be working for me, with the following: Fedora 10, with 'latest' KDE (4.2.2+) and QT (4.5.0+) update RPMs installed. NVidia driver version 185.18.10 with a GeForce 9800 GT Kernel 2.6.28.10 (compiled)
I wonder if http://darktears.wordpress.com/2009/05/22/the-plasma-leak-story/ is related. Check it. Thanks
I tried the workaround... I thought it was working, because plasma stayed up for three days. But it just died (taking ctrl-alt-delete with it; I ended up rebooting).
With the non-seconds version of the digital clock, plasma on my system stays up for about 2 days, and then the icons start vanishing... I can 'rescue' the situation without rebooting, by immediately opening a konsole window, and then killing plasma and restarting it (> killall plasma, then > plasma). So, an imperfect workaround, but not a solution..
According to http://darktears.wordpress.com/2009/05/22/the-plasma-leak-story/ this is caused by the SystemTray widget not freeing the Pixmaps. It is fixed on current 4.3trunk. You could try removing the SystemTray.
I replaced the Digital Clock with Adjustable Clock and Binary Clock. I replaced the systray plasmoid with "trayer" a standalone tray. This bug is still occuring. I guess the next logical step is to replace KDE with something else. It's sad to see so many people from KDE, which I previously considered a smart bunch, fail to realize the impact/importance of this bug.
FWIW, I get errors when plasma starts to misbehave: X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b25955 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 55 (X_CreateGC) Resource id: 0x2b25956 X Error: BadGC (invalid GC parameter) 13 Major opcode: 59 (X_SetClipRectangles) Resource id: 0x2b25956 X Error: BadGC (invalid GC parameter) 13 Major opcode: 59 (X_SetClipRectangles) Resource id: 0x2b25956 X Error: BadGC (invalid GC parameter) 13 Major opcode: 59 (X_SetClipRectangles) Resource id: 0x2b25956 X Error: BadGC (invalid GC parameter) 13 Major opcode: 59 (X_SetClipRectangles) Resource id: 0x2b25956 X Error: BadGC (invalid GC parameter) 13 Major opcode: 59 (X_SetClipRectangles) Resource id: 0x2b25956 X Error: BadGC (invalid GC parameter) 13 Major opcode: 59 (X_SetClipRectangles) Resource id: 0x2b25956 X Error: BadGC (invalid GC parameter) 13 Major opcode: 59 (X_SetClipRectangles) Resource id: 0x2b25956 X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b25956 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 53 (X_CreatePixmap) Resource id: 0x2b25ae5 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b25ae6 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 55 (X_CreateGC) Resource id: 0x2b25b11 X Error: BadGC (invalid GC parameter) 13 Major opcode: 72 (X_PutImage) Resource id: 0x2b25b11 X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b25b11 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 53 (X_CreatePixmap) Resource id: 0x2b25b12 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b25b12 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 55 (X_CreateGC) Resource id: 0x2b25b12 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 (X_PutImage) Resource id: 0x2b25b12 X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b25b14 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x2b25b13 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 7 (RenderFreePicture) Resource id: 0x2b25b13 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 (X_FreePixmap) Resource id: 0x2b25b12 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 53 (X_CreatePixmap) Resource id: 0x2b25b3d X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b25b3e X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 53 (X_CreatePixmap) Resource id: 0x2b25cd0 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b25cd1 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 55 (X_CreateGC) Resource id: 0x2b25cfc X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 55 (X_CreateGC) Resource id: 0x2b25cfd X Error: BadGC (invalid GC parameter) 13 Major opcode: 59 (X_SetClipRectangles) Resource id: 0x2b25cfc X Error: BadGC (invalid GC parameter) 13 Major opcode: 59 (X_SetClipRectangles) Resource id: 0x2b25cfd X Error: BadGC (invalid GC parameter) 13 Major opcode: 59 (X_SetClipRectangles) Resource id: 0x2b25cfc X Error: BadGC (invalid GC parameter) 13 Major opcode: 59 (X_SetClipRectangles) Resource id: 0x2b25cfd X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b25cfd X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b25cfc X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 53 (X_CreatePixmap) Resource id: 0x2b25d28 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b25d29 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 53 (X_CreatePixmap) Resource id: 0x2b25ebb X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b25ebc X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b25ee7 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 55 (X_CreateGC) Resource id: 0x2b25ee8 X Error: BadGC (invalid GC parameter) 13 Major opcode: 72 (X_PutImage) Resource id: 0x2b25ee8 X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b25ee8 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x2b25ee7 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 7 (RenderFreePicture) Resource id: 0x2b25ee7 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b25f13 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 55 (X_CreateGC) Resource id: 0x2b25f14 X Error: BadGC (invalid GC parameter) 13 Major opcode: 72 (X_PutImage) Resource id: 0x2b25f14 X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b25f14 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x2b25f13 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 7 (RenderFreePicture) Resource id: 0x2b25f13 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 53 (X_CreatePixmap) Resource id: 0x2b260a3 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b260a4 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b260cf X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 55 (X_CreateGC) Resource id: 0x2b260d0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 72 (X_PutImage) Resource id: 0x2b260d0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b260d0 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x2b260cf X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 7 (RenderFreePicture) Resource id: 0x2b260cf X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b260fb X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 55 (X_CreateGC) Resource id: 0x2b260fc X Error: BadGC (invalid GC parameter) 13 Major opcode: 72 (X_PutImage) Resource id: 0x2b260fc X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b260fc X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x2b260fb X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 7 (RenderFreePicture) Resource id: 0x2b260fb X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 55 (X_CreateGC) Resource id: 0x2b26291 X Error: BadGC (invalid GC parameter) 13 Major opcode: 72 (X_PutImage) Resource id: 0x2b26291 X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b26291 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 53 (X_CreatePixmap) Resource id: 0x2b26292 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b26292 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 55 (X_CreateGC) Resource id: 0x2b26292 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 (X_PutImage) Resource id: 0x2b26292 X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b26294 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x2b26293 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 7 (RenderFreePicture) Resource id: 0x2b26293 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 (X_FreePixmap) Resource id: 0x2b26292 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 55 (X_CreateGC) Resource id: 0x2b262c0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x2b262c0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x2b262c0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x2b262c0 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 53 (X_CreatePixmap) Resource id: 0x2b262c1 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b262c1 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 55 (X_CreateGC) Resource id: 0x2b262c1 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 (X_PutImage) Resource id: 0x2b262c1 X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b262c3 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x2b262c2 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 7 (RenderFreePicture) Resource id: 0x2b262c2 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 (X_FreePixmap) Resource id: 0x2b262c1 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x2b262c0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x2b262c0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x2b262c0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x2b262c0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x2b262c0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x2b262c0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x2b262c0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x2b262c0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x2b262c0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x2b262c0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 56 (X_ChangeGC) Resource id: 0x2b262c0 X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b262c0 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b26453 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Resource id: 0x2b26454 X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b26454 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x2b26453 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 7 (RenderFreePicture) Resource id: 0x2b26453 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 55 (X_CreateGC) Resource id: 0x2b2647f X Error: BadGC (invalid GC parameter) 13 Major opcode: 72 (X_PutImage) Resource id: 0x2b2647f X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b2647f X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 53 (X_CreatePixmap) Resource id: 0x2b26480 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b26480 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 55 (X_CreateGC) Resource id: 0x2b26480 X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 (X_PutImage) Resource id: 0x2b26480 X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x2b26482 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x2b26481 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 7 (RenderFreePicture) Resource id: 0x2b26481 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 (X_FreePixmap) Resource id: 0x2b26480 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x2b1d8aa X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Major opcode: 53 (X_CreatePixmap) Resource id: 0x2b264a8 X Error: BadIDChoice (invalid resource ID chosen for this connection) 14 Extension: 153 (RENDER) Minor opcode: 4 (RenderCreatePicture) Resource id: 0x2b264a9 X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x2b1d8aa X Error: RenderBadPicture (invalid Picture parameter) 173 Extension: 153 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x2b1d8aa
> fail to realize the impact/importance of this bug. then explain why so many of us have spent so much time in order to fix it. mmm. this problem had a few culprits (meaning it wasn't just your usual "here's the 5 line patch" type bug) and with the latest dev version of Qt and the standard set of widgets, we no longer appear to be leaking pixmaps. (as in, the pixmap count doesn't go up after long runs) for x.org drivers with bugs in them, there's nothing we can do about that except identify and report (which has helped those improve as well)
This is still reproducible for me in 4.3 RC1. I've left KDE running ovenight and the second evening wnen I returned the screen looked like in the attached screenshot. The more I moved the mouse the more things "disappeared". Qt 4.5.1.
Created attachment 35068 [details] plasma with disappearing stuff
Another occurrence: QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setCompositionMode: Painter not active QPainter::end: Painter not active, aborted QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setCompositionMode: Painter not active QPainter::end: Painter not active, aborted KCrash: Application 'plasma-desktop' crashing... I had hoped so much that this would be fixed in 4.3 :(