First of all please excuse me, if I do anything wrong, for it is the first time I report a bug, and my english is far away fom being perfect. I described the bug already in bug 11184, but Colin Guthrie told me to open a new bug, so that's what I do here again. Description of problem: I installed Mageia 4 a week ago with LXDE as the only Desktop. I noticed the error (bug 11184) is only fixed for the user who logs in first. After logging out a logging in of a second different user, this user has the same problem as decribed above. To describe the problem more detailed, I will explain how to reproduce the bug for two users called A and B. I start the system and log in user A. This user can start all programs which require root privilegies from the gui, after inserting root password in the gui-window. Then I log user A out, and log user B in (without rebooting the system) User B is now not able to start programs which require root privilegies from the gui, not even a window asking for root password opens. Then I log user B out, and log user A in again(without rebooting the system) User A again can start all programs which require root privilegies from the gui, after inserting root password in the gui-window. If I reboot and do the procedure it vice versa, the bug apears vice versa: I log in user B first. This user can start now all programs which require root privilegies from the gui, after inserting root password in the gui-window. Then I log user B out, and log user A in (without rebooting the system) User A is now not able to start programs which require root privilegies from the gui, not even a window asking for root password opens. Then I log user A out, and log user B in again(without rebooting the system) User B again can start all programs which require root privilegies from the gui, after inserting root password in the gui-window. addionally I paste comment # 99 from bug 11184: (In reply to Colin Guthrie from comment #97) > Interesting. > > Can you check if "polkit-mate-authentication-agent-1" is running for the > second user? If not, can you try starting it manually in a terminal by > typing: /usr/libexec/polkit-mate-authentication-agent-1 > > Just leave that term open and then try and and run some apps that need auth. > Hopefully this now works. If it does, then it could simply be a (different) > bug in the autostart handling used in LXDE. polkit-mate-authentication-agent-1 did not run for the second user. starting it as second user failed: Gtk-Message: Failed to load module "canberra-gtk-module" ** (polkit-mate-authentication-agent-1:3242): WARNING **: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs. Cannot register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs. after starting it as root I could start programs that need root auth. from panel (after inserting root pw) and from menu Reproducible: Steps to Reproduce:
Summary: MCC does only start from launchers for the first user logged in in LXDE but does from cli (polkit) => MCC does only start from launchers for the first user logged in in LXDE but does only from cli for user who lods in afterwords (polkit)
Component: Release (media or process) => RPM Packages
Summary: MCC does only start from launchers for the first user logged in in LXDE but does only from cli for user who lods in afterwords (polkit) => MCC does only start from launchers for the first user logged in in LXDE but does only from cli for user who logs in afterwords (polkit)
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
(In reply to Michael Engel from comment #0) > > I installed Mageia 4 a week ago with LXDE as the only Desktop. I noticed the > error (bug 11184) is only fixed for the user who logs in first. After > logging out a logging in of a second different user, this user has the same > problem as decribed above. Sounds pretty much exactly like https://bugs.mageia.org/show_bug.cgi?id=16396 except that this should only be valid with Mageia 5 but a similar issue could apply for Mageia 4. Please show the output of cat /run/systemd/users/$(id -u) for the user where it fails to start. If it shows STATE=online then the above bug applies, and you can test the update candidate for Mageia 5, and we can resolve this as a duplicate.
Status: NEW => UNCONFIRMEDCC: (none) => doktor5000Ever confirmed: 1 => 0
Closing as OLD, in case it still happens with Mageia 5 please reopen and update the bug as mentioned in comment 1 and 2.
Status: UNCONFIRMED => RESOLVEDResolution: (none) => OLD