Bluetooth also does not work here! And I thought everything was going well ... :-(

Since most people reported no problems on a fresh install of current, did a fresh install on a spare partition just to see what would happen. Everything worked straight out of the box with no problems, had none of the problems I experienced while upgrading.

Nvidia geforce 6150se nforce430

Just a note, since I had to essentially re-install to make this update error-free, (completely by my own fault, as I previously noted in post #118) I was curious.

I have an IBM Thinkpad R51 laptop that I use while out and about, and it is a very vanilla Slackware 13.1 box.

I pointed slackpkg at a -current mirror and updated, and everything worked perfectly right out of the box.

Pat, Robby, Eric, and the whole Slackware team are some pretty amazing dudes. It's strange to think that, back in 1997 when I chose Slackware out of the myriad distributions available at the time, if I'd've settled on any of the other alternatives (other than Debian, I suppose) I wouldn't have been able to run the same system straight through to the present day.

There's a good reason why Slackware has endured while the others atrophied. Long live the Benevolent Dictator for Life! Long live Volkerding!

What a suck-up... We all like Slackware, and are using it for reason, but if you choose say RedHat or SUSE, or any of *BSDs, back in 1997, what exactly would prevent you to run them up to the present day?

He mistook the year, should have said 1993, then it would have worked

I got the same problem.

the bluez-4.79 package -current update today fixed this.

cdrom/dvd symlinks working fine now with udev-164-x86_64-3. Thanks Robby

Well, just for chuckles I tried running KDE while signed on as root and it ran just fine.
So, with that in mind I deleted my user KDE configuraion and fired it up as user. It
ran for several minutes and then suddenly crashed, as it has since the x upgrades.
What the means, I don't know.

You are correct. I switched to the vesa driver and XFCE would start, but not KDE. It seems that the trashed "radeon" driver is the culprit. But the fonts and the general look is terrible. Someone else has suggested that I try recompiling the kernel or the radeon driver. I will try that. I have never recompiled a driver before, and it has been two years since I have recompiled a kernel, but I am sure I can find adequeate instructions on how to do both of those. I am also going to try to boot from the generic. I will try just about anything to keep this installation intact with having to re-install.

Thanks for your post.

Bob

Your installation media (DVD/CDs) has a good read me on how to set-up your initrd which you will need for a generic kernel.

Yes, but now I have problems with Blueman-manager ...

Please view ...

http://www.linuxquestions.org/questi...anager-845535/

Anybody else have problems with Blueman, if yes please let me know ,please

Thanks

@BobNutfield - First, a big disclaimer, I have NO experience with ATI hardware. (If you avoid the minefield then you will not step on a mine!).
However, my thoughts after some googling.
There is a report in post #8 in the link below of the ATI Radeon X1250 working with KDE 4.5.1 using the r300g driver. I do not see that this driver is built in the Mesa 7.9 in slackware-current. I think you would need to rebuild the Mesa package using the '-enable-gallium-radeon' configure option to get this. Hopefully anybody who has experience with ATI hardware could provide further advice on this.

There is an open bug report about this driver with KDE 4.5.2 and later. https://bugs.kde.org/show_bug.cgi?id=253483
Also, a related bug report. https://bugs.freedesktop.or/show_bug.cgi?id=31499
as well as a recent article. http://www.phoronix.com/scan.php?pag...0g_oct10&num=1

Haven't seen this posted yet.

I ran in to another minor problem after installing the latest -current upgrades.

I run both Slackware-current and Slackware64-current. This problem apparently only affects x86_64 as I do not see this problem on my 32-bit machines.

Problem: Animated GIF images are not displayed correctly in Firefox (Thunderbird and Seamonkey too). Some animations play OK, others only play one or two frames with the rest of the frames showing nothing. Makes for an annoying blinking display to say the least.

After some fiddling and research I have figured that the problem stems from the upgrade to cairo-1.10.0-x86_64-1. Regressing to cairo-1.8.8-x86_64-3 fixed the problem and GIF animations display properly.

Having said all of the above, this does not appear to be a problem with cairo, but with mozilla-firefox. See Bug 597174 – Firefox 3.6.10 doesn't render gifs correctly. Displays (flashes) only the first frame.

So far since regressing to cairo-1.8.8-x86_64-3 I have not encountered any side effects. I do prefer to run with the upgraded cairo but I like seeing the animations.

Edit: I tested this with the mozilla-firefox-4.0b7-x86_64-1 in testing. Problem does not exist with cairo-1.10.0-x86_64-1 installed.

1 members found this post helpful.

Only issue I'm having is with my slackware64 install: All themes/icons work except after upgrading Firefox wouldn't open saying "libgdksomething.so.2" missing
So, I have multilib/compat32pkg and I had compat32pkg convert x86_64 gdkpixbuf into 32bit as I'm running 32bit firefox/flash
Now firefox works but the themes/icons aren't working in firefox??
it's like muted and the icons are missing...

Can I use 64bit firefox/flash in slackware64 yet?

Only since September. http://www.linuxquestions.org/questi...player-833111/