I'm on KDE 4.4.4 and kdesu doesn't use sudo -- at least it's still asking for a password when I have the appropriate NOPASSWD line in /etc/sudoers (checked with command line). I'm following instructions here, Default kdesu to use sudo and not su | Free Techie Blog
View 2 RepliesI've recently installed from scratch Suse 11.2, and I'm having a bit of an issue with kdesu. Basically everytime I try to start an application using kdesu (e.g. Yast), the windows where to put the password appears, but when I click on OK, or I press enter nothing happens, the windows stays where it was, and of course the program does not start. The same issue occurs when I type the password to open kwalletmanager, I suppose the two things are connected.
View 9 Replies View RelatedAfter I upgraded my suse 11.2 to 11.3 (via zypper dup, all worked well), kdesu is not working anymore. A "kdesu -c /sbin/yast2" for example will not produce any output in the terminal.
View 1 Replies View RelatedNot sure but has support and updates for 11.2 come to an end? Every monday morning i make sure i'm upto date with updates etc. This am i get a message saying "repo not available" and having looked online to see if the directory openSUSE_11.2 exists, it doesn't.
At the same time loged in as a std user i regularily offer the command kdesu kwite. the command is accepted without error and the cursur returns on a new line as expected but kwrite doesn't start. I'm guessing that my last update has left me with a broken OS. It doesn't seem very long at all since i installed 11.2!
it seems that kdesu either isn't installed or isn't enable in squeeze, or something. Anyone know how to get it working? when trying to launch dolphin:
Code:
lain@debian:~$ kdesu dolphin
bash: kdesu: command not found
Code:
root@debian:/home/lain# apt-get install kdesu
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package kdesu is not available, but is referred to by another package.This may mean that the package is missing, has been obsoleted, or is only available from another source
E: Package 'kdesu' has no installation candidate
Using squeeze 64 amd64, with KDE. I just need to launch the nvidia settings gui as root.
I have an intermittent problem with kdesu not starting. I can boot and start kde4 and kdesu will perform properly for the full session. If I reboot, there is a chance kdesu will not work at all that session. Yesterday just restarting KDE4 was sufficient to get it back, but today it took two machine reboots.
When it fails it just hangs with no indication and nothing in /var/log/messages.
I had no problems with the previous kernel, 2.6.34-gentoo-r6. I just moved to 2.6.34-gentoo-r12 adding nfs.
Instead of logging out and in again as root, I tried running the file manager dolphin through kdesu, but this was very slow and crashed eventually.
View 1 Replies View RelatedWith Slackware 13.1 I decided to switch to Xfce, but as I like Konsole I'm using it under Xfce. I like to have Konsole being fired up with root privileges, so I added Launcher to Xfce panel with command as follows:
Code:
kdesu -c "konsole -e /bin/bash -l"
Now, when I open the Konsole with this Launcher everything is fine, I can run commands as the root user. But if I try to use tab completion in bash, the CPU usage suddenly goes very high. I found that the process causing this problem is:
Code:
dbus-daemon --fork --print-pid 5 --print-address 7 --session
and it is owned by root. When I kill this process the CPU usage gets normal, but I'm not able to run Konsole with the Launcher any more. The only way to get it back is to kill all the kdesu (owned by me) and dbus processes (owned by root). I also noticed that normal user (that is me using Xfce) has also exactly the same dbus process running, that is
Code:
dbus-daemon --fork --print-pid 5 --print-address 7 --session
BTW, this doesn't happen when I run xterm or Termianl. Also, using
Code:
kdesu dbus-launch konsole
gives the same odd effect. So I'd like to ask how can I solve this problem? I'm running Slackware 13.1 with Xfce 4.6.2 built with Robby Workman's SlackBuild [URL] with the source code modified so it runs KDE4 services (kdeinit4 and krunner) instead of KDE3 services (kdeinit and dcop). I have also my own custom kernel, but I think it's not relevant in any way.
explain the difference between these two commands. I'm currently reading about changing your mac address and both of these commands show up a lot. They sound like the same thing to me. Is one better than the other, or do you need to use both to change your mac address?
Code:
sudo ifconfig eth0 down
sudo /etc/init.d/networking stop
I have a problem when I want to use su I get this error:Code:su: pam_start: error 26I have googled it so I found this topic (http://www.linuxquestions.org/questi...r-26-a-615024/) but it didn't really help me. There was a reply on that topic and his question was what the output of this was:
Code:
ldd /usr/bin/passwd
and
[code]....
A day ago I finally got around to upgrading the PackageKit installation that had been sitting for a week and a half, so I found a new upgrade for sudo available - the one that gives the sudoreplay command, I forget which version number it is exactly. When I try to use the sudo command I get this notice in my terminal:Code:Can't open /var/db/sudo/me/1: Permission deniedI didn't get it before. What do I have to do to make it open? I'm using SELinux in enforcing mode if that helps.
View 1 Replies View RelatedKernel 2.6.21.5, Slackware 12.0
Code:
Code:
On the other hand
Code:
So, I do not understand why the notification "sudo: cd: command not found", considering cd is a bash built-in command.
I have read a lot of questions from people wanting to take Debian (or some other distribution) and make its sudo command act more like the way Ubuntu's sudo does. I want to do the exact opposite, I want to make Ubuntu's sudo command act more like the sudo command from another distribution. ie I want there to be one root password
View 8 Replies View RelatedI try to run a command located in /sbin or /usr/sbin using sudo, like "sudo ifconfig" or "sudo tail -f /var/log/messages", it comes back with "command not found". If I perform a "sudo -i" and drop to a root shell that way, the commands work fine. My sudoers file is as follows:
Code:
Defaults always_set_home
Defaults env_reset
[code].....
I would like to have an user that can execute al command with sudo.I configured sudo with yast2 and in the sudoers file actually there is a line with:USER ALL = (ALL) ALLWhere user is my username.But I can't use some command like ifconfig becouse it say that it can't find the command. I think that this is becouse of path, but shouldn't i get root path using sudo?
View 3 Replies View RelatedIs there a way to change the sudo password after installation has taken place? I know you can change the user password via that box in 'About me' but that still leaves behind the old sudo password.
View 1 Replies View RelatedI am wondering what the easiest way for me to disable su and perform all root stuff using sudo, the way Ubuntu works. I am using a shared system, openSUSE 11.3, and notice that the only item that gets logged in su is who su'd. I need more information and sudo + command gets logged to /var/log/messages so I can see who did what and when. How can I get openSUSE 11.3 to work similiar to Ubuntu when it comes to running elevated commands or editing files that a normal user doesn't have rights to?
View 9 Replies View RelatedInstall wireshark and added it to visudo. But wireshark refused to start in konsole
Code:
# sudo wireshark
(wireshark:7493): Gtk-WARNING **: cannot open display:
However, wireshark will start without problem when in root.
How do you setup the sudo command so that it will insult the user if they enter the wrong password? I know it sounds kind of random, but I found that it was an option while looking up something else. I tried adding "Defaults insults" using visudo, and commenting out "Defaults targetpw" and "ALL ALL=(ALL) ALL", and adding my username as "blank888 ALL=(ALL) ALL" but I still can't get it to work right.
View 9 Replies View RelatedI'm using Debian and openSUSE 11.2 and the sudo-ing is a bit different in Debian. It actually makes more sense to enter your own password like in Debian to achieve sudo status than have to use the root password for sudo status. If I for example would like to give someone on my system sudo rights, I can't give them the root password. Thats just like giving them root access. Or is there a way to change that behavior, or just change sudo password, in openSUSE? Or maybe any other best practice for giving users sudo rights?
View 6 Replies View RelatedI have joined the domain (server 2003) and can log in consistently now. Now I would like to give all the windows users in on specific group (domain power users) SUDO rights on the machines in question. I have found one way to add users on a pr. user basis, but adding 30 users will take some time.
View 4 Replies View RelatedI am trying to edit a postinfo.xsl in my root file dir, and with the command:
frank@linux-avnb:~> sudo gedit
(gedit:14150): Gtk-WARNING **: cannot open display: frank@linux-avnb:~>
I get the following. what am i doing wrong?
Where is the SUDO file at, and remind me how do I add myself as a SUDO'er?
View 3 Replies View RelatedIt is my understanding that they do the same: they ask for my password (if I am allowed in /etc/sudoers), and give me a login shell as root.
Is there any difference between them?
sudo su -
sudo -i
Also, what's the difference between
sudo su
sudo -s
I think that they both ask for my password, and give me a shell with my old environment variables.
I am having trouble running commands by using sudo. I configured visudo file with localuser ALL=(ALL) ALL but I can't run any command, it tells me command not found.
View 8 Replies View RelatedAfter upgrading GNOME to 2.32 in my openSUSE 11.3 x86_64 running graphic applications with sudo is impossible. (that means it worked before upgrading GNOME)
Code:
etam@etam-laptop:~> sudo xeyes
root's password:
No protocol specified
Error: Can't open display: :0.0 From /etc/sudoers:
Code:
Defaults env_keep = "LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS XDG_SESSION_COOKIE XMODIFIERS GTK_IM_MODULE QT_IM_MODULE QT_IM_SWITCHER DISPLAY"
Some interesting facts:
[code]....
I am new to fedora (been using debian based distro's for the longest time). With the new release I decided to give FC13 (The kde 64 bit spin) a try. I told it to wipe my entire hdd and encrypt the partitions. The partition manager made a few LVM partitions which I assume are encrypted.
The problem I am having is that if I attempt to use an application that would normally need root access to run, I am not prompted to enter my root password. Instead, I am required to logout and log back in as root. Is there a way to make it so that FC13 will prompt me to enter in my root password so I do not need to log in and out? Or is there something Different I should have done during the install process? Also, what is the terminal equivalent of "sudo" in fedora, or is it still sudo/KDEsudo
I also have not used SE Linux before. Do I need to manually enforce the permissions for my applications and generate my own profiles for it, or is that done automatically?
I just upgraded opensuse from version 11.3 to 11.4 using the online method changing the repositories. But now when i log into my gnome session as "normal user" and open a gnome terminal, then trying to launch a graphic application such as gedit or any other application that relys on X, it returns a problem such as:
Code:
GLib-GIO: ERROR: gdbusconnection.c:2279:initable_init: assertion failed: (connection->initialization_error == NULL)
The message can show once or repeat several times. I didn't have this problem before.
I set-up my Sudo it works but when I use Gedit I get the following message
Jean-Luc@localhost:~> sudo gedit /etc/fstab
(gedit:7137): Gtk-WARNING **: cannot open display:
samething with /etc/sudoers
If I use vi it's ok, I can modify and save. In Fedora it run ok, but with opensuse?
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 ?
View 3 Replies View Related