Bug 735823

note that according to 
https://fedoraproject.org/wiki/Features/AutomaticPrintDriverInstallation
the driver search is based on RPM "provides" feature

I took a look at the foomatic-db-ppds package, and it provides things like
"postscriptdriver(savin;pro_1106ex;)"

- the format is a bit different than the string passed to InstallPrinterDrivers

it'd be nice if the error message is enhanced like:

"Could not find printer driver in any configured software source. No package provides 'postscriptdriver(canon;adv_c5030;)'."

(um, I've just made up the provides string, I really don't know what is correct for that printer)

I believe that KPackageKit ought not to be showing this message at all due to the 'hide-finished' option being specified.

Are you sure that "hide-finished" is also supposed to hide errors, not just success messages?

Richard Hughes (CC'd): what do you think about this?  Is "no available package" an error here, and if so, should "hide-finished" hide errors?  If not, is there another option that I should use?

It all works as expected with gnome-packagekit.

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

still valid

the actual console output:


$ system-config-printer
WARNING: gnome-keyring:: couldn't connect to: /home/kvolny/.cache/keyring-FGrcnB/pkcs11: No such file or directory
PASSTHRU
'\x00'
ps
'\x00'
lp
'\x00'
PORT1
'\x00'

'\x00'
LPT0
'\x00'
LPT0_PASSTHRU
'\x00'
COM0
'\x00'
COM0_PASSTHRU
'\x00'
LPT1
'\x00'
LPT1_PASSTHRU
'\x00'
COM1
'\x00'
COM1_PASSTHRU
'\x00'
LPT2
'\x00'
LPT2_PASSTHRU
'\x00'
COM2
'\x00'
COM2_PASSTHRU
'\x00'
LPT3
'\x00'
LPT3_PASSTHRU
'\x00'
COM3
'\x00'
COM3_PASSTHRU
'\x00'
LPT4
'\x00'
LPT4_PASSTHRU
'\x00'
COM4
'\x00'
COM4_PASSTHRU
'\x00'
LPT5
'\x00'
LPT5_PASSTHRU
'\x00'
COM5
'\x00'
COM5_PASSTHRU
'\x00'
LPT6
'\x00'
LPT6_PASSTHRU
'\x00'
COM6
'\x00'
COM6_PASSTHRU
'\x00'
LPT7
'\x00'
LPT7_PASSTHRU
'\x00'
COM7
'\x00'
COM7_PASSTHRU
'\x00'
pr0
'\x00'
pr1
'\x00'
pr2
'\x00'
pr3
'\x00'
pr4
'\x00'
pr5
'\x00'
pr6
'\x00'
pr7
'\x00'
pr8
'\x00'
pr9
'\x00'
pr10
'\x00'
pr11
'\x00'
pr12
'\x00'
pr13
'\x00'
pr14
'\x00'
pr15
'\x00'
pr16
'\x00'
pr17
'\x00'
pr18
'\x00'
pr19
'\x00'
pr20
'\x00'
pr21
'\x00'
pr22
'\x00'
pr23
'\x00'
pr24
'\x00'
pr25
'\x00'
pr26
'\x00'
pr27
'\x00'
pr28
'\x00'
pr29
'\x00'
pr30
'\x00'
pr31
'\x00'
pr32
'\x00'
pr33
'\x00'
pr34
'\x00'
pr35
'\x00'
pr36
'\x00'
pr37
'\x00'
pr38
'\x00'
pr39
'\x00'
pr40
'\x00'
pr41
'\x00'
pr42
'\x00'
pr43
'\x00'
pr44
'\x00'
pr45
'\x00'
pr46
'\x00'
pr47
'\x00'
pr48
'\x00'
pr49
'\x00'
Caught non-fatal exception.  Traceback:
File "/usr/share/system-config-printer/probe_printer.py", line 253, in _do_find
    fn ()
File "/usr/share/system-config-printer/probe_printer.py", line 365, in _probe_hplip
    stderr=null)
File "/usr/lib64/python2.7/subprocess.py", line 679, in __init__
    errread, errwrite)
File "/usr/lib64/python2.7/subprocess.py", line 1249, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory
Continuing anyway..
Caught non-fatal exception.  Traceback:
File "/usr/share/system-config-printer/probe_printer.py", line 410, in _probe_smb
    smbc_auth.failed (e)
File "/usr/share/system-config-printer/pysmb.py", line 182, in failed
    raise exc
TimedOutError: (110, 'Connection timed out')
Continuing anyway..
ERROR:dbus.proxies:Introspect error on :1.194:/org/freedesktop/PackageKit: dbus.exceptions.IntrospectionParserException: Error parsing introspect data: <class 'xml.parsers.expat.ExpatError'>: unbound prefix: line 5, column 4

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

system-config-printer-1.4.1-7.fc19.x86_64

the output is very similar, still can't install the driver automagically

...
pr39
'\x00'
pr40
timed out
ERROR:dbus.proxies:Introspect error on :1.2:/org/freedesktop/PackageKit: dbus.exceptions.IntrospectionParserException: Error parsing introspect data: <class 'xml.parsers.expat.ExpatError'>: unbound prefix: line 5, column 4
No ID match for device socket://10.34.22.1:
MFG:Canon;MDL:iR-ADV C5030/5035 (UFR II);CMD:LIPSLX,PS,PostScript,PCL,PJL,CPCA,1284.4-2000;DES:Canon iR-ADV C5030/5035;
No ID match for device socket://10.34.22.1:9100:
MFG:Canon;MDL:iR-ADV C5030/5035 (UFR II);CMD:LIPSLX,PS,PostScript,PCL,PJL,CPCA,1284.4-2000;DES:Canon iR-ADV C5030/5035;

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.