Bug 359161 - Screen refresh rate not saved or restored
Summary: Screen refresh rate not saved or restored
Status: RESOLVED FIXED
Alias: None
Product: KScreen
Classification: Plasma
Component: kcm (show other bugs)
Version: 5.10.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Kügler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-09 01:05 UTC by Bernie Innocenti
Modified: 2018-07-24 11:53 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernie Innocenti 2016-02-09 01:05:13 UTC
With my monitor / display card combination, the preferred mode has a 30Hz refresh rate (probably an unrelated bug).

If I go to systemsettings /  Display Configuration / Advanced, I can change this to 59.9Hz and then click Apply, the mode is correctly changed.

However:

1. After restarting the session, the mode is reset back to 30Hz
2. If I restart systemsettings, the Refresh rate is shown as "Auto"

Also reporting a minor UI issue:

3. Having to click Advanced Settings to reveal the screen refresh rate made the problem a bit harder to diagnose. I think the config UI should show a prominent warning that refresh rate is set unusually low. Users may just think "KDE is slow" when window animations are jerky and videos skip frames.


Reproducible: Always
Comment 1 milesrdz 2016-05-31 03:21:10 UTC
My monitor's refresh rate is not reapplied upon reboot either.
The correct refresh rate is selected but not applied.
Comment 2 NiO 2016-11-25 18:19:56 UTC
This might be related.. my refresh rate setting always gets reverted back to Auto

Demo:  http://i.imgur.com/MWwcCiZ.gif

Plasma 5.8.4
Frameworks 5.28.0
Comment 3 Sebastian Kügler 2016-11-28 16:00:48 UTC
Thanks for the report!

I've fixed this problem in the new KCM's code. It's a bit involved, so I can't easily backport these changes to the old one.
Comment 4 Sebastian Kügler 2016-11-28 16:02:12 UTC
To clarify, could you check with "xrandr -q" is the correct refresh rate (mode) gets applied? I think the problem is in loading the right values into the ui, not setting the correct refresh rate.
Comment 5 Bernie Innocenti 2016-11-28 18:09:18 UTC
Thanks. In which release will the fix first show up?
Comment 6 Sebastian Kügler 2016-11-28 21:14:27 UTC
Probably 5.10, but you haven't answered my question. :)
Comment 7 NiO 2016-11-28 21:25:48 UTC
I planned on testing that out when I get home from work if nobody else does.  I'm pretty sure it's just a UI bug.  Will update again in a couple hours
Comment 8 Sebastian Kügler 2016-11-28 21:38:27 UTC
Cool, thanks!
Comment 9 NiO 2016-11-28 23:27:43 UTC
OK so I have some results for ya.  Yes, changing the refresh rate from the monitor settings does indeed change the output from xrandr.. but something else happened when I ran "qdbus org.kde.KWin /KWin supportInformation"


@144hz:

adam@adam-pc:~$ xrandr -q
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
   2560x1440     59.95 + 144.00*  120.00    99.95    84.98    23.97  
   1024x768      60.00  
   800x600       60.32  
   640x480       59.94  
DP-1 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)




@120hz:


adam@adam-pc:~$ xrandr -q
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
   2560x1440     59.95 + 144.00   120.00*   99.95    84.98    23.97  
   1024x768      60.00  
   800x600       60.32  
   640x480       59.94  
DP-1 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)





Still @120hz, Screen0 reports 143.998hz:



adam@adam-pc:~$ qdbus org.kde.KWin /KWin supportInformation

KWin Support Information:
The following information should be used when requesting support on e.g. http://forum.kde.org.
It provides information about the currently running instance, which options are used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a paste bin service
like http://paste.kde.org instead of pasting into support threads.

==========================

Version
=======
KWin version: 5.8.4
Qt Version: 5.7.0
Qt compile version: 5.7.0
XCB compile version: 1.11.1

Operation Mode: X11 only

Build Options
=============
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_INPUT: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 11804000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==========
Plugin: org.kde.breeze
Theme: 
Blur: 0
onAllDesktopsAvailable: true
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 3
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Options
=======
focusPolicy: 0
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
placement: 6
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 1
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 30
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 30
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 31
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777251
showGeometryTip: false
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
inactiveTabsSkipTaskbar: false
autogroupSimilarWindows: false
autogroupInForeground: true
compositingMode: 1
useCompositing: true
compositingInitialized: true
hiddenPreviews: 1
glSmoothScale: 2
colorCorrected: false
xrenderSmoothScale: false
maxFpsInterval: 16666666
refreshRate: 0
vBlankTime: 6000000
glStrictBinding: false
glStrictBindingFollowsDriver: true
glCoreProfile: true
glPreferBufferSwap: 0
glPlatformInterface: 1
windowsBlockCompositing: true

Screen Edges
============
desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
=======
Multi-Head: no
Active screen follows mouse:  no
Number of Screens: 1

Screen 0:
---------
Name: DP-0
Geometry: 0,0,2560x1440
Refresh Rate: 143.998


Compositing
===========
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 970/PCIe/SSE2
OpenGL version string: 3.1.0 NVIDIA 370.28
OpenGL platform interface: GLX
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 370.28
GPU class: Unknown
OpenGL version: 3.1
GLSL version: 1.40
X server version: 1.18.4
Linux kernel version: 4.4
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used
Painting blocks for vertical retrace:  no

Loaded Effects:
---------------
zoom
slidingpopups
kwin4_effect_login
screenshot
kwin4_effect_windowaperture
minimizeanimation
kwin4_effect_translucency
desktopgrid
cubeslide
kwin4_effect_maximize
kwin4_effect_fade
kwin4_effect_morphingpopups
presentwindows
highlightwindow
kwin4_effect_dialogparent
blur
contrast
startupfeedback
screenedge
kscreen

Currently Active Effects:
-------------------------
blur
contrast

Effect Settings:
----------------
zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
enableFocusTracking: false
followFocus: true
focusDelay: 350
moveFactor: 20
targetZoom: 1

slidingpopups:
fadeInTime: 75
fadeOutTime: 125

kwin4_effect_login:

screenshot:

kwin4_effect_windowaperture:

minimizeanimation:

kwin4_effect_translucency:

desktopgrid:
zoomDuration: 150
border: 10
desktopNameAlignment: 0
layoutMode: 0
customLayoutRows: 2
usePresentWindows: true

cubeslide:
rotationDuration: 250
dontSlidePanels: true
dontSlideStickyWindows: false
usePagerLayout: true
useWindowMoving: false

kwin4_effect_maximize:

kwin4_effect_fade:

kwin4_effect_morphingpopups:

presentwindows:
layoutMode: 0
showCaptions: true
showIcons: true
doNotCloseWindows: false
ignoreMinimized: false
accuracy: 20
fillGaps: true
fadeDuration: 75
showPanel: false
leftButtonWindow: 1
rightButtonWindow: 2
middleButtonWindow: 0
leftButtonDesktop: 2
middleButtonDesktop: 0
rightButtonDesktop: 0

highlightwindow:

kwin4_effect_dialogparent:

blur:
blurRadius: 12
cacheTexture: true

contrast:

startupfeedback:
type: 1

screenedge:

kscreen:
Comment 10 NiO 2016-11-28 23:29:56 UTC
That may just be what's being read from the monitor itself, rather than what is configured in KDE.. I'm not sure but I figured I would mention it just in case.
Comment 11 Sebastian Kügler 2016-11-28 23:31:37 UTC
Cool, thanks! So yes, it's a ui bug.
Comment 12 Bernie Innocenti 2017-06-06 04:42:32 UTC
Still present in 5.10.0.
Comment 13 Frederik Gladhorn 2018-07-24 11:53:19 UTC
Should be fixed in 5.14. https://phabricator.kde.org/D14328