I have this issue too, the segmentation fault thing. But when at runlevel 4, I can start KDE though.

KDE Compositing problem - update
 

I installed (again!) a fresh Slackware-current (32 bit), the last entry in Changelog dated Tue Nov 30 23:39:25 UTC 2010.

OK there has been an update of KDE since then and I will check it ASAP but first let me report about what I have found so far ;)

I have a Nvidia graphical card, lspci|grep VGA says:I installed everything but the Nouveau X driver. Using the huge kernel when I "startx" from runlevel 3 :

• Every WM/desktop but KDE is launched fine with either nv ou vesa X driver (I did put a minimal vesa.conf file in /etc/X11/xorg.conf.d to check with vesa, as when the nouveau module is not installed X use nv by default)
• KDE crashes at startup using either nv or vesa
• But KDE is launched fine if I upgradepkg to the nouveau X driver provided in /extra. This was not the case a while ago, but may be due to the fact that the X server has been patched recently to try nouveau before nv (another solution being to choose explicitly the nouveau X driver in a configuration file)

The same problem occur with KDE if I set the default runlevel to 4 in /etc/inittab.

Workarounds I know of:

• Don't use KDE (just kidding - well, mostly)
• Do what's suggested in the changelog entry dated Sun Nov 14 23:58:42 UTC 2010
  Code:

  ---

  Create a file named
      /etc/X11/xorg.conf.d/disable-composite.conf with this in it:
      Section "Extensions"
      Option "Composite" "Disable"
      EndSection

  ---

• Edit the file ~.kde/share/config/kwinrc which is created at first KDE startup, replacing "OpenGLIsUnsafe=false" by "OpenGLIsUnsafe=true"

PS I couldn't find which program write ~.kde/share/config/kwinrc. Anyhow you will hardly convince me that it's an X or mesa problem unless you expose good reasons. IMHO it's really a KDE problem, may be only with the 4.5.1 version.

Stay tuned, I will provide an update as soon as I can try with KDE-4.5.4

Update after slackpkg update && slackpkg upgrade-all including KDE-4.5.4 && rm -rf ~/.kde : nothing changed, alas.

The /etc/X11/xorg.conf.d/disable-composite.conf solved my problem with KDE. Just updated last night and today there's another patch. Have yo update once again :D

@Didier - Have you tried blacklisting the Blur effect and Lancoz filter? http://www.linuxquestions.org/questi...ml#post4167103

Here is another blog post that provides more information on KDE 4.5 and graphics drivers. http://blog.martin-graesslin.com/blo...orkspaces-4-5/

Thanks for the suggestion allend but I didn't yet - I promise to try in the sake of completion but honestly I do not plan to use KDE any time soon anyhow, thus my only concern is not to have new slackers disappointed by a crash at the first launch of their shiny new slackware-13.2.

In fact my advise to nVidia GPU owners is to either use "nouveau" or (if they post-install it) the proprietary drivers, aka "the blob", as "nv" is really dead now and "vesa" a last resort if nothing else works.

But as "nouveau" is still in "extra" they should be able to use "nv" or "vesa" at first and if they use KDE (most will do, I guess), they will be disappointed unless this issue be fixed by a member of the Slackware Team in concern - EH or PV or P++V++ aka RW I guess ;)

About the link you provided I am not sure I understood everything - in fact I am sure I didn't, let's excuse my bad English on that ;)

<off topic>@dc_eros there is a typo in your signature my friend, should read omelette au fromage</off topic>

<off topic>Someone hasn't seen Dexter's Lab</off topic>

@T3slider: You're right of course, thank you for having provided me a good occasion to enhance my American culture.

I have eventually found it here http://jimerryan.multiply.com/video/...The_Big_Cheese

So I should have complained to Genndy Tartakovsky, sorry about thet dc_eros :confused:

Killed my KDE again:
Tried to switch back from fglrx to radeon driver, so I uninstalled flgrx, removed xorg.conf, rebooted. Bang, KDE crash. Started from cli: crashes because of lack of libatiuki.so.1, which is a part of fglrx. Reinstalled kde, still the same. WTF - why kde becomes dependant on driver provided by fglrx driver?