-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Signal doesn't get past blue starting screen #5047
Comments
Please open the dev tools - there's probably a useful error there that isn't making it to stdout. |
They are empty. You do mean the side panel (ctrl+shift+i) thing, right? |
Having the same issue. Running Gentoo as well, but using an AMD system: Video card is a AMD Radeon RX 5700 XT, though I don't believe that matters. Looking through /var/log/messages, I found the following:
The output for enable logging confirms:
And when I run it with disabling the GPU, it works. I've tested this several times, so definitely something with the library libGLESv2.so in the bin package. |
AFAIU you are running the beta-1 of the current stable version, could you first upgrade to the latest stable version? Maybe ask the Gentoo maintainer to do it. |
The "-r1" in the version is just a "build recipe version", source points correctly to https://updates.signal.org/desktop/apt/pool/main/s/signal-desktop/signal-desktop_1.40.0_amd64.deb |
I have the same problem. Also on Gentoo |
Tracked at https://bugs.gentoo.org/771363 on Gentoo |
Same problem on Gentoo as well. |
This appears to be a bug with an unofficial Gentoo build, which we don't support. I'm going to close this issue in favor of the issue in Gentoo-land. If this becomes a problem for people in supported builds, please open a new issue. |
The Gentoo package is in fact not a separate build, but just a script unpacking and installing the official build, so I would consider this bug an issue of the officially supported build. Therefore, could you please re-open? |
This is the official build! |
@EvanHahn-Signal what made you conclude that the report is about an unofficial build? |
My guess why this is happening: we recently upgraded from Electron 8 to Electron 11. This seems to have caused some GPU-related errors. But I don't know—I would need to do more investigation. @robert7k I don't know much about Gentoo so I may be wrong here, but it seems like the Gentoo package is effectively a wrapper around the official @CMoH Again, I know little about Gentoo, but my understanding is that it doesn't use I'm going to leave this issue closed because I still believe it's affecting an unofficial build (even though it's very similar to the official build), but let me know if that seems unreasonable. |
@EvanHahn-Signal I fail to see how build is not entirely yours. It literally just installs your binary package. |
But we've only seen reported problems from Gentoo and Funtoo, so it's got most likely something to do with how Gentoo/Funtoo handles mesa, or something, or something. (Or other distributions will follow when their system packages are updated) The electron upgrade is a good hint. EDIT: I should launch Debian/Arch containers and study the differences, since ldd, strace etc really give nothing. |
So a hint from Gentoo's chromium maintainers was that the bundled libs are different from system ones, and the package shouldn't try to "unbundle" them. The latest signal-desktop-bin-1.40.0-r3 version in gentoo tree is using bundled libs and seems to work fine. Waiting more feedback on https://bugs.gentoo.org/771363 So to summarize; Seems like both electron update (new libs) and Gentoo's build recipe unbundling was causing it. |
@EvanHahn-Signal It would not be inappropriate for me to appreciate behavior as reasonable/unreasonable. However, without your help, the people that know how all this should work, we would be helpless in solving such problems. I am happy things got solved. |
Bug Description
signal, once started, displays a blank blue screen forever with no further messages in the terminal. If i delete the config directory located in: ~/.config/Signal, it starts and allows me to re-link my device, however after closing the application and restarting it the strange behavior continues.
Steps to Reproduce
start signal
Platform Info
Signal Version: 1.40.0-r1
Operating System: Linux (Linux desktop 5.4.92-gentoo #2 SMP Thu Feb 11 20:42:34 CST 2021 x86_64 Intel(R) Core(TM) i7-9700F CPU @ 3.00GHz GenuineIntel GNU/Linux)
The text was updated successfully, but these errors were encountered: