recent ebuilds of opera assume that java is installed and try to preload it . They should check to see if there is something to preload. # java workaround sed -i -e 's:LD_PRELOAD="${OPERA_JAVA_DIR}/libawt.so":LD_PRELOAD="$LD_PRELOAD"\:"${OPERA_JAVA_DIR}/libawt.so":' ${D}/opt/opera/bin/opera bash-3.1#ERROR: ld.so: object 'libjvm.so' from LD_PRELOAD cannot be preloaded: i gnored. ERROR: ld.so: object 'libawt.so' from LD_PRELOAD cannot be preloaded: ignored. bash-3.1# I have opera configured internally with java off . Could forcing JAVA enabled maybe one cause of frequent crashes of opera? -e 's:#\(OPERA_FORCE_JAVA_ENABLED=\):\1:' \ -e 's:#\(export LD_PRELOAD OPERA_FORCE_JAVA_ENABLED\):\1:' \ Thanks
does opera not start for you or are those messages just on the console? If they are only on the console it's completly harmless, the check has always been in the ebuild.
No, opera starts OK. I have ignored this for a while but I have one or two crashes a day on opera and thought this may be a cause since I imagine it's a less tested senario with most users probably having some form of java on the system. This may be due to the GLIB leak that 8.52 is supposed to fix. Once the ebuild stops sandboxing I'll test that out. Thanks for your help.
A couple of versions onward and with no information that actually shows that the lack or presence of libawt caused opera to crash, I am closing this bug. I have never experienced this problem myself, I must say, and I cannot reproduce it even now.
