Bug 492031 - Opening the notification panel hangs the application
Summary: Opening the notification panel hangs the application
Status: RESOLVED FIXED
Alias: None
Product: Tokodon
Classification: Applications
Component: general (show other bugs)
Version: 24.07.90
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-22 08:50 UTC by Bart Ribbers
Modified: 2024-12-27 23:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bart Ribbers 2024-08-22 08:50:16 UTC
This happens on git master for me but not on 24.05.2.

An error appears in the console:

qrc:/qt/qml/org/kde/tokodon/content/ui/NotificationPage.qml:127:9: QML Connections: Detected function "onPostSourceReady" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name.
Comment 1 Joshua Goins 2024-10-20 16:36:53 UTC
Can you try again on git master? I have a hunch this is because we were missing support for certain notification types, so this might be fixed now.
Comment 2 Bug Janitor Service 2024-11-04 03:46:23 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2024-11-19 03:46:35 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
Comment 4 Bart Ribbers 2024-12-27 20:39:07 UTC
I found this in my mail archives and saw I never answered to it. Just for clarification this indeed seems to have been resolved, currently on 24.12.0 this issue does not occur for me.
Comment 5 Joshua Goins 2024-12-27 23:27:14 UTC
Thanks for following up!