There is a miunderstanding of the packagekit api. You need to watch the 
restartrequired signal on the transaction interface instead. The currently used 
restartschedule signal is used to indicate the client that a later version of 
the daemon has been installed as the currently running one.
In packagekit upstream the signal is only emitted during an upgrade transaction 
(e.g. in the yum backend code).
But aptdaemon will also emit the signal during a get updates call. Hopefully 
the code on the aptdaemon side will land today or tomorrow.
The packagekit api allows to send different types: application, session and 
system. At the moment only system restart will be supported.
-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942104

Title:
  the indicator stopped turning red on restart required

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/942104/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to