Bug 1199610

Summary: [abrt] gtg: notification.py:64:uinit_pynotify:NameError: global name 'pynotify' is not defined
Product: [Fedora] Fedora Reporter: Tim Waugh <twaugh>
Component: gtgAssignee: Ankur Sinha (FranciscoD) <sanjay.ankur>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: andreasfleig, f.semih.dundar, sanjay.ankur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b1d4493330026ecff8cbeff01863c9b7c86ff4b1
Whiteboard: abrt_hash:6840abe5f88acc0f6ea430e48ef6253acc7fbc69
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 12:56:51 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:
Attachments:
Description Flags
File: backtrace
none
File: environ
none
RPM spec patch
none
RPM spec patch none

Description Tim Waugh 2015-03-06 18:14:50 UTC
Description of problem:
This happens when closing gtg when python-notify is not installed.

Version-Release number of selected component:
gtg-0.3.1-4.fc21

Additional info:
reporter:       libreport-2.4.0
cmdline:        /usr/bin/python /usr/bin/gtg
dso_list:       python-libs-2.7.9-5.fc22.x86_64
executable:     /usr/bin/gtg
kernel:         4.0.0-0.rc1.git0.1.fc22.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
notification.py:64:uinit_pynotify:NameError: global name 'pynotify' is not defined

Traceback (most recent call last):
  File "/usr/lib64/python2.7/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/usr/lib/python2.7/site-packages/GTG/plugins/bugzilla/notification.py", line 64, in uinit_pynotify
    pynotify.uninit()
NameError: global name 'pynotify' is not defined

Local variables in innermost frame:

Potential duplicate: bug 1074757

Comment 1 Tim Waugh 2015-03-06 18:14:53 UTC
Created attachment 998983 [details]
File: backtrace

Comment 2 Tim Waugh 2015-03-06 18:14:55 UTC
Created attachment 998984 [details]
File: environ

Comment 3 Andreas Fleig 2015-07-24 18:33:11 UTC
Created attachment 1055865 [details]
RPM spec patch

Comment 4 Andreas Fleig 2015-07-24 18:40:36 UTC
Created attachment 1055866 [details]
RPM spec patch

Mixed up notify-python with python-inotify in changelog of previous patch

Comment 5 Fedora Update System 2015-12-23 12:42:48 UTC
gtg-0.3.1-8.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-030224ceb6

Comment 6 Fedora Update System 2015-12-25 01:58:13 UTC
gtg-0.3.1-8.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-8532b8f1f5

Comment 7 Fedora Update System 2015-12-30 20:57:20 UTC
gtg-0.3.1-8.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-030224ceb6

Comment 8 Fedora End Of Life 2016-07-19 12:56:51 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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
bug.

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