Bug 12181 - No remote control function for Slimp3
: No remote control function for Slimp3
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: IR
: 7.4.0
: PC Windows Home Server
: -- major (vote)
: 7.4.0
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-27 13:18 UTC by Gary
Modified: 2009-10-05 14:37 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gary 2009-05-27 13:18:31 UTC
I don't think this is a Slimp3 firmware issue but seemed the best place to post this.
Since upgarding 2 or 3 versions ago I have had no remote ir function of my Slimp3 player.
When activating debug logging on player.ir I get the following error:
[09-05-27 20:39:03.5991] Slim::Networking::IO::Select::__ANON__ (113) Error: Select task failed calling Slim::Networking::UDP::readUDP: Undefined subroutine &Slim::Hardware::IR::enqueue called at /<C:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Networking/SliMP3/Protocol.pm line 49.

I have checked and I have no network folder at \squeezecenter\slim
Comment 1 Gary 2009-05-27 13:22:50 UTC
This is on squeezecenter 7.4 26738  but happened around the time you went over to SQLlite I think.
Comment 2 Andy Grundman 2009-05-27 13:23:57 UTC
Hey, don't undo my changes. :)  This is an SC bug.
Comment 3 Andy Grundman 2009-05-27 13:27:20 UTC
Fixed in change 26749.
Comment 4 James Richardson 2009-10-05 14:37:21 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

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