[OpenIndiana-discuss] Gnome session start problem: gnome-panel not visible

Jonathan Adams t12nslookup at gmail.com
Fri Jul 4 13:19:07 UTC 2014


At this point, I'm probably out of my depth ...

For reference: I have the "sm-client-id" running on "nautilus" and
"gnome-panel" on my system (hipster illumos-b461c74)


On 4 July 2014 14:04, Carsten Grzemba <grzemba at contac-dt.de> wrote:

> yes, but all users are new and the
> $ gnome-cleanup
> I have also already tried.
>
> How is the login process controled? it is possible to raise some debug
> levels somewhere.
>
> The difference which I can see too working session on an other host is
> that gnome-panel and nautilus is started with an option --sm-client-id <id>,
> which in the failing session is missing.
>
> Am 04.07.14 schrieb Jonathan Adams  <t12nslookup at gmail.com>:
> > is the problem after the login screen?
> >
> > If so can you try logging in a new user, in case it's a configuration
> issue?
> >
> > Jon
> >
> >
> > On 4 July 2014 13:21, Carsten Grzemba <grzemba at contac-dt.de> wrote:
> >
> > >
> > >
> > > Am 04.07.14 schrieb Jonathan Adams <t12nslookup at gmail.com>:
> > > > the pixmaps thing ... hmm I've seen that before, let me find the
> command
> > > to
> > > > fix it.
> > > >
> > > >
> > > > yep, found it:
> > > >
> > > > root at jadlaptop:~# gdk-pixbuf-query-loaders --update-cache
> > > >
> > > > root at jadlaptop:~# grep -i svg
> > > /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache
> > > > "/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so"
> > > > "svg" 2 "gdk-pixbuf" "Scalable Vector Graphics" "LGPL"
> > > > "image/svg+xml" "image/svg" "image/svg-xml" "image/vnd.adobe.svg+xml"
> > > > "text/xml-svg" "image/svg+xml-compressed" ""
> > > > "svg" "svgz" "svg.gz" ""
> > > > " <svg" "* " 100
> > > > " <!DOCTYPE svg" "* " 100
> > > >
> > > Ok, this helps for the SVG images, thanks,
> > > but the problem with gnome-panel still exist.
> > >
> > > >
> > > >
> > > >
> > > > On 4 July 2014 11:37, Carsten Grzemba <grzemba at contac-dt.de> wrote:
> > > >
> > > > >
> > > > >
> > > > > Am 04.07.14 schrieb Jonathan Adams <t12nslookup at gmail.com>:
> > > > > > What do you have set under "Appearance" -> "Visual Effects" ?
> > > > > >
> > > > > >
> > > > > There is set 'None'
> > > > >
> > > > > but there are logged some warnings on startup:
> > > > > (gnome-appearance-properties:3374): Gtk-WARNING **: Could not load
> > > image
> > > > > '/usr/share/gnome-control-center/pixmaps/visual-effects_none.svg':
> > > Couldn't
> > > > > recognize the image file format for file
> > > > > '/usr/share/gnome-control-center/pixmaps/visual-effects_none.svg'
> > > > >
> > > > >
> > > > > >
> > > > > > I had issues a while back where I could no longer run compiz on
> > > Illumos
> > > > > > (Intel based graphics) and had to turn it off to get the desktop
> > > working
> > > > > > correctly ...
> > > > > >
> > > > > > Jon
> > > > > >
> > > > > >
> > > > > > On 4 July 2014 10:33, Carsten Grzemba <grzemba at contac-dt.de>
> wrote:
> > > > > >
> > > > > > > On a new oi151a9 installation I have the problem that on gnome
> > > session
> > > > > > > start, the gnome-panel is not visible. I get only the green
> > > backdrop,
> > > > > but I
> > > > > > > can start a terminal with right mouse click context menu.
> > > > > > > if I run in the terminal:
> > > > > > > $ gnome-panel --replace
> > > > > > > all is fine.
> > > > > > >
> > > > > > > What is going wrong on session start? .xsession-erros logs
> only:
> > > > > > >
> > > > > > > /etc/gdm/Xsession: Beginning session setup...
> > > > > > > /etc/gdm/Xsession: Setup done, will execute:
> /usr/bin/ssh-agent --
> > > > > > > gnome-session_IceTransmkdir: Owner of /tmp/.ICE-unix should be
> set
> > > to
> > > > > root
> > > > > > >
> > > > > > > ** (gnome-settings-daemon:2066): WARNING **: Call to
> > > screen_info_new is
> > > > > > > too frequent, skipping...
> > > > > > >
> > > > > > > ** (gnome-settings-daemon:2066): WARNING **: Call to
> > > screen_info_new is
> > > > > > > too frequent, skipping...
> > > > > > > GNOME_KEYRING_CONTROL=/var/tmp/keyring-R41G3b
> > > > > > > SSH_AUTH_SOCK=/var/tmp/keyring-R41G3b/ssh
> > > > > > > GNOME_KEYRING_PID=2068
> > > > > > > GNOME_KEYRING_CONTROL=/var/tmp/keyring-R41G3b
> > > > > > > SSH_AUTH_SOCK=/var/tmp/keyring-R41G3b/ssh
> > > > > > > GNOME_KEYRING_CONTROL=/var/tmp/keyring-R41G3b
> > > > > > > SSH_AUTH_SOCK=/var/tmp/keyring-R41G3b/ssh
> > > > > > > /usr/bin/dispswitch exiting: too few (less than 2) or too many
> > > (more
> > > > > than
> > > > > > > 2) crtcs: 1
> > > > > > >
> > > > > > > ** (gnome-power-manager:2085): WARNING **: DBUS error: Could
> not
> > > get
> > > > > owner
> > > > > > > of name 'org.gnome.ScreenSaver': no such name
> > > > > > > ** (gnome-power-manager:2085): DEBUG: proxy is NULL, maybe the
> > > daemon
> > > > > > > responsible for org.gnome.ScreenSaver is not running?
> > > > > > > ** Message: Initializing gksu extension...
> > > > > > > Initializing nautilus-open-terminal extension
> > > > > > >
> > > > > > > (nautilus:2075): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c:
> line
> > > > > 2468:
> > > > > > > assertion `format != NULL' failed
> > > > > > > -
> > > > > > >
> > > > > > > and
> > > > > > > $ ptree `pgrep gnome-session`
> > > > > > > 1427 /usr/sbin/gdm-binary
> > > > > > > 1429 /usr/lib/gdm-simple-slave --display-id
> > > > > > > /org/gnome/DisplayManager/Displa
> > > > > > > 1732 /usr/lib/gdm-session-worker
> > > > > > > 2027 gnome-session
> > > > > > > 2046 /usr/bin/ssh-agent -- gnome-session
> > > > > > > 2071 metacity
> > > > > > > 2072 gnome-panel
> > > > > > > 2075 nautilus
> > > > > > > 2078 /usr/bin/xscreensaver -nosplash
> > > > > > > 2083 /usr/bin/python2.6 /usr/lib/updatemanagernotifier
> > > > > > > 2084 /usr/perl5/bin/perl
> /usr/bin/desktop-print-management-applet
> > > > > > > 2090 /usr/lib/ospm/ospm-applet
> > > > > > > 2085 gnome-power-manager
> > > > > > > 2089 /usr/lib/nwam-manager
> > > > > > > 2093 python2.6 /usr/lib/time-slider-notify
> > > > > > > 2094 /usr/lib/evolution/2.30/evolution-alarm-notify
> > > > > > >
> > > > > > > which looks normal for me.
> > > > > > >
> > > > > > > Any help appreciated.
> > > > > > > _______________________________________________
> > > > > > > openindiana-discuss mailing list
> > > > > > > openindiana-discuss at openindiana.org
> > > > > > > http://openindiana.org/mailman/listinfo/openindiana-discuss
> > > > > > >
> > > > > > _______________________________________________
> > > > > > openindiana-discuss mailing list
> > > > > > openindiana-discuss at openindiana.org
> > > > > > http://openindiana.org/mailman/listinfo/openindiana-discuss
> > > > > >
> > > > > >
> > > > > _______________________________________________
> > > > > openindiana-discuss mailing list
> > > > > openindiana-discuss at openindiana.org
> > > > > http://openindiana.org/mailman/listinfo/openindiana-discuss
> > > > >
> > > > _______________________________________________
> > > > openindiana-discuss mailing list
> > > > openindiana-discuss at openindiana.org
> > > > http://openindiana.org/mailman/listinfo/openindiana-discuss
> > > >
> > > >
> > > _______________________________________________
> > > openindiana-discuss mailing list
> > > openindiana-discuss at openindiana.org
> > > http://openindiana.org/mailman/listinfo/openindiana-discuss
> > >
> > _______________________________________________
> > openindiana-discuss mailing list
> > openindiana-discuss at openindiana.org
> > http://openindiana.org/mailman/listinfo/openindiana-discuss
> >
> >
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss
>


More information about the openindiana-discuss mailing list