Thread: [ANNOUNCE] AppLock - An application locking daemon for Maemo handsets
View Single Post
warhawk007 is offline warhawk007
2011-07-11 , 19:36
Posts: 96 | Thanked: 51 times | Joined on Jul 2010 @ India
#83
Originally Posted by SPARTAN563 View Post
Oh, wow okay. If that is happening it means there is something causing the daemon to crash... Very bad news, could be that there is another daemon running, say in a terminal? If that isn't the case though, then what you could do is make sure that you have sent the "initctl emit AppLockStopDaemon" event and run a daemon in a terminal to see what it says.

Ah, sorry about the chown thing, got them the wrong way around it is supposed to be "user:users"
Wow, it worked this time. And we are making progress. Changing the permissions made the UI responsive. Now locking and unlocking the UI adds and removes the lock icon accordingly.
As an example, this is the output when locking and unlocking "contacts' in the UI:

For example this is the output when locking and unlocking "Contacts" in the GUI.

~ $ applock -d
AppLock Daemon - Loading Settings
Loading Application Monitor
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QStr ing,QString,QString)
Loading Session Bus Monitor
Session Filters:
"type='method_call',interface='com.nokia.Messaging UI',member='top_application'"
"type='method_call',interface='com.nokia.osso_addr essbook',member='top_application'"
Adding Filter: "type='method_call',interface='com.nokia.Messaging UI',member='top_application'"
DATA:
Adding Filter: "type='method_call',interface='com.nokia.osso_addr essbook',member='top_application'"
DATA:
DBus Monitor Connected
DBus Monitor Running
Message Recieved on DBus Type= "signal" Sender= "org.freedesktop.DBus" Destination= ":1.1142"
Signal - Interface: "org.freedesktop.DBus" && Member: "NameAcquired"
Adding Filter: "Contacts_Keypress" ( "session" )
"type='method_call',interface='com.nokia.osso_addr essbook',member='search_append'"
Adding search to settings
Adding filter to monitor
Filter Added
Adding Filter: "Contacts_Shortcut" ( "session" )
"type='method_call',interface='com.nokia.osso_addr essbook',member='top_application'"
Adding search to settings
Adding filter to monitor
Filter Added
Removing Filter: "type='method_call',interface='com.nokia.osso_addr essbook',member='search_append'"
DATA: pxpe
SETTINGS - Removing Search: "Contacts_Keypress"
Message Recieved on DBus Type= "error" Sender= "org.freedesktop.DBus" Destination= ":1.1142"
Removing Filter: "type='method_call',interface='com.nokia.osso_addr essbook',member='top_application'"
DATA:
SETTINGS - Removing Search: "Contacts_Shortcut"
Removing Filter: "type='method_call',interface='com.nokia.Messaging UI',member='top_application'"
DATA: type='method_call',interface='com.nokia.MessagingU I',member='top_application'
SETTINGS - Removing Search: "Conversations"
Adding Filter: "Contacts_Keypress" ( "session" )
"type='method_call',interface='com.nokia.osso_addr essbook',member='search_append'"
Adding search to settings
Adding filter to monitor
Filter Added
Adding Filter: "Contacts_Shortcut" ( "session" )
"type='method_call',interface='com.nokia.osso_addr essbook',member='top_application'"
Adding search to settings
Adding filter to monitor
Filter Added

And now the sad part, like I told before, even though the terminal indicates that the UI detects the input, the application still fails to lock in reality.

Though applications added directly through the command line will lock like I showed before in the case of Dorian.
 

The Following User Says Thank You to warhawk007 For This Useful Post: