Bug 914149

Summary: [abrt] yum-3.4.3-49.fc18: ibm-repository.py:91:show_message:Error: GDBus.Error:org.freedesktop.Notifications.MaxNotificationsExceeded: Exceeded maximum number of notifications
Product: [Fedora] Fedora Reporter: Kenneth MUHIA <kzmuhia>
Component: yumAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: admiller, ffesti, jzeleny, naipaul_ojar, packaging-team-maint, tim.lauridsen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:568f8f25bd820c792c5a85e1f5529ae6069b03eb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 19:23:41 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: core_backtrace
none
File: environ
none
File: smolt_data none

Description Kenneth MUHIA 2013-02-22 09:41:25 UTC
Version-Release number of selected component:
yum-3.4.3-49.fc18

Additional info:
cmdline:        /usr/bin/python /usr/bin/yum clean expire-cache
dso_list:       ibm-yum-plugins-0.19-13.fc18.noarch
executable:     /usr/bin/yum
kernel:         3.7.8-202.fc18.x86_64
uid:            0

Truncated backtrace:
ibm-repository.py:91:show_message:Error: GDBus.Error:org.freedesktop.Notifications.MaxNotificationsExceeded: Exceeded maximum number of notifications

Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 319, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 115, in main
    base.getOptionsConfig(args)
  File "/usr/share/yum-cli/cli.py", line 254, in getOptionsConfig
    self.conf
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1018, in <lambda>
    conf = property(fget=lambda self: self._getConfig(),
  File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 408, in _getConfig
    self.plugins.run('init')
  File "/usr/lib/python2.7/site-packages/yum/plugins.py", line 187, in run
    func(conduitcls(self, self.base, conf, **kwargs))
  File "/usr/lib/yum-plugins/ibm-repository.py", line 230, in init_hook
    if not test_intranet_connection(pc):
  File "/usr/lib/yum-plugins/ibm-repository.py", line 109, in test_intranet_connection
    show_message(pc, "Cannot reach IBM Intranet network. Please ensure you have an active IBM connection.", True)
  File "/usr/lib/yum-plugins/ibm-repository.py", line 91, in show_message
    n.show()
Error: GDBus.Error:org.freedesktop.Notifications.MaxNotificationsExceeded: Exceeded maximum number of notifications

Local variables in innermost frame:
closer: <function closer at 0x1e15938>
img: '/usr/share/pixmaps/oc-tux-critical.png'
pynotify: <module 'pynotify' from '/usr/lib64/python2.7/site-packages/gtk-2.0/pynotify/__init__.pyc'>
n: <pynotify.Notification object at 0x20e6c30 (NotifyNotification at 0x21f1620)>
pc: <yum.plugins.InitPluginConduit instance at 0x1db0ab8>
disable: True
disable_cb: <function disable_cb at 0x1e20c08>
msg: 'Cannot reach IBM Intranet network. Please ensure you have an active IBM connection.'
gobject: <module 'gobject' from '/usr/lib64/python2.7/site-packages/gobject/__init__.pyc'>
loop: <glib.MainLoop object at 0x7f475ea6bad0>

Comment 1 Kenneth MUHIA 2013-02-22 09:41:31 UTC
Created attachment 701054 [details]
File: backtrace

Comment 2 Kenneth MUHIA 2013-02-22 09:41:35 UTC
Created attachment 701055 [details]
File: core_backtrace

Comment 3 Kenneth MUHIA 2013-02-22 09:41:39 UTC
Created attachment 701056 [details]
File: environ

Comment 4 Kenneth MUHIA 2013-02-22 09:41:43 UTC
Created attachment 701057 [details]
File: smolt_data

Comment 5 Fedora End Of Life 2013-12-21 11:37:03 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 6 Fedora End Of Life 2014-02-05 19:23:41 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.