Latest LQ Deal: Latest LQ Deals
Go Back > Forums > Linux Forums > Linux - Software
User Name
Linux - Software This 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.


  Search this Thread
Old 01-31-2005, 10:50 PM   #1
Registered: Nov 2003
Location: Sioux Center, IA
Distribution: RH9, Fedora Core I,II,III
Posts: 37

Rep: Reputation: 15
Multiple applications crash with Signal 11 in SIGSEGV

I am running FCII with the KDE desktop.
I have 256mb RAM.
I am using an AGP ATI 3D Rage IIC card.
(I have also tried an ATI 3d Rage Pro AGP 2x card)

My problem: Everything was working great on this build. Then a few days ago I tried upgrading to the 3D Rage Pro Card. Everything still went fine. I then setup VNC to autostart a KDE destop when loaded, so that I can admin this comptuer from another location. Everything was still fine. Then last night when I logged into the KDE interface, I started getting the error:

Konqueror has crashed with a signal 11 error (sigsegv). This had never happened in the past. This also started happening with seemingly randam apps, like certain admin tools and certain simple built in games. Some apps still work fine, like Open Office. But te ones that crash I cannot get to work.

I have tried putting the old video card back in, but I still have the problem. The rest of the system seems to work just fine, just the KDE graphics are messed up. It happens both in VNC and in the workstation desktop when logged in.

Are there any ideas on what could be causing such a "general" error to occure to so many varied applications? And any ideas, short of rebuilding the whole computer, on how to fix this?

If you need more information, please ask.
Old 02-01-2005, 06:05 AM   #2
LQ Newbie
Registered: Jul 2003
Posts: 28

Rep: Reputation: 15
It seems that you might have a hardware problem. You can try to find out using memtest86:
or cpuburn:

I would start with cpuburn.
Old 02-01-2005, 07:41 AM   #3
Senior Member
Registered: Sep 2003
Posts: 3,171

Rep: Reputation: 116Reputation: 116
A hardware fault is certainly possible, but it is not the place to start.

Since you recently installed a new video card and driver, you should start there.

I would think there is a good chance that the video driver changed some library setting that is now messing you up.

Try uninstalling the video drivers, and try going back to the video card that you removed. If the problem goes away, that isolates it to either the video card or the driver. Since you tried two different ATI video cards, more than likely the problem is a driver or library issue.
Old 02-01-2005, 01:01 PM   #4
Senior Member
Registered: Apr 2004
Location: Potchefstroom, South Africa
Distribution: Fedora 17 - 3.3.4-5.fc17.x86_64
Posts: 1,552

Rep: Reputation: 103Reputation: 103
I agree - since the only thing that changed was new video drivers, that most likely is the culprit. If I was you, I'd try reinstalling the whole operating system.

If you are running Windows as dual-boot, try using it for a few days and seeing if it runs. If it too has problems, something in your hardware is not oaky - but if it works fine, that means that you definitely have a Linux software problem.
Old 02-01-2005, 02:30 PM   #5
Dan Angelescu
Registered: Oct 2001
Posts: 81

Rep: Reputation: 15
It is a hardware problem .Maybe ram is faulty or even the mobo. Crashes with Signal 11 in SIGSEGV i used to have with faulty ram.When mobo is faulty all freeeze without leaving a core file.
All the best !
Old 02-02-2005, 05:57 PM   #6
Registered: Nov 2004
Location: Australia
Distribution: Fedora, Ubuntu
Posts: 55
Blog Entries: 2

Rep: Reputation: 17
The most common causes I have seen for random apps getting SIGSEGV is cpu fan stopped or slow, and ram not seated properly. It would be worth taking a quick look before chasing around after drivers etc.
Old 02-09-2005, 05:28 PM   #7
Registered: Nov 2003
Location: Sioux Center, IA
Distribution: RH9, Fedora Core I,II,III
Posts: 37

Original Poster
Rep: Reputation: 15
KDE Still crashing with Signal 11

I tired going back to the orgional card. Kudzu removed the old setup and then setup the orgional card, so I assume this means the old drivers are gone? I tried removeing and reinstalling KDE. No change. I noted that it is only KDE apps that wont' open, like Konsole, Konqeror, the terminal, and various administration tools from KDE. Non-KDE apps, like Open office, FireFox, and Groupwise run fine. Oner person suggested reinstalling X or upgradeing to FCIII. DOes re-installing X sound plausable? If so, how would I do that. Or sould I upgrade to FCII?

I'll let you know what the results on the RAM tests and CPU tests are too.
Old 02-09-2005, 11:53 PM   #8
Senior Member
Registered: Jan 2003
Location: Illinois (SW Chicago 'burbs)
Distribution: openSUSE, Raspbian, Slackware. Older: Coherent, MacOS, Red Hat, Big Iron IXs: AIX, Solaris, Tru64
Posts: 2,744

Rep: Reputation: 547Reputation: 547Reputation: 547Reputation: 547Reputation: 547Reputation: 547
Your power supply might be going bad.

I recently had this very same problem occur. A newly installed operating system (on hardware that was a year and a half old or so) ran fine for a week. Once I'd gotten comfortable with the new install, I fired up YaST to download updates. All sorts of error messages popped up and I wound up killing the update. Rebooting helped but only for a little while and even plain old console commands began failing randomly. Rebooted and select the memory test. Crapped out on the first test. Rebooted several more time and the memory tests died in different places.

I figured it was either a failing memory, motherboard, or power supply. The cheapest thing to replace was the power supply. After replacing that, the system has been trouble free ever since. The OS installation did not have to be redone, BTW. (YMMV)

Not to say you'll get off this cheaply but it's worth a look.

Good luck...
Old 02-14-2005, 12:40 AM   #9
Registered: Nov 2004
Location: Australia
Distribution: Fedora, Ubuntu
Posts: 55
Blog Entries: 2

Rep: Reputation: 17
I have seen KDE apps crashing on startup, or at a particular event (like scrolling) on one of my systems. I had been doing an upgrade (RH7.3 to 9 I think) by installing RPMS. As I "forced" some installs, so I thought I broke something. After a _lot_ of mucking around and installing from scratch and crashing during gentoo installs, I changed the case, CPU, RAM, and PS, and the fault evaporated. My best estimate is that it was the PS had started giving flaky levels. Good enough to boot and work most of the time, but when you stressed the world, it wasn't quite up to the task.

In short, I have to agree with rnturn. You should swap the power supply for another known good one as a test.
Old 04-10-2006, 06:54 PM   #10
LQ Newbie
Registered: Apr 2006
Posts: 2

Rep: Reputation: 0
I also get SIGSEGV on multiple applications when using VNC only. That is, when logging in to my desktop normally, all is fine. When I start Xvnc and use a remote vnc viewer, I see many applications crashing, but eventually desktop is shown.
I use RH-9.

The crashing processes are:
konsole (only when closed)

Is there more insight into this problem?
Old 04-10-2006, 07:14 PM   #11
Senior Member
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,187

Rep: Reputation: 354Reputation: 354Reputation: 354Reputation: 354
There are apps (GKrellM is one I use) that can monitor system temperature(s), power supply voltages, fan speeds, and (with hddtemp installed) hard drive temperature(s). Also CPU, Memory, Disk access, Net traffic, etc.

Of course, it needs to run, but you can set it to issue alarms when things start to go bad.

I keep it on my screen (using the "invisible" theme) as a sort of "security blanket."
Old 04-10-2006, 07:57 PM   #12
Registered: Nov 2004
Location: Australia
Distribution: Fedora, Ubuntu
Posts: 55
Blog Entries: 2

Rep: Reputation: 17
Did you install the vncviewer from the install disks or download them? If you downloaded them, did you have to override any dependancies? Have you updated any other libraries that might be used by vncviewer and had dependancy issues?

Just to clarify, is it the viewer or the server that is getting SIGSEGV?
Old 04-17-2006, 01:20 PM   #13
LQ Newbie
Registered: Apr 2006
Posts: 2

Rep: Reputation: 0
GL related crash

The crashes are on processes running on the server for X applications which display on the remote VNC client.

They all have very similar stack trace

0x40f05368 in waitpid () from /lib/i686/
#0 0x40f05368 in waitpid () from /lib/i686/
#1 0x406d0cb0 in ?? () from /usr/lib/
#2 0x406335cd in KCrash::defaultCrashHandler () from /usr/lib/
#3 0x40f04097 in __pthread_sighandler () from /lib/i686/
#4 <signal handler called>
#5 0x411ff4ff in glXChannelRectSyncSGIX () from /usr/lib/
#6 0x0805e000 in ?? ()
#7 0x412348e0 in ?? () from /usr/lib/
#8 0x0805e000 in ?? ()
#9 0x411fdd56 in glXChannelRectSyncSGIX () from /usr/lib/
#10 0x0805e000 in ?? ()
#11 0x0805e000 in ?? ()
#12 0x40ed71e4 in ?? () from /usr/X11R6/lib/
#13 0x0805d6e8 in ?? ()
#14 0x40e0d472 in XCloseDisplay () from /usr/X11R6/lib/
#15 0x408f9f1b in qt_cleanup () from /usr/lib/qt-3.1/lib/
#16 0x40954f34 in QApplication::~QApplication ()
from /usr/lib/qt-3.1/lib/
#17 0x405cbc3a in KApplication::~KApplication () from /usr/lib/
#18 0x41bf57a7 in main () from /usr/lib/

Which seems to point at lack of GL with VNC.
Yet, it still looks like a bug (why crash on exit only?).

I installed realvnc using rpm.
Old 04-17-2006, 08:22 PM   #14
Registered: Nov 2004
Location: Australia
Distribution: Fedora, Ubuntu
Posts: 55
Blog Entries: 2

Rep: Reputation: 17
Note that this is '' that is crashing and not he VNC server. I guess the same app does not crash without VNC involved. In that case I would be looking for a KDE setting that exercises a missing feature in VNC and handles VNC's 'I cant do that' response badly. Since the crash comes in the glx library, I would be looking for 3D related settings.
Old 04-18-2006, 01:19 AM   #15
LQ Newbie
Registered: Apr 2006
Posts: 2

Rep: Reputation: 0

It happens when there is conflict with the hardware drivers and graphics drivers.
I see the solution in two ways
1) Slow but reliable

I think to go to the root of the problem, clean the harddisk and re-install OS and follow the same steps as you have done earlier and check you encounter the same problem.

2) Fast
Unload VNC, KDE and then card drivers and check if the system behaves the same way.

This way may be you can solve the problem.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Program received signal SIGSEGV, Segmentation fault ims_mca Linux - Distributions 0 03-09-2005 04:16 AM
Kaffeine 0.5 crashes - signal 11 (SIGSEGV) Toonses82 Linux - Software 2 02-02-2005 09:11 AM
k3b crashes with signal 11 sigsegv cf050 Linux - Software 0 11-19-2004 09:39 AM
signal handling (SIGSEGV) in threads Sinner6 Programming 1 11-09-2004 04:52 PM
Konqueror crashed and caused the signal 11 (SIGSEGV) bill.692 Linux - Software 1 04-29-2004 11:15 AM > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 07:33 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration