4alpha2 dualcd with default installation (razorqt) DualCD with openbox or razorqt has 'Install & Remove Software' in the menu but rpmdrake is not available Reproducible: Steps to Reproduce:
Whiteboard: (none) => 4alpha2
rpmdrake is there, but is failing to start. With no terminal program, no messages in .xsession-errors, or in journalctl, though, figuring out why is difficult.
CC: (none) => davidwhodgins
still valid pre-alpha3. rpmdrake is still installed.
CC: (none) => marja11Whiteboard: 4alpha2 => 4alpha3
Noticed this in several light DE's eg. IceWM, LXDE & RazorQT MCC & rpmdrake fail to start from launchers but can be started from cli
CC: (none) => eeeemail
Summary: DualCD has Install & Remove Software in the menu but no rpmdrake => MCC doesn't start from launchers in several light DE but does from cli
(I have no ideas how to bug more)
Priority: Normal => release_blockerCC: (none) => thierry.vignaud
Side effect of migration to polkit?
CC: (none) => mageia
Likely due to not running a GUI polkit authorisation agent. We likely need to do so via some kind of dbus activation or xinit.d/ drop-in which is a noop on desktops that properly provide proper infrastructure. Likely a dupe of bug #11304 ?
I note that LXDE is mentioned above, but we do have lxpolkit package. Is this installed? If not, does installing it make things work on LXDE?
in razorqt (installed from the dual) even running it in a terminal open a popup asking credential but not with the .desktop lib64polkit-qt-core and lib64polkit-qt-agent are installed
Also there is a /usr/bin/lxpolkit in lxsession... what does this binary do? Is it a duplicate of lxpolkit? As there are few deps (just gtk), perhaps we could use lxpolkit as our fallback authorisation agent?
(In reply to Manuel Hiebel from comment #8) > in razorqt (installed from the dual) even running it in a terminal open a > popup asking credential but not with the .desktop > > lib64polkit-qt-core and lib64polkit-qt-agent are installed So some kind of authorisation agent is running then. Perhaps you could find out which one. It should be listening on dbus...
*** Bug 11365 has been marked as a duplicate of this bug. ***
CC: (none) => fx
*** Bug 11322 has been marked as a duplicate of this bug. ***
Created attachment 4401 [details] How make the launcher drakconf OK Drakconf launcher works normally when StartUpNotify is True in file .desktop under XFCE4.
CC: (none) => bernard.al1
I am having this as well with Xfce. I tried changing StartUpNotify to True, but it didn't help. Running "xdg-open mcc.desktop," I see: "Refusing to render service to dead parents." Starts OK under KDE.
CC: (none) => laidlaws
(In reply to alain bernard from comment #13) > Created attachment 4401 [details] > How make the launcher drakconf OK > > Drakconf launcher works normally when StartUpNotify is True in file .desktop > under XFCE4. Your attachment contains "nothing" which is quite strange.... But interesting that StartUpNotify is needed here. @Alain+Doug: When launching under a terminal on XFCE does it prompt you via the command line for passwords etc or pop up a GUI (or neither!)? And by run via the command line, I mean running simply "drakconf" rather than via xdg-open.
> > But interesting that StartUpNotify is needed here. > > @Alain+Doug: When launching under a terminal on XFCE does it prompt you via > the command line for passwords etc or pop up a GUI (or neither!)? And by run > via the command line, I mean running simply "drakconf" rather than via > xdg-open. I posted to the forum, and was advised, apparently by the Maintainer, to set StartUpNotify. It seems to me not to be the right thing. I replied that it didn't work, and it wasn't present in KDE. In answer to your query, when I type "drakconf" in a terminal, I see: ==== AUTHENTICATING FOR org.mageia.control-centre-gui.pkexec.run === Authentication is required to run Mageia Control Centre GUI Authenticating as: root Password: That is what should happen, I think. Only the panel icon and the menu item do not work.
(In reply to Doug Laidlaw from comment #16) > In answer to your query, when I type "drakconf" in a terminal, I see: > > ==== AUTHENTICATING FOR org.mageia.control-centre-gui.pkexec.run === > Authentication is required to run Mageia Control Centre GUI > Authenticating as: root > Password: > > That is what should happen, I think. Only the panel icon and the menu item > do not work. Well kinda. If we are in an X environment, it should pop up a GUI (it does for me under GNOME) with the text-based auth only being a fallback when no graphical agent is registered. So I think the problem is that you have no graphical agent running (as I originally mentioned further up in this bug). Can you install the "polkit-gnome" package? Despite it's name it has an XDG autostart .desktop file with: OnlyShowIn=XFCE; in it. This means this is only used for XFCE to provice polkit stuff. After logging in can you make sure the autostart stuff has worked and it's running (process is /usr/libexec/polkit-gnome-authentication-agent-1). Once this is done, do things behave better for you?
Yes, that got the panel icon working, but not the menu. On the menu, rpmdrake is in the same boat. mcc started up with the dialog for root password. I couldn't close the dialog box: clicking Cancel did nothing. But that is probably an mcc problem?
Perhaps the menu item is just bro(In reply to Doug Laidlaw from comment #18) > Yes, that got the panel icon working, Is this without the StartupNotify mods? > but not the menu. On the menu, rpmdrake is in the same boat. Perhaps this is broken in a different way. Can you check the menu's .desktop file and run the command manually - maybe I broke the paths - e.g. it might be referring to /usr/sbin/rpmdrake when it should really be pointing to /usr/bin/drakrpm... Does running the command via a terminal work? > mcc started up with the dialog for root password. I couldn't close the > dialog box: clicking Cancel did nothing. But that is probably an mcc > problem? Hmm, I don't think so as none of the real mcc code is run yet. Could be a polkit-gnome problem.
I am back in Official at the moment. I did notice that the mcc.desktop file pointed to /usr/sbin, but changing that alone didn't help. Where should I look foor the .desktop file? They are in /usr/share/applications, and I put one in ~/.local/applications to play with.
(In reply to Doug Laidlaw from comment #20) > I am back in Official at the moment. I did notice that the mcc.desktop file > pointed to /usr/sbin, but changing that alone didn't help. Yup, need to fix that at some point too :) > Where should I look foor the .desktop file? They are in > /usr/share/applications, and I put one in ~/.local/applications to play with. [colin@jimmy ~]$ rpm -ql rpmdrake | grep desktop$ /usr/share/applications/gurpmi.addmedia.desktop /usr/share/applications/mageiaupdate.desktop /usr/share/applications/rpmdrake-browse-only.desktop /usr/share/applications/rpmdrake-sources.desktop /usr/share/applications/rpmdrake.desktop /usr/share/mimelnk/application/x-urpmi-media.desktop But looking here, the paths all look good to me. Could you run the exec command from rpmdrake.desktop? (Exec=/usr/bin/rpmdrake here) My only other thought is that there is a stale .dekstop in your local user account or in /etc/ tree somewhere :s
(as a side note, to test the "cancel" issue, you may want to remove polkit-gnome package, and install instead mate-polkit (it has the same list of deps) but modify the file: /etc/xdg/autostart/polkit-mate-authentication-agent-1.desktop and change it to read OnlyShowIn=MATE;XFCE; instead. Then reboot etc. etc. and see if it behaves better than the old gnome one. If it does, then this is likely more sensible as the gnome one is no longer developed (it's built into gnome-shell these days so no longer needed)
2 mid-air collisions. Here is the operative part of /usr/share/applications/drakconf.desktop: Exec=/usr/bin/drakconf Icon=drakconf Terminal=false Type=Application StartupNotify=false Categories=GTK;X-MandrivaLinux-CrossDesktop;System; rpmdrake.desktop has the operative lines scattered among the translations: Icon=rpmdrake Exec=/usr/bin/rpmdrake Terminal=false Type=Application Categories=X-MandrivaLinux-CrossDesktop;GTK;System;PackageManager; StartupNotify=false Viewed in Official. I will go back into Cauldron and advise. It isn't only rpmdrake which doesn't start from the menu; drakconf doesn't either, even after a reboot.
Sorry for the delay. It was approaching midnight here. Wakeful at the moment (02:50.) mate-polkit was already installed. Mate desktop doesn't have a panel icon, but rpmdrake starts from menu OK. running rpmdrake in terminal with polkit-gnome installed gave me the same text request for authorization. Supplied password and rpmdrake started in graphical mode. Uninstalled pokit-gnome: back where I was. From the menu, nothing, with or without polkit-gnome.
(In reply to Doug Laidlaw from comment #24) > Sorry for the delay. It was approaching midnight here. Wakeful at the > moment (02:50.) > > mate-polkit was already installed. Mate desktop doesn't have a panel icon, > but rpmdrake starts from menu OK. > > running rpmdrake in terminal with polkit-gnome installed gave me the same > text request for authorization. Supplied password and rpmdrake started in > graphical mode. Uninstalled pokit-gnome: back where I was. From the menu, > nothing, with or without polkit-gnome. Hmm, maybe I wasn't clear with what I meant in comment 22. What I meant was to use mate-polkit when under XFCE (currently XFCE is using polkit-gnome, but this is a suggestion to replace that with mate-polkit). So, what I meant as to test in XFCE as before, but before logging in, modify the mate-polkit package's .desktop file such that it also starts in XFCE. (modify the OnlyShowIn line to include XFCE. After logging in you should have the authoriser running in the background. Now the panel icon in XFCE should work (once the path is correct to /usr/bin/drakconf as you've previously noted) and the authorisation GUI should pop up happily. Hopefully you can cancel this one and click the panel icon a second time and it should still work as expected. Seeing as it's quite late for you I'll expect a delay in replies :D
My TZ is GMT+11; just started summer time last weekend. Changed the OnlyShowIn line from "MATE;" to "MATE; XFCE;" No change. Perhaps it should have been "MATE;XFCE;" Will test for that in a moment. Starting MCC from the icon, authentication pops up, but when I authenticate, it doesn't start. From the terminal, it starts normally. I have noticed since last update that the mgaapplet icon restarts whenever I click on it, even a right-click, so it is unusable. Added a panel icon for MCC to the MATE panel; it is OK.
Changed to "MATE;XFCE;" The mgaapplet now works as intended, but there is something strange about the updates, so I will leave them for a bit. No change to the Cancel button. After it crashes, I can't repeat. From the panel icon, I enter my password and click "Authenticate". Nothing happens. When running from terminal, MCC starts normally.
OK, so I had a look at lxde specfically. It seems lxsession comes with lxpolkit, but it doesn't run by default. Simply opening a terminal, typing "lxpolkit" and then trying to launch things via another terminal properly pops up an authentication dialog. So the problem is apparently that lxpolkit is not running as part of the default session. Then there is also the "not able to run from panel". This appears to be a bug in LXDE and XFCE etc where they double fork before launching things from the menu and/or panel. I'm guessing the StartupNotify hack prevents this double fork in some cases. References: https://bugzilla.xfce.org/show_bug.cgi?id=9373 and the fixes put into Gnome for this: https://bugzilla.gnome.org/show_bug.cgi?id=675789 https://bugzilla.gnome.org/show_bug.cgi?id=686059
Summary: MCC doesn't start from launchers in several light DE but does from cli => MCC doesn't start from launchers in several light DE but does from cli (polkit)
I can't comment, but it looks as though you are on the track of this bug.
OK, so in LXDE, I now have things working nicely. I've installed lxpolkit to provide the GUI-based authenticator (again, this needs resolved properly as there seems to be two different upstream codebases here but the principle is good) and I've written a quick "prevent double forking" patch for lxpanel which fixes application launchers and the menu. It doesn't fix ALT+F2 tho'. Latest lxpanel with my fix building now - please test for regressions.
I've submitted a patched libxfce4ui-4.11.0-3.mga4 to cauldron/core/updates_testing which should also resolve the issue for XFCE. Testing appreciated.
not finded in core, core-update, core-update-testing. I retry to-morrow. Thanks you.
The update for xfce is there now. Starting drakconf from the icon, it popped up the authentication request. I hit "Cancel." It wouldn't cancel. I killed it; now the icon won't work at all. Successfully started drakconf from a terminal, but the authentication was in the terminal, not a GUI. Starting drakconf from Alt+F2 does nothing. Will reboot to reset everything, then try again.
On reboot: OT to this bug: Kernel 3.12.0 is installed, but system still booting into 3.11.4 Can start drakconf and rpmdrake from menu. If I choose "Authenticate" instead of "Cancel" I can proceed. Can start drakconf from Alt+F2 when there has been no crash. Can start rpmdrake from Alt+F2 likewise. Tried the icon last of all. Gave it root password, but nothing happened. The shield icon is not in the system tray, but I don't know if that is relevant.
I think that it is another update coming with the last update of the system because the version. the good paquetage is not yet on my mirror. Today, The launcher works nice but without startup notified (StartUpNotify is true!). Wait and see ?
It only just occurred to me: the mcc.desktop for the panel launcher wasn't updated with the rest. I have just substituted the drakconf.desktop from /usr/share/applications. drakconf now starts from the icon. Alain, I have never seen StartUpNotify do anything. What does it show?
Which polkit agent are you using while testing the cancel issue Doug? I've tried with lxpolkit (just install it and it will start in both LXDE and XFCE), polkit-gnome (is pulled in by XFCE, so you may have to --nodeps remove it) and mate-polkit (needs autostart .desktop mods to run under LXDE and XFCE) on both LXDE and XFCE and cannot reproduce a problem with the cancel button on any of them :s IMO, the mate version is the nicest (the lxpolkit GUI is just pretty nasty IMO - and the upstream is confused about where it lives (it's actively developed in two separate git repos!) so IMO we should use it everywhere that doesn't have a good, native one.
I have them all: rpm -qa | grep polkit polkit-gnome-0.105-4.mga3 libpolkit-qt-agent-1_1-0.103.0-2.mga3 polkit-0.112-1.mga4 polkit-kde-agent-1-0.99.0-3.mga3 mate-polkit-1.6.0-2.mga4 libpolkit-qt-core-1_1-0.103.0-2.mga3 libpolkit1_0-0.112-1.mga4 polkit-desktop-policy-0.112-1.mga4 I can't find a .desktop file for any of them. The gnome and mate ones are both enabled in XFCE's session-startup. I disabled the gnome one, but no difference yet.
Uninstalled polkit-gnome. --nodeps was not required. Startup problem is still there. It affects a change of mind only. If I su to root (without -) I can start drakconf without an authorization dialog. Tried to run it with strace, but as root, no problem, and as user, sudo has issues with other calls.
what does StartUpNotify? The mouse is changed during the apps start. I don't like it but it is the default mode.
The new version of libxfce4ui is installed. The launchers in the panel and in the menu works. StartUpNotify can be true or false and the mouse is modified during drakconf start only with true and only when the windows is showing. Under Mageia 3, the mouse is modified when I click the launcher and stop when the windows is showing. For me, all is good. Thanks!
Since Alain is happy and my only problem can't be reproduced, I suggest that the bug can be marked as fixed. At the very least, it seems to be no longer a release-blocker, but that is not for me to say. I have been hit by Bug 11377, which seems to be hardware-related, and I got similar symptoms to that Bug from Mondo Rescue. It seems to be unique to my computer. The cancel issue is probably my hardware as well.
Not so fast. I have updated to cauldron last night. When I call (as root) drakconf from a terminal in KDE4 I get: .... OpenJDK Client VM (build 24.0-b56, mixed mode, sharing) Segmentation fault I am running in virtualbox I can run rpmdrake without difficulty.
CC: (none) => bjarne.thomsen
I suppose that the next question is: is it killing drakconf or OpenJDK? I didn't know that JDK had anything to do with MCC. Most of that stuff is Perl, but that is where I really feel my limitations.
Bjarne, please open a new bug and try to provide backtrace if possible: https://wiki.mageia.org/en/Debugging_software_crashes#gdb Thanks
drakconf being a perl script, isn't there a way to debug it using a perl option, before jumping to gdb (that I have never used)?
drakconf works for me and for everybody else. The problems in this bug weren't in drakconf but in its environment. Your problem isn't something to be fixed by altering drakconf, but you need to fix that JVM error, to make drakconf run. Do as Manuel says. File a new bug, and get the help of the Mageia team.
Manuel asked for a traceback. I would do that with strace, but get the bug started, even without it. strace is not installed in Cauldron by default.
I have made some additional tests. I uninstalled openjdk, and then I started drakconf in the following DEs: IceWM: it works fine xfce4: it works fine MATE: it works fine KDE4: segmentation fault without any reference to JVM (obviously). It is not clear (for me) for which package I should open a new bugreport.
Please take this to a new bug as it is not related to polkit auth. It's a totally separate crash issue. I suspect something to do with GTK themes or similar.
So you seem to have eliminated the JVM. When you start your new bug report, file it under the Mga RPMs category, but just leave the package blank. Put ALL your observations in the bug report. The difference between your setup and mine is that you are running under Virtualbox, so mention that. I should have said before, when you see a line: "Traceback (last call first)" or similar, what follows is the backtrace, so you should set that out verbatim. The team will tell you what further tests are needed.
(In reply to Colin Guthrie from comment #50) > Please take this to a new bug as it is not related to polkit auth. It's a > totally separate crash issue. I suspect something to do with GTK themes or > similar. See above :)
Bjarne has started Bug 11506
This bug just won't lie down! In Cauldron with Xfce, I typed "sudo rpmdrake" in a terminal. Reply: "No protocol specified. Can't be run in cosole mode."
That's totally unrelated. By using sudo, you lost the DISPLAY environment variable and thus you cannot run any graphical program at all.
Thanks. I always assumed that sudo was the same as su, but this is the second difference I have found. It must cause problems in the distros without a root login. Bjarne seemed to be having no problem with rpmdrake, so I thought it must be this side of the screen.
I think there is still a problem with gurpmi. I get first popup but not password popup dialogs. It "Refusing to render service to dead parents."
CC: (none) => tarakbumba
(In reply to Atilla ÃNTAÅ from comment #57) > I think there is still a problem with gurpmi. I get first popup but not > password popup dialogs. It "Refusing to render service to dead parents." That is what I saw originally (Comment 14) but I don't see it now.
There is definitely a problem with gurpmi in Cauldron but the command line is no better. I suspect that it is a different bug.
(In reply to Doug Laidlaw from comment #59) From cli it works here.
What desktop are you using? This bug was supposed to be for the "light" desktops. I am using XFce. KDE is outside this particular bug, and no doubt has its own version of polkit. As far as my system is concerned, the polkit issue is now fixed. Anything new is a different bug. Note how Bjarne's issue was completelty different, and he opened a separate report for it. I am seeing apparent "freezes" or "hangs", booth in gurpmi and in the cli. Probably all the buttons in gurpmi are there, but I didn't get to a successful conclusion or exit. That is why I think that my observations don't match this bug description. I haven't searched extensively for a better match.
(In reply to Doug Laidlaw from comment #61) Using Mate here, and i don't think this is a different issue. Same symptoms but with gurpmi. From commandline "gurpmi abc.rpm" works as intended. But not from Mate. There is no password dialog altough confirmation dialog appears.
(In reply to Atilla ÃNTAÅ from comment #62) > (In reply to Doug Laidlaw from comment #61) > Using Mate here, and i don't think this is a different issue. Same symptoms > but with gurpmi. From commandline "gurpmi abc.rpm" works as intended. But > not from Mate. There is no password dialog altough confirmation dialog > appears. Then it smells a bit like mate is doing the whole double forking thing and should be fixed no?
Maybe related, but tools using pkexec fails to start when run remotely through ssh whereas other graphical tools do run
I was using mate's polkit in the end. I now had no problems until today.
(In reply to Doug Laidlaw from comment #65) > I was using mate's polkit in the end. I now had no problems until today. It is 4 a.m. on a sleepless night and I have an earache. I will reply in full when I can think straight.
(In reply to Thierry Vignaud from comment #64) > Maybe related, but tools using pkexec fails to start when run remotely > through ssh whereas other graphical tools do run This is just due to the policy. consolhelper was the same IIRC (I did test doing ssh to other machines and running urpmi.update): [colin@jimmy www (master)]$ ssh -x plateau <---- MGA3 machine Last login: Tue Dec 3 17:30:12 2013 from jimmy.brent.tribalogic.net [colin@plateau ~]$ urpmi.update -a The password you typed is invalid. Please try again. [colin@plateau ~]$ So no regression there AFAICT.
(In reply to Colin Guthrie from comment #63) Unfortunately i don't think so. Because all other tools run from panel shorcut and menu. I don't have a problem but gurpmi. One thing tough keeps me thinking. After polkit migration of drak-tools, new user do not have mcc shorcut in mate panel; altough it should be there by default setup. May be something .desktop file that prevents it from loading. I' ll investigate this. May be related or not.
(In reply to Atilla ÃNTAÅ from comment #68) > (In reply to Colin Guthrie from comment #63) > Unfortunately i don't think so. Because all other tools run from panel > shorcut and menu. I don't have a problem but gurpmi. Just out of curiosity, what are you expecting gurpmi to actually do? I mean how do you run it? It's not really meant to be run as an application as such... it's for installing specific packages. If it's appearing in a menu then something is broken in mate. (the .desktop file has NoDisplay=true) It's really only meant to be triggered e.g. when you double click on an .rpm file or similar then the mime type handler activates it. > One thing tough keeps me thinking. After polkit migration of drak-tools, new > user do not have mcc shorcut in mate panel; altough it should be there by > default setup. May be something .desktop file that prevents it from loading. > I' ll investigate this. May be related or not. Doubt it's related. I didn't change the .desktop files (might be the binary has the wrong path in the .desktop file and mate checks to see if it exists and hides it if not tho')
And fwiw, I just tried running various gurpmi commands under mate (via alt+f2 as I had to provide the package name I wanted to install) and I was prompted for authentication quite happily. If I don't pass a package name, then it exits with an error message which mate doesn't display to the user (as expected - doubt any other desktop env would either). You could argue that as a graphical tool, gurpmi should display it's error message as a graphical msgbox.
(In reply to Colin Guthrie from comment #69) > Just out of curiosity, what are you expecting gurpmi to actually do? I mean how > do you run it? It's not really meant to be run as an application as such... it's > for installing specific packages. If it's appearing in a menu then something is > broken in mate. (the .desktop file has NoDisplay=true) It's really only meant to > be triggered e.g. when you double click on an .rpm file or similar then the mime > type handler activates it. You totally misundestand me. I do not mean i have gurpmi in menu. As you just write, clicking on an rpm brings the very first dialog about my choices (Install, Save, Cancel). Clicking install won't do anything. It used to be work before polkit migration. And still works my MGA3 laptop (using my precompiled MATE from cauldron srpms). > Doubt it's related. I didn't change the .desktop files (might be the binary has > the wrong path in the .desktop file and mate checks to see if it exists and >hides it if not tho') No, desktop file has correct path. But i should investigate this first.
(In reply to Atilla ÃNTAÅ from comment #71) > You totally misundestand me. I do not mean i have gurpmi in menu. As you > just write, clicking on an rpm brings the very first dialog about my choices > (Install, Save, Cancel). Clicking install won't do anything. It used to be > work before polkit migration. And still works my MGA3 laptop (using my > precompiled MATE from cauldron srpms). Ahh right, OK, that makes more sense then! Was getting confused at what you were doing! Looking at the user journalctl output (after logging in with gdm - not sure if other login managers direct debug to journal), it clearly shows me the error: "Refusing to render service to dead parents" So it seems the Mate file manager is doing the whole double fork thing that I mentioned back in comment 63. This is a Mate bug that is exposed by polkit. Mate needs patched for this. I'll see if I can do that if you like?
(In reply to Colin Guthrie from comment #67) > This is just due to the policy. consolhelper was the same IIRC (I did test > doing ssh to other machines and running urpmi.update): I mean I cannot run them despite already being root...
Created attachment 4573 [details] Patch to fix git master caja (aka mate-file-manager) Atilla, Can you liaise with upstream to get this patch accepted please? As noted inside the file I've not really tested (or even compiled) the GTK3 bits but the GTK2 stuff is the same as in the patch I've pushed into our subversion which I did test. Please test the next build thoroughly - it did work for me! I spent waaaaay more time looking at this than I really wanted to. I wish this old GTK2 code would just die! :(
(In reply to Thierry Vignaud from comment #73) > (In reply to Colin Guthrie from comment #67) > > This is just due to the policy. consolhelper was the same IIRC (I did test > > doing ssh to other machines and running urpmi.update): > > I mean I cannot run them despite already being root... Ahh right, well, they seem to work for me fine (ssh + pam_systemd sets up the needed env - but the remote system would need to be running polkitd. I'm pretty sure all our tools avoid pkexec now anyway no? Anyway, if this is an issue can we open a new bug as this one is kinda messy already.
(In reply to Atilla ÃNTAÅ from comment #62) > (In reply to Doug Laidlaw from comment #61) > Using Mate here, and i don't think this is a different issue. Same symptoms > but with gurpmi. From commandline "gurpmi abc.rpm" works as intended. But > not from Mate. There is no password dialog altough confirmation dialog > appears. I have just tested this in Mate. Selected "Install and remove software" from the Mate menu, and successfully installed an update as if it was a new package. No problems with the GUI. I would never use "gurpmi abc.rpm". From the command line, I would use urpmi. Anyway, it seems that I cannot contribute further.
(In reply to Colin Guthrie from comment #74) Thank you Colin, i was digging into Caja as well. But you know,with the lack of programming language it will hard to find a fix. You' re a life saver! I will test new build tonight. I already reported this to Mate devs. Luckily, GTK3 migration is proceeding and i hope it will complete somewhere between Mate Desktop 1.8 - 2.0
Hi, greetings from fedora. I'm mate package maintainer and part of upstream. First some info's for you. Opening apps from mate menu was fixed by me some time ago. https://github.com/mate-desktop/mate-panel/commit/2905402c0b856eaf86e497c41bbe0d630647c6f6 Unfortunately this issue exits if you open an application from inside mate-control-center. Colin, i never notice about that caja is also affected because in fedora opening a rpm with a package manager from inside caja works with packagekit or yumex. Can you do a pull request at github for your fix? It would be nice if you can do that for GTK3 too.....Mate-1.7.x starts with optinal GTK3 support. Thank you
CC: (none) => chat-to-me
Hi Wolfgang! I actually spoke to your fellow Fedorian, Dan Mashal, last night about it too. The patch attached here is actually for caja git master and includes GTK3 fixes too, although I have not tested those bits (it might not even compile, but I think it looks OK!). I'm leaving it with Atilla to try and liaise with upstream to get the patch accepted. I think Dan was going to look at the mate-control-center issue to see if he could cook up a patch but if not I'll take a look at some point (I think there is still one issue in XFCE or LXDE that I'm still working on too)! All the best.
Depends on: (none) => 11956Whiteboard: 4alpha3 => 4beta2
RazorQT is still broken. It seems to run its own policykit agent but it probably does something wrong..
Confirmed in latest isos, see also bug 12287 for it being hidden in the menu and missing the icon.
It could be an issue with the polkit agent or it could be that the launching code does a double fork. Assuming the systemd user session is all setup properly (it should be) try doing a "journalctl -f" as your user in a terminal when you launch whatever launcher you try and launch. If you get a message about refusing to render service to dead parents, then it's the double forking issue.
I don't see anything out of the ordinary in the journal when starting MCC in razorqt. When started from the terminal as ordinary user the polkit agent asks for root password and mcc starts ok. When starting from the menu it doesn't but nothing obvious in the journal.
*** Bug 12364 has been marked as a duplicate of this bug. ***
CC: (none) => loginov_alex
(In reply to Atilla ÃNTAÅ from comment #84) Also, pcmanfm and firefox double forks. Look at duplicated bug#12364
commit 9546268bf1c85d5ddef8204bdfb7e40f55f8b9e3 Author: Colin Guthrie <colin@...> Date: Wed Jan 22 23:00:31 2014 +0000 Do not exec pkexec but run it so it has a parent process to fix double fork issues mga#11184 mga#12364 --- Commit Link: http://gitweb.mageia.org/software/rpmdrake/commit/?id=9546268bf1c85d5ddef8204bdfb7e40f55f8b9e3 Bug links: Mageia https://bugs.mageia.org/show_bug.cgi?id=11184 https://bugs.mageia.org/show_bug.cgi?id=12364
commit f40d4ecae66a6166ef858770d3863729c78dfb64 Author: Colin Guthrie <colin@...> Date: Wed Jan 22 23:00:31 2014 +0000 Do not exec pkexec but run it so it has a parent process to fix double fork issues mga#11184 mga#12364 --- Commit Link: http://gitweb.mageia.org/software/drakx-net/commit/?id=f40d4ecae66a6166ef858770d3863729c78dfb64 Bug links: Mageia https://bugs.mageia.org/show_bug.cgi?id=11184 https://bugs.mageia.org/show_bug.cgi?id=12364
commit ea927d73e6c1218a44d18efae45dbb5ac8a06821 Author: Colin Guthrie <colin@...> Date: Wed Jan 22 23:00:32 2014 +0000 Do not exec pkexec but run it so it has a parent process to fix double fork issues mga#11184 mga#12364 --- Commit Link: http://gitweb.mageia.org/software/rpm/urpmi/commit/?id=ea927d73e6c1218a44d18efae45dbb5ac8a06821 Bug links: Mageia https://bugs.mageia.org/show_bug.cgi?id=11184 https://bugs.mageia.org/show_bug.cgi?id=12364
commit 6acf16149d317f830e3f2576a68205a450ef5b6f Author: Colin Guthrie <colin@...> Date: Wed Jan 22 23:00:32 2014 +0000 Do not exec pkexec but run it so it has a parent process to fix double fork issues mga#11184 mga#12364 --- Commit Link: http://gitweb.mageia.org/software/drakx/commit/?id=6acf16149d317f830e3f2576a68205a450ef5b6f Bug links: Mageia https://bugs.mageia.org/show_bug.cgi?id=11184 https://bugs.mageia.org/show_bug.cgi?id=12364
commit b5c5b3e9c21edeb407ae4060d1ec54b9f542faa3 Author: Colin Guthrie <colin@...> Date: Wed Jan 22 23:00:32 2014 +0000 Do not exec pkexec but run it so it has a parent process to fix double fork issues mga#11184 mga#12364 --- Commit Link: http://gitweb.mageia.org/software/control-center/commit/?id=b5c5b3e9c21edeb407ae4060d1ec54b9f542faa3 Bug links: Mageia https://bugs.mageia.org/show_bug.cgi?id=11184 https://bugs.mageia.org/show_bug.cgi?id=12364
commit 86df91fdd1bae8c5c055de70060902094dc09ba0 Author: Colin Guthrie <colin@...> Date: Wed Jan 22 23:00:32 2014 +0000 Do not exec pkexec but run it so it has a parent process to fix double fork issues mga#11184 mga#12364 --- Commit Link: http://gitweb.mageia.org/software/drakx-kbd-mouse-x11/commit/?id=86df91fdd1bae8c5c055de70060902094dc09ba0 Bug links: Mageia https://bugs.mageia.org/show_bug.cgi?id=11184 https://bugs.mageia.org/show_bug.cgi?id=12364
commit 33b0066a1e912425c7d69f831077d27fa3129082 Author: Colin Guthrie <colin@...> Date: Wed Jan 22 23:00:32 2014 +0000 Do not exec pkexec but run it so it has a parent process to fix double fork issues mga#11184 mga#12364 --- Commit Link: http://gitweb.mageia.org/software/userdrake/commit/?id=33b0066a1e912425c7d69f831077d27fa3129082 Bug links: Mageia https://bugs.mageia.org/show_bug.cgi?id=11184 https://bugs.mageia.org/show_bug.cgi?id=12364
commit 97f71b4dedbea63f0309c9cbf537e63002142855 Author: Colin Guthrie <colin@...> Date: Wed Jan 22 23:00:32 2014 +0000 Do not exec pkexec but run it so it has a parent process to fix double fork issues mga#11184 mga#12364 --- Commit Link: http://gitweb.mageia.org/software/drak3d/commit/?id=97f71b4dedbea63f0309c9cbf537e63002142855 Bug links: Mageia https://bugs.mageia.org/show_bug.cgi?id=11184 https://bugs.mageia.org/show_bug.cgi?id=12364
commit 5d2b909dcdbfd7c44931b153d4e9ea94916e31b1 Author: Colin Guthrie <colin@...> Date: Wed Jan 22 23:00:32 2014 +0000 Do not exec pkexec but run it so it has a parent process to fix double fork issues mga#11184 mga#12364 --- Commit Link: http://gitweb.mageia.org/software/mgaonline/commit/?id=5d2b909dcdbfd7c44931b153d4e9ea94916e31b1 Bug links: Mageia https://bugs.mageia.org/show_bug.cgi?id=11184 https://bugs.mageia.org/show_bug.cgi?id=12364
Fixed now
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
I installed Mageia 4 yesterday with LXDE as the only Desktop. I noticed the error 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. Sorry for the long decription, but my english is no good enough to eplain it using less words
Status: RESOLVED => REOPENEDCC: (none) => michael-engelResolution: FIXED => (none)
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.
I'm not sure whether I'm seeing a variant of this bug or whether something done to fix this bug is responsible, but after urpmi --auto-select updating a KDE cauldron system yesterday, I am seeing: ************************************************** [ftg@ftgme2 ~]$ diskdrake Error executing command as another user: Not authorized This incident has been reported. [ftg@ftgme2 ~]$ mcc Error executing command as another user: Not authorized This incident has been reported. ************************************************** Posting here because several others have said KDE was not affected.
CC: (none) => ftg
(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
(In reply to Frank Griffin from comment #98) > I'm not sure whether I'm seeing a variant of this bug or whether something > done to fix this bug is responsible, but after urpmi --auto-select updating > a KDE cauldron system yesterday, I am seeing: > > ************************************************** > [ftg@ftgme2 ~]$ diskdrake > Error executing command as another user: Not authorized > > This incident has been reported. > [ftg@ftgme2 ~]$ mcc > Error executing command as another user: Not authorized > > This incident has been reported. > ************************************************** > > Posting here because several others have said KDE was not affected. I was under the impression that the KDE polkit stuff was "built in" somehow, but we do also have a separate package: polkit-kde-agent-1. Does installing it and rebooting make things magically work?
(In reply to Michael Engel from comment #99) > (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 OK, then that's the problem. I'll look into it. As this bug is getting really messy with lots of different (if related) issues, can you open a new bug for this and make sure I'm CC'ed/assigned?
(In reply to Colin Guthrie from comment #100) > > I was under the impression that the KDE polkit stuff was "built in" somehow, > but we do also have a separate package: polkit-kde-agent-1. Does installing > it and rebooting make things magically work? [root@ftgme2 ~]# urpmi polkit-kde-agent-1 Package polkit-kde-agent-1-0.99.0-6.mga4.x86_64 is already installed [root@ftgme2 ~]#
(In reply to Frank Griffin from comment #102) > (In reply to Colin Guthrie from comment #100) > > > > I was under the impression that the KDE polkit stuff was "built in" somehow, > > but we do also have a separate package: polkit-kde-agent-1. Does installing > > it and rebooting make things magically work? > > [root@ftgme2 ~]# urpmi polkit-kde-agent-1 > Package polkit-kde-agent-1-0.99.0-6.mga4.x86_64 is already installed > [root@ftgme2 ~]# Can you check that it's actually running correctly? If it's running, try killing it and running it again manually?
Dunno if I did this correctly. Curious that polkit-agent-helper-1 was running originally, but not after the restart: [root@ftgme2 ~]# ps ax | grep polkit 2697 ? Ssl 0:01 /usr/lib/polkit-1/polkitd --no-debug 17486 ? S 0:00 /usr/lib/polkit-1/polkit-agent-helper-1 root cookie0 19853 ? Sl 0:23 /usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1 20001 pts/1 S+ 0:00 grep --color polkit [root@ftgme2 ~]# kill 19853 [root@ftgme2 ~]# /usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1 & [2] 20363 [root@ftgme2 ~]# New PolkitAgentListener 0x225b000 Adding new listener PolkitQt1::Agent::Listener(0x23c61b0) for 0x225b000 [2]+ Done /usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1 [root@ftgme2 ~]# ps ax | grep polkit 2697 ? Ssl 0:01 /usr/lib/polkit-1/polkitd --no-debug 20369 pts/1 Sl 0:00 /usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1 20413 pts/1 S+ 0:00 grep --color polkit [ftg@ftgme2 ~]$ diskdrake Error executing command as another user: Not authorized This incident has been reported. [ftg@ftgme2 ~]$
This seems like a strange issue. Can you open a new bug report because this really is something separate to this bug. Ideally you would copy in the same info as you've done here, close this bug again and CC me on the new bug! If you could also comment on whether you do anything odd to login or if it's just a normal login through a DE (e.g. any tty+startx, autologin etc. etc.)
Oh, also just noticed you were doing things as root. Don't do anything as root, only your user.
Done: https://bugs.mageia.org/show_bug.cgi?id=12572 I'm not closing this one, since I'm not the one who reopened it (I just commented).
I think that Bjarne may have reopened it, and he has taken his issue elsewhere. I was in it at that stage, so I'll close this bug.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
(In reply to Colin Guthrie from comment #101) > (In reply to Michael Engel from comment #99) > > (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 > > OK, then that's the problem. I'll look into it. As this bug is getting > really messy with lots of different (if related) issues, can you open a new > bug for this and make sure I'm CC'ed/assigned? Hi Colin, I opened a new bug, you find it here: https://bugs.mageia.org/show_bug.cgi?id=12721 sorry for the delay, my internet was down for one week. yours Michael
this in apparent in Mageia-5-beta2-x86_64-DVD, Jan 14 20:18:39 CET 2015 fresh install of Lxde
CC: (none) => westel
I thought this was fixed long ago. If this bug has reappeared, it should be reopened. But see Comment 109, which involved lxde. Is your problem really this bug, or the new bug 12721? I will bow out here. So far, in Beta 2, I have tested only KDE.
I am only running 1 user + root doesn't behave like 12721. authentication popup very briefly the first time you click on MCC, after that, no response. launches and behaves correctly from cli I made a note Jan 6 on pad that problem had arrived. then, rebooting system after update fixed it, but now it doesnt
Mageia-5-beta3-x86_64-DVD, Thu Jan 29 18:54:15 CET 2015 issue is unresolved
(In reply to ben mcmonagle from comment #113) > Mageia-5-beta3-x86_64-DVD, Thu Jan 29 18:54:15 CET 2015 > > issue is unresolved The fix before was to install Polkit for Mate. You could try that. Otherwise, I have no ideas. If it is happening only from the icon on the panel, that may need updating, but I thought Colin did that. Iam unsubscribing.
Resolution: FIXED => (none)Status: RESOLVED => REOPENED
CC: laidlaws => (none)
Created attachment 5849 [details] lxde64.png I'm unable to reproduce this Ben. It seems like a separate issue. Polkit is installed and working reliably here from terminal, panel launcher and menu launcher in lxde. Could you create a new bug report please and close this one again. Thanks
There does seem to be 2 polkit versions installed though which may be the cause of your issues.. $ rpm -qa *polkit* lib64mate-polkit1_0-1.8.0-6.mga5 lib64polkit1_0-0.112-7.mga5 gksu-polkit-0.0.3-0.git20131130.11.mga5 mate-polkit-1.8.0-6.mga5 lib64gksu-polkit0-0.0.3-0.git20131130.11.mga5 lib64polkit-gir1.0-0.112-7.mga5 polkit-0.112-7.mga5
$ ps aux | grep polkit polkitd 1350 0.1 1.2 375220 13156 ? Ssl 09:16 0:00 /usr/lib/polkit-1/polkitd --no-debug user 1584 0.2 2.3 332468 23984 ? Sl 09:16 0:00 lxpolkit
FYI, there are not 2 polkit versions - these are different packages. There is polkit the daemon and various agents for different desktops etc. I think it's correct to close and open a new bug report with as much detail as possible if Ben can reliably reproduce the issue! Cheers!
Yes, multiple agents were installed for a plain LXDE installation though. lxpolkit shows as running, wasn't that obsoleted previously? Ben is going to create a new bug anyway so we can debug further there.
enlightenment is still affected by this bug. When started from terminal no pop-up appears, but root password will be asked in terminal. No reaction when started from menu journalctl output when started from terminal: Feb 17 21:10:27 Cauldron polkitd[31019]: Registered Authentication Agent for unix-process:31302:873932 (system bus name :1.173 [/usr/bin/pkexec /usr/libexec/drakconf], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) [root@Cauldron marc]# rpm -qa | grep polkit polkit-kde-agent-1-0.99.1-2.mga5 lib64polkit-qt5-core1-0.112.0-4.mga5 lib64polkit1_0-0.112-7.mga5 lib64polkit-qt-core-1_1-0.112.0-6.mga5 polkit-0.112-7.mga5 lib64mate-polkit1_0-1.8.0-6.mga5 lib64polkit-qt-agent-1_1-0.112.0-6.mga5 mate-polkit-1.8.0-6.mga5 lib64polkit-qt5-agent1-0.112.0-4.mga5 lib64polkit-gir1.0-0.112-7.mga5 I can start a new report to get rid of the long tail but it is exactly the same bug...
CC: (none) => marc.lattemann
*** Bug 13029 has been marked as a duplicate of this bug. ***
CC: (none) => razvan.rotaru
(In reply to Marc Lattemann from comment #120) > enlightenment is still affected by this bug. Definitely a different issue. The primary problem behind this bug was worked around centrally and differently and thus this cannot be a problem in any DE any more even without the patch. What you are seeing is different. I'll comment on your other bug.