Bug 278713 - Skanlite crashes when umax drivers segfault
Summary: Skanlite crashes when umax drivers segfault
Status: RESOLVED WORKSFORME
Alias: None
Product: libksane
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Kåre Särs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-28 15:30 UTC by OpenSUSE User #314
Modified: 2018-11-13 16:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description OpenSUSE User #314 2011-07-28 15:30:47 UTC
Application: skanlite (0.7)
KDE Platform Version: 4.6.5 (4.6.5) "release 5"
Qt Version: 4.7.3
Operating System: Linux 2.6.39.3-37-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I was trying to scan an image with Skanlite using a Umax Powerlook III scanner

The scanner is detected as umax:/dev/sg6
It is connected to an Adaptec SCSI Connect 2904 PCI card.

If I test the scanner through Yast I get to see the following error:
Test with 'scanimage -d umax:/dev/sg6 -v' failed.
The results are:
scanimage: sane_start: Out of memory
/usr/lib/YaST2/bin/test_scanner_backaend: line 66:   788 Segmentation fault   scanimage -d $SANE_DEVICE -v > /dev/null

The crash can be reproduced every time.

-- Backtrace:
Application: Skanlite (skanlite), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f14caa23760 (LWP 31544))]

Thread 3 (Thread 0x7f14b9fe1700 (LWP 31548)):
#0  0x00007f14c7b7e503 in poll () from /lib64/libc.so.6
#1  0x00007f14c35f2114 in ?? () from /lib64/libglib-2.0.so.0
#2  0x00007f14c35f2650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#3  0x00007f14c9174286 in QEventDispatcherGlib::processEvents (this=0x890c40, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f14c91488d2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f14c9148ae5 in QEventLoop::exec (this=0x7f14b9fe0de0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007f14c905d7a4 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:492
#7  0x00007f14c912a008 in QInotifyFileSystemWatcherEngine::run (this=0x890540) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f14c9060095 in QThreadPrivate::start (arg=0x890540) at thread/qthread_unix.cpp:320
#9  0x00007f14c8dcfa3f in start_thread () from /lib64/libpthread.so.0
#10 0x00007f14c7b8767d in clone () from /lib64/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f14b8b27700 (LWP 31553)):
[KCrash Handler]
#6  0x00007f14c8dd56d1 in pthread_cancel () from /lib64/libpthread.so.0
#7  0x00007f14b95c20d2 in do_cancel (scanner=0x7ff790) at umax.c:4677
#8  0x00007f14ca1b31a3 in KSaneIface::KSanePreviewThread::run (this=0x843d80) at /usr/src/debug/kdegraphics-4.6.5/libs/libksane/libksane/ksane_preview_thread.cpp:88
#9  0x00007f14c9060095 in QThreadPrivate::start (arg=0x843d80) at thread/qthread_unix.cpp:320
#10 0x00007f14c8dcfa3f in start_thread () from /lib64/libpthread.so.0
#11 0x00007f14c7b8767d in clone () from /lib64/libc.so.6
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f14caa23760 (LWP 31544)):
#0  0x00007f14c8dd438c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f14c906077b in wait (this=<value optimized out>, mutex=0x890610, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x890610, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x00007f14c905f810 in QThread::wait (this=<value optimized out>, time=18446744073709551615) at thread/qthread_unix.cpp:722
#4  0x00007f14c911d820 in QFileSystemWatcher::~QFileSystemWatcher (this=<value optimized out>, __in_chrg=<value optimized out>) at io/qfilesystemwatcher.cpp:446
#5  0x00007f14c911d8f9 in QFileSystemWatcher::~QFileSystemWatcher (this=0x8904f0, __in_chrg=<value optimized out>) at io/qfilesystemwatcher.cpp:462
#6  0x00007f14c915ba34 in QObjectPrivate::deleteChildren (this=0x890240) at kernel/qobject.cpp:1955
#7  0x00007f14c9160782 in QObject::~QObject (this=0x890510, __in_chrg=<value optimized out>) at kernel/qobject.cpp:946
#8  0x00007f14c65d0e09 in ?? () from /usr/lib64/libsolid.so.4
#9  0x00007f14c7ae95a1 in __run_exit_handlers () from /lib64/libc.so.6
#10 0x00007f14c7ae95f5 in exit () from /lib64/libc.so.6
#11 0x00007f14c8360f48 in ?? () from /usr/lib64/libQtGui.so.4
#12 0x00007f14c9aa0428 in KApplication::xioErrhandler(_XDisplay*) () from /usr/lib64/libkdeui.so.5
#13 0x00007f14c685978e in _XIOError () from /usr/lib64/libX11.so.6
#14 0x00007f14c685703d in _XEventsQueued () from /usr/lib64/libX11.so.6
#15 0x00007f14c68478df in XEventsQueued () from /usr/lib64/libX11.so.6
#16 0x00007f14c8399a4c in ?? () from /usr/lib64/libQtGui.so.4
#17 0x00007f14c35f184c in g_main_context_check () from /lib64/libglib-2.0.so.0
#18 0x00007f14c35f2132 in ?? () from /lib64/libglib-2.0.so.0
#19 0x00007f14c35f2650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#20 0x00007f14c917422f in QEventDispatcherGlib::processEvents (this=0x621b00, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#21 0x00007f14c8399bae in ?? () from /usr/lib64/libQtGui.so.4
#22 0x00007f14c91488d2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#23 0x00007f14c9148ae5 in QEventLoop::exec (this=0x7fff540afa60, flags=...) at kernel/qeventloop.cpp:201
#24 0x00007f14c914cf2b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#25 0x000000000040ac57 in _start ()

Reported using DrKonqi
Comment 1 Andrew Crouthamel 2018-10-29 22:36:22 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 2 Bug Janitor Service 2018-11-13 14:34:12 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 3 OpenSUSE User #314 2018-11-13 15:12:56 UTC
Thank you for getting back to this, however I no loner have the hardware in my possession, so I am unable to test. I am ok with closing this ticket.
Comment 4 Andrew Crouthamel 2018-11-13 16:25:09 UTC
Thanks for the update!