Bug 156094 - Disconnection of a NFS mount causes amarok and keyboard to freeze
Summary: Disconnection of a NFS mount causes amarok and keyboard to freeze
Status: RESOLVED DUPLICATE of bug 137288
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.4.8
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-18 12:39 UTC by Milko Krachounov
Modified: 2009-05-21 17:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Milko Krachounov 2008-01-18 12:39:03 UTC
Version:           1.4.8 (using KDE 3.5.7)
Installed from:    Gentoo Packages
Compiler:          gcc 4.1.2 
OS:                Linux

Half of my collection is residing on a NFS mount. Every time the NFS gets lagged or disconnected, amarok freezes (it continues to play, though) until the NFS comes back, that's even if I'm playing songs from my local hard disk. In addition, it sometimes causes my keyboard to get completely frozen, so I'm not able to kill amarok either. One of the things that leads to my keyboard freezing is pressing XF86Pause to pause the current playing song just after pulling my network cable off. This reproduces the freezing of the keyboard each time. It comes back after I pull the cable back in.

I currently workaround this by Alt+SysRq+R, Ctrl+Alt+F1 and killall -9 amarokapp from the console. As I mounted my NFS shares with intr option, killall -SIGINTR amarokapp should have helped in theory, but I didn't try to do so.
Comment 1 Milko Krachounov 2008-01-18 12:42:27 UTC
Just to be precise, XF86Pause is the key I used in my bindings to pause amarok. Also, neither I press it immediately after I unplug the cable (I wait some time), nor the keyboard and amarok unfreeze instantly on cable plugging.
Comment 2 Michael Jansen 2009-05-21 17:14:39 UTC

*** This bug has been marked as a duplicate of bug 13728 ***
Comment 3 Michael Jansen 2009-05-21 17:15:20 UTC
Sorry . Typo

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