FS#18622 - network-manager-applet 0.8-2: insufficient privileges

Attached to Project: Arch Linux
Opened by Heiko Baums (cyberpatrol) - Tuesday, 09 March 2010, 19:41 GMT
Last edited by Jan de Groot (JGC) - Saturday, 13 March 2010, 19:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
It's not possible to add, edit or delete any connections in network-manager-applet 0.8-2 if the connection shall be accessible for all users.

If a connection which was created with network-manager-applet 0.7 shall be edited or deleted, or a new connection shall be added for all users a window is opened with the error message "Insufficient privileges." I guess the same will appear if such a connection shall be established.

So it's not possible to add, edit, delete or establish any connections for all users except of the automatically established wired eth0 connection. Or in other words it's not possible to use network-manager-applet.
This task depends upon

Closed by  Jan de Groot (JGC)
Saturday, 13 March 2010, 19:18 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in latest polkit-gnome. Anyone not using a desktop that implements /etc/xdg/* stuff has to fix this himself.
Comment by Jan de Groot (JGC) - Tuesday, 09 March 2010, 22:18 GMT
nm-applet uses polkit authorization to allow network connection editing. It's clear that you don't have the correct polkit authorizations. Using a display manager that supports ConsoleKit, or configuring your setup to register with ConsoleKit should do the trick here.
Comment by Heiko Baums (cyberpatrol) - Wednesday, 10 March 2010, 23:57 GMT
  • Field changed: Percent Complete (100% → 0%)
If a software has worked in the previous version and doesn't work after an update without changing the configuration, without a .pacnew file being installed and without a hint about major configuration changes in post_install or the news, then this is no bug? Then I haven't done my "homework"? If there's nothing found about this issue in the forums and in the wiki, then I haven't done my "homework"? You don't think that this is arrogant and ignorant?

network-manager-applet has a bug and is not usable in version 0.8-2. It was in 0.7.

So, please, re-open this bug and try to fix it or at least find out if this a downstream or an upstream bug.
Comment by Jan de Groot (JGC) - Wednesday, 10 March 2010, 23:59 GMT
I looked into this problem, and why it "works for me" is simply because I'm running GNOME.

When you try to add a global connection, networkmanager will ask policykit for authorization to do so. Policykit wants root permissions, so it fires up an authorization agent. These agents are provided by polkit-gnome and polkit-kde at this moment, but both have OnlyShowIn=KDE/GNOME entries in their .desktop files.

I'll add dependencies on polkit-gnome for the next rebuild of networkmanager-applet, and patch the .desktop file in polkit-gnome to remove the OnlyShowIn=GNOME and replace it with DontShowIn=KDE. This fixes the issue in non KDE/GNOME environments.
Comment by Heiko Baums (cyberpatrol) - Thursday, 11 March 2010, 00:33 GMT
Ok, first thanks for re-opening.

I removed the OnlyShowIn lines from /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop and /etc/xdg/autostart/polkit-kde-authentication-agent-1.desktop and now it works again. But you probably shouldn't add the DontShowIn options to these .desktop files. I don't know, if /etc/xdg/autostart/polkit-kde-authentication-agent-1.desktop could be needed in Gnome, too, if someone uses KDE software in Gnome, and if /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop could be needed in KDE, if someone uses Gnome software in KDE. But I don't know too little about polkit to decide this.

One question: Was this a bug or not? A small one, but it was one. ;-)

Another question (a bit off topic): Would you, please, take bug reports more seriously in the future? Then I won't need to get angry again. You can talk with me about nearly everything, but in a friendly way. You can of course ask, if you think that this could be a configuration issue, but, please, only close bugs if the reporter has confirmed that this bug is invalid. And of course it already happened that I filed a few bug reports which were invalid. But nobody is omniscient and everybody can sometimes miss an option. But if I report a bug, it usually is a bug. ;-)

Peace?
Comment by Jan de Groot (JGC) - Thursday, 11 March 2010, 07:56 GMT
polkit-kde and polkit-gnome provide the same authorization agent interface, so you only need to have one running. If you have KDE, you'll have the KDE version running and you don't need the polkit-gnome agent running, if you have a non-KDE desktop the choice is yours, but most logical choice is polkit-gnome in that case (polkit-gnome only pulls in gtk2 and polkit, where polkit-kde pulls in much more).

As for the bug: Initially I didn't read the bug correctly, as it looked like just another bugreport about a user not setting his things up right. When you requested reopening with a bitchy comment, someone else denied the request with another bitchy comment.
Comment by Heiko Baums (cyberpatrol) - Thursday, 11 March 2010, 13:24 GMT
And I haven't read the e-mail about the re-opening deny correctly. So I missed, that you haven't done this. I'm sorry.
The reason why I reacted this way about the closing as "Works for me" was that this didn't happen for the first time.

If only one of the polkit agents is needed, then you should indeed add DontShowIn=KDE to /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop and/or OnlyShowIn=KDE to /etc/xdg/autostart/polkit-kde-authentication-agent-1.desktop, because KDE is the only desktop environment I know which is not based on GTK/Gnome. At least on Xfce and LXDE the Gnome variant is preferred.
Comment by Heiko Baums (cyberpatrol) - Thursday, 11 March 2010, 15:03 GMT
Filed a bug report to upstream: http://bugs.freedesktop.org/show_bug.cgi?id=27019
Comment by Heiko Baums (cyberpatrol) - Thursday, 11 March 2010, 15:37 GMT
The same problem exists with /etc/xdg/autostart/gnome-keyring-daemon.desktop from the package gnome-keyring.
There's also an upstream bug report for LXDE: https://bugzilla.gnome.org/show_bug.cgi?id=609631
And one for Xfce: https://bugzilla.gnome.org/show_bug.cgi?id=610715
But in this case gnome-keyring-daemon is already started by the lines
auth optional pam_gnome_keyring.so
and
session optional pam_gnome_keyring.so auto_start
which are in /etc/pam.d/gdm and which I also added to /etc/pam.d/slim.

Loading...