Comment 29 for bug 130213
Revision history for this message
| rfurgy (rfurgy) wrote Re: rhtmbox doesn't play the next song after first song finished | #29 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Ok, I'm going to post a bug here and get it reopened.
Release: Ubuntu 9.10 Karmic Beta
Version: Rhythmbox 0.12.5
I've been using Rhythmbox quite a bit in the last two days and I can verify that the bug is still there somewhere.
I expect Rhythmbox to play the next song it moves to. It does play the next song a lot of the time, but not all the time. I'll just have it sitting in the background playing music while I'm searching the net or something like that. I have shuffle turned on so it will just keep going to another random song. I have cross fade turned off so I know it's not that.
What happens though is it will cycle through songs pretty well, but every so often it will get done playing a song (which are all MP3s and Oggs on a media partition I have set up) it then will even switch to the next song, but suspends play at 0:00 of the next song. Checking the progress bar and mouse over counter for the system tray icon both show the time standing still. By checking the very top bar, I can tell the song is not paused.
If I skip it forward to the next song, it will resume and play the next song. I can also resume play by manually selecting a different song or even using the previous song button. Also, if I wait long enough, Rhythmbox will eventually resume play on it's own. For and idea of how long it suspends for; as soon as it suspended, I reported the bug from the help menu inside Rhythmbox. I then proceeded to search for this bug and found it, came here and read down to about message #15 before it resumed play on it's own.
I do however have a Last FM account that is logged into when Rhythmbox is started. I even search through those bugs but they didn't seem relevant because I wasn't streaming from them for this to happen (although that doesn't mean that it isn't the problem). Not sure if this has anything to contribute to this problem, but I ended up with the biggest Compiz crash I've ever seen just a few hours ago.
P.S. Please bare with me, I'm a total noob at debugging and may need specific commands to help me through this. Going to see if I can manage to figure out how to debug (for the first time) for when this happens.