OK, I am sad to say this, but it turns out this bug is still here James and your fix no longer works. I thought that apparmor settings got discarded after some updates but after applying it again, the same apparmor errors are shown.
So I disabled apparmor completely to discover that this wasn't really apparmor related at all. I got mislead previously by your fix probably because the real bug does not show itself at all times - the telepathy-sunshine sometimes appears to be somehow working, i.e. it either does not connect at all or connects but does not allow to open the chat windows, just like the original reporter said in the description. I am absolutely sure though that when I was testing your fix everything worked as expected, so I have no idea what could have changed in the meantime. I was thinking about the protocol changes but this should not render UI bugs.
So I removed the empathy/telepathy/mission-control config files, configured the GaduGadu account and went to empathy-debug once again to see if there are some erros and whenever GaduGadu connection fails, I could notice the following:
- "request_connection_cb: RequestConnection failed: org.freedesktop.DBus.Python.KeyError: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 707, in _message_cb
retval = candidate_method(self, *args, **keywords)
File "/usr/lib/python2.7/dist-packages/telepathy/server/connmgr.py", line 96, in RequestConnection
conn = self._protos[proto](self, parameters)
File "/usr/lib/python2.7/dist-packages/sunshine/connection.py", line 200, in __init__
telepathy.server.Connection.__init__(self, 'gadugadu', account, 'sunshine')
File "/usr/lib/python2.7/dist-packages/telepathy/server/conn.py", line 85, in __init__
_Connection.__init__(self, bus_name, object_path)
File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 485, in __init__
self.add_to_connection(conn, object_path)
File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 576, in add_to_connection
self._fallback)
KeyError: "Can't register the object-path handler for '/org/freedesktop/Telepathy/Connection/sunshine/gadugadu/_3XXXXXX': there is already a handler""
- it seems that telepathy actually manages to connect with remote server for a short while because I can see contact text statuses shown in the logs and contact list retrieval debug info.
- Some other warnings that could be relevant:
"e_book_client_new: Cannot get book from factory: Invalid source
Error preparing persona store 'eds:1289332278.3672.18@YYYY': Couldn't open address book ‘1289332278.3672.18@YYYY’: Invalid source
postal-address-details.vala:283: Empty postal address passed to PostalAddressFieldDetails."
OK, I am sad to say this, but it turns out this bug is still here James and your fix no longer works. I thought that apparmor settings got discarded after some updates but after applying it again, the same apparmor errors are shown.
So I disabled apparmor completely to discover that this wasn't really apparmor related at all. I got mislead previously by your fix probably because the real bug does not show itself at all times - the telepathy-sunshine sometimes appears to be somehow working, i.e. it either does not connect at all or connects but does not allow to open the chat windows, just like the original reporter said in the description. I am absolutely sure though that when I was testing your fix everything worked as expected, so I have no idea what could have changed in the meantime. I was thinking about the protocol changes but this should not render UI bugs.
So I removed the empathy/ telepathy/ mission- control config files, configured the GaduGadu account and went to empathy-debug once again to see if there are some erros and whenever GaduGadu connection fails, I could notice the following: connection_ cb: RequestConnection failed: org.freedesktop .DBus.Python. KeyError: Traceback (most recent call last): python2. 7/dist- packages/ dbus/service. py", line 707, in _message_cb method( self, *args, **keywords) python2. 7/dist- packages/ telepathy/ server/ connmgr. py", line 96, in RequestConnection proto]( self, parameters) python2. 7/dist- packages/ sunshine/ connection. py", line 200, in __init__ server. Connection. __init_ _(self, 'gadugadu', account, 'sunshine') python2. 7/dist- packages/ telepathy/ server/ conn.py" , line 85, in __init__ .__init_ _(self, bus_name, object_path) python2. 7/dist- packages/ dbus/service. py", line 485, in __init__ add_to_ connection( conn, object_path) python2. 7/dist- packages/ dbus/service. py", line 576, in add_to_connection op/Telepathy/ Connection/ sunshine/ gadugadu/ _3XXXXXX' : there is already a handler"" .3672.18@ YYYY': Couldn't open address book ‘1289332278. 3672.18@ YYYY’: Invalid source address- details. vala:283: Empty postal address passed to PostalAddressFi eldDetails. "
- "request_
File "/usr/lib/
retval = candidate_
File "/usr/lib/
conn = self._protos[
File "/usr/lib/
telepathy.
File "/usr/lib/
_Connection
File "/usr/lib/
self.
File "/usr/lib/
self._fallback)
KeyError: "Can't register the object-path handler for '/org/freedeskt
- it seems that telepathy actually manages to connect with remote server for a short while because I can see contact text statuses shown in the logs and contact list retrieval debug info.
- Some other warnings that could be relevant:
"e_book_client_new: Cannot get book from factory: Invalid source
Error preparing persona store 'eds:1289332278
postal-