Telegram Desktop
A new era of messaging.
- Devel package for openSUSE:Factory
-
11
derived packages
- Links to openSUSE:Factory / telegram-desktop
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout server:messaging/telegram-desktop && cd $_ - Create Badge
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-webrt |
0000003165 3.09 KB | |
| 0003-revert-webrtc-cmake-target-file.patch | 0000000753 753 Bytes | |
| 0004-use-dynamic-x-libraries.patch | 0000000490 490 Bytes | |
| 0005-use-bundled-ada.patch | 0000000950 950 Bytes | |
| 0006-tdesktop-disable-h264.patch | 0000000572 572 Bytes | |
| 0007-tg_owt-h264-dlopen.patch | 0000010294 10.1 KB | |
| _constraints | 0000000572 572 Bytes | |
| _link | 0000000124 124 Bytes | |
| ada-packager.sh | 0000000359 359 Bytes | |
| ada-v2.9.0.zip | 0000860638 840 KB | |
| rnnoise-git20210122.tar.gz | 0000173774 170 KB | |
| tdesktop-5.9.0-full.tar.gz | 0072447849 69.1 MB | |
| telegram-desktop.changes | 0000103741 101 KB | |
| telegram-desktop.spec | 0000012148 11.9 KB | |
| tg_owt-dlopen-headers.tar.gz | 0000017931 17.5 KB | |
| tg_owt-master.zip | 0022874383 21.8 MB | |
| tg_owt-packager.sh | 0000000690 690 Bytes |
Comments 89
@nuklly, any suggestions toward fixing these build failures? Thanks!
Please also activate the openSUSE Leap 42.4 and openSUSE 15.0 repos. :)) Thanks!
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?
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.
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?
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.
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.
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.
We've already been using system libQt5 and the patch from Arch. What is the error message you get in the failed launch?
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).
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:(After searching a little bit) have you tried installing libqt5-qtbase-platformtheme-gtk3 and libqt5-qtstyleplugins-platformtheme-gtk2?
@nuklly Thanks for looking into this. Both of these are installed on my system.
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'.That font is definitely installed as a system font though. Probably looking in the wrong dir, is telegram.
Here is the log for my successful startup: https://pastebin.com/vj4La8RP The font problem seems to be irrelevant.
I see. Here's my log from non-starting: http://paste.opensuse.org/60941374
@nuklly Finally, what gets telegram started is removing
libqt5-qtstyleplugins-platformtheme-gtk2. Odd, but what do I know! Thanks for all the help.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?
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.
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?
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
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.
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
This probably just needs telegram to build against openSUSE_Factory once. Just give it some time.
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. :-(
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
Anybody knows what it'd take to enable the native notifications support in this package?
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.
Damn, can't have it all I guess. ;-)
Personally I'd favour having native notification support over a nice file chooser but I'm aware others might think differently
In a newest push I have tried to enable both. Both of them works on my computer, but I need more feedbacks.
I'll give it a go when it finishes building, though I'm not a KDE user
it will also turn off for GTK
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.
The last time I tried without it Telegram became unusable on GTK based desktops, but I'll gladly try again
Disregard my previous message, as mentioned in a comment farther up it works after removing
libqt5-qtstyleplugins-platformtheme-gtk2I added a Conflict on that package and will submit it with the next upstream update
after updating from this repository, telegram stopped working on GNOME
Okay I will revert the change.
These changes also need to be undone
Surprise from Factory:Staging https://build.opensuse.org/request/show/723514
Thanks for the Info,
For Factory this shouldn't be a problem as we are now able to use gcc9 there anyway
The current v2.1.1 in Tumbleweed is currently a) outdated and b) broken. Could someone please open a SR for v2.1.8?
Requests tab. https://build.opensuse.org/package/requests/server:messaging/telegram-desktop
Heck, totally overlooked that. Thanks!
Every SR since then got stuck in legal review, if you have contacts with SUSE legal go bother them :P
Can we add openSUSE_Leap_15.2 as build target?
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
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.
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
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.
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
@nukily Great job! Version
2.3.2-109.1launches, runs, can type and send messages, animated gifs work... what else could one ask for! GNOME Wayland, Tumbleweed.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.
I will remove the Requires: for openssl and ffmpeg in the next stable update
Thank you!
Can we add libqt5-qtimageformats as dependency? Some of the systems doesn't have this package.
Done
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
I can add a Recommends: on the next stable update
gr8, thanks!
I think this package should be update to a new version.
Yes, if you can help fix the build of the new version please do: https://build.opensuse.org/package/show/home:tux93/telegram-desktop
This comment has been deleted
Yes, thanks, the maintainer would no doubt appreciate if you built and submitted that.
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
4.1.1?
https://github.com/telegramdesktop/tdesktop/releases/tag/v4.1.1
Can you help check https://build.opensuse.org/request/show/999603 ?
How so? I'm new to this.
Is there a reason why
telegram-desktopas .RPM for SUSE is always behind the the most recent upstream versions (including Flatpak)?https://github.com/telegramdesktop/tdesktop/releases
Thanks
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.
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 . . .
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.
Please enable repository for openSUSE Leap 15.5 too, @nuklly . . .
Thanks !
Unfortunately, I don't have the permission to add or edit target repostories. Please contact the maintainer of server:messaging to add 15.5.
4.8.1 fails to start on 15.5 (in my case) Has to be updated to 4.8.4
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
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.
The packages on Leap are too old to build an up-to-date version.
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.
I can confirm this is already fixed in 4.10.
Why did you parse & pass an update with failed builds for both SUSE Leap and SUSE Tumbleweed into the official repositories ?!_!?
It requires 2 dependent updates: https://build.opensuse.org/request/show/1110894 and https://build.opensuse.org/request/show/1110476
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
What have you done to help?
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!
Please upgrade to new version because of an issue with Qt6.8.
Someone who cares more than you do has already submitted an update which is being reviewed. Either submit an update yourself or do not spam this contributor-only area. Thanks for understanding.
“... A new Era of messaging that just does not work on SUSE . . .“
;-D)