Bug 472732 - OSD and applet: "Switch to laptop screen" action causes external screen to become disabled as expected for a moment, then it turns on again
Summary: OSD and applet: "Switch to laptop screen" action causes external screen to be...
Status: RESOLVED DUPLICATE of bug 466208
Alias: None
Product: KScreen
Classification: Plasma
Component: OSD and Plasma applet (show other bugs)
Version: 5.27.5
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords: multiscreen, wayland
Depends on:
Blocks:
 
Reported: 2023-07-28 08:30 UTC by cuijq
Modified: 2024-02-12 18:07 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Select the laptop screen output mode. (73.87 KB, image/jpeg)
2023-07-28 08:30 UTC, cuijq
Details
The System Tray widget (348.90 KB, image/jpeg)
2023-08-02 09:03 UTC, cuijq
Details
Record the problem (3.57 MB, video/mp4)
2023-08-02 09:21 UTC, cuijq
Details
kscreen-doctor recording part 1 (3.91 MB, application/gzip)
2023-08-04 06:43 UTC, cuijq
Details
kscreen-doctor recording part 2 (3.91 MB, application/octet-stream)
2023-08-04 06:46 UTC, cuijq
Details
kscreen-doctor recording part 3 (3.91 MB, application/octet-stream)
2023-08-04 06:48 UTC, cuijq
Details
kscreen-doctor recording part 4 (3.83 MB, application/octet-stream)
2023-08-04 06:50 UTC, cuijq
Details

Note You need to log in before you can comment on or make changes to this bug.
Description cuijq 2023-07-28 08:30:56 UTC
Created attachment 160578 [details]
Select the laptop screen output mode.

SUMMARY:
Win + P opens the multi -screen management window. The external screen mode is selected from unified output to the laptop screen. After 5-10 seconds after switching, the external screen mode will also jump to the unified output mode, and the laptop screen mode is not available.

STEPS TO REPRODUCE
1. Use win + p keyboard to open the setting window.
2. Select the laptop screen output mode.
OBSERVED RESULT
After 5-10 seconds after switching, the external screen mode will also jump to the unified output mode, and the laptop screen mode is not available.

EXPECTED RESULT
The external screen does not output, only the laptop screen output.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian 12
(available in About System)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.10
Kerne Version: 6.1.24
Graphics Platform: wayland
ADDITIONAL INFORMATION
Comment 1 cuijq 2023-07-28 08:35:20 UTC
This problem has always existed, I hope to get your support, thank you
Comment 2 Nate Graham 2023-07-28 21:00:54 UTC
So to confirm, you started what a laptop and an external screen in Unified mode, and then you changed to "Switch to Laptop screen" mode, and then after 5-10 seconds, it switched back to Unified mode?

Also, does the same thing happen when you use the widget in the System Tray to do this?
Comment 3 cuijq 2023-07-29 03:03:57 UTC
Hello, I am using Lenovo's ThinkBook 14G2 laptop, which is connected to an external display screen of an unknown model through HDMI. There are 5 modes for expanding the screen:
"External screen display only", "Notebook screen display only", "Unified output display", "External screen expands left", "External screen expands right".

Only the 'laptop screen display only' mode is invalid. After selecting this mode, it will be randomly set to one of the other four modes. You can try to see if there is a problem.

When I select -->graphics card and display screen -->disable the expansion screen from the UI interface of the system settings, it only takes effect through the "laptop screen display", but I call "kscreen_osd_service" through the shortcut key [win+P/F7]Choosing the 'laptop screen display only' mode for service is invalid, as it will be randomly set to one of the other four modes.

The above is my description and I hope it will be helpful for you to understand this issue.
Comment 4 Nate Graham 2023-08-01 21:39:54 UTC
Thanks. And can you confirm that the same problem happens when you access this feature from the System Tray widget, and not the OSD?
Comment 5 cuijq 2023-08-02 09:03:45 UTC
Created attachment 160678 [details]
The System Tray widget
Comment 6 cuijq 2023-08-02 09:21:28 UTC
Created attachment 160679 [details]
Record the problem
Comment 7 cuijq 2023-08-02 09:23:11 UTC
Hi,
I confirm that the same problem happens when I access this feature from the System Tray widget,you can view the attachment pictures and videos I uploaded to confirm that the problem still exists. I hope it will help you.
Comment 8 Nate Graham 2023-08-02 15:47:17 UTC
Thanks, the screen recording is helpful. This might be a KWin issue rather than a KScreen issue.
Comment 9 Zamundaaa 2023-08-02 16:05:23 UTC
What happens if you execute
kscreen-doctor output.2.disable output.1.enable
instead of using the GUI?
Comment 10 cuijq 2023-08-03 06:26:37 UTC
(In reply to Zamundaaa from comment #9)
> What happens if you execute
> kscreen-doctor output.2.disable output.1.enable
> instead of using the GUI?

Hi,
I use the Kcreen-Doctor tool to control the external screen and find the following two phenomena:

1. Use the command "Kcreen-Doctor output.2.disable output.1.enable". At this time, switch to "Switch to Laptop Screen" mode, Then use "OSD" to switch the laptop mode and other modes.

2. Use the command "Kcreen-Doctor output.2.enable output.nable", At this time,both screens are displayed normally, but the laptop screen mode cannot be switched, and a phenomenon like attachment video appears.
Comment 11 Nate Graham 2023-08-03 15:24:48 UTC
Can you attach another screen recording of what happens when you run `kscreen-doctor output.2.disable output.1.enable`?
Comment 12 cuijq 2023-08-04 06:43:50 UTC
Created attachment 160723 [details]
kscreen-doctor recording part 1
Comment 13 cuijq 2023-08-04 06:46:28 UTC
Created attachment 160724 [details]
kscreen-doctor recording part 2
Comment 14 cuijq 2023-08-04 06:48:41 UTC
Created attachment 160725 [details]
kscreen-doctor recording part 3
Comment 15 cuijq 2023-08-04 06:50:57 UTC
Created attachment 160726 [details]
kscreen-doctor recording part 4
Comment 16 cuijq 2023-08-04 07:00:13 UTC
(In reply to Nate Graham from comment #11)
> Can you attach another screen recording of what happens when you run
> `kscreen-doctor output.2.disable output.1.enable`?

Hi,
I have recorded a video of the problem before, but it is greater than the support size of the attachment, so I have not uploaded it. Now I will  split compressed video and upload it. You can restore the video through the following command to view the phenomenon of the problem. I hope it will be helpful to you!
cmd :
cat video_0804_part_a* | tar -xvzf -
result:
0803_video.mp4
Comment 17 Nate Graham 2023-08-07 18:05:22 UTC
That video isn't working for me. Can you upload it as a single file with more compression so it fits under the file size limit, or else upload it elsewhere and paste a link to it?
Comment 18 cuijq 2023-08-08 02:09:35 UTC
(In reply to Nate Graham from comment #17)
> That video isn't working for me. Can you upload it as a single file with
> more compression so it fits under the file size limit, or else upload it
> elsewhere and paste a link to it?

Hi,
I have uploaded the video to my github ,Can you download it through as follow link ,https://github.com/jqcui1999/src_public/blob/main/0803_video.mp4.
Comment 19 Nate Graham 2023-08-09 18:30:16 UTC
Thanks. It looks like the KScreen command works, so the problem is that the action in the OSD and applet are failing. Another casualty of following a different codepath.
Comment 20 cuijq 2023-08-10 02:52:32 UTC
(In reply to Nate Graham from comment #19)
> Thanks. It looks like the KScreen command works, so the problem is that the
> action in the OSD and applet are failing. Another casualty of following a
> different codepath.

Hi,
I think so, and it is the difference between the X11 and Wayland protocols, because the problem only appears on Wayland, It seems that the code needs to be checked, but I don’t know much about Kwin and hope to get your help.
Thanks!
Comment 21 cuijq 2023-09-19 01:48:10 UTC
Hi, 
Do you have any progress on this issue?
I want to know if this problem will be supported and solved by kde?
thanks!
Comment 22 Zamundaaa 2024-02-12 18:07:44 UTC
Yes, this will be fixed in Plasma 6.0

*** This bug has been marked as a duplicate of bug 466208 ***