Bug 426671 - Use a function other than random() to decide on which screen to place windows after wakeup
Summary: Use a function other than random() to decide on which screen to place windows...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-multiscreen (show other bugs)
Version: 5.19.5
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-18 07:38 UTC by Anders Lund
Modified: 2020-10-18 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anders Lund 2020-09-18 07:38:50 UTC
When waking up after suspend with an extra screen attached, please restore the screen configuration and windows placement as they were when the system was suspended, instead of randomly 
a) not enabling the laptop screen
b) enabling the laptop screen but move all windows to extra screen

Please.


STEPS TO REPRODUCE
1. Have an extra screen/monitor attached (I use a HDMI cable)
2. suspend system
3. wake up system

OBSERVED RESULT
Often the screen configuration and windows placement is messed up

EXPECTED RESULT
Things working.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: archlinux.
(available in About System)
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
Comment 1 David Edmundson 2020-09-18 11:21:13 UTC
Please don't be deliberately antagonistic.

There is no explicit code to do anything on suspend/resume, and in theory after suspend/resume everything should come up in the same state.

Please include 

kscreen-doctor -l someLog
and perform a supsend/restart that reproduces this issue
Comment 2 Anders Lund 2020-09-18 14:24:58 UTC
Sorry for being ironic.

I tried this:
[anders@elias anders]$ KSCREEN_LOGGING='' kscreen-doctor -l screendoctor
[anders@elias anders]$ 

and found ~/.local/share/kscreen/kscreen.log with a line with "screendoctor" 
in it after a suspend, but no meaningful information.

I will try a few more times, but if I do something wrong, please let me know.

The results after wakeup are not consistent - some times it works like 
expected, but fra from always. If haredware details are helpful, my laptop is 
a Dell Latitude 7440, intel based, and the external monitor is a Dell U2518D.


Anders
--

fredag den 18. september 2020 13.21.13 CEST skrev du:
> https://bugs.kde.org/show_bug.cgi?id=426671
> 
> David Edmundson <kde@davidedmundson.co.uk> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> Resolution|---                         |WAITINGFORINFO
>                  CC|                            |kde@davidedmundson.co.uk
>              Status|REPORTED                    |NEEDSINFO
> 
> --- Comment #1 from David Edmundson <kde@davidedmundson.co.uk> ---
> Please don't be deliberately antagonistic.
> 
> There is no explicit code to do anything on suspend/resume, and in theory
> after suspend/resume everything should come up in the same state.
> 
> Please include
> 
> kscreen-doctor -l someLog
> and perform a supsend/restart that reproduces this issue
Comment 3 David Edmundson 2020-09-18 15:01:25 UTC
My bad.

I meant:

kscreen-console monitor
Comment 4 Bug Janitor Service 2020-10-03 04:33:14 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 5 Bug Janitor Service 2020-10-18 04:33: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!