[Bug 77986] New: When Delegating handlers are given a Requests_Satisfied path that doesn't exist

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Apr 26 17:00:46 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=77986

          Priority: medium
            Bug ID: 77986
          Assignee: telepathy-bugs at lists.freedesktop.org
           Summary: When Delegating handlers are given a
                    Requests_Satisfied path that doesn't exist
        QA Contact: telepathy-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: kde at davidedmundson.co.uk
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: mission-control
           Product: Telepathy

Created attachment 98062
  --> https://bugs.freedesktop.org/attachment.cgi?id=98062&action=edit
Bustle log

What's currently happening:

 - App A has a channel.
 - App A tells MC to delegate a channel to AppB
 - MC sends sends a HandleChannels call to my AppB with a all the normal stuff
and a path to the ChannelDispatcherRequest path as the Requests_Satisfied:
@ao ["/org/freedesktop/Telepathy/ChannelDispatcher/Request24"]

(this is the same request path as when MC gave App A a HandleChannels)

 - TpQt does it's introspection and tries to load the request from the
ChannelDispatcher
 - it fails with "GetAll" with signature "s" on interface
"org.freedesktop.DBus.Properties" doesn't exist"
 - TpQt then explodes and ignores the request.

>From what I can tell there is no request object on MC, as the channel is
already handled.

I think we should modify _mcd_client_proxy_handle_channels to have some
argument to know if it is delegating channels and if so not send any
Requests_Satisfied. Am I right? 

If I modify TpQt to silently ignore loading the ChannelRequest error,
everything works perfectly.

I've attached a quite simply bustle log of the problem.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.


More information about the telepathy-bugs mailing list