Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 156428 - XMMS remote play/pause command is broken
XMMS remote play/pause command is broken
Product: Fedora
Classification: Fedora
Component: xmms (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Paul F. Johnson
Depends On:
  Show dependency treegraph
Reported: 2005-04-29 20:10 EDT by Erich Hoover
Modified: 2008-08-02 19:40 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 20:09:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Erich Hoover 2005-04-29 20:10:43 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.7.7-2

Description of problem:
The remote execution command "play-pause" pauses correctly but cannot unpause after pausing.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start XMMS
2. Play a song
3. Pause the song from the command line (xmms --play-pause)
4. Unpause the song from the command line (xmms --play-pause)

Actual Results:  The song won't unpause, the song must be stopped and restarted to get anything to play again.

Expected Results:  The song should have continued playing.

Additional info:

If you pause/unpause four times this error is shown on the XMMS console (not the remote one):
** WARNING **: snd_pcm_pause() failed: File descriptor in bad state

Please note that this doesn't just hose the command-line operation, any other program that interacts with XMMS to play/pause is effected - the console operation is just an easy test case.
Comment 1 Paul F. Johnson 2007-01-02 19:10:09 EST
Can you test this with a newer version of xmms please and let me know if the
problem is still there?
Comment 2 Bug Zapper 2008-04-03 12:07:29 EDT
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
Comment 3 Bug Zapper 2008-05-06 20:09:37 EDT
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:

Note You need to log in before you can comment on or make changes to this bug.