Created attachment 165500 [details] Bug video SUMMARY *** Discover stutters intensely when resizing. Seen for the past 2 years (not related to Plasma 6, it also happened in 5.26 and 5.27). It only happens in the Discover window in Wayland. This response was given previously, so it can shed some light into the problem: "Is Discover a Kirigami/QML app? If yes, then this has nothing to do with X/Wayland but a QT/QML issue." *** STEPS TO REPRODUCE 1. Resize Discover from the corner of the window OBSERVED RESULT Intense stuttering EXPECTED RESULT No stutter Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.5.0-15-generic (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9400T CPU @ 1.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: HP Product Name: HP Pavilion All-in-One 24-xa0xxx
I can reproduce. Also, if I continue to do if for a couple seconds, Discover will freeze up and crash. Related, or should I file another bug report? Operating System: KDE neon Testing Edition KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.5.0-15-generic (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM Graphics Processor: AMD Radeon Pro WX 3200 Series Manufacturer: Dell Inc. Product Name: Precision 7540
(In reply to Doug from comment #1) > I can reproduce. Also, if I continue to do if for a couple seconds, > Discover will freeze up and crash. Related, or should I file another bug > report? > > Operating System: KDE neon Testing Edition > KDE Plasma Version: 6.0.0 > KDE Frameworks Version: 6.0.0 > Qt Version: 6.6.1 > Kernel Version: 6.5.0-15-generic (64-bit) > Graphics Platform: Wayland > Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz > Memory: 15.4 GiB of RAM > Graphics Processor: AMD Radeon Pro WX 3200 Series > Manufacturer: Dell Inc. > Product Name: Precision 7540 I've found the Welcome Center and System Monitor have the same bug(crazy stuttering). I dont see it as VHI bug but it certainly gives a bad first impression specially for the Welcome Center and Discover. Given how the bug seems to happen for similar KDE core projects and not apps like Okular, the problem might come its Kirigami/QML/QT base. Other apps built in a similar way may have the same stuttering.
(In reply to Doug from comment #1) > I can reproduce. Also, if I continue to do if for a couple seconds, > Discover will freeze up and crash. Related, or should I file another bug > report? > Does it crash if you make it really small and then try to expand? If so it is probably https://bugs.kde.org/show_bug.cgi?id=478638 Regarding stuttering: It doesn't stutter for me (AMD RX 580), just looks a little bit wonky. Do you all have intel IGPU's or old GPU's?
(In reply to duha.bugs from comment #3) > (In reply to Doug from comment #1) > > I can reproduce. Also, if I continue to do if for a couple seconds, > > Discover will freeze up and crash. Related, or should I file another bug > > report? > > > > Does it crash if you make it really small and then try to expand? If so it > is probably https://bugs.kde.org/show_bug.cgi?id=478638 > > > Regarding stuttering: It doesn't stutter for me (AMD RX 580), just looks a > little bit wonky. Do you all have intel IGPU's or old GPU's? yes. It can be resized as small as its limit allows it and it remains open. It crashes right after expanding it. Regular gpu. lspci: 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:14.5 SD Host controller: Intel Corporation Device a375 (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10) 00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #5 (rev f0) 00:1c.5 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #6 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation H370 Chipset LPC/eSPI Controller (rev 10) 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter 03:00.0 Non-Volatile memory controller: SK hynix BC511
Indeed, unfortunately there's nothing we can do about it in KDE; it's a bug/limitation of QtQuick itself, in Qt.
(In reply to Nate Graham from comment #5) > Indeed, unfortunately there's nothing we can do about it in KDE; it's a > bug/limitation of QtQuick itself, in Qt. Has there been an upstream fix or nothing yet
There hasn't been an upstream fix, or else the issue wouldn't still be happening. :) It's something upstream is aware of, but the issue turns out to be super difficult to fix, unfortunately.
*** Bug 491770 has been marked as a duplicate of this bug. ***
Why was this bug marked as "Resolved"? I filed a new bug (linked above) for this same issue because a search of open bugs returned no matches. This bug is not resolved even if its an upstream bug.
The bug is marked as resolved upstream as it is not actionable by KDE. Bugs need to be tracked where they can be fixed. This is not unique to the KDE bugtracker, you will see that other projects handle it the same. In this case the issue is in the QT code, see comment 5. I hope that answers your question.
For more information on the topic, see https://community.kde.org/Get_Involved/Issue_Reporting#Understand_what_the_resolution_statuses_mean.
This problem is this issue has no upstream report. This issue will never be fixed if upstream isn't tracking the problem.
Like I said, "It's something upstream is aware of, but the issue turns out to be super difficult to fix, unfortunately." It's a huge architectural issue central to the core of the technology, not the sort of thing that typically gets a narrow targeting bug report.
Even so, the way this bug is marked is unsearchable (using KDE quicksearch https://bugs.kde.org/) unless I explicitly search for "resolved" bugs. From a user's perspective, I want to see all "unfixed" bugs when I search even if those bugs are "resolved" (no longer considered actionable by the developers). I have opened a bug report for that now: https://bugs.kde.org/show_bug.cgi?id=491910
(In reply to Nate Graham from comment #13) > It's a huge architectural > issue central to the core of the technology, not the sort of thing that > typically gets a narrow targeting bug report. I found an upstream bug report https://bugreports.qt.io/browse/QTBUG-51112 . All reported issues of this kind on the QT bugtracker have eventually been marked as a duplicate of the linked bug report. Even if there is no progress on getting it fixed, this is what should be referred to.
Nice, thanks for finding that.
*** Bug 498261 has been marked as a duplicate of this bug. ***