I can't login after the password-protect-screen-saver comes on during a download.The screen is black, the cursor arrow moves with the mouse, but no login window.I have no idea what is wrong but it seems to correlate with this combination.
The login screen does not accept the password for users. Only the password for Root. The problem is not in the command line, but check the password in the screen. I have tried to change the password from the root and it is still the problem. What I can do?
I have just bought a PC with SUSE 10.1-0. The first time I started the PC an installation menu appeared. I didn't define a user name, thinking that it should log in automatically (as in Windows occurs), but now I can't go farther from the Welcome screen, due to the system is asking me de user and password, but I didn't introduce nothing! Leaving username and password in blank didn't solve the matter.
I can see the admin screen (pressing F10) but I am not able to find any user to log (logically) and I can't include new users from there.
I have also tried to install Windows XP modifying the BIOS but the system returns a message (once in the WinXP installation program) about an error called 4096, about the file i386halaacpi.dll, which is unable to find (something about the HAL), so I am afraid that my (new) RAM memory is damaged.
What could I do? The system is for an old person, so I would like to install finally WinXP and delete Suse.
Is there anyway to make the lock screen password (accesible when clicking the power icon) different from the username password ?Or to lock the screen, with a different, User defined password, seperate to the Default one ?
When I hit Alt+Ctrl+L my system is starting the ScreenSaver but not locking the screen. The keybinding is correctly set. This is happening in only root account but in another user account it works perfect !
What happens is that I resorted to deleting my .kde directory after my kid destroyed my profile where title bar, menu, konsole get broken. After deleting, I login again thus regenerating the .kde directory. To avoid my kid from messing my desktop, I tried to lock it. It does not lock.
It just need a KDE full restart perhaps since when I login the other day, it now works.
I'm updated to Slackware current for almost a month already and have not played a lot on KDE desktop (busy programming stuff).
However, on day I tried to lock the desktop in KDE to avoid the kid from destroying my cool desktop setting, but it didn't lock. Cool, so I tried screen saver and add an option to lock the screen.
When I test screen saver, it displays. But when I wait for 1 minute(I set it that way), it doesn't fire up. Not even after 15 minutes which I think the default.
It usually work before (several months ago) using the lower version of KDE. It is just last Saturday that I noticed it.
I tried to dig the profile management but I could not find anything relevant there.
what program runs the Session lock and the screen saver for gnome and KDE on centos 5.5. But most importantly id like to know what the config file for the screensaver/session lock is called and where its most likely located.
I am having an issue with my screen lock, sometimes when my screen locks and I try to enter my password i get the "checking" message and then about 5 mins later it will timeout and let me try again. On the 2nd retry it will let me get in.
brand new 2 Ubantu & set up standard Ubantu compartment accessed via 1 user name only and password. 1st few times all good but now suddenly, unexpectedly password declared invalid. Had written down password so it is correct & not entry error. Not know how to reset password or bypass 'username/password log on screen' Am on an Acer 5542G with windows 7 home premium.
When I was using AntiX, I liked how I could just type "xlock" in a terminal and it would lock the screen until I came back and typed my password. I saw that there was no "xlock" package, so googling around, I saw it was replaced with xlockmore and xlockmore-gl, neither of which there seems to be a package for in the Squeeze repositories. I tried xscreensaver, but I prefer the simplicity of xlock (and I like that it doesn't leave a daemon runnig when not in use). Is there a way to safely install it, or should I just be looking for an alternative?
I just set up my Debian 8.3.0 Jessie install a couple of days ago. Today I am having a problem carrying out a command in terminal. All I want to do at the moment is make sure my firewall is active. I log in and out of my computer using the password that I set when I originally installed Debian, and I use the same password in the package updater, but today it would not accept that password in terminal. Here is what I am seeing;
rocky@debian:~$ sudo ufw-enable [sudo] password for rocky: rocky is not in the sudoers file. This incident will be reported. rocky@debian:~$ sudo ufw-enable [sudo] password for rocky: Sorry, try again. [sudo] password for rocky:
i set my pass on ubuntu 10.4 and it work so good on installing app but suddenly it stopped working i thought i would restart my pc i tried to inter my pass again ubuntu don't accept it although it's surely true
I have this issue on both Ubuntu and Lubuntu 11.04 64-bit on 2 different machines. I have not tested 32-bit.
When I run synaptic or update-manager it presents me with gksu, not gksudo as it previously did in previous Ubuntu releases, no matter how many times I try it will not accept my password.
I have even given it command line arguments to print the password to the terminal and it's correct.
I have found a workaround - by running gksu-properties and changing the mode from su to sudo it will now display gksudo and accept my password.
However, I want to know why it won't accept my sudo password for the su and gksu commands? There are no error messages which are outputted, the gui just says incorrect password.
The asterisk I downloaded came with Centos 5.3 It runs well on VM console But the problem is when It request for localhost login which accepts input but the password does not accept input at all.
I have recently installed CentOS 5.4. I went ahead and enabled encryption for the root partition. everything was fine for the first few days, but today it started refusing my password on boot. The weird thing is after refusing the password several times it accepted it once, then when I rebooted to test refused the password it had accepted moments earlier. I guessed the password file got corrupt or something so I did a clean install. During the install it asked for the password to access the partition and accepted (!) the password. I went ahead and deleted the old partition and reinstalled from scratch just to be sure. And I made extra certain I put in the correct password with no fumble fingers. Sure enough the blasted thing refuses the password I just created during boot. However, if I input the password into the setup it accepts it. What the hell is going on here?
Code: Select all:~$ su Password: #Typed user password su: Authentication failure ~$ su Password: #Typed root password su: Authentication failure :~$ sudo su
[Code] ....
The file does open but with a warning in red saying i could harm my system. Had almost got everything configured just as like it, tried adding a custom action (open as administrator) to Thunar and my house of cards collapsed around me.
Debian 8 xfce, single user account, passwords and user names are single characters so it's a given there's no typing error.
Code: Linux tmif3 2.6.9-5.ELsmp #1 SMP Wed Jan 5 19:29:47 EST 2005 x86_64 x86_64 x86_64 GNU/Linux I added a user useradd billy because I don't like being root. I changed the password using passwd billy all as normal. when I try to logon, ssh rsh I cannot. even as root with an su - yields the following..
I have just completed a debian netinstall, but am stuck at the "Welcome" screen. Though I took careful notes during the install re the "user account" (did not use my name as my purpose is to get the pc running and give it away) and "user password," it will not accept them. I would like to change or edit both (debian isn't telling me which is incorrect). How can this be done?
Also, this is looking for the "user account" - not the root info, right?
If I am forced to reinstall the OS, will I have to go through the entire process (partitions and all)?
My 1st time using Terminal with sudo it would not accept my password.I use it successfully to log in and is the only password i used during installation.is there a way to get terminal yo accept my password-it does recognize my user name.
Just installed SUSE11.3 and everything was ok until did initial online update. Following update, YAST will not accept root password when launched from KDE (have not tried other window managers). Dialog box is presented to enter root password. It reports back "invalid root password". But I can run yast or yast2 from command line (as root) and that seems to come up, but not all items seem to work.
I can log in as root with no problem. Only YAST will not accept my password. I'm running KDE on a Dell D610. Ran SUSE 11.0 for several years, absolutely no problem.
I'm running 64-bit 11.3 on a Dell 1535 laptop.At lunch today, the system booted-up as normal, then shut-down as normal. A handful of updates were installedduring that time.This evening, however, I arrive at the password splash screen, enter my password, and then the system churns a few seconds before resetting the splash screen. No error message, no "wrong password," just a normal splash screen. I tried going into Xen, the default 11.3 and failsafe -- same thing happened with each. When I navigated to the command line, my password worked fine, both for user and super-user.
I just reinstalled ubuntu lucid after accidentally damaging it, And I used all the same passwords and user names as before, I can login fine, and I can do sudo commands, but the gnome keyring wont accept my password, I tried changing my password using Applications>accessories>Passwords and encryption but that didn't work. How can I fix this so that keyring will accept my password, I need it to save my wireless router password.
For some reason, several irksome changes have occurred. The worst is that it won't let me log in. It will not accept my password.? I was told that if I downloaded Ubuntu, I could use that to get to control panel and fix the problem. After 4.5 hours on another pc, I had the download and the cd does boot Ubuntu. What is my next step I have no working knowledge of Ubuntu.
I recently did a clean install of Maverick Meerkat and copied a few configuration files from my old system. I can log on normally, and the system works just fine. However, when I lock the workstation with any method, the system will not accept my password. I'm certain that I'm typing it correctly (I tried over 20 times) and that the capslock is not on. When I reboot, I can log in again just fine. In other words, my password only works at initial login, not when unlocking the workstation.
