livna-nvidia Bug -- I think ??

[William Case]

Hi;

Before I go off writing bug reports, I thought I would check here.

I have installed akmod-nvidia and kernel-2.6.26.3-29.fc9.x86_64.

At boot I get the following message on the boot echo screen:

"Enabling the nvidia driver: Traceback (most recent call last)
File "/usr/sbin/nvidia-config-display", line 146, in <module> app =
nvidiaConfigDisplay()
File "/usr/sbin/nvidia-config-display", line 52, in __init__ self.run()
File "/usr/sbin/nvidia-config-display", line 129, in self.enable
File "/usr/sbin/nvidia-config-display", line 57, in enable CurrentDriver
= SelfgetDriver
File
"/usr/lib/python2.5/site-packages/livnaConfigDisplay/ConfigDisplay.py",
line 226, in getDriver
returndriver
unboundlocalError: locale variable 'driver referenced before assignment"

A few lines further init.d checks for nvidia, finds it and boots in text
mode.

After some playing around I got the following boot message:
"Parse error on line 12 of section 'Files'
RgbPath is not a valid keyword in this section"

I then examined xorg.conf.

The 'Files' section contained 'RgbPath "/usr/X11R6/lib/X11/rgb".  I have
no such directory -- not even close.

I then commented out the 'Files' section and rebooted to get the
following boot echo screen warning "Enabling nvidia
driver: /etc/rc.d/init.d/functions line 54: 1838 segmentation fault "$@"

A few lines latter "checking for nvidia.ko" was run and passed 'OK'.

The rest of the boot was successful.

1) Do I have a bug or just an individual problem that can fixed?
2) Do I report such bugs (if it is a bug) to livna ?
3) By the way, what happened to the boot.log that used to record all the
boot screen echo messages.  I haven't used it in a while, but the
boot.log exists in /var/log but it is always empty.  Do I have to turn
something on?  In syslog perhaps?


-- 
Regards Bill
Fedora 9, Gnome 2.22.3
Evo.2.22.3.1, Emacs 22.2.1