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

Stephan Diestelhorst <stephan.diestelho...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Power management &          |general
                   |brightness                  |
                 CC|                            |k...@davidedmundson.co.uk
         Resolution|UPSTREAM                    |---
             Status|RESOLVED                    |REOPENED
     Ever confirmed|0                           |1

--- Comment #7 from Stephan Diestelhorst <stephan.diestelho...@gmail.com> ---
That cannot be it, I think.  On the other side of that qdbus is... powerdevil,
again.  I have followed the code and on receiving the DBus command, it *should*
*eventually* follow the same code path that gets called from the Krunner
activity -- which in turn still works.  I have a suspicion that somewhere
between receiving the DBus message and getting it out to logind something
breaks.

There seem to be a few layers of wrapping logic here.  I would like to get some
debug symbols and attach GDB to the powerdevil process and then do the two
approaches again: clicking Sleep in KMenu which works, and then sending the
DBus message.  I should also check that closing the lid and the hotkey actually
send the DBus message, too.

Or are you saying powerdevil is upstream of plasmashell?

In any case.. I am happy to have this assigned to me for now.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to