Closed Bug 124357 Opened 23 years ago Closed 23 years ago

crash on 0.9.8 startup

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: sagiem, Assigned: blizzard)

Details

From Bugzilla Helper: User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.7-10 i686) BuildID: 2002020511 When starting up Mozilla, it crashes with a segmentation fault. Mozilla was installed using the i386 rpm found at ftp.mozilla.org. When trying to run it with parameters, I get: ************************************************** nsNativeComponentLoader: GetFactory(/usr/lib/mozilla/components/libtimer_gtk.so) Load FAILED with error: /usr/lib/mozilla/components/libtimer_gtk.so: cannot open shared object file: No such file or directory ************************************************** Reproducible: Always Steps to Reproduce: Run Mozilla Actual Results: Mozilla crashes whenever started up. For a second you can see the frame of the Mozilla window, but then it's gone. $ mozilla Segmentation fault I should add that when I ran galeon (1.1.3) using this mozilla build, galeon ran and started loading the web page, but didn't show it in the page's tab (the tab was empty) - Made me think the problem is maybe in the mozilla rendering system. When I tried clicking on the page, galeon crashed with a segfault.
I am seeing the same thing. I downloaded the 0.9.8 RPM for Redhat 7.x. When I ran "mozilla &" a window attempts to open, then quickly closes with a "Segmentation fault" in the terminal (no core dump to be found). Running "mozilla -v" returns the following error: ************************************************** nsNativeComponentLoader: GetFactory (/usr/lib/mozilla/components/libtimer_gtk.so) Load FAILED with error: /usr/lib/mozilla/components/libtimer_gtk.so: cannot open shared object file: No such file or directory ************************************************** Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020205, build 2002020511 I checked /usr/lib/mozilla/components and sure enough there is no libtimer_gtk.so there. My machine is Redhat Linux 7.2 (2.4.9-21) and I'm running KDE 2.2.2.
sounds like an rpm problem; installer builds work fine.
Assignee: asa → blizzard
There is so timer_gtk module anymore. I don't know why it's trying to load it. Are you sure you don't have some old rpms installed somewhere?
When did the timer module go away? I ran 0.9.7 for weeks without a problem. To clarify my system's history with Mozilla: 1) Fresh install with Redhat 7.2 2) Mozilla (0.9.2 which came with 7.2) was upgraded to 0.9.7 a few weeks ago with an "rpm -Uvh --nodeps" (the nodeps option was to suppress a complaint about galeon needing 0.9.2). 3) 0.9.7 ran fine for weeks 4) This morning, did the same thing again.. "rpm -Uvh --nodeps" to upgrade to 0.9.8. Timer module problem starts here. Please advise.
I think you've got something bad in your enviroment or something bad installed in /usr/lib/mozilla. That .so vanished between 0.9.7 and 0.9.8 - it's not supposed to be there anymore so I'm not sure what's trying to load it. What does: rpm -qa|grep mozilla say?
rpm -qa | grep -i moz kdebindings-kmozilla-2.2.2-1 nautilus-mozilla-1.0.4-43 mozilla-0.9.8-0 An strace of "mozilla -v" contains this line: open("/usr/lib/mozilla/components/libtimer_gtk.so", O_RDONLY) = -1 ENOENT (No such file or directory) I rm -rf'd my .mozilla directory (set up when I ran 0.9.7) in case there was something wrong in there. Problem persists.
What does: rpm -V mozilla say?
rpm -V mozilla doesn't return anything. But "strings /usr/lib/mozilla/component.reg | grep time" returns: @mozilla.org/network/protocol;1?name=datetime @mozilla.org/network/protocol;1?name=datetime GTK timer rel:libtimer_gtk.so @mozilla.org/timer;1 @mozilla.org/timer;1 rel:libtimer_gtk.so @mozilla.org/js/xpc/RuntimeService;1 @mozilla.org/js/xpc/RuntimeService;1 So you can see there's a reference in this file to libtimer_gtk.so. So I just did "rm component.reg && mozilla" and Mozilla started fine this time. I'm sure this is a big gotcha for Redhat 7.2 users who want to upgrade via rpm - Uvh. Can you somehow incorporate a check for this problem into the RPM?
It should have been rebuilt at install time. I haven't had any problems with this and this is the only report I've seen of it. /usr/lib/mozilla/rebuild-databases.sh should have cought this.
I suspect that the original reporter of the bug probably did an rpm -Uvh upgrade as I did, but he should probably confirm this.
Confirming, my history with mozilla is exactly the same as pluto@4motion.org described at #4.
Also, fully uninstalling mozilla0.9.7 (using rpm -e) and then installing 0.9.8 from scratch made it work perfectly.
This bug or one very much like it appears to be present in the Mac version as well. I've gone from very stable with 0.9.7 to splash screen followed by immediate exit with type 2 error for 0.9.8. That's repeatable on 8.6, anecdotally reported on 9.1, G3 boxen both
I have find exactly the same problem. According to what I have read, what should I do? Just removing the component.reg file?
#14, Either completely remove mozilla-0.9.8 (using "rpm -e") and then install it from scratch (worked for me), or download a non-rpm package (which might cause problems on an rpm-based dist).
For me, the following has worked: - As root, remove the component.reg file. - Then start mozilla as root and the component.reg file is recreated (as root since other user probably has no privileges to create the file) - After that, a normal user can run Mozilla. Thank you for the help.
Is it safe to mark this WORKSFORME or should we keep this bug around ... ?
this was also reported in bug 125325 and bug 125433
Marking invalid - rpm problem, not mozilla.org related. Build is too old to be useful.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.