Hello, I am unable to start the new Opera ... it complains: # opera ERROR: ld.so: object 'libjvm.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libawt.so' from LD_PRELOAD cannot be preloaded: ignored. /opt/opera/lib/opera/8.51-20051114.5/opera: error while loading shared libraries: libqt-mt.so.3: cannot open shared object file: No such file or directory I checked this with ldd .. # ldd /opt/opera/lib/opera/8.51-20051114.5/opera linux-gate.so.1 => (0xffffe000) libpthread.so.0 => /lib32/tls/libpthread.so.0 (0x55588000) libqt-mt.so.3 => not found libX11.so.6 => /emul/linux/x86/usr/lib/libX11.so.6 (0x5559b000) libz.so.1 => /emul/linux/x86/lib/libz.so.1 (0x55665000) libdl.so.2 => /lib32/libdl.so.2 (0x55676000) libstdc++.so.5 => /emul/linux/x86/usr/lib/libstdc++.so.5 (0x5567a000) libm.so.6 => /lib32/tls/libm.so.6 (0x5572e000) libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/32/libgcc_s.so.1 (0x55751000) libc.so.6 => /lib32/tls/libc.so.6 (0x5575a000) /lib/ld-linux.so.2 (0x55555000) ... hm, libqt-mt.so.3 not found, but it is installed: # locate libqt-mt.so.3 /usr/qt/3/lib64/libqt-mt.so.3 /usr/qt/3/lib64/libqt-mt.so.3.3.4 /usr/qt/3/lib64/libqt-mt.so.3.3 ... and ldconfig knows about it: # ldconfig -v ... /usr/qt/3/lib: libqui.so.1 -> libqui.so.1.0.0 libqt-mt.so.3 -> libqt.so.3.3.4 ... - not to forget, that other programs use it: # ldd /usr/kde/3.4/bin/konqueror | grep mt libqt-mt.so.3 => /usr/qt/3/lib64/libqt-mt.so.3 (0x00002aaaac85f000) ... so I consider this to be Opera bug (?) Reproducible: Always Steps to Reproduce:
still a problem?
# emerge --sync ... to get fresh portage (8:35 24.12.2005 CET) # emerge -av opera These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] www-client/opera-8.51 +kde +qt +spell -static 0 kB ... $ opera ERROR: ld.so: object 'libjvm.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object 'libawt.so' from LD_PRELOAD cannot be preloaded: ignored. /opt/opera/lib/opera/8.51-20051114.5/opera: error while loading shared libraries: libqt-mt.so.3: cannot open shared object file: No such file or directory ... oh yeah, it looks like it is still there please tell me if you need some additional info - I am not so experienced to debug this myself meanwhile, some new posts appeared in the forums on the web, so after some googling: the solution may be to install static version of opera or 32bit version of libqt-mt ... # USE="static" emerge -av opera These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] www-client/opera-8.51 +kde +qt +spell +static* 5,674 kB $ opera ... well, this works, so, if the first problem cannot be solved, then the workaround may be to allow to install only the static version on 64bit system
you are running amd64? then you should have app-emulation/emul-linux-x86-qtlibs installed? do you have them? at least there is a dep in the opera ebuild.
(In reply to comment #3) > you are running amd64? at least that's what the cpuinfo says ;-) > then you should have app-emulation/emul-linux-x86-qtlibs > installed? do you have them? # emerge -s emul-linux-x86-qtlibs Searching... [ Results for search key : emul-linux-x86-qtlibs ] [ Applications found : 1 ] * app-emulation/emul-linux-x86-qtlibs Latest version available: 2.1.1 Latest version installed: 2.1.1 ... looks like they are installed > at least there is a dep in the opera ebuild. well, I have overlooked this - so the 32bit libqt-mt should already be installed, as I confirm above ... strange ...
so, I have tried # emerge -av --oneshot emul-linux-x86-qtlibs These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] app-emulation/emul-linux-x86-qtlibs-2.1.1 6,969 kB ... # emerge -av opera These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] www-client/opera-8.51 +kde +qt +spell -static* 0 kB ... and it works now it seems that something was rotten in my system and that Opera is ok - sorry but even if I have removed the problem, it is still unclear how it was possible? ... I would expect that re-emerging a package (or running revdep-rebuild) will fix any library issues, not that I will have to re-emerge the libraries manually - could it be fixed or is that a "feature" of non-compiled packages?
maybe some magic of the emul-libs, no idea ;) but happy that it works now for you.