Graesslin: Driver dilemma in KDE workspaces 4.5 [LWN.net]

Graesslin: Driver dilemma in KDE workspaces 4.5

Posted Sep 6, 2010 22:51 UTC (Mon) by jrn (guest, #64214)
In reply to: Graesslin: Driver dilemma in KDE workspaces 4.5 by Sho
Parent article: Graesslin: Driver dilemma in KDE workspaces 4.5

I believe that, but it is still helpful in such a post to link to bug reports. That would implicitly answer the question "well, what can I do about it?" that some readers may have.

Here are a possible few: https://bugs.freedesktop.org/show_bug.cgi?id=29148 https://bugs.freedesktop.org/show_bug.cgi?id=29223 https://bugs.freedesktop.org/show_bug.cgi?id=29711 https://bugs.freedesktop.org/show_bug.cgi?id=29873

(Log in to post comments)

Graesslin: Driver dilemma in KDE workspaces 4.5

Posted Sep 7, 2010 9:28 UTC (Tue) by tcourbon (subscriber, #60669) [Link]

Hey look !
Their are one of my bug reports here !

*tickling his baby*

It's the first time I tried to report a bug to a such upstream project as xorg ddx. I double double checked the componenent I believed to be faulty. So I'm quite happy now as it look like I has spotted the culprit !

I know that the developers are by far too few to handle properly both the bug fxing and the claimed-since-so-long new feature implementation work. I want to help them and I would like to provide more information but I wasn't able to find directions for debugging the drivers (e.g : How could I trace the deficient function call, memory allocation or at least the faulty code path ?).

It's hard to find documentation generally speaking for those complicated piece of software. I dream of a graphicnewbies.org...

Graesslin: Driver dilemma in KDE workspaces 4.5

Posted Sep 7, 2010 13:05 UTC (Tue) by cesarb (subscriber, #6266) [Link]

For Intel, the bug reporting guide is here: http://intellinuxgraphics.org/how_to_report_bug.html

I do not know if there is a similar guide for radeon or noveau.

Graesslin: Driver dilemma in KDE workspaces 4.5

Posted Sep 8, 2010 8:22 UTC (Wed) by tcourbon (subscriber, #60669) [Link]

Sadly I wasn't able to find something similar.

Dunno if it's just me being idiot or if it's that such guidelines didn't exist.

Graesslin: Driver dilemma in KDE workspaces 4.5

Posted Sep 11, 2010 6:18 UTC (Sat) by Thalience (subscriber, #4217) [Link]

If it is this one (guessing, based on your user name) https://bugs.freedesktop.org/show_bug.cgi?id=29873 then you did a pretty good job :) It would probably be helpful to add the version of Mesa that you are using, however.

Graphics corruption bugs are generally more difficult for end-users to generate good reports for than actual crashes, since there is no backtrace or anything. Perhaps KWin can be convinced to log the sequence of GL calls it is making, but I wouldn't know how...

Seeing as how you (or the reporter of that bug, if I guessed wrong) have an Evergreen (HD5770) card and public GL support for that card is only a few weeks old, the best way you can help is to keep testing the latest mesa git snapshots (running Arch should make this easy). Update (or close) the bug if the behavior changes for the better (or worse).

Developers always like to see that their work has fixed a bug, even if they weren't looking at your problem specifically. And they hate cleaning old bugs out of the bug tracker...