Application: skanlite (23.04.3) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 5.19.0-50-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.7 [CoredumpBackend] -- Information about the crash: I was trying to use my scanner. I set the DPI from 75 to 300, set paper size to A4 and presses the "Scan" button. Skanlite then crashed. It is possible that Skanlite picked up the wrong scanner. I have an Epson L3160, and it shows both as such and as in Epson PID in xsane. However, since I cannot seem to be able to change scanners in Skanlite, I cannot test if it works with the right scanner. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 0x00007fcac86a15d5 in esci_request_extended_status () from /usr/lib/x86_64-linux-gnu/sane/libsane-epson2.so.1 #7 0x00007fcac86a45df in e2_check_adf () from /usr/lib/x86_64-linux-gnu/sane/libsane-epson2.so.1 #8 0x00007fcac86a467e in sane_epson2_start () from /usr/lib/x86_64-linux-gnu/sane/libsane-epson2.so.1 [...] #11 0x00007fcae9a94b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442 #12 0x00007fcae9b26a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Reported using DrKonqi
Created attachment 161068 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Pasting full text of the crashing thread for searchability: Thread 1 (Thread 0x7fcacaffd640 (LWP 62057)): [KCrash Handler] #6 0x00007fcac86a15d5 in esci_request_extended_status () from /usr/lib/x86_64-linux-gnu/sane/libsane-epson2.so.1 #7 0x00007fcac86a45df in e2_check_adf () from /usr/lib/x86_64-linux-gnu/sane/libsane-epson2.so.1 #8 0x00007fcac86a467e in sane_epson2_start () from /usr/lib/x86_64-linux-gnu/sane/libsane-epson2.so.1 #9 0x00007fcaeb78682c in ?? () from /lib/x86_64-linux-gnu/libKSaneCore.so.1 #10 0x00007fcaea2cebd3 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x00007fcae9a94b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442 #12 0x00007fcae9b26a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master (I don't even have an Epson scanner, just a Canon), and the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: > #9 0x00007fcaeb78682c in ?? () from /lib/x86_64-linux-gnu/libKSaneCore.so.1 > #10 0x00007fcaea2cebd3 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 Could you please install debug symbols for ksanecore, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports for details about how to do this. All that said, this may be a bug in the Epson drivers. But we need to rule out our code. Thanks again!
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!
(In reply to Nate Graham from comment #3) > Could you please install debug symbols for ksanecore, reproduce the crash, > and attach a new symbolicated backtrace? I tried, but now I cannot reproduce the error; I get an "Error during device I/O" instead. I might have updated a few packages in the meantime, but skanlite is still at 23.04.3 (-0xneon+22.04+jammy+release+build21, to be precise). I had also realized there was a "Reselect scanner device" button, and using that, I was able to switch to the other scanner (I mean same scanner with different name), which worked under skanlite as well. It caused other problems though (like the paper size dropdown being empty, Width, etc. becoming 0mm), but those are unrelated to this bug.
Ok, if you can't reproduce the crash, then without a prior backtrace with full debug symbols, I'm afraid there is no way for us to debug it. Feel free to open new bug reports about other issues, though.