Salix Forums

Is there a how-to somewhere for the proper way to add KDE to Salix. I decided to 'go for it' and see what the new KDE has to offer, tonight, but I'm unclear on how to actually get it to start.
Not that experienced with the xinitrc file, I think that's what it is, or was, in Slackware. I downloaded the KDE 4 stuff thru the gslapt (16 total packages) but didn't see kdm mentioned. Maybe it's part of the kdebase.

thanks immensely! It worked. Now to do some exploring...

If you have some LInux experience and want to have latest KDE (which is better than the version in available in Slackware) you can check http://alien.slackbook.org/ktown/
But this needs an update to "salix-current" first. Just wanted to drop the note here

Thanks for the tip, I haven't had time to mess around with the new KDE I downloaded yet, but it looks like a fairly shocking change from KDE 3.5, which I was familiar with.
I thought I had Salix already 'current', I keep up with the upgrades....I'll search for more info on that, since I see on distrowatch that a new Salix has been released.
*My biggest complaint with KDE 3.5 has seemingly not been fixed in KDE4 either, I have found. That is a persistent quirk where starting Firefox almost always causes a second instance of Firefox to try to start-causing the little FF logo to bounce around for 30seconds or so until it times out. I have never been able to find out what causes that.

linuxfun wrote:*My biggest complaint with KDE 3.5 has seemingly not been fixed in KDE4 either, I have found. That is a persistent quirk where starting Firefox almost always causes a second instance of Firefox to try to start-causing the little FF logo to bounce around for 30seconds or so until it times out. I have never been able to find out what causes that.

This only happens if I start FF second time from menu. If I click on links in other apps everything works fine: FF just opens another tab and no icon bouncing

It's a mystery to me, but starting the FF from the menu does it every time with this new KDE, and at least half the time in my old OS, Slamd64. Using Salix with the standard DE , I've never seen it happen. I read once somewhere in Slackware that it has something to do with QT, but who knows.

You can change the startup notification behaviour (and time out) in the KDE system settings. But why do you want to start FF from the menu again if it is already running?

Thenktor, I think you misunderstood. I don't want to start FF a second time if it's running. The problem has been, if I choose to open FF from the menu in KDE, it attempts to open 2 instances at once! Or at least that is what appears to be happening. Usually, the browser will open quickly, but as its opening, the little FF logo starts bouncing around on the screen, and shows a second line on the taskbar at tbe bottom of the page, as if I hit the button twice. Sometimes, it totally balks, and the bouncing logo will spin around for 30seconds and FF won't open at all(still showing firefox twice on the taskbar at bottom of the desktop). When that happens I have to wait until the logo disappears and click on firefox again in the menu. Puzzling!
Seems I have tried to start it from a terminal, and it works ok that way, at least it did in KDE 3.5.
Haven't tried that yet in this new kde4, I'll see what happens.
In KDE3.5 , Slackware 12 and Slamd64 12. it worked better if I created a desktop shortcut to FF, and didn't use the menu-entry to start firefox.

Menus suck... Alt+F2 -> firefox... done