Bug 1068 - Visualizers avialable for setting on SB1 even though they aren't supported.
: Visualizers avialable for setting on SB1 even though they aren't supported.
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 6.0.0
: All All
: P2 minor (vote)
: Future
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-03-13 08:31 UTC by Brad King
Modified: 2011-01-24 05: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 Brad King 2005-03-13 08:31:25 UTC
I get the following error on Debian Linux:

Can't locate object method "sendFrame" via package "Slim::Player::SLIMP3" at
/home/guest/SlimServer
_v2005-03-08/Plugins/Visualizer.pm line 249.
Use of uninitialized value in string eq at
/home/guest/SlimServer_v2005-03-08/Slim/Utils/Timers.pm 
line 147 during global destruction.
Then the server crashes (killing all processes)
This occurs when I choose a Visualization Plugin that will not work for me
slimp3 for a screensaver.  (I know this is not correct to do, but the web
interface cheerfully lets me do it.) Presumably the bugfix is to prevent the web
interface from proposing inappropriate plugins for the device.  Either that or
more gracefully handling the situation)
For Reference I am running a Slimp3 with firmware 2.3 using the following Linux
config:

Linux 2.6.11 #1 Wed Mar 2 22:37:11 CET 2005 i686 GNU/Linux
$ perl --version

This is perl, v5.8.4 built for i386-linux-thread-multi

Copyright 1987-2004, Larry Wall
Comment 1 KDF 2005-03-13 11:42:49 UTC
I believe this crash should be fixed already in the nightly builds.  Can you try
that, and let us know?
Comment 2 Brad King 2005-03-13 23:46:01 UTC
SlimServer_v2005-03-13 nightly build fixes the crash, sometimes pops up a screen
on the player saying the mode is only supported on Squeeze2.  (I say sometimes,
it did this on the first click, never thereafter) 

The end user confusion remains however, the web interface shows that the
graphical mode is selected, but in reality, it isn't.  Maybe some simple verbage
of explaination would be enough.  I reloaded the page and it still indicates the
visualization mode is selected.

I confirm that the server crash no longer occurs, which certainly lowers the
bug's priority.
Comment 3 Blackketter Dean 2005-04-04 17:25:41 UTC
We'll fix this in the next release.
Comment 4 Blackketter Dean 2007-10-22 16:57:21 UTC
is this still an issue?