https://bugs.kde.org/show_bug.cgi?id=480093
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=480093
--- Comment #7 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=480093
--- Comment #6 from Reboot ---
I haven't been able to reproduce this bug as consistently as before, even
though my hardware configuration hasn't changed... I did play around with my
display configuration for unrelated reasons though.
Here's a list of
https://bugs.kde.org/show_bug.cgi?id=480093
--- Comment #5 from Jakob Petsovits ---
Seems similar to bug 480026, which btw (just an observation, not necessarily
meaningful) is also using a discrete AMD GPU.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=480093
--- Comment #4 from Jakob Petsovits ---
The screens are supposed to come back on when "user activity" is detected.
Normally, this means the desktop receiving input events from devices like
touchpad, mouse or keyboard. Activity can also be simulated by
https://bugs.kde.org/show_bug.cgi?id=480093
--- Comment #3 from Reboot ---
- I'm using Wayland.
- I've just done a bit of testing, and it seems to only happen when all of the
three screens are plugged in.
- Yes it does, with the same behavior as above: it happens only when the three
screens are
https://bugs.kde.org/show_bug.cgi?id=480093
Nate Graham changed:
What|Removed |Added
Component|common |general
Product|KScreen
