Ubuntu 21.04 with a Lexmark CX317dn, which includes a scanner, quits unexpectedly
The title contains already my setup - x.org instead of wayland - when I run
simple-scan --debug
and click on scan when my scanner is found a white image appears for one second and simple scan is closed. In the terminal I have then the following output:
[+0,00s] DEBUG: simple-scan.vala:2012: Starting simple-scan 3.38.1, PID=4544
[+0,01s] DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
[+0,05s] DEBUG: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
[+0,13s] DEBUG: app-window.vala:1990: Loading state from /home/hl/.cache/simple-scan/state
[+0,13s] DEBUG: app-window.vala:1969: Restoring window to 600x400 pixels
[+0,13s] DEBUG: app-window.vala:1973: Restoring window to maximized
[+0,20s] DEBUG: scanner.vala:1548: sane_init () -> SANE_STATUS_GOOD
[+0,20s] DEBUG: scanner.vala:1554: SANE version 1.0.32
[+0,20s] DEBUG: scanner.vala:1615: Requesting redetection of scan devices
[+0,20s] DEBUG: scanner.vala:828: Processing request
[+0,32s] DEBUG: app-window.vala:2065: Saving state to /home/hl/.cache/simple-scan/state
[+7,05s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+7,05s] DEBUG: scanner.vala:353: Device: name="lexmark_nscan:libusb/001/005" vendor="Lexmark" model="Lexmark CX317dn" type="Scanner"
[+9,05s] DEBUG: simple-scan.vala:1817: Requesting scan at 300 dpi from device 'lexmark_nscan:libusb/001/005'
[+9,05s] DEBUG: scanner.vala:1683: Scanner.scan ("lexmark_nscan:libusb/001/005", dpi=300, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0, paper_height=0, brightness=0, contrast=0, delay=3000ms)
[+9,05s] DEBUG: scanner.vala:828: Processing request
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not valid
Aborted (core dumped)
the same error at the bottom appears with other scanning programs too. Simple-scan is by far my favourite, that is why I post it here. Can it be that some underlying package or driver is corrupted? The error message is very brief from C or C++ I guess, but without any source.
Edited by Manuel T. Schrempf