Bugzilla – Bug 617
Sending a "display" command via CLI will stop a paused player
Last modified: 2008-12-18 11:54:09 UTC
When I issue a command like this to a paused player: player-id display test test 30 the players mode will change from "pause" to "stop" *AFTER* the displayed text goes away (30 seconds in the above example). The players mode should not be affected such a display command. It should stay in a paused state.
I'm not sure why this happens yet, but one of the other patches I have in my own setup seems to have already fixed this. It looks, perhaps, like the current showBriefly for SqueezeboxG loops too fast. For long display times, this causes a disconnect and the player comes back in stopped mode. Here is the debug info showing that case: 2004-10-08 21:38:40.9445 songTime: [2.099875] = (33598(realpos) / 27849037(size) * 1740.5648125(duration) * 1(rate)) + 0(time offset of started stream) 2004-10-08 21:39:01.0071 Backtrace: frame 0: Slim::Player::Source::playmode (/usr/local/slimserver/clean/server/Slim/Player/ Squeezebox.pm line 67) frame 1: Slim::Player::Squeezebox::reconnect (/usr/local/slimserver/clean/server/Slim/Networking/ Slimproto.pm line 328) frame 2: Slim::Networking::Slimproto::process_slimproto_frame (/usr/local/slimserver/clean/server/ Slim/Networking/Slimproto.pm line 233) frame 3: Slim::Networking::Slimproto::client_readable (/usr/local/slimserver/clean/server/Slim/ Networking/Select.pm line 116) frame 4: Slim::Networking::Select::select (./slimserver.pl line 454) frame 5: main::idle (./slimserver.pl line 397) frame 6: main::main (./slimserver.pl line 869) 2004-10-08 21:39:01.0083 00:04:20:05:05:a4: Switching to mode stop from pause 2004-10-08 21:39:01.0092 00:04:20:05:05:a4 New play mode: stop 2004-10-08 21:39:01.0099 Stopping and clearing out old chunks for client 00:04:20:05:05:a4 2004-10-08 21:39:01.0117 00:04:20:05:05:a4: Current playmode: stop Try to make sure you have the patch for bug587. that might fix this too. if not, I'll keeep looking through the rest.
Comfirmed... patch for bug 587 appears to fix this as well.
cool. I'll mark this as a dupe of 587 then, since its a symptom of the same problem thanks for testing it. 587 shoudl be merged into the builds failry soon. *** This bug has been marked as a duplicate of 587 ***
Routine bug db maintenance; removing old versions which cause confusion. I apologize for the inconvenience.