Posts Tagged ‘command’

Now that I have Mandriva Linux, I have actually been using the command line a bit more (not that it’s necessary but I need to not be so hopeless at it) and one of the things I discovered is that the thing about Linux Mint that I miss the most is right clicking on a menu app and clicking on “open as root.”  That was such an amazing option, I think, as I sat here for an hour trying to figure out why I can’t do it from the command line.

Let me tell you, I had the worst time of it with this one so it’s all the more gratifying that I found a solution.  First of all, here’s what I normally did in another distro to open as root from the command line.

I opened the Gnome Terminal..there are several ways to do it but I use Gnome-Do because it Do..everything you can think of practically.  There is usually a menu option in Gnome under tools.  No idea in KDE because of all the branches of their tree-like menus.  At any rate, I opened the terminal and……….

[pariah@HappyFunMachine ~]$ sudo nautilus
bash: sudo: command not found
[pariah@HappyFunMachine ~]$ gksudo nautilus
bash: gksudo: command not found
[pariah@HappyFunMachine ~]$ gksu nautilus
bash: gksu: command not found
[pariah@HappyFunMachine ~]$ su nautilus
su: user nautilus does not exist
[pariah@HappyFunMachine ~]$ you wise-ass bastard
bash: you: command not found
[pariah@HappyFunMachine ~]$ su
Password:
[root@HappyFunMachine pariah]# nautilus

(nautilus:9416): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported
(nautilus:9416): Eel-WARNING **: GConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details –  1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:9416): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.
(nautilus:9416): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(nautilus:9416): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.
[root@HappyFunMachine pariah]#

Gee is anyone having fun here yet???? Okay fine, here’s some more options I tried from searching…(now that I have determined only one thing, that su is the preferred command)

[root@HappyFunMachine pariah]# su – pariah nautilus
/usr/bin/nautilus: /usr/bin/nautilus: cannot execute binary file
[root@HappyFunMachine pariah]# well why the f*ck not???
bash: well: command not found
[root@HappyFunMachine pariah]# su – pariah -l nautilus
/usr/bin/nautilus: /usr/bin/nautilus: cannot execute binary file

So, if you have gotten either of the above errors, like I did, here is what worked for me…remember this is Mandriva Linux 2009 (One) and running a Gnome desktop!

[root@HappyFunMachine pariah]# su -c “nautilus” –

** (nautilus:31388): WARNING **: Unable to add monitor: Operation not supported

No idea why this works, but it does! So if no other option has worked for you try that one…oh yeah, in the command, there is a space after each of these: su, c, and ” (just to be a little more clear) and yes, there is that warning after it but hey i don’t need to add a monitor so I guess it’s okay lol. Oh, I just saw that in the solution, I am already listed as root..but you can do this from your regular user terminal.

Good luck and happy Linuxing!

Blogged with the Flock Browser