Bug 669582 - [abrt] yum-3.2.28-17.fc15: utils.py:127:show_lock_owner:TypeError: %d format: a number is required, not str
Summary: [abrt] yum-3.2.28-17.fc15: utils.py:127:show_lock_owner:TypeError: %d format:...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ded76039
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-14 03:00 UTC by ritz
Modified: 2018-04-11 08:26 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-02-08 17:09:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.78 KB, text/plain)
2011-01-14 03:00 UTC, ritz
no flags Details

Description ritz 2011-01-14 03:00:17 UTC
abrt version: 1.1.14
architecture: x86_64
cmdline: /usr/bin/python /usr/bin/yum -C search dconf-editor
component: yum
executable: /usr/bin/yum
kernel: 2.6.37-2.fc15.x86_64
package: yum-3.2.28-17.fc15
reason: utils.py:127:show_lock_owner:TypeError: %d format: a number is required, not str
release: Fedora release 15 (Rawhide)
time: 1294937899
uid: 500

backtrace
-----
utils.py:127:show_lock_owner:TypeError: %d format: a number is required, not str

Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 262, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 105, in main
    if show_lock_owner(e.pid, logger):
  File "/usr/share/yum-cli/utils.py", line 127, in show_lock_owner
    logger.critical(_("    State  : %s, pid: %d") % (ps['state'], pid))
TypeError: %d format: a number is required, not str

Local variables in innermost frame:
ago: '00:01'
nmsg: u'  The other application is: yum'
logger: <logging.Logger object at 0x2c85150>
pid: '4326'
ps: {'vmexe': '4', 'utrace': '0', 'vmswap': '0', 'uid': '500\t500\t500\t500', 'sigblk': '0000000000000000', 'vmpeak': '326680', 'vmpte': '668', 'cstime': 0, 'pid': '4326', 'vmlck': '0', 'sigq': '0/31481', 'sigpnd': '0000000000000000', 'capprm': '0000000000000000', 'vmlib': '19500', 'nonvoluntary_ctxt_switches': '43', 'tgid': '4326', 'cpus_allowed_list': '0-1', 'cpus_allowed': '3', 'state': u'Running', 'gid': '500\t500\t500\t500', 'capinh': '0000000000000000', 'ppid': '4188', 'vmrss': '19848', 'start_time': 1294937898, 'vmhwm': '19932', 'cutime': 0, 'capbnd': 'ffffffffffffffff', 'vmsize': '326660', 'shdpnd': '0000000000000000', 'tracerpid': '0', 'threads': '1', 'capeff': '0000000000000000', 'groups': '500', 'fdsize': '256', 'sigign': '0000000001001000', 'vmstk': '164', 'name': 'yum', 'mems_allowed_list': '0', 'vmdata': '12356', 'sigcgt': '0000000180000006', 'utime': 0, 'mems_allowed': '00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000001', 'voluntary_ctxt_switches': '1', 'stime': 0}

How to reproduce
-----
1. ran "yum -C search dconf-editor" as a regular user
2.
3.

Comment 1 ritz 2011-01-14 03:00:22 UTC
Created attachment 473465 [details]
File: backtrace

Comment 2 James Antill 2011-01-14 15:53:39 UTC
Patch posted upstream ... don't use -C as non-root will work around it for now.

Comment 3 Horst H. von Brand 2011-01-22 22:15:02 UTC
Package: yum-3.2.29-2.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Rawhide)


How to reproduce
-----
1. yum -y update --skip-broken
2.
3.


Comment
-----
Just updated the machine. Did some "rpm -qi" in the meantime.

Comment 4 Rahul Sundaram 2011-01-25 09:00:00 UTC
Package: yum-3.2.29-2.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Rawhide)


How to reproduce
-----
1.  yum -C search foo
2.
3.


Comment
-----
trying to search

Comment 5 Matěj Cepl 2011-02-07 09:56:26 UTC
This has probably complementary bug for F14 bug 661217.

Comment 6 James Antill 2011-02-08 17:09:27 UTC
I think this is fixed in the latest rawhide.


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