Simple-scan finds the above scanner device but scanning a document fails with the result below.
>simple-scan escl:https://192.168.178.5:443
(simple-scan:10101): Gdk-WARNING **: 10:09:18.403: Vulkan: ../src/amd/vulkan/radv_physical_device.c:2212: Device '/dev/dri/renderD128' is not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)
Tumbleweed release version is 20251205-3834.1
What can I do to correct this?
The Vulkan message is only a warning - likely due to having an older AMD graphics chipset and using the radeon driver perhaps. Post the results from inxi -GSaz for more information about that.
The real issue is the scanner not being detected. Is the sane-airscan package installed?
The scanner is indeed detected after starting the Gnome Document Scanner. However a scan operation fails.
sane-airscan 0.99.36-1.2 is installed. It was all working perfectly until now.
~> inxi -GSaz
System:
Kernel: 6.18.0-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.18.0-1-default
root=UUID=ce70a4cb-918a-4971-a283-3500612754a9 splash=silent
mitigations=auto quiet security=selinux selinux=1 enforcing=1
Desktop: GNOME v: 49.2 tk: GTK v: 3.24.51 wm: gnome-shell
tools: gsd-screensaver-proxy avail: xscreensaver dm: GDM v: 49.2
Distro: openSUSE Tumbleweed 20251205
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Caicos [Radeon HD 6450/7450/8450
/ R5 230 OEM] vendor: PC Partner / Sapphire driver: radeon v: kernel
alternate: amdgpu arch: TeraScale-2 code: Evergreen process: TSMC 32-40nm
built: 2009-15 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports:
active: DVI-D-1,HDMI-A-1 empty: VGA-1 bus-ID: 01:00.0 chip-ID: 1002:6779
class-ID: 0300 temp: 56.5 C
Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.8
compositor: gnome-shell driver: X: loaded: modesetting unloaded: vesa
alternate: fbdev dri: r600 gpu: radeon display-ID: 0
Monitor-1: DVI-D-1 model: AOC 2243W serial: <filter> built: 2010
res: 1920x1080 dpi: 102 gamma: 1.2 size: 477x268mm (18.78x10.55")
diag: 547mm (21.5") ratio: 16:9 modes: max: 1920x1080 min: 720x400
Monitor-2: HDMI-A-1 model: Lenovo L24e-30 serial: <filter> built: 2022
res: 1920x1080 dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65")
diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 vendor: mesa v: 25.3.1 glx-v: 1.4 es-v: 3.1
direct-render: yes renderer: AMD CAICOS (DRM 2.51.0 / 6.18.0-1-default LLVM
21.1.6) device-ID: 1002:6779 memory: 1000 MiB unified: no display-ID: :0.0
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo x11: xprop,xrandr
Ok, a graphics issue then? Any other GTK apps not working currently?
Try forcing software rendering…
LIBGL_ALWAYS_SOFTWARE=1 simple-scan
Does that work ok?
Detects the scanner on opening, but fails to scan
~> LIBGL_ALWAYS_SOFTWARE=1 simple-scan
(simple-scan:52621): Gdk-WARNING **: 19:33:53.454: Vulkan: ../src/amd/vulkan/radv_physical_device.c:2212: Device '/dev/dri/renderD128' is not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)
Yes, but now we’re trying to work on the underlying graphics issue. 
What about:
simple-scan -d
A lot of DEBUG output. What should I look for?
…all good sane messages, then toward the end
[+22.68s] DEBUG: simple-scan.vala:1677: Unable to find colord device airscan:e0:Canon GX6000 series: property match 'Serial'='sane:airscan:e0:Canon GX6000 series' does not exist
you can copy/paste it to
https://paste.opensuse.org/
But please change the remove in the right downside to 3 month.
…also changing the header box details to match this post?
…my bad…very sorry.
That works, especially when I select the right scan source 
…but only once from the flat bed and not from the feeder and then no more again.
On an openSUSE Leap 16 install running in a VM, I too must use the LIBGL_ALWAYS_SOFTWARE=1 environment variable (inserted in the KDE menu entry for simple-scan)…
I don’t have the same “one shot” issue as you describe though. I can perform a scanning job (single or multi-page), save it and undertake a subsequent scanning job without issue.
Is a restart of the application enough to get the next scanning job completed? Does power-cycling the scanner also achieve the same?
Something to try:
Run
scanimage --format=png > test1.png
then do a second scan
scanimage --format=png > test2.png
If the second scan fails, the issue is the backend (sane-airscan) and not specifically with simple-scan.
If you want to specify the scanner, you can use
scanimage --device-name "escl:https://192.168.178.5:443" --format=png > test.png instead.
After reboot of PC and scanner/printer off
test1: scanner triggered on, and scans, but fails with
scanimage: sane_read: Error during device I/O
Exactly same result with test2.
Both png files are saved on the PC, but cannot be read showing
Remote error: org.gnome.glycin.Error.LoadingError: glycin-loaders/glycin-image-rs/src/main.rs:319:52: unexpected end of file
stderr:
Setting process memory limit
Otherwise, generally ‘flaky’ (i.e. seemingly unrepeatable) behaviour.
Meaning e.g. no response from scanner on test1 after very first cold start (from PC bootup and scanner powered off, but successful test2, (i.e. triggered scanner on, and scanned) with readable file.
After the two above tests Document Scanner produced a good scan (pdf), and a new scanimage png test3 thereafter was successful.
So working consistently now?
…not consistently, flakily, i.e. unpredictably.
Should the environment variable
LIBGL_ALWAYS_SOFTWARE=1
be set permanently? Where? Syntax?
For Gnome, create the file ~/.config/environment.d/90-software-rendering.conf (or similar) containing LIBGL_ALWAYS_SOFTWARE=1, save when done, then logout and back in again. It should take effect for graphical apps that require software rendering on your system.
In my home directory? There already exists a renderer .conf file
dleyna-renderer-service.conf
but no `environment.d` folder
Or what do you mean by 'or similar'?