Bug 427178 - I have connected second screen to my computer. Always when I close the laptop cover, screen's layout crashes and sets first screen above second after opening.
Summary: I have connected second screen to my computer. Always when I close the laptop...
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.12.8
Platform: Kubuntu Linux
: NOR major
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-30 20:22 UTC by Filip Koperkiewicz
Modified: 2022-12-09 01:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Excepted and observed result (915.04 KB, image/png)
2020-09-30 20:22 UTC, Filip Koperkiewicz
Details
attachment-11659-0.html (546 bytes, text/html)
2022-12-08 06:03 UTC, Filip Koperkiewicz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Filip Koperkiewicz 2020-09-30 20:22:31 UTC
Created attachment 132031 [details]
Excepted and observed result

SUMMARY
I have connected second screen to my computer. Always when I close the laptop cover, screen's layout crashes and sets first screen above second after opening.

STEPS TO REPRODUCE
1. Set sleep mode after closing laptop cover in power settings.
2. Connect additional screen to computer.
3. Configure this screen to extend desktop at right side (KScreen)
4. Close the cover, wait for sleep and open.

OBSERVED RESULT
See: summary. I think when laptop cover is closing, system thinks that one of screens - build-in or additional is disconnected.

EXPECTED RESULT
System should remember layout of screens and restore it when they'll be connected again.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 18.04
(available in About System)
KDE Plasma Version: 5.12.9
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION
Problem doesn't happen if screen lock is enabled after closing the cover in power settings.
Comment 1 Nate Graham 2022-11-08 21:24:29 UTC
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with Plasma 5.25 or 5.26?

If it is, please change the status to CONFIRMED when replying. If not, or if you can't because you no longer use this setup, you can change the status to RESOLVED WORKSFORME. Thanks a lot!
Comment 2 Bug Janitor Service 2022-11-23 05:15:52 UTC
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!
Comment 3 Bug Janitor Service 2022-12-08 05:15:25 UTC
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!
Comment 4 Filip Koperkiewicz 2022-12-08 06:03:27 UTC
Created attachment 154415 [details]
attachment-11659-0.html

I have no way to check if this bug still apply to the latest version of KDE Plasma. I don't have latest version, because it's not provided by my GNU/Linux distribution yet. You mark an issue as "resolved", but nobody confirmed it, nobody did a pull request mentioning this issue, so how can you tell it's resolved? Inactivity is not a good sign of problem solved, sometimes bugs keeps unfixed for years. https://www.youtube.com/watch?v=1lYgB_NHFYk
Comment 5 Nate Graham 2022-12-09 01:11:13 UTC
Sad but true. The problem really is that multi-monitor bugs can be so random and hardware-specific that it's practically impossible to debug them without having the person who reported the bug available to gather logs, run tests, etc. Ideally that would have been done when you first filed the bug report, but unfortunately it didn't, so here we are. If you no longer use the software or hardware that exhibited the bug, there's no way we can fix it, because none of the people who are in a position to fix it are able to reproduce the issue. I've certainly never encountered something bizarre like what your original screenshot depicts. I am sorry we didn't do a better job two years ago when you originally reported the issue, though.