Bug 453428 - Clicking Notifications Crashes Associated Applications
Summary: Clicking Notifications Crashes Associated Applications
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (show other bugs)
Version: 5.24.5
Platform: Arch Linux Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL: https://git.harting.dev/ALHP/ALHP.GO
Keywords: regression
Depends on:
Blocks:
 
Reported: 2022-05-05 17:08 UTC by nekonexus
Modified: 2022-06-04 04:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
nekonexus: Wayland?
nekonexus: X11+
nekonexus: Usability+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nekonexus 2022-05-05 17:08:24 UTC
SUMMARY

This is kind of odd, because I wouldn't think it a cause, but recently clicking on clickable bodies of (almost) any desktop notification for any application (I've tried) crashes that application for no obvious reason. I even tried enabling the "KDE_COREDUMP_NOTIFY=1" environment variable to try to get DrKonqi to catch what's going on but (the notification for that just asks to run gdb but both GDB and) DrKonqi doesn't run when I try interacting with it.

The only exception I've experienced so far with this issue is KOrganizer; I've had this issue with electron apps (like Discord) and nheko (Qt5)... "notify-send" doesn't seem affected though, but I don't know if that's because it doesn't have a clickable body. :/


STEPS TO REPRODUCE

1. Have a desktop notification go off
2. Click the body of the notification rather than a button within it, if available

OBSERVED RESULT
The associated application that sent the notification crashes.

EXPECTED RESULT
The applications associated should react as they normally should when clicking on notifications. 

SOFTWARE/OS VERSIONS

Linux: Arch Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Graphics Platform: X11

ADDITIONAL INFORMATION

A x86-64-v3 repo is used:
https://git.harting.dev/ALHP/ALHP.GO
Comment 1 Nate Graham 2022-05-05 20:44:23 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Can you please attach one? Thanks!
Comment 2 nekonexus 2022-05-05 20:54:22 UTC
(In reply to Nate Graham from comment #1)
> If something crashed, we need a backtrace of it so we can figure out what's
> going on. See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports
> 
> Can you please attach one? Thanks!

But what do I attach GDB to?
Comment 3 nekonexus 2022-05-05 21:13:42 UTC
Omg, it's been happening to me for at least 2 weeks, and the minute I go looking for it today, it starts to behave...
I'll come back with that backtrace (assuming you want it attached to a Plasma process) if I see it happen again; I'm totally baffled right now
Comment 4 Nate Graham 2022-05-05 23:40:51 UTC
(In reply to nekonexus from comment #2)
> But what do I attach GDB to?
Whatever process is crashing.
Comment 5 Bug Janitor Service 2022-05-20 04:35:43 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2022-06-04 04:35:46 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!