Debian Multimedia :: KDE 3.5 On Lenny Root Password Or Sudo?
Aug 14, 2010
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!
Testing an upgrade Etch>Lenny 5.08, and one issue I've found is that "sudo konqueror" in a teminal no longer gives root priveleges, instead konqueror starts with limited rights. It also seems that using a .desktop shortcut, an attempt to run konqueror under any credentials other than the logged-on user fails.
Yet, 'sudo kwrite' works. Anyone met this before, or know why?
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?
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 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.
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.
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.
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.
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'm on Squeeze with KDE 4.4.5. Basically, I can use my password for things like logging in, or authenticating on a shell with sudo successfully. But in other cases, I am asked to "become root", and when I enter my usual password, I'm told to check if I entered my password correctly. This happens with Aptitude (terminal GUI), for example: from Actions, I try to update the package list, and when I enter my password, I can read su: Authentication failure. However, if I start Aptitude by typing kdesudo aptitude on Konsole I can enter my password in the authentication box successfully, and use Aptitude with administrative privileges.
The example is valid also for other applications, such as System Monitor: just for the sake of the example, if I try to stop a process owned by root, say Aptitude, I'm asked for a password to become root, but my password doesn't do the trick. I'll have to open it from terminal with kdesudo ksysguard, then I'll be allowed to kill that process. Does it have anything to do with my choice at installation? I think I must have chosen to leave the root password field blank, and only entered my password as a user, for it explained I could become root anytime if there was need to with sudo.
I upgraded from Super Ubuntu 2008.11 to Ubuntu 10.04.1 online ( my mistake ). Now I can boot into Ubuntu 10.04 with 2 kernel options and a failsafe. However I can only boot as a user ( rejean ) and not as su or sudo. My other problem is that I don't have a gui. I would like to do a Code:sudo dpkg-reconfigure xserver-xorgbut there is no password that works.What should I do?
In Ubuntu 10.04, I logged in as user1 and when I open a new terminal and issue any command it is asking password.user@ubun-laptop:~$ sudo ifconfig[sudo] password for user: It is asking for password only for first time.From the next command onwards it is not asking.Can some one please tell me if it is possible to issue ONLY ONE COMMAND, in which even if the password request comes, it will automatically fill the password.Just like "ps -elf | grep NetworkManager". I am expecting any combination of commands in a single line, so that password is filled automatically IF PASSWORD IS ASKED. If password is not asked, the command must be executed.
Before upgrading to Lenny there was no noticeable delay between entering a username & the prompt for a password when logging in via ssh. Now there is about a 5-second delay which is rather annoying. There is no delay when logging in through the Gnome UI. Anyone know why the delay is there? Is it something about ssh under Lenny? Is there a setting that can be changed?
is there a way to auto login as root? login in window preferences won't allow me to select rootPS before anyone starts on the me bad, I'm a programmer using it on a closed embedded system, and need to link to others software, and need to be root
I edited fstab to automatically mount my windows data partition on boot, but I screwed it up by not specifying the file system type, however that is not the problem, I was able to fix that easily. The problem was that when it failed to mount the partition, Debian automatically entered root and I guess that is to be expected in order for me to fix it, but I never configured a root password and it just gave me full root access without asking any password, not even my user password. I though that was strange so I set the root password and sure thing it asked me for the root password this time without automatically logging into root....
I then tried to lock the root account to see if it will ask me for a password or not, it did but of course I wasn't able to login as root because it was locked now and I was left with no way to access the system. I had to fix fstab from a live cd so that I can login normally as the user....
I didn't know what to search for or if that is the expected behavior if you don't set root password during installation, but it just seemed a bit strange to automatically enter root when you specifically disable root login during installation...
I have succesfully installed Debian with gnome-core, iceweasel and other useful packages and also followed this guide to autologin and start X. I noticed that the sudo chmod +s /sbin/halt and adding /sbin/halt in ~/.bashrc made Debian refuse me to log out (from X) and 'log out' turns off the computer insted.Removing /sbin/halt from .bashrc turned everything to as i want it. Should I "repair" or remove something I created with chmod +s command or should I leave it as it is?
Also I would like apt-get(or aptitude) update to run after login (and before startx), so i added sudo apt-get update to .bashrc but it will prompt me with password. Is there someway I could do this without the password(s) which su/sudo needs to execute? This is not so important but it would be very nice to update the system on startup.
I have two machines running Debian Squeeze (a laptop and a desktop). On my laptop sudo works fine, however on my desktop sudo doesn't remember my password for 1 second!!! I have created a script for the upgrade procedure with apt (to make things easier). The script is nothing more than a few commands separated by operators. It is completely useless if I have to enter my password six times while my script is running.
I tried to add timestamp_timeout=15 to the sudoers but it didn't help.
I have attempted to install kernel 2.6.34 and 2.6.33 kernels with this Debian howto [url] Everything worked without any errors until I went to boot into the new kernel. When I receive this kernel panic output Kernel panic - not syncing VFS: unable to mount root fs on unknown-block(0,0)
It also spits out something about being unable to access ext2 FS. I googled this symptom and have seen that it is fairly common, but everyone's error seems somewhat unrelated. I used the same kernel configuration as the one that is currently working, to keep things simple.
I installed debian etch on my system. Installation done successfully, but when it boots up the X server is not starting and showing error. Note : It is perfectly working with debian lenny. Configuration : Intel DG41RQ ,1GB Ram ,160GB HDD.
I needed to use Synaptic Package Manager to install an app, but the dialog box ("enter the Administrative Password") that pops up before you can use Synaptic doesn't recognize my password ("incorrect password). I tried typing it into a text editor and it's spelled right, caps lock not turned on or anything.
In Terminal, sudo recognizes it, and it is recognized when I log into Ubuntu. I'm the sole user, I have admin privileges, I've been doing admin things.
I just now did System > Administration > Users and Groups and got a dialog box saying
"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 [URL] for information. (Details - 1: Server ping error: IDLmg.org/CORBA/COMM_FAILURE:1.0)"
Moving past that, I changed my user password, and Ubuntu authenticated it.
How do you launch Synaptic Package Manager from the command line?
recently installed lenny (5.0.4). I can't get any sound whatsoever (except pc speaker). I had to muck around with vlc to get video working, that works fine but there's still no sound. I have a C-media CMI8738 sound card, I've run alsaconf in root which seems to work fine, I've mucked around with alsamixer (v1.0.16) changing volumes and muting things but haven't had any change. Computer is an AMD Athlon xp2500.
I have a computer that is off the internet. It usually works right since I took great care to make it as 'clean' as possible from outside forces.Lately it just hangs whenever GDM is about to start.How to troubleshoot?
I tried a live CD SystemRescueCD, it works even the desktop environment works. so I e2fsck the partitions of the hard drive okay, memory test/checked the 1.2GBRAM -- passed other than these, I have no clue how to troubleshoot.Oh, I also used an nvidia driver which I forgot how I did it because it was installed almost a year ago.
I tryied to modify the root password, but instead of using the "passwd" command, i tried to use "usermod -p", without knowing what outcome exactly i would get. But since then, i can't log as root, neither with my old neither with my new password. And i can't install absolutely nothing on my machine.
Please, help me... i have a test next wednesday, and i can't work in my blueprint. In appendix, i've uploaded a print screen of the sequence commands, for you to be able to explain me this phenomenom and to tell me how to solve it.
I just did a net install of Debian Jessie in VMWare Player. I very much enjoyed the install. I chose not to install a desktop. I set the root password as root. And the user as paul/paul. Now I cant login in root, it says I have the wrong password. How would you resolve this?