Refresh
Refresh
Source Files (show merged sources derived from linked package)
Filename Size Changed Actions
GSL-master.zip 0000078172 76.3 KB about 1 year
_constraints 0000000130 130 Bytes over 1 year
breakpad-master.tar.gz 0005213846 4.97 MB 5 months
catch.hpp 0000422383 412 KB about 2 years
crl-master.zip 0000044789 43.7 KB 2 months
gyp-master.tar.gz 0000627010 612 KB 5 months
libtgvoip.zip 0002042747 1.95 MB 4 months
linux-syscall-support-refs-heads-master.tar.gz 0000034552 33.7 KB 5 months
lz4-dev.zip 0000380587 372 KB 3 months
patch.py 0000012759 12.5 KB about 1 month
range-v3-master.zip 0000833965 814 KB 5 months
rlottie-master.zip 0008033766 7.66 MB about 1 month
tdesktop.patch 0000007395 7.22 KB 3 months
telegram-desktop.changes 0000027580 26.9 KB 18 days
telegram-desktop.spec 0000010142 9.9 KB 18 days
v1.8.9.tar.gz 0014407939 13.7 MB 18 days
variant-master.zip 0000141553 138 KB 5 months
xxHash-master.zip 0000057956 56.6 KB 5 months
Comments for telegram-desktop 42

Atri Bhattacharya's avatar

badshah400 wrote about 2 years ago

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


Thomas Schraitle's avatar

thomas-schraitle wrote about 2 years ago

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


Xu Zhao's avatar

nuklly wrote about 2 years ago

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

badshah400 wrote about 2 years ago

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

nuklly wrote about 2 years ago

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

thomas-schraitle wrote about 2 years ago

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

badshah400 wrote about 2 years ago

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

badshah400 wrote almost 2 years ago

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

nuklly wrote almost 2 years ago

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

nuklly wrote almost 2 years ago

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

badshah400 wrote almost 2 years ago

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

nuklly wrote almost 2 years ago

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


Atri Bhattacharya's avatar

badshah400 wrote almost 2 years ago

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


Atri Bhattacharya's avatar

badshah400 wrote almost 2 years ago

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

badshah400 wrote almost 2 years ago

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


Xu Zhao's avatar

nuklly wrote almost 2 years ago

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


Atri Bhattacharya's avatar

badshah400 wrote almost 2 years ago

I see. Here's my log from non-starting: http://paste.opensuse.org/60941374


Atri Bhattacharya's avatar

badshah400 wrote almost 2 years ago

@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

13ilya wrote over 1 year ago

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

nuklly wrote over 1 year ago

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

13ilya wrote over 1 year ago

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

nuklly wrote over 1 year ago

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

nuklly wrote over 1 year ago

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

13ilya wrote over 1 year ago

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

badshah400 wrote over 1 year ago

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


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

13ilya wrote 8 months ago

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. :-(


Marcel Kuehlhorn's avatar

tux93 wrote 8 months ago

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

ervin wrote 4 months ago

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


Xu Zhao's avatar

nuklly wrote 4 months ago

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

ervin wrote 4 months ago

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


Marcel Kuehlhorn's avatar

tux93 wrote 4 months ago

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

nuklly wrote 4 months ago

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


Marcel Kuehlhorn's avatar

tux93 wrote 4 months ago

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


Dead Mozay's avatar

Dead_Mozay wrote 4 months ago

it will also turn off for GTK


Vitaly Korotkov's avatar

vitalykorotkov wrote 2 months ago

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.


Marcel Kuehlhorn's avatar

tux93 wrote 2 months ago

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


Marcel Kuehlhorn's avatar

tux93 wrote 2 months ago

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

Dead_Mozay wrote 4 months ago

after updating from this repository, telegram stopped working on GNOME


Xu Zhao's avatar

nuklly wrote 4 months ago

Okay I will revert the change.


Dead Mozay's avatar

Dead_Mozay wrote 4 months ago

  • 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

13ilya wrote 2 months ago

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


Marcel Kuehlhorn's avatar

tux93 wrote 2 months ago

Thanks for the Info,

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