View Single Post
Posts: 1,313 | Thanked: 2,978 times | Joined on Jun 2011 @ Finland
#1026
Originally Posted by slarti View Post
It was like that all morning. I waited a while for the script to fire before unlocking but nothing happened. Like I said, a reboot cured it and I haven't seen this behaviour after that. If I see it again, do you have any suggestions what information to collect?
Logs as now are useful. But as I said in the logs it was clear that the script was launched, so it's probably something that the script does that doesn't work. If that happens again try running the script manually and see if it does anything: First run it through ProfileMatic's UI with Test button in custom action. If that doesn't work, run it from terminal. See if there's any output.

I started writing a simple dbus listener in python which listens to dbus messages from the timed daemon and updates a profilematic rule's activation time or active status according to the message.

I wanted to know if using the updateRule method this way would have any adverse effects?
That's safe, but I'm surprised that you can use it. It takes as parameter a serialized C++ object. I don't even know how it looks like building that from python or using dbus-send. Out of curiosity do you have some working sample?

The only caveat is that the object usually changes between each ProfileMatic release. But of course if you take an existing rule and only modify the parts you want, then that's pretty future proof also.
__________________
My N9/N950 projects: