Red Hat Bugzilla – Bug 53866
(MGA 400 AGP) xawtv + switching resolution = lockup
Last modified: 2007-04-18 12:37:15 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010913
Description of problem:
When switching screen resolution from 1024x768 to 800x600 (or vice versa)
while running kwintv (from Powertools 7.1), this is very likely to cause a
server deadlock, i.e. black screen and keyboard being killed.
Version-Release number of selected component (if applicable):
XFree86-4.1.0-3, see below
Steps to Reproduce:
1. Start "kwintv", no matter whether full screen or small window.
2. Press CTRL+ALT+"+" or CTRL+ALT+"-" to toggle screen resolution.
3. (repeat step 2 until screen turns black and X is dead)
Actual Results: Screen turns black. No further keyboard input possible.
Sound keeps playing.
Expected Results: Switch screen resolution without problems, no matter how
Version of Red Hat Linux is Seawolf plus packages from Rawhide (merely to
get ext3 fs, but also XFree 4.1.0 because it is the same with pristine
Seawolf). In particular:
$ uname -mr
$ rpm -qa | egrep ^XFree86\|^glibc\|^Mesa | sort
Created attachment 32198 [details]
Created attachment 32199 [details]
Created attachment 32200 [details]
Created attachment 32201 [details]
lspci -vv ; lspci -vvn
Reproducible with xawtv and Phoebe beta.
Please report this problem upstream to XFree86.org at http://bugs.xfree86.org
I'm hoping that by doing this, one of the numerous developers upstream will
likely investigate the issue and fix it, in which case we can backport any
fixes that come out of it. This would in effect accelerate the time to a
If you do so, please include the upstream bug report URL here so I can track it.
*** Bug 70169 has been marked as a duplicate of this bug. ***
The XFree86 upstream bug is still in open state and has not had any
responses for almost 3 years. We've switched from XFree86 to X.Org
for 5 OS releases now, so closing this as fixed in Fedora development.
If the problem still exists in rawhide, file a bug in the X.Org bug
tracker, which is where current active development is taking place.
Thanks in advance.