ROSA Linux Bugzilla – Bug 4791
Root password request for "PolicyKit1-KDE" appears suddenly
Last modified: 2016-12-21 02:34:37 MSK
Without any explicit action from my side, a dialog suddenly apeared requesting root password for "PolicyKit1-KDE"; additional details showed that the required action was "Folder Watch Limit".
By googling I found out that it may happen when desktop search engine exceeds inotify limits and requests for increase. It conforms with the fact that the dialog appeared shortly after I unpacked a large archive (Qt 5.4.0 sources with 146872 files/folders in it).
I think, such "unprovoked" request would look scary to users. As far as I could find, the suggested solution is to manually increase the fs.inotify.max_user_watches sysctl parameter (currently it is set to 8192) by writing to /proc/sys/fs/inotify/max_user_watches or (to keep it persistent across reboots) by creating additional conf file in /etc/sysctl.d/. Probably we should set it in our disribution to 16384 or even higher by default. Opinions?
+1 to increase the limit.
I've hit this problem too yesterday.
Additional information: 16384 is still too low, with this value I've got another request for increasing the value. So, 32768 is probably a preferred default.
Временное решение — воткнуть генерацию этого файла в генерацию образа.
Лучше засунуть в дефолтный параметр ядра.
(Отдельно найти, кто генерит этот конфиг).
На ТК решили — 32768.
BTW, /etc/sysctl.d/97-kde-baloo-filewatch-inotify.conf is present on my system and does exactly that: sets fs.inotify.max_user_watches = 32768.
That's exactly what this "PolicyKit1-KDE" does: creates this file with new value.
(In reply to comment #6)
> That's exactly what this "PolicyKit1-KDE" does: creates this file with new
I see. On another system, this file sets the limit to 65536, by the way, I cannot say why.
I added the patch to the kernel 3.14.31 I am currently testing. However, I am not sure if it is needed now that PolicyKit1-KDE or, Baloo, or whatever seems to handle the issue.
What do you think?
The way it handles the issue is unintuitive and scary. Average user won't understand why root permission request suddenly appeared, what it intends to do, what program displayed it, and, generally, what the hell is going on. I suggest that we set this value in the kernel, so that much less users found themselves facing this situation.
Ah, I thought, someone has figured out how to handle this automagically. I see.
Anyway, I have already added the kernel patch to increase the default limit. Will appear in kernel 3.14.31.
Still, I don't think this is a good solution. Better to do it in userspace. Perhaps, to provide that file in /etc/sysctl.d with Polkit packages, or Baloo, or whatever.
Increased the limit in the kernel. Kernel 3.14.33 has the appropriate patch.
Again, my opinion is, it should be rather fixed in PolicyKit or whatever is involved.
Please see http://bugs.rosalinux.ru/show_bug.cgi?id=7608
I AM WORRIED