View Single Post
Posts: 242 | Thanked: 169 times | Joined on Nov 2011
#60
For the sake of knowledge, I had same problem reported above upon rebooting.

I found the problem was related to proximityd not starting on boot (shortcutd needs proximityd running).

I solved changing this line into /etc/event.d/proximityd
Code:
#start on started dbus
to this one (I saw shortcutd starts this way)

Code:
start on started hildon-desktop
Now proximityd starts properly on boot and shortcutd works good.
This change made necessary since upgrade to kp53, as reported previously.

Last edited by enne30; 2015-09-15 at 12:06.
 

The Following 4 Users Say Thank You to enne30 For This Useful Post: