On Thu, Feb 19, 2009 at 9:34 PM, Kevin Kofler wrote: > Orcan Ogetbil wrote: >> I get a crash pop-up window whenever I close a KDE3 application. > > Weird, I don't see this on any of my machines, and I still run several KDE 3 > applications. > > Can we get a backtrace? > Sure. Here is some kaffeine crash-on-exit. I believe I have all the necessary debuginfo packages installed. Still the popup window says: -------------------------------------------> Unable to create a valid backtrace. <------------------------------------------- and it gives me this "invalid" backtrace: -------------------------------------------> This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. [Thread debugging using libthread_db enabled] [New Thread 0x7ffff7fb5750 (LWP 6496)] 0x0000003dd3aa7f81 in nanosleep () from /lib64/libc.so.6 Current language: auto; currently c [Current thread is 1 (Thread 0x7ffff7fb5750 (LWP 6496))] Thread 1 (Thread 0x7ffff7fb5750 (LWP 6496)): #0 0x0000003dd3aa7f81 in nanosleep () from /lib64/libc.so.6 #1 0x0000003dd3aa7da7 in __sleep (seconds=<value optimized out>) at ../sysdeps/unix/sysv/linux/sleep.c:138 #2 0x00000030b831117d in KCrash::startDrKonqi (argv=0x7fffffffd3b0, argc=9) at kcrash.cpp:312 #3 0x00000030b831736f in KCrash::defaultCrashHandler (sig=11) at kcrash.cpp:229 #4 <signal handler called> #5 0x0000003dd4e1257d in ?? () from /lib64/libselinux.so.1 #6 0x0000003dd4e04fef in selinux_file_context_cmp () from /lib64/libselinux.so.1 #7 0x0000000000000000 in ?? () <------------------------------------------- Here is a k3b crash-on-exit: -------------------------------------------> This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. [Thread debugging using libthread_db enabled] [New Thread 0x7f99959d3750 (LWP 16554)] 0x0000003dd3aa7f81 in nanosleep () from /lib64/libc.so.6 Current language: auto; currently c [Current thread is 1 (Thread 0x7f99959d3750 (LWP 16554))] Thread 1 (Thread 0x7f99959d3750 (LWP 16554)): #0 0x0000003dd3aa7f81 in nanosleep () from /lib64/libc.so.6 #1 0x0000003dd3aa7da7 in __sleep (seconds=<value optimized out>) at ../sysdeps/unix/sysv/linux/sleep.c:138 #2 0x00000030b831117d in KCrash::startDrKonqi (argv=0x7fff9da18f40, argc=9) at kcrash.cpp:312 #3 0x00000030b831736f in KCrash::defaultCrashHandler (sig=11) at kcrash.cpp:229 #4 <signal handler called> #5 0x0000003dd4e1257d in ?? () from /lib64/libselinux.so.1 #6 0x0000003dd4e04fef in selinux_file_context_cmp () from /lib64/libselinux.so.1 #7 0x0000000000000000 in ?? () <------------------------------------------- What else do I need other than what debuginfo-install k3b kaffeine installs? >> kuickshow is gone among other nice things. > > Replaced by Gwenview. Kuickshow was 1. unmaintained and 2. using the > obsolete imlib 1 which requires other obsolete libraries (it dragged in > GTK+ 1 of all things!). And Gwenview is really the better app. > Unmaintained doesn't necessarily mean bad. If something is fully functional then it can go unmaintained for years. gwenview is not light enough. Meanwhile, I have nothing against GTK+ 1. The best audio application still uses GTK+, and that, I think, is a sufficient proof that GTK+ is better than GTK2+. I also started thinking that all we need to swallow is that Qt3 is better than Qt4. It is a hard bite. But once we digest it, life will get easier. >> kfontview never works. > > Does: > kfontview /usr/share/fonts/dejavu/DejaVuSans.ttf > work? If even that is broken, are you per chance using the proprietary > nvidia driver with "font acceleration" enabled? If so, disable font > acceleration. There are reports of it breaking font display in some places > of KDE (yet another bug in that crappy driver). > If by "font acceleration" you mean "Anti-aliasing", turning it off doesn't do any good. kfontview still shows a blank window. If by "font acceleration" you mean something else, can you be a little more specific? Yes, nvidia sucks by not open sourcing their driver. But I do not have another choice. I'm not a close minded person. I analyze possible choices and pick the best available one. For instance, when I realized that I had a choice, I switched to Linux. > Kevin Kofler > Cheers, Orcan
