Firefox crashes when trying to view Quicktime movie trailers

Bug #376932 reported by Benjamin Humphrey on 2009-05-15
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mplayerplug-in (Ubuntu)
Nominated for Intrepid by drew
Nominated for Jaunty by José Cabo

Bug Description

Binary package hint: firefox

Firefox 3.0.10 crashes on Ubuntu 9.04 when trying to view a Quicktime movie trailer on

lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04

apt-cache policy firefox
  Installed: 3.0.10+nobinonly-0ubuntu0.9.04.1
  Candidate: 3.0.10+nobinonly-0ubuntu0.9.04.1
  Version table:
 *** 3.0.10+nobinonly-0ubuntu0.9.04.1 0
        500 jaunty-updates/main Packages
        500 jaunty-security/main Packages
        100 /var/lib/dpkg/status
     3.0.8+nobinonly-0ubuntu3 0
        500 jaunty/main Packages

Expected to happen: Video open in firefox and play.
What happened: Firefox instantly crashes upon clicking the button to play.

Ryan (rvanderbijl) wrote :

ryan@ryan-laptop:~$ firefox
code: 31
 speed -1
Segmentation fault

Removing mozilla-mplayer avoids the crash, but then I can't view the trailers.

Kurt Wall (kwall) wrote :

Thanks for your bug report and for helping to improve Ubuntu. I was not able to reproduce this behavior. The Quicktime trailer you listed played fine for me and did not crash Firefox.

$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
$ apt-cache policy firefox
  Installed: 3.0.10+nobinonly-0ubuntu0.9.04.1
  Candidate: 3.0.10+nobinonly-0ubuntu0.9.04.1
  Version table:
 *** 3.0.10+nobinonly-0ubuntu0.9.04.1 0
        500 jaunty-updates/main Packages
        500 jaunty-security/main Packages
        100 /var/lib/dpkg/status
     3.0.8+nobinonly-0ubuntu3 0
        500 jaunty/main Packages

Perhaps it is not Firefox but your video driver or video settings?

Ryan (rvanderbijl) wrote :

Well, I've got an nvidia card, see the lspci output below. I tried with the NVIDIA accelerated graphics driver 180, 173, and with neither of them. Same problem for all of them. I think it is an mplayer problem: if I open the URL in xine, it works. In mplayer, it doesn't work, complaining "It seems there is no Xvideo support for your video card available."

ryan@ryan-laptop:~$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
ryan@ryan-laptop:~$ apt-cache policy firefox
  Installed: (none)
  Candidate: 3.0.10+nobinonly-0ubuntu0.9.04.1
  Version table:
     3.0.10+nobinonly-0ubuntu0.9.04.1 0
        500 jaunty-updates/main Packages
        500 jaunty-security/main Packages
     3.0.8+nobinonly-0ubuntu3 0
        500 jaunty/main Packages
ryan@ryan-laptop:~$ apt-cache policy mozilla-mplayer
  Installed: 3.55-1.1ubuntu1
  Candidate: 3.55-1.1ubuntu1
  Version table:
 *** 3.55-1.1ubuntu1 0
        500 jaunty/multiverse Packages
        100 /var/lib/dpkg/status
ryan@ryan-laptop:~$ sudo lspci -vv
01:00.0 VGA compatible controller: nVidia Corporation Quadro FX 1600M (rev a1)
 Subsystem: Dell Device 019b
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at f5000000 (32-bit, non-prefetchable) [size=16M]
 Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M]
 Region 3: Memory at f2000000 (64-bit, non-prefetchable) [size=32M]
 Region 5: I/O ports at df00 [size=128]
 [virtual] Expansion ROM at f6e00000 [disabled] [size=128K]
 Capabilities: [60] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
  Address: 0000000000000000 Data: 0000
 Capabilities: [78] Express (v1) Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <4us
   ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
   MaxPayload 128 bytes, MaxReadReq 512 bytes
  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
  LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <512ns, L1 <4us
   ClockPM- Suprise- LLActRep- BwNot-
  LnkCtl: ASPM L0s L1 Enabled; RCB 128 bytes Disabled- Retrain- CommClk+
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
 Capabilities: [100] Virtual Channel <?>
 Capabilities: [128] Power Budgeting <?>
 Capabilities: [600] Vendor Specific Information <?>
 Kernel driver in use: nvidia
 Kernel modules: nvidiafb

Ryan (rvanderbijl) wrote :

When I view a trailer from the command line, e.g.:
gmplayer ''

Then it will start to play, but will encounter problems a little bit into the trailer, sometimes crashing, sometimes just hanging with a bunch of errors from FAAD. See the attached log file.

I can watch the trailer straight through using xine.

Ryan (rvanderbijl) wrote :

Sorry, the mplayer problems on the command line are a red-herring. If I increase mplayer's cache size then I don't get a problem.

So, I still think the problem is between firefox and mozilla-mplayer.

BTW, I'm running on an Intel(R) Core(TM)2 Duo CPU T8100.

Ryan (rvanderbijl) wrote :

Well, I've switched to gecko-mediaplayer, instead of mozilla-mplayer and it now works.

Kurt Wall (kwall) wrote :

Interesting. If the problem goes away if you switch away from mozilla-mplayer, I'd conclude the problem is the mplayer plugin. I've updated the package accordingly.

Micah Gersten (micahg) wrote :

Moving to mozilla-mplayer

affects: firefox (Ubuntu) → mplayerplug-in (Ubuntu)
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mplayerplug-in - 3.55-2ubuntu1

mplayerplug-in (3.55-2ubuntu1) karmic; urgency=low

  * Merge from debian unstable, remaining changes: LP: #386705
    - debian/control:
      + add Xb-Npp-xxx tags accordingly to "firefox distro add-on support"
      + replace build-depends on iceape-dev with libxul-dev.
      + replace iceweasel with firefox-3.0 | xulrunner.
      + replace iceape-browser with seamonkey-browser.
      + add alternative depends on mplayer-nogui (>= 1.0~rc2).
      + tighten mplayer dependency to (>= 1.0~rc2).
    - debian/mozilla-mplayer.links:
      + add firefox and xulrunner symlinks.
  * Fixes: LP: #239506 LP: #376932 LP: #360756 LP: #360222 (Hopefully).

 -- Bhavani Shankar <email address hidden> Sat, 13 Jun 2009 18:02:40 +0530

Changed in mplayerplug-in (Ubuntu):
status: New → Fix Released
José Cabo (folcwine) wrote :

This bug is NOT fixed. The mplayerplug-in (3.55-2ubuntu1) is ONLY for Karmic (the future 9.10) so Ubuntu 9.04 has the bug yet!

Please, compile the mplayerplug-in (3.55-2ubuntu1) for Jaunty...


Changed in mplayerplug-in (Ubuntu):
status: Fix Released → In Progress
Micah Gersten (micahg) wrote :

Please do not change the status. Fix Released means it is fixed in the latest development release. Please reference this document for the meaning of the status:

The correct way to request this fix for Jaunty is to use the Nominate for Release button near the top of the bug under the task list.

Changed in mplayerplug-in (Ubuntu):
status: In Progress → Fix Released
José Cabo (folcwine) wrote :

Hi Micah.

Sorry for the change. I has nominated the package for jaunty now but how can I show support to the release?


To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments