Bug 156787

Version:            (using KDE 3.5.7)
Installed from:    SuSE RPMs
OS:                Linux

After entering password in login screen,
system continues booting, occasionaly the kde start sequence is interrupted by a crash window for scim.
I am able to save a trace, which is as followed:
[?1034h(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb67f96d0 (LWP 3910)]
[New Thread 0xb6447b90 (LWP 3913)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb7b51df2 in QGListIterator::QGListIterator ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#7  0xb6a65a06 in KServiceTypeProfile::offers () from /opt/kde3/lib/libkio.so.4
#8  0xb6a664cc in KTrader::query () from /opt/kde3/lib/libkio.so.4
#9  0xb6a66db8 in KTrader::query () from /opt/kde3/lib/libkio.so.4
#10 0xb7072f39 in SkimPluginManager::allAvailablePlugins ()
   from /opt/kde3/lib/libskim.so.0
#11 0xb7073ae8 in SkimPluginManager::SkimPluginManager ()
   from /opt/kde3/lib/libskim.so.0
#12 0x0804a7d9 in QGList::~QGList ()
#13 0xb6dd3fe0 in __libc_start_main () from /lib/libc.so.6
#14 0x08049c01 in QGList::~QGList ()

The bad thing is, that after saving this report, and acknowleding the error, the start up sequence of kde does not continue. The only thing to do, is a hard reset and restarting linux. Normally the error does not occur a second time  the same day.

I am confused.

Frank