Telegram Desktop

Edit Package telegram-desktop

A new era of messaging.

Refresh
Refresh
Source Files (show merged sources derived from linked package)
Filename Size Changed
0001-use-bundled-webrtc.patch 0000000582 582 Bytes
0002-use-bundled-rnnoise-expected-gsl-ranges-webrtc.patch 0000003165 3.09 KB
0003-revert-webrtc-cmake-target-file.patch 0000000652 652 Bytes
0004-use-dynamic-x-libraries.patch 0000000490 490 Bytes
_constraints 0000000572 572 Bytes
rnnoise-git20210122.tar.gz 0000173774 170 KB
tdesktop-5.2.3-full.tar.gz 0069745773 66.5 MB
telegram-desktop.changes 0000101991 99.6 KB
telegram-desktop.spec 0000011371 11.1 KB
tg_owt-master.zip 0025189554 24 MB
tg_owt-packager.py 0000003324 3.25 KB
tg_owt-packager.sh 0000000694 694 Bytes
Comments 86

Atri Bhattacharya's avatar

@nuklly, any suggestions toward fixing these build failures? Thanks!


Thomas Schraitle's avatar

Please also activate the openSUSE Leap 42.4 and openSUSE 15.0 repos. :)) Thanks!


Xu Zhao's avatar

Sorry but it seems the parent respository didn't have openSUSE Leap 42.4 and openSUSE 15.0 repo. https://ibb.co/f0O1dk Do you know how to open it for this specific package?


Atri Bhattacharya's avatar

It won't build for 42.2 and 42.3 (assuming that's what you meant rather than 42.4 -- the latter doesn't exist afaik) because they need to built against the corresponding :Update projects -- gcc6 is broken in the main projects, and at the main project server:messaging level. I think that is not advisable for server:messaging, since it contains several other pkgs.

However, I do this over at home:badshah400:Telegram/telegram-desktop, and I just added the 15.0 repository there. Feel free to take a look and see if that works for you.


Xu Zhao's avatar

Just curious, in your home repo, how did you 1) make telegram-desktop compile in 42.3; 2) add openSUSE_Leap_15.0 as a target repository?


Thomas Schraitle's avatar

how did you [...] 2) add openSUSE_Leap_15.0 as a target repository?

I did it with:

1) Click the "Repository" tab in the server:messaging project; 2) Click the "Add Repository" link (you need to scroll down a bit); 3) Click the "Expert mode" link (you need to scroll down a bit); 4) Enter "openSUSE:Leap:15.0" in the project text field; 5) Select "standard" from the "Repository" pull down menu; 6) Change the name to "openSUSE_Leap_15.0" 7) Disable the architectures you do not need.


Atri Bhattacharya's avatar

To compile telegram-desktop for 42.2, for example, I modified the project config as follows:

  <repository name="openSUSE_Leap_42.2">
    <path project="openSUSE:Leap:42.2:Update" repository="standard"/>
    <path project="openSUSE:Leap:42.2" repository="standard"/>
    <arch>x86_64</arch>
  </repository>

I think, for 42.3, it compiles even without the :Update repository. So you may want to follow the suggestion by @thomas-schraitle to do that.

Hope that helps.


Atri Bhattacharya's avatar

Unfortunately this seems to no longer launch on Tumbleweed. Probably since the switch to OpenSSL 1.1, which causes build failures for libtelegram-qt5. Think we need to build against system libQt5, using patches from Debian, or elsewhere.


Xu Zhao's avatar

We've already been using system libQt5 and the patch from Arch. What is the error message you get in the failed launch?


Xu Zhao's avatar

Also on my desktop, the program still launches without any problem. However, after switching to system libQt, I may miss some dependencies that are required to launch tdesktop (which are already installed since I am using KDE).


Atri Bhattacharya's avatar

Sorry, yes, I think I jumped the gun here. I am on a GNOME desktop (Tumbleweed 20180103), and it doesn't launch here. I don't really get an error message when launching from the terminal. The telegram process starts running apparently (shows it running on top); however, the app interface just doesn't show up. Here is what it says:

QApplication: invalid style override passed, ignoring it.

(telegram-desktop:1313): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplayManager'

(telegram-desktop:1313): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(telegram-desktop:1313): GLib-GObject-CRITICAL **: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed



Xu Zhao's avatar

(After searching a little bit) have you tried installing libqt5-qtbase-platformtheme-gtk3 and libqt5-qtstyleplugins-platformtheme-gtk2?


Atri Bhattacharya's avatar

@nuklly Thanks for looking into this. Both of these are installed on my system.


Atri Bhattacharya's avatar

From the log file, the problem seems somewhat clearer: [2018.01.06 14:57:42] Font Error: could not locate 'Open Sans Semibold' font in ':/gui/fonts/OpenSans-Semibold.ttf'.


Atri Bhattacharya's avatar

That font is definitely installed as a system font though. Probably looking in the wrong dir, is telegram.


Xu Zhao's avatar

Here is the log for my successful startup: https://pastebin.com/vj4La8RP The font problem seems to be irrelevant.



Atri Bhattacharya's avatar

@nuklly Finally, what gets telegram started is removing libqt5-qtstyleplugins-platformtheme-gtk2. Odd, but what do I know! Thanks for all the help.


Илья Индиго's avatar

Hello! Thank you very much for supporting this project! :-) I have 2 problems on Tumbleweed without pulseaudio (alsa and apulse).

1 Sounds is works, but mute microphone. On skype via apulse, kwave and audacity microphone work fine. I read this https://github.com/telegramdesktop/tdesktop/issues/783 but don't understand why it is still not working when the fixes were adopted in 1.2.1?

2 At the time of making a voice call, the application always drops. Maybe This is related to 1 and 3.

3 I have a firewall enabled, all ports are closed except the required ones and there is no upnp. Do I need to open tcp or udp ports for correct work and which ones?


Xu Zhao's avatar

1 I have tested on 1.3.0 and the microphone works fine with pulseaudio. Does it still have problem for you? 2 Sorry but I never use voice call on desktop.. If you still have this problem I can try testing with someone. 3 AFAIK Telegram uses 80, 443, and 25. You can use network sniffing tool to figure out what other ports are also used.


Илья Индиго's avatar

1 The problem is still there and it concerns not only the telegram. https://forums.opensuse.org/showthread.php/530861-ALSA-don-t-set-or-mute-default-and-sysdefault-capture-devices Attempting to use apulse results in a full loss of sound, although skype via apulse works fine.

apulse telegram-desktop QApplication: invalid style override passed, ignoring it. AL lib: (EE) ALCpulseCapture_open: Could not build map for channel count (1)! QIODevice :: read (QNetworkReplyHttpImpl): device not open

2 Since version 2.2.17, the voice call no longer causes the application to crash. 3 I'm using 25, 143, 587 ports for mail and 80, 443 ports for web on all desktops. Can this affect the operation of telegram-desktop?


Xu Zhao's avatar

1 Looks like a non-trivial bug. Why not submit an issue to telegram-desktop GitHub repo? 3 No it should not. Just setup your firewall to allow the ports. Telegram also supports proxy settings. See: http://www.youngzsoft.net/ccproxy/telegram.htm?20170813230748


Xu Zhao's avatar

Oh BTW does the same problem appear on the binary prebuilt version of Telegram? If so, you should definitely issue a bug report to their github repo.


Илья Индиго's avatar

Conflict durring upgrade to Tumbleweed with Qt 5.11

Problem: telegram-desktop-1.3.0-9.1.x86_64 requires libQt5Gui.so.5(Qt_5.10.0_PRIVATE_API)(64bit), but this requirement cannot be provided


Atri Bhattacharya's avatar

This probably just needs telegram to build against openSUSE_Factory once. Just give it some time.


Илья Индиго's avatar

Pleace, enable in "Repositories" Debuginfo flags for All. Me need gdb stack for my bug report https://github.com/telegramdesktop/tdesktop/issues/5380 but i can't fetch it. :-(


M K's avatar

That would require to enable Debug for the whole Repo which I can't do

Alternatively you can branch the package and enable it in your branch


Kevin Ottens's avatar

Anybody knows what it'd take to enable the native notifications support in this package?


Xu Zhao's avatar

To enable native notification support, remove the "TDESKTOP_DISABLE_GTK_INTEGRATION" line in the patch.py. However, that will also lead to using GTK-style file open dialogs under KDE.


Kevin Ottens's avatar

Damn, can't have it all I guess. ;-)


M K's avatar

Personally I'd favour having native notification support over a nice file chooser but I'm aware others might think differently


Xu Zhao's avatar

In a newest push I have tried to enable both. Both of them works on my computer, but I need more feedbacks.


M K's avatar

I'll give it a go when it finishes building, though I'm not a KDE user


Dead Mozay's avatar

it will also turn off for GTK


Vitaly Korotkov's avatar

It is worth checking the relevance of the option. I have a fork of this repository, and in it I build Telegram without "TDESKTOP_DISABLE_GTK_INTEGRATION". I have both KDE-style dialogs and system notifications working.


M K's avatar

The last time I tried without it Telegram became unusable on GTK based desktops, but I'll gladly try again


M K's avatar

Disregard my previous message, as mentioned in a comment farther up it works after removing libqt5-qtstyleplugins-platformtheme-gtk2

I added a Conflict on that package and will submit it with the next upstream update


Dead Mozay's avatar

after updating from this repository, telegram stopped working on GNOME


Xu Zhao's avatar

Okay I will revert the change.


Dead Mozay's avatar
  • child.append("'TDESKTOP_DISABLE_GTK_INTEGRATION'")
  • # Turn on GTK support by default
  • # child.append("'TDESKTOP_DISABLE_GTK_INTEGRATION'")

These changes also need to be undone


Илья Индиго's avatar

Surprise from Factory:Staging https://build.opensuse.org/request/show/723514


M K's avatar

Thanks for the Info,

For Factory this shouldn't be a problem as we are now able to use gcc9 there anyway


Vinzenz Vietzke's avatar

The current v2.1.1 in Tumbleweed is currently a) outdated and b) broken. Could someone please open a SR for v2.1.8?



M K's avatar

Every SR since then got stuck in legal review, if you have contacts with SUSE legal go bother them :P


Xu Zhao's avatar

Can we add openSUSE_Leap_15.2 as build target?


M K's avatar

Project maintainers would have to do that, I made a request to replace the 15.0 one with 15.2

https://build.opensuse.org/request/show/813805


jonib's avatar

Hi, I would like to ask if there is any news regarding 2.30 version as the current version on Tumbleweed is outdated. Thank you very much for your help and time.


M K's avatar

I did not yet manage to build it successfully and only have limited time to look into it, any help would be appreciated

https://build.opensuse.org/package/show/home:tux93/telegram-desktop


Xu Zhao's avatar

I have tried a few times but couldn't get it work either. Telegram-desktop now depends on their own fork of webrtc, tg_owt, which further relies on abseil-cpp, a library that doesn't build under C++ 20 (it uses pointer, a field in std::allocator that is removed in C++20). ArchLinux uses their packaged webrtc instead, which we don't have on openSUSE.


Xu Zhao's avatar

I have fixed all the build errors and it runs on TW KDE. However, I am not sure whether it still works on GNOME/XFCE/MATE/Cinnamon. Please help test it when you have time, thanks! The repo address is: https://build.opensuse.org/package/show/home:nuklly:branches:server:messaging/telegram-desktop


Atri Bhattacharya's avatar

@nukily Great job! Version 2.3.2-109.1 launches, runs, can type and send messages, animated gifs work... what else could one ask for! GNOME Wayland, Tumbleweed.


Fein's avatar

Is there a reason why openssl is specified explicitly as a runtime dependency? Would the libopenssl1_1 requirement for libssl.so.1.1 not be picked up automatically? I have libressl installed and have to explicitly let zypper break the dependencies by ignoring the conflict on every update, but it so far seemed to work fine anyway.


M K's avatar

I will remove the Requires: for openssl and ffmpeg in the next stable update



Mustafa Çalışkan's avatar

Can we add libqt5-qtimageformats as dependency? Some of the systems doesn't have this package.



Andrés Barrantes Silman's avatar

Perhaps adding google-opensans-fonts to recommends/suggest could be a good idea, Telegram looks kinda bad without them It's hard to narrow down this deps even on a clean system, damn


M K's avatar

I can add a Recommends: on the next stable update



Nianqing's avatar

I think this package should be update to a new version.


M K's avatar

Yes, if you can help fix the build of the new version please do: https://build.opensuse.org/package/show/home:tux93/telegram-desktop


Anonymous User's avatar

This comment has been deleted


Atri Bhattacharya's avatar

Yes, thanks, the maintainer would no doubt appreciate if you built and submitted that.


Bruno Friedmann's avatar

A nice improvement would be to have a test section which at least try to run the builded executable. Just to check it can run, and avoid the actual situation on TW telegram-desktop --help

(telegram-desktop:331): Telegram-WARNING **: 15:49:03.806: Application was built without embedded fonts, this may lead to font issues. Aborted



Martin von Reichenberg's avatar

Is there a reason why telegram-desktop as .RPM for SUSE is always behind the the most recent upstream versions (including Flatpak)?

https://github.com/telegramdesktop/tdesktop/releases

Thanks


Xu Zhao's avatar

Because it takes time to fix the build on both openSUSE Tumbleweed and openSUSE Leap. It is much easier to move fast on only openSUSE Tumbleweed and drop Leap support.


Martin von Reichenberg's avatar

I see, but that is why there are the options to choose for which version/branch/architecture you would like to build it.

It could mean it would run on Tumbleweed in the meantime on Leap 15.4/15.5 not . . .

And by the way, I do not get the Factory repository being mixed up with Tumbleweed repository -> Factory as a mask for Tumbleweed . . .


Xu Zhao's avatar

I just pick the latest version when I have time to update the bulid, lol. If it passes both Tumbleweed and Leap 15.4/15.5 tests, it should work on all distributions.


Martin von Reichenberg's avatar

Please enable repository for openSUSE Leap 15.5 too, @nuklly . . .

Thanks !


Xu Zhao's avatar

Unfortunately, I don't have the permission to add or edit target repostories. Please contact the maintainer of server:messaging to add 15.5.


Андрей Кувшинов's avatar

4.8.1 fails to start on 15.5 (in my case) Has to be updated to 4.8.4


Manfred Hollstein's avatar

4.8.4 will not work on Leap 15.5 due to newer versions of glib2 and glibmm2 being required by 4.8.4 than what's available on Leap 15.5 4.8.1 however needs to be built against openSUSE:Leap:15.5:Update, not openSUSE:Leap:15.5. I have fixes for all this in my own project at https://build.opensuse.org/project/show/home:manfred-h:server:messaging


Xu Zhao's avatar

The 15.5 repo is at https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP5/telegram-desktop. I believe we should update both the meta of server:messaging and openSUSE:Backports:SLE-15-SP5 to fix this issue.

Again, it is non-trivial to maintain this package on Leap. Personally I am only using TW, so I couldn't help much on maintaining Leap because I don't have environment to test it.


Илья Индиго's avatar

The packages on Leap are too old to build an up-to-date version.


Robert Riemann's avatar

Dears,

first of all: thank you for bringing telegram to opensuse. It works well. However, since I switched to Wayland, Telegram relies on its own window decoration. Without much contrast and no drop shadow, the window border are at times (e.g. on top of gray browser tab) difficult to recognise.

Example screenshot: https://redhat.discourse-cdn.com/fedoraproject/original/3X/a/4/a4d54483085c87a67017a29e25681dd549a91412.jpeg (source: https://discussion.fedoraproject.org/t/73768)

People say the problem has been fixed on the Telegram snap, but I am unable to check.


Xu Zhao's avatar

I can confirm this is already fixed in 4.10.


Martin von Reichenberg's avatar

Why did you parse & pass an update with failed builds for both SUSE Leap and SUSE Tumbleweed into the official repositories ?!_!?



Arnaud Mez's avatar

Snapshot 20230912 for Tumbleweed is released and telegram is still not yet pushed in updates list while in the same time certain kind of messages and shares cannot be read for users still on current official which is version 4.8.4 are we going to see it any time soon ? Thanks to the team/person in charge


Atri Bhattacharya's avatar

What have you done to help?


Manfred Hollstein's avatar

The package telegram-desktop newer than version 4.8.4 no longer builds for any Leap release. I have therefore stopped to build any backported packages. If you need to use telegram-desktop on Leap, I suggest you take the officially built packages for Linux from Github, e.g. https://github.com/telegramdesktop/tdesktop/releases/download/v4.9.9/tsetup.4.9.9.tar.xz for version 4.9.9 Tumbleweed is not affected by this, of course, and we will continue to add newer releases here!

openSUSE Build Service is sponsored by