Lets hear those reviews guys
 

Soooo....just curious what everyone thinks of 13 so far?

I'm upgrading tomorrow I think and just wondering what people really like/don't like so far. I've heard a lot about problems with k3b needing KDE3 compatible libraries to work properly but not much else in the way of criticism (good or bad). Let's hear it :)

I'm running KDE and my head is still spinning from all the changes.

My old desktop is stuffed into a folder display in the upper left corner of the screen.

Dolphin replaced Konqueror as the default file manager and it's different.

I never had to mess with xorg config, it just works.

I'm using the nv drivers instead of the nVidia proprietary drivers for the first time.

I had to recompile KVM but I knew that was going to happen.

I suspect I'll need to learn more about d-bus but ignorance is bliss right now.

All in all I'm very impressed with Slack 13 and with KDE 4.2.4.

READ all the accompanying documentation before you start the upgrade. Robby did a great write up on how to do an upgrade.

Been using it prior to RC1, rock solid as usual.

I've just gotten 13 installed (32-bit). Can't comment on much yet (because I've literally just finished the install and logged in for the first time), except to say that the new kernel logo is very freaky (and yes, I know it's not a Slackware thing!).

Don't forget to submit reviews to the Slackware section of LQ's Distro Reviews. Helps to keep them all in one place and more easily findable.

XavierP: Nice, I haven't seen that section before.

<ontopic>
Well, I wanted to start install it on my laptop just to try it out. I don't really have time to make things work if something goes wrong on my stationary computer, so I'll have to wait with my primary computer until I know I have the time to fix it if it should go wrong.

Unfortunately my old laptop doesn't support booting from DVDs (all thoe it is a DVD player?) so I have an old slackware CD laying around that I'm using as a bootdisk. I use the setup program as well, but I mount the newest slackware image and install it that way.

After an hour of carefully selecting packages I wanted, i finally got passed bsd-games. The old setup program didn't like the new file compression, so that basically for me was an our wasted :P

So heads up, it looks to me that you can't use old slackware cds/dvds as bootdisk anymore.

You should still be able to use an old Slack floppy or USB boot disk to kick off the install though.

Actually I just installed the nVidia binary drivers. The install process created a /etc/X11/xorg.conf file. I discovered errors in /var/log/Xorg.0.log letting HAL and the X server configure everything.

My first clues were occasional window locks and ghost popups. When I tried glxgears and it didn't work that was confirmation. After installing NVIDIA-Linux-x86-185.18.36-pkg1.run the desktop transparency features started working.

I like it really much!
KDE 4 is fancy and, though I had to get used to the new paradigm, the overall usability is greatly improved compared to former versions.

Meanwhile I found a few little snags, that I can very well live with. Most of it is related to encoding problems and incomplete localisation. I set UTF-8 as standard, and all the comments and hints in Slackware include warnings that this might cause problems for some programs. Unfortunately some new KDE programs are affected, which is amazing, as I thought that Qt4 would support Unicode better than previous versions.

Example: KMail
Almost everything is translated to my language, just not the names of weekdays under which messages older than a few weeks are grouped.

Example: Dolphin
It sometimes struggles to display file names containing special national characters correctly. In other cases it displays them as expected, but cannot copy the file or directory to another location. The error message then shows a scrambled replacement code for the special character.
In all these cases, the CLI (I use Konsole) helped me out, so it's not a big deal. Should be fixed, nevertheless, though, as for bulk copies it's enverving when you get an error message for one file hidden in the deepest level of a complex directory structure, and you now have to check what has been copied properly and what failed.

Apart from these minor, more or less cosmetic problems, I am VERY happy with Slackware 13. The advantages of KDE 4 weigh out them by far.

gargamel

Would you be kind enough to expand on these broad, general statements? How is "Usability greatly improved"? "Advantages of KDE 4..." What advantages are those? What does KDE 4, other than being "pretty" do, that 3.5.10 does not?
Thank you.

A lot has changed, but so far everything is working great.

I like the new "look" of KDE4. And I am impressed by my new slackware64 13 distro.
I needed a little time for the new menu stiles and some application changes in KDE4. But I like changes. I have found two difficulties.

1. kdevelop - Since I was using this application a lot I am a little confused by it. I just read on the kdevelop site this:
I was thinking about upgrade (if it will be possible) from 3.9.91 to 3.9.95 I don't know if it changes something.
I don't know if the bugs are between 3.9.91 and 3.9.95 or between 3.5.. and 3.9.91.

2. I cannot start kpackage. It tells me this:
But this is more about KDE then slackware itself.

Kpackage needs smart to work. You can get a SlackBuild here Even then it's not really supported on Slackware - see here for more information.

Quick review: Slackware 13, 64 bit, ext4 FS

KDE 4, I went back to the Classic Menu style.

Not much there in Slackbuilds for 64bit. *see below

I miss Gnome... I'm sure (I hope) the folks at GSB are working away on a Slackware 13 release.

I have not run into any problems.

-JJ

*just read the release notes on $ARCH

I have it installed twice on the same machine. I installed originally using ext4. I ran into trouble with the boot loader and my system. Grub, mepis,slack,and lilo not platying nice with each other. I can fix it but its not pretty but it works.

It is running great and I really like it. First time I did not have to configure Xorg.conf to get my mouse working. Even the horizontal scroll with the tilting mouse wheels works.

I am kind of use to kde3 but kde4 is very different for me. I had to do a bit of reading,searching and fumbling around to get some things to my liking. I am suprised how fast it is. I was not expecting it. I am very pleased and going to stick with slack for a while. I have used it before and left for ububtu. But now am back and happy.

After my boot loader troubles I decided to wipe another partition and install slack again using ext3 fs. I wanted to see if there was any noticeable difference between ext3 and ext4. With this install I had three errors during the install. All seemed well after I booted. I used it for several hours with a couple of hard freezes. Now I cannot start firefox and can only run a couple of minutes without a hard freeze. I am not sure if my disks are faulty or just a fluke. I will use it for learning to see if I can solve the problems. I know its my fault for the problems on this install. I should have aborted and started it again.

Two thumbs up for Pat and the team, great job.

Kelean.

It's overall more intuitive, more "context sensitive" and it helps you actively to find your way, if you get stuck. E. g., in certain situations, when actually you have one window open, that's taking the whole screen, and KDE "guesses" from your mouse or keyboard actions that you are looking for another window behind the big one or on another workplace, it scales down the window view and displays all the windows open, so that you can easily pick the one you want. This may sound very complicated, but in fact it takes a lot longer to describe it than just to use it. Little helpers of this kind are implemented at different places, but usually an experienced user won't notice them. If you know what you are doing, they won't get in your way. They only appear, when they can really be useful. The KDE developers did a great job to implement this kind of feature.

BTW, I have, so far, been unable to reproduce this intentionally! It only happens really, when I am lost in my desktop environment and actually need. I don't know, but it almost seems KDE can read my mind...

And: KDE 4 so far is even more robust and faster than KDE 3.5.10 on my hardware. E. g., I've often seen a crash error message, when I left a KDE 3.5 session. I haven't seen such a useless message in KDE 4, so far.

Finally, I like the new dialogs for system settings and printing better than with 3.5, although the older versions worked well, without a doubt, already.

There are many subtle changes, not only regarding the looks of it, but also the feel. But it doesn't hurt, that all of this is also nicely packaged.

gargamel

Once again, the team has done an outstanding job. The install took about 20 min, and I was off and running! Full 64 bit capability, which is nice because it went a lot easier than installing from slackware64-current. The only problem I had was that the new config-less Xorg didn't detect my screen setup automagically (which is odd, I only have one) so I had to go and grab the nVidia drivers before I could run X. Small inconvenience for me, although I can imagine for some of the newbs that it would be difficult and a little daunting without being familiar with links. either way, KDE 4.2 is beautiful, albeit strange, and all the other software I have tested so far works beautifully. Thanks again Pat!

IIRC, if you take your mouse into the upper right screen and move it a little further it will do that with all the windows. But it has been a bit since I used it, as I am still waiting for time to upgrade Slack on my laptop, and my desktop is still not hooked up and will not be until I find a house.

Hello,

I installed 2 slackware64-13.0 and 2 slackware-13.0 machines since last friday. Everything is working fine.

Since I've been using Slackware64-current before the new installation it is not such a big jump for me.

Thanks to the Slackwareteam.

Markus

Ok i installed my 13.0, 32bit version last night, i mean morning ( from 3 to 5 in the morning ). I came across something totally different from my old 12.2. First the KDE4 wich i was familiar with from the Kubuntu live CD wich i tried out earlier this month. Although it is shiny and fancy, i don`t really like it, so i switched to xfce. My mouse works fine, scroll everything, i think my videocard needs a driver but i don`t know wich one to install. I use sbopkg tool and works very well. I`m happy with the overall result although i`m eager to get the slackbook 3.0 after it will be done :D

I've got Slackware 13 set up virtualized. As I had suspected, KDE 4 is pretty atrocious, even when packaged by Patrick (sorry Patrick... a plate of manure is still manure, no matter how artfully presented and prepared), so I'm going to try to get KDE 3.5.10 working on it and see how that goes. I'll post my results or methodology if I get it to work.

Thanks!
 

I installed 13.0 x86_64 and it is most excellent. I have been anxiously waiting for the release and am very grateful for all the folks at Slackware for putting it all together. The quality, reliability, simplicity, of slackware as a complete package operating system is unmatched. As mentioned by someone else above I momentarily tripped over an improper VESA screen size when first loading X but it was easily resolved when I installed the nvidia drivers. I did not even need to touch xorg.conf for anything which was a pleasant surprise. I am adapting to some of the new features and changes in KDE4 but it has been painless and fun. I visited slackbuilds.org and began grabbing all my necessary build scripts and applications and am on my way.

Thanks again to the Slackware Team and all the OSS contributors. Great Job!

Using Slackware64 here. Here's what I've done and my impressions so far:

1. Decided to try the optional 2.6.30.5 kernel in /testing. Got a few complaints from 'alsactl' upon startup, although sound worked. Chose not to play with fire and went back to 2.6.29.6. Audio comes from Intel HDA (Realtek ALC889)

2. Installed nvidia drivers using slackbuild scripts. No issues, woohoo.

3. KDE4 is pretty ugly out of the box, though that can be fixed in a few minutes. Compositing is nice. I don't care for the new 'System Settings' layout. I didn't notice an option to go into 'Administrator mode' to set permissions for K3B, had to log in as root to do so. There's no CUPS administration in System Settings. Used CUPS's web interface instead.

4. Installed QtCurve-Gtk2 from using slackbuild script. Really makes Firefox, Thunderbird and other GTK2 apps look nice in KDE4.

5. Used Dugan Chen's site for improved fonts. Thanks Dugan! Results are awesome.

6. Have a "take it or leave it" attitude over the default menu style in KDE4. It's nice for my girlfriend, who uses a few apps. Can just add those as Favorites, and she doesn't have to drill around as she would with the classic menu. I use the classic myself.

7. KDE4 version of K3B won't work successfully for me (Plextor SATA DVD burner). I've been using Nero Linux, which unlike the Windows version, is still lightweight. It does a good job.

8. Installed OpenOffice via slackbuilds. No surprises.

9. Installed VirtualBox 3.0.4 PUEL edition via .run file. Have a few minor quirks with it. Now and then, mouse control gets out of whack. If I enter seamless mode, then exit, I end up with an unmovable shade box, and you can't see the guest OS. This probably has something to do with compositing being enabled in KDE. I can shut the guest down with the keyboard, then all is good. Having a slackbuild available for the PUEL edition would be nice, but the .run file installs fine, and it has an uninstall option, so I guess it's not really necessary.

10. It appears I can only have sound coming from one source. If I play an MP3 in Audacious, I can't get audio while watching a flash video on YouTube. If a VBox guest OS grabs audio, I can't hear anything from the host. I guess I don't have a sound server running? Gotta look into that some more.

11. I will probably convert to a multilib setup for a few games, and possibly even Adobe Reader.


Happy to have 64-bit Slackware.

Thanks for the reply.
I came across that "feature" in an earlier version of 4.xx. Sorry, I don't remember which one. However, IIRC, you can trigger it by moving your mouse into the upper left hand corner (as you are looking at your screen). This is something "borrowed" from the Mac, BTW.

I installed Slackware 13 32-bit. So far it's been very solid and I haven't had any problems except for one application crash (the find dialog in KDE).

There are some things that could use improvement in KDE but that is hardly the fault of Slackware. The KDE help is sadly out of date and refers to functions that have been removed. Examples are the administrator mode of the login manager (no longer there) and the ability to disable all sounds (no longer there).

Amarok refuses to display the album covers that I installed on Slackware 12.2 and won't let me download any new ones. It never finds any on Amazon when it searches. There are some Amarok features like adding timing marks that are not really finished (no way to delete them after adding them).

Another strange thing that I've noticed is if I create icons as widgets and the icons refer to shortcuts in the menu, editing the widget icon changes the menu entry. Apparently the icons are more like an alias than a totally separate shortcut. The way I got around that problem was to put copies of shortcuts in a separate folder and then link the widget icons to those shortcuts. I happened to use a "Desktop" folder since I already had shortcuts for most things I wanted in that from the previous version of KDE. The "page" that is displayed does not show the contents of the "Desktop" folder but there is a folder widget that can be used to display the contents of any folder including "Desktop".

My biggest problem is that VirtualBox doesn't work with KDE if I enable the 3D compositing. The contents of the virtual machine windows don't appear and full screen mode doesn't work. Seamless mode does work after clicking the desktop once to make the windows appear. The interesting thing is that VirtualBox does work with XFCE and compositing enabled. I like VirtualBox but I've been fighting an ongoing battle with each version introducing new bugs.

I was a bit disappointed in the analog clock since it only has one color scheme (too dark with no numbers). I also spent some harrowing moments after accidentally dragging things into strange places.

I think Slackware makes the most out of a less than finished KDE. Only time is going to (hopefully) see KDE become more complete and consistent. Some distros have already moved on to KDE 4.3 but I have to wonder how solid that is. At least the KDE 4.2 in Slackware is working without any major problems.

In spite of my complaints with KDE I still feel more comfortable using it than Windows Vista or even Windows 7. Both of those somehow leave me always hunting for things and swearing at the extra mouse clicks and scrolling to get to what I want. My analog clock on Vista slowly drifts to the left with each reboot. It's certainly the strangest time drifting problem I've had. So far things in KDE stay where I put them.

Slackware 13 may very well have the best KDE 4 available and that's no minor feat considering the state of KDE. I think that Slackware 13 is an improvement compared to 12.2 and I thought 12.2 was one of the best Slackware releases.

Use "kdesu systemsettings" instead of logging in as root. I meant to add that to CHANGES_AND_HINTS.TXT, but it slipped my mind until the ISO's had already been sent off to the replicator :/

I'm feeling very slack!
 

Good solution Rob!
---

I've discussed this in at least two other threads, but here it is again: `kdesu` does not work for me on Slack64, at least not the way it should.

I have to:

Execute `kdesu something`
Let it reject my password a couple times.
Maybe then it will accept the PW, but "something" never starts.
Execute `kdesu something` again.
Get at least one more rejected PW.
Now, it starts "something" successfully (usually).

It's really annoying.

I don't blame it on Slackware, I blame KDE. And I'm using XFCE now, just because I prefer KDE4 less than KDE3 or XFCE.

Other than the above, Slack64 (Slackware 13 -- must get used to that!) is as delightful as ever, and I am extremely happy with it-- almost as happy as I'll be when I find the DVD in my mailbox in the near future :)

Sasha

I`m using the32bit 13.0 and I have that issue too.

Absolutely no problems at all with a 32bit install and xfce desktop. Of special note on my own system:

1. Installation was faster
2. Graphics with an only integrated intel graphics controller are crystal clear and quite responsive, improved from 12.2
3. Great new versions of my most-used packages
4. The whole system feels totally renovated and rock-solid!!

One happy customer :-)

Andrew

Just getting down to playing, right now. First of all, I don't think I'm going to get on with KDE 4. It seems that you can't disable all the tooltips (the ones when you hover over the pager and the Kickoff application launcher (K button) are annoying). Also, I don't seem to be able to create a vertical panel as easily I could before. Other than that, I've not noticed anything odd. I've got to disable HAL and create an xorg.conf and then hopefully that will be all I need to do!

Same here.

A possible explanation follows. ALSA allows several sound sources. But
rc.alsa seems to load OSS compatibility kernel modules. If the kernel OSS compatibility layer is used, it forbids other sound sources at the same time (both ALSA and OSS). All modern programs can use ALSA directly, but they often can also use OSS, and if they try OSS first, they go through the compatibility layer and block real ALSA (and other OSS users, too). The fix: rm the OSS compatibility kernel modules, or don't modprobe them and blacklist them, or something. If you have some prehistorical program which doesn't know ALSA, use "aoss" command which preloads libaoss.so userspace OSS compatibility layer.

There seems to be quite a lot of people, me included, who dislike KDE4 and prefer KDE3.5. That's the only thing, and it's a minor thing, I've found to complain about (so far).

I gave ext4 a try with the "slow format with bad block check" option and was a little surprised at how long the format took on 20 and 40 gig partitions. No other problems yet.

I don't like Dolphin, so I've changed the default file manager to Konqueror. A small thing, but I miss not being able to "open a terminal" from any location on the file system I browse to (under tools in konq, but can be added to the toolbar - in the context menu in XFCE). Particularly when I'm configuring a fresh install. And opening that terminal that hangs off the bottom of the Konqueror window is not the same thing. ;)

I'm getting intermittent mouse pointer corruption in both XFCE4 and KDE4, regardless of whether or not desktop effects are turned on or not. I have not yet tried using the suggestion in hints and tips to explicitly turn off compositing from within xorg.conf because it was not just in XFCE and the terminal redraws were not slow as described. Reminds me of a problem I had where I needed to disable offscreen pixmaps - but that was some time ago and I think it was with the Intel drivers at the time. I'm using ATI radeon mobility X1400 with the open-source radeon driver. Haven't really tried to fix that one yet.

All in all, pretty solid release. Most issues seem to be out of the control of Slackware. My biggest disappointment is with Linux in general and the the loss of support from ATI for my graphics card. Many people seem to want to lay all the blaame at the feet of ATI, but I also think that Xorg as well as the kernel development process share some responsibility.

I also used ext4 on a 500GB hard drive with slow format and bad block checks. I think it took about two hours to completely format. I was amazed by this new definition of "slow" :)

KDE4 is pretty horrible and for me it is a major problem. Setting the launcher to classic style mitigates some of the horrors but it seems that one cannot add Quick Launch buttons to the panel which for me is pretty basic.

Arubin, It's possible. please check my answer in the thread you opened on that topic

For those of us slackers who don't much care for KDE, the XFCE side of things in Slack-13 is looking very well. There are no revolutionary changes in XFCE compared to the move from KDE 3.x to 4.x; but that is what you would expect with XFCE. XFCE is simple to use; and it does what you expect it to do.

As for reviews, there is a blurb about Slackware 13 on today's DistroWatch Weekly:
http://distrowatch.com/weekly.php?issue=20090831#news

Hi Nylex,

Not sure what you're intention is re: disabling HAL, but I'm having little success with that :/

I AM using my old xorg.conf, as I always have, and that's fine & dandy; I also have in the xorg.conf the three 'magic lines' disabling HAL from my input devices (see ChangeLog for those lines);

However, for me:

Disabling HAL completely, such as during boot before X starts (like chmodding rc.hald to non-executable, or issuing `rc.hald stop`) causes problems. Specifically, X will still start, but all my VTs are dead, so things like CTRL-ALT-F2 takes me to VT2 with no display (typing in the dark).

Uninstalling HAL, makes X not start at all (dependency on HAL libs).

And removing the 3 magic lines from xorg.conf, makes any mouse movement cause X/KDM to restart (so can't use mouse).

There's a thread already called "hal - thoughts?" so rather than hijack this one, maybe we should direct HAL traffic back to that thread. Here's the link: http://www.linuxquestions.org/questi...&highlight=HAL

Sasha

Yeah, I'm going to try the alternatives to KDE4. In the past, briefly checking them out, I've preferred fluxbox to XFCE.

Some days ago I asked at IRC when would Slackware 13 be released. I got a strong "WHEN IT IS READY"... Well. I have installed it now and I have to smile at that response.

If KDE 4 was not stable yet, why was it included? :confused:

As others have said, it is less usable than 3.5.10. And yes, it has bugs. The new Konsole, for an example, makes a mess of itself when trying to modify the existing profile. I also managed to not allow to log myself after changing my icons set to GTK (had to remove all kde config files). KDM has some Lilliputian tiny fonts - which cannot be changed - which are not linux-compatible with my myopia. I also get the "akonadi" errors when logging into KDE as root.

EDIT: Changing Main Menu style from Kick-off to Classic, setting all font sizes to 10, and changing digital clock font to bold & adding date makes the whole set a bit more elegant. Also, I have found you can copy icons to desktop or panel by dragging them from Main Menu to desktop/panel.

All in all, now both main desktop managers for Linux seem to be quite screwed. Buggy and nazi-like Gnome (Torvalds dixit), and flashy-fairy looking KDE. Windows Vista may be heavy and unusable, but it IS beautiful at least.

EDIT: Well, after looking at it a bit closer, I'm starting to like a bit the new look&feel, I guess this is a bit insane.


I won't complain about the new (awful) kernel logo because I have found it was Torvalds issue, not Slackware's. I hope it will be gone in new kernel releases (I would actually vote for Tasmanian devil's extinction :mad:).

EDIT: Added "logo.nologo" (yes, dot, not "=") kernel parameter at boot and the Taz devils were gone. Better than hard killing them (just in case a Greenpeace member reads this).


Well, that's all for the time being :)

See this thread for some suggestions.
http://www.linuxquestions.org/questi...esting.-704430
I assume this is because they are ugly, nazi-like, gnomic creatures that only look uglier with face cancer.
There is a theory here that the reason that imported feral animals such as cats and foxes have not taken hold in Tasmania ( with consequent destruction of many native species) is because of these nasty little creatures eating up all the food the imports would otherwise dine on.
Beauty is in the myopic eye of the beholder.

I beg to differ from most comments on KDE4. Overall I'm pleased with KDE4 because it has improved speed (at start up and when launching applications like Firefox) although I confess that I'm not a power user so my needs may be limited versus the possibilities one would expect from a modern desktop.

For purpose of clarity, I explain what I do with my machine:

I use Slackware 13.0 with KDE4 as my main desktop at home to do mostly internet browsing (Firefox), office work (Kword + Kspread), listen to music (Amarok), watch some videos (Mplayer), send some mails (Kmail) and do some console work to manage the machine (Konsole).

I didn't tinker that much with the KDE4 shipped with Slackware:

- I changed my system configuration to use French language - OK
- I changed the background image - OK
- I added quick launch buttons and some plasmoids in the panel - OK
- I added my printer (EPSON Stylys Photo 950) - OK
- I transferred photos from my camera (Canon IXY 800 IS) - OK

I still need to test my scanner (hopefully it should be no big deal).

So far, I have two grievances:

- Koffice 2 looks promising but lacks features from 1.6 series (ex: draw charts in Kspread, arrays do not seem to work in Kword). But for simple clerical work, it's OK.

- I'm using Kmymoney2 personal finance manager and it's not yet ready for KDE4.

So to cope with these shortcomings, I still have 12.2 installed in another partition.

To conclude, I try to use Slackware KDE4 as much as possible and if it does not fit my needs I revert to 12.2. It just happens that 13.0/KDE4 fulfills most of my needs :)

Just grab logo_linux_clut224.ppm and logo_linux_vga16.ppm from old kernel's /usr/src/linux/drivers/video/logo/ directory and put it in new kernel's directory. Then change in Makefile ``Temporary Tasmanian Devil'' name with ``Tux'' name. Finally compile the kernel with default .config. You'll get generic-smp kernel with Tux instead of Tasmanian Devil. I did it.

I'm a KDE4 fan too especially after installing the nVidia binary driver using the SlackBuild. I like the look & feel along with the ability to change the desktop effects. It's different from KDE3 but I'm adapting to the KDE4 way of doing things.

I'm running init3, login, startx currently. When I ctrl-alt-f1 to the startup console there are lots of messages with many reporting errors. I don't remember many (if any) of these message with Slack 12.2 and KDE3.

Taz -> Tux
 

:)
You guys could just upgrade to a kernel >= 2.6.30 as Taz is re-replaced with Tux.

Sasha

In the past I compiled and installed every new version of the kernel. Since Slackware started to provide generic kernels I started to use them and stopped to change kernels on my own. I do it for the sake of the documentation of the system:

Likewise here. I'm utterly baffled at why KDE 4 is in Slackware 13 at all; I could see it being included in /testing, or /extras. That would make sense.

But no KDE 3.5.10 at all? And KDE 4.2.4 as the only KDE version?

I have to wonder if this is still Slackware, or if it has been taken over by someone else. I wasn't expecting to see KDE 4 at all in Slack until at least another year's worth of heavy development had taken place in it first (maybe by the time Slackware 14 is ready, KDE 4 might actually be a suitable replacement for KDE 3.5.10).

I wouldn't mind if it was actually the 'Taz' logo from the WB cartoon, but then again copyright issues would arise. :jawa:

I am too lazy to do a recompile just for a silly logo though. I'll just live with it until the next release.

The only other comment is about the bootscreen logo, see (http://www.linuxquestions.org/questi...0-00-750987/): It took me too long to catch that the numbers were binary :doh:, since at first I thought something happened during the install that corrupted the image. Then I wrongly thought it was hexadecimal numbers, not binary, because usually binary numbers are in groups of four not two, the way hexadecimal values are, but I guess Pat just thought it looked better. *shrug*

hexadecimal to decimal:

Just don't understand most of the complaints on KDE4. There are a few quirks here and there but it seems complete and stable in my opinion, and a signifcant improvement overall. I think Slackware has been wise to hang off on incorporating KDE4 until now -- but it seems like this was the right time to finally bring it in. I like KDE3 as much as the next person but the fact is, KDE3 will no longer be supported and will soon be at end of life scenario. Most of the users with the issues should head over to KDE development and try to get some of the issues corrected and also voice their opinions on various features that are missing/disliked. As far as I can tell you can make KDE4 look and feel virtually identical to KDE3... what are the issues?

Thank you for your ideas guys & girls.

I just have added the kernel boot param "logo.nologo" to hide Taz. See my original post for more changes.