libgnutls.so.13 with cups and system-config-printer

[bd54338rre]

i am upgraded from fc9 to fc10 using upgrade methode, no clean install

i am not able to start system-config-printer, by kmenu>administration>printing,
so i can not print, because the printer has been disabled. It worked on fc9.

it simply does not start

using terminal also not:
[root@localhost ~]# system-config-printer
Traceback (most recent call last):
File "/usr/share/system-config-printer/system-config-printer.py", line 56, in <module>
import cups
ImportError: libgnutls.so.13: cannot open shared object file: No such file or directory


cups shows a related error during startup.

i have got gnutls:
[root@localhost ~]# rpm -q gnutls
gnutls-2.4.2-2.fc10.i386

help pls.

[Seve]

Hello:
Can you post the output of:

rpm -aq | grep system-config-printer |sort

Seve

[bd54338rre]

@localhost ~]$ rpm -aq | grep system-config-printer |sort
system-config-printer-1.0.9-1.fc10.i386
system-config-printer-libs-1.0.9-1.fc10.i386

and as root:
[evert@localhost ~]$ sudo rpm -aq | grep system-config-printer |sort
[sudo] password for evert:
system-config-printer-1.0.9-1.fc10.i386
system-config-printer-libs-1.0.9-1.fc10.i386

[Seve]

Hello:
Try

yum update system-config-printer system-config-printer-libs

The current package is 1.0.12-2.fc10

You might also consider updating the rest of your system as well.

Seve

[bd54338rre]

i already updated the system by yum.

@localhost ~]$ rpm -aq | grep system-config-printer |sort
system-config-printer-1.0.12-3.fc10.i386
system-config-printer-libs-1.0.12-3.fc10.i386

i updated these packages by downloading the rpm's
still the same problem

[jigarshah]

Same here...
Any solution ?

[domlayfield]

I just updated from F9 to F10, and encountered the same error.

The problem is not system-config-printer -- that's just a python script, and doesn't have any intrinsic library dependencies.

That dependency comes from /usr/lib/libcups.so.2 (from package cups-libs).

Make sure you've updated the cups packages too.

Of course, why the F10 installer didn't do that (which it certainly should have) is a whole other issue...