Amarok hangs when holding down of next/previous track hotkey

Bug #55585 reported by RobertWiblin
26
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: amarok

Using Amarok 1.3.8 on Ubuntu 6.06 on a Dell Inspiron 6000. Xine engine with oss.

Using Settings, Configure Global Shortcuts, I have set the Next Track and Previous Track functions to be the appropriate keys on the front of my Inspiron laptop (FX86AudioNext, FX86AudioPrev). These work appropriately. However, if you ever hold down the key for more than about a third of a second it will keep on scrolling through the list and playing the first second of each song indefinitely until another hotkey is used to stop it. The program does not respond normally to the mouse.

This is particularly bad when the dynamic playlist is activated, as the playlist never ends and the only way to bring Amarok back to life is to kill it with cntl-alt-delete and start it again.

I hope this bug is fixable. Please report similar experiences with other laptops/keyboards.

Changed in amarok:
status: Unconfirmed → Confirmed
Revision history for this message
Vassilis Pandis (pandisv) wrote :

Please do not confirm your own bugs. What you describe is not a crash, it's a hang.

Changed in amarok:
status: Confirmed → Unconfirmed
Revision history for this message
Jonathan Jesse (jjesse) wrote :

Are you currently on the latest version of Amarok? If not can you make sure you are updated to the new version? Do you have the ability to test this in Edgy?

More information would be great to help out w/ this bug.

Thanks,
Jonathan

Revision history for this message
RobertWiblin (robertwiblin) wrote : Re: [Bug 55585] Re: Amarok hangs when holding down of next/previous track hotkey

Cheers Jonathon,
I have now updated to 1.4. Next time I boot into Ubuntu I will check
this out again.
Thanks,

On 9/19/06, Jonathan Jesse <email address hidden> wrote:
> Are you currently on the latest version of Amarok? If not can you make
> sure you are updated to the new version? Do you have the ability to
> test this in Edgy?
>
> More information would be great to help out w/ this bug.
>
> Thanks,
> Jonathan
>
> --
> Amarok hangs when holding down of next/previous track hotkey
> https://launchpad.net/bugs/55585
>

--
Robert Wiblin
ANUSA Environment Officer
<email address hidden>
Ph: 0401242877
Burgmann College, ANU

Revision history for this message
RobertWiblin (robertwiblin) wrote :

Issue still occuring under 1.4.0 .

Revision history for this message
Andrew Ash (ash211) wrote :

I know we just asked for testing under a newer version, but could you try an even newer version? I think Amarok is up to 1.4.3 now. How about Edgy Beta?

Do you have similar problems with other hotkeys too? Hopefully this information will help get the bug solved.

Revision history for this message
Brandon Holtsclaw (imbrandon) wrote :

1.4.3 is also avaible in dapper-backports is you would like to test on dapper instead

Revision history for this message
el33tcapitan (danmoogle) wrote :

This also happens to me, I have a Dell Inspiron as well. I run 1.4.4 in Edgy

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

I can confirm this too.

Latest edgy, latest amarok. Havent got a feisty installation yet though.

Changed in amarok:
status: Unconfirmed → Confirmed
Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

oh, dell 6400 here :)

Revision history for this message
Andrew Ash (ash211) wrote :

Hey Sarah

I know you've surely got a Feisty installation by now :D Can you confirm this still?

Revision history for this message
RobertWiblin (robertwiblin) wrote :

I can't get Amarok 1.4 under Ubuntu Feisty to even use the Inspiron 6000 forward/backward hotkeys. I guess probably solved in an odd way :-D.

Can anyone else confirm this? I think Ubuntu is stealing them and won't let them go.

Revision history for this message
Kieran Hogg (xerosis) wrote :

Still affects 1.4.5 in gutsy.

Revision history for this message
Kieran Hogg (xerosis) wrote :

I can't seem to reproduce this anymore in 1.4.6. It skips a few times, more than it should I think, but then it stops itself. Anyone confirm?

Revision history for this message
Josh (hashbrowncipher) wrote :

I'm running hardy (snigger all you like), and I continue having this bug (had it with gutsy). I'll provide any additional information pertinent, just ask.

Revision history for this message
Dan Keshet (dkesh) wrote :

I'm on Kubuntu/Gutsy with a Feisty kernel, Inspiron 1521. I don't notice the exact same behavior, but sometimes my keyboard locks up completely. ctrl-alt-delete does nothing, nor caps lock, nor any key, nor keys typed in with the mouse using kvkbd. Unloading and reloading the i8042 module doesn't bring the keyboard back. The only way I can get new text to appear in any application is by copying and pasting characters already shown on the screen. The keyboard comes back completely after killing amarok.

Revision history for this message
Eric DT (ericdt) wrote :

"I don't notice the exact same behavior, but sometimes my keyboard locks up completely. ctrl-alt-delete does nothing, nor caps lock, nor any key, nor keys typed in with the mouse using kvkbd."

I too exerienced these kind of lock. I get this about once a week using Amarok every days.

======== DEBUG INFORMATION =======
Version: 1.4.8
Engine: xine-engine
Build date: Dec 20 2007
CC version: 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)
KDElibs: 3.5.8
Qt: 3.3.7
TagLib: 1.4.0
CPU count: 2
NDEBUG: true

Changed in amarok:
importance: Undecided → Medium
Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 alpha?

Changed in amarok:
status: Confirmed → Incomplete
Revision history for this message
Myriam Schweingruber (myriam) wrote :

I don't think so, as Intrepid uses Amarok 1.4.10.1 and I can't reproduce this bug.
Also, Amarok 1.4.x is not maintained anymore upstream, as Amarok 2 is already in beta 2 and available for Intrepid.
This bug should be closed.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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