Muon package manager needs authorization but isn't asking for it

[tomcloyd]

Running my HP-110 Netbook, with KB 12.04 fully updated, I've been finding lately that once again I must revert to using trusty old Synaptic.The problem with Muon now is that once I have packages to installed marked, it immediately display the following message:

This operation cannot continue since proper authorization was not provided.

On my desktop, at this point, I would have been asked for my administrative password, given, and be on my way. But my Netbook install of Muon is NOT asking for this authorization, then protesting because it doesn't have it. I've tried reinstalling Muon. Nothing I can think of fixes this, which makes Muon all but useless for me.

Anyone have any ideas how to fix this?

[NickStone]

This is only a work-around not a fix.

What you can do is amend the menu entry for Muon Package Manager and add the command sudo to the beginning of the command to run Muon. Then save the settings (obviously).

From then on it will ask you for your password

[HalationEffect]

Wouldn't it be better to use kdesudo rather than sudo?

I've always been given to understand that kdesudo is the command of choice for running graphical programs with root privileges, while sudo is preferred for CLI programs.

[OneLine]

The kdesudo is recommended: https://help.ubuntu.com/community/RootSudo


The KDE Menu has an option to run applications as a different user. With the root the password should be asked when the application is started.

[NickStone]

Does it matter? Both kdesudo and sudo allow you to run an app as root.

[SteveRiley]

Does it matter? Both kdesudo and sudo allow you to run an app as root.

The article to which OneLine linked includes an explanation of why it's important to use a graphical sudo when elevating privileges of graphical programs.

[NickStone]

Well I've learned something new today!

Now what I read about using sudo to run graphical app states that the app will become the owner of root. In the case of running Muon you need root access to be able to download and install apps. So in this case, I still cannot see much difference.

But as mentioned in the docs anyone reading this post please use the graphical sudo (gksudo or kdesudo) command to run any graphical apps on your system.

[tomcloyd]

Thanks, folks. Good and useful responses, all. Don't know why this problem is happening, but the suggested fix works quite well.

I also appreciate the link about RootSudo. I've been wondering for some time about this.

[Snowhog]

Running my HP-110 Netbook, with KB 12.04 fully updated, I've been finding lately that once again I must revert to using trusty old Synaptic.The problem with Muon now is that once I have packages to installed marked, it immediately display the following message:

This operation cannot continue since proper authorization was not provided.

On my desktop, at this point, I would have been asked for my administrative password, given, and be on my way. But my Netbook install of Muon is NOT asking for this authorization, then protesting because it doesn't have it. I've tried reinstalling Muon. Nothing I can think of fixes this, which makes Muon all but useless for me.

Anyone have any ideas how to fix this?

Given that you are on a netbook, and so (likely) the netbook interface/desktop, the prompt for the user password 'might' be underneath the running application, instead of popping up on top of it. Just a guess.

[tomcloyd]

I find that the modal prompt window often doesn't pop up, on my desktop, and so knew to go looking for it. However, on my netbook, where I am running that special adaptation of 12.04 that someone made so it would run leaner and faster (cannot recall the fellow's name or any other details), and NOT the specific netbook version of 12.04 (which I can't stand), I simply cannot find any hidden prompt window - I've looked hard for it.

Starting the launch with kdesudo solves the problem perfectly.

However, that Muon module that watches for updates and puts a notification in the sys-tray still has the authorization problem. That module is run by the OS, not me, so I cannot get to it, and even if I could I'm not sure it's wise to have a TSR (or whatever it's called) running with root status all the time in background. (If I'm babbling nonsense at this point, just ignore me. I'm thinking right at the limit of my modest knowledge. I'm a specialist in psychological trauma, not in Linux or anything else in that region of the universe!) My solution to THAT problem is to respond to the notification icon by manually launching Muon, so the kdesudo invocation IS forced. Not the worst kludge I've ever had to live with.

Thanks for your thoughts.

[tomcloyd]

OneLine: That's an amazing graphic you made for your reply. Very excellent! And thanks for the link. Definitely helpful.