Summary: | Does not work with Empathy 3.2 | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Julian Sikorski <belegdol> |
Component: | sunshine | Assignee: | Krzysztof Klinikowski <kkszysiu> |
Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | git master | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | output of SUNSHINE_PERSIST=1 SUNSHINE_DEBUG=all /usr/libexec/telepathy-sunshine |
Description
Julian Sikorski
2011-10-21 14:21:50 UTC
I just tested this on my older computer running Fedora 14 x86_64: gnome-phone-manager-telepathy-0.65-9.fc14.x86_64 python-telepathy-0.15.19-2.fc14.noarch telepathy-butterfly-0.5.14-1.fc14.noarch telepathy-farsight-0.0.14-2.fc14.x86_64 telepathy-filesystem-0.0.2-1.fc12.noarch telepathy-gabble-0.10.5-1.fc14.x86_64 telepathy-glib-0.11.16-1.fc14.x86_64 telepathy-haze-0.4.0-2.fc14.x86_64 telepathy-idle-0.1.7-1.fc14.x86_64 telepathy-logger-0.1.7-1.fc14.x86_64 telepathy-mission-control-1:5.6.1-1.fc14.x86_64 telepathy-salut-0.4.0-1.fc14.x86_64 telepathy-sunshine-0.2.0-1.fc14.noarch empathy-2.32.2-1.fc14.x86_64 sunshine was able to establish a connection on the old computer. Contact list is almost certainly the same, it is stored on the server anyway. For the record, sunshine in f14 is two commits behind git master. The other obvious differences are twisted versions: 10.1.0 in f14; 10.2.0 in f15 (which still worked) and 11.0.0 in fc16 and above. Strange thing. I'm trying to reproduce it but without success. Julian, could you give me list of current versions of this packages from Fedora 16? I tried to use Empathy 3.2.0 and 3.3.x now to reproduce it but without success. I found where it's crashing but I don't have clue yet how to fix it and why it occurs. When you'll be available on GG I will send you sunshine testing package with more debugging information that will bring us more info about this issue. python-telepathy-0.15.19-3.fc16.noarch telepathy-butterfly-0.5.15-3.fc16.noarch telepathy-farsight-0.0.19-1.fc16.x86_64 telepathy-filesystem-0.0.2-2.fc15.noarch telepathy-gabble-0.12.7-1.fc16.x86_64 telepathy-glib-0.16.0-1.fc16.x86_64 telepathy-haze-0.5.0-1.fc16.x86_64 telepathy-idle-0.1.10-1.fc16.x86_64 telepathy-logger-0.2.10-2.fc16.x86_64 telepathy-mission-control-5.9.3-1.fc16.x86_64 telepathy-salut-0.6.0-1.fc16.x86_64 telepathy-sunshine-0.2.0-2.gite26dd019.fc16.noarch empathy-3.2.1.1-2.fc16.x86_64 Created attachment 53879 [details]
output of SUNSHINE_PERSIST=1 SUNSHINE_DEBUG=all /usr/libexec/telepathy-sunshine
I am attaching the full log in case it might be helpful.
I've got the same problem. Message in log as above. However, there is problem only when connecting with Empathy (3.2.2) When I add account from Empathy Account Dialog(when Empathy itself is not running) it connects correctly. It could be used wit KDE Telepathy 3.1 without problems. After running Empathy error appears. Maybe it could be problem with Empathy KT at the same time, but i don't think so. I'm using Fedora. It could be distribution-specific bug. All similar problems I found was related wit it. (In reply to comment #0) > process 18175: Array or variant type requires that type variant be written, but > end_dict_entry was written. > The overall signature expected here was 'a{ua{sv}}' and we are on byte 6 of > that signature. Using a current version of dbus-python (often called python-dbus in distributions - it's the same thing) should convert this into a normal Python traceback with more information. Which version of dbus-python do you have? -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-sunshine/issues/3. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.