This is a clone of https://bugs.gentoo.org/show_bug.cgi?id=456360 Kirill Elagin 2013-02-10 01:22:06 CET: I'm trying to add a printer, published via dns-sd (by printserver running CUPS+Avahi). When I run print-manager, and click “New printer”, my printer is discovered, but there is a red error “The name org.fedoraproject.Config.Printing was not provided by any .service files”. If I close the window and open it again, the printer is discovered and this error is displayed sometimes, and sometimes there is no error and no printer. It seems to be a bit random for now…
Unfortunately that is a bug on that interface, for some reason failing to init or expose itself we just query it to be able to present a better grouping to the user and to have some useful things like finding the best driver for a given printer. If you are sure to have system-config-printer dbus interface installed then fill a bug against it. Thanks.
Background info, Gentoo splits system-config-printer into system-config-printer-core and system-config-printer-gnome. Somehow the needed part ended up in system-config-printer-gnome... dependency fixed.
@dantti Please say again? print-manager requires s-c-p? I see in code it certainly needs dbus interface descriptor, but what could you be more specifica on what actually print-manager needs from scp? Resolve/Invalid is a bit rude since there's no mention of scp dependency in either CMakeLists.txt or README... Please update buildsystem/readme accordingly.
It's not a hard dep which is why there isn't something explicit about it. I have written many blog posts of why s-c-p is important (but not mandatory), of course you probably missed them. s-c-p help us to merge printers which have more than one protocol into a single entry on the tree, it help us to get the best driver for the chosen printer. Just that, once you have a printer installed you never need it again. It's invalid as it's not a bug in print-manager and I stated what the user was missing which is s-c-p, so it's unfair calling it was rude as I gave enough info for the user know what's wrong. As Andreas mentioned it was a packaging issue. I'll mention this into the README file but it's likely no one will ever read that... Also it could be that his s-c-p installation was bogus. Best
Thanks for info. Btw, among others, I'm s-c-p maintainer in Gentoo so obviously I read READMEs, PACKAGING and buildsystems first. Sorry, I'm not following all upstream developers' blogs .
Sorry Dantii to recover the dead again: > If you are sure to have system-config-printer dbus interface installed then fill a bug against it. You said scp is recommended but not required. Could you then (within this bug) try to sanitize (make UI responses more predictable) print-manager behaviour when scp is not installed? So that one doesn't get that special driver selection functionality, yet is able to add printer (albeit with some manual selection work) without problems.
Btw, Andreas mentioned packaging dbus interface file in s-c-p-gnome (instead of s-c-p-common) as packaging issue. The problem is underlying functionality actually requires "gnome" (so UI) stuff from s-c-p. Our KDE users are often not insterested in installing s-c-p-gnome to get fully working print-manager. Which is why there's my request to handle lack of s-c-p more gracefully in print-manager.
I can't see how this bug is invalid. Users and Distros are not reading your blogs. Please be nice and add s-cp as runtime depend to print-managers build system so everyone knows what s-c-p is about. thx
Patches welcome.
While not made a runtime dependency, we have updated the readme and the Plasma6 (6.0.4) version will handle the scenario when s-c-p fails or is not installed.