https://bugs.kde.org/show_bug.cgi?id=521411
Bug ID: 521411
Summary: Please provide documentation for how to configure
display settings from a TTY or using SSH.
Classification: I don't know
Product: kde
Version First unspecified
Reported In:
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
DESCRIPTION
I'm not sure if this is actually a software limitation or "just" a lack of
documentation. But it turns out to be (almost) impossible to recover from a
non-working display configuration. kscreen-doctor is of no help for this task
as it doesn't "see" the right environment and just bails out (in multiple ways
actually).
I think invalid EDID data of my monitor causes invalid defaults in plasma-setup
of bazzite for some reason (kde is working in NixOS and Cachy but I can easily
"break" it in a similar way using the settings the GUI provides by e.g.
selecting the highest possible resolution and HDR simultaneously)
STEPS TO REPRODUCE
1. Configure display settings that result in a non-working configuration (or
try to install bazzite which for some reason resulted in non-functional
defaults and it was not possible to pass the OOBE.)
2. Try to fix the issue from a TTY or via SSH.
3.
OBSERVED RESULT
Throwing in the towel as documentation is undiscoverable, config files talked
about in forums don't exist and kscreen-doctor bails out.
EXPECTED RESULT
A way to change display settings from a different TTY and/or via SSH to
configure a working configuration.
SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window):
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
Going to TTY2 and running "kscreen-doctor -o" runs into issues as
XDG_RUNTIME_DIR and WAYLAND_DISPLAY are not defined. The user sees a "could not
connect to display" and "core dump" error message.
One way to address this is by setting these two variables (documentation for
this being the case is also non-discoverable, I was told by a kind person on
fedi about this). The provided commands were "export
XDG_RUNTIME_DIR=/run/user/$(id -u)" and "export WAYLAND_DISPLAY=wayland-0".
This probably would normally work, however it didn't for me cause I haven't yet
completed the OOBE and the user "owning" the GUI was "plasma-setup" therefore
the XDG_RUNTIME_DIR variable got misconfigured to my user as that's the one I
was logged into the TTY with. But even when I elevated to root (or even into
the plasma-setup user) kscreen-doctor wasn't usable.
When attempting to run it from either of these (when as root with the uid of
plasma-setup) as any attempt to change settings just resulted in a "applying
config failed! The driver rejcted the output configuration" message.
The only thing that kinda worked was a hack of removing write permission to
`/run/plasma-setup/.config/kwinoutputconfig.json` and changing owner+group to
root after editing it to the correct screen settings. Followed by `systemctl
restart plasmashell.service`. However this killed the OOBE screen and resulted
in a working screen with a cursor (no longer flickering on and off/no-signal)
but quite laggy. And after a few minutes the current time and date was also
shown but still quite laggy and non-responsive.
Tl;Dr: There is a lack of documentation and tooling for handling such issues
and setting working screen settings from a different TTY or SSH.
--
You are receiving this mail because:
You are watching all bug changes.
