Bug 919639

Summary: [abrt] fedmsg-notify-0.5.0-1.fc19: connection.py:651:call_blocking:DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.942 was not provided by any .service files
Product: [Fedora] Fedora Reporter: Dan Mashal <dan.mashal>
Component: fedmsg-notifyAssignee: Luke Macken <lmacken>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: lmacken, peter_daemon, pfrields, rbean, rebus, w.isaac.cortes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:72e009e71f5486b8c92604cf6e722808577faa56
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 14:50:39 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

Description Dan Mashal 2013-03-09 05:09:00 UTC
Description of problem:
Turned notifications on and off too many times too quickly. ;)

Version-Release number of selected component:
fedmsg-notify-0.5.0-1.fc19

Additional info:
cmdline:        /usr/bin/python /usr/bin/fedmsg-notify-config
dso_list:       dbus-python-1.1.1-3.fc19.x86_64
executable:     /usr/bin/fedmsg-notify-config
kernel:         3.9.0-0.rc1.git0.4.fc19.x86_64
uid:            1000

Truncated backtrace:
connection.py:651:call_blocking:DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.942 was not provided by any .service files

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/fedmsg_notify/gui.py", line 178, in activate_cb
    self.toggle_service(button.get_active())
  File "/usr/lib/python2.7/site-packages/fedmsg_notify/gui.py", line 198, in toggle_service
    notify_iface.Disable()
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.942 was not provided by any .service files

Local variables in innermost frame:
byte_arrays: False
self: <dbus._dbus.SessionBus (session) at 0x7fd904a30050>
args: ()
object_path: '/org/fedoraproject/fedmsg/notify'
signature: None
bus_name: dbus.UTF8String(':1.942')
get_args_opts: {'byte_arrays': False, 'utf8_strings': False}
timeout: -1.0
kwargs: {}
dbus_interface: 'org.fedoraproject.fedmsg.notify'
message: <dbus.lowlevel.MethodCallMessage path: /org/fedoraproject/fedmsg/notify, iface: org.fedoraproject.fedmsg.notify, member: Disable dest: :1.942>
method: 'Disable'

Comment 1 Dan Mashal 2013-03-09 05:09:03 UTC
Created attachment 707305 [details]
File: backtrace

Comment 2 Dan Mashal 2013-03-09 05:09:04 UTC
Created attachment 707306 [details]
File: core_backtrace

Comment 3 Dan Mashal 2013-03-09 05:09:06 UTC
Created attachment 707307 [details]
File: environ

Comment 4 Dan Mashal 2013-03-11 13:01:49 UTC
** (fedmsg-notify-daemon:1249): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
/usr/lib64/python2.7/site-packages/gi/overrides/GLib.py:667: PyGIDeprecationWarning: Calling io_add_watch without priority as second argument is deprecated
  PyGIDeprecationWarning)
/usr/lib64/python2.7/site-packages/gi/overrides/GLib.py:678: PyGIDeprecationWarning: Calling io_add_watch with priority keyword argument is deprecated, put it as second positional argument
  PyGIDeprecationWarning)
[moksha.hub] DEBUG 2013-03-11 05:59:13,838 Reloading filter settings
[moksha.hub] DEBUG 2013-03-11 05:59:13,838 Initializing filter: ReportedBugsFilter
[moksha.hub] DEBUG 2013-03-11 05:59:13,839 Initializing filter: InstalledPackageFilter
[moksha.hub] DEBUG 2013-03-11 05:59:13,839 Initializing filter: PackageFilter
[moksha.hub] DEBUG 2013-03-11 05:59:13,839 Initializing filter: MyPackageFilter
[moksha.hub] DEBUG 2013-03-11 05:59:13,839 Initializing filter: UsernameFilter
[moksha.hub] INFO 2013-03-11 05:59:13,839 Loading the Moksha Hub
[moksha.hub] INFO 2013-03-11 05:59:13,840 Loading Consumers
[moksha.hub] DEBUG 2013-03-11 05:59:13,840 Loading explicitly passed entry-points.
[moksha.hub] INFO 2013-03-11 05:59:13,840 FedmsgNotifyService consumer is watching the 'org.fedoraproject.*' topic
[moksha.hub] WARNING 2013-03-11 05:59:13,840 No 'zmq_publish_endpoints' set.  Are you sure?
[moksha.hub] WARNING 2013-03-11 05:59:14,844 <fedmsg_notify.daemon.FedmsgNotifyService at /org/fedoraproject/fedmsg/notify at 0x3ab0990> didn't initialize correctly.  Did you call super(..).__init__?
[moksha.hub] INFO 2013-03-11 05:59:14,845 Loading Producers
[moksha.hub] DEBUG 2013-03-11 05:59:14,845 Loading explicitly passed entry-points.
[moksha.hub] DEBUG 2013-03-11 05:59:14,847 Subscribing to consumer topic org.fedoraproject.*
[moksha.hub] DEBUG 2013-03-11 05:59:14,848 Subscribing to org.fedoraproject. on 'ZmqEndpoint(type='connect', address='tcp://hub.fedoraproject.org:9940')'
[moksha.hub] DEBUG 2013-03-11 05:59:14,848 Creating new txzmq factory.
[moksha.hub] DEBUG 2013-03-11 05:59:14,894 Subscribing to org.fedoraproject. on 'ZmqEndpoint(type='connect', address='tcp://127.0.0.1:4001')'
[moksha.hub] DEBUG 2013-03-11 05:59:14,895 Creating new txzmq factory.
[moksha.hub] INFO 2013-03-11 05:59:15,007 Querying the PackageDB for vicodan's packages
[moksha.hub] DEBUG 2013-03-11 05:59:19,102 Message to org.fedoraproject.prod.buildsys.build.state.change didn't match filters
[moksha.hub] DEBUG 2013-03-11 05:59:24,109 Message to org.fedoraproject.prod.buildsys.tag didn't match filters

hopefully some helpful debug info

Comment 5 Fedora End Of Life 2013-04-03 15:58:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 6 Luke Macken 2013-08-21 23:18:54 UTC
*** Bug 951718 has been marked as a duplicate of this bug. ***

Comment 7 Luke Macken 2013-08-21 23:19:02 UTC
*** Bug 986723 has been marked as a duplicate of this bug. ***

Comment 8 Luke Macken 2013-08-21 23:19:24 UTC
*** Bug 998258 has been marked as a duplicate of this bug. ***

Comment 9 Fedora End Of Life 2015-01-09 17:45:07 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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 10 Fedora End Of Life 2015-02-17 14:50:39 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.