Bug 1377 - Server dies when clicking on Player settings
: Server dies when clicking on Player settings
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Streaming From SlimServer
: 6.0.1
: PC RedHat Linux
: P2 critical (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-14 08:35 UTC by Ben Gritz
Modified: 2008-09-15 14:37 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Gritz 2005-04-14 08:35:10 UTC
Hi, 

I run the latest rpm on fedora core 3.  I use slimserver for streaming music
from my box at home to where i work.

On the latest version (6.x.x), every time I click on the "Player Settings" link,
the slimserver dies and I have to restart it.  Have re-installed version 5.x.x
and that works fine....any ideas why this might be?  

Not sure where the player settings are kept.  If they are not in the
slimserver.db it could be to do with some permissions on the folder where they
are kept?

Cheers

Ben
Comment 1 KDF 2005-04-14 09:48:13 UTC
please supply the actual crash message from the log, or froma command line run
of slimserver.pl.  There was a crash when entering browse playlist or player
settings that has been fixed in the latest nightly builds.  Try that as well and
close this if it works.
Comment 2 Ben Gritz 2005-04-14 10:55:54 UTC
Here's the info from the log:

Can't locate object method "playingModeOptions" via package "Slim::Player::HTTP"
at /usr/local/slimserver//Slim/Web/Setup.pm line 157.

Will attempt to build snapshot tonight and let you know
Comment 3 KDF 2005-04-14 11:12:18 UTC
for certain this is fixed. latest from svn repo, or tar.gz of nightly build
should have it.
Comment 4 Ben Gritz 2005-04-14 12:07:49 UTC
Installed latest rpm and seems to work fine.  Thanks for your help
Comment 5 Chris Owens 2006-06-16 14:39:48 UTC
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.