thanks to alienBOB for getting a hold of that patch and getting in the push 4.3.2 packages for -current.

i know, i read your post. you'll some of the packages from current for kde to work properly. i kept that in mind when i replied.

It is my understanding from reading this thread, although I could be wrong, that the KDE 4.3.1 packages would work on slackware 13.0 and that only KDE 4.3.2 would require an upgrade to slackware-current.
Is this correct?

That's my understanding to. I'm currently running 4.3.1 on a "stock" 13.0.

Cheers.

A few of -current packages as mentioned earlier in this thread are essential for making 4.3.1 work.

So... which is it? :)

KDE 4.3.1 --> Works with Slackware Stable (Default)
KDE 4.3.2 --> Needs Current, as its compiled against them.

That's it.

Make it 4.3.2, typo. :redface:
I didn't notice you just want to use 4.3.1 packages and assumed you would want to upgrade to 4.3.2 instead, hence I suggested -current upgrade. My mistake.

Cool! Glad that's cleared up :)

So... back to my original question: since I don't install "all" of KDE 4.2.4 in my slackware 13.0 machine, should I use or?[/QUOTE]

use this command as i said earlier:

This will install packages that I don't have now in my working KDE 4.2.4
Any reason for this? Are there any packages needed by KDE 4.3.1 that were not needed in 4.2.4?

Sorry for nagging, but I'm not the "full install" type of user.
It makes no sense to me to install things I'll never use.

The scenario the posters are discussing may be safe at the moment but just to warn anyone browsing this thread - mixing Slackware -current packages with the stable release is not recommended and may cause serious problems. You have been warned ;)

Yes, there are some "new" packages, that didn't exist on 4.2.4.

It's easy enough to compare the list of what you have installed, what comes with 13.0, and what's in the new set. Then you can decide which of the "new" packages you want to install.

I ended up replacing what I had currently installed, plus ALL the "new" ones.

Cheers.

I found that the 4.3.2 is enough of an improvement that it is worth the extra effort to install the necessary packages from -current. I am not (hereto-far) committed to staying with -current but I found that upgrading a few packages from the early part of the changelog and additionally the 4.3.2 packages from the announcement made for a significantly better system. Particularly KMail and Konqueror that were periodically crashing with 4.3.1. Aside from a few annoyances, 4.3.1 did run well on -stable.

I downloaded everything from this tread http://www.linuxquestions.org/questi...urrent-763844/ and kde dies so I had to go back to the vbatts packages.

i did update from vbatts packages to -current. i did not face any problems. What problems did u face?.

thats what I did too. it would draw the disk icon of the kde startup and then exit back with a couple screefulls of error messages.

well, could you share, what those error messages were?

and did u update only the <kde> or all the packages from current?

I had that problem with 4.3.2 and it turned out that I had not successfully upgraded qt because the package did not download fully. Did you install all of the packages listed here?

Yes, I downloaded everything on that list. I must have missed something because I went back and did it with slackpkg and it worked fine. The only issue now is finding where slackpkg stores the packages so I can save them.

all you have to do is edit your /etc/slackpkg/mirrors to this. and for 64 bit now comment your old one. because you can only have one mirror. if this does not work do a slackpkg clean-system then do as before.

I just upgraded to current - except the kernel and kde packages, since I use a custom kernel. Then installed all the _vb pkgs since I already had them downloaded. Everything seems fine except for hp-toolbox. Something between sip and qt broke it. I don't really care since I never used the toolbox anyway. I was running 4.3.1, and I just had to try 4.3.2. :)

You may want to get the kde packages from current rather then the vb packages. From reading in the other thread there are a few bugfixes added into the -current ones.

please do prefer packages from the official tree, rather than the unofficial builds like i had published. ;)

take care,

Are you saying I can upgradepkg these -current packages on a 13.0 system?

Well - I have a problem with the new 4.3.2 packages.
First - I can't change the theme. The Apply button stays grayed-out.
Second - The Login Manager won't load for me to automatically login my user.

Not showstoppers because everything else seems to work fine.

The second one fixed itself. Probably just me.

this has been a request to the kde team, regarding the theme, that they will be putting into the system settings panel as a kcm module. but you can change your them by right-clicking on the desktop, and choosing "desktop settings"
it's pretty discrete, but its there.

Take care,

vb

Thanks vbatts! That did the trick in a hurry. :)

You know vbatts the current slackware kde 4.3.2 build uses a new version of PYQT. this was the major fix to the QT module. any way
I really like the 4,3.2 is feels very light and fast. I find it much more fun to use then the 4.2.2 hang in there. Keep up the great work.

4.3.3 is out from kde today, I got the e-mail

From looking at the change log file it wouldn't appear to be enough changes, and/or significant enough changes, to warrant updating to 4.3.3, unless, of course, there is a specific change that could be of benefit to an individual user.
Regardless, since switching to Xfce I've been using it about 90% of the time and don't see the need to use KDE anymore.

How do you download the packages with rsync?

gives me:

I would imagine he deleted those since they went into -current.

Why would you need 4.3.x?

Check this out: http://alien.slackbook.org/blog/kde-...ation-4-4-rc2/

It is awesome!!!. Alien Bob did excellent job. I checked 4.4-rc1 from Alien Bob as well.... There is no way anyone can bring me back to 4.2 or even 4.3.

Check also Eric's blog http://alien.slackbook.org/blog. It has a lot of interesting texts about kde 4 and many many more.

Because I don't want to upgrade to current.

He did not delete 4.3.1, and I know how to get them with lftp. I was asking for help with rsync.

Ok understood.

rsync -avr cardinal.lizella.net::vbatts/kde4-packages/4.3.2/ .
will download 4.3.2 to current directory.
Or choose another version. Available versions are:
PS thank you for your font research. I am using it and do not know, how I could work without it. My eyes would say thank you.

Thanks very much.

rsync is one of those program for which rtfm just didn't work for me.

Hi,

I tried it out, it is really good, but I have some problems with my wireless connection. Till now I used KDE4.3.4 and there was no problem with it, now I can set it only manuall. What has happend? I don't understand, the machine is the same.
And since it is a pre version, there are some crashes, but they are not so disturbing. The problem with the wireless tweaks me.

And a request to Alien: please make the kdei-s also.

What it has to do with wireless? just use wicd from extra. It is not related to KDE anyway.

kdei's are there. in a separate directory kdei.

I use x86 and not x86_64 and there is no kdei directory.
It has to do with wireless, because I use the wicd from extra, and it does not work. And as I said, till now I used current with kde4.3.4 and there was no problem with my wifi.

I posted this in my blog when I made the 32-bit packages available:

Slackware:

• Don’t forget to also install the updated or new dependencies! These “deps” packages can be found in the “x86/deps” directory.
• The KDE 4.4.rc2 packages themselves can be found in “x86/kde“
• If you need a language pack, you can grab one from the 64-bit package tree.

Eric

OK, thank you, I thought that they were x86_64 by mistake.
Thanks again.