• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

SuSE 10.0 updates kill KDE for me

MadRat

MadRat

Lifer
I spent a couple of hours learning how to save my whole setup and restore KDE to its original incantation only to see the AutoUpdate feature for YaST kill it once again. I thought it was an X11 problem but it turns out that it is limited to just KDE and all of the other wm's work fine. I suspect they are importing a 3.5 component that is not somehow compatible with 3.4, but haven't perused the logs to find out.

Anyone else using SuSE seeing the same result with KDE?
 
I haven't had this problem happen to me so far. I haven't logged in Suse for the past day or so though. I'll login in a bit, update, and report back.

Edit: Everything's fine here. It said I hadn't updated in two days, but when I updated it didn't have any updates for KDE or KDE components. Just a wget, net-smnp, and something else.
 
No. I just updated yesterday and everything has been fine for me. I also tried KDE shortly thereafter with no issue.

Yeah, I didn't get any KDE updates either. snmp and other stuff.
 
Well shucks, looks like I need to go through and re-install the base 10.0 KDE stuff again. Are you guys using 10.0 or 10.1?
 
I login and it goes right back to the login. When I change the WM it works with non-KDE WM's. I think its aRTS causing the problem.
 
MadRat if you are being sent right back to the login, what has happened is ~/.bashrc (might be ~/.bash_profile) is screwed for your userid. What you need is this file from the original install. SuSE has a pretty hefty file with a lot of stuff in it and if you don't have it or yours is from a previous install of SuSE then this is most likely your problem.
 
Originally posted by: TonyRic
MadRat if you are being sent right back to the login, what has happened is ~/.bashrc (might be ~/.bash_profile) is screwed for your userid. What you need is this file from the original install. SuSE has a pretty hefty file with a lot of stuff in it and if you don't have it or yours is from a previous install of SuSE then this is most likely your problem.
Click to expand...

Nah, .bashrc is for bash(didn't see it coming, did you? 😉 ), KDE doesn't need that.
Madrat, I haven't used KDM(KDE's welcome/login thingy, Desktop Manager, whatever it's called) for a while, but I'm fairly certain there's an option to start a session called "Console" or some such, basically just a regular init 3 login.
If there isn't, you can always just use ctrl-alt-f1 to get to vc1, login as root, then shutdown KDM using /etc/init.d/kdm shutdown

After you've done that, create a file called ~/.xinitrc and put the command "startkde" in it, nothing more.
Now just start X using "startx", and see what happens.
If it's indeed KDE screwing with you, you should see some kind of error message.
 
Have exactly the same problem. Using the usefull tip by Sunner, startkde shows lib problem. kdecore (KLibLoader): WARNING: KLibrary /opt/kde3/lib/kde3/kcm_kdnssd.so undefined symbol

and after that
could not open lib kmserver.la: libpowersave_dbus.so7
so startkde shuts down
Guess the latter is the problem.
Starting with noapm noacpi does not solve it, tried that already.



Acer Aspire LC1635 / P4 /
 
Yep, a Warning isn't too bad, getting undefined symbol errors isn't uncommon really.

Did you check if that lib file is where it should be?
 
With Debian sid it's not unusual for me for large updates to gnome to break things temporarially.

Usually it's something like a gnome deamon running since before the update that is incompatable with the updated stuff... or junk left over in the /tmp directory.

You can check to make sure that when you logged out of kde that it shut off everything, all the deamons and artsd and such. Then delect any stuff in /tmp directory. Then log in again.

or you can try to simply reboot to be very sure.
 
There's a libpowersave_dbus.so.10.0.0 , so made symbolic link faking so.7, and kde runs. Now it's wait and see if it crashes at some point. Is there an easy way to rpm update kdebase3? i nthe 10.0 dir of ftp.kde.org there's at least 30 rpm's involved.
 
Sounds like there's a version mismatch, guess all of the KDE packages didn't get updated for whatever reason.
Never used SuSE for more than just having a look at it, so I'm not very familiar with their method of updating.

Anyway, you can check what RPM the file belongs to by issuing "rpm -qf <filename>", that should give you the RPM along with it's version, then check that against the version of kdebase(check that using "rpm -q kdebase").
Or if you just wanna make sure you got all the updates that are available there, download all of the KDE rpms, and do "rpm -Fhv *.rpm" whereever you put them, the -F switch will update any RPM that has a newer version available.

Again, I'm guessing SuSE has some smart way of doing this, so if you can, I'd use that instead, the way I described is the ugly workaround 😉
 
I _think_ that with suse you go about updating and linking to online repositories with Yast. Not sure though.
 
Originally posted by: Sunner
Originally posted by: TonyRic
MadRat if you are being sent right back to the login, what has happened is ~/.bashrc (might be ~/.bash_profile) is screwed for your userid. What you need is this file from the original install. SuSE has a pretty hefty file with a lot of stuff in it and if you don't have it or yours is from a previous install of SuSE then this is most likely your problem.
Click to expand...

Nah, .bashrc is for bash(didn't see it coming, did you? 😉 ), KDE doesn't need that.
Madrat, I haven't used KDM(KDE's welcome/login thingy, Desktop Manager, whatever it's called) for a while, but I'm fairly certain there's an option to start a session called "Console" or some such, basically just a regular init 3 login.
If there isn't, you can always just use ctrl-alt-f1 to get to vc1, login as root, then shutdown KDM using /etc/init.d/kdm shutdown

After you've done that, create a file called ~/.xinitrc and put the command "startkde" in it, nothing more.
Now just start X using "startx", and see what happens.
If it's indeed KDE screwing with you, you should see some kind of error message.
Click to expand...



Sunner, you are correct and I should have checked my sh!t before posting. lol It is .xinitrc that is heavily modified. and unless you are in runlevel 3 you need this modified file in place for X to start properly.
 
I have a feeling the SuSE updates are fixed. They had an update for kdebase3 in there that appeared to be the problem. I just re-installed it again and let their new files overwrite the old to fix it. Kind of a pita since this machine doesn't have a cdrom normally attached. Have to crack the case open each and every time to run cd's and dvd's. 😛
 
btw - SuSE supports just about every software installation format available to linux; yum, YaST, Red Carpet, apt-get, etc...
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top