> I actually had to do a complete reinstall . Have you actually checked the logs to see what exactly was failing before resorting to that?
Someone in the Telegram group had a broken filesystem with a 0 byte kwallet xml file which was breaking the new dbus, it's apparently more strict than the old one. Jan 11 08:56:50 desktop-a dbus-broker-launch[820]: Looking up NSS group entry for 'netdev'... Jan 11 08:56:50 desktop-a dbus-broker-launch[820]: NSS returned no entry for 'netdev' Jan 11 08:56:50 desktop-a dbus-broker-launch[820]: Invalid group-name in /usr/share/dbus-1/system.d/ead-dbus.conf +20: group="netdev" Jan 11 08:56:50 desktop-a dbus-broker-launch[820]: Invalid group-name in /usr/share/dbus-1/system.d/iwd-dbus.conf +22: group="netdev" Jan 11 08:56:50 desktop-a dbus-broker-launch[820]: Invalid XML in /usr/share/dbus-1/system.d/org.kde.kcontrol.kcmkwallet5.conf +1: no element found Jan 11 08:56:50 desktop-a dbus-broker-launch[820]: ERROR run @ ../dbus-broker-35/src/launch/main.c +152: Return code 1 Jan 11 08:56:50 desktop-a dbus-broker-launch[820]: main @ ../dbus-broker-35/src/launch/main.c +178 Jan 11 08:56:50 desktop-a dbus-broker-launch[820]: Exiting due to fatal error: -131 .rw-r--r-- 0 root root 7 Dec 2023 /usr/share/dbus-1/system.d/org.kde.kcontrol.kcmkwallet5.conf Martin On Tue, Jan 16, 2024 at 11:46 AM Severus <huynhok....@vnoss.org> wrote: > > Hi folks, > > I notice that thunderbird does not show notification as system > notification. > > And also I see this error: plasma_waitforname[68941]: > org.kde.knotifications: WaitForName: Service was not registered within > timeout. > > Best regards, > Severus > > -- > Trên con đường lấy lửa thử vàng anh phát hiện con tim mình chỉ là đá.
