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

[Norbert Preining]

On Mo, 04 Mai 2009, Josselin Mouette wrote:
> > 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.

I logged-out-added-autostart-logged-in and it is absolutely not
reproducibly. Really strange. Sometimes after adding an autostart item
it crashed, the second time it worked, but diff-ing the desktop files
between the saved autostart and the actual one did not show any
differences.

> 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.

In the course of the session above I realized that it is approximately
every second time it is greyed out and every second time it works.

When I reboot from fresh and log in the first time the button is
working. Logging out and logging in again makes it greyed out.
Maybe the logic of deducing whether someone else is logged in is flawed?

> > 	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. 

Ok.

> > 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.

Right, I am starting the gnome session via ssh-agent, is that what you
mean?

> > 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.

Ok, I changed it in /etc/xdg/autostart/smart-notifier.desktop to false.

> `. `'   “I recommend you to learn English in hope that you in
>   `-     future understand things”  -- Jörg Schilling

Aehmmm ... JS is my favorite ;-)

Best wishes

Norbert

-------------------------------------------------------------------------------
Dr. Norbert Preining <preining at logic.at>        Vienna University of Technology
Debian Developer <preining at debian.org>                         Debian TeX Group
gpg DSA: 0x09C5B094      fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
AYNHO (vb.)
Of waiters, never to have a pen.
			--- Douglas Adams, The Meaning of Liff