well I swear I love slack its my best friend but its like we just got into an argument. every shutdown and restart is different. was just watching a video before reboot now the display is blank again. or I can get the audio working perfect and reboot and its down again.

or a partition idles out and won't remount.

was a clean install of slack 13.0

more venting then anything sorry I need rock solid stability and don't have time to tweak my main box for a week this time. I really need to boot up and start using a spreadsheet and access my exchange server for work.

I used to like it when i had time to play and will again I will install slackware to any secondary boxes but I have to say I am going to have to put windows on this box or tweak for a week. its Sunday morning and I have reports to get out for morning. I just don't have a choice.

I know how to build a kernal from source, don't care I can't download .deb files and kde thats stock with slackware 13.0 4.3 or 4.4 is an evil incarnate. can't switch users it locks, locking users locks. dual booting is not for me done it to much, vnc'ing into slack is nice, ssh to slack is great. but to take a box and install it stock in the morning and you need reports and such working by noon rock solid just isn't happening. I spent to much time this weekend going what the heck and going okay so sound works if i go run level 3 and then startx, but not if I go into run level 4, okay that's why i lost sound for a couple hours.

its this kind of thing that's slowing me down from USING my box right now.

sorry feel like hauling my favourite car to the junk yard stating this.

Robert

Hi
You're not the only one, many people have had troubles using KDE with slack 13. If you want something so that it works without much tweaking out of the box, why don't you get your work done in XFCE or Fluxbox for the time being and when you have the time tweak your KDE settings to your liking. I had k3b burn issues using KDE and a few minor glitches, but it works fine after tuning a little bit.

Yep. I'm definitely leaning towards Xfce as KDE 4.xx still has its problems. Each day I use Xfce more and more as it "doesn't get in the way" and little things that won't work in KDE 4.2.4 or 4.3.1, work in Xfce. In other words, while not as "pretty" as KDE 4.xx, Xfce gets the job done.

I agree with most people at this point. When 13.0 came out I used 4.2.4 for about two weeks and I couldn't use it for more than about 2 hours with out something crashing, ever since I upgraded to the unofficial 4.3.1 packages I have had no problems. XFCE also works flawlessly.

I used KDE 4.2.4 for awhile when 13.0 came out. I didn't have any issues with it after I fixed k3b. However, I now mainly use XFce and Fluxbox as I don't need all the bells and whistles that KDE has.
I love the blazing speed of the lighter environments.

Been using KDE 4.2.4 with slack 13 for about a month. These are the issues I have had.
* Occasional Amarok crash, approx twice a week
* Kmail sometimes does not include the message when forwarding
* Kmail freezes for about a minute when opening up an email with many attached images

That is it, I have KDE4 to be an improvement on KDE3. Additonally I used Kubuntu 9.04 for a few weeks as Slack did not have KDE4 then. Slack 13's KDE4 performs much better than the Kubuntu version especially in speed.

Just curious, how did you fix the k3b issue?

I installed the kde3 version of k3b located in /extra/kde3-compat on the Slackware 13.0 DVD.
Prior to this k3b wouldn't work for me. The kde3 version works flawlessly.

Since I always do a full install I take it for granted everything is installed by default and expect it to work ootb. Thanks for the info, I'll give it a shot again.

You're welcome.
I also use pkgtool to remove the version of k3b that ships with KDE 4.2.4. I also install all of the kde3 compat libraries on my Slackware 13.0 systems.

Yes, it was my careless mistake in reading anyway. It was clearly mentioned in the Release Note about k3b issue and it's solution.