Firefox fails to start with "Segmentation Fault"

[Peter Joseph]

Binary package hint: firefox

Firefox fails to start with "Segmentation Fault". Debug shows the following.

Starting program: /usr/lib/firefox-3.6.16/firefox-bin

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7ddb4d1 in ?? () from /lib64/ld-linux-x86-64.so.2

Release: Ubuntu 10.10
Installed: 3.6.16+build1+nobinonly-0ubuntu0.10.10.1

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: firefox 3.6.16+build1+nobinonly-0ubuntu0.10.10.1
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Sun Apr 10 17:53:32 2011
ExtensionSummary:
FirefoxPackages:
 firefox 3.6.16+build1+nobinonly-0ubuntu0.10.10.1
 firefox-gnome-support N/A
 firefox-branding 3.6.16+build1+nobinonly-0ubuntu0.10.10.1
 abroswer N/A
 abrowser-branding N/A
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: firefox

[Chris Coulson (chrisccoulson)]

Thanks, but we need a backtrace for this report to be of any use. Also, crash reports should be sent directly to Mozilla using the crash reporter dialog that appears when it crashes. Feel free to attach the crash ID of the report you submit to this bug report, and we'll reopen it if it's a distro issue

[Peter Joseph (peterjoseph100)]

Okay. Can you let me know what to do. Is it an strace? No mozilla crash
report dialog appears.
On 10 Apr 2011 19:25, "Chris Coulson" <email address hidden> wrote:
> Thanks, but we need a backtrace for this report to be of any use. Also,
> crash reports should be sent directly to Mozilla using the crash
> reporter dialog that appears when it crashes. Feel free to attach the
> crash ID of the report you submit to this bug report, and we'll reopen
> it if it's a distro issue
>
> ** Changed in: firefox (Ubuntu)
> Status: New => Invalid
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/756692
>
> Title:
> Firefox fails to start with "Segmentation Fault"
>
> Status in “firefox” package in Ubuntu:
> Invalid
>
> Bug description:
> Binary package hint: firefox
>
> Firefox fails to start with "Segmentation Fault". Debug shows the
> following.
>
> Starting program: /usr/lib/firefox-3.6.16/firefox-bin
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff7ddb4d1 in ?? () from /lib64/ld-linux-x86-64.so.2
>
> Release: Ubuntu 10.10
> Installed: 3.6.16+build1+nobinonly-0ubuntu0.10.10.1
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: firefox 3.6.16+build1+nobinonly-0ubuntu0.10.10.1
> ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
> Uname: Linux 2.6.35-28-generic x86_64
> NonfreeKernelModules: fglrx
> Architecture: amd64
> Date: Sun Apr 10 17:53:32 2011
> ExtensionSummary:
> FirefoxPackages:
> firefox 3.6.16+build1+nobinonly-0ubuntu0.10.10.1
> firefox-gnome-support N/A
> firefox-branding 3.6.16+build1+nobinonly-0ubuntu0.10.10.1
> abroswer N/A
> abrowser-branding N/A
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
(20101007)
> ProcEnviron:
> PATH=(custom, user)
> LANG=en_GB.utf8
> SHELL=/bin/bash
> SourcePackage: firefox
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/756692/+subscribe

[Chris Coulson (chrisccoulson)]

Please install firefox-dbg, then run "firefox -g" and follow the steps from step 5 of https://wiki.ubuntu.com/Backtrace when it crashes

[Peter Joseph (peterjoseph100)]

Hello,
   I had some difficulty following the instructions from step five. It
seems that if I do "firefox -g" firefox isn't actually attempting to
run at that point.

However following the install of the firefox-dbg package the symptoms
have changed. Instead of a straight segfault I get a gtk box saying
"Firefox is already running but is not responding, To open a new
window, you must first close the existing Firefox process, or restart
your system".

However during this time I find no evidence with a ps -aux that shows
another firefox-bin.

I was able to get the back trace information from gdb with this
message displayed.

Text file attached.

Regards
Peter

On 11 April 2011 13:14, Chris Coulson <email address hidden> wrote:
> Please install firefox-dbg, then run "firefox -g" and follow the steps
> from step 5 of https://wiki.ubuntu.com/Backtrace when it crashes
>
>
> ** Changed in: firefox (Ubuntu)
>   Importance: Undecided => Low
>
> ** Changed in: firefox (Ubuntu)
>       Status: Invalid => Incomplete
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/756692
>
> Title:
>  Firefox fails to start with "Segmentation Fault"
>
> Status in “firefox” package in Ubuntu:
>  Incomplete
>
> Bug description:
>  Binary package hint: firefox
>
>  Firefox fails to start with "Segmentation Fault". Debug shows the
>  following.
>
>  Starting program: /usr/lib/firefox-3.6.16/firefox-bin
>
>  Program received signal SIGSEGV, Segmentation fault.
>  0x00007ffff7ddb4d1 in ?? () from /lib64/ld-linux-x86-64.so.2
>
>  Release: Ubuntu 10.10
>  Installed: 3.6.16+build1+nobinonly-0ubuntu0.10.10.1
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 10.10
>  Package: firefox 3.6.16+build1+nobinonly-0ubuntu0.10.10.1
>  ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
>  Uname: Linux 2.6.35-28-generic x86_64
>  NonfreeKernelModules: fglrx
>  Architecture: amd64
>  Date: Sun Apr 10 17:53:32 2011
>  ExtensionSummary:
>  FirefoxPackages:
>   firefox 3.6.16+build1+nobinonly-0ubuntu0.10.10.1
>   firefox-gnome-support N/A
>   firefox-branding 3.6.16+build1+nobinonly-0ubuntu0.10.10.1
>   abroswer N/A
>   abrowser-branding N/A
>  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
>  ProcEnviron:
>   PATH=(custom, user)
>   LANG=en_GB.utf8
>   SHELL=/bin/bash
>  SourcePackage: firefox
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/756692/+subscribe
>

--
Peter Joseph

[Chris Coulson (chrisccoulson)]

Thanks, but the trace there just shows it spinning the event loop normally

You need to type "run" in gdb after running "firefox -g". Sorry, I should have been more clear.

[Peter Joseph (peterjoseph100)]

Hi,
  I did type run following the firefox -g. Otherwise I received "no stack" and "no registers".

However due to the change in symptoms I was able to determine that there was a problem with my firefox profile. I think this may have been caused by the original crash and following inability to start.

Due to the changing behavior and my now frustrating inability to reproduce the bug as originally reported I think it is best to close this bug. I will open again and perform backtraces if and when it happens again.

Thanks for your help.

Peter

[Chris Coulson (chrisccoulson)]

Ok, I'll close this for now. Please reopen if you get it again