Bug 193553

Summary:	CP rebooted after command "find" had been started
Product:	[Applications] konsole	Reporter:	Evgeniy <evgenel>
Component:	general	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	robertknight
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Evgeniy 2009-05-21 21:05:36 UTC

Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    SuSE RPMs

Sorry for my English!)
And I have just started learning Linux.
I switched to commandline by pressing keys "Ctr+Alt+f2", after I wanted switch to graphical interface, but I hadn't known how to do it. So I entered command "find" without any parametrs, than system started searching in all derictories. It was searching too much time, so I pressed some keys, but nothing worked. My PC had rebooted during the searching. When Linux loaded I saw message that the fatal error has occured.

Error's report:

Приложение: Служба KDE (kded4), сигнал SIGSEGV
[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xaf2c5d3c in ?? ()
#7  0xb72db6fa in ?? () from /usr/lib/libQtDBus.so.4
#8  0xb72db93a in ?? () from /usr/lib/libQtDBus.so.4
#9  0xb748c281 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#10 0xb6aa78fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
   from /usr/lib/libQtGui.so.4
#11 0xb6aaf75e in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libQtGui.so.4
#12 0xb7bf941d in KApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libkdeui.so.5
#13 0xb747c961 in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
   from /usr/lib/libQtCore.so.4
#14 0xb747d5d5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#15 0xb747d7cd in QCoreApplication::sendPostedEvents(QObject*, int) ()
   from /usr/lib/libQtCore.so.4
#16 0xb74a736f in ?? () from /usr/lib/libQtCore.so.4
#17 0xb63c49a8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#18 0xb63c8063 in ?? () from /usr/lib/libglib-2.0.so.0
#19 0xb63c8221 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#20 0xb74a6fb8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#21 0xb6b40785 in ?? () from /usr/lib/libQtGui.so.4
#22 0xb747b01a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#23 0xb747b1da in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/libQtCore.so.4
#24 0xb747d895 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#25 0xb6aa7777 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#26 0xb80289a6 in kdemain () from /usr/lib/libkdeinit4_kded4.so
#27 0x080487c2 in _start ()

Comment 1 Robert Knight 2009-05-21 21:29:39 UTC

Hello Evgeniy,

A few clarifications:

1.  You can stop a command which is running in the terminal by pressing Ctrl+C, or Ctrl+D for a command which is waiting for your input.  Some programs like 'man' exit when you press the 'q' key.

2.  The 'find' command just lists every file in every directory.  If you add options to it then only certain file names are printed (eg. those containing certain text).

3.  The error report you are seeing does not relate to the Konsole program but one of the background services which crashed.  It is a good idea to report these crashes although they are not usually a serious problem and you can carry on using the desktop.