Bug 348606 - Reports a crash when I close the settings dialog
Summary: Reports a crash when I close the settings dialog
Status: RESOLVED DUPLICATE of bug 346748
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.3.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-06-03 00:32 UTC by Michael
Modified: 2015-06-07 12:59 UTC (History)
0 users

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 Michael 2015-06-03 00:32:28 UTC
Application: kdeinit5 (5.3.0)

Qt Version: 5.4.1
Operating System: Linux 4.0.4-301.fc22.x86_64 x86_64
Distribution: "Fedora release 22 (Twenty Two)"

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

I started the window settings dialog by right clicking screen title bar - when quitting normally it reports a crash.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Control Module (kdeinit5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f25594d3780 (LWP 2968))]

Thread 2 (Thread 0x7f2521ae0700 (LWP 2974)):
#0  0x00007f255626a66d in poll () at /lib64/libc.so.6
#1  0x00007f25546f0dbc in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#2  0x00007f25546f0ecc in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#3  0x00007f25570ab75b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#4  0x00007f2557051a8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#5  0x00007f2556e6fff4 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x00007f253c72d935 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x00007f2556e74ede in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#8  0x00007f25558bc555 in start_thread () at /lib64/libpthread.so.0
#9  0x00007f2556275f3d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f25594d3780 (LWP 2968)):
[KCrash Handler]
#5  0x00007f25561a8a98 in raise () at /lib64/libc.so.6
#6  0x00007f25561aa72a in abort () at /lib64/libc.so.6
#7  0x00007f25561ebea2 in  () at /lib64/libc.so.6
#8  0x00007f25561f353c in _int_free () at /lib64/libc.so.6
#9  0x00007f25561f7e9c in free () at /lib64/libc.so.6
#10 0x00007f255708205c in QMetaCallEvent::~QMetaCallEvent() () at /lib64/libQt5Core.so.5
#11 0x00007f25570820a9 in QMetaCallEvent::~QMetaCallEvent() () at /lib64/libQt5Core.so.5
#12 0x00007f2557056b37 in QCoreApplication::removePostedEvents(QObject*, int) () at /lib64/libQt5Core.so.5
#13 0x00007f2557084352 in QObjectPrivate::~QObjectPrivate() () at /lib64/libQt5Core.so.5
#14 0x00007f2557084479 in QObjectPrivate::~QObjectPrivate() () at /lib64/libQt5Core.so.5
#15 0x00007f255708cb28 in QObject::~QObject() () at /lib64/libQt5Core.so.5
#16 0x00007f253b5a7dd9 in QXcbConnection::~QXcbConnection() () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#17 0x00007f253b5ab73e in QXcbIntegration::~QXcbIntegration() () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#18 0x00007f253b5ab839 in QXcbIntegration::~QXcbIntegration() () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#19 0x00007f2557569b6e in QGuiApplicationPrivate::~QGuiApplicationPrivate() () at /lib64/libQt5Gui.so.5
#20 0x00007f2557d108b9 in QApplicationPrivate::~QApplicationPrivate() () at /lib64/libQt5Widgets.so.5
#21 0x00007f255708cb28 in QObject::~QObject() () at /lib64/libQt5Core.so.5
#22 0x00007f2557d1261b in QApplication::~QApplication() () at /lib64/libQt5Widgets.so.5
#23 0x00007f253bc98200 in kdemain () at /lib64/libkdeinit5_kcmshell5.so
#24 0x000000000040a797 in handle_launcher_request(int, char const*) [clone .isra.22] ()
#25 0x000000000040cb0b in handle_requests(int) ()
#26 0x000000000040500a in main ()

Reported using DrKonqi
Comment 1 Thomas Lübking 2015-06-07 12:59:23 UTC
Dupe of bug #346748 by 99.9 % chance (but lacks debug symbols to say for sure - if you can provide them and they look different, the bug can be unduped)

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