Hi, Leslie
Try this.
Create a file: $HOME/.xinitrc
containing: /usr/local/bin/startxfce4
Then give 'startx' another shot.
I did all the things suggested here at the list with no success so I
decided to clean out and start over.
did pkg_delete -f '*'
rm -r /usr/ports/distfiles
rm
Leslie,
The given port dirs (x11/xorg, etc) still probably have their work
directory, which have the tokens/markers that particular stages of the
port build have been done, such as the installation.
rm -rf /usr/ports/*/*/work
rehash
cd /usr/ports/x11/xorg
make install
Please try that. First
On a newly installed 7.2-RELEASE system with all ports upgraded and
cvsup'ed I have a problem.
Both root and user has
.xsession linked to .xinitrc
and contains
#!/bin/sh
exec /usr/local/bin/startxfce4
If I execute startx as root TWM is started!
If I execute startxfce4 as root XFCE4 is
On Wed, Jun 17, 2009 at 12:27 PM, Leslie Jensenles...@eskk.nu wrote:
On a newly installed 7.2-RELEASE system with all ports upgraded and cvsup'ed
I have a problem.
Both root and user has
.xsession linked to .xinitrc
and contains
#!/bin/sh
exec /usr/local/bin/startxfce4
If I execute
On Wednesday 17 June 2009 08:27:41 Leslie Jensen wrote:
On a newly installed 7.2-RELEASE system with all ports upgraded and
cvsup'ed I have a problem.
Both root and user has
.xsession linked to .xinitrc
and contains
#!/bin/sh
Remove the she-bang and make sure .xinitrc is in $HOME. If
