I’m running OpenSUSE 11.1 with the KDE 4.3 desktop.
Everything worked fine until this morning my file system didn’t function anymore. When opening Dolphin I got some file system error saying that the service was unavailable.
So I rebooted and saw that in the boot text it said that I should manually run fsck because of filesystem errors. Then, the system only booted into something like <system repair> (not sure what it said). So I ran fsck and this gave me many inode errors (bare with me I’m no expert on this).
This then asked me if I wanted to clone certain blocks, which I did.
After rebooting it seemed to work fine, until KDE needed to be loaded. Then it switched to the login screen (normally it wouldn’t since it is a single-user system). When I typed in my password the screen went off and the login screen came back up again, the same happened when I tried to login as root.
So basically I can’t login into KDE anymore, I can however still get into the commandline.
I hope someone can help we with this, because my thesis is on there and its due very soon! :’(
Since you can still get to the command line, the system is still running.
You should be able to login in at the terminal as root or as a normal user.
Now try getting X up by typing startx.
If it still doesn’t work, run yast.
As a first stop, look at the users and see if your users are still there.
If you can’t find anything wrong, it may just be quicker to reinstall kde.
Please only use what you’re trying to get your thesis back. Do not continue working on it. First see that you get your thesis off the machine, then try to repair it.
File system errors don’t come for free: they indicate that there’s something very wrong. Find out what is causing the errors.
I experianced ame beahvior after several upgrades on my oS 11.1. It appeared that console-kit-daemon which should be started at the moment you start your KDE session did not come up as expected causing the KDE to crash and restart.
As a workaround I always started the console-kit-daemon from root’s commandline. After that I was able to log in to KDE without problems.
Unfortunately thi is just a workaround and I did not find real solution of the problem as I was forced to reinstall the system from scratch by other reasons and the problem did not reappear then.
Thanks for your replies.
I was able to use the konsole login to copy my thesis files to a USB drive!
Running startx failed (I will post the output here when I get home again this evening).
I tried installing KDE4.1 using the one-click install through the console. This worked (with some major downgrades) but generated some weird behaviour once KDE started again (at first, in sysinfo the version of KDE shown was 3.5). When I then tried to run upgrades again (using zypper update) the problem reoccured after rebooting.
I think the problem is that by running fsck some essential files were removed to the \lost+found folder (they are still there).
Probably a reinstall of KDE will solve the problem. But I will try the suggestion of running console-kit-deamon first.
linux-s44w:~ # startx
hostname: Host name lookup failure
xauth: creating new authority file /root/.serverauth.3084
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Invalid MIT-MAGIC-COOKIE-1 keygiving up.
xinit: Resource temporarily unavailable (errno: 11): unable to connect to X server
xinit: No such process (errno: 3): Server error.
I’m also not sure what running console-kit-daemon should do. I tried launching it as root and then switching back to KDM to login, but that didn’t change anything.
By the way, is this problem something I could fix by using the “Repair installed system” utility on the DVD? Or would it be best to backup everything and reinstall the entire system?
Thanks for your suggestion. I’m using an Nvidia grahics card and driver.
However I don’t think that graphics is an issue here. I failed to mention this clearly in my first post but I do get the KDM login screen. But I can’t get any further than that, when I type my username and password it just sort of refreshes and gives me KDM again.
Anyhow, I did run sax2 and it gave me the following output:
SaX: initializing please wait...
SaX: your current configuration will not be read in
SaX: access to your display is denied
SPP: prepare device [0] profile: Depth24
SPP: prepare device [0] profile: NVidia
SPP: calling device [0] profile script: NVidia
SPP: prepare device [0] profile: NoModelines
SPP: prepare device [0] profile: Composite
SPP: prepare device [1] profile: logitech-MediaPlay
SPP: including prepared profile(s)...
SPP: prepare device [0] profile: nobus
SPP: including prepared profile(s)...
SaX: startup
This did work in that it gave me some graphics again: KDM!
Any other suggestion are of course more than welcome!
At kdm do this:
Ctrl-Alt-F1
Login with username and password, do this:
su -c Yast
Start the Software Manager, select the KDE4 pattern, and perform the Action ‘All Packages -> Update unconditionally’. This reinstalls your entire KDE4. May take some time, but it looks like you’re missing something.
Reinstall at least all kdebase4, kdelibs4 packages. (no need for the debuginfo packages).
Good luck, otherwise get back to us.
BTW: Linux systems are never single-user. Very hardly ever…
Also: in KDM check which Session type is selected…
Thanks for your reply. I would love to test your suggestions but my HTTP is suddenly not working anymore. Ftp still works though. :S
So as soon as I get that fixed I´ll try it and post here.
BTW1: I meant single user as in I’m the only user and its set to automatically log me in.
BTW2: In KDM I had selected KDE4 as session type. But any other session fails in the same way.
I was trying to install Skype from the Skype site, when the package manager failed. Everything seemed to be OK; however, when I rebooted, KDE 4.2 doesn’t work. It works as root(!) and KDE 3.5 starts OK, but not 4.2 - I keep getting the login screen.
More worryingly are two new phenomena:
VirtualBox has stopped working (I get the little bouncing icon, then nothing)
I get an error each time I try to use YasT software management.
aescott adjusted his/her AFDB on Thursday 20 Aug 2009 15:46 to write:
>
> I’ve had a similar issue today.
>
> I was trying to install Skype from the Skype site, when the package
> manager failed. Everything seemed to be OK; however, when I rebooted,
> KDE 4.2 doesn’t work. It works as root(!) and KDE 3.5 starts OK, but not
> 4.2 - I keep getting the login screen.
rename the hidden file .kde4 in your home directory, change it to something
like .kde4-bak and then logout and try to login to kde4.
This will start a fresh default load of kde4 with all your preferences and
such gone, if it does start then you can copy back some of the files like
you mail dirs and rc`s from the old, when it stops being able to start up
you know you have hit the bad config file, this can be a bit time consuming
but does work.
>
> More worryingly are two new phenomena:
>
> VirtualBox has stopped working (I get the little bouncing icon, then
> nothing)
If you have upgraded the kernel you might have to go through the install
process of virtual box again as it will need to recompile the kernel module
against the new kernel for it to work.
> I get an error each time I try to use YasT software management.
>
try as root in a console:
rpm --rebuilddb
This will rebuild the rpm database, the db can get broke if an install goes
wrong, this might fix the software management prob.
HTH
–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
