On Mon, Mar 15, 2010 at 9:07 AM, mikhail.zabal...@nokia.com wrote:
Yes, it was a problem with our implementation: blocking on disconnection
meant that a RequestConnection call to reestablish the connection timed out.
Even if blocking is resolved, making an object linger in disconnecting
On Wed, Mar 10, 2010 at 7:14 AM, mikhail.zabal...@nokia.com wrote:
To make Mission Control happy, a connection manager should not block its
internal event loop which processes D-Bus method calls, at least at the time
when RequestConnection is called. If the RequestConnection D-Bus call times
On Tue, Mar 9, 2010 at 12:47 PM, Sjoerd Simons sjo...@luon.net wrote:
I downloaded your package and, well, there are quite some things wrong with
it :). It might be useful to read the Debian New Maintainer guide at some
point.
I can understand my package having issues. Maintaining packages is
On Tue, Mar 9, 2010 at 1:12 PM, Sjoerd Simons sjo...@luon.net wrote:
I noticed I still had an issue. I looked closer at my logs (for
example see log mentioned in the bug or its analysis in the above
referenced forum post) and realized what appears to be calls to the
Connection Manager's
On Wed, Mar 3, 2010 at 4:39 AM, Will Thompson
will.thomp...@collabora.co.uk wrote:
You basically don't have to do anything. Just don't ship a .profile, and it
should show up in Empathy.
But if you want to show a nicer, localizable protocol name in Empathy, you
should send a patch to add it to
helpful attention
Ed Page
http://theonering.garage.maemo.org/index.html
On Tue, Mar 2, 2010 at 8:43 PM, Edward Page eop...@byu.net wrote:
I've been hunting down an issue with The One Ring which exhibits
itself as calls randomly failing with an error being reported to the
user as General Error
I wrote and tested my Connection Manager (The One Ring) on my Ubuntu
9.04 system. I then found the port to Maemo 4.1 easy enough and Maemo
5 a little bit more of a challenge but overall it was similar.
I'm now working on switching from Ubuntu 9.04 with Empathy 2.26 and
Mission Control 4(?) to
With The One Ring (GV Connection Manager) I've had a long standing bug
about the inability to reconnect. The issue is the user's Connection
was never being cleaned up so another connection could never be made.
I traced various aspects of it to ways I deviate from the spec and
leaking of some
Sorry this page is totally outdated, I will correct it.
The place to report telepathy-python bugs is in the freedesktop
bugzilla, product Telepathy in component tp-python :
https://bugs.freedesktop.org/enter_bug.cgi?product=Telepathycomponent=tp-python
Thanks, now filed
On the page for telepathy-python I did not see any procedure for
reporting bugs or who to go to for pull requests.
http://telepathy.freedesktop.org/wiki/Telepathy%20Python
I'd like to thank Danielle for helping me determine what the expected
outcome was.
Version: 0.15.13-1
Reproduction Steps:
Thanks for the reply.
You might gain some insight by reading
http://people.collabora.co.uk/~danni/telepathy-book/sect.channel.requesting.html
Unfortunately neither the spec nor that document address whether
RequestHandles is to be called explicitly by the client prior to
calling
Hey,
I've got my Google Voice connection manager working well with my older
version of empathy. I'm now trying to get it to work with the Maemo
5. My initial test case is to enable the CM, open up the chat program
(Conversations), and create a chat with an arbitrary person. This
person is not
I'm working on a GoogleVoice connection manager. So far
telepathy-butterfly's source code. the dbus spec, and empathy's source
code have been huge helps in implementing this. Earlier this week I
had an SMS conversation with someone in Empathy. My goal is to have
this all on Maemo 4.1 and Maemo
13 matches
Mail list logo
