Bug 341462

Summary: Crash while scanning with scanlite
Product: [Applications] Skanlite Reporter: zb4ng <zb4ng>
Component: generalAssignee: Kåre Särs <kare.sars>
Status: RESOLVED WORKSFORME    
Severity: crash CC: andrew.crouthamel, zb4ng
Priority: NOR Keywords: drkonqi
Version First Reported In: 1.1   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description zb4ng 2014-12-01 13:24:53 UTC
Application: skanlite (1.1)
KDE Platform Version: 4.14.3
Qt Version: 4.8.6
Operating System: Linux 3.16.6-2-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

Start scanlite, start scan with Preview ("Vorschau") or normal scan. After a while the application crashes. 
Start scanlite again, I get a message like "Opening of selected scanner not working" (I don't know the exact message, 
since my GUI - language is German)
After that, I can start scanlite, but the the app crashes again, when I start a new scan.

A couple of days ago, the problem has already shown up and disappeared after a little while,
but today it is persistent.

My scanner: HP OfficeJet 6500A

The crash can be reproduced every time.

-- Backtrace:
Application: Skanlite (skanlite), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8e60fa87c0 (LWP 7245))]

Thread 4 (Thread 0x7f8e4f4e5700 (LWP 7250)):
#0  0x00007f8e5dfee3cd in poll () from /lib64/libc.so.6
#1  0x00007f8e575cf268 in ?? () from /usr/lib64/libusb-1.0.so.0
#2  0x00007f8e5f28a0a4 in start_thread () from /lib64/libpthread.so.0
#3  0x00007f8e5dff67fd in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f8e4ce05700 (LWP 7252)):
#0  0x00007f8e5dfee3cd in poll () from /lib64/libc.so.6
#1  0x00007f8e59f3dbe4 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f8e59f3dcec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f8e5f64f0de in QEventDispatcherGlib::processEvents (this=0x7f8e4800b0c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x00007f8e5f620e6f in QEventLoop::processEvents (this=this@entry=0x7f8e4ce04de0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f8e5f621165 in QEventLoop::exec (this=this@entry=0x7f8e4ce04de0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f8e5f51e0bf in QThread::exec (this=this@entry=0x2881120) at thread/qthread.cpp:538
#7  0x00007f8e5f602783 in QInotifyFileSystemWatcherEngine::run (this=0x2881120) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007f8e5f52079f in QThreadPrivate::start (arg=0x2881120) at thread/qthread_unix.cpp:349
#9  0x00007f8e5f28a0a4 in start_thread () from /lib64/libpthread.so.0
#10 0x00007f8e5dff67fd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f8e473cf700 (LWP 7291)):
[KCrash Handler]
#5  0x00007f8e5df46187 in raise () from /lib64/libc.so.6
#6  0x00007f8e5df47538 in abort () from /lib64/libc.so.6
#7  0x00007f8e57a142a5 in _dbus_abort () at dbus-sysdeps.c:91
#8  0x00007f8e57a0aee1 in _dbus_warn_check_failed (format=0x7f8e57a1a4e0 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:275
#9  0x00007f8e579f3a6c in dbus_connection_send (connection=0x0, message=message@entry=0x2559cf0, serial=serial@entry=0x0) at dbus-connection.c:3307
#10 0x00007f8e4eac69dd in SendScanEvent (device_uri=device_uri@entry=0x2815fb0 "hp:/usb/Officejet_6500_E710a-f?serial=CN1AG431DF05JZ", event=event@entry=2000) at scan/sane/io.c:95
#11 0x00007f8e4eacee36 in ledm_start (handle=0x2815fa0) at scan/sane/ledm.c:874
#12 0x00007f8e60710782 in KSaneIface::KSaneScanThread::run (this=0x28370a0) at /usr/src/debug/libksane-4.14.3/libksane/ksane_scan_thread.cpp:98
#13 0x00007f8e5f52079f in QThreadPrivate::start (arg=0x28370a0) at thread/qthread_unix.cpp:349
#14 0x00007f8e5f28a0a4 in start_thread () from /lib64/libpthread.so.0
#15 0x00007f8e5dff67fd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f8e60fa87c0 (LWP 7245)):
#0  0x00007f8e5f28b4c2 in pthread_join () from /lib64/libpthread.so.0
#1  0x00007f8e575cf5a9 in ?? () from /usr/lib64/libusb-1.0.so.0
#2  0x00007f8e575cce9c in ?? () from /usr/lib64/libusb-1.0.so.0
#3  0x00007f8e575c6804 in libusb_exit () from /usr/lib64/libusb-1.0.so.0
#4  0x00007f8e4e4e7899 in ?? () from /usr/lib64/libhpmud.so.0
#5  0x00007f8e4e4dec2d in hpmud_close_device () from /usr/lib64/libhpmud.so.0
#6  0x00007f8e4e4defc0 in device_cleanup () from /usr/lib64/libhpmud.so.0
#7  0x00007f8e60deef3a in _dl_fini () from /lib64/ld-linux-x86-64.so.2
#8  0x00007f8e5df48bf9 in __run_exit_handlers () from /lib64/libc.so.6
#9  0x00007f8e5df48c45 in exit () from /lib64/libc.so.6
#10 0x00007f8e5e804fc8 in ?? () from /usr/lib64/libQtGui.so.4
#11 0x00007f8e60086760 in KApplication::xioErrhandler(_XDisplay*) () from /usr/lib64/libkdeui.so.5
#12 0x00007f8e5d1683be in _XIOError () from /usr/lib64/libX11.so.6
#13 0x00007f8e5d165dbd in _XEventsQueued () from /usr/lib64/libX11.so.6
#14 0x00007f8e5d157deb in XEventsQueued () from /usr/lib64/libX11.so.6
#15 0x00007f8e5e83b0ec in ?? () from /usr/lib64/libQtGui.so.4
#16 0x00007f8e59f3d661 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
#17 0x00007f8e59f3db7b in ?? () from /usr/lib64/libglib-2.0.so.0
#18 0x00007f8e59f3dcec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#19 0x00007f8e5f64f0be in QEventDispatcherGlib::processEvents (this=0x242adf0, flags=...) at kernel/qeventdispatcher_glib.cpp:450
#20 0x00007f8e5e83b676 in ?? () from /usr/lib64/libQtGui.so.4
#21 0x00007f8e5f620e6f in QEventLoop::processEvents (this=this@entry=0x7fffde73cae0, flags=...) at kernel/qeventloop.cpp:149
#22 0x00007f8e5f621165 in QEventLoop::exec (this=this@entry=0x7fffde73cae0, flags=...) at kernel/qeventloop.cpp:204
#23 0x00007f8e5f6265b9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#24 0x000000000040b1c7 in ?? ()
#25 0x00007f8e5df32b05 in __libc_start_main () from /lib64/libc.so.6
#26 0x000000000040b22f in _start ()

Reported using DrKonqi
Comment 1 zb4ng 2014-12-01 14:38:59 UTC
I have to correct myself:
It looks like, if the OJ has been running for a longer time, scanning works fine, but if I switch it off and on, the bug occurs again.
Comment 2 Andrew Crouthamel 2018-10-31 03:56:14 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 3 Bug Janitor Service 2018-11-15 10:49:49 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 4 zb4ng 2018-11-15 13:00:40 UTC
(In reply to Andrew Crouthamel from comment #2)
> 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 zb4ng 2018-11-15 13:04:05 UTC
(In reply to Andrew Crouthamel from comment #2)
> 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!

Looks like issue was fixed a long time ago. Had completely forgotten about it
I am going to put status to "RESOLVED" in a couple of days.
Comment 6 Andrew Crouthamel 2018-11-15 22:51:06 UTC
Thanks for the update!