[SOLVED] Slackware64-current (16/1/2011) - KDE not starting
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I had the same problem for awhile trying to run slackware-current in a vm. I discovered a solution.... but I can't recall if this was it. It is out of the changelog.
Quote:
x/mesa-7.9-x86_64-1.txz: Upgraded.
I was on the fence with this upgrade, and in fact it sat in /testing for
days with mesa-7.8.2 queued instead. But it seems the Intel driver really
does need this version of Mesa or there are major problems with compositing
(most of them leading to an X server crash).
If X crashes at start, try disabling compositing. Create a file named
/etc/X11/xorg.conf.d/disable-composite.conf with this in it:
Section "Extensions"
Option "Composite" "Disable"
EndSection
The machine that had issues here was using an onboard nVidia 6150SE.
Using the nv, nouveau, or even the vesa driver, X crashed at start unless
compositing was disabled. However, everything works perfectly when using
the binary nVidia drivers, and odds are that most users with decent nVidia
hardware are doing just that. So, that's the situation with nVidia and
Mesa as observed here for now. Hopefully the defaults will work better
soon, but meanwhile if you have nVidia hardware you may have to either
disable compositing or obtain and use nVidia's binary drivers.
And yes, it was only crashing on KDE for me as well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.