[SOLVED] Succeeded with /usr/lib thingy, but KDE now refuses login

poseidon · 2012-07-19 15:10:25

Hi all,

I finally managed to upgrade my system by following the steps as written in the wiki. Then I rebooted.

Now, when I enter user name and password as prompted by the KDE login then always a dialog pops up saying "System is booting up!". Clicking the OK button brings me back to the login. That's it, I'm locked out.

I wanted to look at the output of dmesg, but unfortunately I can't open a conole other then CTRL-ALT-F1 and pressing CTRL-C there is w/o any effect.
Any idea how to get at my system again?

Cheers
poseidon

Last edited by poseidon (2012-07-20 06:52:52)

poseidon · 2012-07-19 17:17:27

Strange, seems that rc.local has to be empty now? Had a call to conky in there. After deleting it and rebooting, I could again log into my KDE desktop.

As on my acer no consoles are provieded I had to somehow boot into single user mode. Here is how I did it: http://www.cyberciti.biz/faq/grub-boot- … user-mode/.

poseidon

fsckd · 2012-07-19 17:50:09

Why did you call conky in rc.local? That's a very strange place to put it.

And it seems you have solved your issue. Please mark this thread as such.

cfr · 2012-07-20 01:21:14

Probably you are using systemd? I read that that starts virtual consoles "on demand" rather than by default. (But you can change this, I think.)

Arch Linux

#1 2012-07-19 15:10:25

[SOLVED] Succeeded with /usr/lib thingy, but KDE now refuses login

#2 2012-07-19 17:17:27

Re: [SOLVED] Succeeded with /usr/lib thingy, but KDE now refuses login

#3 2012-07-19 17:50:09

Re: [SOLVED] Succeeded with /usr/lib thingy, but KDE now refuses login

#4 2012-07-20 01:21:14

Re: [SOLVED] Succeeded with /usr/lib thingy, but KDE now refuses login

Board footer