Bug 558382
| Summary: | Yumex stopped working after last weeks updates complaining of no network conn. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Len <len> |
| Component: | yumex | Assignee: | Tim Lauridsen <tim.lauridsen> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 12 | CC: | joe, Per.t.Sjoholm, tim.lauridsen |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 2.9.7-1.fc12 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-02-11 14:50:02 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Len
2010-01-25 04:47:11 UTC
What network connection do you have ? please run 'yumex -d' in a termial an add the output in this report (In reply to comment #1) > What network connection do you have ? > > please run 'yumex -d' in a termial an add the output in this report I'm having the same issue on my desktop with Fedora 11, version 2.9.6 and a wired Ethernet connection. My laptop has Fedora 12, version 2.9.4 and works fine. Output from 'yumex -d' on the desktop follows: [joe@khorlia ~]$ 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_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) Not connected to an network DEBUG: Getting package lists - BEGIN Starting yum child process DEBUG: Initialize yum backend - BEGIN DEBUG: Using yum debuglevel = 2 YUM: Loaded plugins: dellsysidplugin2, fastestmirror, presto, protectbase No network connection, disable non local repo adobe-linux-i386 No network connection, disable non local repo fedora No network connection, disable non local repo livna No network connection, disable non local repo rpmfusion-free No network connection, disable non local repo rpmfusion-free-updates No network connection, disable non local repo rpmfusion-nonfree No network connection, disable non local repo rpmfusion-nonfree-updates No network connection, disable non local repo updates DEBUG: Initialize yum backend - END DEBUG: Sending command: get-packages args: ['updates', 'False'] YUM: Populating Package Cache YUM: Loading mirror speeds from cached hostfile YUM: getting packages - updates DEBUG: Yum Child Task: Command get-packages took 4.95 s to complete DEBUG: Sending command: get-packages args: ['available', 'False'] YUM: getting packages - available DEBUG: Yum Child Task: Command get-packages took 0.00 s to complete DEBUG: Sending command: get-packages args: ['installed', 'False'] YUM: getting packages - installed DEBUG: Getting package lists - END DEBUG: Getting Group information - BEGIN DEBUG: Getting Group information DEBUG: Yum Child Task: Command get-packages took 7.71 s to complete DEBUG: Sending command: get-groups args: [] YUM: Loading mirror speeds from cached hostfile YUM: No Groups Available in any repository DEBUG: Getting Group information - END DEBUG: Getting History Information - BEGIN DEBUG: Yum Child Task: Command get-groups took 0.00 s to complete DEBUG: Sending command: get-history args: [] History Disabled DEBUG: Getting History Information - END DEBUG: Yum Child Task: Command get-history took 0.00 s to complete DEBUG: Sending command: get-repos args: [] DEBUG: START: Getting updates packages DEBUG: START: Adding updates packages to view DEBUG: END: Getting updates packages DEBUG: Quiting the program !!! DEBUG: Yum Child Task: Command get-repos took 0.01 s to complete DEBUG: Sending command: exit args: [] Closing rpm db and releasing yum lock DEBUG: Forcing backend to close yum backend process is ended DEBUG: Backend reset completted [joe@khorlia ~]$ yumex-2.9.7-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/yumex-2.9.7-1.fc12 Why not Fedora 11? I has push it for Fedora 11 too, but forgot to add the bug numbers https://admin.fedoraproject.org/updates/yumex-2.9.7-1.fc11 yumex-2.9.7-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update yumex'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1383 I just updated to yumex 2.9.7 on Fedora 11, from fedora-updates-testing to try to work around another yum issue, but I'm still getting the error of not being connected to a network. However, I edited the Preferences, checked the box labeled Disable startup network check, restarted it and it works. I'll also report this at the feedback link you provided. yumex-2.9.7-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. yumex-2.9.7-1.fc12.noarch still has problem Not connected to an network Do you want to continue Yum does not work fine you can add 'disable_netcheck=1' in /etc/yumex.conf or run yum --disable-netcheck I configured network with system-config-network and stopped service NetworkManager With NetworkManager running yumex will not work(network is up). Not sure if problem is with NetworkManager or yumex or somewhere else. I would guess all 3. I do not use NetworkManager and long ago disabled it. Yumex on F 11 only works if I disable-netcheck. Yumex does not "work fine." I have made the check a little better upstream, so if NetworkManager is not running it will run as online, and only be offline if NetworkManager is running and is not connected. |