Bug 856319 - [abrt] mailnag-0.4.2-2.fc17: types.py:43:function:GError: Error calling StartServiceByName for org.freedesktop.Notifications: The connection is closed
Summary: [abrt] mailnag-0.4.2-2.fc17: types.py:43:function:GError: Error calling Start...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mailnag
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Thorsten Leemhuis
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e58ea161962de9879fbd643544f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-11 18:50 UTC by Calvin Smith
Modified: 2013-08-01 00:24 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 00:24:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: core_backtrace (505 bytes, text/plain)
2012-09-11 18:50 UTC, Calvin Smith
no flags Details

Description Calvin Smith 2012-09-11 18:50:22 UTC
Description of problem:
Attempted to start mailnag. I guess this is the error I get when it attempts to connect?

Version-Release number of selected component:
mailnag-0.4.2-2.fc17

Additional info:
libreport version: 2.0.13
abrt_version:   2.0.12
cmdline:        python /usr/share/mailnag/Mailnag/mailnag.py
kernel:         3.5.3-1.fc17.x86_64

backtrace:
:types.py:43:function:GError: Error calling StartServiceByName for org.freedesktop.Notifications: The connection is closed
:
:Traceback (most recent call last):
:  File "/usr/share/mailnag/Mailnag/mailnag.py", line 144, in <module>
:    if __name__ == '__main__': main()
:  File "/usr/share/mailnag/Mailnag/mailnag.py", line 107, in main
:    mailchecker.check(accounts)
:  File "/usr/share/mailnag/Mailnag/daemon/mailchecker.py", line 97, in check
:    self._notify_single(new_mails)
:  File "/usr/share/mailnag/Mailnag/daemon/mailchecker.py", line 147, in _notify_single
:    n.show()
:  File "/usr/lib64/python2.7/site-packages/gi/types.py", line 43, in function
:    return info.invoke(*args, **kwargs)
:GError: Error calling StartServiceByName for org.freedesktop.Notifications: The connection is closed
:
:Local variables in innermost frame:
:info: <gi.FunctionInfo object (show) at 0x0x7f78cd818098>
:args: (<Notification object at 0x438ca50 (NotifyNotification at 0x436d440)>,)
:kwargs: {}

Comment 1 Calvin Smith 2012-09-11 18:50:26 UTC
Created attachment 611887 [details]
File: core_backtrace

Comment 2 Fedora End Of Life 2013-07-03 22:28:23 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 17'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 3 Fedora End Of Life 2013-08-01 00:24:58 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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


Note You need to log in before you can comment on or make changes to this bug.