I'm running amd64 and am getting some screen corruption, which i believe coincided with the last gnome update. For example in firefox the address bar or bookmarks toolbar buttons can go black then come good again and i can get black bands when i scroll. revdep-rebuild hasnt helped. What should i try next?

Am 06.08.2010 12:00, schrieb Adam Carter:
> I'm running amd64 and am getting some screen corruption, which i believe
> coincided with the last gnome update. For example in firefox the address
> bar or bookmarks toolbar buttons can go black then come good again and i
> can get black bands when i scroll. revdep-rebuild hasnt helped. What
> should i try next?

Hmm, maybe a GTK+ issue. I would try to re-emerge gtk+, xulrunner and
then firefox. If that doesn't help, try other X-Server versions.

On Fri, Aug 6, 2010 at 9:44 AM, Florian Philipp <lists@f_philipp.fastmail.net> wrote:


Am 06.08.2010 12:00, schrieb Adam Carter:

> I'm running amd64 and am getting some screen corruption, which i believe

> coincided with the last gnome update.[snip]


Hmm, maybe a GTK+ issue. I would try to re-emerge gtk+, xulrunner and

then firefox. If that doesn't help, try other X-Server versions.
*I am also running amd64 and experienced gtk+ issues after the recent gnome update. *In my case gtk icon sets were not working as specified in ~/.gtkrc-2.0, regardless what I set*gtk-icon-theme-name to. *For example, thunar refused to display any icons other than its fallback set. *Oddly enough, this only happened on my desktop and not on my laptop, which has an almost identical setup.


revdep-rebuild reported no issues, and re-emerging gtk+, thunar, and*gnome-icon-theme had no effect. *Last night I went with the nuclear option (emerge -eav --keep-going world), and it solved the problem.

I am seeing it in gnome-terminal - corrupted and sometimes leftover buts
of text. As well, when clicking the mouse will see a (usually) black
bock appear at the cursor - sometimes stays for a second or two.

3 systems, all x86 and started with gnome 2.30

BillK


On Fri, 2010-08-06 at 12:37 -0400, Adam Zajac wrote:
> On Fri, Aug 6, 2010 at 9:44 AM, Florian Philipp
> <lists@f_philipp.fastmail.net> wrote:
> Am 06.08.2010 12:00, schrieb Adam Carter:
>
> > I'm running amd64 and am getting some screen corruption,
> which i believe
> > coincided with the last gnome update.
> [snip]
>
> Hmm, maybe a GTK+ issue. I would try to re-emerge gtk+,
> xulrunner and
> then firefox. If that doesn't help, try other X-Server
> versions.
>
> I am also running amd64 and experienced gtk+ issues after the recent
> gnome update. In my case gtk icon sets were not working as specified
> in ~/.gtkrc-2.0, regardless what I set gtk-icon-theme-name to. For
> example, thunar refused to display any icons other than its fallback
> set. Oddly enough, this only happened on my desktop and not on my
> laptop, which has an almost identical setup.
>
>
> revdep-rebuild reported no issues, and re-emerging gtk+, thunar,
> and gnome-icon-theme had no effect. Last night I went with the
> nuclear option (emerge -eav --keep-going world), and it solved the
> problem.

--
William Kenworthy <billk@iinet.net.au>
Home in Perth!

revdep-rebuild reported no issues, and re-emerging gtk+, thunar, and*gnome-icon-theme had no effect. *Last night I went with the nuclear option (emerge -eav --keep-going world), and it solved the problem.



I just tried emerge -e --keep-going gnome and it hasn't helped, so I guess i'll try going nuclear...

On Sun, Aug 8, 2010 at 1:35 PM, Adam Carter <adamcarter3@gmail.com> wrote:




revdep-rebuild reported no issues, and re-emerging gtk+, thunar, and*gnome-icon-theme had no effect. *Last night I went with the nuclear option (emerge -eav --keep-going world), and it solved the problem.




I just tried emerge -e --keep-going gnome and it hasn't helped, so I guess i'll try going nuclear...


Ok, i just tried emerge -e --keep-going world followed by revdep-rebuild and lafilefixer and its still broken...

Any more suggestions? I'm assuming removing the ~/.gnome* directories would not be useful in this instance.

Adam Carter <adamcarter3 <at> gmail.com> writes:
> Any more suggestions?

I suppose this is the same problem as
<http://forums.gentoo.org/viewtopic-t-837535.html>, in which case the easiest
workaround is to downgrade ati-drivers from 10.7 to 10.5 for now. It is not a
Gnome/GTK problem (or at least not directly, I don't know precisely).