| Summary: | Settings for 3 external screens connected via DisplayLink dongle get lost after each reboot | ||
|---|---|---|---|
| Product: | [Plasma] KScreen | Reporter: | ProstMeister <colombo.gab> |
| Component: | common | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | colombo.gab, dpbasti, florian, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.26.3 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
ProstMeister
2022-11-20 07:49:01 UTC
Does this happen if you connect the monitors directly? Or at least, as many as your laptop has internal ports for? These dongles are often really bad about this kind of thing. The kscreen-doctor output indicates that it's telling the system that one screen is DisplayPort, one is HDMI, and one is DVI, despite all three being HDMI screens. It's quite possible that the dongle is internally assigning each screen a different ID on every login, which we've also seen before. (In reply to Nate Graham from comment #1) > Does this happen if you connect the monitors directly? Or at least, as many > as your laptop has internal ports for? These dongles are often really bad > about this kind of thing. The kscreen-doctor output indicates that it's > telling the system that one screen is DisplayPort, one is HDMI, and one is > DVI, despite all three being HDMI screens. It's quite possible that the > dongle is internally assigning each screen a different ID on every login, > which we've also seen before. I didn't try that, but I will and let you know. Anyhow, I don't think it's related to the DisplayLink dongle, for the following reasons: 1. As I stated, this has been working before using exactly the same setup (same laptop, same distro, same set of monitors, same dongle), it got broken with Plasma 2.26; 2. The 2 monitors connected to the dongle retain their relative position and settings; 3. The only monitor that doesn't keep the setup after rebooting (or after logging in/out) is the laptop one: every time it turns back to "enabled" and set back to "primary". I just tried to reproduce the problem by getting rid of the screens attached to the DisplayLink dongle, and I confirm you that the behaviour is the same: if I disable the laptop screen and reboot or logout and re-login, the laptop screen gets enabled and set as primary. Moreover, also the relative position gets lost, as the 2 screens get superimposed. Please let me know if you need further information. 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 bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! I confirm the same behavior - to me it started with Plasma 5.27 on Opensuse Tumbleweed 1. Boot to KDE with a laptop connected to a USB-C docking station with external monitor 2. See both internal (laptop) display and external display working 3. Change preference via kcontrolcenter to switch off internal laptop display (switch to external display only) 4. Reboot OBSERVED RESULT Again both displays are on EXPECTED RESULT Settings should be persistant That's a different bug, Sebastian. Can you submit another bug report for it? Thanks! ProstMeister, can you reproduce this bug with Plasma 5.27? 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 bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |