Description of problem: during start after login Version-Release number of selected component: fedmsg-notify-0.3.2-2.fc18 Additional info: cmdline: /usr/bin/python /usr/bin/fedmsg-notify-daemon dso_list: pygobject3-base-3.4.2-6.fc18.x86_64 executable: /usr/bin/fedmsg-notify-daemon kernel: 3.7.8-202.fc18.x86_64 uid: 1000 Truncated backtrace: types.py:47:function:GError: Przekroczono czas oczekiwania Traceback (most recent call last): File "/usr/bin/fedmsg-notify-daemon", line 9, in <module> load_entry_point('fedmsg-notify==0.3.2', 'console_scripts', 'fedmsg-notify-daemon')() File "/usr/lib/python2.7/site-packages/fedmsg_notify/daemon.py", line 197, in main service = FedmsgNotifyService() File "/usr/lib/python2.7/site-packages/fedmsg_notify/daemon.py", line 111, in __init__ Notify.Notification.new("fedmsg", "activated", "").show() File "/usr/lib64/python2.7/site-packages/gi/types.py", line 47, in function return info.invoke(*args, **kwargs) GError: Przekroczono czas oczekiwania Local variables in innermost frame: info: <gi.FunctionInfo object (show) at 0x0x38c29e0> args: (<Notification object at 0x38c85a0 (NotifyNotification at 0x38eaca0)>,) kwargs: {}
Created attachment 699338 [details] File: backtrace
Created attachment 699339 [details] File: core_backtrace
Created attachment 699340 [details] File: environ
fedmsg-notify-0.5.0-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fedmsg-notify-0.5.0-1.fc18
Package fedmsg-notify-0.5.0-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fedmsg-notify-0.5.0-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-2823/fedmsg-notify-0.5.0-1.fc18 then log in and leave karma (feedback).
after starts gnome Package: fedmsg-notify-0.3.2-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
fedmsg-notify-0.5.0-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
I have this bug with fedmsg-notify-0.5.0-1.fc18
Interesting... reopening. Pant, are you using the gnome-shell?
Yes i do! (So many bugs lately, but this is an other discussion )
I just hit this issue when having to manually restart the gnome shell. I have a feeling that when we port to GDBus this issue will be resolved, because we will be able to call wait_for_bus and ensure that things are properly instantiated before we try and fire off notifications.
*** Bug 984976 has been marked as a duplicate of this bug. ***
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.
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.