Comment 47 for bug 345076

> You are not a developer

I don't know where you get your information from, but your source doesn't seem to be reliable in any way.

> and you go around confirming and invalidating components,

I changed the state according to the knowledge accumulated in this thread. The same you did. Or are you saying that maintaining the bug database is a bad thing to do?

> and playing ping pong confirmed/invalid

Whenever I re-opened the bug, I each time added an explanation and or provided more evidence. Whenever that guy closed it, it was always with a dogmatic "driver issue, don't pester me" against all evidence accumulated so far. I don't think you have to blame _me_ here for not accepting that guys misbehaviour.

> Then you make a remark like that?!?

Check what that guy contributed to the bug fixing. He checked which driver you were using and then just kept insisting on the dogmactic view that "corruption occured => must be driver issue". I do not see any constructive action to get the bug fixed. Not in any way.

> I need this bug fixed

According your comment #35 the bug was fixed for you. I moved the bug to the only components that were different between 4.3b2 and 4.2.4. I also presented further evidence that make it likely to be related to those components. Do you think that was wrong? Do you think you would get the bug fixed if the only thing being done is shifting the blame to some driver that, according to presented evidence, is not at fault here?

> File a different bug,

What purpose would it have to file a different bug that's obviously a duplicate?

> to as the dev implies that your issue is not the same as the OP

That guy implies (in fact, dogmatically claims) a lot. Contrary to all evidence. Just don't let reality get into way of your opinion. Feel free to check the evidence provided and feel free to argue to the contrary.

If you actually want to get this bug fixed, then get someone to figure out why the "QPainter" could become "not active". See your comment #3. This seems to be the core issue here. And that needs to debugged in KDE4 land, not in any video driver.

If you want to do something on your own, deinstall KDE4 python bindings and check whether this fixes the corruptions or not. If it does not, then those where the wrong packages to blame. If it does, then you even have an explaination why not more people are affected.