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. The absolutely inadequate debug logging of the software in question has not made it any easier to debug this issue. 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. Greetings Marc
