Application: krunner (0.1) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.2 Operating System: Linux 3.2-CHAKRA x86_64 Distribution: "Chakra Linux" -- Information about the crash: - What I was doing when the application crashed: Succede sempre quando accende il notebook, da quando ho fatto l'ultimo aggiornamento. The crash can be reproduced every time. -- Backtrace: Application: Interfaccia al comando di esecuzione (kdeinit4), signal: Aborted [Current thread is 1 (Thread 0x7fd2cf0b1780 (LWP 2023))] Thread 2 (Thread 0x7fd2b4a76700 (LWP 2024)): #0 0x00007fd2c99305d0 in ?? () from /usr/lib/libglib-2.0.so.0 #1 0x00007fd2c9930829 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0 #2 0x00007fd2c98f59d0 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x00007fd2cdd34ef6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #4 0x00007fd2cdd05b1f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #5 0x00007fd2cdd05da8 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #6 0x00007fd2cdc09530 in QThread::exec() () from /usr/lib/libQtCore.so.4 #7 0x00007fd2cdce66ef in ?? () from /usr/lib/libQtCore.so.4 #8 0x00007fd2cdc0c47b in ?? () from /usr/lib/libQtCore.so.4 #9 0x00007fd2cd97bede in start_thread () from /lib/libpthread.so.0 #10 0x00007fd2cc73d60d in clone () from /lib/libc.so.6 Thread 1 (Thread 0x7fd2cf0b1780 (LWP 2023)): [KCrash Handler] #5 0x00007fd2cc68dc35 in raise () from /lib/libc.so.6 #6 0x00007fd2cc68f0b8 in abort () from /lib/libc.so.6 #7 0x00007fd2cca58bbd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #8 0x00007fd2cca56cc6 in ?? () from /usr/lib/libstdc++.so.6 #9 0x00007fd2cca56cf3 in std::terminate() () from /usr/lib/libstdc++.so.6 #10 0x00007fd2cca56f66 in __cxa_rethrow () from /usr/lib/libstdc++.so.6 #11 0x00007fd2cdd06014 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #12 0x00007fd2cdd0aa48 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #13 0x00007fd2baef448f in kdemain () from /usr/lib/libkdeinit4_krunner.so #14 0x00000000004080b7 in _start () Possible duplicates by query: bug 300993, bug 300921, bug 300851, bug 300796, bug 300718. Reported using DrKonqi
English, please! Also you don't have debugging symbols installed for kde-workspace, please install those and provide a better backtrace.
Created attachment 71625 [details] New crash information added by DrKonqi krunner (0.1) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.2 - What I was doing when the application crashed: I was logging into my user account. The problem arose for the first time two days ago when I changed the theme of the plasma, and since then he has every reboot after the login. -- Backtrace (Reduced): #11 0x00007f4e7e9d3014 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #12 0x00007f4e7e9d7a48 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #13 0x00007f4e6b11f48f in kdemain () from /usr/lib/libkdeinit4_krunner.so #14 0x00000000004080b7 in _start ()
Chiara, please install the debugging symbols for kde-workspace and provide a better backtrace.
Created attachment 71634 [details] New crash information added by DrKonqi krunner (0.1) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.2 - What I was doing when the application crashed: I was logging into my user account. The problem showed up for the first time two days ago when I changed the plasma theme, and since then it occurred at every reboot after login. -- Backtrace (Reduced): #11 0x00007fb81bdf5014 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #12 0x00007fb81bdf9a48 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #13 0x00007fb80854148f in kdemain (argc=1, argv=0x677770) at /chakra/desktop-testing/kde-workspace/src/kde-workspace-4.8.3/krunner/main.cpp:66 #14 0x00000000004080b7 in _start ()
Thank you for the fast feedback. This is now fixed for KDE 4.8.4. *** This bug has been marked as a duplicate of bug 298131 ***