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 currently having a strange issue when I go to shut down/log off/restart linux.
An error comes up saying KDE panel (kicker) has crashed with a "signal 11 (SIGSEGV)" error. When I close this error message the computer shuts down as normal and while using linux (and the KDE panel) there is no obvious sign that something is not working correctly.
Has anyone had this problem before I cannot find any references to it.
Even if anyone has any idea where to look for a problem. the panel seems to be working fine which is the annoying thing.
This was a very common problem, but it was (supposed to be) fixed in KDE 3.5. What version of KDE are you running? I haven't had this happen since I upgraded.
Sorry Folks, bumping this cause still causing me issues. Does anyone have any ideas of how this problem may be solved? A refresh install of KDE? An update and from where?
Just to let anyone who may have had similar issues this was solved with a yum update of kde. The version I used seemed to have a bug and has obviously been fixed with version 3.5.0-0.2.fc4.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.