timekpr-revived

Can not read configuration

Bug #1802583 reported by korpenkraxar
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
timekpr-revived
Fix Released
Critical
Eduards Bezverhijs

Bug Description

Thanks for a great project!

However, I can not get this to work on either of two user accounts in Ubuntu 18.04 (using Gnome and GDM). I have activated the system tray in the Unite Gnome extension and can interact with the icon and configure and reload the account access times.

I have verifyed that information seemingly sensible information is written to /etc/timekpr/myuser and /etc/security/time.conf and that it is readable by myuser. Unfortunately, I get a Gnome notification popup every 30 seconds that says:

Can not read configuration, time left is unknown at the moment...
Please wait a little for configuration to be initialized...

Any ideas?

Cheers!

Revision history for this message
Nicolai (nschira) wrote :

I can confirm this behaviour:

running on Ubuntu 16.04, using Gnome and Lightdm, I did a fresh install of timekpr 0.3.7.

On the parents side, the icon is available in the system tray and everything works fine. You can enter time limitations for the childs account, and they are stored correctly.

On the childs side, timekpr is displaying a red icon saying, time left is 0 minutes, and every minute or so, the error message mentioned by korpenkraxar appears.

Files /etc/timekpr/CHILDUSER and /etc/security/time.conf are readable by everybody.

No ideas how to proceed...

Thanks for hints!

Revision history for this message
Yuji Kawahara (you2develop) wrote :

I had been the same situation, but fix it.

The modification in this commit was seem incorrect.
 https://bazaar.launchpad.net/~mjasnik/timekpr-revived/trunk/revision/32/support/bin/users.timekpr

I just fix in line 6 to
 loginctl list-users | grep -E '^ *[0-9]+ +[a-z_][a-z0-9_-]*[$]? *$' | sed 's/^ \+//' | cut -d' ' -f2 | sort | uniq | \

I hope this will help.

Revision history for this message
Eduards Bezverhijs (mjasnik) wrote :

Hi, indeed, this is the problem. It worked on my computer.
I'll roll out a fix soon.

Changed in timekpr-revived:
importance: Undecided → Critical
assignee: nobody → Eduards Bezverhijs (mjasnik)
status: New → Confirmed
Eduards Bezverhijs (mjasnik)
Changed in timekpr-revived:
status: Confirmed → Fix Committed
Eduards Bezverhijs (mjasnik)
Changed in timekpr-revived:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.