Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
don't know what that error in particular is (I do see it sometimes when something crashes) but I'm sure it will help people if you gave more details. What are the programs that hang, when do they hang; e.g. a klick on something, trying to open a file, etc. any patters you noticed?
I have received signal 11 errors on starting KDE, and on Kolf. I have received signal 11 errors in Openoffice when I tried to open an MS Publisher file (I first got the normal error message regarding an incompatible file format, but then 5-10 minutes later started getting signal 11 errors in OO.
The machine is also acting odd, with an unexplained sluggishness and slower than normal loading of programs and internet sites (particularly when we use Mozilla.)
see kill -l, 11 is SIGSEGV, that means segmentation fault, see here: https://en.wikipedia.org/wiki/Segmentation_fault. If you got a lot of SIGSEGV that means hardware error. You may try to clean up that box, run memtest to check your hardware, replace RAM modules... Sometimes just taking memory modules out and putting them back solves this kind of issues.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.