Description of problem:
I just did a fresh install of FC4T3 and when I invoke system-config-lvm from the
menu nothing happens. Invoking it from the command line yields a traceback with
the following message
Traceback (most recent call last):
File "/usr/sbin/system-config-lvm", line 48, in ?
from renderer import volume_renderer
ImportError: No module named renderer
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.install fresh system
The file is definitely in the distribution, where it is supposed to be. I have
checked this 6 ways from Sunday!
Well, I played around with this some more.
First of all I remove system-config-lvm and removed
/usr/share/system-config-lvm. I then reinstalled the rpm. Here is what I found
* Invoking this from the Desktom->System Setting->Logical Volume Management
doesn't bring up this tool. The little time icon runs for a while and then it
* invoking "system-config-lvm" from the command line results in the renderer not
found message coming up.
* invoking "sudo system-config-lvm" (ie as root) brings the tool up and it seems
* invoking "system-config-lvm" after running it previously as root will result
in a message "Please restart /usr/sbin/system-config-lvm with root permissions"
* Using the menu to invoke the tool still doesn't work.
Some observations: in other tools the python files *.py are read-execute by
group and others. In system-config-lvm, they are not. When I invoke the tool
as root the *.pyc files get created as read by everyone.
I couldn't figure out why invoking it from the menu doesn't bring up the login
as root prompt that all the other tools provide.
Remember I am using a fresh install of FC4T3 so this is the state of lvm as it
came from rawhide.
Ok I found out what is wrong. The entry in
/usr/share/applications/system-config-lvm.desktop lists the exec path as
/usr/sbin/system-config-lvm instead of /usr/bin/system-config-lvm.
ah - sorry to doubt you! Fixed in 0.9.30-1.0
Fixed in 0.9.30-1.0
QA_READY has been deprecated in favor of ON_QA. Please use ON_QA in the future.
Moving to ON_QA.
Fedora Core 3 and Fedora Core 4 are no longer supported. If you could retest
this issue on a current release or on the latest development / test version, we
would appreciate that. Otherwise, this bug will be marked as CANTFIX one month
from now. Thanks for your help and for your patience.