Bug 684861 - pkcon does not work correctly (outputs nothing useful) + fix
Summary: pkcon does not work correctly (outputs nothing useful) + fix
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: PackageKit
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Nils Philippsen
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-14 16:41 UTC by Ronald Wahl
Modified: 2012-06-20 14:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 14:24:22 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0913 0 normal SHIPPED_LIVE PackageKit bug fix update 2012-06-19 20:46:29 UTC

Description Ronald Wahl 2011-03-14 16:41:09 UTC
Description of problem:
pkcon does not work correctly - e.g. "pkcon repo-list" outputs only
Getting repositories          [=========================]         
Starting                      [=========================]         

Version-Release number of selected component (if applicable):
PackageKit-0.5.8-13.el6.x86_64

How reproducible:
always - when pygobject2 is not installed (its missing from requirements!)

Steps to Reproduce:
1. Install PackageKit
2. Make sure that pygobject2 is not installed
3. Call "pkcon repo-list"
  
Actual results:
Only some meta info and progress bars:

Expected results:
Meta info and progress bars + a list of repositories

Additional info:
The problem is just the missing requirement for pygobject2.

Additionally it would be clever to output an error message if something is missing. Strace showed me that there were some python tracebacks logged but I guess they just vanished somewhere.

Comment 2 Richard Hughes 2011-03-15 10:35:01 UTC
(In reply to comment #0)
> always - when pygobject2 is not installed (its missing from requirements!)

I don't think PackageKit actually requires pygobject2 -- it's possible yum requires pygobject2, which PackageKit uses, but the added dep would belong in yum I think.

> The problem is just the missing requirement for pygobject2.
> Additionally it would be clever to output an error message if something is
> missing. Strace showed me that there were some python tracebacks logged but I
> guess they just vanished somewhere.

Can you get the output of pkcon --verbose without pygobject2 installed please -- I'm surprised there isn't a backtrace. Thanks.

Comment 3 Ronald Wahl 2011-03-15 10:48:21 UTC
# pkcon --verbose repo-list 
TI:11:45:55     FI:egg-debug.c  FN:egg_debug_post_parse_hook,434
 - Verbose debugging 1 (on console 1)
TI:11:45:55     FI:pk-console.c FN:main,1344
 - filter=(null), filters=0
Getting repositories          [=========================]         
Starting                      [=========================]         

Tracing the running packagekitd shows:
# strace -f -e write -s 80 -p 9322
...
[pid  9397] write(2, "Traceback (most recent call last):\n", 35) = 35
[pid  9397] write(2, "  File \"/usr/share/PackageKit/helpers/yum/yumBackend.py\", line 53, in <module>\n", 79) = 79
[pid  9397] write(2, "    ", 4)         = 4
[pid  9397] write(2, "import gio\n", 11) = 11
[pid  9397] write(2, "ImportError", 11) = 11
[pid  9397] write(2, ": ", 2)           = 2
[pid  9397] write(2, "No module named gio", 19) = 19
[pid  9397] write(2, "\n", 1)           = 1
...

Comment 4 RHEL Program Management 2011-04-04 02:08:38 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 5 Richard Hughes 2011-08-18 09:55:19 UTC
Right, you're completely correct. I fixed the same bug in Fedora a few weeks ago. Adding a req for pygobject2 for PackageKit-yum is what we need to do.

Comment 10 errata-xmlrpc 2012-06-20 14:24:22 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0913.html


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