Ryan:
I'm not sure if I'm still getting those error messages but I actually
cleared up the issue. You were correct the gconf session variables
weren't set. I checked /etc/gconf/gconf.xml.defaults and the folder
was empty, so I just added the contents from a default opensolaris
install and everything started to work after that. I'm not sure if
the default config is part of a package I wasn't aware of, but
everything is fine now.
Great, have a fun time with OpenSolaris!
Everyone, thanks for all the help.
Debugging these kinds of problems can be hard. If you have a blog, it
would be interesting to see a write-up of your experiences getting
things working. If you do, let us know. Blogging can also help other
people who run into the same sorts of problem, or who want to do
the same sort of thing.
I can't tell you the number of times I have found solutions to problems
by googling and finding blog entries.
Brian
On Sat, Dec 12, 2009 at 5:14 PM, Brian Cameron <brian.came...@sun.com> wrote:
Ryan:
Messages that org.gnome.SessionManager are odd. If gnome-session is
running, then other process should be able to connect to the
SessionManager. Is the gnome-session process running?
It might be worthwhile to test other D-Bus functionality and try to
determine if this might be a problem with D-Bus communications in
general.
The messages also seem to indicate problems with setting up sockets.
Again, it might be worthwhile to investigate whether there is a
general problems with sockets.
Most of the messages seem to be about gnome-keyring. I don't think
gnome-keyring is essential for the session to startup. So, if the
problems are only with gnome-keyring, I am surprised this is causing
the session to hang.
Did you try googling for the error messages you are seeing and find
out if there are any suggestions on the internet about what common
problems that exhibit this behavior might be?
Brian
Yes all the packages are installed. Apparently I can't redirect
gnome-session output to a file so I'm going to try and transcribe this as
best I can.
/usr/X11/bin/dispswitch exiting: too few (less than 2) or too many (more
than 2)
crtcs: 1
No value set for `/desktop/gnome/applications/at/visual/exec
That is all I get on launch. On exit the following shows up.
Message: another SSH agent is running at: /var/tmp/keyring-W0O11d/ssh
** (gnome-keyring-daemon-wrapper:636): WARNING **: Could not set
SSH_AUTH_SOCK: Message did not receive a reply (timeout by message bus)
** (gnome-keyring-daemon-wrapper:636): WARNING **: Could not set
GNOME_KEYRING_PID: The name org.gnome.SessionManager was not provided by any
.service files
** (gnome-keyring-daemon-wrapper:636): WARNING **: Could not set
SSH_AUTH_SOCK: Message did not receive a reply (timeout by message bus)
** (gnome-keyring-daemon-wrapper:636): WARNING **: Could not set
GNOME_KEYRING_PID: The name org.gnome.SessionManager was not provided by any
.service files
** (gnome-keyring-daemon-wrapper:636): WARNING **: couldn't connect to
daemon at $GNOME_KEYRING_SOCKET: /var/tmp/keyring-W0O11d/socket: No such
file or directory
** (gnome-keyring-daemon-wrapper:636): WARNING **: Could not set
GNOME_KEYRING_SOCKET: The name org.gnome.SessionManager was not provided by
any .service files
** (gnome-keyring-daemon-wrapper:636): WARNING **: Could not set
SSH_AUTH_SOCK: The name org.gnome.SessionManager was not provided by any
.service files
(gnome-keyring-daemon-wrapper:636): EggSMClient-WARNING **: Failed to
connect to the session manager: Could not open network socket
On Fri, Dec 11, 2009 at 12:22 PM, Hemantha Holla <hemantha.ho...@sun.com
<mailto:hemantha.ho...@sun.com>> wrote:
Ryan Proud wrote:
I'm having some issues getting gnome up and running off of a
minimal opensolaris virtualbox appliance. I've got X and GDM
running but when I try and launch a gnome session I just get a
blank desktop (no panel, no nautilus, yada yada yada). I'm
trying to find some logs that would be helpful but I'm having
some difficulties. Could someone point me in the correct
direction and if I'm still having issues after digging into the
logs, I can come back and ask a few more meaningful questions.
Are those components installed ? gnome panel is in the
package SUNWgnome-panel and nautilus in SUNWgnome-file-mgr.
You could also try to manually start gnome-session
(/usr/bin/gnome-session) after logging into failsafe
terminal and look at the output spewed by redirecting it to
a file (also look at thread [1])
HTH
Hemantha
[1]
http://mail.opensolaris.org/pipermail/desktop-discuss/2009-January/010872.html
------------------------------------------------------------------------
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
