Firefox: Segmentation Fault Line 131

Sigi · 2006-11-13 01:13:06

I'm once again having this strange line-131 segfault problems described above. (using firefox 2.0 out of current on a self-created liveCD on on intel-based Computer) I hoped they would be solved now...

iphitus · 2006-11-13 01:29:50

Sigi wrote:

I'm once again having this strange line-131 segfault problems described above. (using firefox 2.0 out of current on a self-created liveCD on on intel-based Computer) I hoped they would be solved now...

just means that something's wrong with firefox and it's segfaulting. the line131 thing is unrelated -- it just appears cause the actual firefox binary (firefox-bin) is run from a script (firefox, run-mozilla.sh).

go through your extensions, or maybe take a look at the liveCD environment as something there could be causing this instability. what are you trying to do when it crashes? maybe its trying to write something where it cant on the liveCD?

James

Sigi · 2006-11-13 02:22:37

The LiveCD was created using gradgrinds larch scripts which simplified do the following tasks:
- install Arch base into a folder
- install a set of packages over the base install
- create a squashed file out of that directory.
- do the same for an overlay directory.
- put this two squashed files and a bootloader into an iso file.

What I want to say is that this is entirely a clean, fresh ArchLinux installation out of the current and extra repositories. There are no firefox extensions/add-ons installed and the error also occures if I remove the whole .mozilla folder out of the users home dir before I try to launch firefox for the first time.

How can I find the "real problem" that causes this error?

edit: one thing I forgot to mention:
Firefox doesn't crash on some sites, it doesn't start at all!

edit2:
starting firefox-bin directly leads to this error:

error while loading shared libraries: libmozjs.so: cannot open...

libmozjs.so is part of the firefox package and located in /opt/mozilla/lib/firefox-2.0, where it belongs to... The file is readable by the user. Why is firefox unable to find this file?

iphitus · 2006-11-13 05:14:02

Sigi wrote:

The LiveCD was created using gradgrinds larch scripts which simplified do the following tasks:
- install Arch base into a folder
- install a set of packages over the base install
- create a squashed file out of that directory.
- do the same for an overlay directory.
- put this two squashed files and a bootloader into an iso file.
edit2:
starting firefox-bin directly leads to this error:
error while loading shared libraries: libmozjs.so: cannot open...
libmozjs.so is part of the firefox package and located in /opt/mozilla/lib/firefox-2.0, where it belongs to... The file is readable by the user. Why is firefox unable to find this file?

not sure. it could be a unionfs bug. if you've used Archie, you will have seen that these can manifest themselves in very unusual ways, like Gaim not showing the available protocols in it's add profile list when run from a unionfs.

James

JGC · 2006-11-13 07:35:17

Running firefox-bin directly is not supported, as you need to have LD_LIBRARY_PATH customized, which the firefox launcher script does for you. Besides the LD_LIBRARY_PATH, the launcher script also makes it possible to start multiple firefoxes, where the -bin command pops up with "another session is active, can't start".

Sigi · 2006-11-13 14:15:04

I'll see what happens when I start the firefox-bin after specifying the LD_LIBRARY_PATH. I'll report back later.

Thanks for the help so far!

gradgrind · 2006-11-13 16:01:03

iphitus wrote:

not sure. it could be a unionfs bug. if you've used Archie, you will have seen that these can manifest themselves in very unusual ways, like Gaim not showing the available protocols in it's add profile list when run from a unionfs.

I know unionfs has had some pretty awkward bugs and probably still has some, but I'm not sure that it's fair blaming it for the problem with gaim - that arises because of gaim's use of binreloc (which can be switched off by a configure option), in conjunction with unionfs's rearranged file-system, which is pretty much unavoidable if you want to use unionfs in this way, and not actually a bug.

lilsirecho · 2006-11-13 16:07:03

Sigi:

Didn't get firefox to show on my Larch2.0 boot with firefox and thunderbird. It may be a seamonkey requirement.

Sigi · 2006-11-13 16:13:08

lilsirecho wrote:

Sigi:
Didn't get firefox to show on my Larch2.0 boot with firefox and thunderbird. It may be a seamonkey requirement.

Sorry, I don't understand the meaning of your sentence.
Have you been able to install firefox? Does it run? It installs here with all the dependencies and so on, it just doesn't work.

gradgrind · 2006-11-13 16:32:45

I just ran a quick test (default larch profile) and didn't notice any problems: amazon.de, archlinux.org, freshmeat.net, distrowatch.com all ok. I guess that doesn't help you much, though. It just makes it all the more puzzling.

lilsirecho · 2006-11-13 16:44:10

Sigi;

I had firefox in the added packs and it didn't show up as an internet option in KDE.

I haven't had time to redo the install as yet. I may try using union from my repo on the other DVD which has all the packages available. It would be an earlier version.

Sigi · 2006-11-13 17:49:53

the packagename of firefox changed from "mozilla-firefox" to "firefox". You could try to put "firefox" or "firefox-i18n" into the addedpacks-file (same for thunderbird, btw). This change isn't that important because "firefox" replaces "mozilla-firefox" automatically on install, at least for me. Maybe it's just the menu entry that is missing. Have you tried to run firefox from a console?

Sigi · 2006-11-13 18:29:30

Ok, I've exported the correct LD_LIBRARY_PATH manually now and ran /opt/mozilla/lib/firefox-2.0/firefox-bin. It now reports "Speicherzugriffsfehler" = "Segmentation fault".
Does anybody know how to make firefox-bin more verbose?

I'll delete my firefox package in the cache, redownload it and rebuild my LiveCD with the new package in between...

lilsirecho · 2006-11-13 18:30:37

Sigi:

Not much help here. Tried from console with no luck.

Tried seamonkey also...no luck.

None of the mozilla related items opens in my Larch boot. They show up in KDE but do not execute.

I loaded the latest via pacman...firefox 2.0-1 and it still doesn't open.

I loaded seamonkey via pacman and it doesn't open but is listed in KDE.

gradgrind · 2006-11-13 21:08:31

How weird! I am posting this from firefox (a.k.a. Bon Echo!), started from the KDE internet menu on a larch live CD system, built yesterday ...

So what's the difference? ...

gradgrind · 2006-11-13 21:33:22

It's still running!

Although it took rather a long time to start, I must say I rather like the look of it, it's quite pleasant to use. But of course if it only works for some of us, that's a bit of a problem ...

lilsirecho · 2006-11-13 21:39:29

Gradgrind;

Tried running the console command for run-mozilla.sh and received ....cannot execute.

Mebbe a clue therein.....

Opera is fine.

lilsirecho · 2006-11-13 21:48:10

Gradgrind;

Initially, I found no reference to firefox in /OPT.....

After running ....pacman -Sy mozilla-firefox.... to enter the package via unionfs, the /OPT contained the mozilla data.

However, going back to hda3 ArchImage which loaded the packages, I found the correct data in /OPT which should have loaded into the .iso.

I may have to rerun and check that out again with a new Larch DVD-RW run.

lilsirecho · 2006-11-13 22:07:40

Reburned the .iso, rebooted and found no /opt/mozilla data so the problem lies in the mklive sequence into the .iso.

Might I enter mklive directly to restart that sequence?

lilsirecho · 2006-11-13 22:49:06

Found the problem...Old ArchImage still in the machine was picked up instead of the new ArchImage package.

Sorry for the oops! :oops:

lilsirecho · 2006-11-13 23:46:43

Gradgrind;

Reinstalled Larch with correct ArchImage and am in firefox with this post with no problem apparent.

Will see how thunderbird runs.

lilsirecho · 2006-11-14 00:14:54

FWIW, the package list for my Larch follows;

# These are needed to build a live CD
squashfs-tools
initcpio_larch

# You need a kernel.
# 'kernel26' needs 'squashfs' and 'unionfs'
# 'kernel26beyond' doesn't
kernel26beyond

#kernel26
#squashfs
#unionfs

# To eject a cd
# eject - no longer used, cdrecord is used instead
cdrtools

# Highly recommended
larchin
#larch

# Might be useful, but package only in AUR ...
#xkmap

# Needed by the installer
python
# dialog is now in basepacks!
# If using 'abs':
cvsup

# Useful for use as installer, etc.
ntfsprogs
parted
mdadm
lvm2
hwd
qtparted

# generally useful tools which don't require X
openssh
dosfstools
lynx
mc
unzip
zip
fakeroot
alsa-lib
alsa-oss
alsa-utils
cdparanoia
cdrdao
dvd+rw-tools
cups
gutenprint

# Xorg packages
xorg
xorg-input-drivers
xorg-video-drivers
# Needed by ttf-ms-fonts:
xorg-clients

# X apps
desktop-file-utils
gimp

# KDE packages
k3b
kde
mplayer
kdewebdev
scribus

# OpenOffice
#openoffice-base

ttf-ms-fonts

vlc
mozilla-firefox
mozilla-thunderbird

Perhaps this listing will help resolve difficulties that others are having with firefox. It runs OK with these packages, perhaps not with others added.

Sigi · 2006-11-14 00:32:48

hm, you use the beyond kernel. Am I the only one using stock kernel here? ;-)

An strace revealed that firefox-bin stopps after three gettimeofday calls.

I'll try beyond now, and later maybe ck. Strange...

gradgrind · 2006-11-14 05:52:51

Sigi wrote:

hm, you use the beyond kernel. Am I the only one using stock kernel here? ;-)
An strace revealed that firefox-bin stopps after three gettimeofday calls.
I'll try beyond now, and later maybe ck. Strange...

I'm using stock kernel.

Sigi · 2006-11-14 08:47:02

Well, beyond didn't change anything here. Weird, I'm wondering what I am doing differently...

I didn't test a burnt image yet, I only ran the iso in qemu. I really don't want to go back to an old firefox build on my LiveCD.

Arch Linux

#26 2006-11-13 01:13:06

Re: Firefox: Segmentation Fault Line 131

#27 2006-11-13 01:29:50

Re: Firefox: Segmentation Fault Line 131

#28 2006-11-13 02:22:37

Re: Firefox: Segmentation Fault Line 131

#29 2006-11-13 05:14:02

Re: Firefox: Segmentation Fault Line 131

#30 2006-11-13 07:35:17

Re: Firefox: Segmentation Fault Line 131

#31 2006-11-13 14:15:04

Re: Firefox: Segmentation Fault Line 131

#32 2006-11-13 16:01:03

Re: Firefox: Segmentation Fault Line 131

#33 2006-11-13 16:07:03

Re: Firefox: Segmentation Fault Line 131

#34 2006-11-13 16:13:08

Re: Firefox: Segmentation Fault Line 131

#35 2006-11-13 16:32:45

Re: Firefox: Segmentation Fault Line 131

#36 2006-11-13 16:44:10

Re: Firefox: Segmentation Fault Line 131

#37 2006-11-13 17:49:53

Re: Firefox: Segmentation Fault Line 131

#38 2006-11-13 18:29:30

Re: Firefox: Segmentation Fault Line 131

#39 2006-11-13 18:30:37

Re: Firefox: Segmentation Fault Line 131

#40 2006-11-13 21:08:31

Re: Firefox: Segmentation Fault Line 131

#41 2006-11-13 21:33:22

Re: Firefox: Segmentation Fault Line 131

#42 2006-11-13 21:39:29

Re: Firefox: Segmentation Fault Line 131

#43 2006-11-13 21:48:10

Re: Firefox: Segmentation Fault Line 131

#44 2006-11-13 22:07:40

Re: Firefox: Segmentation Fault Line 131

#45 2006-11-13 22:49:06

Re: Firefox: Segmentation Fault Line 131

#46 2006-11-13 23:46:43

Re: Firefox: Segmentation Fault Line 131

#47 2006-11-14 00:14:54

Re: Firefox: Segmentation Fault Line 131

#48 2006-11-14 00:32:48

Re: Firefox: Segmentation Fault Line 131

#49 2006-11-14 05:52:51

Re: Firefox: Segmentation Fault Line 131

#50 2006-11-14 08:47:02

Re: Firefox: Segmentation Fault Line 131

Board footer