Bug#887495: cups-browsed: 'No destination host name supplied by cups-browsed for printer "name", is cups-browsed running?' for all queues
Thank you for your reports, Jens, christoph and Marc. For the avoidance
of doubt - I am not a cups-browsed maintainer.
On Thu 11 Oct 2018 at 13:16:13 +0200, Marc Haber wrote:
> On Mon, Mar 26, 2018 at 01:43:00PM +0200, Christoph Pleger wrote:
> > I discovered the same problem on my computer today and found out that it is
> > NO coincidence that the problem occurs on the KDE desktop.
>
> Half a year later without maintainer response on this bug, I stumbled
> about this issue and had the same issue on my system. I would NEVER have
> come to the conclusion that the desktop environment in use plays a role
> in this issue which presents itself as rooted deeply between system
> daemons and network issues.
It is unlikely to be a DE issue. I came across the behaviour today while
working in a non-KDE environment and printing from LibreOffice and with
lp.
Only Jens provides the cups version being used and modifications to
cups-browsed.conf made. For me, its cups v2.2.8 and having "driverless"
for the CreateIPPPrinterQueues directive as the only change. On the
surface, we are using different printing systems. I am only inclined to
conduct tests on unstable. "BrowseRemoteProtocols cups" doesn't motivate
me.
> The absolutely inadequate debug logging of the software in question has
> not made it any easier to debug this issue.
Has anyone managed consistently to reproduce the reported behaviour? I
haven't yet formulated a plan of attack to do so.
> That being said, my system prints again.
>
> What did not help:
> Activate KDE screen saver, start additional session, log in with the
> same account with lxqt, try printing from there (didn't work, same
> error).
>
> What helped:
> Log out of KDE, start new session with same account with lxqt, try
> printing from there (worked), log out of lxqrt, log into KDE with the
> smae account (worked).
>
> This is one of the most mysterious and astonishing issuest hat I have
> encountered in my lifetime. Kudos for nailing this down to KDE.
KDE? Maybe, maybe not. Perhaps the "No destination host name supplied..."
message has three different causes?
Regards,
Brian.
Reply to: