New version is required to render new type of messages. Simple cp telegram-desktop-bin-4.8.9.ebuild telegram-desktop-bin-4.10.2.ebuild does the job. https://github.com/telegramdesktop/tdesktop/releases
Oh, do not bump this release. I'm experiencing nasty crash with it: https://github.com/telegramdesktop/tdesktop/issues/26877 Should be fixed with tomorrow's release.
Updated my PR to latest release which includes the crash fix.
Just confirming here. I've tried telegram-desktop 4.10.3 for 24 hours (and I use telegram a lot). No regressions noticed. As for pull request, I don't see peter@x1 ~ $ lddtree /usr/bin/telegram-desktop /usr/bin/telegram-desktop (interpreter => /lib64/ld-linux-x86-64.so.2) libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 libexpat.so.1 => /usr/lib64/libexpat.so.1 libfreetype.so.6 => /usr/lib64/libfreetype.so.6 libz.so.1 => /lib64/libz.so.1 libbz2.so.1 => /lib64/libbz2.so.1 libpng16.so.16 => /usr/lib64/libpng16.so.16 libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 libfreetype.so.6 => !!! circular loop !!! libgraphite2.so.3 => /usr/lib64/libgraphite2.so.3 libX11.so.6 => /usr/lib64/libX11.so.6 libxcb.so.1 => /usr/lib64/libxcb.so.1 libXau.so.6 => /usr/lib64/libXau.so.6 libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 libmount.so.1 => /lib64/libmount.so.1 libblkid.so.1 => /lib64/libblkid.so.1 libcryptsetup.so.12 => /usr/lib64/libcryptsetup.so.12 libuuid.so.1 => /lib64/libuuid.so.1 libdevmapper.so.1.02 => /lib64/libdevmapper.so.1.02 libudev.so.1 => /lib64/libudev.so.1 libcap.so.2 => /lib64/libcap.so.2 libssl.so.3 => /usr/lib64/libssl.so.3 libcrypto.so.3 => /usr/lib64/libcrypto.so.3 libargon2.so.1 => /usr/lib64/libargon2.so.1 libjson-c.so.5 => /usr/lib64/libjson-c.so.5 libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 libffi.so.8 => /usr/lib64/libffi.so.8 libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 libpcre2-8.so.0 => /lib64/libpcre2-8.so.0 libdl.so.2 => /lib64/libdl.so.2 libm.so.6 => /lib64/libm.so.6 libpthread.so.0 => /lib64/libpthread.so.0 libc.so.6 => /lib64/libc.so.6 ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 peter@x1 ~ $ ldd /usr/bin/telegram-desktop | grep libgdk peter@x1 ~ $ So I can not confirm missing dependency mentioned there.
net-im/telegram-desktop-bin-4.10.3 crashes upon clicking the button to attach a file to a conversation: implib-gen: libgdk-3.so.0: failed to resolve symbol 'gdk_wayland_window_get_type' via dlsym: /usr/lib64/libgdk-3.so.0: undefined symbol: gdk_wayland_window_get_type Aborted Presumably this is due to a similar issue I have seen with other programs in the past where even the function to check whether the display is Wayland or not assumes GTK+ is compiled with Wayland support... Ideally upstream would not do this, but at a minimum it seems like 4.10.3 requires gtk+ with USE wayland.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4542357371bb275b1acfe478c9b487f0e15ef0df commit 4542357371bb275b1acfe478c9b487f0e15ef0df Author: Joe Kappus <joe@wt.gd> AuthorDate: 2023-10-05 06:35:45 +0000 Commit: Hans de Graaff <graaff@gentoo.org> CommitDate: 2023-10-06 07:45:03 +0000 net-im/telegram-desktop-bin: security drop 4.8.4, 4.8.9 Bug: https://bugs.gentoo.org/915066 Signed-off-by: Joe Kappus <joe@wt.gd> Signed-off-by: Hans de Graaff <graaff@gentoo.org> net-im/telegram-desktop-bin/Manifest | 4 -- .../telegram-desktop-bin-4.8.4.ebuild | 53 ------------------- .../telegram-desktop-bin-4.8.9.ebuild | 61 ---------------------- 3 files changed, 118 deletions(-)
Hello. ">=dev-qt/qtwayland-6.5:6[compositor]" should use [compositor qml]. Because telegram does not compile without qml USE flag of qtwayland.
Mike, this bug is a bump request for the -bin ebuild, which is not compiled by Gentoo. I'm going to close this bug as the bump is done and I'm not able to reproduce the file chooser crash right now. However this crash is probably a bug that should be filed separately. I'm wondering if this crash is affected or worked around by use of different gtk_portal or qt_qpa_theme environment variables. Telegram has had similar crashes before recently that they've fixed, so I would encourage filing a bug upstream making sure to mention that you are using their static build.
