Created attachment 155931 [details] Reproduce video SUMMARY The counter in notification will increase wrongly after minimizing/closing discover when installing apps STEPS TO REPRODUCE 1. open discover then install a app 2. close discover 3. open discover again by clicking discover in kickoff 4. close discover OBSERVED RESULT The counter in notification will increase wrongly after minimizing/closing discover when installing apps EXPECTED RESULT correct counter SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230202 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-11320H @ 3.20GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: TIMI Product Name: A18R ADDITIONAL INFORMATION
it seemes every time the discover window is closed a new notification spawns no matter if there is already one. it stacks up. closing discover 3 times gives 3 times the same notification. happens on my device too: Betriebssystem: KDE neon 5.26 KDE-Plasma-Version: 5.26.5 KDE-Frameworks-Version: 5.102.0 Qt-Version: 5.15.8 Kernel-Version: 5.15.0-58-generic (64-bit) Grafik-Plattform: Wayland Prozessoren: 16 × AMD Ryzen 7 5700U with Radeon Graphics Speicher: 62,2 GiB Arbeitsspeicher Grafikprozessor: AMD Radeon Graphics Hersteller: TUXEDO Produktname: TUXEDO Pulse 15 Gen2
Fixed in Plasma 5.27 already.
still exists in plasma 5.27.2 Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.14-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland
(In reply to Nate Graham from comment #2) > Fixed in Plasma 5.27 already. still exists on plasma 6 actually
(In reply to rosswzyang from comment #4) > (In reply to Nate Graham from comment #2) > > Fixed in Plasma 5.27 already. > > still exists on plasma 6 actually https://drive.google.com/file/d/1SXafQC_h0-uLuuwc93JuDZBs1Il_WH3M/view?usp=sharing reproduce steps
*** Bug 486612 has been marked as a duplicate of this bug. ***