Amarok sometimes hangs during playback and has to be killed

Bug #93139 reported by Janne Hyötylä
6
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: amarok

Amarok sometimes hangs during playback (music stops playing, but systray icon still displays 'play' sign).

I am using 1.4.5-0ubuntu2~edgy1 from kubuntu.org repository on Edgy (Gnome) because of another bug, but the problem appeared also with 1.4.3-0ubuntu10 and all the other versions before since at least Dapper. I use the xine engine.

The behaviour changed a bit for 1.4.5 so I describe for both versions:

1.4.3:
Playback stops as described.
When hovering over the systray icon the tooltip about the current song appears normally and the current song time displayed after "Length:" does not change anymore.
When right-clicking on the icon, the menu gets displayed.
When clicking stop, most of the time the application hangs completely. Instead of the play sign a gray rectangle is displayed and I have to "killall amarokapp" after which I can start amarok again.
But sometimes, after clicking on "Stop" the application returns to normal stopped state and I can directly start playing another (or the same) song again.
There seems to be no pattern as to which behaviour will occur, although the complete hangup is more frequent.

1.4.5:
Same behaviour as 1.4.3 until I click on Stop in right-click menu.
Amarok returns to stopped mode and seems to work normally.
But when I want to play again Amarok hangs completely with the small gray rectangle instead of a play sign in systray icon.

This all seems completely random to me, seemingly not depending on the song playing or anything else. It occurs about every 5 hours on average, sometimes more often, sometimes less often. Sometimes it seems to me to occur more often when there is heavy network traffic (eg. Azureus running), but not sure.

If you need more info I'm happy to provide it. If you want me to do something when it hangs the next time, I can try that.

Revision history for this message
Janne Hyötylä (janne-hyotyla) wrote :

This does not happen anymore with Ubuntu 7.04
$amarok --version
Qt: 3.3.7
KDE: 3.5.6
Amarok: 1.4.5

(amarok package version: 2:1.4.5-0ubuntu7)

So I think this had possibly not much to du with amarok itself but other programs that were updated from Edgy to Feisty (ALSA, etc.?)

Revision history for this message
Tom Haddon (mthaddon) wrote :
Download full text (4.3 KiB)

I am still experiencing this issue on gutsy. I am running the gnome desktop, and after playing a number of songs without problem, amarok hangs.

Running strace gives the following output (abbreviated):

gettimeofday({1192576327, 196049}, NULL) = 0
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1192576327, 196085}, NULL) = 0
select(34, [3 4 5 8 10 12 16 24 26 30 33], [], [], {0, 108}) = 0 (Timeout)
gettimeofday({1192576327, 200065}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {79675, 764110304}) = 0
write(3, ">\3\7\0\301\6\300\4\300\6\300\4^\5\300\4\0\0\0\0\0\0\0"..., 16380) = 16380
gettimeofday({1192576327, 200508}, NULL) = 0
write(3, ">\3\7\0\335\1\300\4\300\6\300\4^\5\300\4\0\0\0\0h\1\20"..., 5180) = 5180
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1192576327, 200578}, NULL) = 0
select(34, [3 4 5 8 10 12 16 24 26 30 33], [], [], {0, 15615}) = 0 (Timeout)
gettimeofday({1192576327, 216118}, NULL) = 0
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1192576327, 216180}, NULL) = 0
select(34, [3 4 5 8 10 12 16 24 26 30 33], [], [], {0, 13}) = 0 (Timeout)
gettimeofday({1192576327, 220161}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {79675, 784216771}) = 0
write(3, ">\3\7\0\301\6\300\4\300\6\300\4^\5\300\4\0\0\0\0\0\0\0"..., 16380) = 16380
gettimeofday({1192576327, 220624}, NULL) = 0
write(3, ">\3\7\0\335\1\300\4\300\6\300\4^\5\300\4\0\0\0\0h\1\20"..., 5180) = 5180
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1192576327, 220699}, NULL) = 0
select(34, [3 4 5 8 10 12 16 24 26 30 33], [], [], {0, 1469}) = 0 (Timeout)
gettimeofday({1192576327, 224099}, NULL) = 0
gettimeofday({1192576327, 224160}, NULL) = 0
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1192576327, 224207}, NULL) = 0
select(34, [3 4 5 8 10 12 16 24 26 30 33], [], [], {0, 11986}) = 0 (Timeout)
gettimeofday({1192576327, 236965}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {79675, 801016164}) = 0
write(3, ">\3\7\0\301\6\300\4\300\6\300\4^\5\300\4\0\0\0\0\0\0\0"..., 16380) = 16380
gettimeofday({1192576327, 237409}, NULL) = 0
write(3, ">\3\7\0\335\1\300\4\300\6\300\4^\5\300\4\0\0\0\0h\1\20"..., 5180) = 5180
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1192576327, 237483}, NULL) = 0
select(34, [3 4 5 8 10 12 16 24 26 30 33], [], [], {0, 18710}) = 0 (Timeout)
gettimeofday({1192576327, 256246}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {79675, 820299285}) = 0
write(3, ">\3\7\0\301\6\300\4\300\6\300\4^\5\300\4\0\0\0\0\0\0\0"..., 16380) = 16380
gettimeofday({1192576327, 256697}, NULL) = 0
write(3, ">\3\7\0\335\1\300\4\300\6\300\4^\5\300\4\0\0\0\0h\1\20"..., 5180) = 5180
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1192576327, 256771}, NULL) = 0
select(34, [3 4 5 8 10 12 16 24 26 30 33], [], [], {0, 5397}) = 0 (Timeout)
gettimeofday({1192576327, 264075}, NULL) = 0
gettimeofday({1192576327, 264129}, NULL) = 0
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1192576327, 264173}, NULL) = 0
select(34, [3 4 5 8 10 12 16 24 26 30 33], [], [], {0, 12020}) = 0 (Timeout)
gettimeofday({1192576327, 280110}, NULL) = 0
clock_gettime(CLOCK_MONOTONIC, {79675, 844166549}) = 0
write(3, ">\3\7\0\301\6\300\4\300\6\300\4^\5\300\4\0\...

Read more...

Revision history for this message
Geoffrey (geoffrey-metais) wrote :

same issue on gutsy, since edgy.
On KDE desktop.
The 'freeze' is not related to the size of the playlist, it also happens with one single song.

Revision history for this message
Mario Young (mayeco) wrote :

Thank you for the bug report, BonBonTheJon. There is now a newer version of Amarok out, 1.4.7. Can you replicate this problem in the newer version?)

Revision history for this message
Mario Young (mayeco) wrote :

I'm Sorry!!!!!

Thank you for the bug report, Janne Hyötylä. There is now a newer version of Amarok out, 1.4.7. Can you replicate this problem in the newer version?)

Revision history for this message
Tom Haddon (mthaddon) wrote :

Newer version seems to have fixed it for me.

Revision history for this message
Harald Sitter (apachelogger) wrote :

Apparently this is fixed, if this should not be the case, please reopen this report.

Changed in amarok:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.