Bug 7391 - Slow/frozen interaction with remote control
: Slow/frozen interaction with remote control
Status: RESOLVED FIXED
Product: SB 2/3
Classification: Unclassified
Component: Misc
: unspecified
: PC Debian Linux
: -- blocker (vote)
: ---
Assigned To: Felix Mueller
:
Depends on: 6823
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-03 12:40 UTC by Thomas Morin
Modified: 2008-03-07 18:11 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments
Network trace. (245.29 KB, application/cap)
2008-03-03 12:45 UTC, Thomas Morin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Morin 2008-03-03 12:40:12 UTC
[ The firmware release is 86 (not available in the bugzilla dropdown, by the way). ]

A few weeks ago, a few days after having received it and used for the first times, I noticed that my Squeezebox v3 was very slow after each power up : seconds before taking into account a key press on the remote, until I could manage to play a song, after what everything was just fine, until next sleep/wake up. For this reason, I upgraded my slimcenter, and since the problem has gotten worse : reactions to keypresses are so slow that I thought the SB wasn't even receiving the keypresses. 

I tried upgrading again, I'm now running 7.0.1-17786 on a Debian Linux, but things aren't better.
I have taken network dumps (wireshark) to try to understand what the issue, and noticed a lot of TCP errors.
I switched from a Wifi connection to a plain wire RJ45 Ethernet connection, but things did not improve (nor degrade).
At this point, I can only control the SB from the SC interface, but not even all the time since sometimes it does not even wake up.

I'm attaching a tcpdump trace taken on the slimcenter host, and I'm willing to test any suggested fix and to provide any required detail.
Comment 1 Thomas Morin 2008-03-03 12:45:01 UTC
Created attachment 3030 [details]
Network trace.

Actions made after starting up the trace:
- plug power into SB
- plug the ethernet cord into SB
- wait
- after some time press a few keypresses on the remote in front of the SB : up/down...etc
Comment 2 Felix Mueller 2008-03-05 14:02:50 UTC
Could you check if in Settings - Player - Basic Settings there is a player name defined?
If there is no player name, please enter one and save the change, power-cycle the player and the remote should work again.
Comment 3 Thomas Morin 2008-03-06 00:03:00 UTC
The proposed workaround did actually work the problem around: adding a name to the player made navigation with the remote work again.  Thank you!

Is is in fact a quite surprising fix, I have a hard time correlating TCP errors with an empty player name with seems an application-level and not a network-level issue...

Comment 4 Michael Herger 2008-03-07 18:11:18 UTC
change 17819 - enforce player name to prevent unexpected behaviour with empty names