Bug 319503

Summary: Display issues caused by turning monitor off and back on.
Product: [Plasma] KScreen Reporter: Brian Smith <mindfilled75>
Component: kdedAssignee: Alex Fiestas <afiestas>
Status: RESOLVED DUPLICATE    
Severity: normal CC: dvratil
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Brian Smith 2013-05-08 05:09:09 UTC
When the monitor is powered off and back on, the panel icons by the clock get weird and several things no longer function...like kded, power management, etc. This is usually when a window is supposed to pop up, telling me that KDE has detected a new monitor. Instead, I get the Crash Handler and bug reporting tool.

Executable kdeinit4 PID: Signal:Segmentation Fault (11)

If I try to report the bug, I get this:
Failed to communicate with kded. Make sure it is running.

Reproducible: Always

Steps to Reproduce:
1. Power on the computer (Kubuntu 13.04 AMD 64)
2. Power down the monitor (23" HDTV connected via HDMI, and Nvidia GeForce GT 440)
3. Observe the problem
Actual Results:  
The panel icons by the clock look funny, KDE Daemon - The KDE Crash Handler pops up (Executable kdeinit4 PID: Signal:Segmentation Fault (11), and I cannot report the bug because the OS is unable to communicate with kded.


Expected Results:  
KDE should have displayed a pop-up window telling me that a previous monitor has been disconnected and I have the option to ignore it. KDE should have displayed another pop-up window telling me that it has discovered a new monitor, and I have the option to ignore it.
After that, everything runs smoothly and I have no more problems.

Application: kded4 ($Id$)
KDE Platform Version: 4.10.2
Qt Version: 4.8.4
Operating System: Linux 3.8.0-19-generic x86_64
Distribution: Ubuntu 13.04

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7f0f45bf2700 (LWP 1702)):
#0  0x00007f0f69dd2ae0 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f0f69dd314c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f0f69dd36ba in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f0f45ee24f6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007f0f69df6eb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f0f5d7753b4 in ?? () from /usr/lib/nvidia-310-updates/libGL.so.1
#6  0x00007f0f6a4a7f8e in start_thread (arg=0x7f0f45bf2700) at pthread_create.c:311
#7  0x00007f0f6cc97e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 4 (Thread 0x7f0f451e5700 (LWP 1722)):
#0  0x00007fffe45feaf7 in ?? ()
#1  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f0f449e4700 (LWP 1723)):
#0  0x00007fffe45feaf7 in ?? ()
#1  0x00007f0f449e3ac0 in ?? ()
#2  0x0000000200000001 in ?? ()
#3  0x00007f0f34002660 in ?? ()
#4  0x00007f0f449e3af0 in ?? ()
#5  0x00007f0f449e3ba8 in ?? ()
#6  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f0f33fff700 (LWP 1732)):
#0  0x00007f0f6cc8b3cd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f0f69dd31dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f0f69dd3304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f0f6e0bd036 in QEventDispatcherGlib::processEvents (this=0x7f0f2c0008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f0f6e08d38f in QEventLoop::processEvents (this=this@entry=0x7f0f33ffecd0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f0f6e08d618 in QEventLoop::exec (this=this@entry=0x7f0f33ffecd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f0f6df8f410 in QThread::exec (this=this@entry=0x1dd3a20) at thread/qthread.cpp:542
#7  0x00007f0f6e06eedf in QInotifyFileSystemWatcherEngine::run (this=0x1dd3a20) at io/qfilesystemwatcher_inotify.cpp:256
#8  0x00007f0f6df91bec in QThreadPrivate::start (arg=0x1dd3a20) at thread/qthread_unix.cpp:338
#9  0x00007f0f5d7753b4 in ?? () from /usr/lib/nvidia-310-updates/libGL.so.1
#10 0x00007f0f6a4a7f8e in start_thread (arg=0x7f0f33fff700) at pthread_create.c:311
#11 0x00007f0f6cc97e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f0f6f4217c0 (LWP 1513)):
[KCrash Handler]
#6  KScreen::Output::id (this=this@entry=0x0) at /build/buildd/libkscreen-0.0.81/src/output.cpp:104
#7  0x00007f0f51d15fbc in Generator::extendToRight (this=this@entry=0x1e41280, outputs=...) at /build/buildd/kscreen-0.0.81/kded/generator.cpp:313
#8  0x00007f0f51d17f94 in Generator::idealConfig (this=0x1e41280) at /build/buildd/kscreen-0.0.81/kded/generator.cpp:83
#9  0x00007f0f51d104f6 in KScreenDaemon::applyIdealConfig (this=this@entry=0x1e36c10) at /build/buildd/kscreen-0.0.81/kded/daemon.cpp:110
#10 0x00007f0f51d1077d in KScreenDaemon::applyConfig (this=0x1e36c10) at /build/buildd/kscreen-0.0.81/kded/daemon.cpp:90
#11 0x00007f0f6e0a30ef in QMetaObject::activate (sender=sender@entry=0x1e20170, m=m@entry=0x7f0f51d06b60 <KScreen::Output::staticMetaObject>, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x0) at kernel/qobject.cpp:3539
#12 0x00007f0f51b00a83 in KScreen::Output::isConnectedChanged (this=this@entry=0x1e20170) at /build/buildd/libkscreen-0.0.81/obj-x86_64-linux-gnu/src/output.moc:253
#13 0x00007f0f51b00aa3 in KScreen::Output::setConnected (this=this@entry=0x1e20170, connected=<optimized out>) at /build/buildd/libkscreen-0.0.81/src/output.cpp:308
#14 0x00007f0f516ce4d2 in XRandROutput::updateKScreenOutput (this=this@entry=0x1e3b2b0, output=0x1e20170) at /build/buildd/libkscreen-0.0.81/backends/xrandr/xrandroutput.cpp:265
#15 0x00007f0f516c9469 in XRandRConfig::updateKScreenConfig (this=0x1e40f40, config=0x1e2db00) at /build/buildd/libkscreen-0.0.81/backends/xrandr/xrandrconfig.cpp:107
#16 0x00007f0f51affd4c in KScreen::ConfigMonitor::Private::updateConfigs (this=0x1e482e0) at /build/buildd/libkscreen-0.0.81/src/configmonitor.cpp:46
#17 0x00007f0f51affd9d in KScreen::ConfigMonitor::notifyUpdate (this=0x1e48230) at /build/buildd/libkscreen-0.0.81/src/configmonitor.cpp:89
#18 0x00007f0f516c6f22 in XRandR::updateOutput (this=<optimized out>, output=638) at /build/buildd/libkscreen-0.0.81/backends/xrandr/xrandr.cpp:116
#19 0x00007f0f6e0a30ef in QMetaObject::activate (sender=sender@entry=0x1e29f30, m=m@entry=0x7f0f518d2980 <XRandRX11Helper::staticMetaObject>, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fffe45ec050) at kernel/qobject.cpp:3539
#20 0x00007f0f516c7f52 in XRandRX11Helper::outputChanged (this=this@entry=0x1e29f30, _t1=638) at /build/buildd/libkscreen-0.0.81/obj-x86_64-linux-gnu/backends/xrandr/xrandrx11helper.moc:120
#21 0x00007f0f516c84d5 in XRandRX11Helper::x11Event (this=0x1e29f30, event=0x7fffe45ec1a0) at /build/buildd/libkscreen-0.0.81/backends/xrandr/xrandrx11helper.cpp:140
#22 0x00007f0f6ee3697d in publicX11Event (e=0x7fffe45ec1a0, this=<optimized out>) at ../../kdeui/kernel/ksystemeventfilter.cpp:43
#23 KSystemEventFilterPrivate::filterEvent (this=0x1e3cd00, message=0x7fffe45ec1a0) at ../../kdeui/kernel/ksystemeventfilter.cpp:102
#24 0x00007f0f6e08111e in QAbstractEventDispatcher::filterEvent (this=0x0, message=0x0, message@entry=0x7fffe45ec1a0) at kernel/qabstracteventdispatcher.cpp:539
#25 0x00007f0f6d4da028 in x11EventSourceDispatch (s=0x1c31a00, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:143
#26 0x00007f0f69dd2f05 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007f0f69dd3248 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007f0f69dd3304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007f0f6e0bd016 in QEventDispatcherGlib::processEvents (this=0x1a42670, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#30 0x00007f0f6d4da1ae in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#31 0x00007f0f6e08d38f in QEventLoop::processEvents (this=this@entry=0x7fffe45ec570, flags=...) at kernel/qeventloop.cpp:149
#32 0x00007f0f6e08d618 in QEventLoop::exec (this=this@entry=0x7fffe45ec570, flags=...) at kernel/qeventloop.cpp:204
#33 0x00007f0f6e092cf6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#34 0x00007f0f6d432ffc in QApplication::exec () at kernel/qapplication.cpp:3828
#35 0x00007f0f5844f050 in kdemain (argc=1, argv=0x1abc7c0) at ../../kded/kded.cpp:924
#36 0x00000000004084ea in launch (argc=argc@entry=1, _name=_name@entry=0x40b167 "kded4", args=args@entry=0x0, cwd=cwd@entry=0x0, envc=envc@entry=0, envs=<optimized out>, envs@entry=0x0, reset_env=reset_env@entry=false, tty=tty@entry=0x0, avoid_loops=avoid_loops@entry=false, startup_id_str=startup_id_str@entry=0x40aff6 "0") at ../../kinit/kinit.cpp:738
#37 0x0000000000405b69 in main (argc=4, argv=<optimized out>, envp=0x7fffe45ed1f0) at ../../kinit/kinit.cpp:1853
Comment 1 Daniel Vrátil 2013-05-08 23:16:45 UTC
Please update to KScreen 0.0.92 (or 1.0-RC2), this issue is fixed there.

*** This bug has been marked as a duplicate of bug 318936 ***
Comment 2 Brian Smith 2013-05-09 02:13:44 UTC
I'm somewhat new to the Linux world and don't know how to update to KScreen 0.0.92.
Comment 3 Daniel Vrátil 2013-05-09 12:55:06 UTC
The best way is to check your distribution repositories for updates and/or contact maintainer of kscreen packages in your distribution and ask him to update the package.