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.
Hello all,
MY Bug Reporting Tool reported two notices recently.
1.process/usr/bin/gedit was killed by signal 11(SIGSEGV).
2.process /usr/libexec/gdm-user-switch-applet was killed by signal 11(SIGSEGV).
As a result unable to open *.txt files using mouse. Also as I minimizes the the program , it simply disappears and had to use ctrl+tab to make it visible.
Most distributions include the ability to boot the memcheck utility. It runs standalone and checks CPU and memory fairly well.
Hi,
As I mention at the very first that I am unable to open *.txt files using mouse and as I minimizes the the program , it simply disappears and had to use ctrl+tab to make it visible.
Is it possible to make those actions as normal as before ?
Hardware memory problems are particularly likely to become evident in programs that use a lot of memory.
For instance I had a series of firefox crashes (but did not catch on to the cause) until the kernel crashed and I thought it was time to do memtest ... sure enough a fault found right away. Be prepared to run it for hours though to be more certain of good memory if no fault is found immediately.
Those crashes appeared in my server. I have been running wrf for simulation on it from couple of days and it's still running.
I think I will be getting trouble as I turn off my server.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.