i run xdm normally. after logging it runs my $HOME/.xsession that starts
things like fvwm2
i wanted to run gnome-session once, changed fvwm2 to
/usr/local/bin/gnome-sessions
after loggin in it just exits. no .xsession-errors is created. no idea
where to seek error messages at all.
with
On Sat, 21 Jul 2012 19:19:15 +0200 (CEST), Wojciech Puchar wrote:
i run xdm normally. after logging it runs my $HOME/.xsession that starts
things like fvwm2
i wanted to run gnome-session once, changed fvwm2 to
/usr/local/bin/gnome-sessions
^
Is this a typo?
Is this a typo?
According to the Handbook, /usr/local/bin/gnome-session
(without trailing 's') should be executed.
indeed a typo.
thank you.
after loggin in it just exits. no .xsession-errors is created. no idea
where to seek error messages at all.
Maybe errors are reported to the 1st
On Sat, 21 Jul 2012 20:40:44 +0200 (CEST), Wojciech Puchar wrote:
after loggin in it just exits. no .xsession-errors is created. no idea
where to seek error messages at all.
Maybe errors are reported to the 1st virtual terminal
where the XDM process outputs its messages to (currently
adding
DisplayManager*authName:MIT-MAGIC-COOKIE-1
solves the problem.
Do you have any data about preparations that gdm do?
The Handbook mentions /proc to be mounted, but that's not
related. The settings
gdm_enable=YES
gnome_enable=YES
in /etc/rc.conf would
