Red Hat Bugzilla – Bug 229523
Exception Occurred at Yumex startup
Last modified: 2007-11-30 17:11:57 EST
Description of problem:
Installed Yumex 1.2.2 and set proxy to correct settings. Restarted Yumex and get
Version-Release number of selected component (if applicable):
Start Yumex with proxy configured.
Steps to Reproduce:
1. Applications, System Tools, Yumex
2. Application loads repostitories, then crashes.
Summary: TB03120a34 yumexmain.py:1045:_runBackground:TypeError: iterable
Traceback (most recent call last):
File "/usr/share/yumex/yumexmain.py", line 1108, in ?
mainApp = YumexMainApplication()
File "/usr/share/yumex/yumexmain.py", line 541, in __init__
File "/usr/share/yumex/yumexmain.py", line 990, in setup_yum
File "/usr/share/yumex/yumexmain.py", line 1045, in _runBackground
TypeError: iterable argument required
Local variables in innermost frame:
runfunc: <bound method yumexBase.set_active_repos of <yumex.yumexBase.yumexBase
object at 0xd01910>>
args: (['core', 'extras', 'updates'],)
self: <__main__.YumexMainApplication instance at 0xcf6518>
Should allow me to update, install or whatever. Have yet to see what application
Additional info: running AMD Turion64 and Fedora Core 6, x86-64.
Created attachment 148520 [details]
this is the debug traceback text
Ok, I was able to reporoduce the problem you're having. This is defintely a
Yumex bug and I'll try to patch it today. For now, you can workaround this
problem by specifying the protocol in your proxy setting:
Assuming that the proxy server address you entered was somepoxy.com, make sure
that you specify the protocol by adding "http://" before it:
http://someproxy.com You can change this in /etc/yumex.conf file.
I have just committed the fix to SVN repo so it should be fixed in the next
release of yumex-1.2.x
Thanks Dawid, for fixing the issue for yumex 1.2.x, can you added the changes to
*** Bug 237785 has been marked as a duplicate of this bug. ***
Tim, this issue doesn't seem to apply to 1.9.X branch - at least I couldn't
reproduce because it doesn't crash no matter what the proxy addreess in