I think the problem here is CUPS' own method of generating temporary queues for discovered driverless printers. gnome-control-center, and probably other GUIs, like the GTK print dialog, cannot cope with this. So we leave this bug report assigned to gnome-control-center for now.
Christian, if you stop cups-browsed you have still auto-generated print queues. This is because CUPS itself kicks in here. If you run lpstat -e you see queue names which you do not see with lpstat -v The extra queue names are temporary CUPS queues. These are created by CUPS if you try to print on them or to access them in general, and they are removed by CUPS again after 1 minute of inactivity. gnome-control-center probably gets completely confused by that. It can have seen such a queue as actual queue, shortly after such a queue was used, and added it to its list. Now, more than a minute later, the user clicks on the entry, the queue is not there any more, and he gets something unexpected, an error message, an empty option dialog, a "(null):631". gnome-control-center and all other printing GUIs need to be adapted to CUPS' temporary print queues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813825 Title: "driverless" printer workflow has bad usability/ is partly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
