Description of problem: After a fresh install of mageia 4 I installed gparted. Didn't startup from gui. Didn't startup from shell - neither as user nor as root. Error-Message: "Error getting authority: Could not connect: No such file or directory Version-Release number of selected component (if applicable): gparted-0.16.2-2.1.mga4 How reproducible: always Steps to Reproduce: 1.fresh install 2.install gparted 3.start gparted I could fix the problem by installing gksu-polkit-0.0.3-0.git20131130.9.mga4 Reproducible: Steps to Reproduce:
Summary: dependency to gksu is obviously missing in the package => dependency to gksu is obviously missing in the package gparted-0.16.2-2.1.mga4
had to reboot after installing gksu
it should not be needed if you have a polkit agent, which should be the case cf https://bugs.mageia.org/show_bug.cgi?id=11745 where it was fixed Does mcc open it good ?
I have used the netinstaller of Mageia 4 - doing a fresh install keeping only the /home partition. I selected kde as desktop during the netinstall which supposedly should have installed the polkit-kde package (haven't checked that so far). After the install was finished, system rebooted and I logged on (kde) and used mcc to install some additional packages - (no gnome-related ones afaik). Everything worked fine, no hickups. After the installation of gparted nothing happened when I clicked on the gparted icon. I opened a terminal, tried to start from shell - got the error message above. I ran journalctl -f in a parallel terminal - no message! Logged in as root: same story. Didn't search for any bugs here at that time but following an intuition I looked for the gksu-package and I installed it. I did a reboot as the mcc did not open after the installation. After the reboot everything was fine.
sorry forgot this one: I *had* seen the problem in the Mageia 4 errata on the wiki page - but the package update published in https://advisories.mageia.org/MGAA-2014-0083.html *was* already installed.
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/
As announced over a month ago, 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. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know 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. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 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/
Status: NEW => RESOLVEDResolution: (none) => OLD