[SOLVED] Internal error could not resolve keysym *edited*
Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I installed Fedora 14 on my girlfriends eee. She went to install updates today while I was at school. It told her to log off and log back on after updates. She said that it got hung up and froze on her. She turned it off and back on. After this the system just hangs on the boot splash screen. I looked at my Red Hat books I picked up a few years back, and googled around and could not find anything that matches up to this problem per se but severel close ones that are not fixing the problem or sending us in the right direction. After a bit I found a way to get her logged on in runlevel 3. When I told her to startx it gave the following messeges.
Internal error could not resolve keysym
xf86 touchpad on
xf86 touchpad off
I normally would reload and tell her to have at it again, but I will not see her again untill Saturday after class. If someone could send us in the right direction it would be appreciated. She has experience with Ubuntu and is not afraid of the command line. So I can coach her through on the phone if anyone needs more information or has an idea on a fix.
Thanks in advance for any help.
**Edited this from tsymkeysym to keysym, sorry it was late at night and I misunderstood what she said over the phone, will try googling some more, will post answer if I find one I will post it for others**
OK dug around a little bit, and on Debians forum someone posted some very similar to this. They narrowed it down to a program they uninstalled recently. So I had her reinstall the last 3 programs. Then I read that someone had problems with gdm. I told her to reinstall and gdm. It said the package was not installed. So after installing gdm she gets to the log on screen and it just asks her to log in over and over. Getting closer.