Slackware :: Start Thunar As Root - Won't Run After Sudo
Jun 1, 2011
I have been using ubuntu or a derivative distro and perhaps I grew too used to sudo. If it matters I am on Slackware 13.37 and xfce4. I was able to adjust sudoers to allow sudo but I am having difficulties running some progs as root. The biggest concern is trying to start thunar as root. It wont run after sudo, su, or su -l. What am I doing wrong?
I compiled ffmpegthumbnailer and installed fine. I have thunar-thumbnailers installed, and followed the tutorial at;URL...But i still have nothing. Does any one have any tips on setting up ffmpegthumbnailers?
Found the new small bug after November upgrades:Im using XFCE and now when Thunar showing files and directories in details view, i can one time open folder by double click, then go up to directory and double click wont work anymore, but in compact and in icon view thats work ok.Earlier this worked Ok from others views. Thinking that is bug.To XFCE users: try this too after latest updates...
Accidentally I changed the ownership of all the directories under / to my own instead of root:root. Now I am unable to use sudo and many bad things are happening. Is there a way to revert the changes or change the permissions again to root:root or make sudo work ?
I was trying to edit a file requiring root permissions, so I used sudo. I typed the root password and it failed. This happened three times, and the process was ended. I then logged in as root (su) and was able to navigate to the file and make changes as root. Am I missing something? How would I edit the sudoers file such that this password would work? Or is there another way to log in to the sudo group to make these changes? How do I set sudo passwords?
I use Fedora 13 LXDE and I want to know how to use sudo with my user passwordnd desactivate the root account rather than the su command like Ubuntu distribs
When i install or upgrade the system I want to be asked for the root password instead of just the normal password for sudo. The reason for this is that the kids and so on uses my system and know my password. They do not know my root password though. I do not want them to install or mess up my system by pure fumbling, so is this possible to do. A simple change in who runs the updater/install features...
I don't like about it is the fixation of avoiding root login. I read in the sticky post at the top of this forum that logging into a GUI interface as root is nearly always a bad idea. Why is this? If I have access to the root password, and can simply sudo commands as root, what is the functional difference? The only difference I can see is that I have to continually type in my root password for pretty much everything I do. Elevating a user to root status seems to require a call to the almighty.
I'm usually the only one with access to this system, and I generally like to add in user accounts for any other people that will use the system, and leave root for myself. What is the benefit of requiring 'sudo' all the time?
I need to run a command in a terminal, but cannot get root. I can in "Add Software" to install, I know and tried all the passwords I know from the install, but no show.What can I do?I tried sudo password, then typed in the space, no letters appear, but no success.TO "sudo password" after putting is my password, my username comes up and it says I am not in sudoers file.My Laptop has only one user, I know as I tried switching for a test.
In security terms, would using sudo instead of root be safer? I'd actually prefer to use this if so; I like sudo an awful lot. (It's Mark Shuttleworth's fault)
We have a couple of clusters that are running Oracle. If you're familiar with Oracle you know that it basically has to be installed as root. Something I detest. anyway, when we are building out the box, we change the root pw and give it to the DBA team to do their installs and configs. When they are done, we change the root pw (and do not give it to them), and configure sudo to allow them the rights needed to manage Oracle and their databases.
Now however, we have a different situation. The DBAs need access to uninstall and reinstall components and make modifications on an ongoing basis. Since we only support OS and hardware, not app, they are requesting permanent root access. I promptly told them no, and the politics ensued. Their manager went to their director, who went to my director, and suddenly an exception is given for his good golfing buddy. So here I am, forced to turn lose DBAs on my clusters with full root access/pw. I need a way to allow specific users (or perhaps a specific user group) the ability to become root WITHOUT sharing the root pw with them.
A few years ago I fellow admin showed me this command:sudo su - to change to rootIs this a 'best practice' method or a hap hazzard approach to system administration?I consulted with a senior admin and he frowned on this access to root.
I seem to only be able to start checkgmail as root. I have it listed as a startup application, and in the command line I entered gksudo [path to file]. How do I make it remember the password at each startup?
I want to use root password instead of adding my user to the list of sudoers,In Arch wiki ander Root password:Users can configure sudo to ask for the root password instead of the user password by adding "rootpw" to the Defaults line in /etc/sudoers: but that did not work for me. it asks for root password.Why do I want to do that: 1. I want to do that, I like sudo more than su -c 'some_command'. 2. sudo enables bash completion, su -c does not. 3. I don't want to add my user to sudoers list.
I found many users Suggesting alternatives and lowering the important of my need for this, when I asked this question in anther please.
When I run sudo as a normal unprivileged user, it asks for my password, not the root password. That's often convenient, but it reduces the amount of information someone would have to have in order to run commands as root. So how can I make sudo ask for the root password instead of the invoking user's password? I know it'd be done with a line in /etc/sudoers, but I can never seem to properly parse the BNF grammar in the man page to figure out exactly what to write.
It's been a few years since I last installed Ubuntu. I searched the forums and can't seem to find the answer. I want to be able to do a "su root" and have root access. I know Ubuntu wants you to do the sudo command, and I know you can really mess things up being root. I know I got this to work before. What do I need to do?
when I try to do admin tasks - e.g. setting my wireless connection to "available to all users" or updating a group's settings - it asks for "password for root" rather than asking for my password so it can sudo.I was forced to enable the root password, so I could do anything on my system ( sudo su; passwd; ) but I'd rather keep my root password locked and use sudo if possible.
On my ubuntu I have a command pm-suspend, which puts the computer to sleep. It has to be run with sudo. Since it is inconvenient to be forced to type the password every time I want my computer to sleep, I thought maybe there's a way around it. Naively I thought that if I'd create a script as root, that invokes pm-suspend, and then let anyone execute that script, I could run that script as my own user and then that script would be considered run by root and hence be allowed to run pm-suspend. Obviously that didn't work. The root-check procedure in pm-suspend still found out that the original executor was someone different from root.
Still I think something similar (although slightly more elaborate) should work.I'm thinking about the process that allows the user to mount hard drives for example. Normally root is required, but it is somehow bypassed by the gnome utility mounting.
Stumped on this one. I'm trying to set up limited sudo authority on a desktop with some sensitive user data, and as an extra precaution I wanted to configure sudo to use a password other than the user's or the root's. I'm not sure how to do this. From the manual, we have a few options, such as "runaspw" or "targetpw", but none seem quite what I'm looking for.For instance, "runaspw" could be used if I created a user for nothing other than sudo(ing) purposes, but it requires you set "runas_default", which means that said user would have to have authority to execute said commands in the first place. This is workable, but seems like a lot of extra configuration for each specific command that I want to run, as well as creating some issues with simply commands such as "shutdown" or "reboot". Also, "targetpw" can be used in conjunction with a sudo(ing)-only user if I set an alias, but, again, this isn't quite what I am looking for.
Ultimately, what I am really concerned about in this situation are keystroke loggers, so I would prefer to avoid repeated entering the user or root password when performing administrative tasks. Also, I would prefer not having to create a sudo(ing)-only user as mentioned above to prevent a comprimised password resulting in an attacker being able to log into my system.
I have just installed Lenny on a Thinkpad R50p. During the install I opted for no root password, using the sudo option instead (I've been used to this on Kubuntu for a long time). After installing, I added KDE 3.5 with apt-get install kde-desktop - all seems to be OK, except that I am unable to add packages or perform tasks for which a root / admin password is needed. It seems that the install-time choice of sudo (shared password) does not propagate to the KDE install, which is still expecting a root password.
how to either enable the KDE desktop to work with this shared password setup, or whether there is a better route to a KDE 3.5 desktop than just installing as I did (I am aware of Trinity KDE 3.5 but the Pearson Computing source is still not up, are those packages available for Lenny anywhere else, and are they recommended?). I can of course rerun the whole install and choose root & user passwords but if there is a smarter solution it would be less of a 'reinstall Windows' type of fix
I've had a very frustrating time the last few months trying to find a KDE4 based desktop that is stable enough and not lacking some basic functions (print manager, for goodness sake), so I have temporarily thrown in the towel and will try a Stable installation that is not changing (breaking) all the time, until KDE4 series gets past this adolescent stage of development and settles down.
I do need to get back to a system I can work on rather than keep on trying different installations!