Bug 1257609 - Yumex error when refreshing metada without network connection
Yumex error when refreshing metada without network connection
Product: Fedora
Classification: Fedora
Component: yumex-dnf (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Tim Lauridsen
Fedora Extras Quality Assurance
: 1242055 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2015-08-27 08:44 EDT by kakoskin
Modified: 2016-12-20 09:29 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 09:29:23 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description kakoskin 2015-08-27 08:44:29 EDT
Description of problem:
Start Yumex-dnf without network connection. If metadata needs to be refreshed, yumex-dnf opens a dialog with a backtrace. Closing dialog closes also Yumex-dnf.

Version-Release number of selected component (if applicable):
yumex-dnf: 4.1.3-2.fc23 
dnfdaemon: 0.3.9-2.fc23

How reproducible:

Steps to Reproduce:
1. Ensure you have no network.
2. dnf clean all
3. Run yumex-dnf

Actual results:
Dialog with backtrace:
g-io-error-quark: GDBus.Error:org.freedesktop.DBus.Python.dnf.exceptions.RepoError: Traceback (most recent call last):
  File "/usr/lib/python3.4/site-packages/dnf/repo.py", line 205, in perform
    return super(_Handle, self).perform(result)
  File "/usr/lib64/python3.4/site-packages/librepo/__init__.py", line 1425, in perform
    _librepo.Handle.perform(self, result)
librepo.LibrepoException: (8, "Cannot prepare internal mirrorlist: Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f23&arch=x86_64 [Could not resolve host: mirrors.fedoraproject.org]", 'An Curl handle error')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.4/site-packages/dnf/repo.py", line 795, in load
    if self._try_revive():
  File "/usr/lib/python3.4/site-packages/dnf/repo.py", line 709, in _try_revive
  File "/usr/lib/python3.4/site-packages/dnf/repo.py", line 209, in perform
    raise _DetailedLibrepoError(exc, source)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib64/python3.4/site-packages/dbus/service.py", line 826, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "/usr/lib/python3.4/site-packages/dnfdaemon/server/__init__.py", line 83, in newFunc
    rc = func(*args, **kwargs)
  File "/usr/share/dnfdaemon/dnfdaemon-system", line 205, in SetConfig
    rc = self.set_option(setting, value)
  File "/usr/lib/python3.4/site-packages/dnfdaemon/server/__init__.py", line 696, in set_option

Expected results:
A dialog reporting network failure.
Comment 1 Tim Lauridsen 2015-10-06 05:11:56 EDT
I will look into making yumex-dnf handle this i a better way.

added an upstream issue, to track the development.

Comment 2 Tim Lauridsen 2015-10-06 09:43:56 EDT
*** Bug 1242055 has been marked as a duplicate of this bug. ***
Comment 3 Fedora End Of Life 2016-11-24 07:23:27 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 kakoskin 2016-11-24 07:27:22 EST
I am not seeing this in Fedora 25.
Comment 5 Fedora End Of Life 2016-12-20 09:29:23 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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