Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 installed an unstable release of KDE 3.5 with no issues, Then when the stable release came out, I downloaded the .tar file and followed the same steps as the install: that is:
untar'd the KDE 3.5 tarball (with all the KDE libs etc)
Pointed Yast at it and updated all KDE files highlighted in Blue
Got an 'all clear' when I checked dependancies
Reboot
Now whenever I shut down, the Kicker reappears briefly and I get a 'Sigserv , Kicker crash.
It is a brief error message and then everything shuts down as normal, but is is annoying (especially as I had NO issues like this with the unstable 3.5 release)
I know this sounds a bit obvious, but should I revert back to the unstable 3.5, or is there a fix?
UPDATE: Just wondering, would a better practice be to boot into the Command Line (Runlevel 3), start Yast from there, then do a fresh install of the stable 3.5?
Previously I'd done all this in the KDE GUI
Last edited by Metalbarthug; 12-13-2005 at 07:02 AM.
It's been happening to me too. I found out it only happens when kmix is running. I tried rebuilding the kdemultimedia3 src rpm from the ftp.suse.com update for KDE and still it does the same. I'm clueless.
Just to say, I started getting Kicker crashes after I had customised certain preferences in the panel, for example, backgound image, size of icons. It seems KDE still had a few bugs in that early release of 3.5.
Since then I've moved to using GNOME, seems to be a bit more stable, but it horses for courses when it comes to Desktop choice.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.