LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-04-2009, 05:36 AM   #1
Retne
LQ Newbie
 
Registered: Jun 2009
Distribution: Slackware 12.2
Posts: 12

Rep: Reputation: 0
startx works as root but not as regular user


As the title suggests I can run X as root but not as a regular user. It's a fairly fresh install and I'm not positive I have the permissions down right. Frustratingly X seems to refuse to dump errors into my xorg.0.log so I have no idea what to do to fix it.

Here's what happens: I log into my regular user account then type startx. It loads up the nvidia splash then goes to the kde startup gui thing and then sits there flashing on Initializing components until I ctrl+alt+backspace back to console. I then shift+pgup but all I can see is frustratingly vague messages like: kdeinit: fatal IO error client killed. Nothing to point me in the right direction and when I go check the xorg.0.log the only logs there are from when I run X as root.

As for the permissions, here is the list of groups I have my reg user account in:
audio
cdrom
disk
floppy
man
plugdev
slocate
users
video

Perhaps there is some obscure X11 folder I need to change the permissions on? I haven't changed any folder permissions and the only things I've installed since the computer got up and running was the nvidia driver and a firefox plugin called adblock.

Anyone have any ideas?
 
Old 07-04-2009, 06:08 AM   #2
/dev/me
Member
 
Registered: May 2008
Distribution: Slackware 13
Posts: 116

Rep: Reputation: 20
Is there something in ~/.xsession-errors perhaps?
Code:
cat ~/.xsession-errors
Alternatively, you could try switching to runlevel 4 and log in as user. Does that work?
Code:
# as root:
telinit 4

Last edited by /dev/me; 07-04-2009 at 06:09 AM.
 
Old 07-04-2009, 06:37 AM   #3
Retne
LQ Newbie
 
Registered: Jun 2009
Distribution: Slackware 12.2
Posts: 12

Original Poster
Rep: Reputation: 0
~/.xsession-errors doesn't exist in either my root folder or my reg user folder.

telinit 4 doesn't help either. Still stalls at the same spot.
 
Old 07-04-2009, 09:20 AM   #4
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,443

Rep: Reputation: 73
Try removing or moving your ~/.kde directory and then try again. Give it a lot of extra time the first time to setup all of the default settings properly. Does xfce or fluxbox work for a regular user?
 
Old 07-04-2009, 09:25 AM   #5
kc3
Member
 
Registered: Jun 2009
Distribution: Linux from Scratch
Posts: 172

Rep: Reputation: 35
idk, for some reason I had a similar problem but it worked when I did "startx -m" idk, may not work for you but it did for me.
 
Old 07-04-2009, 09:29 AM   #6
XGizzmo
Member
 
Registered: Mar 2007
Distribution: Slackware
Posts: 264

Rep: Reputation: 69
Check ownership and permissions on the home directory,subdirectories,and files of
the user that can't startx. You are looking for stuff that is owned by root.
There should not be any, if any are found you need to chown them back to said
user.
 
Old 07-04-2009, 09:50 AM   #7
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 9,985

Rep: Reputation: 4569Reputation: 4569Reputation: 4569Reputation: 4569Reputation: 4569Reputation: 4569Reputation: 4569Reputation: 4569Reputation: 4569Reputation: 4569Reputation: 4569
Quote:
Originally Posted by XGizzmo View Post
Check ownership and permissions on the home directory,subdirectories,and files of
the user that can't startx. You are looking for stuff that is owned by root.
There should not be any, if any are found you need to chown them back to said
user.
A quick way to do this is
chown -R dugan /home/dugan
where dugan is that user's name on the system.
 
Old 07-04-2009, 12:05 PM   #8
vharishankar
Senior Member
 
Registered: Dec 2003
Distribution: Debian
Posts: 3,178
Blog Entries: 4

Rep: Reputation: 138Reputation: 138
I believe from your description that this appears to be a KDE problem not an X problem.

Rename the .kde folder in the user directory to .kde-old and copy the .kde folder from root (making sure you change the permissions to your own user) and see if that helps.
 
Old 07-04-2009, 12:10 PM   #9
Uncle_Theodore
Member
 
Registered: Dec 2007
Location: Charleston WV, USA
Distribution: Slackware 12.2, Arch Linux Amd64
Posts: 896

Rep: Reputation: 70
Actually, there's no need to copy root's .kde folder. KDE is supposed to create one at the first run.
Would be interesting to see what error messages KDE produces when "flashing"... Try to go to the first console and see if there's anything interesting there. Ctrl+Alt+F1
 
Old 07-04-2009, 12:12 PM   #10
vharishankar
Senior Member
 
Registered: Dec 2003
Distribution: Debian
Posts: 3,178
Blog Entries: 4

Rep: Reputation: 138Reputation: 138
Quote:
Originally Posted by Uncle_Theodore View Post
Actually, there's no need to copy root's .kde folder. KDE is supposed to create one at the first run.
Would be interesting to see what error messages KDE produces when "flashing"... Try to go to the first console and see if there's anything interesting there. Ctrl+Alt+F1
I suggested it merely because otherwise you'd have to reconfigure everything from scratch.

Also I suggest that anybody be very careful when you mess with .kde folders, because they also hold some important data like mail downloaded using kmail and KDE contacts.
 
Old 07-04-2009, 12:17 PM   #11
Uncle_Theodore
Member
 
Registered: Dec 2007
Location: Charleston WV, USA
Distribution: Slackware 12.2, Arch Linux Amd64
Posts: 896

Rep: Reputation: 70
Maybe, the OP can try a different WM just to rule out a KDE-specific problem.
Something like
echo fluxbox >> .xinitrc
startx
 
Old 07-04-2009, 12:52 PM   #12
Retne
LQ Newbie
 
Registered: Jun 2009
Distribution: Slackware 12.2
Posts: 12

Original Poster
Rep: Reputation: 0
OK I checked the home folder's ownership and the reg user owns it. I renamed the .kde folder and got the same issue. Luckily it actually cranked out a .xsessions-errors this go around so here we go:

xset: bad font path element (#595), 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...
ksplash: Fatal IO error: client killed
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
klauncher: Exiting on signal 1
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
DCOP aborting (delayed) call from 'kded' to 'klauncher'
DCOP aborting while waiting for answer from 'kded'
kded: Fatal IO error: client killed
Warning: connect() failed: : No such file or directory
ksmserver: cannot connect to X server :0

I'm going to try fluxbox now to see if it's just a kde issue.

EDIT: fluxbox works. So I guess it is a kde problem.

EDIT #2: Being that it has been quite a while since I've used linux how do I switch the default X back to kde? I would like to fix the problem.

Last edited by Retne; 07-04-2009 at 01:07 PM.
 
Old 07-04-2009, 01:30 PM   #13
Uncle_Theodore
Member
 
Registered: Dec 2007
Location: Charleston WV, USA
Distribution: Slackware 12.2, Arch Linux Amd64
Posts: 896

Rep: Reputation: 70
You can troubleshoot the "bad font path" problem by looking at the output of

xset -q

and checking which font paths displayed are incorrect. But I doubt that this is the cause of KDE acting up.
 
Old 07-04-2009, 01:58 PM   #14
BrZ
Member
 
Registered: Apr 2009
Distribution: Slackware
Posts: 543

Rep: Reputation: 121Reputation: 121
is it safe? remove all /home/user/.serverauth.xxxx -> clean /tmp/ksocket-username -> clean /tmp/xauth.XXXXXxxxxx -> clean '/var/tmp/kdecache-usename'

Last edited by BrZ; 07-04-2009 at 02:15 PM.
 
Old 07-04-2009, 06:19 PM   #15
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Rep: Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546
Quote:
~/.xsession-errors doesn't exist in either my root folder or my reg user folder.
The stock Slackware does not create the file. If you want the file created then look here:

A More Intelligent startx Script

You can get the .xsession log to appear in run level 4 by editing /etc/kde/kdm/kdmrc:

Code:
[X-*-Core]
ClientLogFile=.xsession-errors-%s
Also, when you boot into run level 4, there will be a kdm.log in addition to the Xorg.0.log. However, the kdm.log typically is nowhere as informative.

If you want more verbosity in Xorg.0.log then use the -logverbose as a server argument with the startx command: for example, -logverbose 10.

KDE needs to establish some temporary directories. They are:

$HOME/.kde/cache-$HOSTNAME linked to /var/tmp/kdecache-$USER/
$HOME/.kde/socket-$HOSTNAME linked to /tmp/ksocket-$USER/
$HOME/.kde/tmp-$HOSTNAME linked to /tmp/kde-$USER/

Thus, be sure your user account has write/change permissions to /var/tmp and /tmp. Typically both directories are assigned 777 permissions.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
can no longer startx as regular user, cannot lock .Xauthority kryptobs2000 Linux - Software 2 08-15-2006 07:26 PM
startx works for root but not users aldenfuchs Red Hat 3 04-01-2005 10:28 AM
CD writing works in root but not for regular user lasindi Linux - Software 5 08-28-2004 11:25 PM
startx only works as root rbrasil Debian 3 12-10-2003 07:45 PM
Modem works as root but not as regular user. bmike1 Linux - Software 16 08-30-2003 02:39 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:46 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration