Bug 495664 - Skanlite fails with message "opening the selected scanner failed"
Summary: Skanlite fails with message "opening the selected scanner failed"
Status: REPORTED
Alias: None
Product: Skanlite
Classification: Applications
Component: general (show other bugs)
Version: 22.12.3
Platform: Debian stable Linux
: NOR major
Target Milestone: ---
Assignee: Kåre Särs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-11-01 00:09 UTC by David Jarvie
Modified: 2024-11-01 16:03 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Jarvie 2024-11-01 00:09:34 UTC
Whenever I run skanlite, it reports that it has found my scanner (a Samsung Xpress M2885FW printer), but then immediately replaces that message with "opening the selected scanner failed". Clicking Ok then exits skanlite. XSane works successfully, however.

This failure only occurs on my laptop, whereas on my desktop it works ok, despite both computers having Debian Stable installed (both of which have all the latest updates installed). I normally have a firewall running, but even when I disabled the firewall, the error still occurred.

I ran skanlite with SANE debugging enabled, using the command
    SANE_DEBUG_AIRSCAN=5 skanlite

The debug output is shown under ADDITIONAL INFORMATION below.


SOFTWARE/OS VERSIONS
Linux: Debian 12 Bookworm,
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Skanlite version: 22.12.3


ADDITIONAL INFORMATION

API: sane_init(): called
loading configuration file /etc/sane.d/airscan.conf
MDNS: AVAHI_CLIENT_S_RUNNING
WSDD: netif addresses update:
WSDD:  + 192.168.178.103
WSDD:  + fe80::922e:7e49:129:b671%3
WSDD: 192.168.178.103: started discovery, UDP port=43129
WSDD: fe80::922e:7e49:129:b671: started discovery, UDP port=54611
WSDD: send_probe: Operation not permitted
API: sane_get_devices(): called
zeroconf: zeroconf_device_list_get: requested
zeroconf: device_list wait: requested
zeroconf: device_list wait: DNS-SD not finished...
MDNS: browse-ipv4("_ipp._tcp"): AVAHI_BROWSER_NEW
MDNS: browse-ipv4("_ipp._tcp"): "Samsung M288x Series (SEC30CDA7C60A29)"
MDNS: browse-ipv6("_ipp._tcp"): AVAHI_BROWSER_CACHE_EXHAUSTED
MDNS: browse-ipv6("_ipp._tcp"): AVAHI_BROWSER_ALL_FOR_NOW
MDNS: browse-ipv6("_ipps._tcp"): AVAHI_BROWSER_CACHE_EXHAUSTED
MDNS: browse-ipv6("_ipps._tcp"): AVAHI_BROWSER_ALL_FOR_NOW
MDNS: browse-ipv6("_uscan._tcp"): AVAHI_BROWSER_CACHE_EXHAUSTED
MDNS: browse-ipv6("_uscans._tcp"): AVAHI_BROWSER_CACHE_EXHAUSTED
MDNS: browse-ipv4("_scanner._tcp"): AVAHI_BROWSER_NEW
MDNS: browse-ipv4("_scanner._tcp"): "Samsung M288x Series (SEC30CDA7C60A29)"
MDNS: browse-ipv6("_scanner._tcp"): AVAHI_BROWSER_CACHE_EXHAUSTED
MDNS: browse-ipv6("_scanner._tcp"): AVAHI_BROWSER_ALL_FOR_NOW
MDNS: resolve-ipv4("_scanner._tcp", "Samsung M288x Series (SEC30CDA7C60A29)"): AVAHI_RESOLVER_FOUND
MDNS: resolve-ipv4("_scanner._tcp", "Samsung M288x Series (SEC30CDA7C60A29)"): 192.168.178.90:9400
WSDD: directed probe: trying if=wlp0s20f3, addr=192.168.178.90
WSDD: HTTP POST http://192.168.178.90/StableWSDiscoveryEndpoint/schemas-xmlsoap-org_ws_2005_04_discovery
WSDD: HTTP resolving 192.168.178.90 80
WSDD: HTTP trying 192.168.178.90:80
WSDD: HTTP fdpoll: {--} -> {-w}
WSDD: HTTP 805 bytes sent
WSDD: HTTP done request sending
WSDD: HTTP fdpoll: {-w} -> {rw}
WSDD: HTTP fdpoll: {rw} -> {r-}
WSDD: send_probe: Operation not permitted
WSDD: HTTP 1499 bytes received
WSDD: HTTP POST http://192.168.178.90/StableWSDiscoveryEndpoint/schemas-xmlsoap-org_ws_2005_04_discovery: got response headers (200)
WSDD: HTTP done response reception
WSDD: HTTP POST http://192.168.178.90/StableWSDiscoveryEndpoint/schemas-xmlsoap-org_ws_2005_04_discovery: 200 OK
WSDD: HTTP POST http://192.168.178.90/StableWSDiscoveryEndpoint/schemas-xmlsoap-org_ws_2005_04_discovery: OK
WSDD: HTTP POST http://192.168.178.90:8018/wsd
WSDD: HTTP resolving 192.168.178.90 8018
WSDD: HTTP trying 192.168.178.90:8018
WSDD: HTTP fdpoll: {--} -> {-w}
WSDD: HTTP 675 bytes sent
WSDD: HTTP done request sending
WSDD: HTTP fdpoll: {-w} -> {rw}
WSDD: HTTP fdpoll: {rw} -> {r-}
WSDD: HTTP 3218 bytes received
WSDD: HTTP POST http://192.168.178.90:8018/wsd: got response headers (200)
WSDD: HTTP done response reception
WSDD: HTTP POST http://192.168.178.90:8018/wsd: 200 OK
WSDD: HTTP POST http://192.168.178.90:8018/wsd: OK
zeroconf: found urn:uuid:16a65700-007c-1000-bb49-30cda7c60a29
zeroconf:   method:    ZEROCONF_WSD
zeroconf:   interface: 3 (wlp0s20f3)
zeroconf:   name:      -
zeroconf:   model:     Samsung Electronics Co., Ltd. M288x Series
zeroconf:   addresses:
zeroconf:     192.168.178.90
zeroconf:   protocol:  WSD
zeroconf:   endpoints:
zeroconf:     http://192.168.178.90:8018/wsd/scan
zeroconf:   device:    0000 (created)
zeroconf: device_list wait: DNS-SD not finished...
WSDD: send_probe: Operation not permitted
WSDD: send_probe: Operation not permitted
WSDD: send_probe: Operation not permitted
WSDD: send_probe: Operation not permitted
MDNS: browse-ipv6("_uscan._tcp"): AVAHI_BROWSER_ALL_FOR_NOW
zeroconf: ZEROCONF_USCAN_TCP: initial scan finished
MDNS: browse-ipv6("_uscans._tcp"): AVAHI_BROWSER_ALL_FOR_NOW
zeroconf: ZEROCONF_USCANS_TCP: initial scan finished
zeroconf: device_list wait: DNS-SD not finished...
WSDD: send_probe: Operation not permitted
WSDD: send_probe: Operation not permitted
WSDD: send_probe: Operation not permitted
WSDD: send_probe: Operation not permitted
WSDD: send_probe: Operation not permitted
WSDD: send_probe: Operation not permitted
WSDD: send_probe: Operation not permitted
WSDD: 192.168.178.103: done discovery
WSDD: fe80::922e:7e49:129:b671: done discovery
zeroconf: ZEROCONF_WSD: initial scan finished
zeroconf: device_list wait: DNS-SD not finished...
zeroconf: initial scan timer expired
zeroconf: device_list wait: DNS-SD not finished...
zeroconf: device_list wait: timeout
zeroconf: zeroconf_device_list_get: building list of devices
zeroconf: Samsung Electronics Co., Ltd. M288x Series (0): can: WSD, use: WSD
zeroconf: zeroconf_device_list_get: resulting list:
zeroconf:   WSD   "w0:Samsung Electronics Co., Ltd. M288x Series"
API: sane_get_devices(): done
MDNS: resolve-ipv4("_ipp._tcp", "Samsung M288x Series (SEC30CDA7C60A29)"): AVAHI_RESOLVER_FAILURE
MDNS: resolve-ipv4("_ipp._tcp", "Samsung M288x Series (SEC30CDA7C60A29)"): Timeout reached
zeroconf: ZEROCONF_MDNS_HINT: initial scan finished
zeroconf: found urn:uuid:05de2c50-c767-6f91-5d11-18223aaa6589
zeroconf:   method:    ZEROCONF_MDNS_HINT
zeroconf:   interface: 3 (wlp0s20f3)
zeroconf:   name:      Samsung M288x Series (SEC30CDA7C60A29)
zeroconf:   model:     Samsung M288x Series
zeroconf:   addresses:
zeroconf:     192.168.178.90
zeroconf:   device:    0001 (created)
API: sane_open("w0:Samsung Electronics Co., Ltd. M288x Series"): called
zeroconf: device_list wait: requested
zeroconf: device_list wait: OK
device_open(w0:Samsung Electronics Co., Ltd. M288x Series): device not found
API: sane_open("w0:Samsung Electronics Co., Ltd. M288x Series"): Invalid argument
Comment 1 Kåre Särs 2024-11-01 14:59:24 UTC
Thanks for the report!

I wonder if this has something to do with trying to restore the previous settings on startup.

Can you try to rename or delete your Skanlite config file ~/.local/share/skanlite/skanlitestaterc
Comment 2 David Jarvie 2024-11-01 16:03:44 UTC
The config file doesn't exist on the laptop. I did a 'find' for any file whose name starts with skanlite, in both ~/.local and ~/.config, and no results were found.

I did find the config file on my desktop computer, and after copying it across to the laptop, skanlite works successfully.

~/.local/share has the same access permissions on both the desktop and laptop ('ls' reports drwx-------, with the correct file owner), so there's no obvious reason why skanlite wouldn't have been able to create the config file if it had tried to.