https://bugs.kde.org/show_bug.cgi?id=394360
Jiri Slaby <jirisl...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |UNCONFIRMED
Resolution|WAITINGFORINFO |---
--- Comment #8 from Jiri Slaby <jirisl...@gmail.com> ---
(In reply to Fabian Vogt from comment #7)
> Please try to run kded5 without the glib event loop:
>
> kquitapp5 kded5; QT_NO_GLIB=1 kded5
>
> If that works fine, it's probably a bug in either glib itself or in its
> integration.
I don't want to be too conclusive now, but after quite few plugs/unplugs of
such kded5:
# grep -z GLIB /proc/`pidof kded5`/environ; echo
QT_NO_GLIB=1
I haven't seen the issue yet.
But to me it seems that it is enough to just re-run kded5 after power on:
kquitapp5 kded5; kded5
I haven't seen the issue with such a restart too. But I only tried few replugs.
--
You are receiving this mail because:
You are watching all bug changes.
