Closed Bug 204585 Opened 23 years ago Closed 23 years ago

Mozilla 1.3 does not start up: Segmentation fault

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 195601

People

(Reporter: alberto.marchamalo, Assigned: asa)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 Build Identifier: http://www.mozilla.org/releases/#1.3 I have been using Mozilla 1.3 without problems during at least one month and now when I try to start Mozilla I get this error [alberto@peggy alberto]$ /usr/local/mozilla/mozilla & [1] 1312 [alberto@peggy alberto]$ /usr/local/mozilla/run-mozilla.sh: line 454: 1318 Segmentation fault "$prog" ${1+"$@"} [1]+ Exit 139 /usr/local/mozilla/mozilla Reproducible: Always Steps to Reproduce: 1./usr/local/mozilla/mozilla & 2. 3. Actual Results: Mozilla does not start up Expected Results: Tostart up and work correctly
Can you try with a new profile ? (run mozilla with -P flag and create a new profile) Or else, provide a stacktrace of the crash. cd to the mozilla directory and run LD_LIBRARY_PATH=`pwd` gdb mozilla-bin when you are in gdb type 'run' and return, when it give you a segmentation fault, type 'bt' (for backtrace) and then return.
Dave I did what you told me and: 1) The answer is the same when I use the -P flag, that is: Segmentation fault 2) The backtrace result is this, what should I do now? [alberto@peggy alberto]$ cd /usr/local/mozilla/ [alberto@peggy mozilla]$ LD_LIBRARY_PATH=`pwd` gdb mozilla-bin GNU gdb Red Hat Linux (5.2.1-4) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"...(no debugging symbols found)... (gdb) run Starting program: /usr/local/mozilla/mozilla-bin (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 1298)] (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 1298)] 0x400d3b0d in pthread_mutex_init () from /lib/i686/libpthread.so.0 (gdb) bt #0 0x400d3b0d in pthread_mutex_init () from /lib/i686/libpthread.so.0 #1 0x4102e768 in __FCDeleteKey () from /usr/local/mozilla/components/talkback/talkback.so #2 0x4101b62e in NSGetModule () from /usr/local/mozilla/components/talkback/talkback.so #3 0x4101f414 in NSGetModule () from /usr/local/mozilla/components/talkback/talkback.so #4 0x4101f567 in __FCInitialize () from /usr/local/mozilla/components/talkback/talkback.so #5 0x400c6edb in NSGetModule () from /usr/local/mozilla/components/libqfaservices.so #6 0x400c7376 in NSGetModule () from /usr/local/mozilla/components/libqfaservices.so #7 0x400c73cb in FCInitialize () from /usr/local/mozilla/components/libqfaservices.so #8 0x400c68d4 in nsQfaServicesImpl::StartService () from /usr/local/mozilla/components/libqfaservices.so #9 0x400c69a3 in nsQfaServicesImpl::Observe () from /usr/local/mozilla/components/libqfaservices.so #10 0x40747c55 in NSGetModule () from /usr/local/mozilla/components/libembedcomponents.so #11 0x080578b6 in getCountry () #12 0x080584d5 in main () #13 0x420158f7 in __libc_start_main () from /lib/i686/libc.so.6
And you haven't upgraded anything on your system (like any libs) since this started happening ? What's wierd is that the crash seems to be happening in the talkback module which is the crash reporting feature of mozilla. Have you had any crashes/unscheduled powerouts on your system which could lead to fs corruption that may explain the talkback module being damaged ? Whatever distro you have, i suggest removing the mozilla package and reinstalling. Fear not, your user profiles will persist so you shouldn't lose anything you've already set up.
dupe of bug 195601 (same stack) *** This bug has been marked as a duplicate of 195601 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.