Bug 466484 - Lost 3rd monitor with Plasma 5.27.1
Summary: Lost 3rd monitor with Plasma 5.27.1
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.27.1
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-26 19:10 UTC by bginsburg
Modified: 2023-05-14 03:46 UTC (History)
2 users (show)

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


Attachments
kscreen-doctor -o after pluggin in 3rd monitor (4.88 KB, text/x-log)
2023-03-09 01:31 UTC, bginsburg
Details
This is the output of kscreen-doctor -o before monitors were plugged in (2.84 KB, text/x-log)
2023-03-09 01:37 UTC, bginsburg
Details
kscreen-doctor output before (2.65 KB, text/plain)
2023-04-13 21:56 UTC, kde
Details
kscreen-doctor output after (3.23 KB, text/plain)
2023-04-13 21:56 UTC, kde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bginsburg 2023-02-26 19:10:39 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
***


STEPS TO REPRODUCE
1. Log into KDE with 3rd monitor attached/Attach 3rd monitor while logged in
2. Open Display settings
3.

OBSERVED RESULT
 3rd monitor not present in Display screen configuration or in drop-down menu of available monitors.
3rd monitor either remains dark or flickers with mirror of second monitor display.

EXPECTED RESULT
3rd monitor should be visible and configurable in Settings
This was working in Plasma 5.26

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 6.1.13-1-lts
(available in About System)
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Graphics Platform X11
Using a USB-C hub to provide two additional monitor outputs
Comment 1 bginsburg 2023-02-26 19:13:26 UTC
Also tried Wayland Session and behavior is the same.
Comment 2 Nate Graham 2023-03-01 16:42:09 UTC
Can you paste the output of `kscreen-doctor -o` before plugging in the 3rd screen, and afterwards?

Also, when the 3rd screen is plugged in, can you run `kscreen-console bug` and paste the contents of the "EDID" sections for each detected screen? Thanks!
Comment 3 bginsburg 2023-03-09 01:31:09 UTC
Created attachment 157130 [details]
kscreen-doctor -o after pluggin in 3rd monitor

This is the output after plugging in 2nd and 3rd monitors.  Display settings shows both now, and both are checked as enabled, but they are not getting a signal.
Comment 4 bginsburg 2023-03-09 01:37:47 UTC
Created attachment 157131 [details]
This is the output of kscreen-doctor -o before monitors were plugged in

This is output after system reboot. Plugging in monitors after worked as expected.
This is a laptop and the system had been sleeping before the other attachment.
Comment 5 Nate Graham 2023-03-10 15:33:38 UTC
Thanks. The output shows four disabled DP screens in the "before" state. Are there actually 4 disabled DP screens? Do you have any docks or KVM switched or other display-related hardware plugged in?
Comment 6 Bug Janitor Service 2023-03-25 03:45:36 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 7 Bug Janitor Service 2023-04-09 03:45:39 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 8 kde 2023-04-13 21:56:33 UTC Comment hidden (spam)
Comment 9 kde 2023-04-13 21:56:59 UTC Comment hidden (spam)
Comment 10 kde 2023-04-13 22:00:02 UTC Comment hidden (spam)
Comment 11 kde 2023-04-13 22:19:50 UTC Comment hidden (spam)
Comment 12 kde 2023-04-13 22:23:53 UTC Comment hidden (spam)
Comment 13 Nate Graham 2023-04-14 18:00:45 UTC Comment hidden (spam)
Comment 14 Bug Janitor Service 2023-04-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 15 Bug Janitor Service 2023-05-14 03:46:00 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!