I removed my laptop computer (HP EliteBook 8560w) from a docking station (with external monitor). Then, the screen flickered for a few seconds and afterwards the bug reporting assistant appeared. The desktop with the program windows and the panel is now too large for the desktop screen (probably as large as the external monitor that was connected). When the mouse pointer reaches an edge of the laptop screen, the part of the desktop that is shown on the laptop screen moves accordingly. This bug may be related to bug #348873 and the following bug, which I experience from time to time on the same computer: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1461001 I wanted to report this bug with the bug reporting assistant but---although I logged into bugs.kde.org with the bug reporting assistan---the assistant claimed that I am not logged in so that I had to file the bug report manually. Here is the information collected by the bug reporting assistant (including a "3 star" backtrace): ========================= Application: plasmashell (5.2.2) Qt Version: 5.4.1 Operating System: Linux 3.19.0-20-generic x86_64 Distribution: Ubuntu 15.04 -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe4cab7c7c0 (LWP 3713))] <<< I will post the (very long) remainder of the backtrace as an attachment because it has more characters than allowed for this field >>> Report to https://bugs.kde.org/ Reproducible: Didn't try
Created attachment 93187 [details] Backtrace and other collected information
Thanks. From the backtrace #6 0x00007fe4b73ef290 in QXcbWindow::devicePixelRatio (this=<optimized out>) at qxcbwindow.cpp:2453 Crash is deep in Qt. it can't cope with their being no screen. This was all rewritten to not crash anymore. I see you're running Qt 5.4.1, could you see if you still have this after you've upgraded to Qt 5.4.2
Thank you for your immediate response, David! Do you know if I will soon get Qt 5.4.2 with the usual (K)Ubuntu (15.04) upgrades or if I have to install it manually? (I am rather reluctant to install it manually, because I do not like to make experiments on a computer that I need so much for my work.)
I can't comment on distro specific things with any accuracy (there are too many for me to follow) but I would imagine it will be in their backports PPA.
Thank you for your response. I can understand. The following bug report for Ubuntu at launchpad may refer to the same (or a related) bug: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1450137
Pasting backtrace inline Thread 1 (Thread 0x7fe4cab7c7c0 (LWP 3713)): [KCrash Handler] #6 0x00007fe4b73ef290 in QXcbWindow::devicePixelRatio (this=<optimized out>) at qxcbwindow.cpp:2453 #7 0x00007fe4b73f584d in QXcbWindow::handleConfigureNotifyEvent (this=0x45a2450, event=0x7fe4b002e610) at qxcbwindow.cpp:1883 #8 0x00007fe4b73e0460 in QXcbConnection::handleXcbEvent (this=this@entry=0x182b490, event=event@entry=0x7fe4b002e610) at qxcbconnection.cpp:884 #9 0x00007fe4b73e14bb in QXcbConnection::processXcbEvents (this=0x182b490) at qxcbconnection.cpp:1303 #10 0x00007fe4c623073a in QObject::event (this=0x182b490, e=<optimized out>) at kernel/qobject.cpp:1245 #11 0x00007fe4c6b08b2c in QApplicationPrivate::notify_helper (this=0x180e1e0, receiver=0x182b490, e=0x7fe4b002ef20) at kernel/qapplication.cpp:3720 #12 0x00007fe4c6b0e000 in QApplication::notify (this=0x7fff3fc403a0, receiver=0x182b490, e=0x7fe4b002ef20) at kernel/qapplication.cpp:3503 #13 0x00007fe4c61fec2b in QCoreApplication::notifyInternal (this=0x7fff3fc403a0, receiver=0x182b490, event=event@entry=0x7fe4b002ef20) at kernel/qcoreapplication.cpp:935 #14 0x00007fe4c6200c9b in sendEvent (event=0x7fe4b002ef20, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:228 #15 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1803bd0) at kernel/qcoreapplication.cpp:1552 #16 0x00007fe4c6201298 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1410 #17 0x00007fe4c6257843 in postEventSourceDispatch (s=0x1863250) at kernel/qeventdispatcher_glib.cpp:271 #18 0x00007fe4c204bc3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007fe4c204bf20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007fe4c204bfcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007fe4c6257c57 in QEventDispatcherGlib::processEvents (this=0x186f470, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #22 0x00007fe4c61fc3e2 in QEventLoop::exec (this=this@entry=0x7fff3fc40220, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #23 0x00007fe4c620402c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188 #24 0x00007fe4c654331c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1510 #25 0x00007fe4c6b047a5 in QApplication::exec () at kernel/qapplication.cpp:2956 #26 0x000000000042fd9b in main (argc=2, argv=<optimized out>) at ../../shell/main.cpp:158 Report to https://bugs.kde.org/
*** Bug 345718 has been marked as a duplicate of this bug. ***