Summary: | can't remove or disable any font | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | sts |
Component: | kcm_fontinst | Assignee: | Craig Drummond <craig> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Screenshot 1
Screenshot 2 |
Description
sts
2010-02-01 13:54:24 UTC
You say compiled from source - so is this really RC2, or is it from a later revision? i.e. do you have <kde install prefix>/lib/kde4/libexec/fontinst_helper ? Or just <kde install prefix>/lib/kde4/libexec/fontinst ? Shortly after RC2, I modified the code so as to use the KAuth framework - and not Policy kit directly. Also, is this with system or personal fonts? with rc3 I get a password question. If I enter my root password I get info can't authorize btw: I use the packages from http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openSUSE_11.2/ So, are you saying the original bug report is from RC2, and now you've upgraded to RC3? Or was the original report RC3 as well? I've just upgraded to RC3 here - and I don't even get asked for a password :-( Did you need to make any other changes to get the password prompt? i.e. did you need to change anything in the 'System policies' module? Can you alter the date and time settings? Because for me that kcm states that I will be asked for a password, but I'm never prompted for this when I press Apply - and no changes are made. the original report is maybe later from rc2. The repository source use also svn source. If I want to alter the date I get a login prompt, but also here the authorization doesn't work. Then this sounds more like a suse build issue, or a problem with KAuth. Created attachment 40474 [details]
Screenshot 1
Created attachment 40475 [details]
Screenshot 2
Not sure what was the point of those screenshots. You've already explanied what happens. However, if the same thing is a happening with the clock kcm - then it would appear to be a suse build issue, or a problem with the KAuth framework that both are using. ok thank you.. I have tested it with root also.. and with root I can't see any font. And he means scanning font list 0% wihout end. It's normal? As to the non-listing of fonts when run as root - thats a different bug! But I've just commited a fix for that. http://websvn.kde.org/?view=revision&revision=1084265 This is a issue with the openSUSE builds - as stated the clock kcm had problems with authorizations. Fixed in late builds. |