When I open Amarok and hit play, it plays the first music ok, but then the interface starts hanging in a way I can't open it again nor select any of the system tray icon options. After the first song finishes playing, it doesn't continue playing any other songs from the playlist and I have to kill the process. I've been noticing this problem since I did the update to Fedora 17. I also noticed the same problem while trying to update the playlist. It's worth saying that my Amarok reads music from a NTFS partition, mounted upon start via fstab. Also worth saying that, when I run it with --debug flag, it sometimes will not hang, working as I expected. Reproducible: Sometimes Steps to Reproduce: 1. Open Amarok 2. Hit play 3. Close the application, leaving it only in tray bar, then try to invoke the graphical interface after some seconds Actual Results: The graphical interface doesn't show up and after the song finishes playing, Amarok doesn't continue playing the playlist (as expected) Expected Results: It should have opened the window and/or the system tray menu. It's running over Fedora 17 and KDE 4.8.5.
Created attachment 73606 [details] Debug output from the last song it played onwards. Debug output, beginning with the last song correctly played by Amarok and listing until crash happened.
Could you please provide the backtrace when this crash happens? See also techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
I'm having some trouble reproducing a situation where I can get the stack trace, since I can always reproduce the bug when not running with --debug, but not always it will crash.
Created attachment 73778 [details] Backtrace of SIGSEGV kill. As I could not reproduce the segmentation fault crash, I killed the process with SIGSEGV while Amarok UI was hanging. Not sure if this will be of any use, though.
Backtrace from comment #4. Please always paste backtraces in the comment field directly, else it is not searchable. The problem is in kdelibs Thread 1 (Thread 0x7f196ecb9880 (LWP 3751)): [KCrash Handler] #6 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:134 #7 0x0000003e38009c71 in _L_lock_889 () from /lib64/libpthread.so.0 #8 0x0000003e38009b8a in __pthread_mutex_lock (mutex=0x2a0f120) at pthread_mutex_lock.c:86 #9 0x0000003e44803526 in FAMPending (fc=0x44dc870) at gam_api.c:1340 #10 0x0000003c2c717970 in KDirWatchPrivate::famEventReceived (this=0x44dc7e0) at /usr/src/debug/kdelibs-4.8.5/kdecore/io/kdirwatch.cpp:1509 #11 0x0000003c2b98cb9f in QMetaObject::activate (sender=0x30136e0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffa33e77d0) at kernel/qobject.cpp:3547 #12 0x0000003c2b9d5f9e in QSocketNotifier::activated (this=<optimized out>, _t1=56) at .moc/release-shared/moc_qsocketnotifier.cpp:102 #13 0x0000003c2b9930ab in QSocketNotifier::event (this=0x30136e0, e=0x7fffa33e7df0) at kernel/qsocketnotifier.cpp:317 #14 0x0000003c2d5ca37c in QApplicationPrivate::notify_helper (this=this@entry=0x2313270, receiver=receiver@entry=0x30136e0, e=e@entry=0x7fffa33e7df0) at kernel/qapplication.cpp:4551 #15 0x0000003c2d5ce7fa in QApplication::notify (this=0x7fffa33ea370, receiver=0x30136e0, e=0x7fffa33e7df0) at kernel/qapplication.cpp:4412 #16 0x0000003c2e8462b6 in KApplication::notify (this=0x7fffa33ea370, receiver=0x30136e0, event=0x7fffa33e7df0) at /usr/src/debug/kdelibs-4.8.5/kdeui/kernel/kapplication.cpp:311 #17 0x0000003c2b9763ee in QCoreApplication::notifyInternal (this=0x7fffa33ea370, receiver=0x30136e0, event=0x7fffa33e7df0) at kernel/qcoreapplication.cpp:915 #18 0x0000003c2b9a3cf8 in sendEvent (event=0x7fffa33e7df0, receiver=<optimized out>) at kernel/qcoreapplication.h:231 #19 socketNotifierSourceDispatch (source=source@entry=0x2313470) at kernel/qeventdispatcher_glib.cpp:110 #20 0x0000003e39c47695 in g_main_dispatch (context=0x2314000) at gmain.c:2539 #21 g_main_context_dispatch (context=context@entry=0x2314000) at gmain.c:3075 #22 0x0000003e39c479c8 in g_main_context_iterate (context=context@entry=0x2314000, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3146 #23 0x0000003e39c47a84 in g_main_context_iteration (context=0x2314000, may_block=1) at gmain.c:3207 #24 0x0000003c2b9a44e6 in QEventDispatcherGlib::processEvents (this=0x21b1c60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #25 0x0000003c2d66a2ee in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207 #26 0x0000003c2b97513f in QEventLoop::processEvents (this=this@entry=0x7fffa33e8030, flags=...) at kernel/qeventloop.cpp:149 #27 0x0000003c2b9753c8 in QEventLoop::exec (this=0x7fffa33e8030, flags=...) at kernel/qeventloop.cpp:204 #28 0x0000003c2b97a1b8 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187 #29 0x0000000000408dea in main (argc=2, argv=0x7fffa33ea4d8) at /usr/src/debug/amarok-2.6.0/src/main.cpp:306 *** This bug has been marked as a duplicate of bug 281312 ***