It seems, that scp-dbus-service is somehow effected by printing or the query of the print-applet: After login (or restart of scp-dbus-service) it can be queried by e.g.
$ qdbus --session org.fedoraproject.Config.Printing
/
/org
/org/fedoraproject
/org/fedoraproject/Config
/org/fedoraproject/Config/Printing
After the first print job (when the icon gets stuck) it does not reply anymore:
$ qdbus --session org.fedoraproject.Config.Printing
Error: org.freedesktop.DBus.Error.NoReply
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.
It seems, that scp-dbus-service is somehow effected by printing or the query of the print-applet: After login (or restart of scp-dbus-service) it can be queried by e.g. ct.Config. Printing ect/Config ect/Config/ Printing
$ qdbus --session org.fedoraproje
/
/org
/org/fedoraproject
/org/fedoraproj
/org/fedoraproj
After the first print job (when the icon gets stuck) it does not reply anymore: ct.Config. Printing .DBus.Error. NoReply
$ qdbus --session org.fedoraproje
Error: org.freedesktop
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.