Bug 170649 - kconf_update requires administrator privileges
Summary: kconf_update requires administrator privileges
Status: RESOLVED FIXED
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.1.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: KDE-Windows
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-08 01:05 UTC by Tim Schumacher
Modified: 2012-02-28 03:30 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Logfile for processmonitor (208.79 KB, application/zip)
2008-09-08 01:08 UTC, Tim Schumacher
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Schumacher 2008-09-08 01:05:29 UTC
Version:            (using KDE 4.1.0)
OS:                MS Windows
Installed from:    MS Windows

When starting amarok2 on kde-windows, kconf-update.exe is run, which requires administrator privileges. Canceling the request for higher privileges brings no visible dis- or advantage. The only thing is, that its very disturbing.

This is Windows Server 2008. I'll attach a file trace of process monitor.
Comment 1 Tim Schumacher 2008-09-08 01:08:32 UTC
Created attachment 27303 [details]
Logfile for processmonitor

Use Process Monitor (http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx) to see what kconf_updatee.exe does here.
Comment 2 Scott 2008-12-22 05:05:43 UTC
This has been a problem ever since I installed KDE 4.1.0 for Windows a number of months ago.

I'm running it on Windows Vista Ultimate (x64).
Comment 3 cerebro84 2008-12-22 13:46:32 UTC
Yes, it's a bit annoying having to give administrator privileges to kconf_update every time I want to run amarok...
Comment 4 Christian Ehrlicher 2008-12-28 18:10:52 UTC
This looks like a common UAC problem to me. The only solution can be found here: http://techbase.kde.org/Getting_Started/Build/KDE4/Windows/emerge#Vista_issues
If the solution with the .manifest file works too we can add such a file. I can't test it atm so it would be nice if someone else could do it for us.
Comment 5 Patrick Spendrin 2012-02-22 23:34:47 UTC
this should have been fixed now by adding a manifest to the file. Nevertheless kconf_update.exe will always fail on Windows and needs to be removed.
Comment 6 Kevin Kofler 2012-02-28 03:30:44 UTC
Working kconf_update is a prerequisite to have packages suitable for end users no matter what the platform. Otherwise their configuration can break and they'll have to reconfigure everything by hand. The updating tool exists for a reason. If you cannot get that to work on your OS, your packages will always suck.