Bug 704051

Summary: [abrt] upnp-inspector-0.2.2-3.fc14: extract.py:121:_toggle_tar:AttributeError: 'Extract' object has no attribute 'email_button'
Product: [Fedora] Fedora Reporter: geminic86
Component: upnp-inspectorAssignee: Andrea Musuruane <musuruan>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: musuruan
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:dc20edad
Fixed In Version: upnp-inspector-0.2.2-5.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-19 21:55:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description geminic86 2011-05-12 00:25:36 UTC
abrt version: 1.1.18
architecture: i686
cmdline: /usr/bin/python /usr/bin/upnp-inspector
component: upnp-inspector
executable: /usr/bin/upnp-inspector
kernel: 2.6.35.13-91.fc14.i686
package: upnp-inspector-0.2.2-3.fc14
reason: extract.py:121:_toggle_tar:AttributeError: 'Extract' object has no attribute 'email_button'
release: Fedora release 14 (Laughlin)
time: 1305160138
uid: 500

backtrace
-----
extract.py:121:_toggle_tar:AttributeError: 'Extract' object has no attribute 'email_button'

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/upnp_inspector/extract.py", line 121, in _toggle_tar
    self.email_button.set_sensitive(w.get_active())
AttributeError: 'Extract' object has no attribute 'email_button'

Local variables in innermost frame:
self: <upnp_inspector.extract.Extract object at 0xa90f1ac>
w: <gtk.CheckButton object at 0xa919b1c (GtkCheckButton at 0xa9e7848)>

How to reproduce
-----
1.open
2.crash
3.

Comment 1 geminic86 2011-05-12 00:25:38 UTC
Created attachment 498416 [details]
File: backtrace

Comment 2 Andrea Musuruane 2011-06-04 15:25:55 UTC
I could reproduce this bug in the following way:

1. Open upnp-inspector
2. Right click on an upnp device
3. Select "extract device and service description"
4. Select "tar.gz" them

A bit more complex than you stated. 

I will report this upstream.

Comment 3 Andrea Musuruane 2011-06-04 15:31:17 UTC
Upstream bug report:
http://coherence.beebits.net/ticket/346

Comment 4 Fedora Update System 2011-08-05 15:58:19 UTC
upnp-inspector-0.2.2-5.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/upnp-inspector-0.2.2-5.fc16

Comment 5 Fedora Update System 2011-08-05 15:58:27 UTC
upnp-inspector-0.2.2-5.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/upnp-inspector-0.2.2-5.fc15

Comment 6 Fedora Update System 2011-08-05 15:58:37 UTC
upnp-inspector-0.2.2-5.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/upnp-inspector-0.2.2-5.fc14

Comment 7 Fedora Update System 2011-08-05 20:08:18 UTC
Package upnp-inspector-0.2.2-5.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing upnp-inspector-0.2.2-5.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/upnp-inspector-0.2.2-5.fc16
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2011-08-19 21:55:26 UTC
upnp-inspector-0.2.2-5.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2011-08-19 22:00:12 UTC
upnp-inspector-0.2.2-5.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2011-08-22 15:03:14 UTC
upnp-inspector-0.2.2-5.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.