-
Notifications
You must be signed in to change notification settings - Fork 343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crash: gdk_pixbuf_new_from_data: assertion 'bits_per_sample == 8' failed #1023
Comments
I get the same crash & error with an empty config file (everything commented out). |
Thanks for the detailled report! Could you try sending a notification by hand with the same icon, but now sent over dbus. You can do that as follows:
|
That works fine. I managed to capture a crash-causing notification with dbus notification
|
That makes me think that nheko does something weird when sending notifications. Might be good to open an issue there as well. Of course, dunst doesn't need to crash when an incorrect notification is sent, and it should be easy to fix that. |
I pushed a commit that should fix the crash. Dunst will now fall back to an icon given by path again. Thanks for the bug report |
Thanks, that fixed the crash! 💖 |
Issue description
dunst crashes when I get a notification from nheko (a Matrix client), but only from a specific account. Notifications from other accounts work and this account worked before. The following is printed on the terminal:
nheko uses the avatar of the account as the notification icon, but
notify-send -a "program" -i /path/to/the/avatar.png "summary" "body"
does not trigger the crash. As far as I can see the avatar didn't change between working and not working notifications.backtrace
Installation info
1.7.3
Gentoo repo
i3
MinimaldunstrcUnfortunately I couldn't reach the account to help me narrow this down, so I'm pasting the full config here for now.
The text was updated successfully, but these errors were encountered: