hamster does not stop activity on shutdown/reboot and can't save preferences (Ubuntu 16.04)

[somhi]

I've installed Hamster from latest master as stated in the building instructions. I'm running Ubuntu 16.04.

First problem is that I cannot save preferences because the folder ~/.gconf/apps/hamster-time-tracker has been assigned root permissions. I can solve that by changing permissions on that folder to my user.

Main concern now is that activities don't stop when I reboot/shutdown the computer. It happens running both as normal user or root user. I've tried also to put a "hamster stop" script at rc0.d and rc6.d without luck.

Any solution/workaround for this?

[sm8ps]

Regarding the preference settings, it does work well here on Ubuntu 16.04 using hamster-indicator 0.1+037dd2e-0ubuntu2. I do, however, see the a similar faulty behavior when I put the computer into sleep mode: immediately after waking up, hamster shows the last current time (before sleep) for the active task. After a moment it seems to recalculate and adds the slept time interval to the active task. I have a feeling that this is may be due to the same cause which is why I do not put it into a report of its own. Edit: maybe the cause is similar to that of #247. In that case, it would make sense to create a wake-up script that would kill hamster-service and (re-)launch hamster-indicator/applet. I do not have much experience with that so I want to wait for some input before endeavoring into such a task.

[elbenfreund]

If I'm not mistaken this is a feature not a bug. Hamster tries to make sure that crashing you computer does not end tracking. Basically hamster records a start datetime and a enddatetime. Anything that happens in between will not have an effect. It is reasonable that this behavior may not match your expectations, please see the following about that.

Project hamster and its various sub-components is currently undergoing some major changes. We prepare the introduction of a rewritten codebase for most of the underlying functionality. A direct consequence of this is that it is unlikely that any open/new bugs within the current/old codebase will be fixed (unless someone steps up and offers to do so) as most resources currently available will be invested in making the rewrite prime time ready.

[sm8ps]

Thanks for your explanation, @elbenfreund, and thanks for relaunching this great software project! I did see the thread about the future of this project; nevertheless I thought it would be worthwhile to point this out. Maybe it should be seen now as a feature request for the future. IMHO it would be good to leave it up to the user to decide how to deal with interruptions of the system. I see both approaches making sense; still I do not see my system crashing as much as sending it to sleep mode. :) Cheers!

[elbenfreund]

@sm8ps I absolutely agree with what you are saying. Implementing a robust system to handle planed shutdown/sleep will require some additional work however, so I would not expect this to be worked on before we launch 1.0.0 which will try as much of the current feature set as possible.

Please keep an eye out for this and feel encouraged to file a feature request in hamster-gtk.

[sm8ps]

Thanks for your comment, @elbenfreund ! I shall keep my eyes open.

[ederag]

The "save" part (https://github.com/projecthamster/hamster/issues/265) seems fixed. And the ~/.gconf/apps/hamster-time-tracker permissions are correct now (as of d15e153a88552fc4a5388433f4334a105ac6f129). Changing the label from bug to enhancement.