Ume Launcher install is not exclusive to current user.

[Michael Z Freeman]

I created another user to test Netbook. When I changed users Ume Launcher still started up over the desktop on the separate (non Netbook Remix) user.

[Neil Mclean (nwmclean)]

Same thing happened to me. Created a separate account just to test the remix. Got it all working nicely. It is VERY nice on an eeepc 900 - excellent work.

When I logged out of that account and logged in on another account (non-netbook remix) I found the ume-launcher loaded up over the desktop. Killed the process and had to disable it in "sessions". (Had to repeat the process to disable ume-launcher in "sessions" for all accounts on the pc).

[Bill Filler (bfiller)]

We should consider removing the ume-launcher.desktop file (that gets installed in /etc/xdg/autostart) out of the ume-launcher package and into the appropriate configuration package (ume-config-netbook). That way, simply installing ume-launcher won't autostart for all users (downside is you'll have to manually start it for desired user or add it via "Sessions").

[Bill Filler (bfiller)]

for Jaunty the decision was made to have an autostart file installed by the netbook-launcher package

[Michael Z Freeman (michael-z-freeman)]

What is the situation for Hardy ? Which is the Ubuntu I'm using.

The issue with this bug is that it makes testing and development difficult. I don't want to work using a dev installation. The other issue is that last time I checked it is difficult to switch to the full desktop if all logins are hogged by ume :)

[Neil J. Patel (njpatel)]

The hardy and intrepid packages do _not_ have the autostart file. If, by some chance, you do have a autostart file, you can esily disable it by removing /etc/xdg/autostart/launcher.desktop.