You are not logged in.
Pages: 1
Ok i have installed xfce4 and have been able to load it using startx while running as root, but when I run as a limited user and type startx, sometimes i get a blak screen and am not able to ctrl+alt+backspace out of it, or I get several xterm windows and a clock. Why cant I startx as a limited user?
Offline
hello,
this is possibly the install bug that I encountered. maybe this will solve your problem:
$ sudo chmod 1777 /tmp
then you should be able to 'startxfce4' as a regular user.
good luck,
stefan
Last edited by stefan1975 (2008-03-04 15:19:40)
"root# su - bofh"
OS: F10_x64, Arch, Centos5.3, RHEL4.7, RHEL5.3
Desktop Hardware: Dell Precision M65 laptop, core2duo, 2gb, 80gb 7200rpm
Registered linux user #459910 since 1998
Offline
What's in your user's ~/.xinitrc?
you should have something like "exec startxfce4".
Have you Syued today?
Free music for free people! | Earthlings
"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- A. de Saint-Exupery
Offline
You can find out about /tmp permissions with ls -l /tmp. This is how it should look:
$ ls -l -d /tmp
drwxrwxrwt ... /tmp
Most likely you'll need to chmod 1777 /tmp and to add the t:
chmod 1777 /tmp
chmod +t /tmp
Hope this solves your problems...
Offline
You can find out about /tmp permissions with ls -l /tmp. This is how it should look:
$ ls -l -d /tmp drwxrwxrwt ... /tmp
Most likely you'll need to chmod 1777 /tmp and to add the t:
chmod 1777 /tmp chmod +t /tmp
Hope this solves your problems...
that is more or less of what I said above apart from the fact that yours is sort of too much, the "1" in "chmod 1777 /tmp" stands for the sticky bit so there is no need to manually do a "chmod +t /tmp" afterwards, that just sets it again.
the values you set before the actual file permission can be as follows:
4=SUID
2=SGID
1=sticky
3=SGID && sticky
5=SUID && sticky
6=SGID && SUID
7=sticky, SUID && SGID
cheers,
stefan
Last edited by stefan1975 (2008-03-04 16:18:20)
"root# su - bofh"
OS: F10_x64, Arch, Centos5.3, RHEL4.7, RHEL5.3
Desktop Hardware: Dell Precision M65 laptop, core2duo, 2gb, 80gb 7200rpm
Registered linux user #459910 since 1998
Offline
Ok, I suppose your right, this is how I learned it, and because much people don't have the 't'.
Thanks anyway, the doubling (in my post) was caused, because I took too long, so you posted while I was typing, I didn't want to say anything better or something.
Offline
Ok i followed the steps above but when trying to run as limited user gave me:
unable to lock .Xauthority
or something like that and it did not work.
Offline
Ok i followed the steps above but when trying to run as limited user gave me:
unable to lock .Xauthority
or something like that and it did not work.
since you started xfce as root it might be that the .Xauthority file is of the wrong user (ie root). Check the permissions on the file (do a "ls -altr" in your home folder and see if it says root or you own user on the file and check if the permissions are at least rw-rw-r--) and change them if necessary to your regular user with at least 755 permissions i'd say.
It should create the file anew if it is missing so you could also try renaming it to a .Xauthority.org file or something and then try again.
good luck,
stefan
Last edited by stefan1975 (2008-03-04 17:28:58)
"root# su - bofh"
OS: F10_x64, Arch, Centos5.3, RHEL4.7, RHEL5.3
Desktop Hardware: Dell Precision M65 laptop, core2duo, 2gb, 80gb 7200rpm
Registered linux user #459910 since 1998
Offline
well i have read & write permissions to the .Xauthority file but the same thing keeps on happening...
Offline
Just to be sure, could you post the output of:
ls -la /usr/bin/Xorg
I had some problems in starting X a while ago which involved that file.
Have you Syued today?
Free music for free people! | Earthlings
"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- A. de Saint-Exupery
Offline
Pages: 1