Bug 1242055

Summary: yumex-dnf crashes at startup if networking isn't availabe
Product: [Fedora] Fedora Reporter: Giulio 'juliuxpigface' <juliux.pigface>
Component: yumex-dnfAssignee: Tim Lauridsen <tim.lauridsen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 23CC: tim.lauridsen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-06 13:43:56 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:
Attachments:
Description Flags
traceback messages from yumex-dnf none

Description Giulio 'juliuxpigface' 2015-07-10 19:11:56 UTC
Created attachment 1050778 [details]
traceback messages from yumex-dnf

Description of problem:
I'm unable to start yumex-dnf on Fedora Nightly 20150704 (Mate spin) whenever the connection is taken down.

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

How reproducible:
Happens every time I try to reproduce it.

Steps to Reproduce:
1. Disable the networking via the nm-applet.
2. Launch yumex-dnf from the system menu.

Actual results:
1. yumex-dnf crashes and shows an untitled dialog displaying the exceptions I'm attaching.

Expected results:
1. yumex-dnf should warn the user that the net isn't working and should exit cleanly.

Additional info:
I'm testing inside a qemu-kvm guest. abrt can't collect the information to generate the report, but the reason it displays is 'pos() takes 2 positional arguments but 4 were given'.

Comment 1 Tim Lauridsen 2015-10-06 13:43:56 UTC

*** This bug has been marked as a duplicate of bug 1257609 ***