View Single Post
epage's Avatar
Posts: 1,684 | Thanked: 1,562 times | Joined on Jun 2008 @ Austin, TX
#656
Originally Posted by activemind View Post
New error:
(18:18:41) ERROR MainThread.connection: __init__
Traceback (most recent call last):
File "/opt/theonering/lib/util/misc.py", line 48, in wrapper
return func(*args, **kwds)
File "/opt/theonering/lib/connection.py", line 118, in __init__
constants._telepathy_implementation_name_
File "/opt/theonering/lib/tp/conn.py", line 82, in __init__
_Connection.__init__(self, bus_name, object_path)
File "/usr/lib/pymodules/python2.5/dbus/service.py", line 480, in __init__
self.add_to_connection(conn, object_path)
File "/usr/lib/pymodules/python2.5/dbus/service.py", line 571, in add_to_connection
self._fallback)
KeyError: "Can't register the object-path handler for '/org/freedesktop/Telepathy/Connection/theonering/gv/myGVAccount': there is already a handler"
(18:18:47) ERROR MainThread.connection: __init__
Traceback (most recent call last):
File "/opt/theonering/lib/util/misc.py", line 48, in wrapper
return func(*args, **kwds)
File "/opt/theonering/lib/connection.py", line 118, in __init__
constants._telepathy_implementation_name_
File "/opt/theonering/lib/tp/conn.py", line 82, in __init__
_Connection.__init__(self, bus_name, object_path)
File "/usr/lib/pymodules/python2.5/dbus/service.py", line 480, in __init__
self.add_to_connection(conn, object_path)
File "/usr/lib/pymodules/python2.5/dbus/service.py", line 571, in add_to_connection
self._fallback)
KeyError: "Can't register the object-path handler for '/org/freedesktop/Telepathy/Connection/theonering/gv/myGVAccount': there is already a handler"

And if I remember the sequence of events correctly, this started happening after I added erminig-ng to my n900 which uses the same account. Also, I deleted my GV account thinking of readding it and now it does not even sign in. Looks like an interaction problem, one is creating a handler and the other one rather than reusing, is trying to create a new one?
This error means that Mission Control (the Connection Manager Manager) lost track of the active TOR connection some how. TOR doesn't know this and can't force it to close. TOR needs to stop and restart to work again. This can be done by rebooting or killing the process.

This happens when a specific Connection Manager is unresponsive when creating connections. I had thought I fixed all cases in TOR but system load can also be a factor. So this might be my fault or might be the systems fault. "They" had done work to make it better with PR1.2 but I've occasionally hit it with TOR and sometimes SIP becomes really bad.
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
 

The Following User Says Thank You to epage For This Useful Post: