Firefox Program received signal SIGABRT, Aborted.

[Tuomas Aavikko]

Binary package hint: firefox-3.1

Up-to-date Jaunty (9.04)

LANG=C apt-cache policy firefox-3.1
firefox-3.1:
  Installed: 3.1~b2+build1+nobinonly-0ubuntu1
  Candidate: 3.1~b2+build1+nobinonly-0ubuntu1
  Version table:
 *** 3.1~b2+build1+nobinonly-0ubuntu1 0
        500 http://archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status

LANG=C apt-cache policy flashplugin-nonfree
flashplugin-nonfree:
  Installed: 10.0.15.3ubuntu2
  Candidate: 10.0.15.3ubuntu2
  Version table:
 *** 10.0.15.3ubuntu2 0
        500 http://archive.ubuntu.com jaunty/multiverse Packages
        100 /var/lib/dpkg/status

dmesg:
[95760.127792] firefox-3.1[16384]: segfault at b7344313 ip b7d023a1 sp bf82c700 error 4 in libc-2.9.so[b7c92000+15c000]
[101721.880369] firefox-3.1[19357]: segfault at b73ac313 ip b7d653a1 sp bf98f890 error 4 in libc-2.9.so[b7cf5000+15c000]

Apparently even nightly builds from mozilla are crashing also, reported by fellow users
In jaunty as Intrepid

Steps to reproduce:
1. www.youtube.com
2. Select any video to view
3. Click video for fullscreen view

Expected to happen:
1. Video is displayed in fullscreen mode

What happened:
1. Firefox crashes any open firefox windows closes.

[Lemmiwinks (lemmiwinks)]

I can confirm this bug with FF3.1 (20090122) on Ubuntu 8.1! Same behavior..

[Alexander Sack (asac)]

please check whether this still happens when you have disabled all extensions;

otherwise please install firefox-3.1-dbg and xulrunner-1.9.1-dbg and get a backtrace:

gdb /usr/lib/firefox-3.0.1*/firefox 2>&1 | tee /tmp/bug.bt.txt

(gdb) run
... # once it crashes do:
(gdb) bt
...
(gdb) bt full
...
(gdb) quit

now submit the /tmp/bug.bt.txt file by attaching to this bug. Thanks!

[Alexander Sack (asac)]

also update the bug description following our standardized bug format: https://wiki.ubuntu.com/MozillaTeam/NormalizedBugFormat

[Tuomas Aavikko (taavikko)]

Extensions disabled (only adblock+ via synaptic)

path was incorrect for gdb, correct was "/usr/lib/firefox-3.1b3pre/firefox-3.1"
here's the output.

[Alexander Sack (asac)]

On Sun, Feb 08, 2009 at 06:51:47PM -0000, Tuomas Aavikko wrote:
>
> - Watching videos in youtube, they play fine, but when hitting that "fullscreen" button, browser crashes.
> - this behaviour doesn't occur while using FF 3.05
> + Steps to reproduce:
> + 1. www.youtube.com
> + 2. Select any video to view
> + 3. Click video for fullscreen view
> +
> + Expected to happen:
> + 1. Video is displayed in fullscreen mode
> +
> + What happened:
> + 1. Firefox crashes any open firefox windows closes.
>

Using a clean profile keeps this bug in place for you?

 - Alexander

[Tuomas Aavikko (taavikko)]

>>Using a clean profile keeps this bug in place for you?

Just tried after --purge remove and erasing settings folder .mozilla/firefox-3.1/
32bit system crashes, output included.

there's no issue in 64bit system, it works as supposed to.

[Rob Hubble (rob-hubble)]

Confirmed also on several Ubuntu computers I have access to. Clean profile, no extensions. I've never seen fullscreen work properly under Ubuntu on sites such as Youtube.

[DoDoENT (dodoentertainment)]

Also happens on amd64 and on other random sites (not only youtube). Running firefox from terminal only prints the output "Aborted" after crash, and npviewer.bin stays running (I have to kill it manually.).

[Julian Alarcon (julian-alarcon)]

Hey... are you using nVidia cards??? There is a know bug here:
https://bugs.launchpad.net/ubuntu/+source/firefox-3.5/+bug/333127

Maybe is the same bug, if someone have another rband of video card, please tell us..

[DoDoENT (dodoentertainment)]

It's not a firefox bug, but instead it's a samba bug. Just turn off wins resolution in /etc/nsswitch.conf and firefox will work fine.

[Micah Gersten (micahg)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 333127, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.