Bug 1221512

Summary:	scanner MFC-J5620DW not anymore recognized by xsane or YaST2
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Willy Weisz <Willy.Weisz>
Component:	Other	Assignee:	Richard Rahl <rrahl0>
Status:	NEW ---	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	tiwai, Willy.Weisz
Version:	Current
Target Milestone:	---
Hardware:	x86-64
OS:	Linux
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Willy Weisz 2024-03-17 07:46:05 UTC

Since the last upgrade of Tumbleweed (including kernel 6.7.7) Xsane doesn't find my Brother MFC-J5620DW. Also YaST2 doesn't find it.
Up to the previous level of Tumbleweed the scanner connected via WiFi worked fine with the Brother-provided driver (brscan4-0.4.4-4.x86_64).

The printer part of the 4-in-1 MFC-J5620DW works as before.

What's the problem?

Comment 1 David Walker 2024-05-21 01:05:16 UTC

I'm having the same problem on Tumbleweed 20240512, aarch64. airscan-discover does find it however:

 > airscan-discover
 [devices]
   Canon MF650C Series = http://192.168.1.130:80/eSCL/, eSCL
   Canon MF650C Series = http://192.168.1.130/active/msu/scan, WSD

> sudo zypper se --details --installed-only sane
Loading repository data...
Reading installed packages...

S  | Name                     | Type    | Version     | Arch    | Repository
---+--------------------------+---------+-------------+---------+------------------------
i  | libsane1                 | package | 1.3.0-1.1   | aarch64 | openSUSE-Tumbleweed-Oss
i+ | sane-airscan             | package | 0.99.29-1.1 | aarch64 | openSUSE-Tumbleweed-Oss
i  | sane-backends            | package | 1.3.0-1.1   | aarch64 | openSUSE-Tumbleweed-Oss
i  | sane-backends-autoconfig | package | 1.3.0-1.1   | noarch  | openSUSE-Tumbleweed-Oss
i+ | xsane                    | package | 0.999-4.3   | aarch64 | openSUSE-Tumbleweed-Oss

Comment 2 Takashi Iwai 2024-05-21 06:37:11 UTC

Is it really a kernel regression?  If so, booting the previous kernel (before the problem appeared) should work.  If the problem persists with the old kernels, it's an issue rather in user-space.

Comment 3 David Walker 2024-05-22 22:35:54 UTC

Good question. I don't do a lot of scanning, so I don't remember the last time I could scan successfully, but I tried kernels 6.8.7-1-default and 6.8.4-rc1-1-default, and both had the same problem.

So, I did a little searching and found that there is a sane-airscan-unstable in home:pzz. I installed it, and scanning works again.

Can this report be reassigned to get the version of sane-airscan in Tumbleweed updated? Also, there's no aarch64 build, and I normally do my scanning from a Raspberry Pi 4 system, so aarch64 would be greatly appreciated. (I can report either or both of these separately, if that's better.)

Comment 4 Takashi Iwai 2024-05-23 06:00:11 UTC

At best ping on OBS or ask via mail.  Unfortunately the package maintainer of sane-airscan doesn't seem registered on Bugzilla, so we can't assign it to him.

I noticed, though, that sane-airscan package seems pretty new.  Didn't the system work after you uninstall that package?

Comment 5 David Walker 2024-05-23 19:40:41 UTC

Thanks. I'll contact him directly.

I believe xsane works correctly with or without sane-airscan, but doesn't support my scanner without it. Rereading the original post here, I see that my issue is likely different from Willy Weisz's, since he is using a vendor-provided driver, whereas I use the "driverless" airscan driver for sane.  (The wi-fi commonality threw me off.)

I don't know what changed in sane-airscan-unstable to make it work, but if it's due to some change in sane or elsewhere in the system, I suppose the Brother driver could have been similarly affected.

Comment 6 David Walker 2024-05-25 21:35:38 UTC

FYI, it turns out my issue was a missing dependency for libsane-airscan1. I have reported that in Bug #1225289, as it's not the same problem as reported originally here.