Results 1 to 4 of 4
After my last update, when I start the FC14, there will be amplifier like program started on the righ side of my screen. It will take nearly half of the ...
- 10-27-2011 #1Just Joined!
- Join Date
- May 2008
- Location
- Wuhan, China
- Posts
- 11
[Help]Can't Input password on the login screen, FC14 64 bit
After my last update, when I start the FC14, there will be amplifier like program started on the righ side of my screen. It will take nearly half of the screen. And a GOK Keyboard will be shown.
I tried to login by terminal mode. And removed the gok. But the amplifier still there, and password can't be input.
How can I remove this amplifier on the login screen? Thank you!
- 10-28-2011 #2Linux Newbie
- Join Date
- Nov 2008
- Location
- Tokyo, Japan
- Posts
- 243
I believe the "Amplifier" program you are referring to is may be the "Conky" program, can you try to take a picture of it and post it on this forum? If I am right, you can just un-install Conky.
You can press "Control-Alt-F2" to hide the Graphical User Interface. You should see a command line terminal, and you can login with your usual name-password. Then use "yum" to remove conky:Enter the root password to begin the un-install process. Finally, type "exit" to log-out of command-line terminal, and then press "Alt-F7" to go back to the graphical login screen.Code:sudo yum remove conky
- 10-28-2011 #3Just Joined!
- Join Date
- May 2008
- Location
- Wuhan, China
- Posts
- 11
Hi Ramin Honary:
Thank you for your reply. The command to switch the terminal and graphic screen is very helpful. I have tried "sudo yum remove conky", but it shows conky was not installed.
How can I check what programs the Linux started when it is start up? May be we can find it.
- 10-28-2011 #4Linux Newbie
- Join Date
- Nov 2008
- Location
- Tokyo, Japan
- Posts
- 243
In most Linux systems, including Fedora/RedHat, the boot programs are all in the /etc/init.d directory. The init man page has information about this. Unfortunately, there are usually quite a few programs in this directory, and some program start other programs, so I don't think that will help you to figure out which program is causing the problem.
Instead what you could do is, in the command line, run as "root" the ps ax | less command. Look at every process name in the list. If you don't know what the name does, look it up on Google, see if it that is the program that is causing the problem. You can ignore programs with names in square-brackets:Notice how kjournald (I highlighted it in blue) is in square-brackets. This is a process that has already stopped running, but is not yet deleted from the system's process table. So you don't need to lookup programs listed in square brackets, because they are not running and therefore not causing the problem.Code:bash-4.1# sudo ps au | less 724 ? S 0:15 [kjournald] 730 ? S 0:00 [kjournald] 771 ? Ss 0:00 /usr/sbin/sshd -D 781 ? Sl 0:35 rsyslogd -c5 811 ? Ss 1:39 dbus-daemon --system --fork --activation=upstart 818 ? S 0:00 /usr/sbin/modem-manager 835 ? S 0:01 avahi-daemon: running [ramins-computer.local] 836 ? Ssl 0:22 NetworkManager 849 ? S 0:00 avahi-daemon: chroot helper 855 ? Ss 0:00 rpc.statd -L 857 ? Ss 0:00 /usr/sbin/cupsd -F
All the other running programs (I highlighted them in red) could be causing your problem. However, this is just an example from my own system, so I am sure that none of the programs I listed here are causing your problem


Reply With Quote
