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

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

xsane: incoherent behaviours

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

Contents

  xsane: incoherent behaviours Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2019-07-30 19:00 +0200
    Re: xsane: incoherent behaviours Brian <ad44@cityscape.co.uk> - 2019-07-31 00:20 +0200
      Re: xsane: incoherent behaviours Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2019-07-31 00:40 +0200
        Re: xsane: incoherent behaviours Brian <ad44@cityscape.co.uk> - 2019-07-31 12:20 +0200
          Re: xsane: incoherent behaviours Brian <ad44@cityscape.co.uk> - 2019-07-31 13:30 +0200
            Re: xsane: incoherent behaviours Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2019-07-31 14:00 +0200
              Re: xsane: incoherent behaviours Brian <ad44@cityscape.co.uk> - 2019-07-31 15:10 +0200
                Re: xsane: incoherent behaviours Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2019-07-31 16:30 +0200
                  Re: xsane: incoherent behaviours Brian <ad44@cityscape.co.uk> - 2019-07-31 16:50 +0200
                    Re: xsane: incoherent behaviours Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2019-07-31 17:40 +0200
                      Re: xsane: incoherent behaviours Brian <ad44@cityscape.co.uk> - 2019-07-31 17:50 +0200
                        Re: xsane: incoherent behaviours Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2019-07-31 19:50 +0200
                          Re: xsane: incoherent behaviours Brian <ad44@cityscape.co.uk> - 2019-07-31 20:20 +0200
                            Re: xsane: incoherent behaviours Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2019-07-31 20:20 +0200
                              Re: xsane: incoherent behaviours Brian <ad44@cityscape.co.uk> - 2019-07-31 20:40 +0200
                                Re: xsane: incoherent behaviours Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2019-07-31 22:00 +0200
                                  Re: xsane: incoherent behaviours Brad Rogers <brad@fineby.me.uk> - 2019-07-31 22:20 +0200
                                    Re: xsane: incoherent behaviours Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2019-08-01 08:30 +0200
                                      Re: xsane: incoherent behaviours Brad Rogers <brad@fineby.me.uk> - 2019-08-01 10:10 +0200
                                        Re: xsane: incoherent behaviours Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2019-08-01 10:20 +0200
                                          Re: xsane: incoherent behaviours Brad Rogers <brad@fineby.me.uk> - 2019-08-01 10:30 +0200
                                        Re: xsane: incoherent behaviours Andrei POPESCU <andreimpopescu@gmail.com> - 2019-08-01 16:20 +0200
                                          Re: xsane: incoherent behaviours Brad Rogers <brad@fineby.me.uk> - 2019-08-01 17:00 +0200
                                            Re: xsane: incoherent behaviours Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2019-08-01 17:20 +0200
                                              Re: xsane: incoherent behaviours Brian <ad44@cityscape.co.uk> - 2019-08-01 18:10 +0200
                                          Re: xsane: incoherent behaviours Brian <ad44@cityscape.co.uk> - 2019-08-01 17:10 +0200
              Re: xsane: incoherent behaviours Brian <ad44@cityscape.co.uk> - 2019-07-31 15:20 +0200
                Re: xsane: incoherent behaviours Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2019-07-31 17:20 +0200
                  Re: xsane: incoherent behaviours Brian <ad44@cityscape.co.uk> - 2019-07-31 18:00 +0200

Page 1 of 2  [1] 2  Next page →

#211923 — xsane: incoherent behaviours

  Brian wrote:
  what does scanimage -L ...

  hi Brian,
  (sorry for the delay)
  on my desktop(buster) and my laptop (amd64/stretch), both devices are listed.
  on my wife's laptop(amd64/stretch), only the laserjet, and as I said scanning
  works...
  Then, the problem is not with the device, but with the xsane version of
  Debian. What is rather difficult to understand is why the 2 laptops which
  seem to have the same config behave so differently.

  Can anybody explain that ?

best regards,
-- 
Pierre Frenkiel

[toc] | [next] | [standalone]

#211938

On Tue 30 Jul 2019 at 18:54:46 +0200, Pierre Frenkiel wrote:

>  Brian wrote:
>  what does scanimage -L ...
> 
>  hi Brian,
>  (sorry for the delay)
>  on my desktop(buster) and my laptop (amd64/stretch), both devices are listed.
>  on my wife's laptop(amd64/stretch), only the laserjet, and as I said scanning
>  works...
>  Then, the problem is not with the device, but with the xsane version of
>  Debian. What is rather difficult to understand is why the 2 laptops which
>  seem to have the same config behave so differently.
> 
>  Can anybody explain that ?

The outputs of 'scanimage -L' from each machine were asked for. They
provide information you have not given.

-- 
Brian.

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

#211942

On Tue, 30 Jul 2019, Brian wrote:

> The outputs of 'scanimage -L' from each machine were asked for. They
> provide information you have not given.
>
> -- 
> Brian.
>
  hi brian,
  I thought that they don't provide more information than what I wrote previously,

  (on my desktop(buster) and my laptop (amd64/stretch), both devices are listed.
  on my wife's laptop(amd64/stretch), only the laserjet)

  but if you want them, here they are

  my desktop:
     device `hpaio:/net/HP_LaserJet_MFP_M227-M231?ip=192.168.1.41' is a Hewlett-Packard HP_LaserJet_MFP_M227-M231 all-in-one
    device `hpaio:/net/laserjet_mfp_m227-m231?ip=192.168.1.41&queue=false' is a Hewlett-Packard laserjet_mfp_m227-m231 all-in-one
    device `hpaio:/net/envy_photo_7100_series?ip=192.168.1.200&queue=false' is a Hewlett-Packard envy_photo_7100_series all-in-one

  my laptop:
    device `hpaio:/net/laserjet_mfp_m227-m231?ip=192.168.1.41&queue=false' is a Hewlett-Packard laserjet_mfp_m227-m231 all-in-one
    device `hpaio:/net/envy_photo_7100_series?ip=192.168.1.200&queue=false' is a Hewlett-Packard envy_photo_7100_series all-in-one

  my wife's laptop:
    device `hpaio:/net/HP_LaserJet_MFP_M227-M231?zc=NPIBDD3AA' is a Hewlett-Packard HP_LaserJet_MFP_M227-M231 all-in-one

  I would be glad if that helps you to explain what happens.
  I specially don't understand why she doesn't see the envy.

  Anyway, thank you for your help.

best regards,
-- 
Pierre Frenkiel

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

#211958

On Wed 31 Jul 2019 at 00:35:51 +0200, Pierre Frenkiel wrote:

> On Tue, 30 Jul 2019, Brian wrote:
> 
> > The outputs of 'scanimage -L' from each machine were asked for. They
> > provide information you have not given.
> > 
> > -- 
> > Brian.
> > 
>  hi brian,
>  I thought that they don't provide more information than what I wrote previously,

The outputs provide the URIs seen by scanimage (and xsane), how the
URIs have been formed and the names of the devices. All essential
information.
 
>  (on my desktop(buster) and my laptop (amd64/stretch), both devices are listed.
>  on my wife's laptop(amd64/stretch), only the laserjet)

Being listed is not sufficient; a URI also has to be correct.
 
>  but if you want them, here they are
> 
>  my desktop:
>     device `hpaio:/net/HP_LaserJet_MFP_M227-M231?ip=192.168.1.41' is a Hewlett-Packard HP_LaserJet_MFP_M227-M231 all-in-one
>    device `hpaio:/net/laserjet_mfp_m227-m231?ip=192.168.1.41&queue=false' is a Hewlett-Packard laserjet_mfp_m227-m231 all-in-one

I think that scanimage (and xsane) use the first offered URI.

Test:

 scanimage -d hpaio:/net/HP_LaserJet_MFP_M227-M231?ip=192.168.1.41 > out.dat
 scanimage -d hpaio:/net/laserjet_mfp_m227-m231?ip=192.168.1.41&queue=false > out.dat

>    device `hpaio:/net/envy_photo_7100_series?ip=192.168.1.200&queue=false' is a Hewlett-Packard envy_photo_7100_series all-in-one
> 
>  my laptop:
>    device `hpaio:/net/laserjet_mfp_m227-m231?ip=192.168.1.41&queue=false' is a Hewlett-Packard laserjet_mfp_m227-m231 all-in-one
>    device `hpaio:/net/envy_photo_7100_series?ip=192.168.1.200&queue=false' is a Hewlett-Packard envy_photo_7100_series all-in-one
> 
>  my wife's laptop:
>    device `hpaio:/net/HP_LaserJet_MFP_M227-M231?zc=NPIBDD3AA' is a Hewlett-Packard HP_LaserJet_MFP_M227-M231 all-in-one
> 
>  I would be glad if that helps you to explain what happens.
>  I specially don't understand why she doesn't see the envy.

The URIs with "queue=false" indicate that your desktop and laptop have
discovered the MFDs from their DNS-SD (Bonjour) broadcasts. Your wife's
laptop does not do such a discovery. This implies that there is some
issue with avahi-daemon on this machine. What do you get for

 avahi-browse -rt _uscan._tcp

and

 avahi-browse -rt _ipp._tcp

avahi-browse is in the avahi-utils package.

-- 
Brian.

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

#211961

On Wed 31 Jul 2019 at 11:16:34 +0100, Brian wrote:

> The URIs with "queue=false" indicate that your desktop and laptop have
> discovered the MFDs from their DNS-SD (Bonjour) broadcasts. Your wife's
> laptop does not do such a discovery. This implies that there is some
> issue with avahi-daemon on this machine. What do you get for

The HP Envy Photo 7100 is not supported by libsane-hpaio on stretch.
How come your laptop can scan from it but your wife's machine cannot?

>  avahi-browse -rt _uscan._tcp
> 
> and
> 
>  avahi-browse -rt _ipp._tcp
> 
> avahi-browse is in the avahi-utils package.

These outputs will still be useful.

-- 
Brian.

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

#211965

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

On Wed, 31 Jul 2019, Brian wrote:

> On Wed 31 Jul 2019 at 11:16:34 +0100, Brian wrote:
>
>> The URIs with "queue=false" indicate that your desktop and laptop have
>> discovered the MFDs from their DNS-SD (Bonjour) broadcasts. Your wife's
>> laptop does not do such a discovery. This implies that there is some
>> issue with avahi-daemon on this machine. What do you get for
>
> The HP Envy Photo 7100 is not supported by libsane-hpaio on stretch.
> How come your laptop can scan from it but your wife's machine cannot?

   It's a good question, as both are on stretch, but I don't have the answer...
   As
   "scanimage -d hpaio:/net/envy_photo_7100_series?ip=192.168.1.200\&queue=false > t
   works on my laptop, it seems that it is supported.

   for avahi-browse -rt _uscan._tcp  and avahi-browse -rt _ipp._tcp
   I put both outputs as attached files, as they are rather big
   If I understand well, they indicate that the envy is actually seen.
   I hope you will understand, as I don't...

   Here are the outputs of scanimage on my desktop:

    scanimage: open of device hpaio:/net/HP_LaserJet_MFP_M227-M231?ip=192.168.1.41 failed: Error during device I/O
    scanimage: open of device hpaio:/net/laserjet_mfp_m227-m231?ip=192.168.1.41&queue=false failed: Error during device I/O


best regards,
-- 
Pierre Frenkiel

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

#211971

On Wed 31 Jul 2019 at 13:52:29 +0200, Pierre Frenkiel wrote:

> On Wed, 31 Jul 2019, Brian wrote:
> 
> > On Wed 31 Jul 2019 at 11:16:34 +0100, Brian wrote:
> > 
> > > The URIs with "queue=false" indicate that your desktop and laptop have
> > > discovered the MFDs from their DNS-SD (Bonjour) broadcasts. Your wife's
> > > laptop does not do such a discovery. This implies that there is some
> > > issue with avahi-daemon on this machine. What do you get for
> > 
> > The HP Envy Photo 7100 is not supported by libsane-hpaio on stretch.
> > How come your laptop can scan from it but your wife's machine cannot?
> 
>   It's a good question, as both are on stretch, but I don't have the answer...
>   As
>   "scanimage -d hpaio:/net/envy_photo_7100_series?ip=192.168.1.200\&queue=false > t
>   works on my laptop, it seems that it is supported.

What is given by 'dpkg -l libsane-hpaio' from both stretch machines?

>   for avahi-browse -rt _uscan._tcp  and avahi-browse -rt _ipp._tcp
>   I put both outputs as attached files, as they are rather big
>   If I understand well, they indicate that the envy is actually seen.
>   I hope you will understand, as I don't...
> 
>   Here are the outputs of scanimage on my desktop:
> 
>    scanimage: open of device hpaio:/net/HP_LaserJet_MFP_M227-M231?ip=192.168.1.41 failed: Error during device I/O
>    scanimage: open of device hpaio:/net/laserjet_mfp_m227-m231?ip=192.168.1.41&queue=false failed: Error during device I/O

Thinking.

-- 
Brian.

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

#211978

On Wed, 31 Jul 2019, Brian wrote:

> What is given by 'dpkg -l libsane-hpaio' from both stretch machines?

   exactly same output:

ii  libsane-hpaio:amd64           3.16.11+repack0-3   amd64               HP SANE backend for multi-function peripherals

best regards,
-- 
Pierre Frenkiel

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

#211981

On Wed 31 Jul 2019 at 16:28:55 +0200, Pierre Frenkiel wrote:

> On Wed, 31 Jul 2019, Brian wrote:
> 
> > What is given by 'dpkg -l libsane-hpaio' from both stretch machines?
> 
>   exactly same output:
> 
> ii  libsane-hpaio:amd64           3.16.11+repack0-3   amd64               HP SANE backend for multi-function peripherals

I thought you might have had a backported package on one machine.

Another check:

grep "envy_photo_7100" /usr/share/hplip/data/models/models.dat

-- 
Brian.

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

#211984

On Wed, 31 Jul 2019, Brian wrote:

> Another check:
>
> grep "envy_photo_7100" /usr/share/hplip/data/models/models.dat
>

   you are right: the envy entry was missing on this laptop.
   thanks a lot for your help

best regards,
-- 
Pierre Frenkiel

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

#211985

On Wed 31 Jul 2019 at 17:31:38 +0200, Pierre Frenkiel wrote:

> On Wed, 31 Jul 2019, Brian wrote:
> 
> > Another check:
> > 
> > grep "envy_photo_7100" /usr/share/hplip/data/models/models.dat
> > 
> 
>   you are right: the envy entry was missing on this laptop.
>   thanks a lot for your help

Which laptop? Both have stretch. Neither should have an envy photo 7100
entry in models.dat.

-- 
Brian.

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

#211992

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

On Wed, 31 Jul 2019, Brian wrote:

> Which laptop? Both have stretch. Neither should have an envy photo 7100
> entry in models.dat.

   this time, facts prove that your are wrong (we say in french
   "les faits sont têtus" i.e. "facts are stubborn"
   and here are the facts:

   - without the envy entry in models.dat, the envy is not seen on both laptops.
   - with the envy entry in models.dat, the envy is seen on both laptops,
     and scanning works perfectly...

the remaining problem is why scanning with the laserjet fails on my desktop
(but this is an other story)

anyway, thank you for your cooperation.
best regards,
-- 
Pierre Frenkiel

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

#211996

On Wed 31 Jul 2019 at 19:43:24 +0200, Pierre Frenkiel wrote:

> On Wed, 31 Jul 2019, Brian wrote:
> 
> > Which laptop? Both have stretch. Neither should have an envy photo 7100
> > entry in models.dat.
> 
>   this time, facts prove that your are wrong (we say in french
>   "les faits sont têtus" i.e. "facts are stubborn"
>   and here are the facts:
> 
>   - without the envy entry in models.dat, the envy is not seen on both laptops.
>   - with the envy entry in models.dat, the envy is seen on both laptops,
>     and scanning works perfectly...

You are misunderstanding. When I said "Neither should have an envy photo
7100 entry in models.dat.", I meant that the *stretch* models.dat does
not have it as an entry. If it is there, it has been put there - and not
by anything which a stretch inastallation would do.

-- 
Brian.

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

#211998

On Wed, 31 Jul 2019, Brian wrote:

> You are misunderstanding. When I said "Neither should have an envy photo
> 7100 entry in models.dat.", I meant that the *stretch* models.dat does
> not have it as an entry. If it is there, it has been put there - and not
> by anything which a stretch inastallation would do.

    - the stretch models.dat does not have an envy entry ==> envy is not seen, and
      of course scanning is not available
    - now, it is there because I put it ==> envy is seen, and scanning works
      do you see an other solution?

best regards,
-- 
Pierre Frenkiel

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

#212000

On Wed 31 Jul 2019 at 20:18:09 +0200, Pierre Frenkiel wrote:

> On Wed, 31 Jul 2019, Brian wrote:
> 
> > You are misunderstanding. When I said "Neither should have an envy photo
> > 7100 entry in models.dat.", I meant that the *stretch* models.dat does
> > not have it as an entry. If it is there, it has been put there - and not
> > by anything which a stretch inastallation would do.
> 
>    - the stretch models.dat does not have an envy entry ==> envy is not seen, and
>      of course scanning is not available

Agreed.

>    - now, it is there because I put it ==> envy is seen, and scanning works
>      do you see an other solution?

Agreed.

But you said your was laptop amd64/stretch; it wasn't. models.dat had
been altered at some time by you. You failed to mention that.

-- 
Brian.

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

#212009

On Wed, 31 Jul 2019, Brian wrote:

> But you said your was laptop amd64/stretch; it wasn't. models.dat had
> been altered at some time by you. You failed to mention that.

   I never modified models.dat before.
   until last week, I used "scanimage -d hpaio:/net/envy_photo_7100..."
   after your question about:
       grep "envy_photo_7100" /usr/share/hplip/data/models/models.dat
   I added it to models.dat

best regards,
-- 
Pierre Frenkiel

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

#212010

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

On Wed, 31 Jul 2019 21:53:43 +0200 (CEST)
Pierre Frenkiel <pierre.frenkiel@gmail.com> wrote:

Hello Pierre,

>       grep "envy_photo_7100" /usr/share/hplip/data/models/models.dat
>   I added it to models.dat

You should be aware that, come next update of hplip, your changes may be
lost, unless you are careful.

-- 
 Regards  _
         / )           "The blindingly obvious is
        / _)rad        never immediately apparent"
Never give in until they crack
Emergency - 999

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

#212033

On Wed, 31 Jul 2019, Brad Rogers wrote:

> You should be aware that, come next update of hplip, your changes may be
> lost, unless you are careful.
>
  thank you for tour warning, but it's not too difficult to make a backup.

best regards,
-- 
Pierre Frenkiel

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

#212040

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

On Thu, 1 Aug 2019 08:24:22 +0200 (CEST)
Pierre Frenkiel <pierre.frenkiel@gmail.com> wrote:

Hello Pierre,

>  thank you for tour warning, but it's not too difficult to make a
> backup.

It's not /quite/ that simple.  I know that the update process is
'clever' enough to detect user made config changes and offer options,
but whether that also applies to, in this case, model.dat, IDK.

So, simply replacing the updated model.dat file with your backup means
you'll lose any improvements that come about from that update.  Of
course, if those improvements don't include tweaks to the stanza for
your printer, then the problem probably isn't an issue.

-- 
 Regards  _
         / )           "The blindingly obvious is
        / _)rad        never immediately apparent"
No guarantee the stimuli must be perceived the same...
Gary Gilmore's Eyes - The Adverts

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

#212041

On Thu, 1 Aug 2019, Brad Rogers wrote:

> So, simply replacing the updated model.dat file with your backup means
> you'll lose any improvements that come about from that update.  Of
> course, if those improvements don't include tweaks to the stanza for
> your printer, then the problem probably isn't an issue.

   you are right, but I speak of a backup, it's only the entry i've added.
   So, I just have to add it to the new models.dat, if any.

best regards,
-- 
Pierre Frenkiel

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

Page 1 of 2  [1] 2  Next page →

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

csiph-web