Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 819048 - net-im/signal-desktop-bin-5.20.0: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
Summary: net-im/signal-desktop-bin-5.20.0: libva error: vaGetDriverNameByIndex() faile...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Robert G. Siebeck
URL:
Whiteboard:
Keywords: PullRequest
Depends on:
Blocks:
 
Reported: 2021-10-20 16:33 UTC by Julien Delquié
Modified: 2021-12-03 09:14 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Julien Delquié 2021-10-20 16:33:26 UTC
With Wayland, Signal interface is just a black and void window with the following verbose in console:

$ 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/loup/.config/Signal
config/get: Successfully read user config file
Set Windows Application User Model ID (AUMID) { appUserModelId: 'org.whispersystems.signal-desktop' }
x-attr dependency did not load successfully
config/get: Successfully read ephemeral config file
making app single instance
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)


Reproducible: Always

Steps to Reproduce:
1. Launch a Wayland session (not X11)
2. Launch Signal
Actual Results:  
Signal with black and void window

Expected Results:  
Signal window with its normal content.

Operating System: Gentoo Linux
KDE Plasma Version: 5.23.0
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.13-gentoo-x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 31.3 Gio of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2
Comment 1 Julien Delquié 2021-10-20 16:58:42 UTC
It seems that launching signal-desktop this way from console works:
signal-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2021-12-01 17:22:38 UTC
Please do include emerge --info in reports, but sounds like glibc-2.34/clone3.
Comment 3 Larry the Git Cow gentoo-dev 2021-12-01 17:24:40 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=70ab23abd46ce2220f03e968c88a53ef0cf29512

commit 70ab23abd46ce2220f03e968c88a53ef0cf29512
Author:     Robert Siebeck <gentoo.2019@r123.de>
AuthorDate: 2021-12-01 17:10:13 +0000
Commit:     Sam James <sam@gentoo.org>
CommitDate: 2021-12-01 17:24:30 +0000

    net-im/signal-desktop-bin: depend on glibc[-clone3]
    
    Uses an older version of Electron which breaks when the clone3 syscall is used
    internally within glibc.
    
    Closes: https://bugs.gentoo.org/819048
    Signed-off-by: Robert Siebeck <gentoo.2019@r123.de>
    Signed-off-by: Sam James <sam@gentoo.org>

 .../signal-desktop-bin-5.24.0-r1.ebuild            | 103 +++++++++++++++++++++
 1 file changed, 103 insertions(+)
Comment 4 Bernard Cafarelli gentoo-dev 2021-12-03 09:14:14 UTC
It looks like this was only needed for 5.20.0 as newer versions have electron >= 13.5.0 ?
https://github.com/signalapp/Signal-Desktop/blob/v5.21.0/package.json#L248

Which does have the clone3 fix:
https://github.com/electron/electron/pull/31091

signal works fine here with glibc-2.34[clone3] (though I do not use Wayland)