SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I tried to check out the new kde 4.2 in -current but when I try to login it starts to load then the screen goes black and a box pops up that says "A Fatal Error Occurred The application Plasma Workspace(plasma) crashed and caused the signal 11 (SIGSEGV)." It goes on to say it is unable to create a valid backtrace because debugging isn't built into the package.
When this happened after an upgrade I decided to try starting it as a new user in case something in my ~/ was messing it up. I got the same results. I then decided to do a fresh install of -current to see if there was just something with my particular install that was causing it. I still get the same result.
I haven't seen any other reports of such a problem. Does anybody have any tips on how I might get this to work, or on steps to take to debug it.
Maybe you should make sure to have all your configuration files up-to-date. Run "slackpkg new-config" will do all the tricks for you. If it does not work, try "rm -rf ~/.kde" and start up kde again, maybe you would like to backup ~/.kde/share/config/plasma-applets.
Thanks for the tips, I did a fresh install of the latest -current so all my conf files should be good. I have tried removing ~/.kde for my normal user as well as with a new user with a blank ~/ and still get the same results. I tried re-installing all the kde packages from a different mirror and that didn't work either. It really has me scratching my head. I am going to try it on another computer and see what kind of results I get there.
Which video card and Xorg driver are you using? If your card has issues with 3d rendering this can cause issues with Plasma. I had issues starting KDE 4 in Virtual Box until I installed the VBox video driver from guest additions.
My card is an ATI HD3850 with fglrx, I also tried radeonhd with the same results. I haven't had any trouble out of the card otherwise. I am not sure what is meant by installing -current in directory l/. Thanks again for everyone's help.
Hi - running a fresh install (today) of -current on a Dell E1505 with a Radeon X1400 video card. I'm using radeonhd and an xorg.conf created by xorgsetup.
Things seem to be running smooth now, but I did have some d-bus related issues at first. I don't know how you are starting KDE, but I found that running as a non-root user and starting from KDM (as opposed to issuing a startx command from the CLI) seemed to clear up the d-bus related errors. These were not the same errors you're seeing, but still d-bus errors.
Reminded me of how freerock gnome would behave if you didn't start it from GDM - error messages about d-bus/messagebus and no icons on the desktop.
Thanks for the tips. I tried starting from KDM and it did get further along before it crashed, but it crashed just the same. I did try installing the kde packages from a different mirror than I originally got them from but I got the same results. I talked with someone else with the same issue as me after upgrading to -current, so I believe there to be a problem with certain setups.