Your message dated Fri, 3 Mar 2017 20:15:38 +0000 with message-id <03032017200538.b4bd686d0ceb@desktop.copernicus.org.uk> and subject line Re: Bug#586644: Unnecessary dbus warnings has caused the Debian Bug report #586644, regarding Unnecessary dbus warnings to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 586644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586644 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Unnecessary dbus warnings
- From: martin f krafft <madduck@debian.org>
- Date: Mon, 21 Jun 2010 11:42:04 +0200
- Message-id: <20100621094204.GA1439@piper.oerlikon.madduck.net>
Package: hplip Version: 2.8.6.b-4 Severity minor I am running hplip on a headless, embedded device. I see absolutely no reason or benefit in running d-bus on this machine, and so I don't. Yet, hplip seems to think that everyone is running d-bus, which is a shame. Hence, every print job, and every scan job is accompanied by a slew of errors and warnings in syslog, as if hplip thinks the world has come to an end because it could not talk to d-bus. I'd prefer if hplip didn't vacuously depend on obviously optional stuff (printing and scanning work), but the trend is obvious and ubiquitous and fighting gratuitous dependencies is like fending off the incoming flood with a sieve.</rant> Assuming hplip cannot dlopen() d-bus stuff and thus make it a recommendation, rather than a hard dependency, at least it would be nice if it noticed once at the start that d-bus is not working on the system and shuts up about it subsequently. vizier HP_LaserJet_3052?ip=192.168.14.65: prnt/backend/hp.c 528: dBus Connection Error (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)! vizier HP_LaserJet_3052?ip=192.168.14.65: prnt/backend/hp.c 511: dbus message send failed! vizier HP_LaserJet_3052?ip=192.168.14.65: prnt/backend/hp.c 511: dbus message send failed! -- .''`. martin f. krafft <madduck@d.o> Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduck http://vcs-pkg.org `- Debian - when you have better things to do than fixing systemsAttachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
--- End Message ---
--- Begin Message ---
- To: 586644-done@bugs.debian.org
- Subject: Re: Bug#586644: Unnecessary dbus warnings
- From: Brian Potkin <claremont102@gmail.com>
- Date: Fri, 3 Mar 2017 20:15:38 +0000
- Message-id: <03032017200538.b4bd686d0ceb@desktop.copernicus.org.uk>
- In-reply-to: <20100621094204.GA1439@piper.oerlikon.madduck.net>
- References: <20100621094204.GA1439@piper.oerlikon.madduck.net>
On Mon 21 Jun 2010 at 11:42:04 +0200, martin f krafft wrote: > I am running hplip on a headless, embedded device. I see absolutely > no reason or benefit in running d-bus on this machine, and so > I don't. Yet, hplip seems to think that everyone is running d-bus, > which is a shame. > > Hence, every print job, and every scan job is accompanied by a slew > of errors and warnings in syslog, as if hplip thinks the world has > come to an end because it could not talk to d-bus. > > I'd prefer if hplip didn't vacuously depend on obviously optional > stuff (printing and scanning work), but the trend is obvious and > ubiquitous and fighting gratuitous dependencies is like fending off > the incoming flood with a sieve.</rant> > > Assuming hplip cannot dlopen() d-bus stuff and thus make it > a recommendation, rather than a hard dependency, at least it would > be nice if it noticed once at the start that d-bus is not working on > the system and shuts up about it subsequently. > > vizier HP_LaserJet_3052?ip=192.168.14.65: prnt/backend/hp.c 528: dBus Connection Error (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)! > vizier HP_LaserJet_3052?ip=192.168.14.65: prnt/backend/hp.c 511: dbus message send failed! > vizier HP_LaserJet_3052?ip=192.168.14.65: prnt/backend/hp.c 511: dbus message send failed! I think Mark Purcell's suggestion is a good one. printer-driver-hpcups and libsane-hpaio are all that are needed for printing and scanning, It is what I use on my headless server. Closing because the objective is achievable. Regards, Brian.
--- End Message ---