Hi.
On 2023-04-01 10:09, Marco wrote:
Am 01.04.2023 um 09:43:15 Uhr schrieb Ralph Little:
Could you let us see the output of the diag from the xerox_mfp
backend?
SANE_DEBUG_XEROX_MFP=4 ...
See the attachment.
I'm seeing a different error from what you reported before. I don't see
Thanks to the wizards who helped me on this problem.
I'm happy to report that scanning is now working with the Canon GX6050
using scangearmp2-4.40 as recommended together with suggested firewall
adjustments. It took a bit longer than I had hoped because I was
juggling with kernel updates in
Am 01.04.2023 um 09:43:15 Uhr schrieb Ralph Little:
> Could you let us see the output of the diag from the xerox_mfp
> backend?
>
> SANE_DEBUG_XEROX_MFP=4 ...
See the attachment.
samsung-xerox_debug
Description: Binary data
Hi,
On 2023-04-01 08:09, Marco wrote:
Am 01.04.2023 um 17:04:12 Uhr schrieb jitesh pandey:
Please provide the output for the command
*export SANE_DEBUG_DLL=255; SANE_DEBUG_SANEI_USB=255;
SANE_DEBUG_XEROX_MFP=4; scanimage -L*
as it will give some insight
See the attachment.
The problem
Am 01.04.2023 um 17:04:12 Uhr schrieb jitesh pandey:
> Please provide the output for the command
>
> *export SANE_DEBUG_DLL=255; SANE_DEBUG_SANEI_USB=255;
> SANE_DEBUG_XEROX_MFP=4; scanimage -L*
>
> as it will give some insight
See the attachment.
samsung
Description: Binary data
Am 25.03.2023 um 14:15:33 Uhr schrieb Marco:
> Does anybody know the reason for that?
I have now verified that the hardware works fine in Windows 10.
