Running an application as root

Registered by Felix

I found out how to do this pretty quickly, but to make this easier, and for consistency I'd recommend:

* Making an alias for programs that don't have very obvious name, like "pantheon-files", which could use an alias "files". It's more obvious to try "sudo files", and is consistent with the application name in the user space.
* Making it possible to also right-click on an icon in slingshot and being able to select "Run as administrator"
* Adding this option to all applications in the dock (right now I can only find it in the right-click menu of Files, but it would be just as useful for e.g. text editors)
* Defining a modifier key which is consistent across the Dock as well as Slingshot which can be held while clicking an icon to start it with elevated root priviliges.

Blueprint information

Not started
Needs approval
Series goal:
Milestone target:

Related branches



IMO the 'Run as administrator' is only needed in some apps: Scratch, Files, and Pantheon Terminal. -luksi.reiku

Indeed for some applications it would not be frequently needed, but would it hurt to have the option available there? And what about non-elementary applications such as gEdit? Wouldn't it be more convenient to just offer it to all application? I don't think the alternative of keeping and maintaining a list of applications for which this is handy would ever work, even just because you'll neven know all the applications out there that have been made or are being made for which this would be very useful. ~Felix

Well, the elementary team tries to make a clean user interface, and having an almost useless option just confuses the user. But is just my opinion.
And about non-elementary apps, elementary removed almost all the icons of third party apps, like synaptic, chrome, pidgin... why they need to add an option just to 'make more useful' some external apps? They are working in thier OS and in thier official apps. -luksi.reiku

A clean user interface is a primary goal indeed. But a rich environment that empowers the user is an equal goal of the team. I believe both can go hand in hand. There are UX principles to guide in positioning of less frequently used but powerful features in an interface. Placing it in the right-click menu or binding it to a modifier key are just some examples, but perhaps there is a better way. ~Felix


Work Items

This blueprint contains Public information 
Everyone can see this information.


No subscribers.