Bug 489820

Summary: Notifications clickable only in popup state, but not from the notification widget/applet history
Product: [Plasma] plasmashell Reporter: Matija <mata987>
Component: NotificationsAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kde, nate
Priority: NOR    
Version: 6.1.2   
Target Milestone: 1.0   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Matija 2024-07-06 09:49:03 UTC 
SUMMARY
When I get notifications from websites in Firefox, I can click them, but only until they go off screen.
From the notifications widget in the system tray/panel, I can see them and only select text from them, but they don't lead to the origin websites anymore.

STEPS TO REPRODUCE
1. Allow notifications from certain sites
2. Firefox is running (or just started, doesn't matter)
3. Aformentioned sites push content and notifications start to appear on the screen (in the form of a popup) which hide themselves after a certain time (set in settings)
4. Those that are clicked while the popup is on the screen, lead to websites they originated from
5. Other ones that weren't clicked are available in the notification widget

OBSERVED RESULT
Clicking a notification in the widget doesn't do anything.
Options are to remove the notification from the list or copy the text of the notification.

EXPECTED RESULT
Clicking a notification does the same as clicking the notification while in popup state, that is it leads to the post/location on the originating website.


SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-41-generic (64-bit)
Comment 1 Matija 2024-07-06 09:52:56 UTC 
https://bugs.kde.org/show_bug.cgi?id=486046

Found't the above already reported, but filled this in as I'm on KDE Neon, and the one reported is Fedora.

Since I don't know if it makes a difference, please make this a duplicate if you deem it so and leave a comment so I know what action to take in similar situations in the future.

Thanks!
Comment 2 Nate Graham 2024-07-27 22:46:32 UTC 

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