I've just updated to 4.11 beta1, Arch Linux packages, and on the next login, I got a polkit window asking me for administrative privileges for an unnamed, undocumented program. The only available information was the pid from the calling process, which turned out to be: /usr/lib/kde4/libexec/kde_nepomuk_filewatch_raiselimit after a quick 'ps aux | grep $PID'. I could not found in the nepomuk KCM where to change this limit manually. Could you improve this dialog / add more informations / add an option somewhere in the nepomuk KCM ? Thanks Reproducible: Always Steps to Reproduce: 1. Update to 4.10.80 2. Log-off / log-on 3. Get the polkit dialog As the 'Don't ask me anymore' checkbox was struck, I probably won't get this dialog box anymore. If you know of a way to revert this, I'll gladly give a screenshot of the dialog. Actual Results: Undocumented / unspecified dialog box with no help to decide if the action is legitimate. Expected Results: Short message telling me it's nepomuk and what it wants to do.
Created attachment 80526 [details] polkit window The polkit dialog I got each time I log in my KDE session.
Created attachment 80527 [details] processes corresponding to PID in the dialog Quick 'ps aux | grep' to find the processes corresponding to PID in the polkit dialog
I'm not sure what to change the text to. The description has been set, but that doesn't seem to be getting displayed. Btw, your Nepomuk installation is completely broken, and indexing will not work for you properly since your inotify limit is too low. You might want to increase it - /proc/sys/fs/inotify/max_user_watches Increase it to at least the number of directories you have. Ideally, double the number of directories would be best.
I chose to index only my "Documents" folder: $ find Documents -type d | wc -l 182 which is still well under: $ cat /proc/sys/fs/inotify/max_user_watches 16384 I can not find where nepomuk stores which folders it is indexing to confirm that the "Documents" folder is the only one really being indexed.
I also tried running 'nepomukindexer Documents' and everything was ok (there was no output and return code was 0).
It doesn't matter what has been set for indexing, we need to create a watch for each directory in order to make sure tags are never lost. You can always tag a file which is not in an indexed directory.
Ok, but the thing is that I don't remember ever tagging any file explicitly. I've tried using the nepomukshell tool to get a list of files with tags, but didn't find it (maybe I missed it?). Any other option to find out why I need such a high filewatch value ?
Workaround suggested in https://bugs.kde.org/show_bug.cgi?id=321495
Am i correct that this is still not fixed? I am using KDE 4.11 with Ubuntu from the KDE Backports PPA, i still get the message.
Created attachment 81869 [details] Message in KDE 4.11 still confusing
I am also getting this error. It has only started happening recently after an update to 4.11.2 on gentoo. The polkit kcm package on gentoo is being phased out and masked, I removed it so that may have something to do with the password prompt I am seeing. Does not seem to have any negative behaviour, but still very annoying.
(In reply to comment #11) > I am also getting this error. It has only started happening recently after > an update to 4.11.2 on gentoo. Correction, this bug is not an error. Sorry. I tried things such as removing directories in my home folder, unchecking watched folders in the strigi indexer kcm module, but I would still get the polkit window. Eventually I just added the following line into my /etc/sysctl.conf file: fs.inotify.max_user_watches=24000 The value is greater than the number of directories in my home folder. That resolved the issue for me.
Thank you for taking the time to file a bug report. The Nepomuk project is no longer included in the KDE Software Compilation. With Plasma 5, we have replaced most of the underlying technology with Baloo and other components. Hopefully this will have addressed your concern. We encourage you to try to Plasma 5 (+Baloo) and let us know if your problem persists.