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.
~Kirk

It seems that you might have a hardware problem. You can try to find out using memtest86:
http://www.memtest86.com/
or cpuburn:
http://pages.sbcglobal.net/redelm/

I would start with cpuburn.

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.

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.

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 !

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.

Howdy.
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.
~K411184

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...

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.

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:
kmixctrl
kcminit
ksplash
konsole (only when closed)

Is there more insight into this problem?

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."

AbuLafya,
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?

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

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.

Note that this is 'konsole.so' 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.

Hi,

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.