RPM reports dependency problems because it looks in its own database, not on the files on disk you have. Also, when you install a lib, you should run as root ‘ldconfig’ (without quotes) to update the linker information. Often but not always, .so.0 is a symlink to .so and if it’s not there, the linker will create it when ldconfig is ran
libglade.so.0 is actually very old, from the times of earlier GTK1 and is provided by the package gtk1-compat-devel
What about making a symlink called libglade.so.0 to libglade.so, running ldconfig, forcing install of that one RPM package with --nodeps and then trying to run the software? It could work but there are no guarantees. I’ve done it in the past for some old programs where I couldn’t find a specific lib version for them and some worked while another ones just bugged out
That file went out with SUSE 9.1. It’s libglad-0.x. And the others are old to. This is why rpm is reporting them not found. They are not on your system, nor should they be. The current libglade package is libglade2. Now as to your cannon i250 driver, try here OpenPrinting database - Printer: Canon i250
I tried looking in YaST, and your printer was not there. I also tried cups.org and looking for the driver there. No luck.
You could force the rpm, but then the driver may not work, or if it does, features wont work. Compiling will likely bomb out for the same reasons. Your dealing with old files and old dependencies. Last time I saw this working was 3 years ago.
Rpm has it’s own database, found in /var. Just cause you link one file to another, doesn’t mean you change the rpm database. This is one of the problems with rpm. If you installed an app via source, you’d have the exact same issue that you are experiencing with rpm. That is to say, rpm would not be aware of it.