This is a plain install of OpenSolaris. I'm not hacker enough to have rebuilt D-Bus or gnome-session by hand. I installed Flash, jdk 6, netbeans, and a few other apps from IPS. I configured Compiz and my desktop the way I wanted it. Other than that it's fresh off the installation CD. I'm using a Sun Ultra 24.
I may have pressed CTRL-ALT-BACKSPACE to get back to the login screen so that I could log into an xterminal to capture the logs you needed. Not sure if that would have caused some of the errors you saw? The system performance would degrade each time I would log in/out without rebooting the computer. I also re-installed the OS three times because after a week or two I could no longer log in (blank screen). Since then I've wiped the hard drive and installed Ubuntu 8.04. I left some space at the end of the drive to install OpenSolaris and help diagnose if someone tells me that it can co-exist with Ubuntu (including configuring GRUB for me). Thanks, Ryan Brian Cameron wrote: > > Ryan: > > The error messages about "This process is currently running > setuid/setgid" seems to indicate that the login process (perhaps in > the GDM PreSession script) should be looked into. We shouldn't be > trying to run any setuid/setgid GTK+ programs in general. If you > can help identify what program is generating this error, then we > could look into fixing this. > > However, I suspect the problem with session not starting up properly > is that D-Bus isn't being started properly on your system. I notice the > error "Cannot locate dbus-daemon" in your log files. Do you have > dbus-daemon installed on your machine? Normally on Solaris it is > installed to /usr/lib. Note that on Solaris, we patch gnome-session so > it finds the dbus-daemon in /usr/lib. If you rebuilt D-Bus or > gnome-session by hand, you need to make sure that you apply the same > patches we use, or you may have broken things. > > As a workaround, it might fix things for you if you edit > /usr/share/xsessions/gnome.desktop so it runs the following command > instead of just calling "gnome-session". > > dbus-launch --exit-with-session gnome-session > > Another workaround might be to make a symlink from /usr/lib/dbus-daemon > to /usr/bin/dbus-daemon. > > Brian > > >>>> The ticket suggested booting to the login screen and waiting some time >>>> before logging in. I waited hours (went out) then logged in. Same >>>> gray >>>> screen. There is absolutely nothing on the screen except a mouse >>>> pointer. >>>> No gnome panels, icons or anything. I don't think gnome panel is >>>> even >>>> running but I can't check because I don't know how to drop to a >>>> command >>>> prompt from here. In Linux I could press CTRL-ALT-F1 or something >>>> like that >>>> to switch to console. >>>> >>>> I have had times where I log in, gnome starts and I can see each >>>> item it >>>> adds to the panel takes a good 30 seconds or so, while CPU is under >>>> heavy >>>> use. I think this is different. >>>> >>> >>> You might want to check ~/.xsession-errors or the dmesg command output. >>> >> I have uninstalled all compiz packages and rebooted. I still get a >> completely blank screen and mouse pointer whenever logging in. I >> have captured the .xsession-errors file and am about to re-install >> the OS. There are some interesting errors in both files. >> >> >> Thanks, >> Ryan >> >> >> ------------------------------------------------------------------------ >> >> This body part will be downloaded on demand. > >
