| Summary: | Display scale is reset on logout | ||
|---|---|---|---|
| Product: | [Plasma] KScreen | Reporter: | poperigby |
| Component: | common | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | florian, kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.25.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
qtdiag output
"kscreen-console bug" output after setting scale "kscreen-console bug" output after login Contents of ~/.local/share/kscreen |
||
|
Description
poperigby
2022-06-29 18:50:48 UTC
>when I log back in it appears to be at 100%
Please include output of "qtdiag" and your real screen resolution.
(In reply to David Edmundson from comment #1) > >when I log back in it appears to be at 100% > > Please include output of "qtdiag" and your real screen resolution. I've attached the output to qtdiag. My real screen resolution is 2256 x 1504. Created attachment 150281 [details]
qtdiag output
qtdiag ran under xwayland. That's rather unexpected. Screens: 1, High DPI scaling: inactive # 0 "XWAYLAND0" Depth: 24 Primary: yes Manufacturer: Model: Serial number: Geometry: 2256x1504+0+0 Available: 2256x1438+0+66 Physical size: 280x190 mm Refresh: 59.9259 Hz Power state: 0 Physical DPI: 204.651,201.061 Logical DPI: 96,96 Subpixel_None DevicePixelRatio: 1 Pixel density: 1 Primary orientation: 2 Orientation: 2 Native orientation: 0 OrientationUpdateMask: 0 It indeed shows us having the scale of 1. --- Next up can I have output of ` kscreen-console bug` after setting the value, and after login (In reply to David Edmundson from comment #4) > qtdiag ran under xwayland. That's rather unexpected. > > Screens: 1, High DPI scaling: inactive > # 0 "XWAYLAND0" Depth: 24 Primary: yes > Manufacturer: > Model: > Serial number: > Geometry: 2256x1504+0+0 Available: 2256x1438+0+66 > Physical size: 280x190 mm Refresh: 59.9259 Hz Power state: 0 > Physical DPI: 204.651,201.061 Logical DPI: 96,96 Subpixel_None > DevicePixelRatio: 1 Pixel density: 1 > Primary orientation: 2 Orientation: 2 Native orientation: 0 > OrientationUpdateMask: 0 > > It indeed shows us having the scale of 1. > > --- > > Next up can I have output of ` kscreen-console bug` after setting the value, > and after login Sure, I've uploaded the output of both. Created attachment 150297 [details]
"kscreen-console bug" output after setting scale
Created attachment 150298 [details]
"kscreen-console bug" output after login
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! (In reply to David Edmundson from comment #4) > qtdiag ran under xwayland. That's rather unexpected. > > Screens: 1, High DPI scaling: inactive > # 0 "XWAYLAND0" Depth: 24 Primary: yes > Manufacturer: > Model: > Serial number: > Geometry: 2256x1504+0+0 Available: 2256x1438+0+66 > Physical size: 280x190 mm Refresh: 59.9259 Hz Power state: 0 > Physical DPI: 204.651,201.061 Logical DPI: 96,96 Subpixel_None > DevicePixelRatio: 1 Pixel density: 1 > Primary orientation: 2 Orientation: 2 Native orientation: 0 > OrientationUpdateMask: 0 > > It indeed shows us having the scale of 1. > > --- > > Next up can I have output of ` kscreen-console bug` after setting the value, > and after login Hey, just wanted to update that I submitted the required information. Created attachment 152452 [details]
Contents of ~/.local/share/kscreen
I've uploaded the contents of ~/.local/share/kscreen, like you said.
What we're seeing is we have conflicting settings where we have some settings saved with: "For any display arrangement" set. Some with "For only this specific display arrangement". What gets loaded is quite poorly defined and the UX is even more ambiguous. Can you try wiping ~/.local/share/kscreen/outputs and confirm that fixes things? (In reply to David Edmundson from comment #11) > What we're seeing is we have conflicting settings where we have some > settings saved with: > "For any display arrangement" set. Some with "For only this specific > display arrangement". > > What gets loaded is quite poorly defined and the UX is even more ambiguous. > > Can you try wiping ~/.local/share/kscreen/outputs and confirm that fixes > things? That doesn't appear to fix it. I wiped ~/.local/share/kscreen/outputs, changed my scale to 125, and rebooted. When I logged back in, the scale was 100% again. It also seems like ~/.local/share/kscreen didn't repopulate the outputs directory. Not sure if that's intentional. 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! There were a lot of kscreen fixes in Plasma 5.27. Any chance you can upgrade to Plasma 5.27.5 to see if it's still an issue? Thanks! 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! Sorry for not replying. This has been fixed! |