Bug 471262 - kscreen crashes after sleep
Summary: kscreen crashes after sleep
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: common (other bugs)
Version First Reported In: 5.27.5
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords: multiscreen
Depends on:
Blocks:
 
Reported: 2023-06-20 10:38 UTC by Raphael K
Modified: 2023-10-14 03:46 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Raphael K 2023-06-20 10:38:13 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

I have a laptop that is attacked to two monitors (1440p@75Hz), with only the external monitors being used when in this setup.

If the laptop goes to sleep and re-awakes one of the monitors suddenly has a lower resolution and refresh rate than before. This decrease starts at 1440p and goes from 1080p to 1050p eventually. I tried to use **kscreen-doctor** to investigate the issue but when trying to output the "broken" monitor's details **kscreen-doctor** always end with the core being dumped.

STEPS TO REPRODUCE
1. Attach two external displays
2. Let the laptop go to sleep
3. Wake the laptop up

OBSERVED RESULT

One of the external monitors has a lower resolution and refresh rate than its default.

EXPECTED RESULT

All external monitors use the setting 1440p@75Hz

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: endeavour OS
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
```
# kscreen-doctor output
kscreen-doctor -o
Output: 1 eDP-1 disabled connected priority 0 Panel Modes: 0:2880x1800@90*! 1:1600x1200@60 2:1280x1024@60 3:1024x768@60 4:2560x1600@60 5:1920x1200@60 6:1280x800@60 7:2880x1620@60 8:2560x1440@60 9:1920x1080@60 10:1600x900@60 11:1368x768@60 12:1280x720@60 Geometry: 0,0 1920x1200 Scale: 1.5 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic
Output: 2 DP-1 enabled connected priority 2 DisplayPort Modes: 0:1920x1080@60 1:1920x1080@60! 2:1920x1080@60 3:1920x1080@50 4:1680x1050@60* 5:1280x1024@75 6:1280x1024@60 7:1440x900@60 8:1280x960@60 9:1280x800@60 10:1152x864@75 11:1280x720@60 12:1280x720@60 13:1280x720@60 14:1280x720@50 15:1280x720@50 16:1440x576@50 17:1440x576@50 18:1024x768@75 19:1024x768@70 20:1024x768@60 21:1440x480@60 22:1440x480@60 23:1440x480@60 24:1440x480@60 25:832x624@75 26:800x600@75 27:800x600@72 28:800x600@60 29:800x600@56 30:720x576@50 31:720x576@50 32:720x576@50 33:720x480@60 34:720x480@60 35:720x480@60 36:720x480@60 37:720x480@60 38:640x480@75 39:640x480@67 40:640x480@60 41:640x480@60 42:640x480@60 43:720x400@70 Geometry: 0,0 1680x1050 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic
Output: 3 HDMI-A-1 enabled connected priority 1 HDMI Modes: 0:2560x1440@75*! 1:2560x1440@60 2:1920x1080@60 3:1920x1080@60 4:1920x1080@60 5:1920x1080@50 6:1680x1050@60 7:1280x1024@75 8:1280x1024@60 9:1440x900@60 10:1280x960@60 11:1280x800@60 12:1152x864@75 13:1280x720@60 14:1280x720@60 15:1280x720@60 16:1280x720@50 17:1280x720@50 18:1440x576@50 19:1440x576@50 20:1024x768@75 21:1024x768@70 22:1024x768@60 23:1440x480@60 24:1440x480@60 25:1440x480@60 26:1440x480@60 27:832x624@75 28:800x600@75 29:800x600@72 30:800x600@60 31:800x600@56 32:720x576@50 33:720x576@50 34:720x576@50 35:720x480@60 36:720x480@60 37:720x480@60 38:720x480@60 39:720x480@60 40:640x480@75 41:640x480@67 42:640x480@60 43:640x480@60 44:640x480@60 45:720x400@70 Geometry: 1680,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic
malloc_consolidate(): unaligned fastbin chunk detected
[1]    66238 IOT instruction (core dumped)  kscreen-doctor -o
```
Comment 1 Nate Graham 2023-09-14 21:33:01 UTC
Is this happening  on X11 or Wayland? If it's only one, can you try with the other?
Comment 2 Bug Janitor Service 2023-09-29 03:46: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 3 Bug Janitor Service 2023-10-14 03:46:08 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!