From: Adam Zajac <strider1551@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Some corruption after gnome 2.30
Date: Fri, 6 Aug 2010 12:37:30 -0400 [thread overview]
Message-ID: <AANLkTi=Kx22YxYcjpU_BOE+5G1_FgNG2HjeWspDPezWB@mail.gmail.com> (raw)
In-Reply-To: <4C5C11C4.2060104@f_philipp.fastmail.net>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 1640 bytes --]
next prev parent reply other threads:[~2010-08-06 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 10:00 [gentoo-user] Some corruption after gnome 2.30 Adam Carter
2010-08-06 13:44 ` Florian Philipp
2010-08-06 16:37 ` Adam Zajac [this message]
2010-08-07 3:54 ` William Kenworthy
2010-08-08 3:35 ` Adam Carter
2010-08-09 1:30 ` Adam Carter
2010-08-22 17:59 ` [gentoo-user] " Mathieu Bonnet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=Kx22YxYcjpU_BOE+5G1_FgNG2HjeWspDPezWB@mail.gmail.com' \
--to=strider1551@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox