Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I'm having a problem with KDE. This problem has been consistent in KDE 3.2 and 3.3, as well as Mandrake 10.1 official and Mandriva 2005 LE.
The problem occurs after running the command init 3.
I started out by installing the new (7174) Nvidia display drivers. Those installed without a hitch. I've got the source code installed, changed X86Config to reflect the drivers of nvidia instead of nv etc, and the install says everything is fine. Before installing the new drivers I booted into Mandrake, went to a command prompt, went into su and typed in init 3 to kill X.
I installed the drivers, and all seemed well. It's when I try to get back into KDE that I have problems. After installing the drivers, I type in init 5 to get back into KDE. That fails. I then type in KDE and it boots up.
Yet the problem occurs that I loose the ability to shutdown and restart through the GUI. The only option I'm given is to log out. And then X is killed and I'm left at the command prompt. I can only go su and then shutdown manually.
When I reboot the machine, I'm also left at the command line in order to get back into KDE. While this is fine for me, other users in my house tend to freak out over the command prompt. Any ideas on keeping my GUI intact?
I've seen a similar thing in Mandriva LE...../etc/initab has init 5 as default which is normal for Mandrake (would be init 4 in slack)
But thing still boots a console prompt. Weird. logging in and forcing init 5 gets the GUI logon. Doesn't bother me but I'm trying to get windoze fools to convert and a console throws them.
only blew out after nvidia module though which of course meant adding sources to mandriva
startx starts x normally....maybe i'll add that to rc.d :-)
OK, When you are in RunLevel 3, run either of the following:
kdm
gdm
to get the GUI back, the KDE Display Manager and/or Gnome Display Manager will start Xwindows and when you try to logout you can see 'Shutdown' options;.
I can run either of those and get back into the GUI, but when I logout again, I'm only given the choice to logout. And when the computer is booted again, it still stops at the command prompt.
If I'm going to make the Windows folks happy, I need to be able to go straight into X and not mess with any command prompts. I've been experimenting with SuSE 9.2 and so far really like the results. I don't want to switch away from Mandriva, but not booting into the GUI after installing nVidia drivers is not going to cut it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.