Bug 454194 - DriverPath wrong in /etc/sysconfig/lcdproc/LCDd.conf
DriverPath wrong in /etc/sysconfig/lcdproc/LCDd.conf
Product: Fedora
Classification: Fedora
Component: lcdproc (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nicolas Chauvet (kwizart)
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-07-06 07:59 EDT by Patrick C. F. Ernzer
Modified: 2008-10-16 11:45 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-16 11:45:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
gendiff /etc/sysconfig/lcdproc .orig (599 bytes, patch)
2008-07-06 07:59 EDT, Patrick C. F. Ernzer
no flags Details | Diff

  None (edit)
Description Patrick C. F. Ernzer 2008-07-06 07:59:29 EDT
Description of problem:
as shipped, lcdproc has a wrong DriverPath in /etc/sysconfig/lcdproc/LCDd.conf

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

How reproducible:

Steps to Reproduce:
1. yum install lcdproc
2. start LCDd
Actual results:
no drivers found

Expected results:
default config should point at the correct driver directory

Additional info:
the required change is minimal, "DriverPath=/usr/lib/lcdproc/" is what is needed.
Comment 1 Patrick C. F. Ernzer 2008-07-06 07:59:29 EDT
Created attachment 311097 [details]
gendiff /etc/sysconfig/lcdproc .orig
Comment 2 Nicolas Chauvet (kwizart) 2008-07-08 08:31:19 EDT
The problem is that driver path is arch dependant and will need to tweak to
/usr/lib64 on lib64 multilibs systems.
This can be done as a dyn patch at buildtime. As there is no -devel package, we
will avoid multiarch conflict. I will fix in devel for now.
Comment 3 Nicolas Chauvet (kwizart) 2008-07-08 13:06:51 EDT
Build for rawhide is failing because of xmlto breakage
You can test this built specially for the initscripts (LSB compliant)

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