https://bugs.kde.org/show_bug.cgi?id=351025
Matthias Blaicher <matth...@blaicher.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matth...@blaicher.com
--- Comment #28 from Matthias Blaicher <matth...@blaicher.com> ---
Given my huge issues with multi-monitors in general on multiple laptops. I've
decided to try reproducing other people's issues first.
I am running Arch Linux with enabled testing repositories, which is
Qt: 5.6.0
Plasma Desktop: 5.6.4
KDE Applications: 16.04.1
KScreen and LibKscreen are from git master (c949f3d, d80fede)
I have a intel Haswell card.
I've followed the steps described in the original post with an external VGA
monitor and could not reproduce the described state where all monitors are
disabled.
However, the plasmashell barely became active on the new monitor, with panels
missing and wrong background. After some time (maybe after pressing Alt+F2),
the panels popped up again.
Reattaching the monitor resulted In the expected beaviour, disabling the Laptop
monitor and only enabling the VGA screen. However, plasmashell behaved
strangely again: While the wallpaper was now right, the panels were in the
middle of the screen, probably at the positions from the old laptop screen.
This was followed by a plasmashell crash, involving Kscreen in some kind:
[KCrash Handler]
#5 0x00007f894a69a7f0 in Plasma::Applet::actions() const () from
/usr/lib/libKF5Plasma.so.5
#6 0x0000000000446303 in ?? ()
#7 0x000000000044647f in ?? ()
#8 0x00007f894622b71c in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#9 0x00007f894b366d73 in
KScreen::Output::apply(QSharedPointer<KScreen::Output> const&) () from
/usr/lib/libKF5Screen.so.7
#10 0x00007f894b3480a4 in
KScreen::Config::apply(QSharedPointer<KScreen::Config> const&) () from
/usr/lib/libKF5Screen.so.7
#11 0x00007f894b354586 in
KScreen::ConfigMonitor::Private::updateConfigs(QSharedPointer<KScreen::Config>
const&) () from /usr/lib/libKF5Screen.so.7
#12 0x00007f894b356709 in
KScreen::ConfigMonitor::Private::edidReady(QDBusPendingCallWatcher*) () from
/usr/lib/libKF5Screen.so.7
#13 0x00007f894622b71c in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#14 0x00007f894704167f in
QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from
/usr/lib/libQt5DBus.so.5
#15 0x00007f8947041778 in ?? () from /usr/lib/libQt5DBus.so.5
#16 0x00007f894622c179 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#17 0x00007f89473b47bc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#18 0x00007f89473b995f in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#19 0x00007f89461fe280 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#20 0x00007f89462001fc in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#21 0x00007f89462542c3 in ?? () from /usr/lib/libQt5Core.so.5
#22 0x00007f8941db2dd7 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#23 0x00007f8941db3040 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0x00007f8941db30ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#25 0x00007f89462546cf in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQt5Core.so.5
#26 0x00007f89461fc46a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQt5Core.so.5
#27 0x00007f8946204a0c in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#28 0x000000000041c17c in ?? ()
#29 0x00007f8945875741 in __libc_start_main () from /usr/lib/libc.so.6
#30 0x000000000041c2e9 in _start ()
Why does plasma anything to do with libkscreen?
In conclusion, maybe this is about the plasmashell not coming up again instead
of the monitor change not executed? At least #3 described seeing the mouse
cursor.
--
You are receiving this mail because:
You are watching all bug changes.
