419421 2020-03-30 15:34:02 +0000 QML timers go too fast with multi-threaded render loop when using any high refresh rate screens on X11 when using FOSS amdgpu drivers 2024-10-01 17:11:33 +0000 1 1 4 Plasma plasmashell general 5.19.5 Kubuntu Linux CLOSED FIXED https://bugs.kde.org/show_bug.cgi?id=446637 https://bugs.kde.org/show_bug.cgi?id=470365 https://bugs.kde.org/show_bug.cgi?id=493909 https://bugs.kde.org/show_bug.cgi?id=492478 VHI normal 1.0 0 nucrap kde angad.tendulkar cabanur chriswhy dolphin-bugs-null ekurzinger gabecodes hugs kde kitt3120 kya_cryptsetup lars.luis makosol marcelhentschel580 nate nicolas.fella null plasma-bugs-null postix pqwoerituytrueiwoq sergio temp02 uwu yaroslav4167 https://invent.kde.org/frameworks/kdeclarative/-/commit/66c5bb0efa6ac2a9a7bef8a4776150fdaf129353 6.0 0 oldest_to_newest 1919012 0 nucrap 2020-03-30 15:34:02 +0000 I have recently set to open folders/files by double clicking instead of single click, in the plasma settings. While it works fine within dolphin, I cannot open any files or folder on my desktop. It is broken. 1919013 1 nucrap 2020-03-30 15:35:21 +0000 Steps to repro: 1. Set settings to double click in plasma settings 2. Try to open a folder/file by double clicking, which is on the desktop. 1919047 2 nate 2020-03-30 19:47:53 +0000 Works for me. What Qt version do you have installed? Qt has broken this before. 1919048 3 nate 2020-03-30 19:48:22 +0000 (stub) 1919092 4 nucrap 2020-03-31 00:28:02 +0000 Yeah it started working a while ago session, but after restarting the system it stopped working again. My Qt is v5.14.1 1919094 5 nucrap 2020-03-31 00:28:30 +0000 *in one user session 1919181 6 nate 2020-03-31 16:39:45 +0000 Weird. I've also got Qt 5.14.1 and double-click works fine for me with Desktop icons. 1922379 7 nate 2020-04-15 00:45:50 +0000 Still working for me. Is this still broken for you? 1929185 8 cfeck 2020-05-12 12:19:54 +0000 If you can provide the information requested in comment 7, please add it. Please also try with a freshly created user account to rule out configuration issues. 1932888 9 bug-janitor 2020-05-27 04:33:12 +0000 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! 1936924 10 bug-janitor 2020-06-14 04:33:21 +0000 This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! 1942575 11 nucrap 2020-07-09 03:35:54 +0000 Hey sorry for the late answer. Tbh I have kinda given up reporting bugs related to plasma, but here we go. Yes the bug is still occuring to me. I have tried your suggestion of adding a new user. I did it the GUI way and encountered at least 3 plasma bugs again but who cares (last time I tried out wayland it completely destroyed my regular plasma session, so I have basically given up on experimenting). Anyways on a new session I cannot reproduce the bug. However I have only tried it once. As I said the issue is intermittend for me - meaning sometimes it just works, but other times it just doesn't. So not sure what to make of this, if you want any logs, I can provide it, however I am not going to reset my whole user session or anything comparable. I have a hard time avoiding bugs in plasma already, yet reconfiguring my session. 1994696 12 yaroslav4167 2021-01-15 15:13:00 +0000 I have same bug. I found a relationship - if any section is selected in the application launch menu except for the favorites, for example (Computer / Applications / Exit, etc.), then links and folders on the desktop do not open. If you select favorites in the menu, then everything works fine. Versions: Kubuntu 20.10 KDE Plasma: 5.19.5 KDE Frameworks: 5.74.0 Qt: 5.14.2 Core: 5.8.38-generic 1994756 13 nate 2021-01-15 18:46:13 +0000 Hmm, I still can't reproduce that that. If I open kickoff and then double-click on a desktop file or folder while it's still open, it works no matter which page is open. 1994761 14 yaroslav4167 2021-01-15 19:25:34 +0000 I have 240hz monitor. if i set 60hz mode all works fine. But if i set 240hz - desktop elements need to be clicked very quickly. Also the monitor mode affects the hold time of the notifications. (in the settings, 20 seconds are crushed, and the notification itself actually disappears in 5-7 seconds). In dolphin and other applications all works good. 1994762 15 nate 2021-01-15 19:32:06 +0000 Aha! That seems very relevant. Perhaps QML Timer objects aren't scaling by the refresh rate. That would be pretty sucky. I don't have any higher-than-average refresh rate screens to test, sadly. 1994764 16 yaroslav4167 2021-01-15 19:40:57 +0000 Oh.. Okay. I will wait and try to find some solution =/ 1994766 17 nate 2021-01-15 19:43:55 +0000 Found someone with a 144hz screen two graciously tested this, and he said it was working for him. How exactly did you set it the screen to 240hz mode? Just using the Display Configuration page in System Settings, or some command line tool, or something else? Also, Philip P, do you also have a high refresh rate screen? 1994774 18 nate 2021-01-15 20:01:53 +0000 Oh and also what GPU are you folks using? 1994777 19 yaroslav4167 2021-01-15 20:12:33 +0000 I set mode in system configuration. And modify two files: in /.config/kwinrc in section [Compositing] i add parameter MaxFPS=240 in /etc/environment i added to the end of the file: LUTTER_DEFAULT_FPS=240 __GL_SYNC_DISPLAY_DEVICE=DP-2 without this modifications testufo.com displayed 60 Hz and the monitor continued to work in 60 Hz mode. If i removed my modifications desktop-elements you also need to click very quickly. I have a GPU: GTX 1060 3GB Driver: nvidia-driver-450 (proprietary) 1994778 20 nate 2021-01-15 20:14:20 +0000 Thanks for the info! 1994787 21 yaroslav4167 2021-01-15 20:58:50 +0000 And yet - I have 2 monitors. second monitor (DVI-D) 60Hz. I tried to disable it and after reboot everything started working properly. But I need my second monitor. :/ (With the condition that the first will be 240 Hz) offtop: I would like to be able to set 265Hz, but I don't know how to do it =) 1994789 22 nate 2021-01-15 21:03:09 +0000 Ahh, so this is caused by your workaround for us not supporting mixed refresh rates on X11. :/ We just merged some big changes to support this on Wayland in Plasma 5.21. Maybe you can switch to Wayland and use that eventually. You're still using regular KWin, right? Not one of the forks? I wonder if it could actually be a bug in the proprietary Nvidia driver... We've had issues before where it caused timers and animations to go too fast. 1994809 23 yaroslav4167 2021-01-15 21:32:42 +0000 I tried a lot of things to solve my frequency problems. I just recently switched to Linux and in particular KDE, so I don't even know how to switch this X11 to Wayland =) kwin --v showed (kwin 5.19.5) echo $XDG_SESSION_TYPE showed (x11) for now, I'll try to test it with another video driver. 1994825 24 yaroslav4167 2021-01-15 21:54:06 +0000 With the "X.Org server - Nouveau dusplay driver" I have a limit of 60 fps on both monitors and all elements of the desktop can be opened with a double click. 1994831 25 nate 2021-01-15 22:02:53 +0000 I'm starting to lean towards the Nvidia driver being at fault here. :) 1995332 26 nucrap 2021-01-16 06:16:00 +0000 Hey looks like this finally blew up a little :D Im also on a 240hz(DP)<->60hz(hdmi) setup. AMD RX470 graphics card here, with open drivers. I did not not modify an config files though, I was able to simply set the 240hz from the Plasma Settings. Same issue with the notifications (I never knew what the heck is wrong with then lol). The progress bar within notifications is also often not working correctly.. but that might also be a different bug :p 1995459 27 yaroslav4167 2021-01-16 14:51:47 +0000 In my settings, too, 240 was set, but in the browser/games it was still 60. I had to look for an alternative solution. With the open driver, everything worked for me because all the monitors started working in 60Hz mode again. (although in the settings the first one is set to 240Hz) apparently because everything is synchronized on the monitor in DVE-D-0 (60Hz) 1995464 28 nate 2021-01-16 15:08:06 +0000 Moving to KWin for now; the developers there should be able to triage this further. 1995519 29 kde 2021-01-16 17:37:18 +0000 I am extremely lost as to what this bug is about. Comment #1 is about folderview The title is about QML Timer, which is /entirely/ client side. >Perhaps QML Timer objects aren't scaling by the refresh rate. That would be pretty sucky. Why would a timer be scaled? Can someone confirm a clear summary of what is known. 1995526 30 yaroslav4167 2021-01-16 18:01:25 +0000 I just found two problems: 1. Files and folders don`t open by double click. But.. This problem don`t work if Comment 12. Or i set 60Hz mode on my DP-1 monitor. 2. Notifications hide faster if monitor mode > 60-120hz. 1995535 31 134944 kde 2021-01-16 18:58:31 +0000 Created attachment 134944 test case 1995536 32 kde 2021-01-16 19:01:11 +0000 Can you download the above and run "qmlscene test.qml" It's a timer, a double click, and an animation. I'm somewhat confused how there could be a link, and debugging with a whole plasma is an uphill battle as it has too much noise. Qt's Timer driven from the frame rate. QAnimationDriver is, but they serve different purposes. We have seen issues with QAnimationDriver getting confused. Running "kcmshell5 qtquicksettings" and selecting the basic render loop can suppress that 1995561 33 yaroslav4167 2021-01-16 20:21:11 +0000 Test worked properly. In "kcmshell5 qtquicksettings" i set "simple" render loop in the list was (automatic simple and multi-threaded), restart PC - and everything start working properly! =) Thank you! 1995841 34 vlad.zahorodnii 2021-01-18 07:46:01 +0000 (sorry for the noise, I didn't see that the bug report was already moved back to plasma) 1996181 35 nate 2021-01-19 16:56:24 +0000 RESOLVED WAITINGFORINFO isn't a status that makes sense; re-opening. :) It seems like a workaround has been found, which hopefully helps to isolate the problem itself. It seems like the automatic or multi-threaded render loop settings are provoking this issue? 1996183 36 yaroslav4167 2021-01-19 17:02:45 +0000 Yes. automatic and Multi-threaded methods include this problem. 1996243 37 kde 2021-01-19 22:58:39 +0000 >Test worked properly. Including the spinning rectangle on the right? If you run plasmashell --replace does the issue also go away? 1996283 38 chriswhy 2021-01-20 04:41:24 +0000 I've also experienced the issue of double-clicking items on the desktop not working most of the time. Often I'd need to triple-click or just try again. My display is 144 Hz. With it set to 60 Hz mode, the issue wouldn't crop up. I tried running the test, and that seemed to work fine. When I changed that setting Yaroslav mentioned to Basic (choices for me were Automatic, Basic, Threaded) the problem went away immediately. 1996285 39 nate 2021-01-20 04:57:56 +0000 Does the same thing happen where notifications time out too fast with 144Hz? 1996314 40 yaroslav4167 2021-01-20 09:23:52 +0000 > Including the spinning rectangle on the right? Yes. One rotate in one second. (In all rendering modes) > If you run plasmashell --replace does the issue also go away? Yes problem going away. (I set automatic rendering method, restart PC and executed plasmashell --replace) 2008754 41 nate 2021-03-04 20:53:24 +0000 *** Bug 428978 has been marked as a duplicate of this bug. *** 2016477 42 nate 2021-03-18 14:51:21 +0000 *** Bug 403272 has been marked as a duplicate of this bug. *** 2023248 43 nate 2021-04-07 17:33:30 +0000 *** Bug 435469 has been marked as a duplicate of this bug. *** 2023325 44 nate 2021-04-07 19:43:20 +0000 Erik, could I prevail upon you to take a look at this? Thanks! 2023692 45 nate 2021-04-09 02:31:29 +0000 *** Bug 435508 has been marked as a duplicate of this bug. *** 2031746 46 sergio 2021-05-11 08:21:56 +0000 It's curious. When I cannot do (double) click to open the files and folders on my desktop, if I open Kickoff menu and then close it by clicking on the desktop, it already lets me open files and folders on the desktop by double clicking until after a while it returns to pass and I have to do the same. Is it known if there is any progress on this bug? Thanks. 2038557 47 sergio 2021-06-08 15:27:59 +0000 (In reply to Nate Graham from comment #45) > *** Bug 435508 has been marked as a duplicate of this bug. *** I have updated to KDE 5.22. Now i can to do double click on my desktop files and open it. I think that this bug is fixed. 2038558 48 nate 2021-06-08 15:29:18 +0000 Oh wow, that's nice. Can any other Nvidia users with high refresh rate screens confirm? 2038564 49 sergio 2021-06-08 15:45:36 +0000 (In reply to Nate Graham from comment #48) > Oh wow, that's nice. Can any other Nvidia users with high refresh rate > screens confirm? Sorry Nate. I don't know what happened but this fail again. Now i can't open my desktop files. 2038671 50 null 2021-06-08 19:42:01 +0000 Hello, No, the bug is not resolved. I've a nvidia card. Sometimes if I switch one of the screens back to 60hz I can open the desktop items, other times, even when I switch back to 60hz, it doesn't open. 2038778 51 yaroslav4167 2021-06-08 22:40:14 +0000 On KDE 5.22.0 (Neon) bug still working. Desktop icons needs clicked very fast to open and notifications after showing quickly hidden. The proposed temporary solution with the basic render loop (kcmshell5 qtquicksettings) solves these problems. 2041497 52 nate 2021-06-16 20:47:08 +0000 *** Bug 438718 has been marked as a duplicate of this bug. *** 2056780 53 nate 2021-08-27 20:52:25 +0000 Would be fixed by https://invent.kde.org/frameworks/kdeclarative/-/merge_requests/71 2056946 54 yaroslav4167 2021-08-28 18:38:38 +0000 For me, the problem is solved. 2056953 55 nate 2021-08-28 19:27:19 +0000 ...When you apply that merge request or switch to the Basic render loop? 2057060 56 yaroslav4167 2021-08-29 12:07:57 +0000 I set automatic render loop, and use KDE Neon (KDE plasma 5.22.4, KDE Frameworks 5.86.0, Qt 5.15.3). 2057808 57 nate 2021-08-31 20:15:29 +0000 Fixed by David Redondo in Plasma 5.23 with https://invent.kde.org/frameworks/kdeclarative/-/commit/66c5bb0efa6ac2a9a7bef8a4776150fdaf129353, which makes Plasma use the single-threaded render loop by default for NVIDIA users. 2057841 58 kde 2021-08-31 22:55:50 +0000 That patch will make absolutely no difference for users here. 2057846 59 nate 2021-08-31 23:32:06 +0000 But using the basic render loop works around the issue here. Isn't that what that patch does? 2057848 60 kde 2021-08-31 23:39:08 +0000 There's an if (QGuiApplication::platformName() == QLatin1String("wayland")) { 2057850 61 nate 2021-08-31 23:56:57 +0000 Oh. Maybe we should consider doing it on X11 too... 2057865 62 bug-janitor 2021-09-01 03:08:12 +0000 A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kdeclarative/-/merge_requests/75 2083667 63 nicolas.fella 2021-12-07 21:14:06 +0000 https://bugs.kde.org/show_bug.cgi?id=446637 describes a probably related issue, but with an AMD GPU 2084634 64 pqwoerituytrueiwoq 2021-12-11 22:23:07 +0000 Bug 446637 also shows up with integrated Intel GPUs (i3-2100 / HD 2000) 2092361 65 nate 2022-01-12 00:34:40 +0000 *** Bug 447625 has been marked as a duplicate of this bug. *** 2138875 66 nate 2022-07-13 18:55:31 +0000 *** Bug 456504 has been marked as a duplicate of this bug. *** 2159487 67 nate 2022-10-09 23:46:43 +0000 *** Bug 460012 has been marked as a duplicate of this bug. *** 2218111 68 kde 2023-03-24 00:03:01 +0000 Qt 6.4 has auto detection of this and falls back to a software timer 2218135 69 nucrap 2023-03-24 07:48:17 +0000 I am not sure who changed the title of this bug report, but I am the original reporter of this bug and I have never used an NVIDIA graphics card... As I have pointed out earlier I am on a RX470. I will test again once Plasma is on Qt6. 2218166 70 postix 2023-03-24 12:11:44 +0000 (In reply to Philip P. from comment #69) > I am not sure who changed the title of this bug report, but I am the > original reporter of this bug and I have never used an NVIDIA graphics > card... You can click on the "History" link [1] next to modify on the top of this page to see when and by whom something was changed. In this case it was Nate who came to the conclusion that it'd be NVIDIA's fault (which always a good first guess :P ), but basically it anyone registered can change the title. [1] https://bugs.kde.org/show_activity.cgi?id=419421 David, can you confirm that bug #446637 for "AMD cards" has been resolved with Qt6.4 too? 2218721 71 nate 2023-03-27 17:59:43 +0000 *** Bug 446637 has been marked as a duplicate of this bug. *** 2250667 72 nate 2023-09-05 19:34:09 +0000 *** Bug 474188 has been marked as a duplicate of this bug. *** 2252747 73 temp02 2023-09-13 09:39:09 +0000 I've noticed since system upgrade that plasma timer 2.0 runs too fast. Downgrading qt5 and the timer functions as normal. Arch Linux. [2023-09-13T11:25:47+0200] [ALPM] downgraded qt5-base (5.15.10+kde+r155-1 -> 5.15.10+kde+r152-1) [2023-09-13T11:26:08+0200] [ALPM] downgraded qt5-declarative (5.15.10+kde+r31-1 -> 5.15.10+kde+r29-1) [2023-09-13T11:26:27+0200] [ALPM] downgraded qt5-tools (5.15.10+kde+r3-2 -> 5.15.10+kde+r3-1) 2252751 74 temp02 2023-09-13 09:56:42 +0000 (In reply to temp02 from comment #73) > I've noticed since system upgrade that plasma timer 2.0 runs too fast. > Downgrading qt5 and the timer functions as normal. Arch Linux. > > [2023-09-13T11:25:47+0200] [ALPM] downgraded qt5-base (5.15.10+kde+r155-1 -> > 5.15.10+kde+r152-1) > [2023-09-13T11:26:08+0200] [ALPM] downgraded qt5-declarative > (5.15.10+kde+r31-1 -> 5.15.10+kde+r29-1) > [2023-09-13T11:26:27+0200] [ALPM] downgraded qt5-tools (5.15.10+kde+r3-2 -> > 5.15.10+kde+r3-1) This is with 120Hz on X11 with Nvidia. 2252764 75 temp02 2023-09-13 10:53:44 +0000 Nevermind, the problem is back again. 2252770 76 nate 2023-09-13 11:51:07 +0000 As the "Version Fixed In" field says, this is fixed in Plasma 6. So if you're not using Plasma 6 yet, it's still expected to be broken. 2275726 77 nate 2023-12-21 20:29:08 +0000 *** Bug 478786 has been marked as a duplicate of this bug. *** 134944 2021-01-16 18:58:31 +0000 2021-01-16 18:58:31 +0000 test case test.qml text/plain 1189 kde aW1wb3J0IFF0UXVpY2sgMi42CmltcG9ydCBRdFF1aWNrLkNvbnRyb2xzIDIuMgoKSXRlbSB7CiAg ICB3aWR0aDogODAwCiAgICBoZWlnaHQ6IDYwMAoKICAgIFJlY3RhbmdsZSB7CiAgICAgICAgaWQ6 IHJlY3QKICAgICAgICB4OiA1MAogICAgICAgIHkgOjUwCiAgICAgICAgd2lkdGg6IDEwMAogICAg ICAgIGhlaWdodDogMTAwCiAgICAgICAgcHJvcGVydHkgYm9vbCBmbGlwOiBmYWxzZQogICAgICAg IGNvbG9yOmZsaXAgPyAgInJlZCIgOiAiYmx1ZSIKICAgICAgICBUaW1lciB7CiAgICAgICAgICAg IGludGVydmFsOiAxMDAwCiAgICAgICAgICAgIHJ1bm5pbmc6IHRydWUKICAgICAgICAgICAgcmVw ZWF0OiB0cnVlCiAgICAgICAgICAgIG9uVHJpZ2dlcmVkOnJlY3QuZmxpcCA9ICFyZWN0LmZsaXAK ICAgICAgICB9CiAgICB9CgogICAgUmVjdGFuZ2xlIHsKICAgICAgICBpZDogcmVjdDIKICAgICAg ICB5IDo1MAogICAgICAgIHg6IDIwMAogICAgICAgIHdpZHRoOiAxMDAKICAgICAgICBoZWlnaHQ6 IDEwMAogICAgICAgIGNvbG9yOmZsaXAgPyAgInJlZCIgOiAiYmx1ZSIKICAgICAgICBwcm9wZXJ0 eSBib29sIGZsaXA6IGZhbHNlCgogICAgICAgIE1vdXNlQXJlYSB7CiAgICAgICAgICAgIGFuY2hv cnMuZmlsbDogcGFyZW50CiAgICAgICAgICAgIG9uRG91YmxlQ2xpY2tlZDogcmVjdDIuZmxpcCA9 ICFyZWN0Mi5mbGlwCiAgICAgICAgfQogICAgfQoKICAgIFRleHQgewogICAgICAgIHk6IDE4MAog ICAgICAgIHRleHQ6ICJmaXJzdCBjaGVjayBmbGlwIGNvbG91cnMgZXZlcnkgc2Vjb25kLCBzZWNv bmQgYm94IGNoYW5nZXMgb24gZG91YmxlIGNsaWNrLCB0aGlyZCBib3ggcm90YXRlcyBvbmNlIGV2 ZXJ5IHNlY29uZCIKICAgIH0KCiAgICBSZWN0YW5nbGUgewogICAgICAgIGlkOiByZWN0MwogICAg ICAgIHg6IDQwMAogICAgICAgIHkgOjUwCiAgICAgICAgd2lkdGg6IDEwMAogICAgICAgIGhlaWdo dDogMTAwCiAgICAgICAgY29sb3I6ICJncmVlbiIKCiAgICAgICAgUm90YXRpb25BbmltYXRvciB7 CiAgICAgICAgICAgIHRhcmdldDogcmVjdDM7CiAgICAgICAgICAgIGZyb206IDA7CiAgICAgICAg ICAgIHRvOiAzNjA7CiAgICAgICAgICAgIGR1cmF0aW9uOiAxMDAwCiAgICAgICAgICAgIHJ1bm5p bmc6IHRydWUKICAgICAgICAgICAgbG9vcHM6IC0xCiAgICAgICAgfQogICAgfQp9Cg==