Mailinglist Archive: opensuse-bugs (3497 mails)

< Previous Next >
[Bug 860633] New: Strange PolicyKit1-Kde dialog asks for root password to change the "Folder Watch Limit"(?)
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 27 Jan 2014 18:04:30 +0000
  • Message-id: <bug-860633-21960@http.bugzilla.novell.com/>

https://bugzilla.novell.com/show_bug.cgi?id=860633

https://bugzilla.novell.com/show_bug.cgi?id=860633#c0


Summary: Strange PolicyKit1-Kde dialog asks for root password
to change the "Folder Watch Limit"(?)
Classification: openSUSE
Product: openSUSE Factory
Version: 13.2 Milestone 0
Platform: x86-64
OS/Version: openSUSE 13.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: carthexis@xxxxxxxx
QAContact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---


Created an attachment (id=576002)
--> (http://bugzilla.novell.com/attachment.cgi?id=576002)
Screenshot of the insane dialog

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101
Firefox/26.0

Some time after KDE startup I get the following annoying dialog:

PolicyKit1-KDE
An application is attempting to perform an action
that requires root privilges. Authentication is required
to perform this action

Password for root: [ ]
[X] Remember authorization
[ ] For this session only

Application:
Action: Folder Watch Limit
polkit.subject_pid: 2545
polkit.caller-pid: 3137

The programs in question seem to be:

$> ps ax | grep '2545\|3137'
2545 ? SNl 0:12 /usr/bin/nepomukfilewatch
3137 ? Sl 0:00
/usr/lib64/kde4/libexec/kde_nepomuk_filewatch_raiselimit

Why is something KDE/desktop related asking for my root password?
What could _possibly_ justify such an insanity?

Regards,
Lorenz

PS: I have openSUSE 13.1 with Tumbleweed, which is apparently not something one
can directly specify in this bugtracker(?)

Reproducible: Always

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
This Thread
  • No further messages