| View previous topic :: View next topic |
| Author |
Message |
zbindere
Guru
Joined: 27 May 2004
Posts: 356
Location: Switzerland
|
 Posted: Wed Feb 02, 2005 11:43 am Post subject: xfce4 startscript not working |
 |
|
I installed xfce4 and wanted to start it with:
I got the following errror:
| Code: | /usr/bin/startxfce4: X server already running on display :0.0
xrdb: Connection refused
xrdb: Can't open display ':0.0'
Agent pid 6541
which: no dbus-launch in
(/bin:/usr/bin:/usr/local/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.3.5:/opt/ati/bin:/opt/Acrobat5:/usr/X11R6/bin:/opt/ibm-jdk-bin-1.4.2/bin:/opt/ibm-jdk-bin-1.4.2/jre/bin:/usr/qt/3/bin:/usr/kde/3.3/bin:/usr/kde/3.2/bin:/opt/vmware/bin)xscreensaver: Can't open display: :0.0
(xfce4-session:6544): Gtk-WARNING **: cannot open display:
xscreensaver: initial effective uid/gid was root/users (0/100)
xscreensaver: running as rz/users (1000/100)
xscreensaver: This is probably because you're logging in as root. You
shouldn't log in as root: you should log in as a normal user,
and then `su' as needed. If you insist on logging in as
root, you will have to turn off X's security features before
xscreensaver will work.
Please read the manual and FAQ for more information:
Agent pid 6541 killed
|
I had no X Server running at that time. And gnome works. |
|
| Back to top |
|
 |
tetromino
Retired Dev
Joined: 02 Dec 2003
Posts: 215
|
| Posted: Wed Feb 02, 2005 2:21 pm Post subject: |
|
|
The error messages imply that you do have X running on display :0.0 ; try "psaux | grep X" and see what X servers are active. If you want to launch xfce on a new X server in a new virtual console, you can try "startx /usr/bin/startxfce4 -- :1 vt08" (provided that you don't have X on :1 and the vt08 virtual console is available).
The xscreensaver error implies that you are running as root. Self-explanatory: don't run X as root. Bad for security, and it breaks stuff.
The dbus error suggests you don't have it installed; so emerge sys-apps/dbus. |
|
| Back to top |
|
|
graphic23
Tux's lil' helper
Joined: 06 Dec 2004
Posts: 102
Location: Chicago
|
| Posted: Wed Feb 02, 2005 6:33 pm Post subject: |
|
|
Hi, just do:
killall X.
And as aforementioned, emerge dbus .
after doing these two thigns, you can just do, startxfce4
_________________
Sincerly,
Graphic23 |
|
| Back to top |
|
|
loutr
n00b
Joined: 02 Feb 2005
Posts: 1
Location: New-Caledonia
|
| Posted: Wed Feb 02, 2005 8:12 pm Post subject: |
|
|
hi,
i've got the same problem. However, no X server is running (i launch startxfce4 just after boot), but the $DISPLAY variable is set to ":0.0". If I unset it everything works correctly, until next login... I can't find what gives it that value... |
|
| Back to top |
|
|
zbindere
Guru
Joined: 27 May 2004
Posts: 356
Location: Switzerland
|
| Posted: Wed Feb 02, 2005 8:30 pm Post subject: |
|
|
I didn't have an X Server running. However it works wenn I run
| Code: | | startx /usr/bin/startxfce4 |
Is it not possible to put something like:
in the /etc/rc.conf |
|
| Back to top |
|
|
GrayFox
Apprentice
Joined: 24 Jan 2004
Posts: 183
Location: Germany
|
|
| Back to top |
|
|
FrozenMist
n00b
Joined: 01 Dec 2004
Posts: 30
|
| Posted: Thu Feb 03, 2005 5:47 am Post subject: |
|
|
| I get the same error, except I just put at the end of my .xinitrc file, so it works fine for me. |
|
| Back to top |
|
|
zbindere
Guru
Joined: 27 May 2004
Posts: 356
Location: Switzerland
|
| Posted: Thu Feb 03, 2005 9:25 pm Post subject: |
|
|
| it worked, it was the pam bug. |
|
| Back to top |
|
|
|
Desktop Environments
