| Summary: | Win+P still assumes the monitors position wrongly, ignoring the Display Configuration. | ||
|---|---|---|---|
| Product: | [Plasma] KScreen | Reporter: | Sin Jeong-hun <typingcat> |
| Component: | common | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | kde, luca.de.martini, micheleoro.nobili, rasmus.oltrogge |
| Priority: | NOR | ||
| Version First Reported In: | 5.24.2 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Sin Jeong-hun
2018-11-30 17:05:18 UTC
This is still broken in plasma 5.22.5 Also, the problem is not only limited to the display position, but the primary display is also forgotten! The two displays are Display port and HDMI and the HDMI one is always set as primary in my case. This is really annoying and broken since forever Still present in 5.24.2. It is really annoying. Luckly with a fast search on reddit you can see that everyone is overcoming the issue setting a personal script with help from arandr and/or xrandr. But really the solution at the moment is to disable kscreen and setting up a personal script. A fix to kscreen would be welcome. To add some information on the issue: I have display A (HDMI-1) and B (HDMI-0). Both connected with HDMI. A is my main monitor, B is my television. B is always connected but I only enable it (extend) when seeing something. Whenever I use kscreen (default Meta+P) to extend (to the right*) the primary monitor change to display B. I don't want that. A should always be my Primary. So I open the display configuration, set everything right (primary/position/etc..). Then if I disable the B screen (Meta+P and select external monitor) and then I want to re-enable the B monitor (Meta+P and extend to the right) I am at the starting point again. Like if kscreen never encountered the B monitor before. In ~/.local/share/kscreen/outputs I see that there two files (file names are something like "e51393b4fa33a19dd6987077f0efcdcf") that store the information of my two displays. So kscreen is able to recognize them. In ~/.local/share/kscreen/ there are two files with the configuration for single monitor and extended monitor. When I correct the primary monitor in the display configuration the file (the dual monitor one) is updated and correctly says which one is the primary. But then it seems that if I revert to single monitor and re enable the extended layout kscreen simply delete all the informations and recreate the file from zero. I see that when checking the option " For only this display arrangement " in the display configuration a new file is created inside ~/.local/share/kscreen/control/configs. This file has the same name of the file in ~/.local/share/kscreen/ that store my current dual monitor configuration, but a lot less informations. Is it possible that it should save the current configuration to reuse it later when I connect/change active displays? For sure in that file the "primary" setting is not saved. I tried to set it myself but that didn't work too. It seems to be completely ignored. ---------------------------------------------------------------------------------------------------- *BTW: the extend to the left and to the right seems only useful when connecting for the first time to a display for the first time. Is it really that useful? Chance are that on the first time you will have to enter display configuration to set resolution anyway. And after the first time if kscreen works correctly it should remember the display and extend correctly. I believe I have fixed that with my recent patch. It will now extend from the primary screen, and not change primary screeen. As far as I know the fix will be in 5.27.. Reopen if this isnt a sufficient solution. Very similar to 376341 and 396071. Anyhow, I say, this should even be put into the #15-minute-initiative |