Bug 3628 – hit play on any RSS feed causes SS to crash

Bug 3628 - hit play on any RSS feed causes SS to crash

Summary:

hit play on any RSS feed causes SS to crash

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Plugin
Version:	6.3.0
Platform:	Macintosh MacOS X 10.4

Importance:	P2 minor (vote)
Target Milestone:	---
Assigned To:	Chris Owens

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-06-23 13:37 UTC by Ross Levine
Modified:	2008-09-15 14:38 UTC (History)
CC List:	4 users (show)

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 Ross Levine 2006-06-23 13:37:41 UTC

SlimServer Version: 6.3.0 - 8002 - Mac OS X 10.4.6 (8I127) - EN - utf8

TMID 5531 discovered this bug. I easily verified the existance of this bug. 

Also for some reason, RSS isn't a default option, needed to be added from player settings. 

Try going to any RSS feed, and hit play, Slim Server immediatly crashes.

Comment 1 KDF 2006-06-23 14:03:14 UTC

Reverse the conditionals on XMLBrowser.pm line 743 to:
elsif ( ref($item->{'items'}) eq 'ARRAY' && scalar @{$item->{'items'}} ) {

can do tonight, unless andy wants to beat me to it :)


as for default option, I think there is a request to have it in Plugins at least, instead of buried in screensavers (which it is).  Don't think there is currently a clean way to have a plugin in multiple places in the plugin menu structure.  Altering the default Home list of options is easy enough (especially if you don't need to force the change on existing users as well)

Comment 2 Andy Grundman 2006-06-23 14:12:11 UTC

Fixed, thanks kdf.

Comment 3 Ross Levine 2006-06-26 12:44:35 UTC

SlimServer Version: 6.3.0 - 8132 - Mac OS X 10.4.6 (8I127) - EN - utf8

Verified to be fixed.

Comment 4 Chris Owens 2006-06-27 14:22:05 UTC

This bug fix is now part of a released version, and so has been marked closed. If you are still experiencing this problem, please reopen the bug.