Bug 1099900 - kscreen configuration on wayland not persistent
kscreen configuration on wayland not persistent
Status: NEW
: 1096815 (view as bug list)
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Workspace (Plasma)
Current
x86-64 Other
: P5 - None : Major (vote)
: ---
Assigned To: E-Mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-02 19:51 UTC by Miroslav Špehar
Modified: 2018-07-23 11:58 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
kscreen output in json format (15.47 KB, text/plain)
2018-07-02 20:13 UTC, Miroslav Špehar
Details
kscreen from config dir (510 bytes, application/octet-stream)
2018-07-02 20:13 UTC, Miroslav Špehar
Details
journal (298.73 KB, text/plain)
2018-07-02 20:14 UTC, Miroslav Špehar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Miroslav Špehar 2018-07-02 19:51:53 UTC
while on wayland, systemsettings5 won't save monitor setup.

my setup is 2 monitors, one standard dpi, the other one hidpi. they are in reversed order than settings shows by default, so

1. i change the order of monitors (left-right swap)
2. change scaling of hidpi monitor to 2

these settings are not persisted between reboots.
Comment 1 Miroslav Špehar 2018-07-02 20:13:18 UTC
Created attachment 775888 [details]
kscreen output in json format
Comment 2 Miroslav Špehar 2018-07-02 20:13:51 UTC
Created attachment 775889 [details]
kscreen from config dir
Comment 3 Miroslav Špehar 2018-07-02 20:14:16 UTC
Created attachment 775890 [details]
journal
Comment 4 Miroslav Špehar 2018-07-06 07:40:39 UTC
*** Bug 1096815 has been marked as a duplicate of this bug. ***
Comment 5 Miroslav Špehar 2018-07-06 07:41:22 UTC
reported upstream

https://bugs.kde.org/show_bug.cgi?id=396236
Comment 6 Deleted Name 2018-07-23 08:37:31 UTC
Rotation is not persistent too.

I have one monitor 90 rotated counterclockwise and it gets reset after reboot.

I don't think it is related to wayland as my journal doesn't show wayland starting (unlike that of the reporter). I have noticed this bug more than a year ago, so it is not something new.
Comment 7 Deleted Name 2018-07-23 09:54:21 UTC
More info found while looking for a workaround:

[~]: kscreen-doctor -o
Output: 99 DVI-I-1 enabled connected primary DVI Modes: 104:2560x1440@60*! 105:1920x1200@60 106:1920x1080@60 107:1600x1200@60 108:1280x1024@60 109:1280x960@60 110:1024x768@60 111:800x600@60 112:640x480@60 Geometry: 0,160 2560x1440
Output: 100 DVI-D-1 enabled connected  DVI Modes: 107:1600x1200@60*! 108:1280x1024@60 110:1024x768@60 111:800x600@60 112:640x480@60 113:720x400@70 Geometry: 2560,0 1200x1600
Output: 101 HDMI-1 disabled disconnected  HDMI Modes: Geometry: 0,0 0x0
Output: 102 DP-1 disabled disconnected  DisplayPort Modes: Geometry: 0,0 0x0
[~]: kscreen-doctor output.DVI-D-1.rotation.right
Unable to parse argumentsoutput.DVI-D-1.rotation.right

But kscreen-doctor should accept such argument:

https://cgit.kde.org/libkscreen.git/commit/?id=659d750b773b536d6836a01fb1486af75aafac48
Comment 8 Fabian Vogt 2018-07-23 11:34:29 UTC
(In reply to Name Deleted from comment #7)
> More info found while looking for a workaround:
> 
> [~]: kscreen-doctor -o
> Output: 99 DVI-I-1 enabled connected primary DVI Modes: 104:2560x1440@60*!
> 105:1920x1200@60 106:1920x1080@60 107:1600x1200@60 108:1280x1024@60
> 109:1280x960@60 110:1024x768@60 111:800x600@60 112:640x480@60 Geometry:
> 0,160 2560x1440
> Output: 100 DVI-D-1 enabled connected  DVI Modes: 107:1600x1200@60*!
> 108:1280x1024@60 110:1024x768@60 111:800x600@60 112:640x480@60
> 113:720x400@70 Geometry: 2560,0 1200x1600
> Output: 101 HDMI-1 disabled disconnected  HDMI Modes: Geometry: 0,0 0x0
> Output: 102 DP-1 disabled disconnected  DisplayPort Modes: Geometry: 0,0 0x0
> [~]: kscreen-doctor output.DVI-D-1.rotation.right
> Unable to parse argumentsoutput.DVI-D-1.rotation.right
> 
> But kscreen-doctor should accept such argument:
> 
> https://cgit.kde.org/libkscreen.git/commit/
> ?id=659d750b773b536d6836a01fb1486af75aafac48

Works fine here - what's the version of kscreen5 on your system?
I think this is unrelated to this bug report though.
Comment 9 Deleted Name 2018-07-23 11:37:51 UTC
[~]: rpm -q kscreen5
kscreen5-5.12.5-lp150.1.1.x86_64
Comment 10 Fabian Vogt 2018-07-23 11:39:51 UTC
(In reply to Name Deleted from comment #9)
> [~]: rpm -q kscreen5
> kscreen5-5.12.5-lp150.1.1.x86_64

Of course, the commit you linked is only part of kscreen >= 5.13, so not Leap 15.0.
Comment 11 Deleted Name 2018-07-23 11:43:10 UTC
Then:

> Works fine here

Is not fine for everyone else (at least one who uses Leap's packages).
Comment 12 Fabian Vogt 2018-07-23 11:53:20 UTC
(In reply to Name Deleted from comment #11)
> Then:
> 
> > Works fine here
> 
> Is not fine for everyone else (at least one who uses Leap's packages).

This bug got reported against Tumbleweed and you didn't state that you're using Leap 15.
Comment 13 Deleted Name 2018-07-23 11:58:29 UTC
Sorry, my mistake.