Version: (using KDE KDE 3.2.0) Installed from: Compiled From Sources Compiler: GCC 3.3.1 Built from source, quite standard OS: Linux Backtrace: [New Thread 16384 (LWP 7746)] 0x41a131b7 in __libc_waitpid (pid=7747, stat_loc=0x0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:28 28 return INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL); #0 0x41a131b7 in __libc_waitpid (pid=7747, stat_loc=0x0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:28 #1 0x40d089cf in KCrash::defaultCrashHandler(int) () from /usr/local/kde/lib/libkdecore.so.4 #2 0x41a118e5 in __pthread_sighandler (signo=11, ctx= {gs = 7, __gsh = 0, fs = 0, __fsh = 0, es = 123, __esh = 0, ds = 123, __dsh = 0, edi = 137350480, esi = 3221222384, ebp = 3221222648, esp = 3221222336, ebx = 0, edx = 137465256, ecx = 0, eax = 3221222448, trapno = 14, err = 4, eip = 134745038, cs = 115, __csh = 0, eflags = 66178, esp_at_signal = 3221222336, ss = 123, __ssh = 0, fpstate = 0xbffff140, oldmask = 2147483648, cr2 = 0}) at sighandler.c:38 #3 <signal handler called> #4 0x08080bce in PlaylistSplitter::readPlaylists() () #5 0x0807f875 in PlaylistSplitter::readConfig() () #6 0x0807d10c in PlaylistSplitter::PlaylistSplitter(QWidget*, char const*) () #7 0x08092551 in JuK::setupLayout() () #8 0x08091667 in JuK::JuK(QWidget*, char const*) () #9 0x08097caa in main () I made this error by: Opening a directory of songs, generating a *.m3u playlist, then stopping and starting juk. Can't reproduce ... as I can't get juk to run again.
Well, just to get it to start again you can remove ~/.kde/share/apps/juk/* Could you give more detailed steps on what you did when this happened? Sadly there's not much useful information in the backtrace above.
Alright, I cleared out the ~./kde/share/apps/juk/* I then went and made a small playlist of ~ 12 songs. I can now close, open Juk or whatever I want to do. Sorry, I can't reproduce the error at all now. Juk is finding the old playlist I made of ~300 songs even now. So ..... yeah, now it's working perfectly! Again, sorry I can't reproduce this bug ... I'm sure you'd love to know what it was that was happening.
Ok, I'll mark this one as closed for the moment. If you're able to track it down a bit more at some point please reopen it with the relevant details.