Unable to start KDE 3.5.1 successfully as non-root users
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Unable to start KDE 3.5.1 successfully as non-root users
First off I would like to say hello to the Slackware community. It's been less than a day since I finished installing Slackware; Although not everything worked the way I wanted to right out of the box, I went through the process of fixing and changing stuff which, to my surprise, was very educational! (Yes I've migrated from Windows).
The only problem that's kept me busy for hours is what the topic says. When I try to startx as a non-root user the KDE splash screen hangs on "Starting system services" indefinitely. My guess is it should be permission related since KDE starts fine with the root account, although I have not been able to prove it because after switching back to the terminal with CTRL + ALT + F1 when KDE hangs, I don't see any informative errors. Here's what the terminal says:
Code:
xauth: creating new authority file /home/phidelity/.serverauth.2434
X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Slackware 12.1 Slackware Linux Project
Current Operating System: Linux Honey 2.6.27.7-smp #2 SMP Thu Nov 20 22:32:43 CST 2008 i686
Build Date: 30 June 2008 11:35:29PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Sep 15 21:40:57 2009
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module "ramdac" already built-in
xset: bad font path element (#315), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
startkde: Starting up...
kbuildsycoca running...
At first I thought it's because of that fonts error/warning, but after comparing this log with the log generated from running KDE as root, I noticed that it's there too so that goes out of the window as well(?)
I think I need your knowledge to fix this one. Feel free to ask if you need more info. Thanks for your time.
P.S. I am able to run other window managers with non-root users.
hmm... regular users can use other wm but not kde... font type error reported when trying to start up...
maybe kde uses fonts the other wm don't and those fonts are not installed on your system, or the path to them might be incorrect in the FontPath option of xorg.conf...
... i would try examining the FontPaths in xorg.conf and then verify that they are pointing to directories that exist on your system... also check permissions and ownerships (on my 12.2 system, /usr/share/fonts and all subdirectories are owned by root:root with permissions mode of 0755...
... when installing did you install all of the kde set? did you check, at the mirror where you downloaded the sets to see if there were any kde-related packages in the patches directory (I switched from 12.0 to 12.2 and skipped 12.1, so don't recall anything about 12.1 patches)...
... since it is a fresh install, is there any reason to use 12.1 over 12.2 or 13?
hmm... regular users can use other wm but not kde... font type error reported when trying to start up...
maybe kde uses fonts the other wm don't and those fonts are not installed on your system, or the path to them might be incorrect in the FontPath option of xorg.conf...
... i would try examining the FontPaths in xorg.conf and then verify that they are pointing to directories that exist on your system...
I just double-checked the paths, They all refer to existing sources. I wouldn't be able to run KDE as root if xorg.conf had incorrect settings right?
Quote:
Originally Posted by globaltree
also check permissions and ownerships (on my 12.2 system, /usr/share/fonts and all subdirectories are owned by root:root with permissions mode of 0755...
Same here.
Quote:
Originally Posted by globaltree
... when installing did you install all of the kde set? did you check, at the mirror where you downloaded the sets to see if there were any kde-related packages in the patches directory (I switched from 12.0 to 12.2 and skipped 12.1, so don't recall anything about 12.1 patches)...
... since it is a fresh install, is there any reason to use 12.1 over 12.2 or 13?
Yes I think I have, since I installed full Slackware from the 12.2 DVD downloaded from one of the mirrors on slackware.com . I've noticed the line where it says 12.1 but I have no Idea why because I'm running 12.2 I would get Slackware 13 but ATM I don't have access to a high-speed internet connection.
Delete /var/tmp/kdecache-<user that cant run kde> and /tmp/kde-<user that cant run kde>
You may also want to run as root chown -R <user that cant run kde>:users /home/<user that cant run kde> . If all that fails delete /home/<user that cant run kde>/.kde
Hmm... I've might have missed it, but looking this thread over, I don't see any mentioning of you ever having run, as root, xorgsetup (which does it for you) or xorgconfig ( in which you have to know which video card driver to choose and your monitor's horizontal sync and vertical refresh frequencies)... either of these apps will make an /etc/X11/xorg.conf for you, though it is a good idea to back up original.
Your user does need to belong to various groups to run various services within the wm ( i.e., using the file pointed out by gegechris99, I add myself to floppy to use floppy disks, to audio to hear sound in wm, to plugdev to mount disks, to cdrom, to scanner, etc.). however, before I was aware of this, the wm did start up, except I didn't have sound and couldn't use cd's, etc... so I came to this forum and read the sticky on hal, and then that was solved, but it (and I was using xfce4 for wm) did start up before I added the user to any of those groups...
Thanks all for trying to help. I'll try to put the outcome of all your suggestions in one post.
Quote:
Originally Posted by mRgOBLIN
Well if root has a working xorg.conf in his current directory (likely /root/) then X will use that instead of the default /etc/X11/xorg.conf.
If you find an xorg.conf file there maybe (back up the original) and copy that to /etc/X11/xorg.conf.
Did you check the /var/log/Xorg.0.log ?
I Didn't find a xorg.conf file in my root folder. I checked the logs generated from startx both as root and non-root and it says "Using config file: "/etc/X11/xorg.conf" so they should be using the same file.
I have attached a log generated by a non-root user.
Quote:
Originally Posted by gegechris99
Please post the list of groups to which your user belongs to:
Code:
ls /etc/group | grep username
audio, video, cdrom, plugdev and power . I added the user to these groups as suggested by rg3 earlier.
Quote:
Originally Posted by XGizzmo
Delete /var/tmp/kdecache-<user that cant run kde> and /tmp/kde-<user that cant run kde>
You may also want to run as root chown -R <user that cant run kde>:users /home/<user that cant run kde> . If all that fails delete /home/<user that cant run kde>/.kde
I deleted /var/tmpkdecache-<user> but /tmp/cache/kde-<user> didn't exist, ran chown -R <user>:users /home/<user>. It didn't help. I also deleted /home/<user>/.kde afterwards and tried startx as <user> to no avail. The latter just resulted in the kde first-time-configuration-wizard to be shown when I tried to startx as <user>, but after completing the wizard KDE hanged on "starting system services" again.
Quote:
Originally Posted by globaltree
Hmm... I've might have missed it, but looking this thread over, I don't see any mentioning of you ever having run, as root, xorgsetup (which does it for you) or xorgconfig ( in which you have to know which video card driver to choose and your monitor's horizontal sync and vertical refresh frequencies)... either of these apps will make an /etc/X11/xorg.conf for you, though it is a good idea to back up original.
Your user does need to belong to various groups to run various services within the wm ( i.e., using the file pointed out by gegechris99, I add myself to floppy to use floppy disks, to audio to hear sound in wm, to plugdev to mount disks, to cdrom, to scanner, etc.). however, before I was aware of this, the wm did start up, except I didn't have sound and couldn't use cd's, etc... so I came to this forum and read the sticky on hal, and then that was solved, but it (and I was using xfce4 for wm) did start up before I added the user to any of those groups...
hopefully it just takes xorgsetup !
Yes I had run xorgconfig to setup x right after installing slackware. I was having the same problem with the xorg.conf generated by xorgconfig. I have also tried xorgsetup. My current xorg.conf is generated by the latest Nvidia driver which seems to work great in my root account; But the problem with non-root users persists.
You seem to have installed the proprietary nvidia drivers. Is that correct? If yes then you should have told us.
You need to search the forum for specific issues related to this proprietary driver.
As a first step, you can try with the open source nvidia driver. In xorg.conf, change in the Device section:
Code:
Driver "nvidia"
into
Code:
Driver "nv"
I'm reading some pages about problems related to this driver, but as I mentioned I was having this problem before installing the nvidia driver.
Quote:
Originally Posted by phidelity
Yes I had run xorgconfig to setup x right after installing slackware. I was having the same problem with the xorg.conf generated by xorgconfig. I have also tried xorgsetup. My current xorg.conf is generated by the latest Nvidia driver which seems to work great in my root account; But the problem with non-root users persists.
I suggest that you switch to 'nv' driver so that if you still have issue as non-root user, we are not polluted with potential issues related to proprietary driver.
Please post /var/log/Xorg.0.log after you switched to 'nv' driver.
One of the main reasons that attracted me to Linux was the security it offered, but always being logged in as root isn't really what I call secure. So hopefully with the help of you Linux gurus I would be able to fix this problem without switching to another distro.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.