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: I started the system (Chakra Linux) and I saw a notification that KRunner crashed. It repeats every time I start the system. The crash can be reproduced every time. -- Backtrace: Application: Run Command Interface (kdeinit4), signal: Aborted [Current thread is 1 (Thread 0x7f8f1e7d8780 (LWP 1864))] Thread 2 (Thread 0x7f8f03843700 (LWP 1865)): #0 0x00007f8f1be580bf in poll () from /lib/libc.so.6 #1 0x00007f8f190188b6 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x00007f8f190189e4 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x00007f8f1d458ef6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #4 0x00007f8f1d429b1f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #5 0x00007f8f1d429da8 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #6 0x00007f8f1d32d530 in QThread::exec() () from /usr/lib/libQtCore.so.4 #7 0x00007f8f1d40a6ef in ?? () from /usr/lib/libQtCore.so.4 #8 0x00007f8f1d33047b in ?? () from /usr/lib/libQtCore.so.4 #9 0x00007f8f1d09fede in start_thread () from /lib/libpthread.so.0 #10 0x00007f8f1be6060d in clone () from /lib/libc.so.6 Thread 1 (Thread 0x7f8f1e7d8780 (LWP 1864)): [KCrash Handler] #5 0x00007f8f1bdb0c35 in raise () from /lib/libc.so.6 #6 0x00007f8f1bdb20b8 in abort () from /lib/libc.so.6 #7 0x00007f8f1c17c9cd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #8 0x00007f8f1c17aad6 in ?? () from /usr/lib/libstdc++.so.6 #9 0x00007f8f1c17ab03 in std::terminate() () from /usr/lib/libstdc++.so.6 #10 0x00007f8f1c17ad76 in __cxa_rethrow () from /usr/lib/libstdc++.so.6 #11 0x00007f8f1d42a014 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #12 0x00007f8f1d42ea48 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #13 0x00007f8f09a4648f in kdemain () from /usr/lib/libkdeinit4_krunner.so #14 0x00000000004080b7 in _start () Possible duplicates by query: bug 301047, bug 301032, bug 301008, bug 301003, bug 300993. Reported using DrKonqi
Created attachment 71764 [details] New crash information added by DrKonqi krunner (0.1) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.2 - Unusual behavior I noticed: When I Login to my KDE4 Desktop this send me an error with kdeinit4 and crash the execute a command option -- Backtrace (Reduced): #11 0x00007fcd2cbdb014 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #12 0x00007fcd2cbdfa48 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #13 0x00007fcd1936748f in kdemain () from /usr/lib/libkdeinit4_krunner.so #14 0x00000000004080b7 in _start ()
Created attachment 71782 [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: Logged into the system. The crash occurs every time since I re-compiled KDE. (See below) - Custom settings of the application: I have rebuild my system using gcc-4.7.0 and upgrading to QT-4.8.2 because I need the newest gcc for my work. Everything works like a charm but this crash of krunner and a plasma desktop crash whenever I attach a second monitor after wakeup from suspend. Oh, Screen locking after waking up from suspend doesn't work either. -- Backtrace (Reduced): #6 0x00007f4eaa859cf5 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x00007f4eaa85b178 in __GI_abort () at abort.c:91 #8 0x00007f4eaac2d56d in __gnu_cxx::__verbose_terminate_handler () at /home/portage/sys-devel/gcc-4.7.0/work/gcc-4.7.0/libstdc++-v3/libsupc++/vterminate.cc:95 #9 0x00007f4eaac2b676 in __cxxabiv1::__terminate (handler=<optimized out>) at /home/portage/sys-devel/gcc-4.7.0/work/gcc-4.7.0/libstdc++-v3/libsupc++/eh_terminate.cc:40 #10 0x00007f4eaac2b6a3 in std::terminate () at /home/portage/sys-devel/gcc-4.7.0/work/gcc-4.7.0/libstdc++-v3/libsupc++/eh_terminate.cc:50
I just noticed, that when I open a konsole and enter krunner >/dev/null 2>&1 & krunner starts just fine and works normally as far as I have witnessed. It is just the first login when it crashes.
On Wed 13 Jun 2012 01:26:44 AM CST, Sven Eden wrote: > https://bugs.kde.org/show_bug.cgi?id=301096 > > --- Comment #3 from Sven Eden <sven.eden@gmx.de> --- > I just noticed, that when I open a konsole and enter > > krunner >/dev/null 2>&1 & > > krunner starts just fine and works normally as far as I have witnessed. It is > just the first login when it crashes. > Thanks Sven! I note that, run this command and work fine, thank you so much! -- ----------------------------- Alexander Morales Villatoro | Analista de Informatica | Resortes De Leon, S.A. | amorales@corpdl.com | -----------------------------
Created attachment 71935 [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: Logged into the system - Custom settings of the application: I have rebuilt my system after upgrading gcc to version 4.7.1. This had the effect that there is no longer a crash when I attach a second monitor or detach it again. But the crash after login remains. -- Backtrace (Reduced): #6 0x00007f7568073cf5 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x00007f7568075178 in __GI_abort () at abort.c:91 #8 0x00007f75684486fd in __gnu_cxx::__verbose_terminate_handler () at /home/portage/sys-devel/gcc-4.7.1/work/gcc-4.7.1/libstdc++-v3/libsupc++/vterminate.cc:95 #9 0x00007f7568446806 in __cxxabiv1::__terminate (handler=<optimized out>) at /home/portage/sys-devel/gcc-4.7.1/work/gcc-4.7.1/libstdc++-v3/libsupc++/eh_terminate.cc:40 #10 0x00007f7568446833 in std::terminate () at /home/portage/sys-devel/gcc-4.7.1/work/gcc-4.7.1/libstdc++-v3/libsupc++/eh_terminate.cc:50
*** This bug has been marked as a duplicate of bug 298131 ***