https://bugs.kde.org/show_bug.cgi?id=470429
Roy Orbitson <roy-orbit...@devo.net.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |roy-orbit...@devo.net.au
--- Comment #2 from Roy Orbitson <roy-orbit...@devo.net.au> ---
I regularly encounter the same issue on a similar setup: two external monitors
on a notebook and the built-in monitor disabled. Physically unplugging then
reconnecting the "disconnected" display usually gets its connection status
reset.. After doing this, I sometimes need to use the Panels and Desktop
Management dialogue to move thins back to the correct monitors.
I don't know if it's a separate issue but, like bug 427278, Plasma will also
"forget" the config eventually, and at a fresh login will have incorrect
monitors enabled/disabled or has the externals as duplicates of each other,
though I've never set it that way. The login screen (sddm?) never seems to
respect these arrangement settings, and will re-enable the built-in monitor
and/or disable one of the externals.
I tried using autorandr, which applies profiles perfectly from manual
invocation, but seems to conflict with Plasma's own automatic detection. If
anyone knows how to disable Plasma's detection so I can try autorandr properly,
please tell me.
I reduce the frustration by backing up this config (after I've made any changes
and everything's arranged right):
cp -a ~/.config/plasma-org.kde.plasma{,-BACKUP}.desktop-appletsrc
When things go awry again, I log out of any graphical sessions, open a TTY
session, restore it as follows, then log in again:
cp -a ~/.config/plasma-org.kde.plasma{-BACKUP,}.desktop-appletsrc
--
You are receiving this mail because:
You are watching all bug changes.
