Cannot use all the weekly timeslot selected

Hi there,

I have the latest version of the application (2.10) running on my XUbuntu desktop. Initially I configured weekly schedule with couple of days using the GUI and once I understood how the app works, I added schedule for rest of the week, again using the GUI. But then the set schedules were not working, including the old ones. So I manually modified the user config file /var/lib/timekpr/config/timekpr.<user id>.conf. Now the app is letting user access his desktop on certain set schedule on some days, but not on other days. See the config file attached below.

So, I want to find out

(1) if the app caches the config after reading it from the user config file, and if that's the case, is there a way to delete that cache so that it can pick up the updated config in the text format?

(2) Also, does the app log error somewhere for debugging purpose? I want to make sure the app is able to read the user config in the text format I am using.

Thanks.

prateek@aruba:~/stuff$ cat /var/lib/timekpr/config/timekpr.nitin.conf
[DOCUMENTATION]
#### this is the user configuration file for timekpr-next
#### if this file can not be read properly, it will be overwritten with defaults

[nitin]
# this defines which hours are allowed (remove or add hours to limit access), configure limits for start/end minutes for hour in brackets, example: 22[00-15]
ALLOWED_HOURS_1 = 17[30-60];18[0-15]
ALLOWED_HOURS_2 = 17[30-60];18[0-15];22[0-30]
ALLOWED_HOURS_3 = 17[30-60];18[0-15]
ALLOWED_HOURS_4 = 17[30-60];18[0-15]
ALLOWED_HOURS_5 = 17[30-60];18[0-15]
ALLOWED_HOURS_6 = 10;11
ALLOWED_HOURS_7 = 10;11
# this defines which days of the week a user can use computer (remove or add days to limit access)
ALLOWED_WEEKDAYS = 1;2;3;4;5;6;7
# this defines allowed time in seconds per week day a user can use the computer
LIMITS_PER_WEEKDAYS = 2700;2700;2700;2700;2700;7200;7200
# this defines allowed time per week in seconds (in addition to other limits)
LIMIT_PER_WEEK = 604800
# this defines allowed time per month in seconds (in addition to other limits)
LIMIT_PER_MONTH = 2678400
# this defines whether to account sessions which are inactive (locked screen, user switched away from desktop, etc.)
TRACK_INACTIVE = False