[i945gm] Video Players crashes when using virtual > 2048
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-intel (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xserver-
Some info:
pretto@karnak:~$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
pretto@karnak:~$ pt-cache policy xserver-
bash: pt-cache: command not found
pretto@karnak:~$ apt-cache policy xserver-
xserver-
Installed: 2:2.6.3-0ubuntu9
Candidate: 2:2.6.3-0ubuntu9
Version table:
*** 2:2.6.3-0ubuntu9 0
500 http://
100 /var/lib/
xorg.conf
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
SubSection "Display"
Virtual 1560 800
EndSubSection
EndSection
Section "Device"
Identifier "Configured Video Device"
Driver "intel"
EndSection
Section "ServerFlags"
Option "DontZap" "True"
EndSection
Every player i tried using virtual > 2048 closes after open the video file.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xserver-
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
SourcePackage: xserver-
Uname: Linux 2.6.28-11-generic i686
[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
Subsystem: Acer Incorporated [ALI] Device [1025:0090]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
Subsystem: Acer Incorporated [ALI] Device [1025:0090]
description: | updated |
summary: |
- Video Players crashes when using virtual > 2048 + [i945gm] Video Players crashes when using virtual > 2048 |
tags: | added: crash |
Changed in xserver-xorg-video-intel (Ubuntu): | |
status: | New → Confirmed |
This is possibly the same bug as bug 366979, but I haven't checked the symptoms in detail.