Bug 1242055 - yumex-dnf crashes at startup if networking isn't availabe
Summary: yumex-dnf crashes at startup if networking isn't availabe
Keywords:
Status: CLOSED DUPLICATE of bug 1257609
Alias: None
Product: Fedora
Classification: Fedora
Component: yumex-dnf
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Tim Lauridsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-10 19:11 UTC by Giulio 'juliuxpigface'
Modified: 2015-10-06 13:43 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-10-06 13:43:56 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
traceback messages from yumex-dnf (2.80 KB, text/plain)
2015-07-10 19:11 UTC, Giulio 'juliuxpigface' 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.