Summary: | kconf_update requires administrator privileges | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Tim Schumacher <tim> |
Component: | general | Assignee: | KDE-Windows <kde-windows> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | cerebro84, Ch.Ehrlicher, geekboy, kde-windows, zahl |
Priority: | NOR | ||
Version: | 4.1.0 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Logfile for processmonitor |
Description
Tim Schumacher
2008-09-08 01:05:29 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. 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). Yes, it's a bit annoying having to give administrator privileges to kconf_update every time I want to run amarok... 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. 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. 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. |