FS#73266 - [signal-desktop] 5.27.0 doesn't work on Wayland

Attached to Project: Community Packages
Opened by Ammako (Ammako) - Wednesday, 05 January 2022, 17:44 GMT
Last edited by Toolybird (Toolybird) - Saturday, 09 July 2022, 01:20 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
kpcyrd (kpcyrd)
Santiago Torres (sangy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

On my end: Gnome 41.2, nvidia 495.46, the app doesn't work with and without ozone flags. With --use-tray-icon I can force the app to show up, but the window is blank and you can't do anything with it.

5.26.1 works fine

Additional info:
* 5.27.0-1
* See log.txt
* https://github.com/signalapp/Signal-Desktop/issues/5719

Steps to reproduce:
1. Be on Wayland session
2. Update signal-desktop to 5.27.0
3. Attempt to run the app
   log.txt (5.1 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 09 July 2022, 01:20 GMT
Reason for closing:  Fixed
Comment by Franz (enbQao) - Wednesday, 05 January 2022, 19:34 GMT
I can confirm that is does not work under Wayland using the ozone flags. I get the following error:


[1] 35435 segmentation fault (core dumped) signal-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland


However, starting it without the ozone flags under Wayland (so that is runs under XWayland) seems to work for me (I get the normal window and can receive/send messages as usual; though with all the known XWayland issues like blurry-ness when using scaling etc.)
Comment by Ammako (Ammako) - Wednesday, 05 January 2022, 19:35 GMT
Which gpu? It not working on Xwayland may be a nvidia-specific issue.
Comment by Jonas Große Sundrup (cherti) - Wednesday, 05 January 2022, 22:02 GMT
> Which gpu? It not working on Xwayland may be a nvidia-specific issue.

Can confirm the problem for Intel-GPUs as well, although it does work under XWayland for me.
Comment by alice salem (burrhole) - Thursday, 06 January 2022, 10:34 GMT
The same issue occurs with AMD and Sway as well.
Comment by myrealname (gothmog123) - Thursday, 06 January 2022, 12:44 GMT
confirmed with ivy bridge
Comment by Jan Žegklitz (zegkljan) - Thursday, 06 January 2022, 18:37 GMT
I experience this on X11 as well (Gnome 41.2, GeForce 940M, nvidia 495.46-6).

If I start as just signal-desktop, I get the following thing in stdout (the interesting bit)

[9289:0106/192930.288310:ERROR:gpu_process_host.cc(968)] GPU process exited unexpectedly: exit_code=136
GPU at BusId 0x1 doesn't have a supported video decoder
[9289:0106/192930.817579:ERROR:gpu_process_host.cc(968)] GPU process exited unexpectedly: exit_code=136
GPU at BusId 0x1 doesn't have a supported video decoder
[9289:0106/192931.311609:ERROR:gpu_process_host.cc(968)] GPU process exited unexpectedly: exit_code=136
GPU at BusId 0x1 doesn't have a supported video decoder
[9289:0106/192931.839627:ERROR:gpu_process_host.cc(968)] GPU process exited unexpectedly: exit_code=136
GPU at BusId 0x1 doesn't have a supported video decoder
[9289:0106/192932.361900:ERROR:gpu_process_host.cc(968)] GPU process exited unexpectedly: exit_code=136
GPU at BusId 0x1 doesn't have a supported video decoder
[9289:0106/192932.920070:ERROR:gpu_process_host.cc(968)] GPU process exited unexpectedly: exit_code=136
[9462:0106/192932.927719:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is disabled, ANGLE is

and then it just hangs, no window, no nothing. If I start with tray, I can get the window (the GPU errors are still present), but it is just blank. Version 5.26.1 works without a problem, but there are a few of the GPU errors on stdout as well.

To be honest, I have some problems related to graphics card at other places as well (e.g. VLC crashes because of the same GPU at BusID error) which I haven't figured out yet. However, regarding signal, this behaviour appeared with the newest version, so there must be something in signal as well.
Comment by Ammako (Ammako) - Friday, 07 January 2022, 14:02 GMT
--disable-gpu flag should let you bypass nvidia to run it on X11/XWayland
Comment by Ammako (Ammako) - Saturday, 08 January 2022, 00:57 GMT
This is likely an electron 16 bug. 5.26.1 used electron 15.3.0, a workaround would be to build the package using that version of electron instead (works on my end.) Otherwise there isn't much to do but to wait for upstream to fix.
Comment by Tim Ruffing (realorrandom) - Thursday, 23 June 2022, 19:59 GMT
Fixed upstream in >=5.28.0, see https://github.com/signalapp/Signal-Desktop/issues/5719. So this can be closed.

Loading...