[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdelibs-bugs
Subject:    [frameworks-kcmutils] [Bug 348401] KCModuleProxy fails to detect open kcm (at least kcmshell blocks)
From:       Thomas Lübking <thomas.luebking () gmail ! com>
Date:       2015-05-31 21:59:46
Message-ID: bug-348401-90985-INLIKQ23sb () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=348401

Thomas Lübking <thomas.luebking@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|System settings freezes if  |KCModuleProxy fails to
                   |Windows manager settings is |detect open kcm (at least
                   |open                        |kcmshell blocks) if 1st
                   |                            |kcmshell5 was invoke w/
                   |                            |--icon parameter
            Product|kwin                        |frameworks-kcmutils
     Ever confirmed|0                           |1
                 CC|                            |thomas.luebking@gmail.com
           Assignee|kwin-bugs-null@kde.org      |kdelibs-bugs@kde.org
          Component|general                     |general
             Status|UNCONFIRMED                 |CONFIRMED

--- Comment #7 from Thomas Lübking <thomas.luebking@gmail.com> ---
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 style

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Kdelibs-bugs mailing list
Kdelibs-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdelibs-bugs

[prev in list] [next in list] [prev in thread] [next in thread]