I installed Opera 7.10 B1 by downloading the static package manually from the regular download pages at www.opera.com, and trivially modifying the 6.12 ebuild in a local portage overlay. I had xfree-4.2.1-r2 installed at the time, and Opera was working fine. I then emerged xfree-4.3.0-r1, after which Opera's UI is severely crippled, as shown in the screenshot I will attach. The same upgrade lot also involved these upgrades: freetype-2.1.3-r2 => freetype-2.1.4 nvidia-kernel-1.0.3123-r2 => nvidia-kernel-1.0.4349-r1 nvidia-glx-1.0.3123 => nvidia-glx-1.0.4349 vte-0.10.25 => vte-0.10.26 libao-0.8.3 => libao-0.8.3-r1 xvid-0.9.0 => xvid-0.9.1 xloadimage-4.1 => xloadimage-4.1-r1 svgalib-1.4.3-r4 => svgalib-1.9.17-r1 ... all of which seem either likely or certain to be innocent of this crime, since it apparently involves layout computation errors for UI elements. (But I'm not familiar enough to be certain of that, so I listed them here for your judgment.) It also seems unlikely that this is Opera's fault, since it was working just fine before the xfree-4.3.0-r1 upgrade (but again, that's not a sure bet -- and I have not seen any other applications undergo these severe layout defects; I haven't been testing for very long after the xfree upgrade) The screenshot I'm attaching is taken after I tried emerging the Opera ebuild in Bug 19154, instead of the one I fudged in. That's version 7.1.0 TP4, whereas the one I first emerged was called 7.1.0 B1 and was not available in the same place (snapshots) on opera.com; don't know why. The layout defects in 7.1.0 B1 were very similar but not identical; none of the icons of the top bar were visible at all in that version, and the Exit Opera dialog box was two or three times wider than the screen (and a lot of UI elements were extremely elongated as well). Reproducible: Always Steps to Reproduce: 1. start with xfree-4.2.1-r2 installed 2. emerge Opera 7.1.0, e.g. using the ebuild in Bug 19154 3. emerge xfree-4.3.0-r1 4. start up opera and gaze at it in open-mouthed horror Actual Results: The Opera UI looked as shown in the screenshot. Web page rendering was OK, except that form elements appeared to suffer from the layout problems as well as the UI elements outside the webpage view. Expected Results: It should have laid out and rendered its UI elements normally. Configuration changes have already been detailed, above. The output from "emerge info" follows: Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r4) ================================================================= System uname: 2.4.20-gentoo-r2 i686 AMD Athlon(tm) XP 2000+ GENTOO_MIRRORS="http://ftp.linux.is/gentoo http://gentoo.oregonstate.edu/ http://www.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg libg++ mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gdbm berkdb slang readline arts tetex svga tcltk java guile mysql X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl mozilla" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O3 -pipe -fforce-addr -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4" CXXFLAGS="-march=athlon-xp -O3 -pipe -fforce-addr -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
Created attachment 10654 [details] Screenshot of the bogus layout/rendering Attaching a screenshot of the bogus layout/rendering, as promised.
Wrong assignment. What's kde to do with this?
Sorry about the wrong initial assignment; at first glance KDE seemed like the "least inappropriate" component, but given the implied stupidity of that choice, I assume "Unspecified" is less inappropriate. Maybe there should be a specific component for x11-*/*? I'll submit that to the Gentoo Linux Bugzilla product, for somebody to consider.
I just added the ebuild for 7.10 (bug 19154), and it looks fine under Xfree 4.2. Have you tried removing ~/.opera (just a shot in the dark).
Yes, opera 7.10 looked fine under Xfree 4.2 for me too. It was under Xfree 4.3 that I got these problems I'm reporting. Please try that. I'll try removing ~/.opera when I get home (actually already tried it remotely from work and it worked fine, but that was dumb; I was testing in my X server at work, not the gentoo xfree-4.3.0-r1 :)
I have this exact same problem on my system after emerging opera 7.10. I too have xfree 4.3 My opera looks exactly like this attachment in this bug report.
Removing ~/.opera did nothing (oh well, it was a long shot anyway :)
Apparently the opera 7.10 that has just appeared in portage has a similar problem: the inital screen and the configure screen that pops up on first start are some 8 times the width of the screen. the webpage seems to render okay, but the UI is completely invisible and garbled. Vag
Confirm the screenshot under xfree-4.3.0-r2, though I do not even have the menu-bar text. I also had the same problem under 4.2.1. Maybe it isn't 4.3.0 specific?
hi Seems like emerging the latest freetype and fontconfig might help. I emerged: media-libs/freetype-2.1.4 media-libs/fontconfig-2.1.94-r1 gl
That's very right, thanks! I had already emerged freetype 2.1.4, and Opera was still screwy. After emerging fontconfig 2.1.94-r1, Opera behaves fine. So I guess the appropriate dependencies should be added to the Opera 7.10 B1 ebuild, to resolve this bug?
yup the fontconfig update worked for me as well. Although I get a segment fault when the ebuild script tries to run fc-cache -f but that's another issue... :) Still works :)
Works for me.
Should be fixed in 7.10_beta1-r2. Thanks for the good work/feedback to all!
