Bug#526807: gnome-panel: shutdown button does not work after upgrade to 2.26

[Josselin Mouette]

Le lundi 04 mai 2009 à 13:54 +0200, Norbert Preining a écrit :
> I have removed all autostart files and it worked. 

Good. It would still be interesting to know what added them, and how it
made gnome-session crash, because it looks like something ready to
happen again on other people’s systems.

> Now it starts, but still the shutdown button is greyed out.
> Interestingly, once I saw the button NOT greyed out, but then again
> greyed out after logging in. Strange.

If you just installed consolekit, you may need a gdm restart. Note that
if several people are logged on, it will be greyed out and that is
expected.

> > I’d appreciate if you could retry with a gnome-session built with
> > debugging symbols. It would already give the name of the function.
> 
> I didn't find gnome-session-dbg, are there any debug symbols for that,
> or do I have to recompile the beast?

Yes, unfortunately you need to recompile it for the moment.

> Here are the errors of the current start, I assume that it has something
> to do with the 
> 	Window manager warning: Failed to read saved session file /home/norbert/.config/metacity/sessions/1079.....

This warning is harmless. Something saved the metacity state but the
state file was removed in the meantime. 

> Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
> GNOME_KEYRING_SOCKET=/tmp/keyring-vAPIMl/socket
> SSH_AUTH_SOCK=/tmp/keyring-vAPIMl/socket.ssh
> Window manager warning: Failed to read saved session file /home/norbert/.config/metacity/sessions/1079a8cf9d3bf0fe1f124143772678761700000271310020.ms: Failed to open file '/home/norbert/.config/metacity/sessions/1079a8cf9d3bf0fe1f124143772678761700000271310020.ms': No such file or directory

The gnome keyring environment shows up late, I assume you are not using
libpam-gnome-keyring; otherwise this is normal.

> gnome-session[27131]: WARNING: Unable to parse command '(null)': Key file contains key 'Terminal' which has value that cannot be interpreted.
> gnome-session[27131]: WARNING: Could not launch application 'smart-notifier.desktop': Unable to start application: Key file contains key 'Terminal' which has value that cannot be interpreted.

Haha, so I was wrong, the buggy Terminal line is not the one triggering
the crash earlier. This is clearly a bug in smart-notifier. “False” is
not an accepted boolean value; “false” is.

-- 
 .''`.      Josselin Mouette
: :' :
`. `'   “I recommend you to learn English in hope that you in
  `-     future understand things”  -- Jörg Schilling
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Ceci est une partie de message num?riquement sign?e
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20090504/2e75e243/attachment.pgp>