Comment 1 for bug 661250

I have this problem on the Natty i386 live CD (most recently tested with daily-live natty-desktop-i386.iso, 25-Mar-2011, md5sum cc56ab0dbbfd8c3acd2d0d73e8f2b2bb) which runs indicator-session 0.2.15-0ubuntu1, but only after performing an installation. Before running Ubiquity, the Indicator Session menu has all the normal options in it (logging out, shutting down, restarting), and they all work fine. But after I install (and then select the option to continue testing rather than restarting immediately), the Indicator Session menu only contains Suspend. Since this happens after I run Ubiquity, perhaps it's worth mentioning that the ubiquity package version is 2.5.29. Please note, however, that I have been experiencing this for quite some time (months, or perhaps always but I never noticed until a few months ago), I've just never gotten around to reporting it until now.

When I restart and boot from the installed system, I do not ever experience this problem. It only occurs with the live CD.

I'm not sure if what I'm experiencing is the same as this bug. In particular:

(1) The Indicator Session menu works normally if I don't run the installer. But once I've installed with Ubiquity, then this problem occurs. Is that the case, in this bug?

(2) When I click on the Indicator Session menu, I *only* see the Suspend option. It's not that the other options are there but fail, or that they're there but grayed out. They're not there at all. Is that the case, in this bug?

(3) I'm perfectly *able* to log out, restart, or shut down the computer, without elevating my privileges to root with sudo or a similar mechanism. For example, I can run the command "/usr/lib/indicator-session/gtk-logout-helper --shutdown" (without the quotes), and that will raise a message box asking if I want to shut down the computer. If I say yes, it shuts down successfully. Is that the case, in this bug?

Please let me know, so that I know if I should continue indicating that this bug affects me (and perhaps attach some additional information), or if I should stop indicating that it affects me and instead file a new bug report.

(By the way, in case it's relevant, the machine on which I am testing this is a 32-bit VMware Workstation 7.1.3 build-324285 virtual machine, and the host machine runs Maverick amd64. Since I'm running from the live CD, I haven't installed VMware Tools, but this problem does not occur on an installed Ubuntu system in a VMware virtual machine without VMware Tools installed. While VMware Tools is not installed, the live CD does ship with and run the video and mouse integration guest drivers; specifically, xserver-xorg-video-vmware 1:11.0.3-1ubuntu3 and xserver-xorg-input-vmmouse 1:12.6.99.901-1ubuntu2.)