Bug 137297

Summary: Crash after using k3b, SIGSEGV in sane_microtek_start()
Product: [Applications] kooka Reporter: Bernd Kloss <b_kloss>
Component: generalAssignee: Klaas Freitag <freitag>
Status: RESOLVED WORKSFORME    
Severity: crash CC: kloss.b
Priority: NOR    
Version First Reported In: 0.44   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Bernd Kloss 2006-11-13 20:14:51 UTC
Version:           0.44 (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Kooka is running without problems, but as soon as k3b has been running before and also ended, kooka crashes with sigsev 11 as soon as you start prescan or scan.
with kdegraphics-dbg crashmanager reports:

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1503152448 (LWP 6913)]
[KCrash handler]
#6  0xa5ce6b3e in sane_microtek_start ()
   from /usr/lib/sane/libsane-microtek.so.1
#7  0xa69e6a8f in sane_dll_start () from /usr/lib/libsane.so.1
#8  0xa69e87bd in sane_start () from /usr/lib/libsane.so.1
#9  0xa7ac9c58 in KScanDevice::acquire_data (this=0x819fbf8, isPreview=true)
    at /build/buildd/kdegraphics-3.5.5/./libkscan/kscandevice.cpp:1007
#10 0xa7ae4edb in KScanDevice::acquirePreview (this=0x819fbf8, 
    forceGray=false, dpi=0)
    at /build/buildd/kdegraphics-3.5.5/./libkscan/kscandevice.cpp:818
#11 0xa7ae548e in ScanParams::slAcquirePreview (this=0x8200d40)
    at /build/buildd/kdegraphics-3.5.5/./libkscan/scanparams.cpp:1000
#12 0xa7ae674c in ScanParams::qt_invoke (this=0x8200d40, _id=48, 
    _o=0xaff8454c) at ./scanparams.moc:154
#13 0xa6e35cb3 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#14 0xa6e36744 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0xa71c7d3f in QButton::clicked () from /usr/lib/libqt-mt.so.3
#16 0xa6ed2c4e in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
#17 0xa6e6c654 in QWidget::event () from /usr/lib/libqt-mt.so.3
#18 0xa6dcdbd6 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#19 0xa6dcfd79 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#20 0xa74c3e0e in KApplication::notify () from /usr/lib/libkdecore.so.4
#21 0xa6d61445 in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#22 0xa6d600df in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#23 0xa6d5e660 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#24 0xa6d74cb2 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#25 0xa6de8129 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#26 0xa6de7f4a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#27 0xa6dcf76f in QApplication::exec () from /usr/lib/libqt-mt.so.3
#28 0x0808c546 in main (argc=8, argv=0xa6a9c350)
    at /build/buildd/kdegraphics-3.5.5/./kooka/main.cpp:117
#29 0xa7875ea8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#30 0x080634f1 in _start () at ../sysdeps/i386/elf/start.S:119
Comment 1 Pino Toscano 2007-09-04 17:57:11 UTC
*** Bug 149535 has been marked as a duplicate of this bug. ***
Comment 2 Jonathan Marten 2008-02-24 14:59:10 UTC
This looks suspiciously like a kernel or SANE problem.  Please confirm the scanner model and connection in use.

Please also verify if possible whether this still happens with an up-to-date SANE and Kooka installation (try KDE 3.5.9, unfortunately no Kooka in KDE 4).
Comment 3 Bernd 2008-02-24 20:23:33 UTC
Mikrotek ScanMaker E6 

scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
        <Adaptec 2940A Ultra SCSI adapter>
        aic7860: Ultra Single Channel A, SCSI Id=7, 3/253 SCBs

Still KDE 3.5.5 

2.6.18-6-k7
all updates with aptitude

Something seems to have changed. Problem occurs even without K3B in advance.
Crash appears in 3 out of 10 times, then reboot is necessary.

Comment 4 Andrew Crouthamel 2018-10-29 22:33:47 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2018-11-13 14:18:05 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2018-11-28 04:46:19 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!