Bug 341964 - kde kscreen crashes when unplugging HDMI
Summary: kde kscreen crashes when unplugging HDMI
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 1.0.5
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords: drkonqi, triaged
Depends on:
Blocks:
 
Reported: 2014-12-17 07:52 UTC by Jiri Slaby
Modified: 2018-10-27 03:59 UTC (History)
1 user (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 Jiri Slaby 2014-12-17 07:52:13 UTC
Application: kcmshell4 (4.14.3)
KDE Platform Version: 4.14.3
Qt Version: 4.8.6
Operating System: Linux 3.17.6-1.g12b7bf1-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I unplugged the HDMI connector and it crashed. The screen was somehow shrunk then on the LVDS.

-- Backtrace:
Application: KDE Control Module (kcmshell4), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f455d420780 (LWP 22613))]

Thread 3 (Thread 0x7f45410e6700 (LWP 22614)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f454e56e8cb in ?? () from /usr/lib64/libQtScript.so.4
#2  0x00007f454e56e909 in ?? () from /usr/lib64/libQtScript.so.4
#3  0x00007f455bcda0a4 in start_thread (arg=0x7f45410e6700) at pthread_create.c:309
#4  0x00007f455aa467fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f44bfcbc700 (LWP 22615)):
#0  0x00007f4557b928e9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x00007f4557b50bca in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f4557b50cec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f455c09f0de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#4  0x00007f455c070e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#5  0x00007f455c071165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#6  0x00007f455bf6e0bf in QThread::exec() () from /usr/lib64/libQtCore.so.4
#7  0x00007f455c052783 in ?? () from /usr/lib64/libQtCore.so.4
#8  0x00007f455bf7079f in ?? () from /usr/lib64/libQtCore.so.4
#9  0x00007f455bcda0a4 in start_thread (arg=0x7f44bfcbc700) at pthread_create.c:309
#10 0x00007f455aa467fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f455d420780 (LWP 22613)):
[KCrash Handler]
#5  0x00007f45410f1c14 in KScreen::Output::id() const () from /usr/lib64/libkscreen.so.1
#6  0x00007f44bec43464 in XRandRConfig::updateKScreenConfig (this=0x18b4380, config=0x19f40b0) at /usr/src/debug/libkscreen-1.0.5/backends/xrandr/xrandrconfig.cpp:160
#7  0x00007f45410f1319 in KScreen::ConfigMonitor::Private::updateConfigs() () from /usr/lib64/libkscreen.so.1
#8  0x00007f45410f134d in KScreen::ConfigMonitor::notifyUpdate() () from /usr/lib64/libkscreen.so.1
#9  0x00007f44bec40c44 in XRandR::updateCrtc (this=<optimized out>, crtc=<optimized out>) at /usr/src/debug/libkscreen-1.0.5/backends/xrandr/xrandr.cpp:154
#10 0x00007f455c0861fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#11 0x00007f44bec41f17 in outputChanged (_t1=<optimized out>, this=<optimized out>) at /usr/src/debug/libkscreen-1.0.5/build/backends/xrandr/xrandrx11helper.moc:119
#12 XRandRX11Helper::x11Event (this=0x18babb0, event=0x7fff2a5dd110) at /usr/src/debug/libkscreen-1.0.5/backends/xrandr/xrandrx11helper.cpp:147
#13 0x00007f455ce3bdd8 in ?? () from /usr/lib64/libkdeui.so.5
#14 0x00007f455c0641ce in QAbstractEventDispatcher::filterEvent(void*) () from /usr/lib64/libQtCore.so.4
#15 0x00007f455b28b4f0 in ?? () from /usr/lib64/libQtGui.so.4
#16 0x00007f4557b50a04 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#17 0x00007f4557b50c48 in ?? () from /usr/lib64/libglib-2.0.so.0
#18 0x00007f4557b50cec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#19 0x00007f455c09f0be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#20 0x00007f455b28b676 in ?? () from /usr/lib64/libQtGui.so.4
#21 0x00007f455c070e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#22 0x00007f455c071165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#23 0x00007f455b690d1c in QDialog::exec() () from /usr/lib64/libQtGui.so.4
#24 0x00007f4546a6c315 in kdemain () from /usr/lib64/libkdeinit4_kcmshell4.so
#25 0x0000000000408815 in _start ()

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

Possible duplicates by query: bug 336718, bug 335646, bug 334947.

Reported using DrKonqi
Comment 1 Daniel Vrátil 2015-03-06 14:56:10 UTC
Can you still reproduce this crash with Plasma 5 version of KScreen?
Comment 2 Jiri Slaby 2015-03-09 10:08:55 UTC
(In reply to Daniel Vrátil from comment #1)
> Can you still reproduce this crash with Plasma 5 version of KScreen?

The thing is that I was unable to run plasma 5. So I cannot answer this until p5 is properly packaged for opensuse.
Comment 3 Andrew Crouthamel 2018-09-25 21:36:23 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 set the bug status 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 4 Andrew Crouthamel 2018-10-27 03:59:26 UTC
Dear Bug Submitter,

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!