Nevermind, I think it was a hardware issue. Same thing started happening in Windows. I've played with the memory and it seems to be working now. If you're still interested in what the problem was, read on:



I have just installed SuSE 9.2 to on my computer (ftp install worked like a charm!). I have it set up to dual boot, and I am using KDE. I have been having problems, however, while on the internet. Regardless of which browser I am using (Firefox, Konqueror, or the GNOME one), I get kicked out of KDE (back to the login page) when I try to move from the homepage. I can sometimes get a couple pages past the homepage, but not often.

No error message appears, just a black screen, then the login page. If there is a way to see the error report I don't know about it, yet.

I did receive the following report, whih is cryptic to my untrained eyes, when Konqueror kicked me out of the browser, but not all the way out of KDE:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1095694848 (LWP 5984)]
[KCrash handler]
#7 0x41719b04 in KonqMainWindow::slotSendFile ()
from /opt/kde3/lib/libkdeinit_konqueror.so
#8 0x4171ff62 in KonqCombo::insertPermanent ()
from /opt/kde3/lib/libkdeinit_konqueror.so
#9 0x417200c6 in KonqMainWindow::comboAction ()
from /opt/kde3/lib/libkdeinit_konqueror.so
#10 0x4172019c in KonquerorIface::addToCombo ()
from /opt/kde3/lib/libkdeinit_konqueror.so
#11 0x41777a89 in KonquerorIface::process ()
from /opt/kde3/lib/libkdeinit_konqueror.so
#12 0x408d41d2 in DCOPClient::receive () from /opt/kde3/lib/libDCOP.so.4
#13 0x408d8e06 in DCOPProcessInternal () from /opt/kde3/lib/libDCOP.so.4
#14 0x408da417 in DCOPProcessMessage () from /opt/kde3/lib/libDCOP.so.4
#15 0x408e93e8 in KDE_IceProcessMessages () from /opt/kde3/lib/libDCOP.so.4
#16 0x408d5517 in DCOPClient::processSocketData ()
from /opt/kde3/lib/libDCOP.so.4
#17 0x408da23b in DCOPClient::qt_invoke () from /opt/kde3/lib/libDCOP.so.4
#18 0x40bf80ee in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x40bf871d in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x40f48fe0 in QSocketNotifier::activated ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x40c17d40 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x40b9585f in QApplication::internalNotify ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x40b97423 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x40827a91 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#25 0x40b899d6 in QEventLoop::activateSocketNotifiers ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x40b42f12 in QEventLoop::processEvents ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0x40bad7b1 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0x40bad5f6 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x40b972ef in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x41767b3c in kdemain () from /opt/kde3/lib/libkdeinit_konqueror.so
#31 0x0804e7a6 in launch ()
#32 0x0804eebc in handle_launcher_request ()
#33 0x0804f479 in handle_requests ()
#34 0x0804fc5a in main ()

Any help with this would be greatly appreciated.

*I did put a new stick of memory in soon after the install. I thought that this might be contributing to the problem, but running memtest didn't come up with any errors.