Bug#766489: Many links created in /tmp

2014-10-23 Thread Gedalya
Package: cups Version: 1.7.5-5 I really don't have much detail here but it's certainly strange. This happened about 1 hour after upgrading from 1.7.5-4+b1 to 1.7.5-5 when I had to print something. As a side note, I'm not quite sure why this broke my system (the mkstemp and gpgv failures shown

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

2017-10-24 Thread Gedalya
59706, and renaming it to [officejet_pro_8710] as the log suggests. That works fine. Regards, Gedalya

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

2017-11-22 Thread Gedalya
On 11/22/2017 01:46 PM, Brian Potkin wrote: > I forgot to ask: is scanning successful if, instead of duplicating the > section. you just delete the "hp_" from [hp_officejet_pro_8710]? Yes, same effect.

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

2017-11-22 Thread Gedalya
On 11/21/2017 08:09 PM, Brian Potkin wrote: > > Hello Gedalya. Thank you for your report. I forwarded it upstream and > now you will see there is a reply. Please would you respond to that > message there as I am unable to speak for you. I'll look into that. Thank you! > &g

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

2017-11-23 Thread Gedalya
On 11/23/2017 01:37 PM, Brian Potkin wrote: > >> Note: In order to produce this, I need to stop cupsd. Somehow, at some >> point sane started finding the scanner via CUPS, the printer being >> configured there. > I take this to mean you configured the printer with something like > hp-setup and the

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

2017-11-23 Thread Gedalya
On 11/23/2017 05:44 PM, Brian Potkin wrote: > On Thu 23 Nov 2017 at 14:05:38 +0100, Gedalya wrote: > >> On 11/23/2017 01:37 PM, Brian Potkin wrote: >>>> Note: In order to produce this, I need to stop cupsd. Somehow, at some >>>> point sane started finding the

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

2017-11-29 Thread Gedalya
On 11/23/2017 09:08 PM, Brian Potkin wrote: > >>> So where does scanimage get the uri from when cups is running? From the >>> Bonjour broadcasts? What happens when you deactivate broadcasting on the >>> printer? >> I don't know how to do that. > Go to http://192.168.9.238 with a browser. Look under

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

2017-11-29 Thread Gedalya
On 11/23/2017 09:08 PM, Brian Potkin wrote: >>> This device-uri should also be given by hp-makeuri. Would you confirm >>> this and check printing takes place. >> This in fact works only with the original models.dat, with the hp_ prefix: > That in itself should indicate something to you. > I get th

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

2017-11-30 Thread Gedalya
On 11/30/2017 03:11 PM, Brian Potkin wrote: > I wonder how you would go on with the queue > > >  lpadmin -p 4500 hp:/net/envy_4500_series?ip=192.168.9.238 -E -m > drv:///hpcups.drv/hp_envy_4500_series.ppd\ lpadmin: Unknown argument "hp:/net/envy_4500_series?ip=192.168.9.238". not sure where to g

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

2017-11-30 Thread Gedalya
On 11/30/2017 11:19 PM, Brian Potkin wrote:  lpadmin -p 4500 -v hp:/net/envy_4500_series?ip=192.168.9.238 -E -m drv:///hpcups.drv/hp_envy_4500_series.ppd\ ^ ^ We both have access to the same manual. :) You're right. But I'm just not following most of wh

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

2017-12-01 Thread Gedalya
On 12/01/2017 05:51 PM, Brian Potkin wrote: > > I would appreciate that you do one re-test. Depending on the outcome, I > think we will see light at the end of the tunnel. :) > > You report: > > > When cupsd is running and the AIO is configured as a printer > > in CUPS, this issue does not occur.

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

2017-12-01 Thread Gedalya
On 12/01/2017 05:51 PM, Brian Potkin wrote: > > With CUPS running, or with models.dat edited: > >$ scanimage -L > > device `hpaio:/net/officejet_pro_8710?ip=192.168.9.238&queue=false' is a > Hewlett-Packard officejet_pro_8710 all-in-one And now, with cupsd running and Bonjour enabled: device

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

2017-12-01 Thread Gedalya
On 12/01/2017 07:05 PM, Brian Potkin wrote: > How does that sound? In terms of gut-feeling / speculation, we have arrived at what was obvious to me when opening this bug. > (It does not look at the broadcasts when the print queue is operative). The same lines get printed to syslog, so it does

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

2017-12-01 Thread Gedalya
On 12/01/2017 02:04 PM, Brian Potkin wrote: Sorry; another typo. It's drv:///hpcups.drv/hp-envy_4500_series.ppd OK, finally I get: device `hpaio:/net/envy_4500_series?ip=192.168.9.238' is a Hewlett-Packard envy_4500_series all-in-one You are definitely not wasting my time. I'm unsure wheth

Bug#879719: libsane-hpaio: Does not recognize OfficeJet Pro 8710

2018-11-15 Thread Gedalya
On 11/11/18 1:07 AM, Brian Potkin wrote: > Gedalya, if you are on unstable please upgrade to 3.18.10+dfsg0-2. If > you are on testing, install libsane-hpaio from unstable. This is the > only package you need for scanning; it will overwrite models.dat. > > How do you go on now?