Description: kchildlock is a tool to monitor and restrict the time a children spends on the computer. The limits can be specified per day of the week, by lower and upper hour limits, maximum daily usage time, and maximum weekly usage time. The same restriction limits can be applied to applications based on the user login. It requires the KDE4 Desktop.Last changelog:
v0.91.1 * updates needed for packaging of actual versions (opensuse 13.x) * correct existing bugs for 64 bit versions of KDE * communicaiton wih DBUS now no more needs Console Kit, but standard functions in KDE * some minor rework done for the deamon (mainly get_active_session)
v0.90.4.2 * new greek translation by Dimitrios Glentadakis
v0.90.4.1 * common include file changed for opensuse 12.2 (compilation error)
v0.90.4 * new czech translation by Pavel Fric * bug fix: change layout of consumption file: every user record now has day_of_week and week_of_year. If supervising two or more children, the resetting of dayly or weekly values was only done for the current user; the others kept accumulated values. * bug fix: in some cases the limits for groups were not applied. (time duration). Only the first member of a group was restricted. * bug fix 3381398: prevent fclose on null pointer
v0.90.3 * bug fix: documentation compilation on Chakra repositores did not work * new russian translation by Z. Lezhnin * new ukrainian translation by Yuri Chornoivan * documentation updated
...on a Fedora 17 x86_64 box with kde 4.9.3 (kchildlock version 0.90)
sorry for posting it also in the knowledge base, this is where it should be maybe?)
It is installed, the interface comes up and lets you define limits, apply and save them, export profiles etc... just as explained in the documentation, no warning at all. Both when launched from the system settings panel and from the command line as /usr/bin/kcmshell4 kcm_kchildlock --lang en_US
then when the users whose sessions should be time-limited log in, nothing at all happens. No system tray icon and above all no block /logoff or whatever else should happen after the specified time limits.
files **are** created in /var/lock/, with names like kchildlockd_20121214_094614_debuglog.tmp, but they have no effect at all. No warning is generated in any moment, and I can't find any log file anywhere related to kchildlock. Is this app working for others??? How to debug it?
Thanks,
M
Please try with latest version 0.90.4.2 and install the 32bit version.
If that does not work, please send me the debug files under /var/opt/kchildlock/ including .kch_time.dat and /usr/share/kde4/config/kchildlockrc*
and /root/.kde4/share/config/kchildlockrc*
Very good idea!
kchildlock Mageia2 exist but the program work not correctly.
Ideas? Experiences? Help?
(sorry for my english; It is very limited!)
Thank
jeffans
Many thanks for your fine work on a much-needed application. It's straight-forward and intuitive, without sacrificing power and flexibility. I'm wondering if it would be possible to implement a "whitelist" feature, which would only allow certain programs to be run by a user, especially during a given time. Also, for the "Program Times" and "Program Duration" tabs, couldn't you give the option to add more programs than the imposed limit of five?
On kubuntu 11.04 64bit
When I start service :
Thread 1 (Thread 0x7f9a17d21780 (LWP 1330)):
[KCrash Handler]
#6 0x00007f9a155720e4 in fclose () from /lib/x86_64-linux-gnu/libc.so.6
#7 0x00007f99f0167e07 in ?? () from /usr/lib/kde4/kded_kchildlockdaemon.so
#8 0x00007f99f015d147 in KchildlockDaemon::startupTimePassed() () from /usr/lib/kde4/kded_kchildlockdaemon.so
#9 0x00007f99f015df4c in KchildlockDaemon::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/kde4/kded_kchildlockdaemon.so
#10 0x00007f9a169b25f8 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#11 0x00007f9a169b11c9 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#12 0x00007f9a15d5e9e4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#13 0x00007f9a15d633aa in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#14 0x00007f9a17719716 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#15 0x00007f9a1699d49c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#16 0x00007f9a169caf12 in ?? () from /usr/lib/libQtCore.so.4
#17 0x00007f9a169c7d18 in ?? () from /usr/lib/libQtCore.so.4
#18 0x00007f9a129fabcd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f9a129fb3a8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f9a129fb639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f9a169c83ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#22 0x00007f9a15e05dfe in ?? () from /usr/lib/libQtGui.so.4
#23 0x00007f9a1699c882 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#24 0x00007f9a1699cabc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#25 0x00007f9a169a0ecb in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#26 0x00007f9a078c8135 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so
#27 0x0000000000406dd3 in _start ()
Hope that help
please install the 32bit Version of kchildlock. If the problem persists, you can enable a debug log. To enable the logging function of the daemon, create a file '/var/opt/kchildlock/kchildlockd__debuglog.tmp' with any content. The generated log files will be named like '/var/opt/kchildlock/kchildlockd_yyyymmdd_HHMMSS_debuglog.tmp'.
Have a look at that file, or send it to me.
I saw a download link for Chakra in a TXT in SourceForge. I just wanted to say that it links to the script used to create the package, but a binary package created with it exists in the official repositories.
Maybe this is a better link for users: http://chakra-project.org/packages/index.php?act=search&subdir=&sortby=date&order=descending&searchpattern=kchildlock
Hello,
my question is. Can I use kchildlock as a router software on Kubuntu ?
I like to make a router with firewall and proxy server with ip adress connected to mac-Adress.
So will be nice to take this software connected to a ip adresss or a group of ip adresses too.
So it will be a nice way to block the connection by time for my child.
Thanks for your reply...
micky1067
I am getting following error while cmake -
CMake Error at /usr/share/cmake-2.8/Modules/FindKDE4.cmake:98 (MESSAGE):
ERROR: cmake/modules/FindKDE4Internal.cmake not found in
/home/kompkin/.kde/share/apps;/usr/share/kubuntu-default-settings/kde4-profile/default/share/apps;/usr/share/kde4/apps
Call Stack (most recent call first):
CMakeLists.txt:3 (find_package)
CMake Warning (dev) in CMakeLists.txt:
No cmake_minimum_required command is present. A line of code such as
cmake_minimum_required(VERSION 2.8)
should be added at the top of the file. The version specified may be lower
if you wish to support older CMake versions for this project. For more
information run "cmake --help-policy CMP0000".
This warning is for project developers. Use -Wno-dev to suppress it.
-- Configuring incomplete, errors occurred!
In the meantime there is a package for kubuntu on sourceforge. I generated it on launchpad, and in the control file there is a line included with dependencies:
Depends: ..., cmake (>= 2.6.2-1ubuntu1 ), ...
It compiled without problem with this line.
I Have a compilation problem on my Slackware 13.37.
This is the compiler output
[ 96%] Generating index.cache.bz2
index.docbook:12: warning: failed to load external entity "dtd/kdex.dtd"
]>
^
index.docbook:25: parser error : Entity 'language' not defined
<book lang="&language;">
^
index.docbook:25: element book: validity error : No declaration for attribute lang of element book
<book lang="&language;">
^
index.docbook:31: element application: validity error : No declaration for element application
<title>The &kchildlock; Handbook</title>
^
index.docbook:31: element title: validity error : No declaration for element title
<title>The &kchildlock; Handbook</title>
^
index.docbook:35: element firstname: validity error : No declaration for element firstname
<firstname></firstname>
^
index.docbook:36: element othername: validity error : No declaration for element othername
<othername></othername>
.
.
.
.
index.docbook:687: element book: validity error : No declaration for element book
</book>
^
make[2]: *** [doc/en/index.cache.bz2] Errore 1
make[1]: *** [doc/en/CMakeFiles/en-handbook.dir/all] Errore 2
make: *** [all] Errore 2
The system I have kchildlock installed on is an older piece of hardware with limited memory.
I have the users running the icewm desktop because it uses less memory than KDE. KDE4 is installed.
I would like to have the daemon running no matter what desktop they select (KDE, gnome, icewm, etc).
I'm running openSuSE 11.2.
Is there some way to get the daemon to autostart for any environment? Perhaps copy/move one of the .desktop files to /etc/xdg/autostart?
OK, I thought that was the case, but wanted to check.
I hope you will be able to incorporate it with other desktops. Many people seem to like gnome, icewm, etc, also.
I'm using icewm on the machine in question because it doesn't use as much memory and the machine only has 512MB of ram.
Will keep checking and looking for a new release.
Ratings & Comments
68 Comments
same for latest kde 4.10 fresh archlinux install. may be some dependences missed?
...on a Fedora 17 x86_64 box with kde 4.9.3 (kchildlock version 0.90) sorry for posting it also in the knowledge base, this is where it should be maybe?) It is installed, the interface comes up and lets you define limits, apply and save them, export profiles etc... just as explained in the documentation, no warning at all. Both when launched from the system settings panel and from the command line as /usr/bin/kcmshell4 kcm_kchildlock --lang en_US then when the users whose sessions should be time-limited log in, nothing at all happens. No system tray icon and above all no block /logoff or whatever else should happen after the specified time limits. files **are** created in /var/lock/, with names like kchildlockd_20121214_094614_debuglog.tmp, but they have no effect at all. No warning is generated in any moment, and I can't find any log file anywhere related to kchildlock. Is this app working for others??? How to debug it? Thanks, M
Please try with latest version 0.90.4.2 and install the 32bit version. If that does not work, please send me the debug files under /var/opt/kchildlock/ including .kch_time.dat and /usr/share/kde4/config/kchildlockrc* and /root/.kde4/share/config/kchildlockrc*
Confirm. On distros, who was migrated on systemd, dbus-query for consolekit don't work. It's need to be changed by query to logind.
Very good idea! kchildlock Mageia2 exist but the program work not correctly. Ideas? Experiences? Help? (sorry for my english; It is very limited!) Thank jeffans
Arch's package : https://aur.archlinux.org/packages.php?ID=32943
Many thanks for your fine work on a much-needed application. It's straight-forward and intuitive, without sacrificing power and flexibility. I'm wondering if it would be possible to implement a "whitelist" feature, which would only allow certain programs to be run by a user, especially during a given time. Also, for the "Program Times" and "Program Duration" tabs, couldn't you give the option to add more programs than the imposed limit of five?
Translation for the Greek language: http://glenbox.free.fr/files/kchildlock/el.po
thank you very much! It will be included with the next revision.
Still not included
Sorry, I forgot this! I am just now generating the rpms (with your translation). They are already on sourceforg.net Rene
On kubuntu 11.04 64bit When I start service : Thread 1 (Thread 0x7f9a17d21780 (LWP 1330)): [KCrash Handler] #6 0x00007f9a155720e4 in fclose () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x00007f99f0167e07 in ?? () from /usr/lib/kde4/kded_kchildlockdaemon.so #8 0x00007f99f015d147 in KchildlockDaemon::startupTimePassed() () from /usr/lib/kde4/kded_kchildlockdaemon.so #9 0x00007f99f015df4c in KchildlockDaemon::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/kde4/kded_kchildlockdaemon.so #10 0x00007f9a169b25f8 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #11 0x00007f9a169b11c9 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #12 0x00007f9a15d5e9e4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #13 0x00007f9a15d633aa in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #14 0x00007f9a17719716 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #15 0x00007f9a1699d49c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #16 0x00007f9a169caf12 in ?? () from /usr/lib/libQtCore.so.4 #17 0x00007f9a169c7d18 in ?? () from /usr/lib/libQtCore.so.4 #18 0x00007f9a129fabcd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007f9a129fb3a8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007f9a129fb639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007f9a169c83ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #22 0x00007f9a15e05dfe in ?? () from /usr/lib/libQtGui.so.4 #23 0x00007f9a1699c882 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #24 0x00007f9a1699cabc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #25 0x00007f9a169a0ecb in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #26 0x00007f9a078c8135 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so #27 0x0000000000406dd3 in _start () Hope that help
please install the 32bit Version of kchildlock. If the problem persists, you can enable a debug log. To enable the logging function of the daemon, create a file '/var/opt/kchildlock/kchildlockd__debuglog.tmp' with any content. The generated log files will be named like '/var/opt/kchildlock/kchildlockd_yyyymmdd_HHMMSS_debuglog.tmp'. Have a look at that file, or send it to me.
I saw a download link for Chakra in a TXT in SourceForge. I just wanted to say that it links to the script used to create the package, but a binary package created with it exists in the official repositories. Maybe this is a better link for users: http://chakra-project.org/packages/index.php?act=search&subdir=&sortby=date&order=descending&searchpattern=kchildlock
The link on SF has been corrected. thank you!
Hello, my question is. Can I use kchildlock as a router software on Kubuntu ? I like to make a router with firewall and proxy server with ip adress connected to mac-Adress. So will be nice to take this software connected to a ip adresss or a group of ip adresses too. So it will be a nice way to block the connection by time for my child. Thanks for your reply... micky1067
Sorry, but this software can NOT be used as a router software. It basically does the checks on local interactive users of the PC.
I am getting following error while cmake - CMake Error at /usr/share/cmake-2.8/Modules/FindKDE4.cmake:98 (MESSAGE): ERROR: cmake/modules/FindKDE4Internal.cmake not found in /home/kompkin/.kde/share/apps;/usr/share/kubuntu-default-settings/kde4-profile/default/share/apps;/usr/share/kde4/apps Call Stack (most recent call first): CMakeLists.txt:3 (find_package) CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as cmake_minimum_required(VERSION 2.8) should be added at the top of the file. The version specified may be lower if you wish to support older CMake versions for this project. For more information run "cmake --help-policy CMP0000". This warning is for project developers. Use -Wno-dev to suppress it. -- Configuring incomplete, errors occurred!
In the meantime there is a package for kubuntu on sourceforge. I generated it on launchpad, and in the control file there is a line included with dependencies: Depends: ..., cmake (>= 2.6.2-1ubuntu1 ), ... It compiled without problem with this line.
I Have a compilation problem on my Slackware 13.37. This is the compiler output [ 96%] Generating index.cache.bz2 index.docbook:12: warning: failed to load external entity "dtd/kdex.dtd" ]> ^ index.docbook:25: parser error : Entity 'language' not defined <book lang="&language;"> ^ index.docbook:25: element book: validity error : No declaration for attribute lang of element book <book lang="&language;"> ^ index.docbook:31: element application: validity error : No declaration for element application <title>The &kchildlock; Handbook</title> ^ index.docbook:31: element title: validity error : No declaration for element title <title>The &kchildlock; Handbook</title> ^ index.docbook:35: element firstname: validity error : No declaration for element firstname <firstname></firstname> ^ index.docbook:36: element othername: validity error : No declaration for element othername <othername></othername> . . . . index.docbook:687: element book: validity error : No declaration for element book </book> ^ make[2]: *** [doc/en/index.cache.bz2] Errore 1 make[1]: *** [doc/en/CMakeFiles/en-handbook.dir/all] Errore 2 make: *** [all] Errore 2
http://sourceforge.net/tracker/?func=detail&aid=3302040&group_id=238079&atid=1105478
Many thanks!
The system I have kchildlock installed on is an older piece of hardware with limited memory. I have the users running the icewm desktop because it uses less memory than KDE. KDE4 is installed. I would like to have the daemon running no matter what desktop they select (KDE, gnome, icewm, etc). I'm running openSuSE 11.2. Is there some way to get the daemon to autostart for any environment? Perhaps copy/move one of the .desktop files to /etc/xdg/autostart?
I don't think this is possible yet. The daemon is tigthly coupled to KDE mechanisms.
OK, I thought that was the case, but wanted to check. I hope you will be able to incorporate it with other desktops. Many people seem to like gnome, icewm, etc, also. I'm using icewm on the machine in question because it doesn't use as much memory and the machine only has 512MB of ram. Will keep checking and looking for a new release.