Version: (using KDE 4.1.96) OS: Linux Installed from: Ubuntu Packages Application: System Settings (systemsettings), signal SIGSEGV [Current thread is 0 (LWP 11093)] Thread 2 (Thread 0xb447bb90 (LWP 11140)): #0 0xb80c9430 in __kernel_vsyscall () #1 0xb6978df1 in select () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7597150 in ?? () from /usr/lib/libQtCore.so.4 #3 0xb74c76ae in ?? () from /usr/lib/libQtCore.so.4 #4 0xb65d850f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #5 0xb6980a0e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb61d46c0 (LWP 11093)): [KCrash Handler] #6 0xb703f43a in QProgressBar::minimum () from /usr/lib/libQtGui.so.4 #7 0xb75c753f in QObject::event () from /usr/lib/libQtCore.so.4 #8 0xb6c5a8ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #9 0xb6c6272e in QApplication::notify () from /usr/lib/libQtGui.so.4 #10 0xb7aecfed in KApplication::notify () from /usr/lib/libkdeui.so.5 #11 0xb75b7e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #12 0xb75e5d81 in ?? () from /usr/lib/libQtCore.so.4 #13 0xb75e2520 in ?? () from /usr/lib/libQtCore.so.4 #14 0xb650b6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #15 0xb650eda3 in ?? () from /usr/lib/libglib-2.0.so.0 #16 0xb650ef61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #17 0xb75e2478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #18 0xb6cf4ea5 in ?? () from /usr/lib/libQtGui.so.4 #19 0xb75b652a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #20 0xb75b66ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #21 0xb75b8da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #22 0xb6c5a767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #23 0x08056c5b in _start ()
Hi! Could you exactly explain how to reproduce the crash? Thanks!
Probably related to bug 178885
System settings > Appearance > Fonts Change all fonts to one size smaller than default value. click on Apply Close. Crash notification appears
Fortunatly I'm not able to reproduce here on current trunk.
*** This bug has been marked as a duplicate of bug 178885 ***