OS acting weird

MTK358 · 01-07-2010, 02:06 PM

Recently I had (and am still having) a lot of trouble with my Fedora 12 installation.

First, 3D acceleration and sound stopped working. This was solver by adding my account to the "video" and "audio" groups (I wonder howcome it worked before?).

Then, my keyboard stopped working in X. It would work fine in CLI mode, but as soon as I start X not even the Num Lock LED worked! I think I glimpsed that it might be due to a missing keymap or something, but I don't know. I got my computer back by making Xfce's keyboard settings override X, but it still isn't right, and I can't use anything other than Xfce.

Recently I tried to burn a CD/DVD but neither Brasero, K3B, nor cdrecord could detect the DVD burner.

I decided to maybe try something like rkhunter, but it quits with an error message:

Code:

$ sudo rkhunter --check
Invalid XINETD_CONF_PATH configuration option - non-existent pathname specified: /etc/xinetd.conf

I just wonder what's wrong, and whether I should just erase this Fedora 12 installation and move on, either reinstalling Fedora 12 or trying out a new distro.

kbp · 01-07-2010, 03:11 PM

I'm not sure of the cause of your various errors but the message from rkhunter indicates you probably don't have xinetd installed, try 'yum install xinetd' from a terminal

cheers

MTK358 · 01-07-2010, 03:46 PM

After I installed xinetd, here are all the warnings that rkhunter brought up. I don't think any of them are a problem.

Code:

    Checking for prerequisites                               [ Warning ]
    Checking for passwordless accounts                       [ Warning ]
    Checking for passwd file changes                         [ Warning ]
    Checking for group file changes                          [ Warning ]
    Checking for hidden files and directories                [ Warning ]

At least it didn't find any rootkits.

I still wonder how come my Fedora installation started acting up that way. It was working perfectly before.

kbp · 01-07-2010, 03:53 PM

Sometimes things go weird due to a change you've made that you think is harmless, it's also possible that there's been some corruption introduced somewhere. You can use the 'verify' option of rpm to check whether a packages files have been modified since installation

eg.

Code:

rpm -V xorg-x11-server-common

cheers

MTK358 · 01-07-2010, 04:57 PM

That command brought no output.

One thing I have done is forcefully reinstall X.

I think I might have run sudo yum update around that time, I am not sure exactly.

kbp · 01-07-2010, 05:08 PM

That was just an example, if you're not sure which package could be casing problems you can check everything:

Code:

rpm -aV

.. however this will provide a lot of output and may be difficult to wade through. Maybe write the output to a file:

Code:

rpm -aV > /tmp/rpm_verify_log

Take a look at the rpm man page to see which changed attributes could be important

cheers