Comment 6 for bug 1813825

Thanks for the info, the logs don't have much though :/

The journal has that
gnome-control-c[31150]: gtk_container_add: assertion 'GTK_IS_CONTAINER (container)' failed

It would be interesting to get a backtrace of that warning, unsure if you know your were around debugging enough to do that though?

Basically you would need to
- enable the debug packages repository as explained on https://wiki.ubuntu.com/Debug%20Symbol%20Packages and install the gnome-control-center-dbgsym libgtk-3-0-dbgsym libglib2.0-0-dbgsym at least
- get a backtrace using gdb, the principle is explained on https://wiki.ubuntu.com/Backtrace but to get the one from the log you would need to "b g_log" and type "c" until you get to a call corresponding to the gtk_container_add warning

If you want to try that it would be nice, if it's too technical for you that's fine

Reading the description again I think the issues are

1- there is no easy way to "block" a specific ipp printer to be auto-added, which can either be a feature missing from cups or one that exists but has no UI interface, Till should know about that

2- the 'cups-pk-helper: setting default printer to Kyocera_ECOSYS_P6026cdn failed: client-error-not-found' error, which is probably a problem on the cups/cups-pk-helper side. It's weird that nothing got logged about in the journal or cups logs though...

3- the settings UI not dealing well without the 'situation' (unsure what bits are confusing it though)

Does system-config-printer deal works better? Does it list the right printer and allow you to see the options or does it have issues as well?