Solved:
Code: Select all
emerge gtk-engines
Code: Select all
emerge gtk-engines

You just have to re-emerge or recompile those themes against gtk+ 2.4.hanzotutu wrote:Especially those Aqua themes. I've emerged back to gtk+2.2.4-r1

Right and gtk-engines too.Deepu Sudhakar wrote:You just have to re-emerge or recompile those themes against gtk+ 2.4.hanzotutu wrote:Especially those Aqua themes. I've emerged back to gtk+2.2.4-r1


Code: Select all
For gtk themes to work correctly after an update, you might have to rebuild your theme engines.
Executing 'qpkg -f -nc /usr/lib/gtk-2.0/2.2.0/engines | xargs emerge' should do the trick if
you upgrade from gtk+-2.2 to 2.4 (requires gentoolkit).

yeah, i did the update overnight while I slept!EdSchouten wrote:Here a message that was on screen (and that you ignored):
Code: Select all
For gtk themes to work correctly after an update, you might have to rebuild your theme engines. Executing 'qpkg -f -nc /usr/lib/gtk-2.0/2.2.0/engines | xargs emerge' should do the trick if you upgrade from gtk+-2.2 to 2.4 (requires gentoolkit).
Code: Select all
emerge gtk-enginesOf course the trick with that is seeing it long enough to actually do something about it, because Portage almost immediately pushes it out of the scrollback buffer with the output from cleaning old versions.EdSchouten wrote:Here a message that was on screen (and that you ignored):
Code: Select all
For gtk themes to work correctly after an update, you might have to rebuild your theme engines. Executing 'qpkg -f -nc /usr/lib/gtk-2.0/2.2.0/engines | xargs emerge' should do the trick if you upgrade from gtk+-2.2 to 2.4 (requires gentoolkit).