Closed dtrash1 closed 3 years ago
Thank you for reporting. I'll spin up a virtual machine to check this out.
I guess I have to find a way to automatically detect these cases
Well.. I've spent some time trying to debug this.
The problem is the same: signal-desktop packaging source includes pre-built binaries.
These binaries are built with a newer GLIBC version, namely GLIBCXX_3.4.21
CentOS 7 is older than the GLIBC version required by the pre-built binaries shipped with signal.
This already happened with zkgroup
(issue #3 )
The solution was building zkgroup
from source when building Signal-Desktop and then replace the shipped binary with the one built when creating the package.
The problem is that when we try to do the same trick with RingRTC is too much effort. I can do it in my machine, but it fails when using the Copr buildsystem for some reason.
One of the possible causes is that the RingRTC source/build folders require 20GB free space. Probably it is too much pressure for a free service like Copr.
One alternative I can think of is to try their flatpak release.
Since I cannot guarantee new releases for CentOS 7 anymore I'm removing CentOS 7 from the copr project.
This way I can also remove zkgroup
el7 conditional building from the spec file.
I've added signal-ringrtc-zkgroup-el7.spec
to this git if someone wants to pick up from there.
Thanks for spending the time to look at this. It's not difficult to believe that copr can't or doesn't want to support builds that absorb so many resources.
It looks like your flatpak suggestion will work for me, so thanks for that, too.
On Wed, Dec 9, 2020 at 8:33 AM Guilherme Cardoso notifications@github.com wrote:
Well.. I've spent some time trying to debug this.
The problem is the same: signal-desktop packaging source includes pre-built binaries. These binaries are built with a newer GLIBC version, namely GLIBCXX_3.4.21 CentOS 7 is older than the GLIBC version required by the pre-built binaries shipped with signal.
This already happened with zkgroup (issue #3 https://github.com/luminoso/fedora-copr-signal-desktop/issues/3 ) The solution was building zkgroup from source when building Signal-Desktop and then replace the shipped binary with the one built when also building the rest of the signal-desktop source code.
The problem now doing the same and building RingRTC https://github.com/signalapp/ringrtc is too much effort. I can build it in my machine, but I can't identify when building using the rpmspec it fails.
The RingRTC source/build folders also require 20GB free space.
I advise you to try to find a solution, their flatpak release https://flathub.org/apps/details/org.signal.Signal can be a possible solution
So I'm removing CentOS 7 from this copr repo. This way I can also stop remove zkgroup el7 conditional building from the spec file.
I've added signal-ringrtc-zkgroup-el7.spec to the repo if someone wants to pick up from there.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/luminoso/fedora-copr-signal-desktop/issues/5#issuecomment-741810381, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNEEBPO4V4GAU6UT3P5EMDST6DDRANCNFSM4R447ZUA .
Just wanted to thank you for copr repo.. was looking for a way to install signal on fedora 33. just moved to it from OSX.. and did not want to use snaps.. did find a diff repo but that one had version 1.8.0... and did not sync contacts.. i was so happy there was a better option.. So thank you for doing this for everyone ;-)
Well.. I've spent some time trying to debug this. The solution was building
zkgroup
from source when building Signal-Desktop and then replace the shipped binary with the one built when creating the package.I've added
signal-ringrtc-zkgroup-el7.spec
to this git if someone wants to pick up from there.
Would you mind posting instructions for building el7 package? I can't use flatpack on my particular system. Another thought - disable RingRTC, is it possible?
Latest working el7 package is also in this repo here: https://github.com/luminoso/fedora-copr-signal-desktop/blob/master/signal-ringrtc-zkgroup-el7.spec
It demos the strategy of building external dependencies for zkgroup. You'll need to use the same strategy for ringrtc.
I tried it, but RingRTC implies building WebRTC if I'm not mistaken.
Bug Description
Signal-Desktop never leaves the "loading" screen with the 3 animated dots when running on CentOS 7.
An error is printed indicating a failure to load
GLIBCXX_3.4.21
. My CentOS 7 seems to useGLIBCXX_3.4.19
.If this dependency issue is like the previous (issue #3 ), the problem may be that the included RingRTC module isn't built to run on CentOS 7.
This bug appears to be present in versions after 1.35.1. Last known working version is 1.34.5.
Steps to Reproduce
Actual Result:
Signal-Desktop never leaves the "loading" screen with the 3 animated dots.
Expected Result:
Signal-Desktop starts up normally, loading messages followed by a switch to the messaging UI.
Screenshots
N/A
Platform Info
Signal Version:
Reproduced with 1.35.1, 1.36.2, 1.36.3
Operating System:
CentOS Linux release 7.8.2003 (Core)
Linked Device Version:
Android: Signal 4.71.5
Link to Debug Log
The "View"->"Debug Log" menu item is unresponsive, however, the console shows the following (from 1.36.3, specifically):