Bug 669867 - Missing dependecy qt-webkit while installing kchmviewer-qt
Summary: Missing dependecy qt-webkit while installing kchmviewer-qt
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kchmviewer
Version: 14
Hardware: i686
OS: Linux
low
low
Target Milestone: ---
Assignee: Robin Lee
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-15 08:18 UTC by Marcin
Modified: 2011-01-17 22:37 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-17 22:37:10 UTC
Type: ---


Attachments (Terms of Use)

Description Marcin 2011-01-15 08:18:08 UTC
Description of problem:
After installation of kchmviewer-qt only packages there is still missing dependecy lib libQtWebKit.so.4 from qt-webkit package.

Version-Release number of selected component (if applicable):
5.2.5.f14

How reproducible:
1. Installl clean standard GNOME Desktop version Fedora with no chm viewer at all.
2. Have installed only qt-4.7.1-7.fc14.i686 qt-sqlite-4.7.1-7.fc14.i686 qt-x11-4.7.1-7.fc14.i686

Steps to Reproduce:
1. Installl clean standard GNOME Desktop version Fedora with no chm viewer at all.
2. Have installed only qt-4.7.1-7.fc14.i686 qt-sqlite-4.7.1-7.fc14.i686 qt-x11-4.7.1-7.fc14.i686
3. Double click in GNOME some chm file, agree to automatic searching for package that can open this type of file.
4. Choose kchmviewer-qt package and install it with dependencies which are: kchmviewer-common and chmlib.
5. Try start kchmviewer-qt from desktop shortcut. Nothing happens.
6. Try start from terminal window ang get:
kchmviewer-qt: error while loading shared libraries: libQtWebKit.so.4: cannot open shared object file: No such file or directory
  
Actual results:
Dependency qt-webkit not installed with kchmviewer-qt package resulting in missing lib.

Expected results:
All dependecies required to run kchmviewer-qt binary installed.

Additional info:

Comment 1 Robin Lee 2011-01-15 12:44:51 UTC
That was strange. kchmviewer-qt requires libQtWebKit.so.4. You can run 'rpm -q --requires kchmviewer-qt' to see that.

Comment 2 Marcin 2011-01-15 20:40:29 UTC
(In reply to comment #1)
> That was strange. kchmviewer-qt requires libQtWebKit.so.4. You can run 'rpm -q
> --requires kchmviewer-qt' to see that.

Yes, indeed. But it happened. I checked second time and the result is the same. Maybe this bug should go to PackageKit ???

Comment 3 Robin Lee 2011-01-16 01:28:36 UTC
And what's the result if you use yum directly, like running 'sudo yum install kchmviewer-qt'?

Comment 4 Marcin 2011-01-17 20:37:40 UTC
(In reply to comment #3)
> And what's the result if you use yum directly, like running 'sudo yum install
> kchmviewer-qt'?

The same as through the GNOME way.
sudo yum install kchmviewer-qt

......

Running Transaction
  Installing     : kchmviewer-common-5.2-5.fc14.noarch                      1/3 
  Installing     : chmlib-0.40-3.fc14.i686                                  2/3 
  Installing     : kchmviewer-qt-5.2-5.fc14.i686                            3/3 

Installed:
  kchmviewer-qt.i686 0:5.2-5.fc14

Comment 5 Rex Dieter 2011-01-17 20:39:50 UTC
Fwiw, my f14/x86_64 vm pulled in qt-webkit via when doing 'yum install kchmviewer-qt'

Comment 6 Rex Dieter 2011-01-17 20:45:37 UTC
do you have any yum plugins that might be getting in the way here?

Does,
yum --noplugins install kchmviewer-qt
yield the same results?

Comment 7 Rex Dieter 2011-01-17 20:47:41 UTC
While we're at it,

rpm -q yum qt qt-webkit
rpm -q --whatprovides libQtWebKit.so.4

on the affected boxes

Comment 8 Marcin 2011-01-17 21:03:38 UTC
I found what has messed with dependecies. A rpm of PacketTracer from Cisco:

rpm -q --whatprovides libQtWebKit.so.4
PacketTracer-5.2.1-1.i386
qt-webkit-4.7.1-7.fc14.i686

After deinstalling PacketTracer installing kchmviewer-qt installs with qt-webkit dependency successfully.

The problem lies in this, that PacketTracer rpm provides libQtWebKit.so.4 but only in its installed tree.

Seems rpm deps resolution is not immune for this kind of buggy packages. :-(

Is it worth to submit bug to the rpm ??? Submitting it to the Cisco resolves problem with PAcketTracer, not with the resolution mechanism.

So...

thank Your for Your time

Regards
Marcin

Comment 9 Rex Dieter 2011-01-17 22:37:10 UTC
buggy PacketTracer is indeed the source of the problem here, not much we can do about it's bogus provides.


Note You need to log in before you can comment on or make changes to this bug.