Bug 4368

1) enable the "core release debug"
2) install the following packages: gdb glibc-debug firefox-debug
3) run the following command from a terminal:
   gdb -q firefox
4) then type "run"
5) when it segfaults, type "bt" and copy back the stack trace in a file you'll
attach (not paste) to this bug report
Thanks

Also are you sure it's not one of your extensions ?

Keywords: (none) => NEEDINFO
Summary: Segmentation fault => Segmentation fault in firefox
Severity: critical => major

Just fyi, opening the site in the description in firefox on my i586
mageia 1 system works fine, so it is most likely a addon causing
the crash.

CC: (none) => davidwhodgins

Created attachment 1483 [details]
debuger

The problem is not extensions , on-off all - the same.

@ dmorgan 

Do you have any ideas on the backtrace?

@ lomion

did you try wether you have the same problem when using firefox after having logged in as a different user?

CC: (none) => dmorganec, marja11

Yes i tried - same problem.Just a guess, maybe the problem is related somehow with а cyrillic alphabet since only i complain (i am a Bulgarian).

(In reply to comment #5)
> Yes i tried - same problem.Just a guess, maybe the problem is related somehow
> with а cyrillic alphabet since only i complain (i am a Bulgarian).

Please start your firefox in the konsole/terminal with:

LC_ALL=C firefox

It'll start in English then.

If the problem isn't there anymore, the cyrillic alphabet could indeed be the problem

LC_ALL=C firefox -no change.I booted live cd in bulgarian sesion and firefox work like charm on it.Therefore some update after is the problem.I have even difficulty login here.

can you try with firefox 10 ? (in the core updates testing reposity)

Ha, ha strange thing, now with firefox 10 work faultless everywhere except here -bugs.mageia.org. When i click to additional comments -boom!!!-disappears.

(In reply to comment #9)
> Ha, ha strange thing, now with firefox 10 work faultless everywhere except here
> -bugs.mageia.org. When i click to additional comments -boom!!!-disappears.

:(

Do you mind running firefox 10 in gdb too, and attach that backtrace?

firefox 10 debug is in /debug/core/updates_testing/ (Core Updates Testing Debug in MCC)

Created attachment 1602 [details]
gdm-backtrace

This time gdm show same thing else. After all, cyrillic could indeed be the problem.

I went to Edit-Preferences-Adwanced and uncheck - Chech my spelling as I type. Now Firefox 10 work correctly, but this is standart function in Firefox, can you fix it?

(In reply to comment #12)
> This time gdm show same thing else. After all, cyrillic could indeed be the
> problem.

It really shows something else, great :)

This looks a lot more useful


 (In reply to comment #13)
> I went to Edit-Preferences-Adwanced and uncheck - Chech my spelling as I type.
> Now Firefox 10 work correctly, but this is standart function in Firefox, can
> you fix it?

assigning to maintainer and cc'ing QA because FF 10 is in updates/testing

cc'ing hunspell maintainer as well

Keywords: NEEDINFO => (none)
CC: (none) => n54, qa-bugs
Assignee: bugsquad => dmorganec
Summary: Segmentation fault in firefox => Segmentation fault in firefox 10
Source RPM: firefox => firefox-10.0.2
Severity: major => normal

Do we have any progress on this?  Should it block Bug 4405

Removing QA from CC for now so this doesn't appear in our list.

CC: qa-bugs => (none)

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

As far I'm concern the problem exist in Mageia2. I can not provide more information because I switch distro, Mageia has to  many bugs for my taste. Sorry !

(In reply to comment #18)
> As far I'm concern the problem exist in Mageia2. I can not provide more
> information because I switch distro, Mageia has to  many bugs for my taste.
> Sorry !

Thanks for the feedback, sorry to hear Mageia doesn't work well for you.

@ yurchor

So far, no one was able to reproduce this bug.

Since Ukrainian uses the Cyrillic alphabet, too, can you maybe reproduce it?

CC: (none) => yurchor
Version: 1 => 2
Whiteboard: (none) => MGA1TOO

(In reply to comment #19)
> @ yurchor
> 
> So far, no one was able to reproduce this bug.
> 
> Since Ukrainian uses the Cyrillic alphabet, too, can you maybe reproduce it?

No. All the above mentioned sites work here as expected here without any crashes.

Spellchecking in Ukrainian and Bulgarian works as expected.

Firefox 10.0.5 (Ukrainian interface), Mageia 2, i586, Adobe Flash plugin 11.2 r202 installed.

Created attachment 2966 [details]
gdb -q firefox

Linux localhost.localdomain 3.3.8-desktop-2.mga2 #1 SMP Mon Jul 30 21:35:06 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Mozilla Firefox 10.0.9

I had the seg fault too.

Doesn't seem to be site related. 


Tried removing .mozilla/firefox to avoid history, plugins, etc; Firefox still seg faults.

CC: (none) => nrgiroux

does it help if you remove lib(64)proxy-mozjs and install lib64proxy-webkit ? 

(like in https://bugs.mageia.org/show_bug.cgi?id=7237)

Created attachment 3055 [details]
gdb -q firefox / run / bt on segfault

No

The segfault seems to be in xulrunner for both of the reporters

That doesn't change the assignee, though

Status: UNCONFIRMED => NEW
Summary: Segmentation fault in firefox 10 => Segmentation fault in firefox 10 (libxul.so)
Ever confirmed: 0 => 1
Source RPM: firefox-10.0.2 => firefox-10.0.2, xulrunner

so again what does said "rpm -qa | proxy"

furthermore your logs speak about firefox-10.0.9 when firefox-10.0.10 what pushed end october.

(In reply to comment #27)
> so again what does said "rpm -qa | proxy"
> 
> furthermore your logs speak about firefox-10.0.9 when firefox-10.0.10 what
> pushed end october.

ping?

Whiteboard: MGA1TOO => NEEDINFO

rpm -qa|grep proxy

lib64proxy1-0.4.7-6.1.mga2
libproxy-gxsettings-0.4.7-6.1.mga2
netprofile-plugin-proxy-0.28-3.mga1
python-libproxy-0.4.7-6.1.mga2
lib64proxy-networkmanager-0.4.7-6.1.mga2
lib64proxy-gnome-0.4.7-6.1.mga2
lib64proxy-webkit-0.4.7-6.1.mga2


The firefox version installed is now 10.0.11 but I can't comment further on this bug since I switched to Google Chrome as my primary browser.

(In reply to comment #29)
> rpm -qa|grep proxy
> 
> lib64proxy1-0.4.7-6.1.mga2
> libproxy-gxsettings-0.4.7-6.1.mga2
> netprofile-plugin-proxy-0.28-3.mga1
> python-libproxy-0.4.7-6.1.mga2
> lib64proxy-networkmanager-0.4.7-6.1.mga2
> lib64proxy-gnome-0.4.7-6.1.mga2
> lib64proxy-webkit-0.4.7-6.1.mga2
> 
> 
> The firefox version installed is now 10.0.11 but I can't comment further on
> this bug since I switched to Google Chrome as my primary browser.

Thx for the feedback

So we have a newer version of FF than the one that segfaulted, and none of the reporters can test whether the bug still exists with it.
Closing as OLD

Please reopen if needed.

Status: NEW => RESOLVED
Resolution: (none) => OLD
Whiteboard: NEEDINFO => (none)