Bug 558604

Summary: xdmxconfig will not run
Product: [Fedora] Fedora Reporter: David Johnston <david>
Component: xorg-x11-serverAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 903986 (view as bug list) Environment:
Last Closed: 2010-12-03 23:49:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Johnston 2010-01-25 19:29:50 UTC
Description of problem:
xdmxconfig is a GUI for creating Xdmx (multihead) configuration files.
xdmxconfig will not run.

Version-Release number of selected component (if applicable):
xorg-x11-server-Xdmx-1.7.4-1.fc12.x86_64

How reproducible:
Execute xdmxconfig or sudo xdmxconfig.

Actual results:
# xdmxconfig
(**) dmx: Unable to read configuration file 
X Error of failed request:  BadPixmap (invalid Pixmap parameter)
  Major opcode of failed request:  55 (X_CreateGC)
  Resource id in failed request:  0x4200029
  Serial number of failed request:  141
  Current serial number in output stream:  162


Expected results:
xdmxconfig program should start.

Additional info:
Results are identical if a configuration file is specified on the command line, eg
# xdmxconfig /etc/xdmx.conf

This appears to be the same problem listed in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495816
dated Wed, 20 Aug 2008 16:30:02 UTC

According to that bug report, this happens on all architectures.  However, I've only verified it on Fedora 12 x86_64.

Workaround:
Create the configuration file in a text editor.

Comment 1 Bug Zapper 2010-11-03 23:56:31 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2010-12-03 23:49:48 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.