tdesktop icon indicating copy to clipboard operation
tdesktop copied to clipboard

Issues after deleting group avatar

Open aNNiMON opened this issue 6 years ago • 18 comments

Steps to reproduce

  1. Go to group settings and upload pic1, pic2 and pic3 image
  2. Delete pic3 image

Expected behaviour

After deleting pic3, the group picture should be set to pic2

Actual behaviour

After deleting pic3 there is no group picture at all: image

But if we click on the image above service message image the list of all group avatars will appear image

Now set pic4 as the group avatar image All previous group avatars will appear (including removed pic3)


One more thing. If we try to remove latest pic (now it's pic4), we get this message: image

But if we try to remove old pics, we get another message image


#5279 may be related to this, but it's different issue

Configuration

Operating system: Windows 7

Version of Telegram Desktop: 1.6.5 beta

Used theme: Any

aNNiMON avatar Apr 10 '19 21:04 aNNiMON

Still an issue in 2.4.3 :cry:

aNNiMON avatar Oct 07 '20 15:10 aNNiMON

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

stale[bot] avatar Apr 05 '21 15:04 stale[bot]

2.7.1, stiil an issue Almost 2 years :tada:

aNNiMON avatar Apr 05 '21 16:04 aNNiMON

@aNNiMON About the "One more thing. If we try to remove latest pic (now it's pic4), we get this message:"

The list of group profile photos is really a list of messages about changing the group photo. So deleting the old ones is about deleting the corresponding messages. The last one is deleted from the group, clearing the group photo.

john-preston avatar Apr 06 '21 07:04 john-preston

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

stale[bot] avatar Oct 03 '21 08:10 stale[bot]

Issue still exists

aNNiMON avatar Oct 06 '21 19:10 aNNiMON

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

stale[bot] avatar Apr 06 '22 17:04 stale[bot]

Issue still exist in 3.6.1. I'm waiting for 3.6.2+ to check if 1bd4595bba8f73ee78e31670f2f42a747d620f7a fixes this.

aNNiMON avatar Apr 07 '22 19:04 aNNiMON

Still reproducible in 3.6.3

aNNiMON avatar Apr 14 '22 21:04 aNNiMON

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Oct 12 '22 02:10 github-actions[bot]

Issue still exists

aNNiMON avatar Oct 12 '22 08:10 aNNiMON

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Apr 12 '23 01:04 github-actions[bot]

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Oct 11 '23 01:10 github-actions[bot]

Still reproducible in 4.10.2

aNNiMON avatar Oct 11 '23 17:10 aNNiMON

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Apr 09 '24 01:04 github-actions[bot]

Still reproducible in 4.16.6

aNNiMON avatar Apr 13 '24 19:04 aNNiMON

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Oct 12 '24 01:10 github-actions[bot]

Still reproducible in 5.6.1

aNNiMON avatar Oct 12 '24 18:10 aNNiMON

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Apr 11 '25 02:04 github-actions[bot]

Not stale.

soredake avatar Apr 11 '25 06:04 soredake

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

github-actions[bot] avatar Oct 10 '25 02:10 github-actions[bot]

not stale

soredake avatar Oct 10 '25 10:10 soredake

Expected behaviour

After deleting pic3, the group picture should be set to pic2

@aNNiMON @soredake Hi guys. Can you tell me where I can find similar behavior? I checked both iOS and Android apps, and after deleting the current group photo, the group photo is completely reset and becomes empty, just like on the desktop.

23rd avatar Dec 22 '25 12:12 23rd

@23rd, correct. However, please also take into account that the Edit Group/Channel screen on Telegram Android only displays a single group photo, so it's expected that removing this photo will clear the group photo entirely. Telegram X Android is even better; it shows a "Remove group photo" or "Remove channel photo" button when the user tries to update the photo.

tdesktop has a different approach. The user needs to open the current photo and delete it. The problem is that previous photos are displayed here as well, so the user thinks that removing the current photo will automatically switch to the next one, if there's one.

What would be great, at least for me, is to have a separate option in the context menu to remove the group/channel photo. Here: Image

And here: Image

aNNiMON avatar Dec 22 '25 18:12 aNNiMON