Bug 4899 - SlimTray's stop SlimServer option doesn't work on Vista
: SlimTray's stop SlimServer option doesn't work on Vista
Status: CLOSED WORKSFORME
Product: Logitech Media Server
Classification: Unclassified
Component: Slimtray
: 6.5.2
: PC Windows Vista
: P2 normal (vote)
: ---
Assigned To: Ross Levine
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-10 17:25 UTC by Ross Levine
Modified: 2008-12-18 11:11 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Levine 2007-04-10 17:25:20 UTC
6.5.2 4-10-07 with SlimServer installed and running right-clicking SlimTray and selecting Stop SlimServer brings up a small message 'stopping SlimServer...' but it doesn't actually stop. Easy to reproduce.
Comment 1 Ross Levine 2007-04-27 17:31:15 UTC
Thanks to Triode for identifying the cause of this bug. 

The installer installs SlimTray as an application run of the user, which cannot stop or start SlimServer. Running SlimTray 'as administrator' allows SlimTray to stop and start SlimServer; a work around for now. 
Comment 2 Adrian Smith 2007-04-28 10:24:15 UTC
Hopefully change 11852 improves this.

The issue is that UAC means that SlimTray is not able to stop a service when running as a normal user.  

The new slimtray removes options which don't work.  To stop the server if it is run as a service requires starting SlimTray as admin [stop server, right click on SlimTray and select "run as administrator"]  This gives SlimTray admin rights and the ability to perform all operations previously possible from SlimTray.

As a user, if SlimTray is used to start slimserver, then it starts it as an app and so is also able to stop it.  [at present it does not stop mysqld though.]
Comment 3 Ross Levine 2007-04-30 16:47:52 UTC
Works now, thanks Triode!
Comment 4 Chris Owens 2007-05-22 12:10:27 UTC
Fixed in 6.5.2, which is now released and available for download at http://www.slimdevices.com/su_downloads.html

If you're still experiencing this bug, please re-open it!