https://bugzilla.suse.com/show_bug.cgi?id=1169817 https://bugzilla.suse.com/show_bug.cgi?id=1169817#c8 --- Comment #8 from Martin Wilck --- (In reply to Johannes Meixner from comment #7)

https://github.com/OpenPrinting/cups-filters/issues/391#issuecomment-8750661...

"cups-browsed [...] fully automatically creates local permanent queues for all discovered printers. [...] The driverless utility retro-fits driverless printing into pseudo drivers, to make it accessible in printer setup tools". Am I understanding correctly that "cups-browsed" and "driverless" are supposed to work together ("cups-browsed" for the queues, and "driverless" for the setup tools)? IOW: does "driverless" provide the configuration interface that is later used by "cups-browsed"? Or are these rather competing concepts for achieving similar goals? Does the yast printing module support "driverless"? "I have always succeeded to let the show go on seamlessly for the users, whatever feature Michael (or anyone else) is removing by throwing in workarounds and retro-fits quickly enough, before running into a pandemic-alike "I CANNOT PRINT!!!" crisis." That sounds like a dangerous working model in the long run. One side permanently removing features and the other side trying to cope with it by retro-fitting. What if Till is hit by a bus? -- You are receiving this mail because: You are on the CC list for the bug.