KDM wont let me in KDE 4.3.1

Message

techcode · Post by **techcode** » Mon Nov 02, 2009 11:30 pm

This is very weird since:

* I can run X
* I can login to both KDE 3.5.10 and KDE 4.3.1 (changing rc.conf or ~/.xinitrc) and manually starting with startx once logged into terminal

But once KDE 4.3.1's KDM starts every attempt to login (with correct password) fails for some reason. For a moment it looks like it's loading the desktop, but immediately after I'm back at the login screen. However, if I use 3.5.10 KDM and select 4.3.1 session - I can login without problems to the KDE 4.3.1 session.

I don't see anything weird in kdm.log except:
(EE) XKB: No components provided for device Virtual core keyboard
- and that's it.

I also saw it complaining it can't load dri/dri2 - which it shouldn't even try to load as I don't have that in Xorg.conf due to Nvidia video card. But it seem to be some old content in the log.

Does anyone have any ideas/suggestions?

forkboy · Post by **forkboy** » Tue Nov 03, 2009 12:40 am

Can you post

Code: Select all

rc-update show

danomac · Post by **danomac** » Tue Nov 03, 2009 1:12 am

Make sure consolekit is in the default runlevel, i.e.

Code: Select all

$ rc-update add consolekit default

I found this out after upgrading my laptop a few days ago.

forkboy · Post by **forkboy** » Tue Nov 03, 2009 1:30 am

danomac wrote:Make sure consolekit is in the default runlevel, i.e.
Code: Select all
$ rc-update add consolekit default

Which is what I was trying to find out.

techcode · Post by **techcode** » Tue Nov 03, 2009 6:18 pm

Yes that was the problem - adding consolekit to default run level solved it! Since I haven't found out about it anywhere I'm wondering where did you find out about it (did I overlook something)?

I added section to the wiki KDE4 page under troubleshooting for this.

Now if I can only get the iwl3945 and wpa_supplement/wicd to connect me to the wpa/wpa2 hidden sessid AP again - right now I'm on neighbors unlocked (yeah I told him to lock it - good thing he didn't

) wireless...

forkboy · Post by **forkboy** » Tue Nov 03, 2009 8:26 pm

I submitted a bug report when I first had this issue but the devs marked it as invalid as the elog from kdm tells you consolekit needs to be running.

lokuarachi · Post by **lokuarachi** » Thu Nov 05, 2009 5:00 pm

having same problem, added consolekit to default but still no joy with kdm.....

any other suggestions?

the.root · Post by **the.root** » Thu Nov 05, 2009 7:58 pm

lokuarachi wrote:having same problem, added consolekit to default but still no joy with kdm.....

any other suggestions?

please post the following:

Code: Select all

rc-status
cat /var/log/kdm.log

lokuarachi · Post by **lokuarachi** » Mon Nov 09, 2009 1:09 pm

....just maybe......I needed to have kwin et al installed before i logged in.....problem solved.