SUSE / openSUSEThis Forum is for the discussion of Suse 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.
Yesterday I spent a good four hours installing SUSE v9.3, updating packages, and customizing its desktop (the second time I have devoted a half-day to this). Using the system for the rest of the session was truly a joy, just as the first time.
This morning, just as the morning after the first installation, the system is inoperable. When the boot process stops, after I have given my user password, the desktop looks normal, except that the panel at the bottom is absent and the mouse cursor is immovable at center screen.
The boot log, as I watch it scrolling by during the boot, gives no clue to the failure; everything is "done", and there are no warnings. There have been no improper shutdowns. I am at a total loss to understand why this has happened TWICE, and how to repair it. Or, at a minimum, to understand what I must do differently on a third installation in order to have assurance that this will not happen yet again. I do not have many more half-days left in me to devote to repeated failures of this sort.
The installation was made in a single 40GB Reisner partition on an IDE HD, and a 1GB SWAP partition which resides on another HD. If more details are needed for analysis of the problem, please tell me what to add.
I would be exceedingly grateful for any constructive comments and advice. If the installation DVD has a way to repair or diagnose the problem, I would be grateful for pointers on to how to use it.
If the desktop comes up, but fails to load completely, there may be something wrong with the kde configuration. What you could do is to delete/rename the configuration in your homedirectory (/home/user/.kde). This will cause a default configuration to be created on next restart. Hopefully this will be functional.
Originally posted by abisko00 If the desktop comes up, but fails to load completely, there may be something wrong with the kde configuration. What you could do is to delete/rename the configuration in your homedirectory (/home/user/.kde). This will cause a default configuration to be created on next restart. Hopefully this will be functional.
Thanks much for your reply.
Before I installed v9.3, I had installed v9.1 (because it came with the book I bought). The problem did not appear with that release. I have done nothing differently with v9.3; the fact that the problem has appeared twice leads me to the conclusion that the new release has an intolerance (read: bug) that the earlier one didn't have. OK, that happens in the world of software.
More to the point: as an utter newbie with only anagregate operating time of one hour ( =;-/8 ) I don't know how to catch the system before it hangs and cause it tobring up a comman line instead of the desktop. If you will give me that clue, I will immediately try your suggestion.
To get into commandline you can type a '3' on the initial grub menu. This will bring you into runlevel 3, which is the non-graphical mode in SUSE Linux. From here you can login to your user account and rename the .kde directory:
Code:
mv .kde .kde-backup
Then, you can start your KDE environment by typing 'startx'. This will create a new configuration and hopefully brings you to a working desktop. If it still fails, you may see some error messages appearing that can help us to find the mistake. If it works, you can logoff from kde, delete the backup 'rm .kde-backup' and on the next reboot you will be taken to the graphical login again. From commandline you can reboot with 'shutdown -r now'.
Originally posted by abisko00 To get into commandline you can type a '3' on the initial grub menu. This will bring you into runlevel 3, which is the non-graphical mode in SUSE Linux. From here you can login to your user account and rename the .kde directory:
Code:
mv .kde .kde-backup
Then, you can start your KDE environment by typing 'startx'. This will create a new configuration and hopefully brings you to a working desktop. If it still fails, you may see some error messages appearing that can help us to find the mistake. If it works, you can logoff from kde, delete the backup 'rm .kde-backup' and on the next reboot you will be taken to the graphical login again. From commandline you can reboot with 'shutdown -r now'.
That is very clear and thorough; many thanks. I'll try doing this later today.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.