x crashes when playing a video in totem or vlc

Bug #375129 reported by Stephen
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Totem
Invalid
Undecided
Unassigned
xserver-xorg-video-intel (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi,
     I'm running Ubuntu 8.04 LTS on an HP pavillion dv5 laptop with an Intel Graphics Media Accelerator 4500MHD. Everytime I open a video in Vlc or Totem (both players I've tried), x freezes. Initially after installing, the mouse would still work after the freeze, but I could not switch to a terminal, only hold down the power button or use 'alt+print screen' and 'r,s,e,i,t,b' to turn off the laptop. Upon restart it starts fine. After updating, even the mouse freezes, although that seems to be the only thing that has changed. Even opening vlc in terminal results in the crash as soon as I open a file. Even an mp3, (although in all cases above, sound will play).
      I recently put 8.04 LTS on this laptop as for the past week I tried to get sound to work on 9.04 (which I could not do). Interestingly, the sound works great here, but now I can't play video. could I install whatever x server or intel drivers ubuntu 9.04 uses?

- thanks

I'm newer to the ubuntu scene and have only used ubuntu for about 2 weeks. (although I've used Fedora 8,9, and 10 over the past two years on my desktop). Fedora 10 x64 also worked on this laptop if that helps. (I'm switching only because this laptop is used by a few others besides myself downloading and giving presentations, and Ubuntu seems more intuitive to them, and also seems to be able to browse much faster on the internet).

Revision history for this message
Bartosz Kosiorek (gang65) wrote :

Please attach "lspci -vvn" output, and your Xorg.0.log and xorg.conf files

Revision history for this message
Stephen (d557charger) wrote :
Download full text (20.9 KiB)

my lspci -vvn output:
Enable-
  Address: 00000000 Data: 0000
 Capabilities: [d0] Power Management version 3
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.1 0380: 8086:2a43 (rev 07)
 Subsystem: 103c:3602
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0
 Region 0: Memory at d6500000 (64-bit, non-prefetchable) [size=1M]
 Capabilities: [d0] Power Management version 3
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:1a.0 0c03: 8086:2937 (rev 03) (prog-if 00 [UHCI])
 Subsystem: 103c:3602
 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0
 Interrupt: pin A routed to IRQ 16
 Region 4: I/O ports at 90e0 [size=32]
 Capabilities: [50] #13 [0306]

00:1a.1 0c03: 8086:2938 (rev 03) (prog-if 00 [UHCI])
 Subsystem: 103c:3602
 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0
 Interrupt: pin B routed to IRQ 21
 Region 4: I/O ports at 90c0 [size=32]
 Capabilities: [50] #13 [0306]

00:1a.7 0c03: 8086:293c (rev 03) (prog-if 20 [EHCI])
 Subsystem: 103c:3602
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0
 Interrupt: pin D routed to IRQ 19
 Region 0: Memory at dc705c00 (32-bit, non-prefetchable) [size=1K]
 Capabilities: [50] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [58] Debug port
 Capabilities: [98] #13 [0306]

00:1b.0 0403: 8086:293e (rev 03)
 Subsystem: 103c:3621
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 22
 Region 0: Memory at dc700000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: [50] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
  Address: 0000000000000000 Data: 0000
 Capabilities: [70] Express Unknown type IRQ 0
  Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
  Device: Latency L0s <64ns, L1 <1us
  Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
  Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
  Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
  Link: Supported Speed unknown, Width x0, ASPM unknown, Port 0
  Link: Latency L0s <64ns...

Revision history for this message
Stephen (d557charger) wrote :
Revision history for this message
Stephen (d557charger) wrote :
affects: hardy-backports → totem
Geir Ove Myhr (gomyhr)
tags: added: gm45 hardy intel xorg
Revision history for this message
Geir Ove Myhr (gomyhr) wrote :

Stephen, you have a fairly new graphics chipset (GM45) and the support for that wasn't very good in the (now) old intel driver 2.2.1 that Hardy (8.04) was shipped with. Actually, according to http://en.wikipedia.org/wiki/Intel_GMA the chipset was launched in July 2008, and Hardy was shipped in April 2008. With such recent hardware, I can only recommend using the newer Ubuntu version 9.04 as a lot of work has been done in the driver to support newer chipsets since last year.

Unfortunately, you can't use Jaunty's drivers in Hardy. This is because the driver depends on newer versions of libdrm, mesa, and probably the linux kernel and the xserver. If you change all of this, you basically get a new distribution.

I'm closing this bug report (setting the status to Invalid) which does not mean that you're not experiencing a real problem, only that it is a problem we simply cannot solve.

To work around your problem, you may try a number of things. One thing is to try if you can turn of "xv" or "XVideo" in the video player. You may also disable it in xorg.conf with the line
  Option "XVideo" "false"
in the "Device" section of your xorg.conf. You may try the forums or other the "Answers" section on Launchpad to find other workarounds.

Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Invalid
Changed in totem:
status: New → Invalid
Revision history for this message
Stephen (d557charger) wrote : RE: [Bug 375129] Re: x crashes when playing a video in totem or vlc
Download full text (3.7 KiB)

Okay
     Thank you for your support.
               I just reinstalled Fedora on the Laptop, and everything works fine with that. Thanks again for all your help though. I still use ubuntu personally, don't worry ;)
                                                                          - steve

> Date: Sun, 31 May 2009 02:28:40 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 375129] Re: x crashes when playing a video in totem or vlc
>
> Stephen, you have a fairly new graphics chipset (GM45) and the support
> for that wasn't very good in the (now) old intel driver 2.2.1 that Hardy
> (8.04) was shipped with. Actually, according to
> http://en.wikipedia.org/wiki/Intel_GMA the chipset was launched in July
> 2008, and Hardy was shipped in April 2008. With such recent hardware, I
> can only recommend using the newer Ubuntu version 9.04 as a lot of work
> has been done in the driver to support newer chipsets since last year.
>
> Unfortunately, you can't use Jaunty's drivers in Hardy. This is because
> the driver depends on newer versions of libdrm, mesa, and probably the
> linux kernel and the xserver. If you change all of this, you basically
> get a new distribution.
>
> I'm closing this bug report (setting the status to Invalid) which does
> not mean that you're not experiencing a real problem, only that it is a
> problem we simply cannot solve.
>
> To work around your problem, you may try a number of things. One thing is to try if you can turn of "xv" or "XVideo" in the video player. You may also disable it in xorg.conf with the line
> Option "XVideo" "false"
> in the "Device" section of your xorg.conf. You may try the forums or other the "Answers" section on Launchpad to find other workarounds.
>
> ** Changed in: xserver-xorg-video-intel (Ubuntu)
> Status: New => Invalid
>
> ** Changed in: totem
> Status: New => Invalid
>
> --
> x crashes when playing a video in totem or vlc
> https://bugs.launchpad.net/bugs/375129
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Totem Movie Player: Invalid
> Status in “xserver-xorg-video-intel” source package in Ubuntu: Invalid
>
> Bug description:
> Hi,
> I'm running Ubuntu 8.04 LTS on an HP pavillion dv5 laptop with an Intel Graphics Media Accelerator 4500MHD. Everytime I open a video in Vlc or Totem (both players I've tried), x freezes. Initially after installing, the mouse would still work after the freeze, but I could not switch to a terminal, only hold down the power button or use 'alt+print screen' and 'r,s,e,i,t,b' to turn off the laptop. Upon restart it starts fine. After updating, even the mouse freezes, although that seems to be the only thing that has changed. Even opening vlc in terminal results in the crash as soon as I open a file. Even an mp3, (although in all cases above, sound will play).
> I recently put 8.04 LTS on this laptop as for the past week I tried to get sound to work on 9.04 (which I could not do). Interestingly, the sound works great here, but now I can't play video. could I install whatever x server or intel drivers ubuntu 9.04 uses?
>
> - thanks
>
> I'm n...

Read more...

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.