On Thu 01 Aug 2019 at 17:13:43 +0200, Pierre Frenkiel wrote:
> On Thu, 1 Aug 2019, Andrei POPESCU wrote:
>
> > > model.dat being a file in /usr/share it will most likely be overwritten
> > > without any warning (but I'm too lazy to check).
>
> that's not a big problem:
> a simple "grep" can
On Thu, 1 Aug 2019, Andrei POPESCU wrote:
model.dat being a file in /usr/share it will most likely be overwritten
without any warning (but I'm too lazy to check).
that's not a big problem:
a simple "grep" can show whether the file has been updated,
a simple "cat" can re-introduce my env
On Thu 01 Aug 2019 at 17:13:59 +0300, Andrei POPESCU wrote:
> On Jo, 01 aug 19, 08:37:47, Brad Rogers wrote:
> > On Thu, 1 Aug 2019 08:24:22 +0200 (CEST)
> > Pierre Frenkiel wrote:
> >
> > > thank you for tour warning, but it's not too difficult to make a
> > > backup.
> >
> > It's not /quite/
On Thu, 1 Aug 2019 17:13:59 +0300
Andrei POPESCU wrote:
Hello Andrei,
>model.dat being a file in /usr/share it will most likely be overwritten
>without any warning (but I'm too lazy to check).
Likewise. :-)
Cheers for the clarification (which I trimmed for brevity).
--
Regards _
On Jo, 01 aug 19, 08:37:47, Brad Rogers wrote:
> On Thu, 1 Aug 2019 08:24:22 +0200 (CEST)
> Pierre Frenkiel wrote:
>
> > 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
On Thu, 1 Aug 2019 10:10:26 +0200 (CEST)
Pierre Frenkiel wrote:
Hello Pierre,
> 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.
Now I understand. In my mind I was overcomplicating things.
Cheers.
--
Regard
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 i
On Thu, 1 Aug 2019 08:24:22 +0200 (CEST)
Pierre Frenkiel 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
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
On Wed, 31 Jul 2019 21:53:43 +0200 (CEST)
Pierre Frenkiel 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
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 questi
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, i
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 wou
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.
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
On Wed 31 Jul 2019 at 17:18:16 +0200, Pierre Frenkiel wrote:
> On Wed, 31 Jul 2019, Brian wrote:
>
> > On Wed 31 Jul 2019 at 13:52:29 +0200, Pierre Frenkiel wrote:
> >
> > > Here are the outputs of scanimage on my desktop:
> > >
> > >scanimage: open of device
> > > hpaio:/net/HP_LaserJet
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
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
On Wed, 31 Jul 2019, Brian wrote:
On Wed 31 Jul 2019 at 13:52:29 +0200, Pierre Frenkiel wrote:
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
h
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
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
On Wed 31 Jul 2019 at 13:52:29 +0200, Pierre Frenkiel wrote:
> 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_m
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) broadca
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 so
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
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 mo
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/
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 sa
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 t
On Fri 26 Jul 2019 at 12:58:25 +0200, Pierre Frenkiel wrote:
> hi,
> I have 2 all-in-one printers
> - hp laserjet pro
> - hp envy
> And I have different behaviours on different computers:
>
> - on my desktop (debian/buster), xsane list both correctly
> but scanning doesn't work on the laserj
hi,
I have 2 all-in-one printers
- hp laserjet pro
- hp envy
And I have different behaviours on different computers:
- on my desktop (debian/buster), xsane list both correctly
but scanning doesn't work on the laserjet:
" failed to open device ..."
- on my laptop, same thing
- on my wif
31 matches
Mail list logo
