Latest current ?
 

I upgraded to current packages except Kde branch and Qt library.

I don't see any quirks as of today while using my laptop.

Has anybody here any deeper experiences with yesterday's Kde/Qt packages ?

Are you disappointed that nothing broke immediately? Or just surprised?

:-) One of the reasons you'll have to love Slack... Hey Pat, I upgraded and nothing broke! Fix it! :-D

To get back on the topic: I haven't tried to upgrade yet. Recently I have been working hard struggling to get various devices working under Slack (one of them was my midi keyboard) Now that I have everything running I'm a bit reluctant to jeopardize the now-perfect setup.

When a large upgrade like this one (kernel + kde + glibc and more) appears in -current, I normally wait a few days and check the forums and newsgroups...
But up to now I haven't read anything negative.
I guess I know what I'll be doing this weekend :)

Almost always I've been upgrading immediately to current packages. There were some issues some long time ago with hal/dbus as I remember, but nothing serious indeed.
As Pat served us with huge jump into KDE 4.2.1 as mainstream version I thought I'd be more than cautious with this fresh KDE.

And how I am today ? Not disappointed nor surprised but curious . . . and waiting. With thumbs up of course.

how did you update?
 

what did you do to get to current? i have 12.2 installed now.. love it..
thanks for any info

See here:

ftp://slackware.mirrors.tds.net/pub/...kware-current/

I think I got a glitch.

After upgrading to current (not KDE as of yet) I lost the possibility to print through the parallel port.
Testing printer in KDE-3.5.10 gives nothing. KJobViewer reports "error" state.

Dmesg gave me this:

ppdev0: registered pardevice
ppdev0: unregistered pardevice
ppdev0: registered pardevice
ppdev0: negotiated back to compatibility mode because user-space forgot

Is it a newer kernel 2.6.28.7 to blame or what ?

I will not even venture a guess as to your problem but I did find out on a kde list that the kde 3 printer aps/functionality have not been ported to kde 4 and that printing functionality is tied in with QT-4 (somehow) but it wasn't explained in detail other than to say that my printing problems would probably go away as kde 4/qt 4 evolve.

I had a few problems using the upgrade to kde-4 and qt 4 on 12.2 with the packages from /current/testing, no one on the kde list could explain why but I was told to upgrade qt which I did with the 4.4.3 slackbuild from slackbuild.org which helped some.

I think it is going to be a matter of make the jump completely or stay with kde-3.5.X. You can't live in both places.

and BTW, a word of advice, if you move to kde-4 move your ~/.kde to backup and let kde-4 create a new one. Kde 3 application configs are not 100% compatable with kde 4 and some things may not work right. I found this to be the case in konsole, kate, and konqueror.

Things like bookmarks can always be copied back over later.

Hmm ... In Rio de Janeiro where I suppose you are I would rather go to beach or later to Lapa . . .
Or maybe it is only a faint idea of me being far far away from there.

I made an ISO image of the latest -current tree and used it to make a full install in a VM in VirtualBox in my Slackware 12.2 system. I installed it in a single ext4 partition (no partition for /home in order to optimize available space usage in the virtual disk, but a small swap partition).

All went well during install, but at first -- and only, for now -- try I couldn't properly launch KDE.

I do not draw any conclusion of that, which can come from my VM's setting or any other thing.

Pretty busy now, but I will try again next week-end and see what happens.

EDIT In fact I couldn't wait and tried again.

KDE 4.2.1 launched OK at second try. ;)

I mailed Pat and asked him a question according my printing problem.

The key was the output of the "lpstat -t" which yielded "The PPD version (135261371) is not compatible with Gutenprint 5.2.3"

He suggested to remove the content of /usr/share/cups/model/gutenprint
and remove existing printer using http://localhost:631 and create it again.

It worked :-)

Hahahaha.... after the Carnival I need to slow down a bit... :D

Hello!

I upgraded my slack to current and i can't install the Nvidia drivers. The message is something like: "gcc and libc (...) the compiler 'cc' does not appear to be able to create executables (...)"

I upgraded glibc-solibs first and pkgtools then i upgraded the rest...

What i did wrong? How can i fix this?
I think is the 1st time that i installed (too soon) from current

Thx a lot
EddY

The new gcc depends on l/mpfr-2.3.1-i486-1.tgz. Install that package and the nvidia driver will build fine (I had the same problem).