Application: juk (3.5) KDE Platform Version: 4.4.85 (KDE 4.4.85 (KDE 4.5 Beta2)) Qt Version: 4.7.0 Operating System: Linux 2.6.32-22-generic x86_64 Distribution: Ubuntu 10.04 LTS -- Information about the crash: - What I was doing when the application crashed: Using VLC Phonon backend, Juk crashes when closed whilst a song is playing. I also get the same behaviour with Amarok too. Happens everytime, even when a song is not playing. The crash can be reproduced every time. -- Backtrace: Application: JuK (juk), signal: Segmentation fault [Current thread is 1 (Thread 0x7fcfae49f780 (LWP 23739))] Thread 3 (Thread 0x7fcf96cdd710 (LWP 23740)): #0 0xffffffffff60017b in ?? () #1 0x00007fcf96cdca70 in ?? () #2 0x00007fffc787c852 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 2 (Thread 0x7fcf5ef2b710 (LWP 23743)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x00007fcf95697f02 in ?? () from /usr/lib/libvlccore.so.5 #2 0x00007fcfa7e5f9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300 #3 0x00007fcfaa3386cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #4 0x0000000000000000 in ?? () Thread 1 (Thread 0x7fcfae49f780 (LWP 23739)): [KCrash Handler] #6 __pthread_mutex_lock (mutex=0x0) at pthread_mutex_lock.c:50 #7 0x00007fcfa92100b7 in XrmDestroyDatabase (db=0xa01190) at ../../src/Xrm.c:2642 #8 0x00007fcfa91fa95d in _XFreeDisplayStructure (dpy=0xa062a0) at ../../src/OpenDis.c:839 #9 0x00007fcfa91e5e7f in XCloseDisplay (dpy=0xa062a0) at ../../src/ClDisplay.c:82 #10 0x00007fcfac0b5635 in qt_cleanup () at kernel/qapplication_x11.cpp:2638 #11 0x00007fcfac0463a7 in ~QApplication (this=0x7fffc7820a90, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1110 #12 0x0000000000477e97 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../juk/main.cpp:94 This bug may be a duplicate of or related to bug 240001. Possible duplicates by query: bug 240001. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 240001 ***