Bug 236381
| Summary: | xmms playback disrupted when restoring from sleep | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Christopher Beland <beland> |
| Component: | xmms | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7 | CC: | chris.brown, triage |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-06-17 01:17:49 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Christopher Beland
2007-04-13 15:01:17 UTC
(The original report was with Fedora Core 6.) kernel-2.6.22.4-65.fc7 xmms-1.2.10-36.fc7 alsa-lib-1.0.14-3.fc7 alsa-utils-1.0.14-1.fc7 The behavior has changed with Fedora 7. xmms no longer "plays" the remainder of the file in a few seconds. The progress bar is stopped at the place where playback was when the sleep cycle was initiated. However, hitting "play" restarts playback from the beginning of the file, not the place where it was stopped. Though this could be an artifact of high load triggering Bug 196583. Hello, I'm reviewing this bug as part of the kernel bug triage project. http://fedoraproject.org/wiki/KernelBugTriage As xmms is no longer actively maintained, I would be interested to learn if you experience the same issue with audacious, the apparent successor to xmms. This is just curiosity - I'm not recommending you to switch apps. Also it might help narrow things down a bit. Cheers Chris I do *not* see the same behavior with Audacious. I'm totally switching over; thanks for the pointer! :) Great news Christopher. I'm re-assigning to xmms though there really doesn't seem much hope of this being fixed. Cheers Chris This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists. Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs: http://docs.fedoraproject.org/release-notes/ The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. Fedora 7 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |