sure.. why not?
But i think it's better to let the Xorg project knows about this, since Pat didn't work on Xorg

I did comment on the bug on xorg's site that I confirmed it on my system, just wondered is pat knew if he would want to roll back to an earlier for the next slack or not release until its fixed.

hm.. you could always revert to the stable packages. That's why Pat always gives 2 differents version (Stable and Current)

yea, the issue there was kde in the stable packages was older.

To all interested:
1) Check out software.jaos.org and install slapt-get.
2) Edit /etc/slapt-get/slapt-getrc and comment out (using #) the ftp. slackware stuff and use these:

SOURCE=ftp://ftp.biochem.uthscsa.edu/pub/linux/slackware/slackware current
SOURCE=ftp://ftp.biochem.uthscsa.edu/pub/linux/slackware/slackware-current/extra
SOURCE=ftp://ftp.biochem.uthscsa.edu/pub/linux/slackware/slackware-current/testing

It will keep you up to date with the latest kernel (currently 2.6.15.6) and the related packages, X, arts, and such.

Be sure to read the documentation, but here is a quick start....

1)as root in console type: slapt-get --update
2)when that is done type: slapt-get --upgrade

Also, you can install (from the same web site) gslapt, a graphical front end to slapt-get.

Enjoy

Thanks rodimus,

Can anyone else comment on this being a good/bad for a method of updating my Slack 10.2 installation?

I have my distro EXACTLY the way I want it, and I don't want to mess it up, yet I do want to update it...

Any thoughts much appreciated.

What bug is this? I use Slackware Current with KDE 3.5.2 and don't see anything wrong at all on my i810 box.

I experienced similar problems upgrading my Slackware 10.2 Kde from 3.4 to 3.5.2. However, I was sucessful by 1. Grabbing the Slackware 10.2 packages from the KDE website 2. Killing the x server and from the CLI uninstalling all the existing KDE packages, KOffice, and arts from my system 3. Installing the new packages. The key for me was to use KDE packages that were build for Slackware 10.2 stable.

In my previous post, I provided a quick tip for using slapt-get to keep updated. I should mention, that I always run Slackware Current. There are good things and bad things about this.

Good Things:
1) Always getting the latest packages, including patches.

2) Quick updates with little management needed.
NOTE: Slapt-get only updates packages you have installed! It will not install a package you need without it already being there, or installing it manually first.

3) It lets you see what new packages are available quickly.

Gotchas!:
1) If you are running a program that is kernel dependent, i.e. 2.6.16.16 and use slapt-get to upgrade your kernel, you will have to recompile your program. A good example of this is the NVidia(R) driver.

2) If you upgrade packages such as apache and mysql, you have to be sure to back up your configurations before hand (especially mysql). On at least one occasion, mysql has died after a major update and I had to import and rebuild my databases.

3) VERY IMPORTANT: If you are updating your kernel, sometimes (I don't fully understand why yet) slapt-get will update the kernel-source, kernel-modules, kernel-headers, and Say its updating the kernel, but the kernel doesn't get installed. So be sure to have your previous kernel packages on hand for an emergency. I create a little backup folder and put the four packages in it: kernel-headers*, kernel-source*, kernel-modules*, and the kernel-(version) itself, so that if something breaks, I can just reinstall these 4, run lilo and reboot, then reinstall the new ones.

Sorry if anyone has had a problem using slapt-get since my last post because of needing this information.

Have fun!

Rodimus