a quick update on the argb hell i'm living in. it seems that the scrolling bug is only visible with the proprietary nvidia drivers. awesome.
anyways, zack came up with this patch for those affected in the meantime. update: turns out the patch provenance and discovery of the nvidia relatedness of the problem goes back to frederikh
apparently it has to do with tiles used during rendering pointing to invalidated surfaces after dma flushes. so qt is doing the right thing apparently, but the driver gets in the way. this makes it doubtful the patch will go into qt itself as it's slower. if this is indeed an nvidia problem (which we can only guess at, but that's a good guess based on the fact that it only seems to happen with those drivers) they need to fix their stuff. if it were open source, maybe we could help them, but its not and so we're screwed until the boys at nvidia Do The Right Thing(tm) on our behalf. score one for proprietary code.
i've also filed a bug report against gtk for the systray problem. in conversation with one of the plasma devs, a gtk dev referred to this problem as a "feature request". i hope that was just a misinterpretation of the issue and that the gtk team doesn't view crash inducing bugs as feature requests; i'm sure they don't =) in any case, they are set to do a release in early january from what i understand, so with some luck this could even be fixed in time for kde 4.0.
anyways, zack came up with this patch for those affected in the meantime. update: turns out the patch provenance and discovery of the nvidia relatedness of the problem goes back to frederikh
apparently it has to do with tiles used during rendering pointing to invalidated surfaces after dma flushes. so qt is doing the right thing apparently, but the driver gets in the way. this makes it doubtful the patch will go into qt itself as it's slower. if this is indeed an nvidia problem (which we can only guess at, but that's a good guess based on the fact that it only seems to happen with those drivers) they need to fix their stuff. if it were open source, maybe we could help them, but its not and so we're screwed until the boys at nvidia Do The Right Thing(tm) on our behalf. score one for proprietary code.
i've also filed a bug report against gtk for the systray problem. in conversation with one of the plasma devs, a gtk dev referred to this problem as a "feature request". i hope that was just a misinterpretation of the issue and that the gtk team doesn't view crash inducing bugs as feature requests; i'm sure they don't =) in any case, they are set to do a release in early january from what i understand, so with some luck this could even be fixed in time for kde 4.0.
(updated: i just fixed the links in this entry; i keep forgetting that kblogger does rich text so typing the link tags manually isn't what i should be doing. all this new-fangled technology, i swear ;))
11 comments:
I am thinking that kblogger should notice if you write HTML in your post with no other formatting and, if you do, ask whether it should do the conversion anyway.
In response to the ARGB issue: is there a way for the system tray to notice that there is a gtk app being loaded, and then as a result load the icon differently? is it is that not possible. (I'm sure it's already been thought of)
Anyway, as a result of this, I've just been using kopete, and xchat for irc instead of pidgin, and Juk instead of rhythmbox. It's a shame the GTK guys are not very apt to admit that they are dealing with a bug that shows up in a competitive project.
Perhaps they don't realize that they are further screwing the state of interoperability?
Is there something that the Gnome boys and girls want KDE to do for them, some inter-DE lovin' might speed things up?
re stephan:
If plasma just papers over GTK's bugs then why fix the bugs? They won't be causing any crashes.
In the meantime the plasma developers will be stuck maintaing a GTK spesific compatibility layer in their code, far better just to fix the bugs once and for all.
Best of luck to you Aaron, I know its tough being on the bleeding edge, its going to be worth it though!
If it is nvidia problem, try to report it here:
http://www.nvnews.net/vbulletin/forumdisplay.php?f=14
and generate a bug-report attachment
Haha I'm commenting on your twitter talking about KRunner having a history now.
Now people can bitch about 100 list items being too much/little
Aseigo! Looks like Gnome is doing ARGB stuff too now. Perhaps the GTK bug you mentioned will be fixed soon because of this.
GNOME theme engine designer adds transparency to GTK:
http://arstechnica.com/journals/linux.ars/2007/12/12/gnome-theme-engine-designer-adds-transparency-to-gtk
Add I must say, it ARGB theming at the toolkit level looks sexy! Does Qt have that?
"Looks like Gnome is doing ARGB stuff too now."
yes, as always, pressured they try to keep up =) free software competition is great. more so when you're ahead, maybe, but still ;)
"Perhaps the GTK bug you mentioned will be fixed soon because of this."
no, it's unrelated unfortunately.
"Does Qt have that?"
for several years now =) that's what we've using for many of the plasma effects, for instance.
Hey!
Nvidia released new drivers, among others fixes it is mentioned:
- Fixed problems scrolling ARGB X drawables in Qt.
Maybe this is it?
See:
http://www.nvidia.com/object/linux_display_ia32_169.07.html
Any update on the GTK issue? It sadly looks like a "it's not our bug!" fight.
it's been marked resolved/notabug by the gtk crowd.
Post a Comment