https://bugs.kde.org/show_bug.cgi?id=351079
Elvis Stansvik <elvst...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |elvst...@gmail.com
--- Comment #9 from Elvis Stansvik <elvst...@gmail.com> ---
I'm also hitting these problems (see my comments on
https://bugs.kde.org/show_bug.cgi?id=356899 which I think may be related to
this).
Desktop Settings were not persisted properly across re-logins for me, and I
discovered that I get extra containments added in
~/.config/plasma-org.kde.plasma.desktop-appletsrc_after (see my attachments on
the other bug).
The settings I apply get saved to a containement with lastScreen=-1, probably
somehow due to these (from .xsession-errors):
last screen is < 0 so putting containment on screen 0
last screen is < 0 so putting containment on screen 1
requesting config for "Desktop" without a containment!
as mentioned by Fredy above.
I also have spurious:
kscreen: Primary output changed from KScreen::Output(Id: 73 , Name: "VGA1" ) (
"VGA1" ) to KScreen::Output(Id: 73 , Name: "VGA1" ) ( "VGA1" )
occurring in .xsession-errors, both before and after those "last screen..."
warnings.
So I think somehow Plasma is confused about what is the current screen to which
the settings should be applied? I know that Qt 5.6 will have several fixes and
improvements re. screen handling and XCB, but could something be done now?
This is on Arch Linux with Qt 5.5.1 and Plasma 5.5.1. I have one internal
LVDS1, which was not active during these tests. I only used the external (VGA1)
output. I should note also that I use xrandr to change monitors normally, since
doing so through System Settings has resulted in crashes in Plasma and Qt (via
Plasma) (should also become better with Qt 5.6).
This bug is NEEDSINFO / WAITINGFORINFO. What more information is needed?
--
You are receiving this mail because:
You are watching all bug changes.
