https://bugs.kde.org/show_bug.cgi?id=394360
Jiri Slaby <jirisl...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |UNCONFIRMED
--- Comment #13 from Jiri Slaby <jirisl...@gmail.com> ---
(In reply to Jiri Slaby from comment #8)
> 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
Correct – it is enough to re-run kded5 like this and kded5 no longer spawns
children. So neither setxkbmap is exec'ed nor other processes. So unless you
have an idea how to run a new (strace'd) instance kded5 which would behave as
the one run by the session, I cannot provide the requested info.
--
You are receiving this mail because:
You are watching all bug changes.
