Bug 332256 - Renaming a group on Facebook gives a massive error
Summary: Renaming a group on Facebook gives a massive error
Status: CONFIRMED
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: contactlist (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: Future
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-17 16:38 UTC by Gabriel
Modified: 2021-03-09 07:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gabriel 2014-03-17 16:38:13 UTC
Error conection and fixed rename the list for: facebook friends. (account @chat.facebook.com)

Reproducible: Always
Comment 1 Martin Klapetek 2014-03-17 16:48:12 UTC
Thanks for the report, but I'm confused. 

Can you please describe exactly what is wrong, how to reproduce and what should be the desired result?
Comment 2 Gabriel 2014-03-17 16:50:52 UTC
option into the list contacts= rename group
result=error rename
Comment 3 Martin Klapetek 2014-03-17 17:00:08 UTC
So you are trying to rename a group from your facebook account? Yes, that is expected to fail as facebook does not provide the necessary interface for xmpp groups.

We could still rename things and store locally when server does not support it. There could be a mapping in config file like 

[Groups rename]
facebookId@chat.facebook.com+Friends on Facebook = Whatever I renamed it to

Also please next time use the full interface, the guided one[1], especially the "steps to reproduce" field with the numbered steps, we request all the information there for a reason. Thanks

[1] - https://bugs.kde.org/enter_bug.cgi?product=telepathy&format=guided
Comment 4 David Edmundson 2014-04-02 16:50:26 UTC
We shouldn't throw up a massive error though. Particularly not so disconnected from the UI.
Comment 5 Justin Zobel 2021-03-09 07:25:40 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.