Amarok (amarok-2.8.90-8.fc25.x86_64) got stuck, I attach gdb trace gdb output [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 135 2: movl %edx, %eax (gdb) bt #0 0x00007f4112c5b38d in __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x00007f4112c54eca in __GI___pthread_mutex_lock (mutex=0x559e5994aa50) at ../nptl/pthread_mutex_lock.c:115 #2 0x00007f410d7a6254 in FAMPending (fc=fc@entry=0x559e59915bf0) at gam_api.c:1340 #3 0x00007f4115f79c08 in KDirWatchPrivate::famEventReceived() (this=0x559e59915b60) at /usr/src/debug/kdelibs-4.14.26/kdecore/io/kdirwatch.cpp:1525 #4 0x00007f4114de0090 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x559e5994aa80, m=m@entry=0x7f411512fcc0 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffca47f3f40) at kernel/qobject.cpp:3567 #5 0x00007f4114e3123e in QSocketNotifier::activated(int) (this=this@entry=0x559e5994aa80, _t1=<optimized out>) at .moc/release-shared/moc_qsocketnotifier.cpp:102 #6 0x00007f4114dea7ab in QSocketNotifier::event(QEvent*) (this=0x559e5994aa80, e=0x7ffca47f4220) at kernel/qsocketnotifier.cpp:316 #7 0x00007f4115329ecc in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x559e59259210, receiver=receiver@entry=0x559e5994aa80, e=e@entry=0x7ffca47f4220) at kernel/qapplication.cpp:4565 #8 0x00007f4115330dcc in QApplication::notify(QObject*, QEvent*) (this=this@entry=0x7ffca47f45c0, receiver=receiver@entry=0x559e5994aa80, e=e@entry=0x7ffca47f4220) at kernel/qapplication.cpp:4351 #9 0x00007f4116594c8a in KApplication::notify(QObject*, QEvent*) (this=0x7ffca47f45c0, receiver=0x559e5994aa80, event=0x7ffca47f4220) at /usr/src/debug/kdelibs-4.14.26/kdeui/kernel/kapplication.cpp:311 #10 0x00007f4114dcbeed in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7ffca47f45c0, receiver=0x559e5994aa80, event=event@entry=0x7ffca47f4220) at kernel/qcoreapplication.cpp:955 #11 0x00007f4114dfca42 in QCoreApplication::sendEvent(QObject*, QEvent*) (event=0x7ffca47f4220, receiver=<optimized out>) at kernel/qcoreapplication.h:231 #12 0x00007f4114dfca42 in socketNotifierSourceDispatch(GSource*, GSourceFunc, gpointer) (source=0x559e59202f10) at kernel/qeventdispatcher_glib.cpp:117 #13 0x00007f410d2d7e42 in g_main_dispatch (context=0x559e592595b0) at gmain.c:3203 #14 0x00007f410d2d7e42 in g_main_context_dispatch (context=context@entry=0x559e592595b0) at gmain.c:3856 #15 0x00007f410d2d81c0 in g_main_context_iterate (context=context@entry=0x559e592595b0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3929 #16 0x00007f410d2d826c in g_main_context_iteration (context=0x559e592595b0, may_block=may_block@entry=1) at gmain.c:3990 ---Type <return> to continue, or q <return> to quit--- #17 0x00007f4114dfc45e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x559e5914a8f0, flags=...) at kernel/qeventdispatcher_glib.cpp:450 #18 0x00007f41153d25a6 in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207 #19 0x00007f4114dca7bf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffca47f4470, flags=...) at kernel/qeventloop.cpp:149 #20 0x00007f4114dcab25 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffca47f4470, flags=...) at kernel/qeventloop.cpp:204 #21 0x00007f4114dd0779 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1227 #22 0x0000559e58aa8e45 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/amarok-2.8.90/src/main.cpp:329
What do you mean got stuck, can you give some help on how to reproduce this? The gdb output doesn't show any problems in Amarok itself, more like a FAM lockup, that would be system depending.
I mean that the window of the application was completely freezed. I have no way to reproduce the bug
Ah it must be gam_server, I have completely forgotten it. When Amarok freezes, I kill gam_server process and it resumes its normal behaviour
I guessed as much, that is not an Amarok problem, you should report this to your distribution, they need to tweak that on their side. the GAMIN problem has been reported on various occasions, but there is really not much we can do here. See also bug #281312
For anybody who will find this bugreport while doing searches: check gamin upstream bugreport https://bugzilla.gnome.org/show_bug.cgi?id=777997