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

Unable to open story. #28432

Closed
tuxmaster5000 opened this issue Sep 19, 2024 · 10 comments
Closed

Unable to open story. #28432

tuxmaster5000 opened this issue Sep 19, 2024 · 10 comments

Comments

@tuxmaster5000
Copy link

Steps to reproduce

  1. click on an story

Expected behaviour

The the story will opens

Actual behaviour

Nothing happens on click

Operating system

Fedora 39 (X11)

Version of Telegram Desktop

5.5.6beta

Installation source

Static binary from official website

Crash ID

No response

Logs

No error gets logged.
@ilya-fedin
Copy link
Contributor

Can't reproduce

@tuxmaster5000
Copy link
Author

5.5.5 will works.

@ilya-fedin
Copy link
Contributor

Works on both 5.5.5 and 5.5.6

@clsv
Copy link

clsv commented Sep 19, 2024

Version 5.5.6 beta, same issue, media view doesn't work at all.

@ilya-fedin
Copy link
Contributor

ilya-fedin commented Sep 19, 2024

@clsv if you use Wayland, this is a GNOME bug and you have to update to Fedora 40 or ask your distro maintainer to backport the fix.

@clsv
Copy link

clsv commented Sep 19, 2024

@ilya-fedin Sorry, I forgot to mention that I'm using X11 with XFCE4. Before the upgrade, everything was working fine.

@ilya-fedin
Copy link
Contributor

Then I can't reproduce 🤷‍♂️

@clsv
Copy link

clsv commented Sep 19, 2024

I've disabled the option - OpenGL rendering for media, and now the media view works fine.

@tuxmaster5000
Copy link
Author

I've disabled the option - OpenGL rendering for media, and now the media view works fine.

Thanks, this was the problem. Disabled -> all ok. Enabled -> unable to open the story's.

Copy link

github-actions bot commented Oct 4, 2024

This issue has been automatically closed because no developer succeeded to reproduce the issue with the given reproduction steps. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you find what's missing to reproduce the issue so that we can investigate further.

Note that GitHub is a developer communication platform. If you're an ordinary user seeking for help, get to support crew via Settings -> Ask question in the application.

@github-actions github-actions bot closed this as completed Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants