Created attachment 163643 [details] demo SUMMARY After few clicks, application launcher may stop work. After re-adding widget or switch to alternative, it may work some time, but breaks later STEPS TO REPRODUCE 1. Flood click on widget or flood by pressing Super-key OBSERVED RESULT Application launcher may stop works EXPECTED RESULT Application launcher always opens SOFTWARE/OS VERSIONS Linux kernel: 6.6.3 KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 GPU: Nvidia ADDITIONAL INFORMATION Multi-monitor setup. Each monitor have widget. When one widget broken, other widgets may work Tested on panels: - floating panel with fill space - floating panel with fit space - always visible panel with fit space - auto-hide panel with fit space
Can't reproduce on beta1. Maybe there are some packaging issues? I think the kde-unstable repo for arch linux hasn't finished all the updates to beta1 when you posted this. Could you try this again after updating your system? Also, could you provide complete system logs when this happens? Thanks!
> Maybe there are some packaging issues? I think the kde-unstable repo for > arch linux hasn't finished all the updates to beta1 when you posted this. It's load sources like that: ``` pkgver=5.90.0 _dirver=$(echo $pkgver | cut -d. -f1-3) source=(https://download.kde.org/unstable/plasma/$_dirver/$pkgname-$pkgver.tar.xz{,.sig}) ``` So it must be clear sources from KDE site. Also, I check SHA256 from package sources with archives from KDE site, and it's match > Could you try this again after updating your system? Ok, I try it later > Also, could you provide complete system logs when this happens? Thanks! Sorry, but no - I rolled back to Plasma 5, and do not have logs from Plasma 6 now
(In reply to SR_team from comment #2) > > Maybe there are some packaging issues? I think the kde-unstable repo for > > arch linux hasn't finished all the updates to beta1 when you posted this. > > It's load sources like that: > ``` > pkgver=5.90.0 > _dirver=$(echo $pkgver | cut -d. -f1-3) > source=(https://download.kde.org/unstable/plasma/$_dirver/$pkgname-$pkgver. > tar.xz{,.sig}) > ``` > > So it must be clear sources from KDE site. > > Also, I check SHA256 from package sources with archives from KDE site, and > it's match Ah I meant that some dependencies might have not gotten updates when you posted..
> Ah I meant that some dependencies might have not gotten updates when you > posted.. No, package updated yesterday, I installed and test it today. Sources for 5.90.0 at download.kde.org do not changed in this time
(In reply to SR_team from comment #4) > > Ah I meant that some dependencies might have not gotten updates when you > > posted.. > > No, package updated yesterday, I installed and test it today. Sources for > 5.90.0 at download.kde.org do not changed in this time Sorry for not making myself clear. I meant that the *packages on kde-unstable* might not have been up to date. True, beta1 was released on 11/29, but the Arch packages for those don't update instantly. The maintainers were packaging and pushing those to kde-unstable one by one, or batch by batch. During the process, you might have updated in your system at a time where some packages were beta1, but some packages were still at alpha, which might cause a lot of problems. Of course, this is assuming you installed beta1 from the kde-unstable repo. Is this how you installed plasma beta1?
(In reply to fanzhuyifan from comment #5) > (In reply to SR_team from comment #4) > > > Ah I meant that some dependencies might have not gotten updates when you > > > posted.. > > > > No, package updated yesterday, I installed and test it today. Sources for > > 5.90.0 at download.kde.org do not changed in this time > > Sorry for not making myself clear. I meant that the *packages on > kde-unstable* might not have been up to date. > True, beta1 was released on 11/29, but the Arch packages for those don't > update instantly. The maintainers were > packaging and pushing those to kde-unstable one by one, or batch by batch. > During the process, you might have > updated in your system at a time where some packages were beta1, but some > packages were still at alpha, which > might cause a lot of problems. > > Of course, this is assuming you installed beta1 from the kde-unstable repo. > Is this how you installed plasma beta1? There are now some updates that were sent this evening (UTC). But these are just applications. Plasma itself was updated before my installation - in the evening of 11/29 and in the morning of 11/30 (UTC)
(In reply to SR_team from comment #6) > > There are now some updates that were sent this evening (UTC). But these are > just applications. Plasma itself was updated before my installation - in the > evening of 11/29 and in the morning of 11/30 (UTC) Thanks for making that clear! Hopefully the logs can offer some useful information, since I cannot reproduce this..
I think I saw another bug report about this recently, but now I can't find it.
I runed just plasmashell from Plasma 6 in Plasma 5 session via distrobox (`distrobox-enter -n neon -- kstart plasmashell`), and this bug not reproduced
Created attachment 163790 [details] System logs Add system logs. `.local/share/sddm/wayland-session.log` is empty. So add only systemd logs
Cannot reproduce on Plasma 6 either. But it's not a Plasma or a KWin issue; the issue is with your icon theme as some files seem to be missing.
(In reply to Nate Graham from comment #11) > Cannot reproduce on Plasma 6 either. But it's not a Plasma or a KWin issue; > the issue is with your icon theme as some files seem to be missing. Thanks, you right. I checked plasma styles and some files from `libplasma` package are missing - reinstall package resolved this. P.S. Package do not changed in repos, maybe it's problem with FS of my drive
(In reply to SR_team from comment #12) > (In reply to Nate Graham from comment #11) > > Cannot reproduce on Plasma 6 either. But it's not a Plasma or a KWin issue; > > the issue is with your icon theme as some files seem to be missing. > > > Thanks, you right. I checked plasma styles and some files from `libplasma` > package are missing - reinstall package resolved this. > > P.S. Package do not changed in repos, maybe it's problem with FS of my drive I reinstalled all system packages and bug reproduced for me. I use PC and Nvidia is main GPU without iGPU
I'm actually encountering the same issue with an nvidia gpu and a two monitor setup. But it's not limited to just the Application Launcher. It will randomly start occurring with any mouse click activated widget popups in a panel. I've had it happen with the Application Launcher, the System Monitor sensor, the system tray (both individual tray icons and the "Show hidden icons" popup), the system clock, and the notifications widget. I'm able to reproduce this on Plasma 6 Beta 1 with EndeavourOS (Arch). But I was also able to reproduce this on Plasma 5 on OpenSUSE Tumbleweed by changing the Plasma Renderer Render Loop setting to "Threaded". If I change Plasma 6 Beta 1's render loop to "Basic", this popups not working issue goes away for me. But I don't know what other side effects that setting has. I only have my EndeavourOS Plasma 6 Beta 1 install available at the moment, but I used the same system for OpenSUSE Tumbleweed Plasma 5. Operating System: EndeavourOS KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Kernel Version: 6.6.4-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 7.0 NVidia Driver Version: 545.29.06 NVML Version: 12.545.29.06
Oops, my comment should have been directed at another bug report. This one clearly isn't about icons.
I think we have a bunch of bug reports about this issue , for example https://bugs.kde.org/show_bug.cgi?id=477028 This Qt patch https://codereview.qt-project.org/c/qt/qtwayland/+/503674 fixes NVidia related freezes on my machine. So if this is not merged in time into 6.6 for Plasma release we can go back to forcing basic render loop for NVidia again https://invent.kde.org/plasma/plasma-integration/-/merge_requests/119
https://bugs.kde.org/show_bug.cgi?id=455913 is potentially another one
Thanks David! I'll consolidate everything and mention it on https://community.kde.org/Plasma/Wayland_Showstoppers *** This bug has been marked as a duplicate of bug 477028 ***
*** This bug has been marked as a duplicate of bug 455913 ***