Version: (using KDE KDE 3.3.2) Installed from: Unlisted Binary Package OS: Linux Can't tell what this is about but it happened a couple of times with my kooka. The problem is gone for now but I just wanted to report it. I started kooka via the console and then it crashed and gave me this: 0xa6a89656 in waitpid () from /lib/i686/libpthread.so.0 #0 0xa6a89656 in waitpid () from /lib/i686/libpthread.so.0 #1 0xa76810c5 in KCrash::defaultCrashHandler(int) () from /usr/lib/libkdecore.so.4 #2 0xa6a884ec in __pthread_clock_settime () from /lib/i686/libpthread.so.0 #3 0xa6887ca8 in __libc_sigaction () from /lib/i686/libc.so.6 #4 0x080852a4 in KComboBox::itemSelected(QListBoxItem*) () #5 0x08067ed3 in KParts::DockMainWindow::metaObject() const () #6 0x08063ca3 in QGList::count() const () #7 0x08063724 in QComboBox::setEditText(QString const&) () #8 0xa6874c57 in __libc_start_main () from /lib/i686/libc.so.6
I'm having the same problem. Start Kooka, and it crashes. When starting from console, I get: [alex@fergus povray-3.6]$ kooka QLayout: Adding QComboBox/PREVIEWFORMATCOMBO (child of QVButtonGroup/unnamed) to layout for Previewer/unnamed libkscan: WARNING: Trying to copy a not healthy option (no name nor desc) libkscan: WARNING: Trying to copy a not healthy option (no name nor desc) QObject::connect: Cannot connect (null)::guiChange(KScanOption*) to ScanParams::slOptionNotify(KScanOption*) KCrash: Application 'kooka' crashing... [alex@fergus povray-3.6]$ Was installed from Mandrake 10.2 (2005 LE) RPMs, scanner is a Canon FB330P parallell port unit. It has always worked fine previously, seems to have only started crashing since the new version. Note however, it may not be entirely Kooka's fault. Xsane crashes as well, but with different messages. I haven't ried using the sacnner from within teh Gimp yet, possibly later. On the face of things, it appears that there may be a regression of some type.
Please check whether this is still a problem with a recent version of KDE, for example 3.5.8 (unfortunately no Kooka in 4.0).
No further information received, no backtrace. Please reopen the bug if the problem is still happening and can be reproduced.