Description of problem: Yumex reports backend not running as expected and closes Version-Release number of selected component (if applicable): How reproducible: Launch Yumex and enter root password get message Steps to Reproduce: 1. Launch Yum Extender 2. enter root password 3. Get failure message Actual results: Yumex fails to launch Expected results: to be able to use yumex Additional info: Ran yumex -d from cli got this: yumex -d running Current Settings autorefresh: True branding_title: 'Yum Extender NextGen' color_install: 'darkgreen' color_normal: 'black' color_obsolete: 'blue' color_update: 'red' debug: True disable_netcheck: False disable_repo_page: False history_limit: 15 plugins: True proxy: '' recentdays: 14 repo_exclude: ['debug', 'source'] win_height: 600 win_sep: 300 win_width: 1000 yumdebuglevel: 2 /usr/lib/python2.6/site-packages/guihelpers/__init__.py:199: GtkWarning: gtk_scrolled_window_add(): cannot add non scrollable widget use gtk_scrolled_window_add_with_viewport() instead self.add_from_file(filename) eth0 (e100) is connected /usr/lib/python2.6/site-packages/yumexgui/gui.py:178: DeprecationWarning: Use the new widget gtk.Tooltip self.tooltip = gtk.Tooltips() /usr/lib/python2.6/site-packages/yumexgui/gui.py:205: DeprecationWarning: Use the new widget gtk.Tooltip self.tooltip.set_tip(button, tooltip) eth0 (e100) is connected Connected to an network DEBUG: Getting package lists - BEGIN eth0 (e100) is connected Starting yum child process DEBUG: Initialize yum backend - BEGIN DEBUG: Using yum debuglevel = 2 YUM: Loaded plugins: auto-update-debuginfo, presto, remove-with-leaves, rhnplugin, YUM: Traceback (most recent call last): YUM: File "/usr/share/yumex/yumex-yum-backend", line 61, in <module> YUM: my = YumServer(debuglevel, plugins, offline, repos) YUM: File "/usr/lib/python2.6/site-packages/yumexbackend/yum_server.py", line 202, in __init__ YUM: self.doLock() YUM: File "/usr/lib/python2.6/site-packages/yumexbackend/yum_server.py", line 271, in doLock YUM: yum.YumBase.doLock(self) YUM: File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 1377, in doLock YUM: if self.conf.uid != 0: YUM: File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 778, in <lambda> YUM: conf = property(fget=lambda self: self._getConfig(), YUM: File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 310, in _getConfig ERROR: Fatal Error : backend-not-running ERROR: backend not running as expected (yumex will close) DEBUG: Quiting the program !!! yum backend process is ended DEBUG: Backend reset completted Program Terminated
If additional information is needed please give instructions on how to get, where to get it,and what is needed. Thanks
Why are you running the rhnplugin, it don't do you much good in fedora, it is for RHEL. Please disable it and try again. Dont yum work at the command line (Try 'yum list updates' as root)
(In reply to comment #2) > Why are you running the rhnplugin, it don't do you much good in fedora, it is > for RHEL. Please disable it and try again. ok if I run 'yum --disableplugin= rhnplugin' without the quotes and as root it doesn't get disabled. > Dont yum work at the command line (Try 'yum list updates' as root) yum does work from cli. I ran yum upgrade before I posted this bug and it did that. I can run software updater (PackageKit, PUP, or Pirut... What ever it's called in F12) without errors also.
could you please try running 'yumex -d --debuglevel=9'
(In reply to comment #4) > could you please try running 'yumex -d --debuglevel=9' I just removed the RHN plugin and Yumex is working again. This can be closed. If you want to find why it is killing Yumex with the RHN plugin just install the plugin and try launching Yumex.
where have you got the RHN plugin from ?, it is not part of fedora, but part of RHEL.
Created attachment 421902 [details] Screen shot of rhnplugin as displayed by Yumex
Created attachment 421903 [details] repos viewed by Yumex
(In reply to comment #6) > where have you got the RHN plugin from ?, it is not part of fedora, but part of > RHEL. I have attached screen shots of what yumex tells me I have for repos and where yumex shows the repo from. If you need me to run a command to help find the actual way I got the rhnplugin as an available package or something let me know.
ok, I see, there is a rhn-plugin in fedora, to use against custom RHN server. I will check it out to see why it fails with yumex
Created attachment 422579 [details] fix yum-rhn-plugin issue, with a blank OptionParser object from yum
I have added a proposed to the rnh-plugin, to not blow up running with a yum api user like yumex.
Fixed in spacewalk.git in commit f3fbab86131955dfc5fc162aed47c8da474f0e5c
Fixed in yum-rhn-plugin-1.1.3-1.fc14
Thanks !