Bug 371417

Summary:	screens not (re-)actived after (un-)docking cycles of a notebook
Product:	[Plasma] KScreen	Reporter:	OlafLostViking <olaf.the.lost.viking>
Component:	common	Assignee:	Sebastian Kügler <sebas>
Status:	RESOLVED WORKSFORME
Severity:	grave	CC:	azrdev, nate, olaf.the.lost.viking
Priority:	NOR
Version:	5.8.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=359542
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	kscreen.log while the described problem happened

Description OlafLostViking 2016-10-21 14:50:20 UTC

As asked for in bug #359542 here a shorter summary of the problem mentioned there.

KScreen fails to (re-)enable displays after docking/sleep cycles.

Reproducible: Sometimes

Steps to Reproduce:
1. Put Notebook to sleep.
2. Undock from docking station A (internal screen + one external screen).
3. Dock into docking station B (two external screens).
4. Wake-up.

Actual Results:  
Internal display goes on, gets deactivated, external displays do not get even powered on. Undocking does not reactive the internal display. Open data/application states get lost.

Expected Results:  
Internal display should go off but the two external displays should also get activated.

DELL E6430 with a mobile nvidia chip.

Docking Station A has an horizontal Full-HD display on the DVI port. The internal 1600x900 display LVDS is used.

Docking Station B has an horizontal 2560x1440 display on the DP port and a vertical 2048x1152. The internal display cannot be used.

Comment 1 OlafLostViking 2016-10-21 14:52:56 UTC

Created attachment 101684 [details]
kscreen.log while the described problem happened

The failure should be around 20.10.2016 08:07.

Comment 2 Sebastian Kügler 2016-11-10 12:27:13 UTC

Thanks, much clearer now. Unfortunately, it's nothing I can test or reproduce, as my docking station and laptop can only handle one external monitor, and I don't use NVidia hardware either.

Comment 3 Nate Graham 2022-11-08 19:53:17 UTC

Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please see if you can reproduce the issue with Plasma 5.25 or 5.26?

If you can, please change the status to CONFIRMED when replying. Thanks a lot!

Comment 4 Bug Janitor Service 2022-11-23 05:14:17 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 2022-12-08 05:13:52 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!