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

media viewer not show on ubuntu desktop #28401

Closed
alirayaneh opened this issue Sep 13, 2024 · 25 comments
Closed

media viewer not show on ubuntu desktop #28401

alirayaneh opened this issue Sep 13, 2024 · 25 comments
Labels

Comments

@alirayaneh
Copy link

Steps to reproduce

Screenshot from 2024-09-13 09-39-26
i use official telegram desktop on ubuntu . but recently after new update . i cant see any media . when click on any media its not show

Expected behaviour

when click on any media its not show

Actual behaviour

when click on any media its not show

Operating system

ubuntu 24

Version of Telegram Desktop

5.5.4

Installation source

Snap

Crash ID

No response

Logs

No response

@alirayaneh alirayaneh added the bug label Sep 13, 2024
@HoangFuc
Copy link

i have the same error. Hope to know the solution for this bug

@Alazar42
Copy link

i have the same error. Hope to know the solution for this bug, even from the official website i downloaded the tar.gz and also from snap but the error persists
.

@igamid
Copy link

igamid commented Sep 13, 2024

Having the same issue. Looks like a regression in v5.5.x b/c v5.4.x works as expected on both systems:
system 1

OS: Ubuntu 23.10 x86_64 
DE: GNOME 45.2 
Dual screen setup

system 2

OS: Ubuntu 24.04.1 LTS x86_64 
DE: GNOME 46.0
Single screen setup

@ilya-fedin
Copy link
Contributor

Please upgrade your system. Latest 24.04.1 doesn't have such problem and 23.10 is no more supported so it doesn't receive bug fixes and must be upgaded.

@alirayaneh
Copy link
Author

Please upgrade your system. Latest 24.04.1 doesn't have such problem and 23.10 is no more supported so it doesn't receive bug fixes and must be upgaded.

But the problem still exists. And it is not resolved, why did you close the topic?
I am using the latest version of Ubuntu. 24.04
It is ridiculous that you suggest to change the operating system. Changing the operating system is sometimes a complicated and time-consuming process.
I have 2 monitors. Could that be the problem?

@ilya-fedin
Copy link
Contributor

ilya-fedin commented Sep 13, 2024

I am using the latest version of Ubuntu. 24.04

I'm pretty sure you're not. A person on other thread had an outdated system despite claiming it's latest. Latest version of Ubuntu 24.04 would return 46.2 for mutter --version command. If it returns a different value then it's not latest (if the system clams it's latest anyway then updating mechanism of your installation is broken).

It is ridiculous that you suggest to change the operating system. Changing the operating system is sometimes a complicated and time-consuming process.

I understand but what you propose? Do you want tdesktop project to fix the bug in your system component? If you would implement that then no problems.

@alirayaneh
Copy link
Author

Screenshot from 2024-09-14 00-52-08
this is my system os details٫
Well, as it is clear, this is not my personal problem and many other people have this bug
In most projects, in such cases, a problem is found and a solution is created in the source of the project. Not to invite all people to change the operating system

@igamid
Copy link

igamid commented Sep 13, 2024

  • v5.4.1 works fine on both 23.10 and 24.04, so it looks like regression issue.

@ilya-fedin
Copy link
Contributor

ilya-fedin commented Sep 13, 2024

In most projects, in such cases, a problem is found and a solution is created in the source of the project.

That is complicated. The bug is in system component. Basically, the system says "don't draw" despite the window is visible. I don't see any solution here, only a workaround - ignoring what system says. But this leads to very increased CPU usage & battery drain. This was done for a half of the year but now that most users don't have a bugged system this workaround doesn't feel acceptable (draining battery/CPU for EVERYONE in the sake of a few users who don't know how to update their systems).

@ilya-fedin
Copy link
Contributor

this is my system os details٫

Your system is not latest, sorry.

@linermgn
Copy link

linermgn commented Sep 14, 2024

the same issue, all available updates were installed, but mutter --version shows mutter 46.0

image

@ilya-fedin
Copy link
Contributor

This means updates are broken on your system. Maybe something is wrong with sources.list.

@linermgn
Copy link

This means updates are broken on your system. Maybe something is wrong with sources.list.

https://askubuntu.com/questions/1525948/how-to-upgrade-to-24-04-1

maybe not my updates were broken

Upgrades to 24.04.1 from older releases are currently blocked due to a critical bug discovered during initial rollout and enabling of upgrades.

@ilya-fedin
Copy link
Contributor

ilya-fedin commented Sep 14, 2024

The link is about updating from other releases. You're already using 24.04.

@acosonic
Copy link

24.04.1 was removed ... due to upgrade issues... How about letting us choose default viewer for media?

@ilya-fedin
Copy link
Contributor

I see the mutter version is still 46.2 on the repos: https://packages.ubuntu.com/noble-updates/mutter

@acosonic
Copy link

Yes, but that's 24.04.1 to which we can't upgrade...

I know that's not your problem, though...

I can't even edit .desktop file it gets overwritten if I add
env QT_QPA_PLATFORM=xcb ./Telegram

next time I launch there's no env var anymore..

image

@ilya-fedin
Copy link
Contributor

ilya-fedin commented Sep 18, 2024

Yes, but that's 24.04.1 to which we can't upgrade...

There's perhaps misunderstanding. Canonical couldn't disable 24.04 -> 24.04.1 upgrades technically because it's the same version (noble) and updates happen through the same repo (noble-updates), you don't need to run do-release-upgrade. What they disabled are 22.04 -> 24.04 upgrades. The only reasons you can't get 24.04.1 are 1) you broke your sources.list somehow (maybe by launching some script you don't even know) and 2) your mirrors are very slow to update.

@acosonic
Copy link

Yes, but that's 24.04.1 to which we can't upgrade...

There's perhaps misunderstanding. Canonical couldn't disable 24.04 -> 24.04.1 upgrades technically because it's the same version (noble) and updates happen through the same repo (noble-updates), you don't need to run do-release-upgrade. What they disabled are 22.04 -> 24.04 upgrades. The only reasons you can't get 24.04.1 are 1) you broke your sources.list somehow (maybe by launching some script you don't even know) and 2) your mirrors are very slow to update.

Not broken...

https://discourse.ubuntu.com/t/noble-numbat-24-04-1-lts-point-release-status-tracking/46972

Temporarily suspended...

@Aokromes
Copy link
Collaborator

Yes, but that's 24.04.1 to which we can't upgrade...

There's perhaps misunderstanding. Canonical couldn't disable 24.04 -> 24.04.1 upgrades technically because it's the same version (noble) and updates happen through the same repo (noble-updates), you don't need to run do-release-upgrade. What they disabled are 22.04 -> 24.04 upgrades. The only reasons you can't get 24.04.1 are 1) you broke your sources.list somehow (maybe by launching some script you don't even know) and 2) your mirrors are very slow to update.

Not broken...

discourse.ubuntu.com/t/noble-numbat-24-04-1-lts-point-release-status-tracking/46972

Temporarily suspended...

Therefore, updates to Noble have been temporarily suspended while the issue is being addressed.

@ilya-fedin
Copy link
Contributor

Not broken...

https://discourse.ubuntu.com/t/noble-numbat-24-04-1-lts-point-release-status-tracking/46972

Temporarily suspended...

Sorry but you're wrong. The link says about 22.04 -> 24.04 updates, not 24.04 -> 24.04.1, just like I explained. As long as packages.ubuntu.com says that the 24.04.1 versions of packages are on noble-updates repo, they couldn't be suspended. If you can't update, your system is broken.

@acosonic
Copy link

Eventualy I was able to upgrade, but when I specifically enabled "development upgrades", after that, system upgraded to 24.04.1 and mutter is 46.2 I can confirm that media viewer works with 46.2 so my system is/was not broken...

image

@linermgn
Copy link

This means updates are broken on your system. Maybe something is wrong with sources.list.

Thank you, you were right

I fixed my sources.list as mentioned here and a lot of updates were comming. The problem is gone.

@ilya-fedin
Copy link
Contributor

Eventualy I was able to upgrade, but when I specifically enabled "development upgrades", after that, system upgraded to 24.04.1 and mutter is 46.2 I can confirm that media viewer works with 46.2 so my system is/was not broken...

That shouldn't really be needed as 46.2 is on noble-updates. Perhaps your sources.list is broken so that it's missing noble-updates and updates are coming only from noble-proposed.

@saadazghour
Copy link

QT_QPA_PLATFORM=xcb ./Telegram

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

No branches or pull requests

9 participants