Bug 486684

Summary: Sometimes it is not possible to recall notification history
Product: [Plasma] plasmashell Reporter: Synthetic451 <bugs.kde.org.facelift226>
Component: NotificationsAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kde, nate, nicolas.fella
Priority: NOR    
Version First Reported In: 6.0.4   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Synthetic451 2024-05-06 20:07:15 UTC
SUMMARY
Sometimes I am unable to revisit the notification history again after clicking on it once. Clicking the "Show hidden icons" arrow in the tray and clicking Notifications does nothing. This usually happens right after the Notifications tray button goes from Visible to Hidden after clicking on it once.

STEPS TO REPRODUCE
1. (Not sure if necessary, but it's what's on my setup) Make sure Notifications is set to "Shown when relevant" in the System Tray settings
2. Trigger a notification to come in. I did this with Gmail browser notifications
3. Click on the Notification bell icon that appears in the Tray
4. Dismiss the notification history pane. Notification bell should go back into hidden
5. Click on the "Show hidden icons" arrow
6. Click on the Notifications bell

OBSERVED RESULT
Nothing happens when clicking on Notifications bell

EXPECTED RESULT
Clicking on notifications bell should show history

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.9-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2
Product Name: X570 Taichi
Comment 1 Nicolas Fella 2024-05-06 20:28:48 UTC

*** This bug has been marked as a duplicate of bug 483246 ***
Comment 2 Synthetic451 2024-05-06 20:34:43 UTC
@Nicolas, that bug you duped mentions that it was fixed in Plasma 6.0.3, but I am on 6.0.4 and I am still seeing the issue. Has that fix not made it into a stable release yet?
Comment 3 Nate Graham 2024-05-08 16:52:51 UTC

*** This bug has been marked as a duplicate of bug 452732 ***