Bug 447324 - Identification visualization for disabled display inappropriately shown on enabled display
Summary: Identification visualization for disabled display inappropriately shown on en...
Status: RESOLVED DUPLICATE of bug 447205
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kscreen (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-21 09:54 UTC by Pavel
Modified: 2022-11-12 15:11 UTC (History)
3 users (show)

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

Attachments
Wrong behavior (659.98 KB, image/png)
2021-12-21 09:54 UTC, Pavel 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel 2021-12-21 09:54:43 UTC 
Created attachment 144748 [details]
Wrong behavior

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. Login with plasma-wayland session
2. Click settings/display and monitor/identify


OBSERVED RESULT
Shows both monitor, even second is disabled
(better on images)
Notebook + 4K monitor

EXPECTED RESULT
Same results as plasma-x11
(on image should be visible only one monitor)

SOFTWARE/OS VERSIONS
Manjaro Linux x86_64 

Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-11-12 14:43:14 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.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 Nate Graham 2022-11-12 15:11:17 UTC 
*** This bug has been marked as a duplicate of bug 447205 ***