620771 - Crash at startup in libgnomevfs-2.so 2.24.0

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Alexander Lopatin]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13

Firefox chrashed while starting up and shown the "Mozilla Crash Reporter" window. If I press "Restart Firefox" — it restarts and crashes again. If I write a bugreport into that window and press "Restart Firefox" — it says "There was a problem while submitting your report".

I ran Firefox with "-safe-mode" argument (BTW, it would be so nice for inexperienced users to have the "Safe Mode" button in the bug report window), turned off all the extensions and was turning on them one by one. Firefox crashes again, when one of those extensions is on: FoxyProxy Basic 1.8.3, Stylish 1.0.11 and Vimerator 0.7.3. Problem occurred after updating a part of the system (Gentoo GNU/Linux, it still runs "emerge -e system").

Reproducible: Always

Steps to Reproduce:
1. Install one of those extensions: FoxyProxy Basic, Stylish or Vimerator
2. Restart Firefox
3. Get the segfault.



Here is the backtrace:

/usr/bin/gdb /opt/firefox/firefox-bin -x /tmp/mozargs.VuMdBs
GNU gdb 6.8
...
(gdb) r
Starting program: /opt/firefox/firefox-bin
(no debugging symbols found)
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb4d3f730 (LWP 17348)]
0xb45962f5 in ?? () from /usr/lib/libgnomevfs-2.so.0
(gdb) bt
#0  0xb45962f5 in ?? () from /usr/lib/libgnomevfs-2.so.0
(gdb)

Comment 1

[Alexander Lopatin]

I misspelled in "Vimperator" word.

So, I've moved ~/.mozilla and ran Firefox with the clean profile. It crashed after trying to select Edit -> Preferences and it crashes again at startup even in safe mode.

Comment 2

[Matthias Versen [:Matti]]

Please provide a stack trace https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report

Comment 3

[Alexander Lopatin]

Attachment: stacktrace

Comment 4

[timeless]

you need to install symbols for:
> #0  0xb45d02f5 in ?? () from /usr/lib/libgnomevfs-2.so.0

doing this involves reading the instructions from your distro on how to do this, it could be  a -dbg or -debug package or they could have a magic script which does it.

Comment 5

[Alexander Lopatin]

I have updated gnome-vfs from 2.24.0 version (it is no longer available from distro's repository) to 2.24.3, and it's solved a problem.

Comment 6

[Kevin Brosnan]

Marking works for me as the reporter no longer crashes with an updated version of gnome-vfs.