Bug 329958 - KDE Goes to black screen with mouse pointer after plugging in HDMI monitor and powering up from sleep
Summary: KDE Goes to black screen with mouse pointer after plugging in HDMI monitor an...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: solid
Classification: Frameworks and Libraries
Component: powermanagement-daemon (show other bugs)
Version: 4.11.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-01-14 15:19 UTC by stevenpuzzle
Modified: 2018-09-04 15:44 UTC (History)
6 users (show)

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 stevenpuzzle 2014-01-14 15:19:22 UTC
Application: kded4 (4.11.3)
KDE Platform Version: 4.11.3
Qt Version: 4.8.4
Operating System: Linux 3.11.0-14-generic x86_64
Distribution: Ubuntu 13.10

-- Information about the crash:
- What I was doing when the application crashed: Powered up from sleep with HDMI monitor plugged into laptop that was not plugged in before sleep. 

- Unusual behavior I noticed: Screen was not "frozen", just black with working mouse pointer that worked on both laptop and external monitor. No keyboard or click action seemed to correct. Unplugging and replugging HDMI fixed.

- Custom settings of the application:

The crash can be reproduced sometimes.

-- Backtrace:
Application: KDE Daemon (kded4), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe8ec9577c0 (LWP 1815))]

Thread 6 (Thread 0x7fe8d2048700 (LWP 1817)):
#0  0x00007fe8e730d0f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fe8e730d399 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe8e72cd286 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe8e72cd708 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fe8e72cd7ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fe8eb5faa76 in QEventDispatcherGlib::processEvents (this=0x7fe8cc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007fe8eb5cc5ef in QEventLoop::processEvents (this=this@entry=0x7fe8d2047db0, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007fe8eb5cc8e5 in QEventLoop::exec (this=this@entry=0x7fe8d2047db0, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007fe8eb4cb88f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#9  0x00007fe8eb4cdf2f in QThreadPrivate::start (arg=0x2639680) at thread/qthread_unix.cpp:338
#10 0x00007fe8e79a8f6e in start_thread (arg=0x7fe8d2048700) at pthread_create.c:311
#11 0x00007fe8ea1cf9cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 5 (Thread 0x7fe8c588c700 (LWP 1834)):
#0  0x00007fe8e730d0ea in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fe8e730d3c9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe8e72cd299 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe8e72cd708 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fe8e72cdb0a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fe8c5d87b66 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x00007fe8e72f20f5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007fe8e79a8f6e in start_thread (arg=0x7fe8c588c700) at pthread_create.c:311
#8  0x00007fe8ea1cf9cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 4 (Thread 0x7fe8c4e7f700 (LWP 1835)):
#0  0x00007fff755f1a2f in clock_gettime ()
#1  0x00007fe8ea1e496d in clock_gettime (clock_id=<optimized out>, tp=<optimized out>) at ../sysdeps/unix/clock_gettime.c:115
#2  0x00007fe8eb522757 in do_gettime (frac=0x7fe8c4e7eb00, sec=0x7fe8c4e7eaf8) at tools/qelapsedtimer_unix.cpp:123
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#4  0x00007fe8eb5fbfe5 in updateCurrentTime (this=0x7fe8a8002860) at kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x7fe8a8002860, tm=...) at kernel/qeventdispatcher_unix.cpp:461
#6  0x00007fe8eb5fa82c in timerSourcePrepareHelper (src=<optimized out>, timeout=0x7fe8c4e7ebb4) at kernel/qeventdispatcher_glib.cpp:136
#7  0x00007fe8eb5fa8d5 in timerSourcePrepare (source=<optimized out>, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#8  0x00007fe8e72ccd4d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x00007fe8e72cd5c3 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007fe8e72cd7ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007fe8eb5faa76 in QEventDispatcherGlib::processEvents (this=0x7fe8a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#12 0x00007fe8eb5cc5ef in QEventLoop::processEvents (this=this@entry=0x7fe8c4e7ed70, flags=...) at kernel/qeventloop.cpp:149
#13 0x00007fe8eb5cc8e5 in QEventLoop::exec (this=this@entry=0x7fe8c4e7ed70, flags=...) at kernel/qeventloop.cpp:204
#14 0x00007fe8eb4cb88f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#15 0x00007fe8cb539fd7 in KCupsConnection::run() () from /usr/lib/libkcupslib.so
#16 0x00007fe8eb4cdf2f in QThreadPrivate::start (arg=0x267b130) at thread/qthread_unix.cpp:338
#17 0x00007fe8e79a8f6e in start_thread (arg=0x7fe8c4e7f700) at pthread_create.c:311
#18 0x00007fe8ea1cf9cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7fe8b7fff700 (LWP 1836)):
#0  0x00007fe8ea1c2f7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fe8e72cd6a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe8e72cd7ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe8eb5faa76 in QEventDispatcherGlib::processEvents (this=0x7fe8b00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007fe8eb5cc5ef in QEventLoop::processEvents (this=this@entry=0x7fe8b7ffedb0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fe8eb5cc8e5 in QEventLoop::exec (this=this@entry=0x7fe8b7ffedb0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fe8eb4cb88f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#7  0x00007fe8eb4cdf2f in QThreadPrivate::start (arg=0x2782a00) at thread/qthread_unix.cpp:338
#8  0x00007fe8e79a8f6e in start_thread (arg=0x7fe8b7fff700) at pthread_create.c:311
#9  0x00007fe8ea1cf9cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7fe8b77fe700 (LWP 1837)):
#0  0x00007fe8e730d0ea in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fe8e730d399 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe8e72cd286 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe8e72cd708 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fe8e72cd7ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fe8eb5faa76 in QEventDispatcherGlib::processEvents (this=0x7fe8ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007fe8eb5cc5ef in QEventLoop::processEvents (this=this@entry=0x7fe8b77fdd70, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007fe8eb5cc8e5 in QEventLoop::exec (this=this@entry=0x7fe8b77fdd70, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007fe8eb4cb88f in QThread::exec (this=this@entry=0x2700f50) at thread/qthread.cpp:542
#9  0x00007fe8eb5add13 in QInotifyFileSystemWatcherEngine::run (this=0x2700f50) at io/qfilesystemwatcher_inotify.cpp:265
#10 0x00007fe8eb4cdf2f in QThreadPrivate::start (arg=0x2700f50) at thread/qthread_unix.cpp:338
#11 0x00007fe8e79a8f6e in start_thread (arg=0x7fe8b77fe700) at pthread_create.c:311
#12 0x00007fe8ea1cf9cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7fe8ec9577c0 (LWP 1815)):
[KCrash Handler]
#5  0x00007fe8e23f76a7 in ?? () from /usr/lib/libsolid.so.4
#6  0x00007fe8eb5e1a58 in QMetaObject::activate (sender=0x2885670, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3539
#7  0x00007fe8eb5e1a58 in QMetaObject::activate (sender=sender@entry=0x2885680, m=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff755eb2a0) at kernel/qobject.cpp:3539
#8  0x00007fe8e8965762 in QDBusInterfacePrivate::metacall (this=0x2892600, c=<optimized out>, id=0, argv=0x7fff755eb2a0) at qdbusinterface.cpp:278
#9  0x00007fe8e8952e36 in QDBusConnectionPrivate::deliverCall (this=0x254b940, object=0x2885680, msg=..., metaTypes=..., slotIdx=5) at qdbusintegrator.cpp:951
#10 0x00007fe8eb5e5dce in QObject::event (this=0x2885680, e=<optimized out>) at kernel/qobject.cpp:1194
#11 0x00007fe8ea96adfc in QApplicationPrivate::notify_helper (this=this@entry=0x24616a0, receiver=receiver@entry=0x2885680, e=e@entry=0x27e4000) at kernel/qapplication.cpp:4567
#12 0x00007fe8ea971470 in QApplication::notify (this=0x7fff755eba80, receiver=0x2885680, e=0x27e4000) at kernel/qapplication.cpp:4353
#13 0x00007fe8ec34ba6a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#14 0x00007fe8eb5cd8bd in QCoreApplication::notifyInternal (this=0x7fff755eba80, receiver=receiver@entry=0x2885680, event=event@entry=0x27e4000) at kernel/qcoreapplication.cpp:946
#15 0x00007fe8eb5d0e1f in sendEvent (event=0x27e4000, receiver=0x2885680) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#16 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x23bd150) at kernel/qcoreapplication.cpp:1570
#17 0x00007fe8eb5d12c3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1463
#18 0x00007fe8eb5fb073 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#19 postEventSourceDispatch (s=0x2461b10) at kernel/qeventdispatcher_glib.cpp:279
#20 0x00007fe8e72cd3b6 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fe8e72cd708 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007fe8e72cd7ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007fe8eb5faa55 in QEventDispatcherGlib::processEvents (this=0x23bf670, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#24 0x00007fe8eaa0c9d6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x00007fe8eb5cc5ef in QEventLoop::processEvents (this=this@entry=0x7fff755eb950, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007fe8eb5cc8e5 in QEventLoop::exec (this=this@entry=0x7fff755eb950, flags=...) at kernel/qeventloop.cpp:204
#27 0x00007fe8eb5d1e5b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#28 0x00007fe8d746195b in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so
#29 0x00000000004083f5 in _start ()

Possible duplicates by query: bug 329033, bug 328733, bug 328057, bug 327839, bug 327329.

Reported using DrKonqi
Comment 1 Christoph Feck 2014-01-14 22:57:29 UTC
If this is reproducible, please install debug symbols for kdelibs, and add an updated backtrace.
Comment 2 stevenpuzzle 2014-02-04 16:16:48 UTC
Since this happened, I trashed my partition and had to do a fresh install of Kubuntu 13.10. I can not reproduce now. I suspect, as with many things like the KWallet pop-up after log in, the fresh install cleaned up issues remaining from upgrading. I started in the 11's somewhere.
Comment 3 mhruscak 2015-01-20 12:46:18 UTC
specifications:
Lenovo t440s with docking station, external monitor connected to docking station with DVI cable.
Fedora 21 with KDE plasma-workstation

This bug annoys me every time a turn-on my computer without docking station and external monitor. Then turn-off(not sleep or hibernate) plug in to docking station with attached ext. monitor and after that turn-on -> black screen (probably plasma-desktop not loaded correctly)

Any other applications, shortcuts works fine. Nothing special in logs nor in processes observed.

Seems like desktop wallpaper and all widget are covered with black color, because when trying to unplug monitor or detach from docking station, the desktop shows for half a second or less.

Reproducible:
100%

Steps to reproduce:
1. power-on notebook without any connected HW(mouse, monitor, etc) 
2. normal power-off
3. attach to docking station with external monitor connected
4. power-on -> log-in
5. black desktop screen appears

Actual results:
plasma-desktop is all black and inactive

Expected results:
plasma-desktop should load and work after log-in

Possible workaround:
1) When I reinstall KDE plasma desktop group using yum, it works as expected for 1-2 times, then happened again.
2) Start the notebook alone(without plugging it into docking station), log-in -> attach to docking-station(monitor will not be detected automatically) -> system settings -> display and monitor -> manually enable external monitor - works for me

Contact me pleae on email if you will need some log files or something.
Comment 4 Jonathan Riddell 2015-03-11 19:17:19 UTC
This bug is reported on libsolid which is the kdelibs4 version of the solid library.  It is now in maintenance mode.  If you think it should still be fixed in the KDE Frameworks 5 version of solid please move it to or report a bug on frameworks-solid or Powerdevil.
Comment 5 Jimmy Berry 2015-10-20 00:49:44 UTC
I see the same issue with a three monitor setup. Many times the third monitor (same each time) will start black with no interactions. I can place windows on that screen, but no background or interaction. The only solution I've found is to enable and disable the monitor. Which results in a crash similar to #351777.

qt 5.5.0
plasma-framework 5.14.0
plasma5-workspace 5.4.1
Comment 6 Margot 2015-11-18 06:45:22 UTC
I am also experiencing this bug. 

I upgraded my system yesterday (11/16/15) and KDE Plasma had a huge upgrade that came down the pipeline. Since then, every time I plug my HDMI cable into my laptop (Macbook Pro Early 2015), my laptop screen goes black and the external monitor does, too. I can see a pointer on the screen but no desktop. I cannot click anything and am forced to do a hard reboot. Previously, the HDMI external monitor connection had been buggy, but only when returning from sleep mode and was 90% of the time functioning. Now it is functioning 0% of the time.

Arch Linux 4.2.5
KDE Plasma 5.4.3
Comment 7 Margot 2015-11-18 06:45:41 UTC
I am also experiencing this bug. 

I upgraded my system yesterday (11/16/15) and KDE Plasma had a huge upgrade that came down the pipeline. Since then, every time I plug my HDMI cable into my laptop (Macbook Pro Early 2015), my laptop screen goes black and the external monitor does, too. I can see a pointer on the screen but no desktop. I cannot click anything and am forced to do a hard reboot. Previously, the HDMI external monitor connection had been buggy, but only when returning from sleep mode and was 90% of the time functioning. Now it is functioning 0% of the time.

Arch Linux 4.2.5
KDE Plasma 5.4.3
Comment 8 rockmen1 2015-12-05 04:45:55 UTC
Same here, my HTPC connects to a HDMI TV, when I turn off/on the TV, plasma desktop will be gone, leaving only a mouse pointer.

Arch Linux 4.2.5
KDE Plasma 5.4.3
Comment 9 Thomas Weissel 2016-04-16 18:02:42 UTC
the same bug occurs on my setup
kubuntu 16.04
plasmashell 5.5.5

dual (or triple) screen setup


everytime one of the screens goes to sleep or is powered down plasma shell "kinda" crashes..  
(not ontirely - otherwise it would just restart)

sometimes on one of the screens the wallpaper is still visible and rightclick opens the context menu..  usually the screens are just black and input events are not recognized anymore..  the rest of the system (kwin, other programs) continue to work properly..   so starting krunner and killing && restarting plasmashell gives you a working system again.

it seems to be irrellevant if the display is connected via usb (displaylink), hdmi, dvi or displaylink.
Comment 10 Andrew Crouthamel 2018-09-04 15:44:14 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. Please try again with the latest version and submit a new bug to frameworks-solid if your issue persists. Thank you!