On Sun, Mar 1, 2009 at 8:54 AM, Kevin Kammer <BateleurRGB at mac.com> wrote: > I have encountered a strange error since upgrading to snv_107. After booting, > gdm attempts to start an X session, but fails. After several retries, the X > server gives up, and the console login screen remains. Thereupon, I can login > to a text session, and type: > > $ pfexec svcadm restart gdm > > ...and X starts up with no problem. > > An examination of /var/log/Xorg.0.log (corresponding to the current, > successful X session) and /var/log/Xorg.0.log.old (corresponding to the X > failure, when gdm came up as part of the boot process) shows that there is no > difference in the logs, except the failed log ends with a backtrace and > "Fatal server error: Caught signal 11. ?Server aborting." All other steps in > the log are identical between the working and the crashed X sessions. > > This happens every time I reboot; the gdm service must be restarted manually, > whereupon everything works as it should. > > I'm not sure where to start troubleshooting this issue, given that the Xorg > log shows no abnormalities, until it crashes and burns, apparently for no > reason. Any ideas or advice would be appreciated. > -- > This message posted from opensolaris.org > _______________________________________________ > opensolaris-help mailing list > opensolaris-help at opensolaris.org >
I see the same issue on snv_108 currently. I haven't found a fix, and am stuck with just console login currently. My advice: revert to snv_106 if you can. -- Brent Jones brent at servuhome.net
