Gnome Settings Daemon does not start when connecting via VNC
Jan Drewnak
drewnak at gmx.de
Tue Jun 17 16:18:31 UTC 2008
> > This is my /root/.vnc/xstartup file:
> > ******
> > unset SESSION_MANAGER
> > #exec /etc/X11/xinit/xinitrc
> > #[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
> > [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
> > #startkde &
> > gnome-session &
> > ******
> >
> > Did anybody encounter a similar problem or do you have some hints how to
> track
> > down the issue?
>
> Yep, despite the name gnome-session doesn't actually run everything
> you need to start a gnome session :-). I don't normally run a gnome
> session, but something like this may work better for you:
>
>
> if [ -z "$SSH_AUTH_SOCK" ]
> then
> KILL_AGENT=yes
> eval `ssh-agent -s`
> fi
> if [ -z "$DBUS_SESSION_BUS_ADDRESS" ]
> then
> eval `dbus-launch --exit-with-session --sh-syntax`
> fi
> gnome-session
> if [ "$KILL_AGENT" = "yes" ]
> then
> ssh-agent -k
> fi
>
> Possibly the dbus-launch is the only really important bit.
> > This is my /root/.vnc/xstartup file:
> > ******
> > unset SESSION_MANAGER
> > #exec /etc/X11/xinit/xinitrc
> > #[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
> > [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
> > #startkde &
> > gnome-session &
> > ******
> >
> > Did anybody encounter a similar problem or do you have some hints how to
> track
> > down the issue?
>
> Yep, despite the name gnome-session doesn't actually run everything
> you need to start a gnome session :-). I don't normally run a gnome
> session, but something like this may work better for you:
>
>
> if [ -z "$SSH_AUTH_SOCK" ]
> then
> KILL_AGENT=yes
> eval `ssh-agent -s`
> fi
> if [ -z "$DBUS_SESSION_BUS_ADDRESS" ]
> then
> eval `dbus-launch --exit-with-session --sh-syntax`
> fi
> gnome-session
> if [ "$KILL_AGENT" = "yes" ]
> then
> ssh-agent -k
> fi
>
> Possibly the dbus-launch is the only really important bit.
>
Hi Tom and all,
I solved the issue which actually was /two/ issues.
The crashing gnome-settings-daemon issue is described in the Ubuntu bug database which also provides a work-around: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/199245
The access restrisction problems were caused by -- quite obviously, in retrospect -- PolicyKit. Not having read the PolicyKit documentation in detail, I still wonder why users of VNC sessions are handled different compared to locally logged in by default.
Thanks,
Jan
--
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/?mc=sv_ext_mf@gmx
More information about the fedora-list
mailing list