-current, multilib, and KDE-4.3.4
 

I am running -current with multilib enabled. I know that I can't upgrade gcc or glibc, but I was wondering if upgrading KDE would break anything. TB-3x was a wash for me since I couldn't get it to open links in FF. I went back to TB-2x. But my real interest is in KDE, since its my DE of choice.

Running -current, multilib with KDE4.3.4 here. Yet to discover any problems. One thing I had to manually fix was that perl upgrade to 5.10.1 broke something. But everything works great now. KDE 4.3.4 is fast and stable and feels lighter than it's predecessors.

Regards

Agreed!

samac

Do you read this?

http://www.linuxquestions.org/questi...bird-3-775851/

Yes - I had read that. I may revisit your last post later. Right now, I have KDE running in init 3, but my default is init 4 with auto login. I just get a command prompt only here. I go back to init 3 and startx, and all is well. I may have to delete the old .kde and reconfigure. I tried to merge the common lines, but I don't think that will be sufficient.

Then I will tackle TB again. Now its time for a nap because I have a 12 hour shift coming up.

So, what exactly was that "something"?

Eric

Hi,
It broke frozen-bubble which I had built from slackbuilds. When I tried launching it, it was looking for files [e.g.->locale-gettext] in perl5/5.10.1 which didn't exist, but they were present in 5.10.0, so I just copied them over to 5.10.1. I tried uninstall /re-install of frozen-bubble still it didn't work, then I did the copy operation. It seems like a dirty method but it worked.

Well, I deleted .kde and .kderc, and I still get only a small box in the upper left corner for a shell. I am presently just using startx in init 3. Must be something else in the way.

Try running xwmconfig this has worked for me in the past when I have broken my upgrade and only got a TWM desktop. KDE 4.3.4 works very well with multi-lib current.

samac

I gave xwmconfig a whirl and that didn't work either. KDE runs fine in init 3. Its init 4 where the problem lies.............hmmmmmmmm - off to try something else in a bit.

Ok - I stopped all the auto-login stuff and switched to init 4. Once there, I put in my username and password and selected the session type. I got the shell in the upper left corner again. So then I logout, start over and select XFCE 4. I got the same result. Can't run XFCE 4 in init 4 either. Something is broken in init 4. Not sure what, but I am going Christmas shopping with the wife for now. This one can wait.

I ain't having much luck trying to figure out why KDE (or any DE) will not start in init 4. I've been searching for permission problems in my home folder, but have had no luck there either. I'm still looking. :)

I finally got this figured out. The problem was in /etc/kde/kdm/kdmrc
What I did was to update another partition that Slackware64 was on to -current. I had no problems after the update getting KDE to work in init 4 with autologin and no password. After the upgrade was finished, I deleted the .kde folder, and simply selected O for all new config files. Basically, I was starting fresh.

Entering init 4 for the first time, I noticed that kdm was very different from what I was seeing on my main install. So I then ventured off to /etc/kde/kdm for a look around. It was there that I found the difference in the two files from each partition. All I did was to edit kdmrc to match the new one on my freshly updated old install. Now I am back in business.

Maybe tomorrow, I will tackle TB 3x and see if I can finally resolve the links opening in FF problem.

Merry Christmas to all!