On 20. Juni 2025 7:05 Jan <bugreporter...@protonmail.ch> wrote: >> But more interesting would be why n.show() returns false, >> e.g. which function is in [3] getting called? > Indeed.
Downloading the source archives and setting `directory` appropriately in GDB, I traced this bug further. Unfortunately, usbguard-notifier spawns one thread per event which makes debugging a bit non-linear and cumbersome. After two or three more wrappers, `notify_notification_show` [4] gets called, which in turn calls `g_dbus_proxy_call_sync` and tests its return value. So I added a breakpoint there ``` break 'libnotify/notification.c':1230 commands print result cont end ``` and for one of the parallel threads the result is indeed `$4 = (GVariant *) 0x0`. I'll follow up when I find more time. Just wanted to document the current progress. [4] https://sources.debian.org/src/libnotify/0.8.6-1/libnotify/notification.c/#L1122 Regards, Jan
