Bug 186448 - The application Konsole (konsole) crashed and caused the signal 11 (SIGSEGV).
Summary: The application Konsole (konsole) crashed and caused the signal 11 (SIGSEGV).
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-03-07 15:00 UTC by Walter Green
Modified: 2018-10-21 05:02 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Walter Green 2009-03-07 15:00:37 UTC
Version:           konsole 4.2.00 (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

konsole starts when I restart linux and had previously been running it before shutdown. I have to kill it because the bash script that was running inside the konsole does not start. After killing the konsole using the 'x' in the corner of the window I receive the following error:

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.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5fe46c0 (LWP 6716)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7f91430 in __kernel_vsyscall ()
[Current thread is 0 (process 6716)]

Thread 1 (Thread 0xb5fe46c0 (LWP 6716)):
#0  0xb7f91430 in __kernel_vsyscall ()
#1  0xb660af10 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb660ad4e in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7972d72 in ?? () from /usr/lib/libkdeui.so.5
#4  0xb7973734 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0xb7f1de2d in ?? () from /usr/lib/libkdeinit4_konsole.so
#7  0xb7f24445 in ?? () from /usr/lib/libkdeinit4_konsole.so
#8  0xb7f3892d in ?? () from /usr/lib/libkdeinit4_konsole.so
#9  0xb79e6320 in KMainWindow::closeEvent () from /usr/lib/libkdeui.so.5
#10 0xb6ac8383 in QWidget::event () from /usr/lib/libQtGui.so.4
#11 0xb6e1c517 in QMainWindow::event () from /usr/lib/libQtGui.so.4
#12 0xb79e5a67 in KMainWindow::event () from /usr/lib/libkdeui.so.5
#13 0xb7a2a26c in KXmlGuiWindow::event () from /usr/lib/libkdeui.so.5
#14 0xb6a708ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#15 0xb6a787fa in QApplication::notify () from /usr/lib/libQtGui.so.4
#16 0xb7902fed in KApplication::notify () from /usr/lib/libkdeui.so.5
#17 0xb73cce61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#18 0xb6acb4b3 in QWidgetPrivate::close_helper () from /usr/lib/libQtGui.so.4
#19 0xb6ad060b in QApplication::x11ClientMessage () from /usr/lib/libQtGui.so.4
#20 0xb6ae16ec in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#21 0xb6b0b7aa in ?? () from /usr/lib/libQtGui.so.4
#22 0xb63136f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0xb6316da3 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0xb6316f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0xb73f7478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#26 0xb6b0aea5 in ?? () from /usr/lib/libQtGui.so.4
#27 0xb73cb52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#28 0xb73cb6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#29 0xb73cdda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#30 0xb6a70767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#31 0xb7f3ae52 in kdemain () from /usr/lib/libkdeinit4_konsole.so
#32 0x080486e2 in _start ()
#0  0xb7f91430 in __kernel_vsyscall ()
Comment 1 Dario Andres 2009-03-07 22:09:05 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? 
You need to install the "kdebase-apps-dbg" package
Thanks :)
Comment 2 Dario Andres 2009-04-17 18:39:04 UTC
Marking as NEEDSINFO
Comment 3 Brian Wootton 2009-04-25 21:38:16 UTC
Konsole crashed 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.

(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)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f15c15a2750 (LWP 3157)]
(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)
0x00007f15bc6f0cf0 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (process 3157)]

Thread 1 (Thread 0x7f15c15a2750 (LWP 3157)):
#0  0x00007f15bc6f0cf0 in nanosleep () from /lib/libc.so.6
#1  0x00007f15bc6f0b47 in sleep () from /lib/libc.so.6
#2  0x00007f15bfef5b1f in ?? () from /usr/lib/libkdeui.so.5
#3  0x00007f15bfef642a in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#4  <signal handler called>
#5  0x00007f15c11645a0 in ?? () from /usr/lib/libkdeinit4_konsole.so
#6  0x00007f15c1169d79 in ?? () from /usr/lib/libkdeinit4_konsole.so
#7  0x00007f15c117c621 in ?? () from /usr/lib/libkdeinit4_konsole.so
#8  0x00007f15bff5f381 in KMainWindow::closeEvent () from /usr/lib/libkdeui.so.5
#9  0x00007f15be4f039d in QWidget::event () from /usr/lib/libQtGui.so.4
#10 0x00007f15be8a507b in QMainWindow::event () from /usr/lib/libQtGui.so.4
#11 0x00007f15bff9b838 in KXmlGuiWindow::event () from /usr/lib/libkdeui.so.5
#12 0x00007f15be49f83d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#13 0x00007f15be4a7a2a in QApplication::notify () from /usr/lib/libQtGui.so.4
#14 0x00007f15bfe9026b in KApplication::notify () from /usr/lib/libkdeui.so.5
#15 0x00007f15bf2b575c in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#16 0x00007f15be4f548b in QWidgetPrivate::close_helper () from /usr/lib/libQtGui.so.4
#17 0x00007f15be4fc755 in QApplication::x11ClientMessage () from /usr/lib/libQtGui.so.4
#18 0x00007f15be50fc16 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#19 0x00007f15be538514 in ?? () from /usr/lib/libQtGui.so.4
#20 0x00007f15ba1aa20a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0x00007f15ba1ad8e0 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0x00007f15ba1ada7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0x00007f15bf2dee6f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#24 0x00007f15be537c9f in ?? () from /usr/lib/libQtGui.so.4
#25 0x00007f15bf2b4002 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#26 0x00007f15bf2b43cd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#27 0x00007f15bf2b6694 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#28 0x00007f15c117e874 in kdemain () from /usr/lib/libkdeinit4_konsole.so
#29 0x00007f15bc6675a6 in __libc_start_main () from /lib/libc.so.6
#30 0x0000000000400799 in _start ()
#0  0x00007f15bc6f0cf0 in nanosleep () from /lib/libc.so.6
Comment 4 Dario Andres 2009-04-28 03:00:54 UTC
@Brian Wootton: your crash could be a different one. If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace in a NEW report? Thanks :)
Comment 5 Andrew Crouthamel 2018-09-19 04:34:30 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-21 05:02:23 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!