Bugzilla Bug 157359

I just picked up the gtk-engines 2.8.2 stable update for AMD64. Unfortunately,
it broke the UI of mozilla-firefox and mozilla-firefox-bin. Nothing else is
broken; I re-emerged gtk-engines and everything that installs to
/usr/lib/gtk-2.0/2.10, and rebuilt all the emul-linux-x86 X/gtk-related
packages. However, though the rest of the Gnome environment displays normally,
including nautilus windows, Gnome applications, menus, etc., ff and ff-bin are
broken. Only errors I could find are in ~/.xsession-errors:

/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:59: error: unexpected identifier
`animation', expected character `}'
No running windows found
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:59: error: unexpected identifier
`animation', expected character `}'
No running windows found
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:59: error: unexpected identifier
`animation', expected character `}'

Opening the file doesn't show anything too unusual, except that the '}' is on
its own line, rather than on the same line as 'animation = FALSE'.

BEFORE screenshot (gtk-engines-2.6.9):
http://dev.gentoo.org/~nightmorph/Screenshot.png
AFTER screenshot (gt-engines-2.8.2):
http://dev.gentoo.org/~nightmorph/broken-firefox.png

emerge --info:

Portage 2.1.1-r2 (default-linux/amd64/2006.1, gcc-4.1.1, glibc-2.4-r4,
2.6.18-gentoo-r3 x86_64)
=================================================================
System uname: 2.6.18-gentoo-r3 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor
4600+
Gentoo Base System version 1.12.6
Last Sync: Wed, 06 Dec 2006 06:30:01 +0000
ccache version 2.3 [enabled]
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: 1.3.7, 2.0.30
dev-lang/python:     2.4.3-r4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.3
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.60
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r4
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf
/etc/java-config/vms/ /etc/revdep-rebuild /etc/splash /etc/terminfo"
CXXFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer"
FEATURES="autoconfig ccache collision-protect distlocks metadata-transfer
parallel-fetch sandbox sfperms strict"
LANG="en_US.UTF-8"
LC_ALL="en_US.UTF-8"
LINGUAS="en"
MAKEOPTS="-j4"
USE="X a52 aac acpi alsa amd64 berkdb bitmap-fonts bzip2 cairo cdr cli cracklib
crypt cups curl dbus dlloader dri dvd dvdr elibc_glibc encode firefox
foomaticdb fortran gdbm gnome gpm gtk gtk2 gtkhtml hal iconv
input_devices_keyboard input_devices_mouse isdnlog jpeg kernel_linux lame
libg++ libwww linguas_en lm_sensors mad mime mozsvg mp3 mpeg ncurses nls nptl
nptlonly nvidia ogg opengl pam pcre pdf perl png ppds pppd python quicktime
readline reflection session spell spl ssl svg tcpd truetype truetype-fonts
type1-fonts udev unicode usb userland_GNU video_cards_nvidia xml xorg zlib"

In my experience, gtk-engines-2.8.2 was rushed to stabilization on AMD64. It's
definitely broken -- at least, the clearlooks theme update is.

And yes, downgrading to gtk-engines fixes the problem with firefox/firefox-bin,
no recompiling of other packages is necessary.

(In reply to comment #1)
> And yes, downgrading to gtk-engines fixes the problem with firefox/firefox-bin,
> no recompiling of other packages is necessary.
> 

It can be fixed by emerging the latest ~arch versions of:
emul-linux-x86-gtklibs
emul-linux-x86-xlibs
emul-linux-x86-baselibs

and then recompiling everything that builds in /usr/lib/gtk-2.0/foo. Thanks to
Luis Medinas (metalgod) on IRC for the suggestion. So, can we AMD64 users get
those packages stabilized, as they're built with gtk+-2.10, not gtk+-2.8?

Reassigning as requested by metalgod.

yes.. I know its early.. but I stabled it anyways... we need to follow GTK+
2.10