Description of problem: Lauching drakconf as an ordinary user just produces "pkexec must be setuid root" and the user is not asked for the root password. Version-Release number of selected component (if applicable): Version : 12.50 Release : 1.mga4 How reproducible: Always. Steps to Reproduce: 1.In a terminal, being not root, launch "drakconf". OR 1. Click on the Mageia control center icon (either in the menu or in the tool board at the bottom of the screen.). Expected: as in Mageia 3, a dialogue small window should ask for the root password. Note: the workaround ("su") is only easy for those who know the command name ("drakconf"), which is probably a minority of Mageia users. Reproducible: Steps to Reproduce:
Is this fresh install or upgrade from mga3? The problem is not in drakconf but for some reason your pkexec command is missing setuid. What is the output of this command: ls -l /usr/bin/pkexec
Keywords: (none) => NEEDINFOCC: (none) => mageia, mageiaSource RPM: drakconf-12.50-1.mga4.src.rpm => (none)
(In reply to Sander Lepik from comment #1) > What is the output of this command: > ls -l /usr/bin/pkexec and "rpm -V polkit"
Ah! Thank you. So this is probably related with the upgrade story: https://bugs.mageia.org/show_bug.cgi?id=12375 # ls -l /usr/bin/pkexec -rwxr-xr-x 1 root root 24264 Oct 19 20:23 /usr/bin/pkexec* # rpm -V polkit .M....... /usr/bin/pkexec .M....... /usr/lib/polkit-1/polkit-agent-helper-1 .....U... /usr/share/polkit-1/rules.d
Yeah, so you'll need to do the following (as root) to fix your polkit install: chmod u+s /usr/bin/pkexec /usr/lib/polkit-1/polkit-agent-helper-1 to get polkit working again.
Status: NEW => RESOLVEDResolution: (none) => WORKSFORME
That said, I cannot see why your upgrade would cause problems here. It's almost like the disk is mounted with a nosetuid option...
Thank you very much: the MCC icon works now. In /etc/fstab , I have # Entry for /dev/sda1 : UUID=6f3a595c-4539-4935-8fb6-7b7cf085820c / ext4 acl,relatime 1 1 # Entry for /dev/sda6 : UUID=92e72b01-2378-46bf-bcd7-88c4a0614314 /home ext4 acl,relatime 1 2 none /proc proc defaults 0 0
Resolution: WORKSFORME => FIXED
Yeah if you can fix it with current mounts then all is well, but it's confusing as to how it got into the non-setuid state during upgrade :s It's almost like the installer was not allowed to write the setuid bits... perhaps *it* mounted it with nosetuid? We'd get all kinds of errors that way tho' :s