Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 328007 - kde-base/systemsettings-4.5* does not work with kdesu anymore, only policykit
Summary: kde-base/systemsettings-4.5* does not work with kdesu anymore, only policykit
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: High normal with 1 vote (vote)
Assignee: Gentoo KDE team
URL: https://bugs.kde.org/show_bug.cgi?id=...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-12 21:53 UTC by Nikos Chantziaras
Modified: 2011-03-12 13:16 UTC (History)
2 users (show)

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


Attachments
emerge --info (emerge-info,4.23 KB, text/plain)
2010-07-12 21:54 UTC, Nikos Chantziaras
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nikos Chantziaras 2010-07-12 21:53:46 UTC
I'm on KDE SC 4.5 RC2 (4.4.92). I've also opened a bug about this upstream:

https://bugs.kde.org/show_bug.cgi?id=244444

I'm trying to change the KDM configuration. Since there doesn't seem to be a
way to do that from the KDE GUI, I have to resort to the terminal and do:

kdesu systemsettings

However, when I hit "Apply" nothing happens.  When I then try to quit
systemsettings, it tells me that I didn't apply the settings.  I hit "Apply"
there too, but I get an error dialog saying:

Unable to authenticate/execute the action:  (code 2)

Reproducible: Always

Steps to Reproduce:
Run "kdesu systemsettings".
Change any "Login Manager" setting and hit "Apply".
Quit, and in the dialog that pops up hit "Apply".

Actual Results:  
Error message.

Expected Results:  
Applying of new settings.

Kernel 2.6.34.1
Qt 4.7.0 Beta 2
KDE SC 4.5 RC2 (4.4.92)
Comment 1 Nikos Chantziaras 2010-07-12 21:54:14 UTC
Created attachment 238515 [details]
emerge --info
Comment 2 Nikos Chantziaras 2010-07-12 22:55:23 UTC
Upstream explained to me that with KDE 4.5, "kdesu systemsettings", which was working in KDE 4.4, is not supported anymore.  PolicyKit is needed to change settings now.  I had the "policykit" USE flag disabled globally.  I suppose an emerge message informing the user of this change might be a good idea, because the error message "Unable to authenticate/execute the action:  (code 2)" is not exactly verbose about the nature of the problem. Only if the USE flag is disabled of course.
Comment 3 Nikos Chantziaras 2010-07-13 19:47:47 UTC
I've enabled the "policykit" USE flag for kdelibs and consolekit (I don't need consolekit but policykit seems to need it), and the "consolekit" USE flag for KDM with these in package.use:

  kde-base/kdelibs policykit
  sys-auth/consolekit policykit
  kde-base/kdm consolekit

However, it still doesn't work.  The error message changed though:

Unable to authenticate/execute the action:  (code 3)

(Note that it was "code 2" before.)

What is happening?  It should work.
Comment 4 Sergey Kondakov 2010-08-13 17:18:58 UTC
i can confirm that.
policykit is such a nasty thing :(
Comment 5 Nikos Chantziaras 2010-08-13 17:28:17 UTC
This got fixed for me somewhere along the way.  It was probably due to a full rebuild of all KDE packages when I updated from 4.5.0 RC3 to the final 4.5.0.

That probably means that some package should have been rebuilt when changing the USE flags, but didn't.  I don't know which...
Comment 6 maneesh singh 2010-09-11 06:08:47 UTC
The package that you needed to rebuild is kde-base/systemsettings. I faced a similar issue in kde 4.5.1 in ~amd64 branch.
Comment 7 Andreas K. Hüttel archtester gentoo-dev 2010-11-13 21:26:47 UTC
OK summarizing, 
* when you flip policykit useflags you may need to rebuild packages
* -policykit is not supported upstream for kde-4.5
Comment 8 Nikos Chantziaras 2010-11-13 21:58:30 UTC
(In reply to comment #7)
> OK summarizing, 
> * when you flip policykit useflags you may need to rebuild packages
> * -policykit is not supported upstream for kde-4.5

I get confused about policykit and polkit.  Anyway, it doesn't matter.  What matters is that enabling the policykit USE flag, portage correctly triggered a rebuild of some packages and also pulled-in polkit (but not policykit) as a dep. But it missed some packages that needed to be rebuilt.  Could be just kde-base/systemsettings, as #6 mentions, could be more; I have no idea.  The only sure thing is that flipping the USE flag misses some packages that need to be rebuilt.

Comment 9 Kamen Dokov 2010-11-23 21:42:37 UTC
Well I rebuild my world 3 times in vain. The result is still:
"Unable to authenticate/execute the action:  (code 2)"

And I still can`t reboot/log off/shutdown the system from my user account :(
Comment 10 MrPenguin07 2010-12-30 10:07:23 UTC
I believe I am affected by this, albeit with upgraded package versions. I have had policykit enabled since ~kde 4.4 and have only had the problem since the >=4.5.85 releases.

I can start systemsettings successfully with either kdesu or from the gui however upon activating autologin for a user and applying, while exiting back to 'overview' the save,discard,exit dialog returns the error "Unable to authenticate/execute the action:  (code 2)" - thus I can't save my settings.

[I-O] [  ] kde-base/kdelibs-4.5.90:4.6
[I-O] [  ] kde-misc/polkit-kde-kcmodules-9999:4
[IP-] [  ] sys-auth/polkit-0.99-r1:0
[I-O] [  ] sys-auth/polkit-kde-agent-9999:4
[I-O] [  ] sys-auth/polkit-qt-9999:0

kdelibs and consolekit are both built with +policykit. 
Comment 11 Kamen Dokov 2011-02-05 23:19:29 UTC
(In reply to comment #10)
> I believe I am affected by this, albeit with upgraded package versions. I have
> had policykit enabled since ~kde 4.4 and have only had the problem since the
> >=4.5.85 releases.
> 
> I can start systemsettings successfully with either kdesu or from the gui
> however upon activating autologin for a user and applying, while exiting back
> to 'overview' the save,discard,exit dialog returns the error "Unable to
> authenticate/execute the action:  (code 2)" - thus I can't save my settings.
> 
> [I-O] [  ] kde-base/kdelibs-4.5.90:4.6
> [I-O] [  ] kde-misc/polkit-kde-kcmodules-9999:4
> [IP-] [  ] sys-auth/polkit-0.99-r1:0
> [I-O] [  ] sys-auth/polkit-kde-agent-9999:4
> [I-O] [  ] sys-auth/polkit-qt-9999:0
> 
> kdelibs and consolekit are both built with +policykit. 
> 

kde-4.6 behaves in same way!
Comment 12 Franz Trischberger 2011-03-12 06:43:01 UTC
Does it help, if you rebuild qt-core and qt-gui with enabled glib-USE-Flag?
Comment 13 Kamen Dokov 2011-03-12 08:24:10 UTC
(In reply to comment #12)
> Does it help, if you rebuild qt-core and qt-gui with enabled glib-USE-Flag?

Well, found the source of my problem. It was copy/paste problem.I found out that i was compiling  kdelibs with -policykit all the time! That forgotten '-' sign tormented me for 3 months :(
I'm sorry for the inconvenience.