Alexander:
For two builds (130,131) I hit 13540 bug (Xorg dies on gnome-session startup).
I couldn't make more sophisticated diagnostics, but all other main gnome
processes (gnome-settings-daemon, metacity, nautilus, gnome-panel) may be
launched by hand from xterm and work successfully.
However, I see that people work with these builds successfully. What can be a
reason for such a strange behavior? Can I help in any way in diagnosing this
problem?
GDM saves the stdout/stderr output from your user session in the file
$HOME/.xsession-errors. Try causing the failure to happen and see if
there are any useful error messages in this file which might indicate
what the failure may be.
You can also try modifying the /usr/share/xsessions/gnome.desktop file
so that the Exec line adds the --debug argument, so it looks like this:
Exec=gnome-session --debug
This will cause gnome-session to generate extra debug messages that
should get sent to the $HOME/.xsession-errors file when you log into
a GNOME session from the GDM login screen.
You can also check the Xorg logs in /var/log/Xorg* and /var/log/gdm
to see if there is a reason the Xserver may be crashing.
What happens if you log into a failsafe xterm from the login screen and
run this command:
$ /etc/gdm/Xsession gnome-session --debug
This will start the gnome-session in a more similar way as GDM does, and
might cause the problem to become more visible.
Normally problems with starting the user session after authentication
are not GDM bugs, but you could try to turn on debug in GDM by adding
the "Enable=true" line after the "[debug]" line in /etc/gdm/custom.conf
so it looks like this:
[debug]
Enable=true
Then restart GDM or reboot, create the problem, and see if there are any
useful error messages in the syslog (/var/adm/messages).
It is also possible that some process is crashing. Note that some
processes do not generate core files unless you configure coreadm. I
configure it like this so that system core files (like ones from the
GDM processes or the Xserver) get saved to /var/tmp:
global core file pattern: /var/tmp/core-%f.%p
global core file content: all
init core file pattern: core
init core file content: all
global core dumps: enabled
per-process core dumps: enabled
global setid core dumps: enabled
per-process setid core dumps: enabled
global core dump logging: disabled
You can refer to the coreadm man page to see how to set this up. Once
you do this, if you recreate the problem, you should check to see if
there are any core files named /var/tmp/core*.
Brian
_______________________________________________
opensolaris-discuss mailing list
[email protected]
