Bug 1920 – SoftSqueeze won't start, gives error message

Bug 1920 - SoftSqueeze won't start, gives error message

Summary:

SoftSqueeze won't start, gives error message

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Softsqueeze
Version:	6.2.0
Platform:	PC Windows XP

Importance:	P2 major (vote)
Target Milestone:	---
Assigned To:	Richard Titmuss

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-08-03 09:04 UTC by Ben Sandee
Modified:	2008-12-15 11:57 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
screenshot showing error message (20.61 KB, image/png) 2005-08-03 09:05 UTC, Ben Sandee	Details
View All 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 Ben Sandee 2005-08-03 09:04:11 UTC

I can't start SoftSqueeze on my machine by launching from the SlimServer link. 
It's Windows XPSP2 with J2SDK 1.5.0_04.

The error I get eventually is in a dialog:

Error starting SoftSqueeze: null
java.util.prefs.AbstractPreferences.put(Unknown source)
...

I'll attach a screenshot with the complete stack trace.

I've not tried to run SoftSqueeze in some time so I don't know if there's
something that recently broke or if it's something unique to my machine.

Thanks

Comment 1 Ben Sandee 2005-08-03 09:05:52 UTC

Created attachment 694 [details]
screenshot showing error message

Comment 2 Blackketter Dean 2005-08-04 17:52:38 UTC

Moving to 6.2.  Richard:  if this affects 6.1 commonly, please move to 6.1.2

Comment 3 Richard Titmuss 2005-08-07 12:21:40 UTC

Fixed, please try Softsqueeze 2.0b11.

Comment 4 Ben Sandee 2005-08-07 18:51:58 UTC

rockin',  works great!

Comment 5 James Richardson 2008-12-15 11:57:37 UTC

This bug has been fixed in the latest release of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.