Skip to content
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

Closed
1 task done
ghost opened this issue Feb 20, 2021 · 17 comments
Closed
1 task done

Signal doesn't get past blue starting screen #5047

ghost opened this issue Feb 20, 2021 · 17 comments

Comments

@ghost
Copy link

ghost commented Feb 20, 2021

  • I have searched open and closed issues for duplicates

Bug Description

screen
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)

@scottnonnenberg-signal
Copy link
Contributor

Please open the dev tools - there's probably a useful error there that isn't making it to stdout.

@ghost
Copy link
Author

ghost commented Feb 20, 2021

They are empty. You do mean the side panel (ctrl+shift+i) thing, right?

@Will9982890
Copy link

Having the same issue. Running Gentoo as well, but using an AMD system:
Linux buggs-bunny 5.10.15-gentoo-x86_64 #1 SMP Thu Feb 11 15:06:31 EST 2021 x86_64 AMD Ryzen 7 3800X 8-Core Processor AuthenticAMD GNU/Linux

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:

Feb 19 22:55:30 kernel: signal-desktop[12867]: segfault at 18 ip 00007f431509df24 sp 00007ffc05ca7320 error 4 in libGLESv2.so[7f4314ffc000+473000]
Feb 19 22:55:30 kernel: Code: cc cc cc cc cc cc 55 48 89 e5 48 8b 4f 18 48 8d 41 f8 48 85 c9 48 0f 44 c1 5d c3 cc cc cc cc cc cc cc cc cc cc cc 55 48 89 e5 <48> 8b 47 18 5d c3 cc cc cc cc cc cc 55 48 89 e5 48 8b 47 18 48 3b
Feb 19 22:55:30 kernel: signal-desktop[12907]: segfault at 18 ip 00007f431509df24 sp 00007ffc05ca7320 error 4 in libGLESv2.so[7f4314ffc000+473000]
Feb 19 22:55:30 kernel: Code: cc cc cc cc cc cc 55 48 89 e5 48 8b 4f 18 48 8d 41 f8 48 85 c9 48 0f 44 c1 5d c3 cc cc cc cc cc cc cc cc cc cc cc 55 48 89 e5 <48> 8b 47 18 5d c3 cc cc cc cc cc cc 55 48 89 e5 48 8b 47 18 48 3b
Feb 19 22:55:30 kernel: signal-desktop[12932]: segfault at 18 ip 00007f431509df24 sp 00007ffc05ca7320 error 4 in libGLESv2.so[7f4314ffc000+473000]
Feb 19 22:55:30 kernel: Code: cc cc cc cc cc cc 55 48 89 e5 48 8b 4f 18 48 8d 41 f8 48 85 c9 48 0f 44 c1 5d c3 cc cc cc cc cc cc cc cc cc cc cc 55 48 89 e5 <48> 8b 47 18 5d c3 cc cc cc cc cc cc 55 48 89 e5 48 8b 47 18 48 3b
Feb 19 22:55:30 kernel: signal-desktop[12973]: segfault at 140 ip 00007f4315a8f0be sp 00007ffc05ca72d0 error 4 in libGLESv2.so[7f4315895000+1fe000]
Feb 19 22:55:30 kernel: Code: 00 05 00 00 5b 41 5c 41 5e 41 5f 5d e9 88 00 00 00 41 89 0e 5b 41 5c 41 5e 41 5f 5d c3 53 48 8b 3d d7 3c 01 00 e8 ec 00 00 00 90 40 01 00 00 48 85 c0 74 1f 48 89 c3 48 8b 00 48 89 df ff 50
Feb 19 22:55:30 kernel: signal-desktop[12999]: segfault at 140 ip 00007f4315a8f0be sp 00007ffc05ca72d0 error 4 in libGLESv2.so[7f4315895000+1fe000]
Feb 19 22:55:30 kernel: Code: 00 05 00 00 5b 41 5c 41 5e 41 5f 5d e9 88 00 00 00 41 89 0e 5b 41 5c 41 5e 41 5f 5d c3 53 48 8b 3d d7 3c 01 00 e8 ec 00 00 00 90 40 01 00 00 48 85 c0 74 1f 48 89 c3 48 8b 00 48 89 df ff 50
Feb 19 22:55:31 kernel: signal-desktop[13026]: segfault at 140 ip 00007f4315a8f0be sp 00007ffc05ca72d0 error 4 in libGLESv2.so[7f4315895000+1fe000]
Feb 19 22:55:31 kernel: Code: 00 05 00 00 5b 41 5c 41 5e 41 5f 5d e9 88 00 00 00 41 89 0e 5b 41 5c 41 5e 41 5f 5d c3 53 48 8b 3d d7 3c 01 00 e8 ec 00 00 00 90 40 01 00 00 48 85 c0 74 1f 48 89 c3 48 8b 00 48 89 df ff 50

The output for enable logging confirms:

$ signal-desktop --enable-logging
Set Windows Application User Model ID (AUMID) { appUserModelId: 'org.whispersystems.signal-desktop' }
NODE_ENV production
NODE_CONFIG_DIR /opt/Signal/resources/app.asar/config
NODE_CONFIG {}
ALLOW_CONFIG_MUTATIONS undefined
HOSTNAME undefined
NODE_APP_INSTANCE undefined
SUPPRESS_NO_CONFIG_WARNING undefined
SIGNAL_ENABLE_HTTP undefined
userData: /home//.config/Signal
config/get: Successfully read user config file
x-attr dependency did not load successfully
config/get: Successfully read ephemeral config file
making app single instance
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"app ready","time":"2021-02-20T04:03:46.203Z","v":0}
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"starting version 1.40.0","time":"2021-02-20T04:03:46.203Z","v":0}
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"media access status undefined undefined","time":"2021-02-20T04:03:46.203Z","v":0}
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"updateSchema:\n Current user_version: 23;\n Most recent db schema: 23;\n SQLite version: 3.33.0;\n SQLCipher version: 4.4.2 community;\n (deprecated) schema_version: 113;\n","time":"2021-02-20T04:03:46.213Z","v":0}
[14122:0219/230346.240673:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 1 time(s)
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"Initializing BrowserWindow config: {"show":true,"width":1066,"height":694,"minWidth":680,"minHeight":550,"autoHideMenuBar":true,"titleBarStyle":"default","backgroundColor":"#3a76f0","webPreferences":{"nodeIntegration":false,"nodeIntegrationInWorker":false,"contextIsolation":false,"enableRemoteModule":true,"preload":"/opt/Signal/resources/app.asar/preload.js","nativeWindowOpen":true,"spellcheck":true,"backgroundThrottling":false},"icon":"/opt/Signal/resources/app.asar/images/signal-logo-desktop-linux.png","x":2006,"y":1034}","time":"2021-02-20T04:03:46.282Z","v":0}
[14122:0219/230346.288135:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 2 time(s)
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"spellcheck: user locale: en-US","time":"2021-02-20T04:03:46.323Z","v":0}
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"spellcheck: available spellchecker languages: ["af","bg","ca","cs","cy","da","de","el","en-AU","en-CA","en-GB","en-GB-oxendict","en-US","es","es-419","es-AR","es-ES","es-MX","es-US","et","fa","fo","fr","he","hi","hr","hu","hy","id","it","ko","lt","lv","nb","nl","pl","pt-BR","pt-PT","ro","ru","sh","sk","sl","sq","sr","sv","ta","tg","tr","uk","vi"]","time":"2021-02-20T04:03:46.323Z","v":0}
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"spellcheck: setting languages to: ["en-US"]","time":"2021-02-20T04:03:46.323Z","v":0}
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"Begin ensuring permissions","time":"2021-02-20T04:03:46.350Z","v":0}
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"Ensuring file permissions for 2 files","time":"2021-02-20T04:03:46.355Z","v":0}
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"Finish ensuring permissions in 6ms","time":"2021-02-20T04:03:46.356Z","v":0}
[14122:0219/230346.360011:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 3 time(s)
[14122:0219/230346.399725:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 4 time(s)
[14122:0219/230346.438334:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 5 time(s)
[14122:0219/230346.483889:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 6 time(s)
[14122:0219/230346.489586:WARNING:gpu_process_host.cc(991)] Reinitialized the GPU process after a crash. The reported initialization time was 0 ms
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"Updating BrowserWindow config: {"maximized":false,"autoHideMenuBar":true,"fullscreen":false,"width":1069,"height":697,"x":2003,"y":1031}","time":"2021-02-20T04:03:46.855Z","v":0}
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"config/set: Saving ephemeral config to disk","time":"2021-02-20T04:03:46.855Z","v":0}
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"close event {"shouldQuit":false}","time":"2021-02-20T04:03:56.608Z","v":0}
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"requestShutdown: Requesting close of mainWindow...","time":"2021-02-20T04:03:56.608Z","v":0}
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"requestShutdown: Response never received; forcing shutdown.","time":"2021-02-20T04:05:56.609Z","v":0}
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"before-quit event {"readyForShutdown":true,"shouldQuit":false}","time":"2021-02-20T04:05:56.610Z","v":0}
{"name":"log","hostname":"","pid":14122,"level":30,"msg":"close event {"readyForShutdown":true,"shouldQuit":true}","time":"2021-02-20T04:05:56.610Z","v":0}

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.

@hiqua
Copy link
Contributor

hiqua commented Feb 20, 2021

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.

@juippis
Copy link

juippis commented Feb 20, 2021

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

@CMoH
Copy link

CMoH commented Feb 21, 2021

I have the same problem. Also on Gentoo

@CMoH
Copy link

CMoH commented Feb 21, 2021

Tracked at https://bugs.gentoo.org/771363 on Gentoo

@drupol
Copy link

drupol commented Feb 22, 2021

Same problem on Gentoo as well.

@EvanHahn-Signal
Copy link
Contributor

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.

@robert7k
Copy link

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?

@drupol
Copy link

drupol commented Feb 22, 2021

This is the official build!

@CMoH
Copy link

CMoH commented Feb 22, 2021

@EvanHahn-Signal what made you conclude that the report is about an unofficial build?

@EvanHahn-Signal
Copy link
Contributor

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 .deb we distribute. Though it seems lightweight, it's still a wrapper and not something we officially support today.

@CMoH Again, I know little about Gentoo, but my understanding is that it doesn't use .deb files natively.

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.

@rgwott
Copy link

rgwott commented Feb 23, 2021

@EvanHahn-Signal I fail to see how build is not entirely yours. It literally just installs your binary package.

@juippis
Copy link

juippis commented Feb 23, 2021

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.

@juippis
Copy link

juippis commented Feb 23, 2021

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.

@CMoH
Copy link

CMoH commented Feb 27, 2021

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

9 participants