https://bugs.kde.org/show_bug.cgi?id=449571
--- Comment #1 from Vlad Zahorodnii <vlad.zahorod...@kde.org> --- It seems to be related to KGlobalAccel and d-bus. #0 0x00007f7e8eb942a2 raise (libc.so.6 + 0x3d2a2) #1 0x00007f7e8eb7d950 abort (libc.so.6 + 0x26950) #2 0x00007f7e8e844b16 _dbus_abort.cold (libdbus-1.so.3 + 0x10b16) #3 0x00007f7e8e86b010 _dbus_warn_check_failed (libdbus-1.so.3 + 0x37010) #4 0x00007f7e9100c869 _ZN22QDBusConnectionPrivate19getNameOwnerNoCacheERK7QString (libQt5DBus.so.5 + 0x2e869) #5 0x00007f7e9100dd19 _ZN22QDBusConnectionPrivate13addSignalHookERK7QStringRKNS_10SignalHookE (libQt5DBus.so.5 + 0x2fd19) #6 0x00007f7e9100f821 _ZN9QtPrivate11QSlotObjectIM22QDBusConnectionPrivateFbRK7QStringRKNS1_10SignalHookEENS_4ListIJS4_S7_EEEbE4implEiPNS_15QSlotObjectBaseEP7QObjectPPvPb (libQt5DBus.so.5 + 0x31821) if you've updated qt5 or libdbus-1, can you try rolling them back? -- You are receiving this mail because: You are watching all bug changes.