Bug 6209 – SqueezeCenter opens UI even on user login - it shouldn't

Bug 6209 - SqueezeCenter opens UI even on user login - it shouldn't

Summary:

SqueezeCenter opens UI even on user login - it shouldn't

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Slimtray
Version:	7.0
Platform:	PC Windows XP

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Michael Herger

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-11-21 09:49 UTC by Dan Evans
Modified:	2008-12-18 11:12 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dan Evans 2007-11-21 09:49:44 UTC

Previously SqueezeCenter would only auto-open if you started it manually from the tray icon.  Currently with the latest builds it auto-opens when I log in to Windows.  Is this intentional or a bug?  

I think the SC UI should only open when the user initiates it; e.g. they click 'Open SC' or they start it manually with 'Start SC' or browse to localhost:9000.

Thoughts?

Comment 1 Michael Herger 2007-11-21 21:31:51 UTC

Are you running it as a service or on logon?

Comment 2 Michael Herger 2007-11-22 01:02:14 UTC

change 14930 - I've reorganized the opening of the page a bit. It should now work as expected. But the change might have side effects on starting it from the desktop icon, tray etc., too. So please test this change. It should be in the 11-22 nightly build (trunk only, no special builds). Please reopen if you encounter any problem. Thanks.

Comment 3 Dan Evans 2007-11-26 10:59:21 UTC

Tested this morning's trunk build.  It no longer auto-opens when I log in.

Comment 4 Chris Owens 2008-03-07 09:04:27 UTC

This bug is being closed since it was resolved for a version which is now released!  Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html

If you are still seeing this bug, please re-open it and we will consider it for a future release.