pitsi

It does not crash at all. It is just that weird message it pops on every in dmesg. I am on debian testing/unstable x64.

Ok here goes my first try with gdb. ``` Reading symbols from dunst... (No debugging symbols found in dunst) Starting program: /usr/bin/dunst [Thread debugging using libthread_db enabled] Using host libthread_db...

I thought so :( The issue seems to happen only on boot and not when running dunst again (after killing it). Sadly, I can not find how it is started...

How can I know when it is started? There is a dunst.service file, but it is not even enabled as it seems. ``` $ systemctl status dunst.service Unit dunst.service could...

It may be dbus, because it has some dbus related file as you can see here https://packages.debian.org/sid/amd64/dunst/filelist As for dunst being the only notification daemon, it probably is because I...

Libglib has taken a couple of updates since then, like dunst which is now on 1.9.2. In fact, it is now on 2.78.**4** and the only thing different in dmesg...

It's 64 bit. Call me cocky, but there is no 32bit lib on my system. ``` $ file /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.4 /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7800.4: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically...

I know that fairly simple way. Before that "make install" part, I must also have all build dependencies available or it won't build, and that is annoying for me. Anyway,...

How can I do that? Because a) we are in the systemd era and such "this starts after that" incidents are now taken care by systemd with the "After=" parameter,...

I think I will do the second option first. So, assuming dbus starts it, how can I tell when it starts or stop it temporarily? Stopping dbus completely is out...