Lost KDE gui and stuck mostly with cli

English Install/Boot/Login
1

Hello All,

I can’t get my usual gui now. I had videocard problems which I was attempting to solve by uninstalling the proprietary ATI driver. While doing this the card failed completely and I had nothing on the screen at all. So I had to shut it down by killing the power.

I now have a new video card in the machine but I’ve lost KDE. I’m not sure how it happened but when I tried to log in I was presented with the login screen one usually gets when you choose to log out of your account after a normal boot up using, in my case, KDE. Logging in normally in that screen as my usual user didn’t work. It simply went back to the login screen after a few seconds. But this screen also gives you various options to log in that aren’t KDE and I chose one of those. I don’t remember which. It sort of worked. I get a small cli window in the upper left corner of the screen. However, I can start programs from there, including Firefox, which I’m using to post this. I have the gui within those programs.

How do I get my usual KDE gui back? I’m using 11.3 and an ati 4350 card. Thanks in advance.

2

You mean you get this:
http://dl.dropbox.com/u/10573557/Session%20Login/session.type.png

And you chose an option other than kde because kde just throws you back to the login screen?

If you do a console login:
http://dl.dropbox.com/u/10573557/Session%20Login/console.login.png

Login with your username and password
Let try renaming the .kde4 folder with

mv .kde4 .kde4-backup

now type: startx

3

There are several possible reasons, but it might not have anything to do with your GFX-card - it’s the typical behaviour when /tmp (and therefore the /-partition) is full. Check that with:

df -h

…and also post the output of:

grep BOOTUP /etc/sysconfig/cron

If I am correct, the output will explain to you why /tmp is overflowing.

Edit: one should try to avoid shutting down the power of a running system. A good way to do so when a system does not respond is by using the →Magic SysRq keys.

4

Ok, I’ve managed to get into IceWM, so I have a gui now that works. But how do I get KDE back? Trying to log-in regularly into KDE (or into failsafe) just kicks me back into the log-in screen after a few seconds. Thanks again.

edit in response to the response above: I’ve forgotten how to cut and paste in IceWM. But the partitions don’t appear to be full. They are at 49,1,1, and 22 percent. devtmpfs and tmpfs are both at 1. “home” is at 22 percent. the response to the second command is “no”. It doesn’t clear the temp directory (if I understand this right). Thank you very much for your help.

5

Did you try the .kde4 rename?

6

Yes, that’s the screen I get. I will post the results of the rest of what you suggest shortly. Thank you very much.

7

Yes, I did. I renamed the folder. It didn’t give me my gui back though. x server shut down. Part of the message (near the bottom of the console output) read: libGL.so.1 “cannot open shared object: file not present” or words to that effect. Is there any way I can dump the console to a text file so I can put it up here. I remember using “condump” from my Quake playing days to save console output. Does it work here? Thanks.

8

You should login with IceWM
And visit software management
with a view to making sure you are updated and your graphics driver is properly installed. There are some issues with ATI but I am not fulling in tune with those.

9

We assume the new card is ATI, is it???

10

Yes, it is. A 4350.

I ran Yast and did an update the first moment I could.

11

Ok, back to trying to get KDE to work properly. I’m in IceWM, trying to install the ATI proprietary driver. I run the installer, and it gets to a certain point where the progress “report” says “postprocessing Kernel Module” and then it stops. I ran the installer using the cli. The terminal window there tells me:

loki_setup: Can't create //usr/X11R6/lib/modules/dri/fglrx_dri.so: File exists
loki_setup: Can't create //usr/X11R6/lib64/modules/dri/fglrx_dri.so: File exists

So I saw that and thought those files where from the failed attempt to uninstall the driver last week. So I removed them using the cli. It seemed to be successful. But they reappeared. Next time I tried to install the driver I got the same message. I can see from the folders that indeed they’ve returned. How should I proceed from here? Thanks.

12

I can’t confidently advise you because I have never actually worked with ATI. Someone who uses ATI in their system should advise as there are it seems so many issues ATM

13

Ok, I tried to install it using YaST. I added the repository then searched for the correct drivers. I found them and attempted to install them but it failed. Here’s the output from the error message:

Subprocess failed. Error: RPM failed: rpmdb: PANIC: Invalid argument
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) storing record  into Provideversion
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "8.762-33.1" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "8.762-33.1" records from Provideversion index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Installtid index using db3 -  (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Sigmd5 index using db3 -  (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Sha1header index using db3 -  (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Filedigests index using db3 -  (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery

Not sure what to do now. I don’t understand much of the error message. I don’t like the word “panic” in the first line. I would like to avoid having to reinstall but that’s where this is going if I can’t fix it. Thanks.

14

As su -

rpmdb --rebuilddb

15

Woohoo!!! It’s back. It isn’t perfect. And I’m not 100 percent certain what fixed it. But I can play some games again, even though some do not work. I have to redo some stuff (I think it reverted to default stuff when I renamed my KDE folder?) but it’s not a problem. Thanks a lot for the help.

16

Great. Well done working thru that