Bug 910973 - after pause of CD track, unable to start play again
Summary: after pause of CD track, unable to start play again
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 17
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-14 04:38 UTC by Stuart D Gathman
Modified: 2013-07-31 21:29 UTC (History)
4 users (show)

Fixed In Version:
Clone Of: 757530
Environment:
Last Closed: 2013-07-31 21:29:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Stuart D Gathman 2013-02-14 04:38:10 UTC
+++ This bug was initially created as a clone of Bug #757530 +++

Description of problem:
After starting the play of a CD track and then pausing, it is not
possible to resume playing without ejecting and reloading the CD.

Version-Release number of selected component (if applicable):
rhythmbox-2.90.1-17.git20110927.fc16.x86_64

How reproducible:
always

Steps to Reproduce:
1. insert CD, select Rhythmbox for play
2. start play of CD
3. press the Play button to pause track
  
Actual results:
unable to continue playing CD

Expected results:
able to continue playing CD

Additional info:

--- Additional comment from Stuart D Gathman on 2012-01-02 18:16:39 EST ---

Workaround after pausing: 
 1. mentally note track and position 
 2. exit rhythmbox
 3. start rhythmbox again
 4. select CD, select tract, 
 5. press play, slide position pointer

--- Additional comment from Stuart D Gathman on 2012-11-18 09:27:53 EST ---

This is still broken in Fedora 17.  Please bump version instead of closing at F16 EOL.  

Another workaround: eject CD.  Reload CD.  Position to mentally noted track and position.  This somehow seems easier than exiting and reloading rhythmbox.

--- Additional comment from Stuart D Gathman on 2012-11-18 09:33:40 EST ---

I think this is a rhythmbox problem, not gstreamer, because totem works ok.

Comment 1 Fred New 2013-03-21 06:49:45 UTC
I can confirm that this problem exists in both 32-bit and 64-bit Fedora 18, currently rhythmbox-2.98-4.fc18.

Comment 2 Fred New 2013-03-21 06:59:55 UTC
I just noticed that rhythmbox is a Gnome package.  Perhaps it is having problems interfacing with LXDE on both of my systems.

Comment 3 Fedora End Of Life 2013-07-03 20:55:00 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.

Comment 4 Fedora End Of Life 2013-07-31 21:29:27 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.


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