MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This may be in the wrong forum, if so, please move.
I really don't know what I did but somehow while trying different desktops I
managed to mess things up so I can no longer just start the system with a
GUI, I can only run the sys. with CLI. In the process of all this I also lost the
ability to auto mount the cd along with the ability to shut down the sys.
This whole process started when I wanted to change the fonts in GTK1 and
GTK2 apps.
In reading these forums there were suggestions to use Gnome and change the
fonts in there and that would do the trick. Well, it changed alright, the fonts
went from very small to very large and I couldn't get them any smaller. I then
deleted Gnome and from that point, things have gone downhill.
As my wife uses this machine also I need to get things back to the GUI with
auto log in.
Surely someone out there will have compassion on me and not let me go
hungry until I get this straightned out.
How, exactly did you delete it? Did you remove it using urpme (or rpm -e)? Is so, you can re-install it if you use this command:
Code:
urpmi gnome
But you need to be root in order to do that. If you just deleted a random folder, do you recall which one?
Jeremy
Jeremy, thanks for the reply.
To the best I remember I unstalled Gnome thru the MDK software uninstall. I was getting a little confused at this point. All I wanted to do was get the fonts to look right.
I don't recall all of the depen. which was included in the Gnome package when I uninstalled it. I sure hope I don't but I might have to reinstall MDK to get things working right again.
Originally posted by jerm1701 You can use the method above to re-install gnome since you uninstalled it using MCC. It should take care of the dependencies for you.
Good luck!
Jeremy
Jeremy,
Tried urpmi gnome with the following:
Some package requested cannot be installed:
xine-gnomevfs-1-0.rc5.9.1.101mdk.i586 (due to unsatisfied libgnomevfs-2.so.0) (Y/n)
Makes no difference if I select either Y or N it still want load.
Well, first, make sure you have all the other media turned off besides your original installation CDs/DVD. That way, you should be able to install just like you did the first time.
Second, if you run into trouble with dependencies like that again, force the installation of the individual rpm using.
Code:
rpm -i --force rpmname.rpm
I think turning off your updates, contrib and other media will be the best bet, though. That way you won't have to worry about updates conflicting with the orginal packages.
Jeremy
If you reinstall MandrakeLinux using "upgrade" you will not lose your home (personal) files. It might be the easiest course at this point.
When prompted "Is this an upgrade or install?" (or words to that effect) be sure to reply by checking the "upgrade" box and your home directory will not be affected; at worst you might have to reinstall some programs you were using before.
I have done this numerous times because of mistakes I've made that resulted in it being the easiest way to get back to working. It may not be elegant or a good way to learn things, but it works.
Originally posted by Dooley Thanks to both Jeremy and jonr.
I will see if I can get this worked out.
If I don't post again you will know everything is ok.
Originally posted by jonr Good luck! But please post and tell how it went.
I tried both suggestions, force install of depends. and the upgrade and no go, still have the CLI log in.
Everything was fine until I uninstalled Gnome. I must have missed something or removed something that has to do with KDE and the GUI log in. Each to his own poision, but I just don't like Gnome and it runs slower on my machine than KDE.
I will keep plugging at it and see what comes up. Any further help would be appreciated.
Originally posted by Dooley I tried both suggestions, force install of depends. and the upgrade and no go, still have the CLI log in.
Everything was fine until I uninstalled Gnome. I must have missed something or removed something that has to do with KDE and the GUI log in. Each to his own poision, but I just don't like Gnome and it runs slower on my machine than KDE.
I will keep plugging at it and see what comes up. Any further help would be appreciated.
Dooley
MDK 10 OE
Well, I can tell you how to get your GUI login, but you need to back up the file in question
(just copy it with another name) in case you slip up.
Assuming you can access an editor of some kind, as root copy the file /etc/inittab to something like
inittab.safe or some other name you will remember, for safety.
Then edit /etc/inittab so that the default runlevel is 5 instead of three. You will see near the top
of the file a list of 6 runlevels and a statement about each of them. Runlevel 5 is X11, or what will
give you your GUI login. Runlevel 3, which it's undoubtedly set at now, is the command line
login.
Change the "3" to a "5" in the line that reads "id:3:initdefault:" and reboot and you should be
at a GUI login.
Originally posted by jonr Well, I can tell you how to get your GUI login, but you need to back up the file in question
(just copy it with another name) in case you slip up.
Assuming you can access an editor of some kind, as root copy the file /etc/inittab to something like
inittab.safe or some other name you will remember, for safety.
Then edit /etc/inittab so that the default runlevel is 5 instead of three. You will see near the top
of the file a list of 6 runlevels and a statement about each of them. Runlevel 5 is X11, or what will
give you your GUI login. Runlevel 3, which it's undoubtedly set at now, is the command line
login.
Change the "3" to a "5" in the line that reads "id:3:initdefault:" and reboot and you should be
at a GUI login.
Once again, you have to do that editing as root.
I might be missing something here again so I will list the settings in etc/initab:
I copied and pasted as is.
# Default runlevel. The runlevels used by Mandrakelinux are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
#
id:5:initdefault:
This is all greek to me but I would say it is set at 5.
I want be able to do anything else until tomorrow.
# Default runlevel. The runlevels used by Mandrakelinux are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
#
id:5:initdefault:
[/B]
Well, I was hoping it would read "3." Back to the proverbial drawing board, then.
For some reason your X Window system must not be working. I don't understand why,
after a new installation--which should have supplied all the working parts again.
I and I hope some others more knowledgable here will give this more thought and if
I get any clue that might help you I'll post it. Don't give up. Something simple but not
obvious may have happened.
Rest assured it CAN be fixed.
If you have to, you can do a new fresh install (choosing "install" instead of "upgrade" and still not lose any of your home files, as long as you're very careful to only let the installation process format /hda1. Your home files are on partition /hda6. If you are careful and don't format /hda6, they will remain intact and untouched by this fresh installation.
If you make a mistake and have "all disk space" formatted or for some reason format /hda6, you will lose EVERYTHING. So just be very careful and think twice before you check any boxes.
If that doesn't solve the problem, I have no idea (at this point) what would. You won't have to worry about any dependencies or updates or anything--it will be just like the first time you (successfully) installed, only the home files you've created since your first installation will be there too.
I have done this and though I don't like doing it (and would like it even less if I didn't have my home files backed up in a separate location) it is sometimes, like the "upgrade" trick, the fastest way to get back to "normal."
I would like to thank all who so kindly tried to help with my problem.
The mystery has been solved.
While trying to get the fonts to look better I add -dpi100 to the
etc/x11/xdm/xserver file. I have no idea why that crashed the GUI log in, but it did.
As I have A.G.E. I had forgotten about adding that to the xserver file.
As soon as I removed the -dpi100 everything started working correctly again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.