https://bugs.kde.org/show_bug.cgi?id=492629
--- Comment #3 from Tuomas Nurmi <tuo...@norsumanageri.org> --- (In reply to Eddie from comment #2) > Created attachment 173513 [details] > gbd debug > > Ok ran gbd amarok run | output is > Thread 1 "amarok" received signal SIGSEGV, Segmentation fault. > ___pthread_mutex_lock (mutex=mutex@entry=0x28) at pthread_mutex_lock.c:80 > 80 unsigned int type = PTHREAD_MUTEX_TYPE_ELISION (mutex); Great, thank you! Interesting, so this is apparently not quite the same issue as the other one. Could you also try getting a gdb backtrace by running gdb amarok run backtrace and pasting the out here, please? -- You are receiving this mail because: You are watching all bug changes.
