Bug 406703 - VSync setting does not work after reboot
Summary: VSync setting does not work after reboot
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 5.19.5
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Andrei Rybak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-20 11:54 UTC by Andrei Rybak
Modified: 2021-09-24 23:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
qdbus org.kde.KWin /KWin supportInformation output before applying workaround (3.44 KB, text/plain)
2019-05-05 15:46 UTC, Andrei Rybak
Details
qdbus org.kde.KWin /KWin supportInformation output after applying workaround (5.53 KB, text/plain)
2019-05-05 15:48 UTC, Andrei Rybak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrei Rybak 2019-04-20 11:54:35 UTC
SUMMARY
"Full screen repaints" is not honored after reboot.

STEPS TO REPRODUCE
1. Open "System Settings > Display and Monitor > Compositor"
2. Set "Tearing prevention" to "Full screen repaints"
3. Reboot the PC.

OBSERVED RESULT
Windows visibly tear.

EXPECTED RESULT
"Full screen repaints" prevents tearing.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 18.04
(available in About System)
KDE Plasma Version: 5.12.7
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION
Workaround: go through steps 1-2 again, and tearing stops.
Comment 1 Vlad Zahorodnii 2019-04-21 12:51:49 UTC
Please post output of `qdbus org.kde.KWin /KWin supportInformation` before and after applying the workaround.

Also, out of curiosity, why do you want full screen repaints? :-)
Comment 2 Andrei Rybak 2019-05-04 20:41:56 UTC
> Also, out of curiosity, why do you want full screen repaints? :-)

Because without this setting, the windows tearing hurts my eyes.

> Please post output of `qdbus org.kde.KWin /KWin supportInformation` before and after applying the workaround.

I'll try to get this next time I reboot.
Comment 3 Andrei Rybak 2019-05-05 15:46:57 UTC
Created attachment 119848 [details]
qdbus org.kde.KWin /KWin supportInformation output before applying workaround
Comment 4 Andrei Rybak 2019-05-05 15:48:36 UTC
Created attachment 119850 [details]
qdbus org.kde.KWin /KWin supportInformation output after applying workaround

Added two attachments. Output of qdbus before and after applying workaround.
Comment 5 Vlad Zahorodnii 2019-05-06 07:32:12 UTC
Hmm, looks like compositing is not enabled by default.

If you enable compositing as well set tearing prevention back to "Automatic", does screen tearing occur?
Comment 6 Bug Janitor Service 2019-05-21 04:33:08 UTC
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!
Comment 7 Andrei Rybak 2019-05-21 22:29:48 UTC
> If you enable compositing as well set tearing prevention back to "Automatic", does screen tearing occur?

With the "Automatic" settings, the screen tearing does not occur. Thank you for fixing my setup — turns out I didn't actually need "Full screen repaints".

Off-topic:
It would seem that the *UX* for checkbox "Enable compositor on startup" could be improved.  It was not clear at all to me, that all the settings below this checkbox depend on it being turned on. I would have expected for this checkbox to get selected automatically when you change anything else on that screen. Especially since "compositor" actually turns itself on automatically when you touch these settings (as logs in the comment above have shown). Another possible approach would be to show a big warning at the bottom of the dialog (near "Apply" button):

> The settings will be reset on restart, if you don't check the checkbox "Enable compositor on startup".
Comment 8 Andrei Rybak 2020-09-13 16:31:35 UTC
Setting "Enable compositor on startup" still breaks sometimes in 5.19.5

Operating System: KDE neon 5.19
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
Kernel Version: 5.3.0-51-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Comment 9 Andrei Rybak 2021-09-24 23:33:16 UTC
Nowadays, in KDE Plasma Version 5.22.5, I don't see such tearing caused by V-sync breaking, so it's time to close this ticket.