Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Application crash when renaming an active session #26452

Closed
suprunchuk opened this issue Jun 27, 2023 · 2 comments
Closed

Application crash when renaming an active session #26452

suprunchuk opened this issue Jun 27, 2023 · 2 comments

Comments

@suprunchuk
Copy link

Steps to reproduce

Precondition: You must have at least one active session in your account.

  1. Download and install the portable version of Telegram v4.8.3 x64 on your PC.
  2. Log in to your account.
  3. Open "Settings" -> "Privacy and Security" -> "Show all sessions".
  4. In the "this device" section, click "rename".
  5. Enter any new name. Click the "save" button.

1

Expected behaviour

The new name of your current device should be saved.

Actual behaviour

When you click the save button, the application crashes.

Operating system

windows 10 pro

Version of Telegram Desktop

portable v4.8.3 x64

Installation source

Static binary from official website

Crash ID

56b54f7f-28f0-406b-b866-a68b61ba6078

Logs

No response

@suprunchuk suprunchuk added the bug label Jun 27, 2023
@2raghu
Copy link

2raghu commented Jul 8, 2023

Seems issue is specific with Windows 10 pro.
I could not reproduce on

Edition Windows 11 Pro
Version 22H2
Installed on ‎3/‎9/‎2023
OS build 22621.1555
Experience Windows Feature Experience Pack 1000.22640.1000.0

Do you see the issue only with portable version ?
I have not tried reproduction on Win10 pro.

Copy link

github-actions bot commented Jan 5, 2024

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 github-actions bot added the stale label Jan 5, 2024
@github-actions github-actions bot closed this as completed Feb 5, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants