It doesn't matter if version 0.4 or 0.5, KDE Telepathy failed since I first tried it to properly save and memorize my ICQ nickname. Everytime I go to account settings and change my name, it changes back to my icq number on next launch. Reproducible: Always Steps to Reproduce: 1. Change your ICQ name 2. Close KDE Telepathy 3. Look at your name... Arch Linux KDE 4.9
Do you have any chance to test with empathy? We use the same backend and if Empathy does not work, there's a very high probability, that this functionality is missing in the backend itself. Also if possible, try testing with Pidgin, that also has the same backend but without one additional layer.
(In reply to comment #1) > Do you have any chance to test with empathy? We use the same backend and if > Empathy does not work, there's a very high probability, that this > functionality is missing in the backend itself. Also if possible, try > testing with Pidgin, that also has the same backend but without one > additional layer. Hey. Yup, I tested it with Empathy and it doesn't work as well. However, Pidgin does it's job. So the 'additional layer' is causing the problem?
Most likely. That additional layer is telepathy-haze. You can try providing more debug by going offline, deactivating all accounts and leaving enabled only ICQ, then make sure no process telepathy-haze is running and then run this from console: G_MESSAGES_DEBUG=all HAZE_PERSIST=1 HAZE_DEBUG=all /usr/lib/telepathy-haze then connect and change your username. Then paste the log in some file here. Your telepathy-haze might be at different location though, so try looking it up first (eg. 'locate telepathy-haze'). Thanks for the testing btw.
(In reply to comment #3) > Most likely. That additional layer is telepathy-haze. You can try providing > more debug by going offline, deactivating all accounts and leaving enabled > only ICQ, then make sure no process telepathy-haze is running and then run > this from console: > > G_MESSAGES_DEBUG=all HAZE_PERSIST=1 HAZE_DEBUG=all /usr/lib/telepathy-haze > > then connect and change your username. Then paste the log in some file here. > Your telepathy-haze might be at different location though, so try looking it > up first (eg. 'locate telepathy-haze'). > > Thanks for the testing btw. No problem. If I know exactly how I can help, you can count on me. Here's the output: purple/oscar-INFO: X-Status: num1 25933, num2 27497 purple/oscar-INFO: X-Status: 0x0004, 0x000b not an xstatus reply purple/util-Message: Writing file accounts.xml to directory /tmp/haze-3Hi7cx purple/util-Message: Writing file /tmp/haze-3Hi7cx/accounts.xml (haze:2422): haze-DEBUG: set_aliases_foreach: setting alias for myself to "jovin" (haze:2422): haze-DEBUG: set_alias_failure_cb: couldn't set alias: This protocol does not support setting a public alias. purple/util-Message: Writing file accounts.xml to directory /tmp/haze-3Hi7cx purple/util-Message: Writing file /tmp/haze-3Hi7cx/accounts.xml
(haze:2422): haze-DEBUG: set_alias_failure_cb: couldn't set alias: This protocol does not support setting a public alias. Well there goes your answer I guess :) It's actually a libpurple bug, you can read more about it on Telepathy bugzilla (last three comments are enough): https://bugs.freedesktop.org/show_bug.cgi?id=13124 Closing this bugreport then as there's nothing we can do, sorry.