Related upstream multiscreen bugs below. I believe many of them are actual duplicates (with the same root cause). I propose to keep the list somewhat updated and when we feel multiscreen support is good enough (not necessarily waiting for all bugs listed to be closed), close this bug. Multiscreen configuration not preserved: https://bugs.kde.org/show_bug.cgi?id=356884 https://bugs.kde.org/show_bug.cgi?id=354437 https://bugs.kde.org/show_bug.cgi?id=346961 https://bugs.kde.org/show_bug.cgi?id=350132 KScreen possibly messing with xrandr settings: https://bugs.kde.org/show_bug.cgi?id=350874 https://bugs.kde.org/show_bug.cgi?id=343608 Last but not least bugs with output hot-plug recognition: https://bugs.kde.org/show_bug.cgi?id=340120 https://bugs.kde.org/show_bug.cgi?id=356505 https://bugs.kde.org/show_bug.cgi?id=351025 https://bugs.kde.org/show_bug.cgi?id=346535 Crashes/hangs related to multiscreen. Admittedly crashes are just minor inconvenience, since it's mostly plasma desktop, so restartable: https://bugs.kde.org/show_bug.cgi?id=354823 https://bugs.kde.org/show_bug.cgi?id=353129 https://bugs.kde.org/show_bug.cgi?id=314073 https://bugs.kde.org/show_bug.cgi?id=343543
KDE-3 was the last to successfully manage multiple _separate_ screens, aka "Zaphod mode" (no Xinerama, no TvinView). KDE-4 and onwards including PLASMA-5 do *not* support any setup to reliably deal with a diverse combination of + multiple _different_ HW Graphics Adapters, each having connected + multiple _different_ HW Monitors (esp. with different screen resolutions) Core KDE developers (Martin Gräßlin, Thomas Lübking) state that they are not going to resolve this matter because they judge it being "unimportant" [ https://bugs.kde.org/show_bug.cgi?id=256242#c1 ] , refer to "dbus being screen-agnostic" and hope for Wayland. P.S.: Per default: "X Windowing System: ... the X display *without* the screen number ..." But, a little bit above, a possible alternative is pointed out: "Message Bus Service Scope ... We could add an optional scope to a bus name. For example, for per-(display,session pair), we could have a unique ID for each display generated automatically at login and set on screen 0 by executing a special "set display ID" binary. The ID would be stored in a _DBUS_DISPLAY_ID property and would be a string of random bytes. This ID would then be used to scope names. Starting/locating a service could be done by ID-name pair rather than only by name. ..." [ http://dbus.freedesktop.org/doc/dbus-specification.html#message-bus-starting-services ] Thus, the default X dbus scope is screen-agnostic, correct - but I begin to doubt the dogma of the core KDE developers that it can not be done. Unfortunately, I don't know about the situation in (current) qtdbus.
This is a tracker bug and not a discussion forum. Thanks.
Upstream will drop kscreen at the time Qt 5.6.1 is released. This should solve almost all of the issues.
> https://git.reviewboard.kde.org/r/125451/ Patch is merged to master. Upstream is asking for feedback: http://vizzzion.org/blog/2016/05/multiscreen-in-plasma-5-7-and-beyond/. If you want to help you will need Plasma master branch (kde overlay) and Qt 5.6 stable branch (qt overlay).
(In reply to Johannes Huber from comment #4) > > https://git.reviewboard.kde.org/r/125451/ > > Patch is merged to master. Upstream is asking for feedback: > http://vizzzion.org/blog/2016/05/multiscreen-in-plasma-5-7-and-beyond/. If > you want to help you will need Plasma master branch (kde overlay) and Qt 5.6 > stable branch (qt overlay). Qt 5.6.1 and Plasma 5.6.5 with patch backported now in ~arch.
*** Bug 587394 has been marked as a duplicate of this bug. ***
(In reply to Michael Palimaka (kensington) from comment #5) > (In reply to Johannes Huber from comment #4) > > > https://git.reviewboard.kde.org/r/125451/ > > > > Patch is merged to master. Upstream is asking for feedback: > > http://vizzzion.org/blog/2016/05/multiscreen-in-plasma-5-7-and-beyond/. If > > you want to help you will need Plasma master branch (kde overlay) and Qt 5.6 > > stable branch (qt overlay). > > Qt 5.6.1 and Plasma 5.6.5 with patch backported now in ~arch. Plasma 5.7.0 is now in ~arch too. Please test and give feedback. (On my multiscreen setup it works.)
*** Bug 588286 has been marked as a duplicate of this bug. ***
two more crashes here: https://bugs.kde.org/show_bug.cgi?id=360165 - fixed in qt5.6 https://bugs.kde.org/show_bug.cgi?id=351507 - n/a
Some freezes may not be caused by Plasma-5, but Intel Skylake: https://lists.freedesktop.org/archives/intel-gfx/2016-August/102349.html
Last call for testing: Any serious issues left with Qt 5.6.{1,2} + KDE Plasma 5.8?
*** Bug 588770 has been marked as a duplicate of this bug. ***
I've just upgraded to Plasma 5 from KDE4 The only combination that works for me so far is Plasma 5.8.3 and Qt 5.6.2 Previous versions would just mess up my desktop after login, as in one of those bugs: https://bugs.kde.org/show_bug.cgi?id=371196 https://bugs.kde.org/show_bug.cgi?id=362051 https://bugs.kde.org/show_bug.cgi?id=356225 After upgrading to Qt 5.6.2, it stopped messing panels up, instead I had no instances of Plasma on secondary monitor and two instances of it on primary monitor, but deleting old kscreen configuration seems to fix that Some windows are still restored in weird places after login, but at least multi-screen setup seems to be usable now
(In reply to Valeriy Malov from comment #13) > After upgrading to Qt 5.6.2, it stopped messing panels up, instead I had no > instances of Plasma on secondary monitor and two instances of it on primary > monitor, but deleting old kscreen configuration seems to fix that > > Some windows are still restored in weird places after login, but at least > multi-screen setup seems to be usable now Thanks for testing! For the remaining issues, please check out the following PR to 5.8.3-r1: https://github.com/gentoo/gentoo/pull/2799
One issue surfaced after upgrading to 5.8.3 + Qt 5.6.2, wacomtablet's screen mapping now confuses screen numbers on boot, not sure if it's a wacomtablet bug yet. When mapped to the right screen, it maps to left one instead, but uses geometry of the right screen. It works fine after I restart kded5. If it's a wacomtablet's bug I guess I'll just report it to upstream later.
*** Bug 599420 has been marked as a duplicate of this bug. ***
All needed arches are stable for both Qt 5.6.2 and Plasma 5.8.3. We won't track the multiscreen issues downstream anymore as the majority are fixed now. So please contribute any further issues to the upstream bug tracker.
