Bug 350636

Summary:	Konsole sometimes crashes when exiting with EOF
Product:	[Applications] konsole	Reporter:	Nicolas F. <kdebugs>
Component:	general	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	martin.sandsmark, moorkai
Priority:	NOR	Keywords:	drkonqi
Version:	15.04.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Nicolas F. 2015-07-26 18:13:29 UTC

Application: konsole (15.04.0)

Qt Version: 5.5.0
Operating System: Linux 4.1.2-2-ARCH x86_64
Distribution: "Arch Linux"

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

Closed konsole with Ctrl+D, which sends an EOF signal. The crash only happens sometimes, but if it does terminates all other konsole windows too.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[KCrash Handler]
#5  0x00007fb17d6e3528 in raise () from /usr/lib/libc.so.6
#6  0x00007fb17d6e493a in abort () from /usr/lib/libc.so.6
#7  0x00007fb17d721bb2 in __libc_message () from /usr/lib/libc.so.6
#8  0x00007fb17d7270fe in malloc_printerr () from /usr/lib/libc.so.6
#9  0x00007fb17d7278db in _int_free () from /usr/lib/libc.so.6
#10 0x00007fb179c4692c in QMetaCallEvent::~QMetaCallEvent() () from /usr/lib/libQt5Core.so.5
#11 0x00007fb179c46979 in QMetaCallEvent::~QMetaCallEvent() () from /usr/lib/libQt5Core.so.5
#12 0x00007fb179c1d3f7 in QCoreApplication::removePostedEvents(QObject*, int) () from /usr/lib/libQt5Core.so.5
#13 0x00007fb179c486f2 in QObjectPrivate::~QObjectPrivate() () from /usr/lib/libQt5Core.so.5
#14 0x00007fb179c48819 in QObjectPrivate::~QObjectPrivate() () from /usr/lib/libQt5Core.so.5
#15 0x00007fb179c512c8 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#16 0x00007fb16801e949 in QXcbConnection::~QXcbConnection() () from /usr/lib/libQt5XcbQpa.so.5
#17 0x00007fb168020346 in QXcbIntegration::~QXcbIntegration() () from /usr/lib/libQt5XcbQpa.so.5
#18 0x00007fb168020459 in QXcbIntegration::~QXcbIntegration() () from /usr/lib/libQt5XcbQpa.so.5
#19 0x00007fb17a1704c3 in QGuiApplicationPrivate::~QGuiApplicationPrivate() () from /usr/lib/libQt5Gui.so.5
#20 0x00007fb17a94f069 in QApplicationPrivate::~QApplicationPrivate() () from /usr/lib/libQt5Widgets.so.5
#21 0x00007fb179c512c8 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#22 0x00007fb17a950e59 in QApplication::~QApplication() () from /usr/lib/libQt5Widgets.so.5
#23 0x00007fb17da75ab4 in kdemain (argc=3, argv=0x7ffdb35ae508) at /home/fratti/absbuilds/konsole/src/konsole-15.04.3/src/main.cpp:87
#24 0x00007fb17d6d0790 in __libc_start_main () from /usr/lib/libc.so.6
#25 0x0000000000400789 in _start ()

Possible duplicates by query: bug 350512, bug 350464, bug 350169, bug 349837, bug 349754.

Reported using DrKonqi

Comment 1 moorkai 2016-02-01 23:36:53 UTC

Created attachment 96969 [details]
New crash information added by DrKonqi

konsole (15.12.1) using Qt 5.5.1

- What I was doing when the application crashed:
Closed Konsole by middle-clicking on its entry in the taskbar.

- Unusual behavior I noticed:
I've set FreeSans as the default font in my Arch installation. When I search for an application in the application launcher, query text bleeds out of the search field.

- Custom settings of the application:
None known except for the little aesthetic bug in previous "Unusual behavior I noticed" part.

-- Backtrace (Reduced):
#12 0x00007fbdb7b3b707 in QCoreApplication::removePostedEvents(QObject*, int) () from /usr/lib/libQt5Core.so.5
#13 0x00007fbdb7b66a22 in QObjectPrivate::~QObjectPrivate() () from /usr/lib/libQt5Core.so.5
#14 0x00007fbdb7b66b49 in QObjectPrivate::~QObjectPrivate() () from /usr/lib/libQt5Core.so.5
#15 0x00007fbdb7b6f618 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#16 0x00007fbda80bb409 in QXcbConnection::~QXcbConnection() () from /usr/lib/libQt5XcbQpa.so.5

Comment 2 Martin Sandsmark 2016-08-13 17:45:24 UTC


*** This bug has been marked as a duplicate of bug 346826 ***