Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 18192 - kpackage crashes when listing file
kpackage crashes when listing file
Product: Red Hat Linux
Classification: Retired
Component: kpackage (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Depends On:
  Show dependency treegraph
Reported: 2000-10-03 03:47 EDT by Need Real Name
Modified: 2008-05-01 11:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-10-05 06:00:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2000-10-03 03:47:10 EDT
I installed RH7.0 and the kpackage RPM.  It works fine to list
all the installed packages on the system, but when i select a package
and want to list the files which compose it, the program just crashes
without saying anything.
Comment 1 Christian Schultes 2000-10-05 06:00:50 EDT
I have the same problem described above.

When i start kpackage from the xterm i got the following Message:
  rpmTagTable has different size in shared object. consider relinking
then, kpackages starts, but when i want to view the filelist it crashes.
Comment 2 Ngo Than 2000-10-11 10:01:50 EDT
It's fixed in kpackage-1.3.10-6. You find it in rawhide
Comment 3 Rocky Pope 2000-10-26 12:21:11 EDT
Is this file still on Rawhide server?  I could not locate it.  I need this file since kpackage shows the sames symptoms as the others mentioned.  Also, if I 
select a package and select uninstall, kpackage reports the package isn't installed, which is incorrect.


Rocky Pope
Comment 4 Ngo Than 2000-10-30 04:48:51 EST
i will make errata for kpackage-1.3.10-7 today. You will find it
under ftp://ftp.redhat.com/pub/redhat/updates/powertools/7.0/i386/

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