View Single Post
qwazix's Avatar
Moderator | Posts: 2,622 | Thanked: 5,447 times | Joined on Jan 2010
#143
I'm debugging this right now and I think the problem is that timenow starts before proximityd. So I modified the upstart job to look like this.

Code:
start on started proximityd
stop on stopped hal
#stop on stopped dbus
respawn
respawn limit 15 3

script
    sleep 2
    exec su user -c "run-standalone.sh /opt/timenowd/bin/timenowd"

end script
post-stop script
    # clean up
    killall timenowd
end script
Kossuth, please edit your /etc/event.d/timenow.conf to look like above and test again. If it fixes the problem I will include the modified startup job in the package, and push an update.

The fact that it happens to some people and not other is probably due to the different startup services of each setup.
__________________
Proud coding competition 2012 winner: ρcam
My other apps: speedcrunch N9 N900 Jolla –– contactlaunch –– timenow

Nemo UX blog: Grog
My website: qwazix.com
My job: oob
 

The Following 2 Users Say Thank You to qwazix For This Useful Post: