[kde] [Bug 328102] New: Kscreen crashed when HDMI cable unplugged with kscreen open

[josephj at main.nc.us]

https://bugs.kde.org/show_bug.cgi?id=328102

            Bug ID: 328102
           Summary: Kscreen crashed when HDMI cable unplugged with kscreen
                    open
    Classification: Unclassified
           Product: kde
           Version: unspecified
          Platform: unspecified
                OS: Linux
            Status: UNCONFIRMED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: josephj111111 at gmail.com

Application: kscreen-console (1.0)
KDE Platform Version: 4.11.3
Qt Version: 4.8.2
Operating System: Linux 3.2.0-56-generic x86_64
Distribution: Ubuntu 12.04.3 LTS

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

Just did a massive backports update after adding the ppa and then installing
kscreen. (Rebooted)
Then unplugged my HDMI cable while kscreen was open in system settings.

- Unusual behavior I noticed:
HDMI monitor went active, but stayed black.
Tasks showed up in taskbar, but clicking on them didn't restore them.

The crash can be reproduced every time.

-- Backtrace:
Application: KScreen Console (kscreen-console), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  KScreen::Mode::size (this=0x0) at
/build/buildd/libkscreen-0.0.71/src/mode.cpp:84
#7  0x0000000000407d92 in Console::printConfig (this=<optimized out>) at
/build/buildd/kscreen-0.0.71/console/console.cpp:72
#8  0x00007fc48290d781 in QMetaObject::activate (sender=0xbf3a60, m=<optimized
out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#9  0x00007fc471e8bf9d in XRandR::updateOutput (this=<optimized out>,
output=67) at /build/buildd/libkscreen-0.0.71/backends/xrandr/xrandr.cpp:116
#10 0x00007fc48290d781 in QMetaObject::activate (sender=0xc7d5d0, m=<optimized
out>, local_signal_index=<optimized out>, argv=0x7fffe99cd000) at
kernel/qobject.cpp:3547
#11 0x00007fc471e8d052 in XRandRX11Helper::outputChanged (this=<optimized out>,
_t1=67) at
/build/buildd/libkscreen-0.0.71/obj-x86_64-linux-gnu/backends/xrandr/xrandrx11helper.moc:120
#12 0x00007fc471e8d465 in XRandRX11Helper::x11Event (this=0xc7d5d0,
event=0x7fffe99cd570) at
/build/buildd/libkscreen-0.0.71/backends/xrandr/xrandrx11helper.cpp:133
#13 0x00007fc4811cae26 in publicX11Event (e=0x7fffe99cd570, this=<optimized
out>) at ../../kdeui/kernel/ksystemeventfilter.cpp:43
#14 KSystemEventFilterPrivate::filterEvent (this=0xc7f490,
message=0x7fffe99cd570) at ../../kdeui/kernel/ksystemeventfilter.cpp:102
#15 0x00007fc4828ebdce in QAbstractEventDispatcher::filterEvent
(this=<optimized out>, message=<optimized out>) at
kernel/qabstracteventdispatcher.cpp:539
#16 0x00007fc481d22fc8 in x11EventSourceDispatch (s=0xaa4510, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:143
#17 0x00007fc47f98cd13 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fc47f98d060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fc47f98d124 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fc4829288bf in QEventDispatcherGlib::processEvents (this=0xa82b90,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#21 0x00007fc481d22cde in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007fc4828f7e62 in QEventLoop::processEvents (this=<optimized out>,
flags=...) at kernel/qeventloop.cpp:149
#23 0x00007fc4828f80b7 in QEventLoop::exec (this=0x7fffe99cd910, flags=...) at
kernel/qeventloop.cpp:204
#24 0x00007fc4828fd407 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1187
#25 0x0000000000403ff3 in main (argc=3, argv=0x7fffe99cdd28) at
/build/buildd/kscreen-0.0.71/console/main.cpp:79

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the assignee for the bug.