Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 65392 - user login in kdm gives only a shell instead of starting kde
Summary: user login in kdm gives only a shell instead of starting kde
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-26 04:38 UTC by Stefan Raspl
Modified: 2005-01-18 12:29 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Raspl 2004-09-26 04:38:46 UTC
After emerging kde 3.3.0, kdm login gives troubles.
Loggin in with a plain user does NOT start kde, but gives a single shell instead. If one types 'startkde' in that shell, kde will come up, no problem.
When one logs in as root in kdm to start kde, kde will come up fine.

I found quite a few entries in the forum of users having the same problem, e.g., http://forums.gentoo.org/viewtopic.php?t=165614&highlight=kdm+kde+startkde+shell+root
I also found the solution:
/usr/kde/3.3/share/config/kdm/Xsession is not executable for plain users, only for root. Doing a 'chmod a+rx /usr/kde/3.3/share/config/kdm/Xsession' solved the problem for good. Since only a few users are affected by this problem, I guess it might be a special upgrade issue - so the respective ebuild should be checked to set permission correctly.
Also, startkde complained that /usr/bin/cpp was not executable by plain users and also /usr/qt/3/etc/settings/qt* was not readable by all users.



Reproducible: Always
Steps to Reproduce:
1.make kdm the login manager
2.login at kdm with a plain (non-root) user for a kde session

Actual Results:  
kde does not start, a single shell appears instead


Expected Results:  
kde should start instead
Comment 1 Gregorio Guidi (RETIRED) gentoo-dev 2005-01-18 12:29:18 UTC
As you said, we don't know a way to reproduce this bug, so there's really nothing we can do about it...