KDE lockup on Mandrake 10.1
 

After an auto-update my internet connection fails and only starts when I go to mandrake config and change something and then change it back. This is a ridiculous windowsesque situation that I don't intend to suffer under.

More importantly however, upon starting my internet connection, no apps, shortcuts, menu items will launch with only a pathetic "KLauncher could not be reached via DCOP" for explanation. I literally can't do anything that wasn't running beforehand (I'm typing in an Opera7.23 window I had already opened).

What the hell is going on!!

Ok, I've had the same "klauncher could not be reached" problem repeatedly in Mandrake 9.2 with KDE 3.1. It seems to have gone away now, as it hasn't happened to me in at least a month. It was really annoying, but I remember being able to log out and log back in, and get it working this way. I think I could still access log out from the K menu, but I'm not sure. In any case, loging back in works for it.

Don't know anything about the network config, sorry.

It doesn't sound like it from your post but it's worth asking, did the problem just disappear or did you have any input in it? It just doesn't feel like a true linux phenomenon to just have to reboot periodically to fix a problem.

I'm more concerned with the fact that there's no mention of a Mandrake 10.1 on their homepage so maybe I wasn't exactly getting the real deal but surely that's impossible since there were no bad signatures and I used the same source as all other previous updates.

My problem did fix itself for a day (even for a clean boot-up with no restarting) but now I have to manually fill in my IP address and Netmask every time.
The Gateway stays but how is it that Mandrake just can't file the numbers away?

Relaunching X isn't something I can see myself bothering to do a lot because it doesn't even solve the problem all the time and my internet just caves again afterwards.
Now I can't be on the net as well as just having a functional desktop at the same time.

Ok, that sounds like a more serious problem. I wouldn't know what to tell you. I haven't had any problems with my network connection, I just had to log out of some sessions because of the "klauncher failed" thing. There's obviously some bug, and, I agree, it's very un-Linux-like to have to restart repeatedly. And, no, I didn't do anything about it. It didn't happen often enough to make me too mad, and it's gone away now it seems. BTW, I haven't heard of 10.1, are you sure that's what it is? The current version 10 CE is terribly buggy. It's not an actual 'stable' release. I haven't tried it, nor do I intend to until the official release, but I've heard about a whole lot of problems with it. Sorry I couldn't be of more help.

Just double-checked and now it says I'm on 10.1 Cooker during the kernel loadup which I don't remember doing at all.
I have to disagree with you about 10.0CE being buggy though. It's as buggy as the "Final" release of 9.2.
It's only called CE and not Official so they don't get completely unforseen things like the infamous LG CD Writer incident but as far as the OS is concerned, it's all there.

I can relaunch X very quickly and easily now though with the added bonus of having my connection back up AND kde not dying on me though so not all is bad in MandrakeLinuxland.

Maybe you know if /etc/sysconfig/network or /etc/sysconfig/networking/ifcfg-lo are the files that store my IP address and so on because both of network only seems to list my Gateway while ifcfg-lo has the wrong IP address and Netmask. I tried to correct the info in ifcfg-lo but then KDE wouldn't even load.
I'll try again because it's unlikely that was a related problem but I'd like to know if you can tell me I'm even on the right track.

Thanks for your help so far anyway.

I had the same problem, my 10 went to 10.1, when d/l updates for bugs on mandrake 10.
For some reason, someone said the d/l mirors where changing(whatever that means!)
The 10.1 is suppose to be a cooker, why is it in with the updates for 10!

I'm right there with you on the pure weirdnes of it but when all is said and done, I'm pretty sure it's still my fault for not checking what I was really doing.

What I really need to know is how to MANUALLY set my IP address, gateway etc and, once again, MANUALLY set it to dhcpcd.