Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 593188 - /etc/xorg.conf.d/ ignores input device configuration files
Summary: /etc/xorg.conf.d/ ignores input device configuration files
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-18 05:59 UTC by k.t.
Modified: 2011-06-27 16:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-06-27 16:27:04 UTC
Type: ---

Attachments (Terms of Use)
simple optical mouse .conf file (146 bytes, text/plain)
2010-05-18 05:59 UTC, k.t.
no flags Details
xorg log with input .conf file in /etc/xorg.conf.d/ directory (38.63 KB, text/plain)
2010-05-18 06:00 UTC, k.t.
no flags Details
xorg log with input .conf file in /etc/X11/xorg.conf.d/ directory (38.98 KB, text/plain)
2010-05-18 06:01 UTC, k.t.
no flags Details

Description k.t. 2010-05-18 05:59:38 UTC
Created attachment 414740 [details]
simple optical mouse .conf file

Description of problem:

according to documentation - https://fedoraproject.org/wiki/Input_device_configuration#Fedora_13 - I am supposed to use /etc/xorg.conf.d/ directory for my custom input device config files, however then I placed my razer conf file in there nothing changed

Version-Release number of selected component (if applicable):
Fedora 13 beta

How reproducible:

Steps to Reproduce:
1. create .conf file in /etc/xorg.conf.d/
2. log out of gnome
3. desirable settings in conf file have not been applied
Actual results:
.conf is ignored

Expected results:
do not ignore .conf file

Additional info:
I can use /etc/X11/xorg.conf.d/ directory

Comment 1 k.t. 2010-05-18 06:00:31 UTC
Created attachment 414741 [details]
xorg log with input .conf file in /etc/xorg.conf.d/ directory

Comment 2 k.t. 2010-05-18 06:01:28 UTC
Created attachment 414742 [details]
xorg log with input .conf file in /etc/X11/xorg.conf.d/ directory

Comment 3 Bug Zapper 2011-06-02 13:53:28 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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: 

Comment 4 Bug Zapper 2011-06-27 16:27:04 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

Note You need to log in before you can comment on or make changes to this bug.