[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [frameworks-kcmutils] [Bug 348401] KCModuleProxy fails to detect open kcm (at least kcmshell blocks)
From: djx <sna7e_7 () hotmail ! com>
Date: 2015-05-31 22:39:47
Message-ID: bug-348401-17878-5ic72mYV0c () http ! bugs ! kde ! org/
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=348401
--- Comment #8 from djx <sna7e_7@hotmail.com> ---
(In reply to Thomas Lübking from comment #7)
> Ahhhhhhh... I completely misunderstood the problem.
> You *intentionally* try to open the kcm twice.
>
> The sycoca message is a red herring then.
>
> This happens, but don't ask me why:
>
> KWin "Show WM settings..." effectively calls
>
> kcmshell5 --icon preferences-system-windows kwindecoration kwinactions
> kwinfocus kwinmoving kwinadvanced kwinrules kwincompositing kwineffects
> kwintabbox kwinscreenedges kwinscripts &
>
> If I do this, a subsequent
>
> kcmshell5 kwineffects
>
> blocks (just like when invoking that command from the context menu)
>
> Now here's the strange part:
>
> kcmshell5 kwindecoration kwinactions kwinfocus kwinmoving kwinadvanced
> kwinrules kwincompositing kwineffects kwintabbox kwinscreenedges kwinscripts
> &
>
> and then
>
> kcmshell5 kwineffects
>
> works as expected.
>
> KCModuleProxy will have trouble to detect the opened kcm, but I've not the
> least idea why.
> What I can say for sure is that it's NOT a kwin problem, try eg
>
> kcmshell5 --icon foo style &
> kcmshell5
With
kcmshell5 --icon foo style &
kcmshell5
only one (the first one) windows opens.
--
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic