After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 335774 - Incorrect "Last track" and "Next track" button state
Incorrect "Last track" and "Next track" button state
Status: RESOLVED DUPLICATE of bug 335490
Product: rhythmbox
Classification: Other
Component: User Interface
0.9.3
Other All
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-24 01:02 UTC by Tamim
Modified: 2006-03-24 08:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tamim 2006-03-24 01:02:34 UTC
Please describe the problem:
When an artist is double clicked in browser view, the "last track" and "next
track" buttons remain inactive not allowing one to skip to next track without
explicitly clicking on the next track in the track list.

Steps to reproduce:
1. start rhythmbox and click on the "loop"(the 4th one from left) button and
close rhythmbox
2. start rhythmbox
3. double click on an artist in browser view to play "all albums"
4. click on "loop" button to turn looping off and then turn looping on again.

Actual results:
After step 3, the "last track" and "next track" buttons remain frozen or
inactive. But when the loop button is clicked off and on again, the "last track"
and "next track" buttons have the right state.

Expected results:
When starting rhythmbox, last track and next track buttons should be active or
at least be active when an artist is double clicked.

Does this happen every time?
Yes

Other information:
No
Comment 1 Alex Lancaster 2006-03-24 08:34:43 UTC
I can duplicate that this here.   Sounds like a special case of bug #335490.  Can you check that patch on CVS HEAD and see if it fixes it for you?
Comment 2 Alex Lancaster 2006-03-24 08:40:36 UTC
The patch on that bug fixes this bug for me, closing as a dupe.

*** This bug has been marked as a duplicate of 335490 ***