Summary: | External display rendered unusable due to misconfiguration | ||
---|---|---|---|
Product: | [Plasma] KScreen | Reporter: | Matthias <shalokshalom> |
Component: | common | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | fanzhuyifan, nate |
Priority: | NOR | Keywords: | multiscreen |
Version First Reported In: | 6.0.2 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=485285 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Matthias
2024-03-27 11:50:28 UTC
Maybe we add kscreen-doctor to the KCM? (By the way, there is no component for KScreen here in the bugtracker) The configuration should automatically revert after 15 seconds if you don't hit confirm. Is this what you are looking for? No. I missed to specify that, but the error occurs, when I confirm a configuration, that doesnt work. As you can read from my report, I am already in a situation, that prevents me from using that TV as an external display. There is no way, to restore its functionality so far as I can see. (Not even modifiying a text file can help, sincs that one is generated and cannot be modified seemingly.) The issue is, that the irrevertable action does not come with the KCM setting itself, but by using the Fn+F7 menu (dont know its name) with which you determine the output configuration. It allows you to choose between several options, among those: ) Switch to internal display ) Switch to external display ) Unify output ) Extend left ) Extend right If you choose to follow the steps outlined in the original report, and then choose 'Switch to external display' there is no way of changing the setup again. And plugging the device in, will always result in a black screen on both devices. Since it is only possible to edit it once plugged in, and plugging it in, it switches to 'external screen only' - even though that one is in an ill state. The TV rejects the format, and we seem to have no detection for that. Another possible solution would be, to never except such an illegal state in the first place. My TV does not accept a seemingly plausible resolution (2560 x 1440) and shows this on its screen. I dont know, if it reports this back on an API as well. *** This bug has been marked as a duplicate of bug 485285 *** I just ran into this again (the confirmation window did not revert to the working state, for some reason) on Arch Linux. |