Bug 825109

Summary:	yumex-3.0.5-2.fc16 upgrade: Backend not running as expected (yumex will close)
Product:	[Fedora] Fedora	Reporter:	K. Deniz Ogut <kdenizogut>
Component:	yumex	Assignee:	Tim Lauridsen <tim.lauridsen>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	16	CC:	jim.swain, tim.lauridsen
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-09 05:17:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description K. Deniz Ogut 2012-05-25 07:02:10 UTC

Description of problem:
Today I started Yumex 3.0.4.1fc16 and realized just one update: yumex-3.0.5-2.fc16 . I performed it and exit Yumex. Then, I tried to start Yumex again to see the situation after the upgrade. It gave the error: Fatal error (I'm not sure of the expression, I'm re-translating this part from Turkish) and -in English-: "Backend not running as expected (yumex will close)". Then from the command line via yum I uninstalled Yumex and instaled it again. I got the same error. Then I undid all those changes one by one with the help of "yum history undo" command. Now I'm with the Yumex as before all these started and it functions. It still proposes me the update yumex-3.0.5-2.fc16. I'm not trying to do it once more.


Version-Release number of selected component (if applicable):
Yumex already at hand: 3.0.5-2.fc16 Yumex which is tried to be upgraded to: 3.0.4.1fc16


How reproducible:


Steps to Reproduce:
1. Have a machine with Fedora 16 and Yumex 3.0.4.1fc16
2. View the Yumex 3.0.4.1fc16 the update warning via Yumex and apply it.
3. Exit Yumex
4. Start Yumex
  
Actual results:

Yumex says: Fatal error[?] Backend not running as expected (yumex will close)

Expected results:

Yumex to function

Additional info:

I can create the situation again and send any info, output of some commands etc. if you ask me to do so and tell me the exact files, commans and so on.

Comment 1 K. Deniz Ogut 2012-05-25 07:27:01 UTC

Sorry, I copied and pasted the version numbers just the opposite in somewhere. Obviously it should be read as:

Version-Release number of selected component (if applicable):
Yumex already at hand: 3.0.4.1fc16 Yumex which is tried to be upgraded to: 3.0.5-2.fc16

Steps to Reproduce:
2. View the Yumex 3.0.5-2.fc16 update warning via Yumex and apply it.

Comment 2 Jim Swain 2012-05-27 01:00:53 UTC

I also tried the upgrade to Yumex 3.0.5-2.fc16 and observed the same error when attempting to exit yumex.  The upgraded version seems to confuse the shutting down of the yum backend as an error, rather than just a normal event in the shutdown process.  I have downgraded to the pre-existing version Yumex 3.0.4.1.fc16.

Comment 3 Tim Lauridsen 2012-06-06 12:45:54 UTC

works for me on F17 & RHEL6 (Don't have a F16 system anymore)

try running

/usr/bin/yumex -d in a console and attach the output to this report

Comment 4 Jim Swain 2012-06-06 16:18:46 UTC

(In reply to comment #3)
> works for me on F17 & RHEL6 (Don't have a F16 system anymore)
> 
> try running
> 
> /usr/bin/yumex -d in a console and attach the output to this report

This problem seems to have been corrected (due to other updates subsequent to initial report?)

-----

$ /usr/bin/yumex -d
09:13:35 : DEBUG - Current Yumex Settings:
09:13:35 : DEBUG -     autorefresh: True
09:13:35 : DEBUG -     branding_title: 'Yum Extender'
09:13:35 : DEBUG -     bugzilla_url: 'https://bugzilla.redhat.com/show_bug.cgi?id='
09:13:35 : DEBUG -     color_downgrade: 'goldenrod'
09:13:35 : DEBUG -     color_install: 'darkgreen'
09:13:35 : DEBUG -     color_normal: 'black'
09:13:35 : DEBUG -     color_obsolete: 'blue'
09:13:35 : DEBUG -     color_update: 'red'
09:13:35 : DEBUG -     debug: True
09:13:35 : DEBUG -     disable_netcheck: False
09:13:35 : DEBUG -     disable_repo_page: False
09:13:35 : DEBUG -     history_limit: 15
09:13:35 : DEBUG -     no_gpg_check: False
09:13:35 : DEBUG -     plugins: True
09:13:35 : DEBUG -     proxy: ''
09:13:35 : DEBUG -     recentdays: 14
09:13:35 : DEBUG -     repo_exclude: ['debug', 'source']
09:13:35 : DEBUG -     show_newest_only: True
09:13:35 : DEBUG -     skip_broken: False
09:13:35 : DEBUG -     typeahead_search: False
09:13:35 : DEBUG -     use_sortable_view: False
09:13:35 : DEBUG -     use_sudo: False
09:13:35 : DEBUG -     win_height: 987
09:13:35 : DEBUG -     win_sep: 427
09:13:35 : DEBUG -     win_width: 1918
09:13:35 : DEBUG -     yum_conf: '/etc/yum.conf'
09:13:35 : DEBUG -     yumdebuglevel: 2
/usr/lib/python2.7/site-packages/guihelpers/__init__.py:256: GtkWarning: gtk_scrolled_window_add(): cannot add non scrollable widget use gtk_scrolled_window_add_with_viewport() instead
  self.add_from_file(filename)
org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
09:13:35 : INFO - Can't detect the network connection state
09:13:35 : DEBUG - Getting package lists - BEGIN   <yumexgui.populate_package_cache>
org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
09:13:35 : INFO - Starting yum child process
09:13:35 : DEBUG - Initialize yum backend - BEGIN   <yum_backend.setup>
09:13:35 : DEBUG - Setup START   <yum_backend.setup>
09:13:43 : DEBUG - Command to run : /usr/share/yumex/yum_childtask.py 2 True False /etc/yum.conf   <yum_backend.setup>
09:13:43 : DEBUG - LAUNCHER: Ready for commands   <yum_backend._check_for_message>
09:13:43 : DEBUG - Sending: #run args: ['UycvdXNyL3NoYXJlL3l1bWV4L3l1bV9jaGlsZHRhc2sucHkgMiBUcnVlIEZhbHNlIC9ldGMveXVtLmNvbmYnCnAwCi4=']   <yum_backend._send_command>
09:13:43 : DEBUG - Setup END   <yum_backend.setup>
09:13:43 : DEBUG - LAUNCHER - Starting : /usr/share/yumex/yum_childtask.py 2 True False /etc/yum.conf   <yum_backend._check_for_message>
09:13:43 : DEBUG - Using yum debuglevel = 2   <yum_backend._check_for_message>
09:13:43 : INFO - YUM: Yum Version : 3.4.3
09:13:43 : INFO - YUM: Loaded plugins: presto
09:13:43 : DEBUG - Initialize yum backend - END   <yum_backend.setup>
09:13:43 : DEBUG - Getting package lists - END   <yumexgui.populate_package_cache>
09:13:43 : DEBUG - Sending: get-repos args: []   <yum_backend._send_command>
09:13:44 : DEBUG - START: Getting updates packages   <yumexgui.on_packageFilter_changed>
09:13:44 : DEBUG - get-repos Args: ['']  took 0.00 s to complete   <yumexbackend.yum_server>
09:13:44 : DEBUG - Sending: get-packages args: ['updates', 'False']   <yum_backend._send_command>
09:13:44 : INFO - Getting available updates
09:13:45 : DEBUG - got 0 packages from yum backend   <yum_backend.get_packages>
09:13:45 : INFO - 0 packages returned
09:13:45 : DEBUG - get-packages Args: ['updates', 'False']  took 1.59 s to complete   <yumexbackend.yum_server>
09:13:45 : DEBUG - Sending: get-packages args: ['obsoletes', 'False']   <yum_backend._send_command>
09:13:46 : INFO - Getting available obsoletes
09:13:46 : DEBUG - got 0 packages from yum backend   <yum_backend.get_packages>
09:13:46 : INFO - 0 packages returned
09:13:46 : INFO - Adding Packages to view
09:13:46 : DEBUG - START: Adding updates & obsoletes packages to view   <yumexgui._add_packages>
09:13:46 : INFO - Added 0 Packages to view
09:13:46 : DEBUG - END: Getting updates packages   <yumexgui.on_packageFilter_changed>
09:14:06 : DEBUG - Quiting the program !!!   <yum_backend.quit>
09:14:06 : DEBUG - get-packages Args: ['obsoletes', 'False']  took 0.00 s to complete   <yumexbackend.yum_server>
09:14:06 : DEBUG - Sending: exit args: []   <yum_backend._send_command>
09:14:06 : INFO - Closing rpm db and releasing yum lock
09:14:06 : DEBUG - :end   <yum_backend.reset>
09:14:06 : INFO - yum backend process is ended
09:14:06 : DEBUG - LAUNCHER: Ready for commands   <yum_backend._check_for_message>
09:14:06 : DEBUG - Sending: #exit args: []   <yum_backend._send_command>
09:14:06 : DEBUG - LAUNCHER : Terminating   <yum_backend._check_for_message>
09:14:06 : DEBUG - &exit   <yum_backend._close>
09:14:08 : DEBUG - Forcing backend to close   <yum_backend._close>
09:14:08 : DEBUG - Backend reset completed   <yum_backend.quit>

Comment 5 K. Deniz Ogut 2012-06-08 07:19:36 UTC

As being the original reporter, I can confirm that this bug is no more valid. After submitting the report, I was applying all the updates but the yumex update in question. After the last two comments, I applied it as well and yumex works in a normal fashion. I don't know what update fixed the issue because there was an amount of them.