Bug 525001

Summary: segfault starting firefox on XFCE liveCD
Product: [Fedora] Fedora Reporter: Brock Organ <borgan>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: 12CC: gecko-bugs-nobody, mcepl, vedran
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-04 18:31:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot showing firefox segfault none

Description Brock Organ 2009-09-22 22:34:07 UTC
* F12-Snap3-i686-Live-XFCE.torrent
* after automatic login as liveuser

starting firefox, a segfault occurs (see attached screenshot) ...

Comment 1 Brock Organ 2009-09-22 22:35:01 UTC
Created attachment 362148 [details]
screenshot showing firefox segfault

Comment 2 Brock Organ 2009-09-23 19:59:17 UTC
as a data point, firefox does not segfault this way using F12-Snap3-x86_64-Live-XFCE.torrent ...

Comment 3 Matěj Cepl 2009-09-24 09:31:12 UTC
Could we get that report from abrt (click on the bubble which jumped up), please? Also I have my deep suspicion that this is just a zillionth duplicate of bug gecko-execmem.

Comment 4 Matěj Cepl 2009-09-24 09:31:48 UTC
Stupid bugzilla, I meant bug 512845

Comment 5 Matěj Cepl 2009-09-24 09:33:58 UTC
No, sorry, it can't be ... that bug is just 32bit one. So, yes, we need that bactrace from abrt (just file a new bug through abrt GUI and make a comment in the abrt's comment box that it is duplicate of this bug), or if you cannot get it from there, then use the old-fashioned manual way:

Please install firefox-debuginfo (debuginfo-install is from yum-utils package).

	debuginfo-install firefox

Then run firefox with a parameter -g. That will start firefox running inside of gdb debugger. Then use command run and do whatever you did to make firefox crash. When it happens, you should go back to the gdb and run

	(gdb) thread apply all backtrace

This produces usually many screens of the text. Copy all of them into a text editor and attach the file to the bug as an uncompressed attachment.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 6 Brock Organ 2009-09-24 17:52:59 UTC
Hi Matej,

I'm sorry, I'm having network problems with the VM image I used to run this test, so I haven't been able to install the debuginfo firefox package yet, nor get the gdb trace ...

Brock

Comment 7 Matěj Cepl 2009-09-25 13:50:21 UTC
No need to apologise ... answer when you can (but in a month, otherwise we will close this as INSUFFICIENT_DATA).

Comment 8 Brock Organ 2009-09-29 20:20:58 UTC
verified this issue is fixed using post-install system installed from livecd:

xfce-i386-20090928.14.iso

Comment 9 Bug Zapper 2009-11-16 12:46:48 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 Vedran Miletić 2009-12-04 18:31:34 UTC
The VERIFIED, FAILS_QA and RELEASE_PENDING bug states are not used by Fedora (they are used in the RHEL process).

---

Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers