Ubuntu :: Can't Log In \ Introduce Password The OS Takes Every Single Letter As An 'intro'?
May 29, 2010
Everytime I try to introduce my password the OS takes every single letter as an 'intro'. If I want to type, for example, 'batman', it will take every single character as an intro and therefore I can't get access to the OS.... what can I do?Btw, all of this began when I was trying to write something in a console. When I tried to type anything in the console was like If I was clicking on the 'close window' button, so I though I was a little bug and I had to restart.
i'm trying to make a folder on fat32 partition named NEW by typing in console mkdir NEW, then i open PCMan file manager then go to that folder at first the folder name was NEW but after i doubleclick it and go back the folder name was changed to 'new'then i tried to rename it to NEW but it says file exist then i tried to rename it to 'not new' (this time inside PCMan) and it work then i rename it again to NEW, go into that folder and go back again... the folder name changed to 'new' again.anyone know why this happen?? this doesn't happen if i make the folder name more than one word such as 'NEW NEW'
Ubuntu boots normally, and the login screen appears. When I press the 'g'-keybutton (the first letter op my password), the system complete reboots. Pressing the 'q' does not cause a reboot. Filling out my password using the onscreen keyboard goes OK. After logging in (using the onscreen keyboard method), I can just press the G without problems, and the system is stable.
I have a Sony laptop CPU 2.80GHz HDD 60Gb and 512Mb RAM. I have defragmented.I downloaded Ubuntu 9 and burned to CD and all begins well as follows:
1 booting logo 2 Opening dialog screen 3 screen full of text(lasts about 5 seconds) 4 a screen full of mosaic patterns appears 5 a mauve screen flashes (with small rectangular patterns on it 6 that's it - I have to switch off after 10 minutes or more!
Sent for the CD from Canonical - same happens as above. A friendly suggestion offered was to try the alternate iso. I downloaded this and unzipped the files. These are scattered around the desktop in folders and files. How do I burn these to a disk?(get them together or just start with the"install" folder?)I'd like to persevere.Hello! I have a Sony laptop CPU 2.80GHz HDD 60Gb and 512Mb RAM. I have defragmented.I downloaded Ubuntu 9 and burned to CD and all begins well as follows:
1 booting logo 2 Opening dialog screen 3 screen full of text(lasts about 5 seconds) 4 a screen full of mosaic patterns appears 5 a mauve screen flashes (with small rectangular patterns on it 6 that's it - I have to switch off after 10 minutes or more!
Sent for the CD from Canonical - same happens as above. A friendly suggestion offered was to try the alternate iso. I downloaded this and unzipped the files. These are scattered around the desktop in folders and files. How do I burn these to a disk?(get them together or just start with the"install" folder?)
I recently upgraded the memory in one of my computers running Ubuntu 10.10 amd64 to 4GB of RAM from 2GB.It's a Biostar TA690G AM2, with an Athlon X2 BE-2400 in it. It supposedly supports up to 4GB of RAM when done as 4 1GB sticks, at least according to the original manual that came with it. Upon start up, I no longer get my login screen, it appears to crash when it gets to the part where it starts up Xorg.
At first I figured the memory might not be happy with the computer so I ran Memtest86, every thing seems fine there. So I try the recovery boot to the root prompt with networking. Everything seems to work fine there, at least as far as a root prompt with no gui goes.. However, if I try startx here, it crashes again.
Ok, so I then try an Ubuntu 10.10 amd64 boot CD. I get the Try/Install buttons in the little Xorg intro gui running. It's getting my hopes up now. However upon clicking "Try Ubuntu" it thinks for a second or two and then locks up, with the busy mouse cursor icon still spinning. I don't have windows installed on this computer, so I can't really say that it works fine in windows.
Is there some weird BIOS setting or xorg.conf setting that needs to be enabled so that it doesn't croak? The Bios recognizes the memory, Memtest86 recognizes the memory, and Linux recognizes the memory (at least until xorg starts). If I pull one of the sticks out, it will once again run, but then it's in single channel mode, and I'm missing out on 1GB of RAM goodness.
In a desperate attempt to overcome frequent crashing accompanied by XLog lines that suggest to me that Pulseaudio is the cause, I removed Pulsaudio from my Ubuntu 10.4(LTS) using Software Centre. Now I cannot start up Ubuntu but I can get to Terminal via the Recovery Mode. My question is how can I use Terminal to re-introduce Pulseaudio so that I may get back to where I was, albeit with the random crashes that I have had for many months?
I want to create a script in bash to allow me to retrieve some files I have in a cluster. Access is through ssh, and the command I use to copy files is scp. The problem here is that when the script is run it asks for the password three times (it is instructed to copy from three different folders).
Code: scp user@server.com:/home/user/FolderA/* user@server.com:/home/user/FolderB/* user@server.com:/home/user/FolderC/* it still asks for the password three times. Is there a way I can use scp that asks for the password once?
I want to fix my disks with fsck but using sudo init 1 is not allowing me in. It shuts my services down, then gives a "Give root password for maintenance" prompt. I've tried my password, but it rejects it.
I have ubuntu 11.04 installed along side windows. And I often share files with windows computers. If I am installing a new package from ubuntu software center, and consquently I have to log in as root to do so, which means I have given the system 'privileges' as the program is being installed, I decide to go open mozilla, and surf suspicious sites on the net. Is it possible in that case for me to get a virus?
When we enter the password for the root user in order to run one program such as ubuntu software center, does that mean that all programs have root privileges for the time being (as the software center is installing the program)?
It seems that every time I use the 'sudo' command I have to type a password. Is there a way to get 'sudo' to remember the password at least for the current session after I use it once or something like that?
I am trying to create a "GUI File Transfer " Application , for transferring the files within the network. For That I will obtain User name, Password through the GUI, I will have to append username and password in a single line and run it . I am facing difficulties in exploring the "command",
Still working scanning results, this time with DISA's SRR scripts.More than one scanning package complains about;The UNIX host is bootable in single user mode without a password..So, I assume in /etc/passwd there is an entry that corrects this?what is the specific syntax and where does it go ?
My question is probably very common, but I didn't find an answer.I have several computers, each with different user. Each user has a shared folder in samba. I want all users to access all these shares with a single login/password (not with the login/passw of each particular user)
I wish to allow a user to use sudo to run a single command (service app status) to determine if my application app is running, in my sudoers file i have: user ALL= /sbin/service app status I understand that there is a parameter called timestamp_timeout that will set the timeout for the 'user', but requires at least 1 entry of the root password.
I wish to allow the user to do "sudo service app status" and not have to enter the root password ever(maybe once is ok), but still make the user enter the root password for all other root activities. Is there a way to prevent the password entry for this command only and no others?
I need to recover the root password or reset it. For this, I am trying to follow the following steps to get into the single-user mode & where exactly I am getting stuck: 1. Reboot the machine2. Press <esc>3. At the boot loader screen, i have 'Red Hat Enterprise Linux Server ($version info)' highlighted. 4. Simply pressing 'e' (for editing) does not work (does nothing). 5. I have the option to press 'p' to enter boot-loader password and then go into the single user mode.What if I don't know the boot loader password as well & I want to get into the single-user mode WITHOUT using a boot CD? Is this possible? If so, please share the procedure to do so.
Can someone assist me with recovering/resetting the password for Root via Single User Mode in CentOS v5? I've modified the kernel line using Single, S, and 1 but it appears that these commands are being totally ignored as the server continues with the boot process and displays the GUI logon screen. The server in question is a VM box running on ESX v3.5 U4. The person that created this VM is no longer employed here and I've exhausted everything I know regarding Single User Mode.
I followed instructions to enter single user mode by adding single at the end of kernel line but after that it doesn't ask for root password but brings up the sh# prompt. Isn't that supposed to be insecure? I understand for this the grub password can be applied but even after adding "single" it should ask for root password..or it should not..??
When I go to single user mode for resetting root password, It ask root pawssword for login.The message displayed on prompt is "Give root password for login.On the boot prompt, I select kernel and press 'e' and after one space type 1 for single User mode and then press 'b' for booting.It shows message entering in single user mode but ask root password. Even I tried into rescue mode, but I couldn't ser root password.In rescue mode on prompt, It shows rescue login: I typed root, But when typed 'passwd' foe resetting root pawssword,It shows message unknown user and not authetication.
Being able to reset the root password by booting into single usermode by editing grub. This is a MAJOR flaw. I know it makes no real difference against internet bourne attacks, but even so I must say I found it shocking. The only way I've found to stop this is to encrypt the entire HDD, so noone could get into single user mode without first knowing the encryption key/password.
I am running Centos 5.3. I ran no updates, performed no installs, nor changed any configuration immediately prior to this issue. My problem is this: when I run the command startx (default runlevel 3), it is a long time (5-10 minutes) before Gnome startx, and once it does start applications will not run. Also, when I try to use sudo (from any environment, even ssh), it is a long time (5-10) before the command is executed.
I cannot say for sure, but it seems like this is an intermittent problem. Sometimes X takes a long time to start, but once it starts it will launch programs. Sometimes X takes a long time to launch, but once it starts it will only launch certain programs. Though presently X always takes a long time to start, and I cannot successfully launch any programs.
A while back a had a similar problem to this (x taking long time to start, sudo taking long time to execute) and it ended up being a DNS problem. Unfortunately, I cannot remember exactly what it was and I stupidly did not document it. Maybe this is also DNS related, I don't know.
I don't know what log files to look at for problems with X, Gnome, and sudo taking a long time to start.
I have question about the UNIX sockets. my goal is to connect multiple sockets from a single client to a single server and keep them open...I'm not sure if that is possible to create or not. Do you have any suggestion or an example of code?
