Howdy!
Let's see, I am using Mint 8 Helena x64 on my system. When I rebooted, I came to the log in menu, and signed in. The two little dots twirl around for a minute then the terminal open up in the top left corner of the screen and that is it.
I can type in commands, and can get docky to open, or conky. Probably can get more opened but don't know the commands to use to open them. When conky opens it open in the position it is programmed to do from it's config file. In the terminal window that I start it from, it goes through it's programming and has errors that shouldn't be errors like, borders = and it gives an error stating that there is no such thing.
When I try to open anything else with conky open it will not work. I have to ctrl-c to get out of conky then I can open something else. So I opened docky. It opened where it was supposed to with the correct icons, etc. I could open any of the programs I had icons showing on the docky bars. I opened up firefox and was able to get online, but it had no title bar. I then clicked the terminal and opened up an instance of it. It opened on the top left directly on top of firefox. It had no title bar either. I was unable to type in this terminal as the keyboard would not work in it. I finally closed it and then closed firefox, the original terminal was still there without a prompt. I had to close docky down to use it again.
**********************************************************************Edit****************************************************************************
I have noticed when I click on my userid that on the bottom of the screen is a taskbar with three options showing. One is, I believe language, the second is keyboard(?) and the third is what you want to log into. I only have two choices. Window Maker and xterm. GNOME and Failsafe GNOME are not present. I was able to log into Window Maker and check several things out, but I have no idea where to re-add those two options back onto my login screen.
I was also able to get into the Updater while in Window Maker. Today, I had several updates that were installed. Maybe something in there messed it up? But how would I know what to remove and go back to an older version of? And how would I go back? I was under the impression that you were able to do so using the Update manager but that is not the case. At least not in Window Maker.
Also, just so you know, this has now turned into a learning experience for me. I installed Mint 8 x64 again on another partition. The one I had set aside for some other Linux distro, but now which has become my main login. I want to fix the old install though so I know what I did and how to fix it next time. So please, any help or suggestions or ideas would be appreciated.
********************************************************************End Edit************************************************************************
I can tell you it has nothing to do with hardware as I am able to get into both of my Windows installs. Not that I have been in the much since I installed Mint!
Any ideas would be appreciated as I am using the liveCD right now. BTW, I am still a newbie when it comes to Linux although I have learned quite a bit over the past...forget how long I have had it installed! I think it's been three weeks or so. Heck I just installed it on my laptop in a dual boot with XP because I am so impressed with it! Now I just have to figure out what I did to mess it up!
Steve
Unable to log into GUI
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Unable to log into GUI
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Unable to log into GUI
Yes I did. Twice. Each time I got an error message that is so garbled that it is unintelligible. Also, this is with either kernel. I have both kernels loaded and I can get neither of them to load Gnome, but I can get into xterm or Window Maker with either of them.fwc wrote:Did you try the restore option in the grub menu on boot?
Steve
Re: Unable to log into GUI
Ouch, that sounds bad. If you can post an "fdisk -l" after going into the boot CD it might help but if both kernels are corrupted you may have to reinstall altogether.Txnca wrote:Yes I did. Twice. Each time I got an error message that is so garbled that it is unintelligible. Also, this is with either kernel. I have both kernels loaded and I can get neither of them to load Gnome, but I can get into xterm or Window Maker with either of them.fwc wrote:Did you try the restore option in the grub menu on boot?
Steve
Re: Unable to log into GUI
fwc wrote:Ouch, that sounds bad. If you can post an "fdisk -l" after going into the boot CD it might help but if both kernels are corrupted you may have to reinstall altogether.
Code: Select all
sdb1 sdb # fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x40615164
Device Boot Start End Blocks Id System
/dev/sda1 1 6375 51207156 7 HPFS/NTFS
/dev/sda2 * 6376 12751 51210240 7 HPFS/NTFS
/dev/sda3 12751 12752 12008 83 Linux
/dev/sda4 12753 38913 210138232+ 5 Extended
/dev/sda5 12753 12815 506016 82 Linux swap / Solaris
/dev/sda6 12816 14103 10345828+ 83 Linux
/dev/sda7 14104 15391 10345828+ 83 Linux
/dev/sda8 15392 16679 10345828+ 83 Linux
/dev/sda9 16680 17967 10345828+ 83 Linux
/dev/sda10 17968 23066 40957686 83 Linux
/dev/sda11 23067 38913 127290996 7 HPFS/NTFS
Re: Unable to log into GUI
That would probably be the best idea.Txnca wrote:If the kernels are corrupted couldn't I just over write them with a new copy and fix the issue?
Re: Unable to log into GUI
OK, then I will give that a try. Now exactly where are they? Still very much a newbie when it comes to where everything is. I've been digging into the file system but haven't really been looking for the kernels. So any help would be appreciated!fwc wrote:That would probably be the best idea.Txnca wrote:If the kernels are corrupted couldn't I just over write them with a new copy and fix the issue?
Steve