Bug 345708 - Konsole crash during exiting
Summary: Konsole crash during exiting
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.14.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-03-31 00:14 UTC by Giuseppe Roberti
Modified: 2018-11-30 04:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Giuseppe Roberti 2015-03-31 00:14:48 UTC
Application: konsole (2.14.2)
KDE Platform Version: 4.14.6
Qt Version: 4.8.6
Operating System: Linux 3.18.9-200.fc21.x86_64 x86_64
Distribution: "Fedora release 21 (Twenty One)"

-- Information about the crash:
- What I was doing when the application crashed:

I was editing a file using vim on a Konsole tab.
Afer exiting vim i quit the shell using Ctrl+d as I usually do.
Then the crash occour.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f80e639c880 (LWP 2214))]

Thread 2 (Thread 0x7f80b75bb700 (LWP 2685)):
#0  0x00007f80e2f33c8d in poll () at /lib64/libc.so.6
#1  0x00007f80df61cb34 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#2  0x00007f80df61cc4c in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#3  0x00007f80e4d414be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#4  0x00007f80e4d10cc1 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#5  0x00007f80e4d11025 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#6  0x00007f80e4c05b49 in QThread::exec() () at /lib64/libQtCore.so.4
#7  0x00007f80e4cf1623 in QInotifyFileSystemWatcherEngine::run() () at /lib64/libQtCore.so.4
#8  0x00007f80e4c083af in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4
#9  0x00007f80e497752a in start_thread () at /lib64/libpthread.so.0
#10 0x00007f80e2f3f22d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f80e639c880 (LWP 2214)):
[KCrash Handler]
#6  0x0000000000000000 in  ()
#7  0x00007f80e3ec4ba0 in QApplication::x11ProcessEvent(_XEvent*) () at /lib64/libQtGui.so.4
#8  0x00007f80e3eecff4 in x11EventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQtGui.so.4
#9  0x00007f80df61c7fb in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#10 0x00007f80df61cb98 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#11 0x00007f80df61cc4c in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#12 0x00007f80e4d4149e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#13 0x00007f80e3eed176 in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtGui.so.4
#14 0x00007f80e4d10cc1 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#15 0x00007f80e4d11025 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#16 0x00007f80e4d16709 in QCoreApplication::exec() () at /lib64/libQtCore.so.4
#17 0x00007f80c4484f69 in kdemain () at /lib64/libkdeinit4_konsole.so
#18 0x000000000040825d in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) ()
#19 0x00000000004090a9 in handle_launcher_request(int, char const*) [clone .isra.15] ()
#20 0x0000000000409787 in handle_requests(int) ()
#21 0x000000000040537d in main ()

The reporter indicates this bug may be a duplicate of or related to bug 333662.

Possible duplicates by query: bug 333693, bug 333662.

Reported using DrKonqi
Comment 1 Andrew Crouthamel 2018-10-31 04:08:24 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Bug Janitor Service 2018-11-15 10:52:20 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 3 Bug Janitor Service 2018-11-30 04:04:51 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!