Hello,

I am wondering if anyone can make any sense of the following
as I would like to stay with OpenSuse KDE which I find most
usable for my purposes.

System info: Intel Q9650 with 8GB ram running OpenSuse 11.1 64 KDE.
It is used for running flow simulation codes.

Problem: Cannot log in back again after installing g++ and libstdc++.so.5.

Problem History: Installed OpenSuse 64 KDE without a hitch about
15 days ago. I wanted to install the Intel compiler (ifort) so I had
to install the prerequisites g++ and libstdc++.so.5 which were done
with no problem.

Installed the intel compiler and the Nvidia graphics driver OK. Run
four codes simultaneously 24/24 for 14 days with no problem. Today
I logged out for the first time. Then I could no longer log in back
again with KDE - something about the "ksmserver" was flashing in the
login screen. Web search was not useful on fixing the problem.

I used the console login to save the data and then reinstalled
OpenSuse. Installed g++ and libstdc++.so.5 only and logged out again.
I could not login again. Repeated the process with no success.

Any ideas what may be going on? Any pointers?

Thanks,
--

Do you get the kdm login menu, but it returns there? It sounds like a partition has run out of disk space. I had the same thing happen lately due to a runaway process causing a log to fill up the /var/log/ partition. Zeroing out the log file fixed the problem.

There could also be a problem with KDE. In an earlier version of SuSE & KDE, the ~/.xsession-errors log file grew to a ridiculous size a couple times. I would go to a virtual terminal and try to log in that way and check the free space on your partitions. I think it may have been due to something I did such as logging in remotely, running another instance of KDE while locally another was running using the same username. ( In other words, playing around )

Another possibility is that the Xorg server isn't starting up. Look for lines starting with (EE) in your /var/log/Xorg.0.log file to pinpoint if that is the problem. Running sax2 or nvidia-xconfig might fix a configuration problem.

Running "sudo /sbin/ldconfig" and "sudo /sbin/depmod -a" can sometimes help with library dependency problems in the case where the installer didn't finish up. Also try "sudo /sbin/SuSEconfig". Sometimes there are more than one config file that SuSE uses. The generic one and a more general one that YaST2 uses. Running SuSEconfig is the last step that is done after using YaST. Perhaps this was interrupted.

FYI. I just looked at which library files I had. The libstdc++.so.5 library is supplied by the compat rpm:
i | compat-libstdc++ | The Old stdc++ Library | package

Did you do anything funky to install it. The standard c library is something you should install from the rpm package. Installing it from source is very complicated and why introduce unnecessary errors if you can avoid it.

I doubt that any KDE programs or QT libraries in your current version would use the old C++ standard library however.
Installing g++ and compat-libstdc++ from the SuSE package wouldn't cause the problem you are seeing. I have both on my laptop.

Thanks jschiwal.

I will look into what you say.