SUMMARY Skanlite randomly detects scanner dimensions as 14 metres wide upon initialization, and necessitates a reinitialization to remediate it. STEPS TO REPRODUCE 1. Install cpe:/o:opensuse:tumbleweed:20240320. 2. Install https://download.opensuse.org/repositories/openSUSE:/Factory/standard/x86_64/epson-inkjet-printer-escpr-1.7.22-2.1.x86_64.rpm. 3. Install https://download.opensuse.org/repositories/openSUSE:/Factory/standard/x86_64/skanlite-24.02.0-1.1.x86_64.rpm. 4. Connect the scanner. 5. Confirm it is listed as connected in kcm_printer_manager. 6. Invoke "gdb skanlite" with debuginfod enabled. OBSERVED RESULT https://discuss-cdn.kde.org/uploads/default/original/2X/7/7a1d2a0d17e4484469b97ab1a3f03a2e1668e4a6.png EXPECTED RESULT It should always detect the correct dimensions of my scanner. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240320 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: ASRock Product Name: X670E Taichi ADDITIONAL INFORMATION * I use an EPSON Expression Home XP-247, and used to experience the same on my previous 245. * I've set the https://bugs.kde.org/page.cgi?id=fields.html#bug_severity to “normal” because this *necessitates* reinitialization of Skanlite to remediate, which is unintuitive.
(In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #0) Sorry, not “[approximately] 14 metres” — specifically, 16557 mm.
Thanks for the report. This looks like a backend issue, possibly caused by trying to restore settings from the previous session... Can you try to run Skanlite with debug logging enabled for the epson2 backend? The command to run in a terminal would be something like: SANE_DEBUG_EPSON2=16 skanlite And maybe play with the number a bit to see what gives a reasonable output, the values go from 1 to 128 and 128 returns all possible debug output... Then attach the output here, Thanks in advance, Kåre
Created attachment 167902 [details] Depiction of the problem. https://discuss-cdn.kde.org/uploads/default/original/2X/7/7a1d2a0d17e4484469b97ab1a3f03a2e1668e4a6.png
(In reply to Kåre Särs from comment #2) So I've tried that, and quite unexpectedly discovered both https://bugs.kde.org/show_bug.cgi?id=484675#c0 and https://bugs.kde.org/show_bug.cgi?id=484678#c0 during the course of it. However, I've not been able to reproduce *this* on my new Fedora 40 installation (yet?).
(In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #4) I thought it could be because I was using a combination of different locales for different things, but switching a few to C hasn't worked. I think I'll close this until it occurs again, but I'll ensure that I run Skanlite with the debugger from here onward in case it does again.