From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description of problem: I have a monitor which identifies itself as '19" Monitor'. Since a double quote is used for the options in XF86Config, the additional double quote breaks redhat-config-xfree86. This is a long-standing but which is fixed until now. Version-Release number of selected component (if applicable): redhat-config-xfree86-0.9.6-1 How reproducible: Always Steps to Reproduce: 1. Buy an monitor which has the internal DPMS name 19" monitor 2. delete /etc/X11/XF86Config 3. run 'redhat-config-xfree86' Additional info:
I'm having exactly the same problem; I just purchased a pallet of cheap 17" LCD monitors from Daewoo which identify themselves uselessly as: 17" TFT Resulting in the error: Parse error on line 91 of section Monitor in file /etc/X11/XF86Config "TFT"" is not a valid keyword in this section. Taking out the extra quote manually results in a working config file.
Hmm, this looks like a dupe of bug #87588, which was fixed long ago but seems to have returned. I can't figure out how, though, since the code is still there in monitor.py from rhpl. What version of rhpl are you running?
It's the version from Fedora beta1: rhpl-0.113-1
Created attachment 98323 [details] replacement monitor.py with some debug messages added I can't really see how this bug can still be happening since the code has been there for almost a year that strips out all " chars from the probed return value. Use this monitor.py to replace your /usr/lib/python2.2/site-packages/rhpl/monitor.py file. I have added some debug messages to try to figure out what is happening. Then run redhat-config-xfree86 from a command line and paste all the debug messages to this bug report.
Also, it would be helpful if both of you could run (as root) '/usr/sbin/ddcprobe' and paste the output here too.
Since I do not have this monitor any more (now I have a 19" digital TFT one :-))), I cannot do this anymore. Sorry.
Ok, well, since Dirk is the original bug reporter, I'm going to close this bug. Jason, please reopen this report if you can perform the tests I recommended above.