segmentation fault output on trying to run opera !
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
segmentation fault output on trying to run opera !
I am currently running Fedora 7 and have been trying to run opera but it outputs the message below.
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.
Segmentation fault
I managed to configure opera to point to the right place in regards to libjvm.so and libawt.so by altering the shell script /usr/bin/opera. The only remaining problem is I can't actually run opera because of the segmentation fault. When I delete the directory ./opera in my home directory and try to run opera it prints the error message below and terminates.
Afterwards if I try running opera without first deleting the ./opera directory it simply outputs 'Segmentation fault' and then terminates. I have even tried to install the static rpm package as opposed to the dynamic package. The weird bit is that version 9.21 works but I want to use version 8.54 because the latest version works slower on my system. There is about 1 to 3 second(s) delay when using the user interface like navigating between tabs for example. The problem is driving me crazy as opera is my preferred web browser because of certain features, but I will have to resort to firefox if need be if I can't find a solution.
The first thing that I would do is put the original /usr/bin/opera back. Hopefully you made a backup before you edited it.
The way that I handle the few cases that an application is looking for a library in the wrong place is to make a soft link in the area that the application is looking that points to the actual location of the library. I use soft links so I that know which name is the original and which is the one that I made.
Did you install Opera from the Fedora RPM repository or from a kit at the Opera web site? I always try to use applications that are in my distro's package repository because I know that the developers have tested it on my distro. If you install software from the application's web site you run the risk of having the application written for a slightly different file arrangement. It's a minor issue but it's still worth avoiding if you can.
And, as always, since Fedora Core is a development distribution this may be due to something in Fedora that will eventually be fixed. I advise everyone to use a stable distribution, not a development distribution.
Last edited by stress_junkie; 07-14-2007 at 08:29 PM.
Already thought about creating a symlink to the library files. The reason I didn't create one is because I don't know exactly where opera is looking for these library files by default so I modify one line in /usr/bin/opera as shown below.
To: LD_PRELOAD="/usr/java/j2re1.4.2_15/lib/i386/client/libjvm.so:/usr/java/j2re1.4.2_15/lib/i386/libawt.so:${OPERA_LD_PRELOAD}"[/COLOR]
This had the effect of removing the two errors that where reported by opera as shown below.
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.
Segmentation fault
This had left me with the segmentation fault as shown in the previous post. I had the further idea of removing the xine multimedia package because the segmentation fault has output a few lines refering to xine library files. Now when I try to run opera it gives the NEW output as shown below.
NPP_GetValue()
NPP_GetValue()
Segmentation fault
Furthermore, I know that Fedora distributes three types of packages from its own repository which are stable, development, and testing. The development and testing reposirories are disabled by default in yum. I only use the stable packages from Fedora and do not generally use RPM packages if they are known to be unstable. I also know that Fedora does not distribute opera so I got a RPM package directly from the opera website. Also note that I have the static RPM version installed on my system.
Finally, I had "Fedora Core 4" on my system about two weeks ago and "Opera 8.54" worked fine until I installed "Fedora 7". Now "Opera 8.54" won't work on "Fedora 7" but "Opera 9.21" does work which is the latest version. The problem with the latest version is that it runs slow on both "Fedora Core 4" and "Fedora 7". For some reason "Opera 8.54" refuses to work on "Fedora 7" for some strange reason.
There are different options on the opera website for the different FC versions. I however could only find the 9 series for download and not the 8 series that you want to use. But there might also have been a similar difference for the 8 series which basically means that a version for FC4 will not run on FC7.
I have the feeling that there are some differences in one or more libraries that cause the problems.
This is common to many Linuxes; I myself had this problem on Ubuntu. I don't remember the solution, but I can tell you to search the Opera for UNIX forum, because that's what I did and how I solved it.
Yep, I noticed that as well. I have also taken a look in the opera archives at http://arc.opera.com/pub/opera/linux but for some reason they only provide one RPM package along with two tarballs and debian package. I was actually thinking of maybe trying to build a RPM package but opera also does not provide the .spec file neither which I think they should at least have done to enable you to build the RPM package for the target linux distribution. Do you know of anyway to automatically produce a .spec file ?
AlucardZero:
Chers ! I will also try the Opera for UNIX forum and check it out !
Sorry, but can't help you there. I would try to find the correct versions of the libraries and add symlinks for opera to those; however not sure if it's possible to do so.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.