Skip to content
This repository has been archived by the owner on Jan 27, 2024. It is now read-only.

group still appear on my list after exit... normal group upgrade to supergroup created a duplicated on my list #262

Open
ghost opened this issue Apr 4, 2016 · 4 comments
Labels

Comments

@ghost
Copy link

ghost commented Apr 4, 2016

version : dev-1.3.0
problem1 : I exited some groups and the group still appear on my list...
problem2: after normal group upgrade to supergroup, it duplicated on my list
for example, the group "#archlinux-cn" was a normal group, but upgraded to supergroup
it appear twice on my list..
group duplicated

@majn
Copy link
Owner

majn commented Jul 29, 2016

These are two different issues.

problem1: I exited some groups and the group still appear on my list...

Did you leave the group in Pidgin or on a different client? Telegram will keep local copies of the chat history until you have deleted them manually on each device. You can do it by deleting the node or choosing "delete and exit" on the Blist icon.

problem2: after normal group upgrade to supergroup, it duplicated on my list

I wasn't able to properly test the migration from group chat to supergroup yet, this is most likely an unfixed bug.

@majn majn added the bug label Jul 29, 2016
@meersjo
Copy link

meersjo commented Aug 17, 2016

I have the same problem(s), running 1.3.0-1webupd8trusty0 from that ppa.

A group that converted to supergroup before 1.3.0 added support for those has/had the following symptoms:

  • Could no longer use before upgrade (obviously)
  • in 1.3.0, the group opens, I could type messages which would appear in other clients, but not locally; nor would messages from other clients appear. Looked like write-only. This has been resolved by exiting the group and being reinvited (private group).
  • The upgraded group has, as above, a "Use of OpenSSL is GPL-incompatible #1" appended to it's name. The previous incarnation also still exists in my list.
  • The old group has a member count, whereas the new supergroup does not
  • I can enter the old group, but when I "delete and exit", I get the error "71: RPC_CALL_FAIL 400: PEER_ID_INVALID", suggesting that the old group (it has a different ID from the new supergroup) no longer exists serverside.
  • I have deleted all history for it; and a grep -ri of my entire .purple directory yields no more matches for the group name.

For me personally this is now minor, as I can use the chat; but I suggest that fixing group conversion is fairly important :-)

@rodneyrod
Copy link

AFAIK this is an issue since the group and supergroup are two separate entities in telegram-purple and this happens with two groups with identical names i.e. your original group and its new supergroup entity.

The only way I know how to clear it up is to delete both groups and their histories.

@meersjo
Copy link

meersjo commented Aug 19, 2016

@rodneyrod, per the 5th bullet in my previous comment, I get an error when I try to delete the old group.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants