Timekpr-nExT

unexpected error updating configuration. Please inspect Timekpr-nExT log files

Asked by Xudong Sun

When I click apply daily limit in the timekpr admin app, it said unexpected error updating configuration. Please inspect Timekpr-nExT log files

ls /tmp/
timekpra.root.pid timekprc.sunxd.log timekprd.pid
timekpra.su.log timekprc.sunxd.pid

cat timekprc.sunxd.log

2022-01-28 07:17:03.261649: start initializing client configuration manager
2022-01-28 07:17:03.261883: finish initializing client configuration manager
2022-01-28 07:17:03.272381: starting up timekpr client
2022-01-28 07:17:03.272415: start initTimekprIndicator
2022-01-28 07:17:03.272430: start init timekpr indicator
2022-01-28 07:17:03.272447: start init timekpr notifications
2022-01-28 07:17:03.273201: finish init timekpr notifications
2022-01-28 07:17:03.656835: finish init timekpr indicator
2022-01-28 07:17:03.656879: finish initTimekprIndicator
2022-01-28 07:17:03.656896: start initTimekprIndicatorIcon
2022-01-28 07:17:03.671175: finish initTimekprIndicatorIcon
2022-01-28 07:17:06.528991: INFO: dbus connection to screensaver delayed for 1 more times
2022-01-28 07:17:06.529606: requesting timelimits
2022-01-28 07:17:06.531857: requesting timeleft
2022-01-28 07:17:09.511594: INFO: using gnome screensaver dbus interface as a workaround
2022-01-28 07:33:24.930687: requesting session attributes
2022-01-28 07:33:25.094817: verifying session attributes
2022-01-28 07:33:29.510385: verifying session attributes
2022-01-28 07:33:38.530682: verifying session attributes
2022-01-28 07:33:47.539773: verifying session attributes
2022-01-28 07:33:50.568393: requesting session attributes
2022-01-28 07:33:50.629510: verifying session attributes

cat timekpra.sunxd.log
2022-01-28 07:50:06.763725: initializing configuration manager
2022-01-28 07:50:06.763901: finish configuration manager

Question information

Language:
English Edit question
Status:
Answered
For:
Timekpr-nExT Edit question
Assignee:
Eduards Bezverhijs Edit question
Last query:
Last reply:
Revision history for this message
Eduards Bezverhijs (mjasnik) said : 		#1

Which version of the app are you using?

Revision history for this message
Xudong Sun (sunxd) said : 		#2

The timekpr client is 0.5.2, I did not mange to figure out the version for the admin app.

Revision history for this message
Eduards Bezverhijs (mjasnik) said : 		#3

Well, please look into /var/log/timekpr.log, it looks like the error is there...
Although, I have never heard a situation when config files just blew up on their own :)

Did you went to config files and changed them by hand or the like?

Revision history for this message
Xudong Sun (sunxd) said : 		#4

ah, sorry, forgot the other log file,

2022-01-28 08:00:46.290930: Unexpected ERROR (setAllowedHours): int() argument must be a string, a bytes-like object or a number, not 'NoneType '¬

To be honest, I did not change the configure file for a long time.

Revision history for this message
Eduards Bezverhijs (mjasnik) said : 		#5

Please get the log file /var/log/timekpr.log (not just the error) and config files /var/lib/timekpr/*, zip them up and upload somewhere I can get them, so I can take a look at them.

Revision history for this message
Xudong Sun (sunxd) said : 		#6

https://drive.google.com/file/d/1UgwyXNWjQzGzKJqkuK-XJJnpXdKdN3uA/view?usp=sharing

Revision history for this message
Eduards Bezverhijs (mjasnik) said (last edit ): 		#7

I checked the log file, I did not see any errors there...

Please reproduce the error, mention steps and values you tried to enter (or make a screenshot right after the error) and then grab log files and share. If there is no error and I don't know what you did (including values), I'm unable to reproduce the error locally and won't be able to help.

Revision history for this message
Eduards Bezverhijs (mjasnik) said : 		#8

Had you encountered the issue yet?

Revision history for this message
Xudong Sun (sunxd) said : 		#9

Hi,
    I guess the error just occurred but does not affect the use.
    I did not try yet since I finish work on time now :)

On Tue 15. Feb 2022 at 16:10, Eduards Bezverhijs <
<email address hidden>> wrote:

> Your question #700424 on Timekpr-nExT changed:
> https://answers.launchpad.net/timekpr-next/+question/700424
>
> Eduards Bezverhijs requested more information:
> Had you encountered the issue yet?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/timekpr-next/+question/700424
>
> You received this question notification because you asked the question.
>

Revision history for this message
Eduards Bezverhijs (mjasnik) said : 		#10

.

Can you help with this problem?

Provide an answer of your own, or ask Xudong Sun for more information if necessary.

To post a message you must log in.