Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #230454 > unrolled thread

simple-scan fails with Canon LiDE 300--except as root

Back to article view | Back to linux.debian.user

Contents

  simple-scan fails with Canon LiDE 300--except as root Jen Nussbaum <bg271828@yahoo.com> - 2021-01-08 23:50 +0100
    Re: simple-scan fails with Canon LiDE 300--except as root ghe2001 <ghe2001@protonmail.com> - 2021-01-09 00:30 +0100
      Vim fails with some unspecified out-of-memory error [was: Re:  simple-scan fails with Canon LiDE 300--except as root] Andrei POPESCU <andreimpopescu@gmail.com> - 2021-01-09 07:50 +0100
    Re: simple-scan fails with Canon LiDE 300--except as root Brian <ad44@cityscape.co.uk> - 2021-01-09 01:10 +0100
      Re: simple-scan fails with Canon LiDE 300--except as root "Dr. Jennifer Nussbaum" <bg271828@yahoo.com> - 2021-01-09 05:00 +0100
        Re: simple-scan fails with Canon LiDE 300--except as root Brian <ad44@cityscape.co.uk> - 2021-01-09 13:20 +0100
          Re: simple-scan fails with Canon LiDE 300--except as root "Dr. Jennifer Nussbaum" <bg271828@yahoo.com> - 2021-01-09 13:40 +0100
            Re: simple-scan fails with Canon LiDE 300--except as root Brian <ad44@cityscape.co.uk> - 2021-01-09 13:50 +0100
              Re: simple-scan fails with Canon LiDE 300--except as root "Dr. Jennifer Nussbaum" <bg271828@yahoo.com> - 2021-01-09 14:00 +0100
                Re: simple-scan fails with Canon LiDE 300--except as root Brian <ad44@cityscape.co.uk> - 2021-01-09 14:10 +0100
                  Re: simple-scan fails with Canon LiDE 300--except as root "Dr. Jennifer Nussbaum" <bg271828@yahoo.com> - 2021-01-09 14:30 +0100
                    Re: simple-scan fails with Canon LiDE 300--except as root Brian <ad44@cityscape.co.uk> - 2021-01-09 14:50 +0100
                      Re: simple-scan fails with Canon LiDE 300--except as root Brian <ad44@cityscape.co.uk> - 2021-01-09 15:20 +0100

#230454 — simple-scan fails with Canon LiDE 300--except as root

After using a rather old Canon scanner for many years, I recently upgraded to the Canon LiDE 300, and installed the drivers as directed, on a Bullseye system (10.2.0-17).

The printer is recognized:

$ scanimage -L
device `pixma:04A91913_47A8A4' is a CANON CanoScan LiDE 300 multi-function peripheral
device `escl:http://127.0.0.1:60000' is a Canon LiDE 300 (USB) flatbed scanner

When I run simple-scan, it detects the printer and announces itself ready to go, but when I try to scan anything, I get the message "Failed to scan Unable to connect to scanner". I Googled for anything related to this; there's a bunch of stuff on Ubuntu and Mint forums about purging the "ippusbxd" package, but this isn't on Debian.

I then ran simple-scan with the debug flag, and at the moment I try to initiate a scan, I got:

[+20.83s] DEBUG: simple-scan.vala:1817: Requesting scan at 150 dpi from device 'escl:http://127.0.0.1:60000'
[+20.83s] DEBUG: scanner.vala:1683: Scanner.scan ("escl:http://127.0.0.1:60000", dpi=150, scan_mode=ScanMode.GRAY, depth=2, type=single, paper_width=0, paper_height=0, brightness=0, contrast=0, delay=3000ms)
[+20.83s] DEBUG: scanner.vala:828: Processing request
[+20.83s] DEBUG: scanner.vala:889: sane_open ("escl:http://127.0.0.1:60000") -> SANE_STATUS_NO_MEM
[+20.83s] WARNING: scanner.vala:893: Unable to open device: Out of memory


I'm not sure what could be going on, as I have a ton of memory on my system.

I don't know why I tried this, but I then ran simple-scan as root, and...it worked perfectly.

I'm bewildered by this--any idea what I should be looking at?

[toc] | [next] | [standalone]

#230457

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, January 8, 2021 10:28 PM, Jen Nussbaum <bg271828@yahoo.com> wrote:

> I don't know why I tried this, but I then ran simple-scan as root, and...it worked perfectly.

I had a similar problem with vim -- I have no idea what was wrong.  I fixed it with a line in .bashrc: alias vi="sudo vi" (I was already in /etc/sudoers with a no password login).

Not the most elegant solution, but it saved a lot of time, and it works...

--
Glenn English
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJf+OjNACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDKpoAgAn6FUbE4JjUwBQdtPLBjcW/uaylna8B/OzLIiMNf7okVs0ExH
uutXA5d9gXp/0woFHyD/bCnkCaFAJQd8HzXzUzS7i4vnqYonh8VCsiJLMD8+
2tL/dRPNSAFlzXWB3SFleGxUnwFUETeBo9v3cJkfVjUSGcE6+cWx1xLZPVAa
TjP2khdYCQTwCQ1gcTCkSGOmFY8yehM/swuHJBL5eiGSlRTcZ/XHHE89nhys
G0ssWy+zgmazb0A/SWsThGStHcWh9gRdpSI5/EUuK3aX/661WEdQKcdUbIVM
NSENL87rvqDK83UjDFt+3Qy6RtzlJIFvRyC3nOxs+84KPzmeiTM8JQ==
=zJwX
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#230467 — Vim fails with some unspecified out-of-memory error [was: Re: simple-scan fails with Canon LiDE 300--except as root]

[Multipart message — attachments visible in raw view] — view raw

On Vi, 08 ian 21, 23:20:46, ghe2001 wrote:
> 
> 
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Friday, January 8, 2021 10:28 PM, Jen Nussbaum <bg271828@yahoo.com> wrote:
> 
> > I don't know why I tried this, but I then ran simple-scan as root, and...it worked perfectly.
> 
> I had a similar problem with vim -- I have no idea what was wrong.  I 
> fixed it with a line in .bashrc: alias vi="sudo vi" (I was already in 
> /etc/sudoers with a no password login).
 
This is most likely completely unrelated.

> Not the most elegant solution, but it saved a lot of time, and it works...

The fix probably works simply because you are running vi(m) as a 
different user and consequently with a different configuration.

You can easily confirm this either by running vim as a different 
*regular* user, or just moving your ~/.vimrc and ~/.vim/ out of the way.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#230459

On Fri 08 Jan 2021 at 17:28:16 -0500, Jen Nussbaum wrote:

> 
> After using a rather old Canon scanner for many years, I recently
> upgraded to the Canon LiDE 300, and installed the drivers as directed,
> on a Bullseye system (10.2.0-17).
> 
> The printer is recognized:
> 
> $ scanimage -L
> device `pixma:04A91913_47A8A4' is a CANON CanoScan LiDE 300 multi-function peripheral
> device `escl:http://127.0.0.1:60000' is a Canon LiDE 300 (USB) flatbed scanner
> 
> When I run simple-scan, it detects the printer and announces itself
> ready to go, but when I try to scan anything, I get the message
> "Failed to scan Unable to connect to scanner". I Googled for anything
> related to this; there's a bunch of stuff on Ubuntu and Mint forums
> about purging the "ippusbxd" package, but this isn't on Debian.

ippusbxd is certainly not on Debian but ipp-usb is. See the wiki.

> I then ran simple-scan with the debug flag, and at the moment I try to
> initiate a scan, I got:
> 
> [+20.83s] DEBUG: simple-scan.vala:1817: Requesting scan at 150 dpi from device 'escl:http://127.0.0.1:60000'
> [+20.83s] DEBUG: scanner.vala:1683: Scanner.scan ("escl:http://127.0.0.1:60000", dpi=150, scan_mode=ScanMode.GRAY, depth=2, type=single, paper_width=0, paper_height=0, brightness=0, contrast=0, delay=3000ms)
> [+20.83s] DEBUG: scanner.vala:828: Processing request
> [+20.83s] DEBUG: scanner.vala:889: sane_open ("escl:http://127.0.0.1:60000") -> SANE_STATUS_NO_MEM
> [+20.83s] WARNING: scanner.vala:893: Unable to open device: Out of memory

Nothing about the pixma backend (driver)?

> I'm not sure what could be going on, as I have a ton of memory on my
> system.

Just to confirm your experience, what happens with scanning with

  simple-scan "pixma:04A91913_47A8A4"

and

  simple-scan "escl:http://127.0.0.1:60000"

> I don't know why I tried this, but I then ran simple-scan as root,
> and...it worked perfectly.

I do not understand why this should be so. Do both the previous commands
work as root?

> I'm bewildered by this--any idea what I should be looking at?

Yes; there is a possible solution. Give what you get for

  lsusb -v | grep -A 3 bInterfaceClass.*7

and

  systemctl list-units "ipp-usb*" | grep service

-- 
Brian. 

[toc] | [prev] | [next] | [standalone]

#230462

[Multipart message — attachments visible in raw view] — view raw

 Just to clarify what someone else in the thread asked about, the user I'm running this under _does_ appear in the scanner group.
    On Friday, January 8, 2021, 07:07:40 PM EST, Brian <ad44@cityscape.co.uk> wrote: 
 On Fri 08 Jan 2021 at 17:28:16 -0500, Jen Nussbaum wrote:

>> When I run simple-scan, it detects the printer and announces itself
>> ready to go, but when I try to scan anything, I get the message
>> "Failed to scan Unable to connect to scanner". I Googled for anything
>> related to this; there's a bunch of stuff on Ubuntu and Mint forums
>> about purging the "ippusbxd" package, but this isn't on Debian.
>
> ippusbxd is certainly not on Debian but ipp-usb is. See the wiki.

Yes, and I do have that; the point was just that the solution that worked onMint (to remove ippusbxd and install ipp-usb) isn't relevant here.
>> I then ran simple-scan with the debug flag, and at the moment I try to
>> initiate a scan, I got:
>> 
>> [+20.83s] DEBUG: simple-scan.vala:1817: Requesting scan at 150 dpi from device 'escl:http://127.0.0.1:60000'
>> [+20.83s] DEBUG: scanner.vala:1683: Scanner.scan ("escl:http://127.0.0.1:60000", dpi=150, scan_mode=ScanMode.GRAY, depth=2, type=single, paper_width=0, paper_height=0, brightness=0, contrast=0, delay=3000ms)
>> [+20.83s] DEBUG: scanner.vala:828: Processing request
>> [+20.83s] DEBUG: scanner.vala:889: sane_open ("escl:http://127.0.0.1:60000") -> SANE_STATUS_NO_MEM
>> [+20.83s] WARNING: scanner.vala:893: Unable to open device: Out of memory
>
> Nothing about the pixma backend (driver)?

pixma only appears during the startup:
[+7.62s] DEBUG: scanner.vala:353: Device: name="pixma:04A91913_47A8A4" vendor="CANON" model="CanoScan LiDE 300" type="multi-function peripheral"

> Just to confirm your experience, what happens with scanning with
>
 > simple-scan "pixma:04A91913_47A8A4"

This fires up simple scan, and when I click on "scan" it scans the document successfully.

> and
>
> simple-scan "escl:http://127.0.0.1:60000"

This does _not_ work; the response here is the same as when I run it normally, i.e. the "Unable to contact scanner" error.

>> I don't know why I tried this, but I then ran simple-scan as root,
>> and...it worked perfectly.
>
> I do not understand why this should be so. Do both the previous commands
> work as root?

The "pixma" version worked as root, as it did as the regular user. Curiously, the "escl" version did not work as root,even though when I run simple-scan without any arguments, it did work as root.

> > I'm bewildered by this--any idea what I should be looking at?
>
> Yes; there is a possible solution. Give what you get for
>
> lsusb -v | grep -A 3 bInterfaceClass.*7

---$ lsusb -v | grep -A 3 bInterfaceClass.*7Couldn't open device, some information will be missing      bInterfaceClass         7 Printer      bInterfaceSubClass      1 Printer      bInterfaceProtocol      4       iInterface              0 can't get debug descriptor: Resource temporarily unavailableCouldn't open device, some information will be missingCouldn't open device, some information will be missing--      bInterfaceClass         7 Printer      bInterfaceSubClass      1 Printer      bInterfaceProtocol      4       iInterface              0 Couldn't open device, some information will be missingCouldn't open device, some information will be missingcan't get debug descriptor: Resource temporarily unavailableCouldn't open device, some information will be missing---
(The "Couldn't open device" line was repeated multiple times wherever it appeared;I deleted it here for brevity.)
> and
>
>  systemctl list-units "ipp-usb*" | grep service

---$ systemctl list-units "ipp-usb*" | grep service  ipp-usb.service loaded active running Daemon for IPP over USB printer support---
Thank you.
  

[toc] | [prev] | [next] | [standalone]

#230469

On Sat 09 Jan 2021 at 03:53:28 +0000, Dr. Jennifer Nussbaum wrote:

>  Just to clarify what someone else in the thread asked about, the user
>  I'm running this under _does_ appear in the scanner group.

For what you wish to achieve, being a member of the scanner group is
completely unnecessary. See

  https://wiki.debian.org/Scanner

>     On Friday, January 8, 2021, 07:07:40 PM EST, Brian <ad44@cityscape.co.uk> wrote: 
>  On Fri 08 Jan 2021 at 17:28:16 -0500, Jen Nussbaum wrote:
> 
> >> When I run simple-scan, it detects the printer and announces itself
> >> ready to go, but when I try to scan anything, I get the message
> >> "Failed to scan Unable to connect to scanner". I Googled for anything
> >> related to this; there's a bunch of stuff on Ubuntu and Mint forums
> >> about purging the "ippusbxd" package, but this isn't on Debian.
> >
> > ippusbxd is certainly not on Debian but ipp-usb is. See the wiki.
> 
> Yes, and I do have that; the point was just that the solution that
> worked onMint (to remove ippusbxd and install ipp-usb) isn't relevant
> here.

ipp-usb is relevant insofar as it enables the sane-escl and sane-airscan
backends to be used for scanning.

> >> I then ran simple-scan with the debug flag, and at the moment I try to
> >> initiate a scan, I got:
> >> 
> >> [+20.83s] DEBUG: simple-scan.vala:1817: Requesting scan at 150 dpi from device 'escl:http://127.0.0.1:60000'
> >> [+20.83s] DEBUG: scanner.vala:1683: Scanner.scan ("escl:http://127.0.0.1:60000", dpi=150, scan_mode=ScanMode.GRAY, depth=2, type=single, paper_width=0, paper_height=0, brightness=0, contrast=0, delay=3000ms)
> >> [+20.83s] DEBUG: scanner.vala:828: Processing request
> >> [+20.83s] DEBUG: scanner.vala:889: sane_open ("escl:http://127.0.0.1:60000") -> SANE_STATUS_NO_MEM
> >> [+20.83s] WARNING: scanner.vala:893: Unable to open device: Out of memory
> >
> > Nothing about the pixma backend (driver)?
> 
> pixma only appears during the startup:
> [+7.62s] DEBUG: scanner.vala:353: Device: name="pixma:04A91913_47A8A4"
> vendor="CANON" model="CanoScan LiDE 300" type="multi-function
> peripheral"
> 
> > Just to confirm your experience, what happens with scanning with
> >
>  > simple-scan "pixma:04A91913_47A8A4"
> 
> This fires up simple scan, and when I click on "scan" it scans the
> document successfully.

I would not expect this to hapen when ipp-usb is active, which it is.
See

  https://wiki.debian.org/CUPSDriverlessPrinting

> > and
> >
> > simple-scan "escl:http://127.0.0.1:60000"
> 
> This does _not_ work; the response here is the same as when I run it
> normally, i.e. the "Unable to contact scanner" error.

sane-escl is designed to work with an active ipp-usb. This may be a bug
in the backend.
 
> >> I don't know why I tried this, but I then ran simple-scan as root,
> >> and...it worked perfectly.
> >
> > I do not understand why this should be so. Do both the previous commands
> > work as root?
> 
> The "pixma" version worked as root, as it did as the regular user.
> Curiously, the "escl" version did not work as root,even though when I
> run simple-scan without any arguments, it did work as root.

At this site, neither simple-scan nor xsane opens a display when run as
root.

> > > I'm bewildered by this--any idea what I should be looking at?
> >
> > Yes; there is a possible solution. Give what you get for
> >
> > lsusb -v | grep -A 3 bInterfaceClass.*7
> 
> ---$ lsusb -v | grep -A 3 bInterfaceClass.*7Couldn't open device, some information will be missing      bInterfaceClass         7 Printer      bInterfaceSubClass      1 Printer      bInterfaceProtocol      4       iInterface              0 can't get debug descriptor: Resource temporarily unavailableCouldn't open device, some information will be missingCouldn't open device, some information will be missing--      bInterfaceClass         7 Printer      bInterfaceSubClass      1 Printer      bInterfaceProtocol      4       iInterface              0 Couldn't open device, some information will be missingCouldn't open device, some information will be missingcan't get debug descriptor: Resource temporarily unavailableCouldn't open device, some information will be missing---
> (The "Couldn't open device" line was repeated multiple times wherever
> it appeared;I deleted it here for brevity.)

"bInterfaceProtocol      4" indicates that the Canon LiDE 300
understands the IPP-over-USB protocol.

> > and
> >
> >  systemctl list-units "ipp-usb*" | grep service
> 
> ---$ systemctl list-units "ipp-usb*" | grep service  ipp-usb.service loaded active running Daemon for IPP over USB printer support---

Indicates that the IPP-over-USB protocol is being used.

Install sane-airscan and give

  scanimage -L

and

  airscan-discover

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#230471

[Multipart message — attachments visible in raw view] — view raw

 On Saturday, January 9, 2021, 07:19:39 AM EST, Brian <ad44@cityscape.co.uk> wrote:
 
 > Install sane-airscan and give
>
> scanimage -L
$ scanimage -Ldevice `pixma:04A91913_47A8A4' is a CANON CanoScan LiDE 300 multi-function peripheraldevice `escl:http://127.0.0.1:60000' is a Canon LiDE 300 (USB) flatbed scannerdevice `airscan:e0:Canon LiDE 300 (USB)' is a eSCL Canon LiDE 300 (USB) ip=127.0.0.1
> and
>
>  airscan-discover
$ airscan-discover [devices]  Canon LiDE 300 (USB) = http://127.0.0.1:60000/eSCL/, eSCL
When I try to run simple-scan now, it's the same result as before; debug shows the airscan, but I still get the out-of-memory error.
Thank you for sticking with this.  

[toc] | [prev] | [next] | [standalone]

#230472

On Sat 09 Jan 2021 at 12:31:43 +0000, Dr. Jennifer Nussbaum wrote:

>  On Saturday, January 9, 2021, 07:19:39 AM EST, Brian <ad44@cityscape.co.uk> wrote:
>  
>  > Install sane-airscan and give
> >
> > scanimage -L
> $ scanimage -Ldevice `pixma:04A91913_47A8A4' is a CANON CanoScan LiDE 300 multi-function peripheraldevice `escl:http://127.0.0.1:60000' is a Canon LiDE 300 (USB) flatbed scannerdevice `airscan:e0:Canon LiDE 300 (USB)' is a eSCL Canon LiDE 300 (USB) ip=127.0.0.1
> > and
> >
> >  airscan-discover
> $ airscan-discover [devices]  Canon LiDE 300 (USB) = http://127.0.0.1:60000/eSCL/, eSCL
> When I try to run simple-scan now, it's the same result as before; debug shows the airscan, but I still get the out-of-memory error.
> Thank you for sticking with this.

How do you go on with

  simple-scan "airscan:e0:Canon LiDE 300 (USB)" ?

Would you also try

  xsane "airscan:e0:Canon LiDE 300 (USB)"

and

  xsane ?

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#230473

[Multipart message — attachments visible in raw view] — view raw

 
   > On Saturday, January 9, 2021, 07:43:41 AM EST, Brian <ad44@cityscape.co.uk> wrote: > > On Sat 09 Jan 2021 at 12:31:43 +0000, Dr. Jennifer Nussbaum wrote:
>
> >  On Saturday, January 9, 2021, 07:19:39 AM EST, Brian <ad44@cityscape.co.uk> wrote:
>  >
>  > > Install sane-airscan and give
> > >
> > > scanimage -L
> > $ scanimage -L> > device `pixma:04A91913_47A8A4' is a CANON CanoScan LiDE 300 multi-function peripheraldevice `escl:http://127.0.0.1:60000' is a Canon LiDE 300 (USB) flatbed scannerdevice `airscan:e0:Canon LiDE 300 (USB)' is a eSCL Canon LiDE 300 (USB) ip=127.0.0.1
> > > and
> > >
> > > airscan-discover
> > $ airscan-discover > > [devices]  Canon LiDE 300 (USB) = http://127.0.0.1:60000/eSCL/, eSCL
> > When I try to run simple-scan now, it's the same result as before; debug shows the airscan, but I still get the out-of-memory error.
> > Thank you for sticking with this.
>
> How do you go on with
>
>  simple-scan "airscan:e0:Canon LiDE 300 (USB)" ?
This works. (As it did when we specified the "pixma" interface.)
> Would you also try
>
>  xsane "airscan:e0:Canon LiDE 300 (USB)">
> and
>
>  xsane ?
I don't have xsane installed. Is that just for background info? I've used it in the past, and always foundit far too complicated to bother with.  

[toc] | [prev] | [next] | [standalone]

#230474

On Sat 09 Jan 2021 at 12:55:07 +0000, Dr. Jennifer Nussbaum wrote:

>  
>    > On Saturday, January 9, 2021, 07:43:41 AM EST, Brian <ad44@cityscape.co.uk> wrote: > > On Sat 09 Jan 2021 at 12:31:43 +0000, Dr. Jennifer Nussbaum wrote:
> >
> > >  On Saturday, January 9, 2021, 07:19:39 AM EST, Brian <ad44@cityscape.co.uk> wrote:
> >  >
> >  > > Install sane-airscan and give
> > > >
> > > > scanimage -L
> > > $ scanimage -L> > device `pixma:04A91913_47A8A4' is a CANON CanoScan LiDE 300 multi-function peripheraldevice `escl:http://127.0.0.1:60000' is a Canon LiDE 300 (USB) flatbed scannerdevice `airscan:e0:Canon LiDE 300 (USB)' is a eSCL Canon LiDE 300 (USB) ip=127.0.0.1
> > > > and
> > > >
> > > > airscan-discover
> > > $ airscan-discover > > [devices]  Canon LiDE 300 (USB) = http://127.0.0.1:60000/eSCL/, eSCL
> > > When I try to run simple-scan now, it's the same result as before; debug shows the airscan, but I still get the out-of-memory error.
> > > Thank you for sticking with this.
> >
> > How do you go on with
> >
> >  simple-scan "airscan:e0:Canon LiDE 300 (USB)" ?
> This works. (As it did when we specified the "pixma" interface.)

Thanks. I still do not understand how the pixma backend can work.
ipp-usb has control of USB; pixma should be unable to access the USB
bus.

Can you scan by choosing airscan, eSCL (note the lower case e), from
simple-scan's drop-down menu.

> > Would you also try
> >
> >  xsane "airscan:e0:Canon LiDE 300 (USB)">
> > and
> >
> >  xsane ?
> I don't have xsane installed. Is that just for background info? I've
> used it in the past, and always foundit far too complicated to bother
> with.

You can always remove it afterwards, but I wanted to know which of
the options it offers work. A preview is enough to do.

-- 
Brian. 

[toc] | [prev] | [next] | [standalone]

#230476

[Multipart message — attachments visible in raw view] — view raw

 
    On Saturday, January 9, 2021, 08:07:37 AM EST, Brian <ad44@cityscape.co.uk> wrote:  
 
 > On Sat 09 Jan 2021 at 12:55:07 +0000, Dr. Jennifer Nussbaum wrote:
>
> Can you scan by choosing airscan, eSCL (note the lower case e), from
> simple-scan's drop-down menu.

This did work at first, and I was very excited! However, it worked on a text scan; whenI tried an image scan, it hung for several minutes with the error"Unable to find colord device airscan:e0:Canon LiDE 300 (USB): property match 'Serial'='sane:airscan:e0:Canon LiDE 300 (USB)' does not exist",and then after that I was unable to do another text scan--with no error, it justhung.

> > > Would you also try
> > >
> > > xsane "airscan:e0:Canon LiDE 300 (USB)">
> > > and
> > >
> >  > xsane ?
> > I don't have xsane installed. Is that just for background info? I've
> > used it in the past, and always foundit far too complicated to bother
> > with.
>
> You can always remove it afterwards, but I wanted to know which of
> the options it offers work. A preview is enough to do.
xsane works perfectly, whether or specify airscan from the commandline, orif I just run it bare and then select either the pixma or the eSCL airscandevice from the select box.

  

[toc] | [prev] | [next] | [standalone]

#230477

On Sat 09 Jan 2021 at 13:22:30 +0000, Dr. Jennifer Nussbaum wrote:

>  
>     On Saturday, January 9, 2021, 08:07:37 AM EST, Brian <ad44@cityscape.co.uk> wrote:  
>  
>  > On Sat 09 Jan 2021 at 12:55:07 +0000, Dr. Jennifer Nussbaum wrote:
> >
> > Can you scan by choosing airscan, eSCL (note the lower case e), from
> > simple-scan's drop-down menu.
> 
> This did work at first, and I was very excited! However, it worked on
> a text scan; whenI tried an image scan, it hung for several minutes
> with the error"Unable to find colord device airscan:e0:Canon LiDE 300
> (USB): property match 'Serial'='sane:airscan:e0:Canon LiDE 300 (USB)'
> does not exist",and then after that I was unable to do another text
> scan--with no error, it justhung.

This is now getting above my pay grade, Jennifer. Could be a simple-scan
bug or one in the device's firmware or in sane-airscan. Try switching
the Canon off and disconnecting from USB. Re-power and re-plug after
about a minute.

> > > > Would you also try
> > > >
> > > > xsane "airscan:e0:Canon LiDE 300 (USB)">
> > > > and
> > > >
> > >  > xsane ?
> > > I don't have xsane installed. Is that just for background info? I've
> > > used it in the past, and always foundit far too complicated to bother
> > > with.
> >
> > You can always remove it afterwards, but I wanted to know which of
> > the options it offers work. A preview is enough to do.
> xsane works perfectly, whether or specify airscan from the
> commandline, orif I just run it bare and then select either the pixma
> or the eSCL airscandevice from the select box.

This, at least, gives you working scanning.

-- 
Brian.

  

[toc] | [prev] | [next] | [standalone]

#230479

On Sat 09 Jan 2021 at 13:49:07 +0000, Dr. Jennifer Nussbaum wrote:

>  Yes, I can at least scan. I'll keep fiddling, but the important thing
>  is that I can use it.
> 
> OK, thank you so much for your help, and sorry for the top-post at the
> end.

I will probably consult the sane-airscan author, but would not expect an
immediate response.

Another debugging idea if you want to narrow down whether simple-scan is
the problem:

  scanimage d "airscan:e0:Canon LiDE 300 (USB)" --format=png > image.png

Thanks for engaging.

-- 
Brian.
                                 

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web