Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 925337 - net-im/telegram-desktop-bin-4.15.0: option to show your desktop to your interlocutor stopped working
Summary: net-im/telegram-desktop-bin-4.15.0: option to show your desktop to your inter...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Henning Schild
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-23 15:35 UTC by bagas
Modified: 2024-04-07 21:29 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bagas 2024-02-23 15:35:57 UTC
Hello.

Graphic shell xfce4 - 4.18.5
soft net-im/telegram-desktop-bin-4.15.0
My system Linux 6.6.13-gentoo x86_64.

When calling an interlocutor, the show screen function does not work.
When I call my interlocutor, I see the Screen button at the bottom, I press it, but nothing happens.

Communication takes place computer-to-computer, the systems are the same and the telegram versions are the same.


In these versions the Screen function worked.
4.14.9
4.14.2

Doesn't work in these versions.
4.15.0
4.14.15
Comment 1 bagas 2024-02-24 07:09:15 UTC
tested.

comp Linux <-> comp Linux - desktop display does not work

comp Linux <-> comp Windows 11 - showing the desktop works only from Windows 11, the option to show the desktop still does not work from Linux.
Comment 2 Henning Schild 2024-03-01 00:15:47 UTC
Will have to look into that. But i guess it could be an upstream problem as well.

Here is where one could look if the problem is known
https://github.com/telegramdesktop/tdesktop/issues

Are you using X11 or wayland? And in case you can try both, does one maybe work and the other one fails?

You could also try launching "telegram-desktop" from a shell and see if any error messages scroll when you hit that share button.

Also the changelog or even the commit history might give a clue on what changed.

https://github.com/telegramdesktop/tdesktop/blob/dev/changelog.txt
Comment 3 bagas 2024-03-01 05:23:40 UTC
I'm using X11, but the system is built with the wayland flag.
Comment 4 Henning Schild 2024-04-03 22:13:03 UTC
Does this still happen on newer versions? If so please provide more details, like possible output when launched with a shell.
Comment 5 Henning Schild 2024-04-03 22:14:53 UTC
Did you maybe somehow force to not install actually required runtime deps? I have had people before who refused to install deps for some reason and then complained about stuff not working as expected.
Comment 6 Henning Schild 2024-04-03 22:18:29 UTC
I just called myself and shared the screen with me. Version 4.15.2 on X11

So could not repro but was not using the older versions you reported on.
Comment 7 bagas 2024-04-04 17:42:55 UTC
Bug is still present.
The desktop is not shown to the interlocutor.

What are you about?
What old versions, what?

I'm using the available version from the repository.
Now the version is net-im/telegram-desktop-bin-4.15.2.
Comment 8 bagas 2024-04-04 18:09:57 UTC
Call from computer to mobile phone.
I try to show the screen from the computer, the screen does not show.

This log is from a computer.

$ telegram-desktop
QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter
MESA-LOADER: failed to open zink: /usr/lib64/dri/zink_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
D/tgvoip: === Updating voip config ===
D/tgvoip: {"enable_vp8_encoder":true,"enable_vp8_decoder":true,"enable_vp9_encoder":true,"enable_vp9_decoder":true,"enable_h265_encoder":true,"enable_h265_decoder":true,"enable_h264_encoder":true,"enable_h264_decoder":true,"audio_frame_size":60,"jitter_min_delay_60":2,"jitter_max_delay_60":10,"jitter_max_slots_60":20,"jitter_losses_to_reset":20,"jitter_resync_threshold":0.5,"audio_congestion_window":1024,"audio_max_bitrate":20000,"audio_max_bitrate_edge":16000,"audio_max_bitrate_gprs":8000,"audio_max_bitrate_saving":8000,"audio_init_bitrate":16000,"audio_init_bitrate_edge":8000,"audio_init_bitrate_gprs":8000,"audio_init_bitrate_saving":8000,"audio_bitrate_step_incr":1000,"audio_bitrate_step_decr":1000,"use_system_ns":true,"use_system_aec":true,"force_tcp":false,"jitter_initial_delay_60":2,"adsp_good_impls":"(Qualcomm Fluence)","bad_call_rating":true,"use_ios_vpio_agc":false,"use_tcp":false,"audio_medium_fec_bitrate":20000,"audio_medium_fec_multiplier":0.1,"audio_strong_fec_bitrate":7000}
[OpenH264] this = 0x0x7f0a003c5c10, Warning:Change QP Range from(0,51) to (12,42)
[OpenH264] this = 0x0x7f0a003c5c10, Warning:Actual input framerate 0,000000 is different from framerate in setting 15,000000, suggest to use other rate control modes
[OpenH264] this = 0x0x7f0a003c5c10, Warning:[Rc] iDid = 0,iContinualSkipFrames(3) is large
[OpenH264] this = 0x0x7f0a003c5c10, Warning:[Rc] iDid = 0,iContinualSkipFrames(3) is large
Comment 9 bagas 2024-04-07 13:02:27 UTC
What version of qt/glibc is needed for net-im/telegram-desktop-bin?
maybe it's a matter of qt/glibs versions?

such versions.
$ qlist -Iv | egrep 'qt|glib'
dev-libs/dbus-glib-0.112
dev-libs/glib-2.78.3
dev-qt/linguist-tools-5.15.13
dev-qt/qtconcurrent-5.15.13
dev-qt/qtcore-5.15.13
dev-qt/qtdbus-5.15.13
dev-qt/qtgui-5.15.13
dev-qt/qtprintsupport-5.15.13
dev-qt/qtsql-5.15.13
dev-qt/qtwayland-5.15.13
dev-qt/qtwidgets-5.15.13
dev-qt/qtxml-5.15.13
dev-util/glib-utils-2.78.3
net-libs/glib-networking-2.78.0
sys-libs/glibc-2.38-r10
Comment 10 Henning Schild 2024-04-07 21:29:24 UTC
Most of the qt stuff is bundled as binary so i do not think it is relevant.

I suggest you ask the question on the upstream issue tracker and browse that to see if the problem is already known.

Also make sure to use the upstream package for a comparison. Ideally in the same affected versions so that results can actually be compared.

If you can maybe try and compare with kde or gnome, xfce is not so common and maybe there is something going on with dbus or polkit and alike.

Another option would be to try net-im/telegram-desktop, it might offer more ways of debugging if it also shows the problem.

Once we found and solved the problem you can switch back to the -bin package from gentoo.

But since i can not repro i am not sure how i could help out.