Bug 502230

Summary:	Scanner not usable in skanpage (options are grayed out), skanlite, xsane are OK
Product:	[Applications] Skanpage	Reporter:	Sergio <sergio.callegari>
Component:	general	Assignee:	Alexander Stippich <a.stippich>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	john.kizer
Priority:	NOR
Version First Reported In:	24.12.3
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Sergio 2025-03-31 08:37:20 UTC

SUMMARY

I have a scanner that is detected via airscan (Brother MFC-L6900DW series). This device is unfortunately unusable with skanpage, even if it works just fine with skanlite and xsane.

The problem is that the scanner options cannot be configured, since they are all grayed out in skanpage.

STEPS TO REPRODUCE
1. Open skanpage
2. Select the airscan:e2:Brother MFC-L6900DW series scanner
3. Press configure visibility

OBSERVED RESULT

Options are all grayed out, cannot be configured

EXPECTED RESULT

Available options can be selected and configured.

SOFTWARE/OS VERSIONS

Operating System: Manjaro Linux 
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.12.20-2-MANJARO (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION

N/A

Comment 1 Alexander Stippich 2025-04-05 14:04:00 UTC

Hi, when you configure the visibility, you can click on them and add them to the options panel this way. When you click the "Configure Visibility" button again and disable that view, it shows up in the filtered options list. Alternatively, you can click "Show More" button to show all options.
The UI needs improvement, but I have not yet find the time and the right idea to do this.

Comment 2 John Kizer 2025-04-12 19:00:16 UTC

For the bug reporter here, could you please confirm if Alexander's guidance there addresses what was reported? Thanks!

Comment 3 Sergio 2025-04-13 07:08:51 UTC

Was not a matter of visibility, but a sort of a misbehavior with the interface, where the elements were present but inactive. Recently, it is not happening anymore, and I suspect the problem was with some system update on my side. I'll reopen if the issue resurfaces. So far, sorry for the noise.