497978 – kde-base/nepomuk-core-4.11.5 tries to raise inotify max_user_watches although it is already raised

Bug 497978 - kde-base/nepomuk-core-4.11.5 tries to raise inotify max_user_watches although it is already raised

Summary: kde-base/nepomuk-core-4.11.5 tries to raise inotify max_user_watches although...

Status:	RESOLVED OBSOLETE

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] KDE (show other bugs)
Hardware:	All Linux

Importance:	Normal trivial
Assignee:	Gentoo KDE team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-01-13 10:06 UTC by Fabian Köster
Modified:	2014-02-25 21:00 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Fabian Köster 2014-01-13 10:06:11 UTC

After every login KDE executes /usr/lib64/kde4/libexec/kde_nepomuk_filewatch_raiselimit and tries to get user the rights using Polkit to install /etc/sysctl.d/97-kde-nepomuk-filewatch-inotify.conf although it is already present and /proc/sys/fs/inotify/max_user_watches is already set to 32768. This should only happen once and the code should check if limit is already raised before showing the polkit dialog.

I will look into the code when I have some time and try to provide a patch.

Reproducible: Always

Comment 1 Michael Palimaka (kensington) gentoo-dev

2014-02-25 19:28:00 UTC

Can you please provide some more information, such as emerge --info and the specific error messages you are receiving?

(I am having difficulty reproducing, for example I do not have any KDE-related files installed into /etc/sysctl.d)

Comment 2 Fabian Köster 2014-02-25 21:00:26 UTC

I am not sure when it happened but this problem does not occur anymore on my system. 

I hope I did not forget some workaround I may have created. I am closing this bug now and will reopen it in case the issue reappears.