5.27 breaks Wayland support #5719

sandersteenhoudt · 2022-01-05T15:00:44Z

I have searched open and closed issues for duplicates

I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Bug Description

After upgrading to 5.27.0-1 on Arch Linux, Signal Desktop no longer starts on Wayland (using ozone flags). Reverting back to 5.26.1-1 fixes the issue.

Steps to Reproduce

Run signal-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland

Let me know if you need any additional information!

Actual Result:
Signal doesn't start.

signal-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland
Set Windows Application User Model ID (AUMID) { appUserModelId: 'org.whispersystems.signal-desktop' }
NODE_ENV production
NODE_CONFIG_DIR /usr/lib/signal-desktop/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/steen/.config/Signal
config/get: Successfully read user config file
config/get: Successfully read ephemeral config file
making app single instance
[6603:0105/154522.895686:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is egl, ANGLE is 
[6603:0105/154522.898629:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
{"level":30,"time":"2022-01-05T14:45:22.910Z","pid":6540,"hostname":"thinkpad","msg":"MainSQL: updateSchema:\n  Current user_version: 44;\n  Most recent db schema: 46;\n  SQLite version: 3.36.0;\n  SQLCipher version: 4.5.0 community;\n  (deprecated) schema_version: 210;\n"}
{"level":30,"time":"2022-01-05T14:45:22.912Z","pid":6540,"hostname":"thinkpad","msg":"app ready"}
{"level":30,"time":"2022-01-05T14:45:22.912Z","pid":6540,"hostname":"thinkpad","msg":"starting version 5.27.0"}
{"level":30,"time":"2022-01-05T14:45:22.913Z","pid":6540,"hostname":"thinkpad","msg":"media access status [object Undefined] [object Undefined]"}
{"level":30,"time":"2022-01-05T14:45:22.914Z","pid":6540,"hostname":"thinkpad","msg":"got fast spellcheck setting true"}
{"level":30,"time":"2022-01-05T14:45:22.915Z","pid":6540,"hostname":"thinkpad","msg":"getSystemTraySetting had no flags and did no DB lookups. Returning DoNotUseSystemTray"}
{"level":30,"time":"2022-01-05T14:45:22.915Z","pid":6540,"hostname":"thinkpad","msg":"Initializing BrowserWindow config: {\"show\":false,\"width\":956,\"height\":1145,\"minWidth\":712,\"minHeight\":550,\"autoHideMenuBar\":false,\"titleBarStyle\":\"default\",\"backgroundColor\":\"#3a76f0\",\"webPreferences\":{\"devTools\":false,\"nodeIntegration\":false,\"nodeIntegrationInWorker\":false,\"contextIsolation\":false,\"preload\":\"[REDACTED]/preload.bundle.js\",\"nativeWindowOpen\":true,\"spellcheck\":true,\"backgroundThrottling\":false,\"enablePreferredSizeMode\":true},\"icon\":\"[REDACTED]/images/signal-logo-desktop-linux.png\",\"x\":0,\"y\":0}"}
[6540:0105/154522.915875:ERROR:cursor_loader.cc(114)] Failed to load a platform cursor of type kNull
Segmentation fault (core dumped)

Expected Result:
Signal starts on Wayland

Platform Info

Signal Version: 5.27.0

Operating System:
Arch Linux

The text was updated successfully, but these errors were encountered:

gothmog123 · 2022-01-05T15:38:05Z

confirmed

EvanHahn-Signal · 2022-01-05T17:21:47Z

Sorry to hear this...unfortunately, we don't support the Arch Linux installation and haven't heard reports of this from supported packages, so I'm going to close this issue. I recommend bringing this up with the Arch package maintainer.

If someone can reproduce this on an official build, let me know and we'll reopen.

cherti · 2022-01-06T13:39:56Z

@EvanHahn-Signal The same issue occurs on Ubuntu 20.10, with the official installation instructions, with the aforementioned flags the application segfaults.

Furthermore, I have built 5.28-beta1 and unfortunately the same issue occurs.

EvanHahn-Signal · 2022-01-06T15:13:36Z

@cherti Thanks for confirming. I'll reopen.

samsapti · 2022-01-06T18:22:12Z

Can confirm. The issue can be reproduced on Artix Linux as well (installed from Arch [community] repo). Downgrading does solve the issue.

ganguin · 2022-01-07T00:18:05Z

Same error with the flatpak build:

flatpak run --socket=wayland org.signal.Signal --enable-features=UseOzonePlatform --ozone-platform=wayland

After the upgrade to 5.27.0 I got the same error:

[40:0107/010726.373549:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is egl, ANGLE is 
[40:0107/010726.403065:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.

ghost · 2022-01-07T00:42:58Z

With nvidia it's entirely non-functional, even on X11/XWayland.

Can the app be built with debug symbols? Would that help?

physkets · 2022-01-07T08:45:03Z

I am also on Arch and see the same issue. And just to confirm, it does work without the Ozone flags, when it uses Xwayland.

cherti · 2022-01-07T13:52:13Z

I think we shouldn't spam the issue with just confirmations of the problem, I think general overview is better served in form of thumbs-upping the opening post. :)

@Ammako have you tried adding --disable-gpu? that was recommended to try in another issue, possibly it's a different problem if it totally doesn't work?

ghost · 2022-01-07T14:54:51Z

Upstream electron 16 issue?

I just built 5.27.1 with electron 15.3.0 and it runs just fine, under Wayland with both ozone flags.

May be related: electron/electron#31885

mordax7 · 2022-01-07T19:46:02Z

On Arch Wayland, I noticed that when I start Signal from the dmenu it crashes directly but starting it from the terminal it works.

samsapti · 2022-01-07T22:54:07Z

@mordax7 can you give the full command you used to start it from the terminal? Are you sure it didn't start in XWayland?

josephdunn · 2022-01-07T23:34:54Z

I suspect that this is an Electron issue. With Electron 16.0.6 on Arch Linux (sway/Wayland) I get a very similar crash with a random .asar file (that works fine under Electron 15) when run with the params detailed in the above bug report.

mordax7 · 2022-01-08T11:04:25Z

@mordax7 can you give the full command you used to start it from the terminal? Are you sure it didn't start in XWayland?

@theanonymousexyz forgot to mention. When I start it in dmenu I start it with signal-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland and from the terminal I use signal-desktop.

This is the error if I try to start it with ozone:

{"level":30,"time":"2022-01-08T11:06:06.423Z","pid":12673,"hostname":"xps13-9300","msg":"Initializing BrowserWindow config: {\"show\":false,\"width\":1906,\"height\":555,\"minWidth\":712,\"minHeight\":550,\"autoHideMenuBar\":false,\"titleBarStyle\":\"default\",\"backgroundColor\":\"#3a76f0\",\"webPreferences\":{\"devTools\":false,\"nodeIntegration\":false,\"nodeIntegrationInWorker\":false,\"contextIsolation\":false,\"preload\":\"[REDACTED]/preload.bundle.js\",\"nativeWindowOpen\":true,\"spellcheck\":true,\"backgroundThrottling\":false,\"enablePreferredSizeMode\":true},\"icon\":\"[REDACTED]/images/signal-logo-desktop-linux.png\",\"x\":7,\"y\":638}"}
[12673:0108/120606.425538:ERROR:cursor_loader.cc(114)] Failed to load a platform cursor of type kNull
fish: Job 1, 'signal-desktop --enable-feature…' terminated by signal SIGTRAP (Trace or breakpoint trap)

samsapti · 2022-01-08T13:23:11Z

and from the terminal I use signal-desktop.

Then it's because it starts with XWayland.

jameskupke · 2022-01-08T16:51:37Z

Confimed that I updated signal flatpack and also encountering this issue in Fedora 35

$> flatpak run org.signal.Signal --enable-features=UseOzonePlatform --ozone-platform=wayland

[2 preload-host-spawn-strategy] Running: /app/bin/zypak-helper child - /app/Signal/signal-desktop --type=zygote --enable-crashpad
Set Windows Application User Model ID (AUMID) { appUserModelId: 'org.whispersystems.signal-desktop' }
NODE_ENV production
NODE_CONFIG_DIR /app/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/james/.var/app/org.signal.Signal/config/Signal
config/get: Successfully read user config file
config/get: Successfully read ephemeral config file
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[2:0108/104930.578044:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[49:0108/104930.637145:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is egl, ANGLE is
[49:0108/104930.643825:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[2:0108/104930.649912:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0108/104930.649943:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0108/104930.649967:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[2:0108/104930.652208:ERROR:cursor_loader.cc(114)] Failed to load a platform cursor of type kNull

jmc-figueira · 2022-01-09T12:53:17Z

Confirmed on NixOS unstable as well:

[996825:0109/124750.241455:ERROR:cursor_loader.cc(114)] Failed to load a platform cursor of type kNull
[1]    996825 segmentation fault (core dumped)  signal-desktop --use-tray-icon --enable-features=UseOzonePlatform

mpsq · 2022-01-09T15:10:03Z

Could it be because the version of Electron used by Signal 5.27 is affected by swaywm/wlroots#3168?
Actual upstream / Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1246834

Ashiix · 2022-01-12T14:44:34Z

Almost certainly an Electron issue, segfaulting on all attempts to launch Electron under wayland, including the default popup.

tabell · 2022-01-15T01:10:34Z

Just to add, I am running Arch without xwayland ie. passing --enable-features=UseOzonePlatform --ozone-platform=wayland and I can confirm that adding the additional flag --disable-gpu causes signal to start and run without any apparent issues.

jmc-figueira · 2022-01-15T01:25:31Z

Just to add, I am running Arch without xwayland ie. passing --enable-features=UseOzonePlatform --ozone-platform=wayland and I can confirm that adding the additional flag --disable-gpu causes signal to start and run without any apparent issues.

This does not resolve the issue for me. Same issue occurs.

cherti · 2022-01-15T12:39:44Z

Just to add, I am running Arch without xwayland ie. passing --enable-features=UseOzonePlatform --ozone-platform=wayland and I can confirm that adding the additional flag --disable-gpu causes signal to start and run without any apparent issues.

~~If you don't even run wayland, it's unsurprising that you cannot reproduce a regression on wayland.~~

Sorry, misread the original post.

jmc-figueira · 2022-01-15T12:48:47Z

Just to add, I am running Arch without xwayland ie. passing --enable-features=UseOzonePlatform --ozone-platform=wayland and I can confirm that adding the additional flag --disable-gpu causes signal to start and run without any apparent issues.

If you don't even run wayland, it's unsurprising that you cannot reproduce a regression on wayland. 🙃

tabell said they don't use XWayland, not that they don't use Wayland.

tabell · 2022-01-15T17:56:19Z

I've tested the --disable-gpu flag again and observed both behaviors - segfaulting and starting normally - so it's actually intermittent for me. It appeared to start working after I changed my sway output position to be (0,0), but then after sleeping the laptop overnight it now fails again, so it may just be a coincidence. In any case it seems like this is an Electron issue, so I'll cease further comments here unless more details are needed.

ofcaah · 2023-08-12T13:57:25Z

Isn't it ozone-platform-hint=auto?

signal starts this way, however it requires clicking the shortcut twice for the window to pop up, and there's no tray icon

sbug0 · 2023-08-15T19:31:13Z

I can't run Signal in Wayland on my Debian 12 no matter I do :-(

Neither the flatpak version, or the package from the repo loads any window when I use the flag --ozone-platform=wayland

draptik · 2023-08-23T22:42:55Z

Isn't it ozone-platform-hint=auto?

signal starts this way, however it requires clicking the shortcut twice for the window to pop up, and there's no tray icon

...and using a tiling window manager like sway: One has to start the application twice.

stickyburn · 2023-08-26T20:55:13Z

For me starting the app twice opens it, but the second I focus my cursor it crashes with segmentation fault 🙃 I think it has to do with no system tray on my twm.

dortonway · 2023-10-31T07:27:54Z

I have 1440p, Ubuntu 22.04.3, Wayland, and a fractional scaling of 125%.

I tried:

signal-desktop --ozone-platform=wayland
signal-desktop --ozone-platform-hint=auto

Then Signal opens by clicking the icon only. It's not blurry, but it does not have the window header to drag it around and resize (the window is very small). So it's not usable.

This way it has window decorations, it runs not in a native way, but it seems to be usable:

signal-desktop --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland

kingofdreams777 · 2023-11-26T01:41:51Z

Bumping this, any update here?

Using Arch Linux and Hyprland (Wayland Window Manager) and Signal Desktop fails with a segfault when running signal-desktop --use-tray-icon --enable-features=UseOzonePlatform --ozone-platform=wayland

Error Code Below:

[1]    5404 segmentation fault (core dumped)  signal-desktop --use-tray-icon --enable-features=UseOzonePlatform

jm355 · 2023-11-26T20:59:31Z

Setting signal to open in floating mode rather than tiling mode seems to prevent the crash, but any time I try to tile it it crashes. It seems to have a problem with being told what size the window is

kingofdreams777 · 2023-11-26T21:16:59Z

Interesting. What flag do I need to set to have it open in floating

jm355 · 2023-11-26T21:18:22Z

that's handled by your window manager. In my sway config I have for_window [app_id="signal"] floating enable

kingofdreams777 · 2023-11-26T21:36:49Z

Perfect. I'll look into that for Hyprland

kingofdreams777 · 2023-11-26T22:25:01Z

@jeremiah-miller unfortunately even with a window rule enable for signal with Hyprland the program still SegFaults

jm355 · 2023-11-26T23:00:23Z

Do you launch it with /usr/bin/signal-desktop --enable-features=WaylandWindowDecorations --ozone-platform-hint=auto --ozone-platform=wayland?

kingofdreams777 · 2023-11-27T01:04:48Z

@jeremiah-miller Yup still failing with a SegFault with those exact flags. If I don't add a --use-tray-icon then the window does not pop up at all either. (worth noting)

signalapp/Signal-Desktop#5719

aurelien-brabant · 2023-12-11T20:14:14Z

I'm encountering the same issue, the following invocation of signal-desktop seems to start the app normally (according to the logs) however no window pops up

/usr/bin/signal-desktop --enable-features=WaylandWindowDecorations --ozone-platform-hint=auto --ozone-platform=wayland

Tested on Gentoo with hyprland as a window manager (works normally through XWayland)

scottnonnenberg-signal · 2023-12-12T02:08:53Z

What are you seeing on the latest beta? It has an updated version of Electron: https://support.signal.org/hc/articles/360007318471-Signal-Beta

aurelien-brabant · 2023-12-12T06:54:07Z

What are you seeing on the latest beta? It has an updated version of Electron: https://support.signal.org/hc/articles/360007318471-Signal-Beta

I'm willing to test with that one, however is there a way I can download signal-desktop-beta as a pre-built linux binary since I'm not using a debian based distro?

boredland · 2023-12-19T21:40:48Z

Same issue with signal-desktop-beta (6.43.0beta.2-1 (+38 0.47)) without flags:

Set Windows Application User Model ID (AUMID) { AUMID: 'org.whispersystems.signal-desktop-beta' }
NODE_ENV production
NODE_CONFIG_DIR /opt/Signal Beta/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/jonass/.config/Signal Beta
config/start: Did not find user config file (or it was empty), cache is now empty object
config/start: Did not find ephemeral config file (or it was empty), cache is now empty object
getLogger: Logger not yet initialized!
crashReporter: enabled
making app single instance
[99621:1219/223941.346726:ERROR:ozone_platform_x11.cc(240)] Missing X server or $DISPLAY
[99621:1219/223941.346776:ERROR:env.cc(255)] The platform failed to initialize.  Exiting.
[1]    99621 segmentation fault (core dumped)  signal-desktop-beta

those flags work for both the stable and the beta:

signal-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland --disable-gpu

justin13888 · 2024-01-08T23:17:10Z

Using flatpak Signal (stable) (version 6.43.1 production) on Fedora Workstation (Gnome). Could confirm it also doesn't run (hangs instead of crashing outright).

flatpak run org.signal.Signal --enable-features=UseOzonePlatform --ozone-platform=wayland

Stdout:

Debug: Will run signal with the following arguments:
Debug: Additionally, user gave: --enable-features=UseOzonePlatform --ozone-platform=wayland
Set Windows Application User Model ID (AUMID) { AUMID: 'org.whispersystems.signal-desktop' }
NODE_ENV production
NODE_CONFIG_DIR /app/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/<omitted>/.var/app/org.signal.Signal/config/Signal
config/get: Successfully read user config file
config/get: Successfully read ephemeral config file
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings

wmfinck · 2024-01-09T18:15:39Z

I am having the same experience as justin13888 on Fedora 39 and I am also using flatpak Signal (stable) version 6.43.1. I have tried various combinations of the flags below:

flatpak run org.signal.Signal --enable-features=UseOzonePlatform --ozone-platform=wayland --disable-gpu

Debug: Will run signal with the following arguments:
Debug: Additionally, user gave: --enable-features=UseOzonePlatform --ozone-platform=wayland --disable-gpu
[2 zypak-helper] Wait found events, but sd-event found none
Set Windows Application User Model ID (AUMID) { AUMID: 'org.whispersystems.signal-desktop' }
NODE_ENV production
NODE_CONFIG_DIR /app/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/wmfinck/.var/app/org.signal.Signal/config/Signal
config/get: Successfully read user config file
config/get: Successfully read ephemeral config file
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings

vincentkoevoets · 2024-01-18T06:18:36Z

What are you seeing on the latest beta? It has an updated version of Electron: https://support.signal.org/hc/articles/360007318471-Signal-Beta

I installed the latest beta, and wayland seems to be working again, but still not natively. I have a custom .desktop file, and the exec command is this:

Exec="/opt/Signal Beta/signal-desktop-beta" --no-sandbox --enable-features=UseOzonePlatform,waylandWindowDecorations --ozone-platform=wayland %U

With these options, the screen is clear (no blurryness), but the window controls are on the wrong side (left instead of right) and also seem different from other app window controls, and the icon in the bottom taskbar (so not the notification icon) is a cogwheel instead of the blue Signal icon.
But it is usable, which is nice.

stickyburn · 2024-01-18T09:33:56Z

@vincentkoevoets I have these flags and none of the issues you mentioned:

--ozone-platform-hint=auto --enable-features=WaylandWindowDecorations

Except native wayland ofcourse 🙃

vincentkoevoets · 2024-01-18T10:05:40Z

@vincentkoevoets I have these flags and none of the issues you mentioned:
--ozone-platform-hint=auto --enable-features=WaylandWindowDecorations
Except native wayland ofcourse 🙃

Hmm that's strange, something else must be wrong then. I ran this from the command line:

signal-desktop-beta --ozone-platform-hint=auto --enable-features=WaylandWindowDecorations

but got exactly the same symptoms as described in my previous post. Do you use any other options?

stickyburn · 2024-01-18T11:50:54Z

Nope sorry. Mayybbe try --disable-gpu just to check, but don't think it'll have any affect.

vincentkoevoets · 2024-01-19T05:50:29Z

Well I did try --disable-gpu, just in case, but still with the same symptoms. I will be diving further into this, maybe it has to do with scaled desktop, of maybe something else is wrong. Will try a clean ubuntu install also, just to see if it makes any difference. Thanks for the help.

justin13888 · 2024-01-19T06:25:21Z

Using flatpak Signal (stable) (version 6.43.1 production) on Fedora Workstation (Gnome). Could confirm it also doesn't run (hangs instead of crashing outright).

flatpak run org.signal.Signal --enable-features=UseOzonePlatform --ozone-platform=wayland

Stdout:

Debug: Will run signal with the following arguments:
Debug: Additionally, user gave: --enable-features=UseOzonePlatform --ozone-platform=wayland
Set Windows Application User Model ID (AUMID) { AUMID: 'org.whispersystems.signal-desktop' }
NODE_ENV production
NODE_CONFIG_DIR /app/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/<omitted>/.var/app/org.signal.Signal/config/Signal
config/get: Successfully read user config file
config/get: Successfully read ephemeral config file
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings

Since my last message, I managed to get Signal to run on Wayland by updating my desktop file as follows and making sure signal hasn't been started on another process. It appears that Signal Desktop (6.44.1 production; Flatpak) works (at least on Fedora 39 Workstation) on Wayland.

[Desktop Entry]
Name=Signal
Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=signal-desktop --file-forwarding org.signal.Signal @@u %U @@
Terminal=false
Type=Application
Icon=org.signal.Signal
StartupWMClass=Signal
Comment=Private messaging from your desktop
MimeType=x-scheme-handler/sgnl;x-scheme-handler/signalcaptcha;
Categories=Network;InstantMessaging;Chat;
X-Desktop-File-Install-Version=0.27
X-Flatpak-RenamedFrom=signal-desktop.desktop;
X-Flatpak=org.signal.Signal

vincentkoevoets · 2024-01-19T07:04:23Z

That's one thing I hadn't tried yet. So I removed all repo versions of Signal and installed the Flatpak one. I still have to start with flatpak run org.signal.Signal --enable-features=UseOzonePlatform --ozone-platform=wayland, but everything works fine with those options. So I will be running this one for now.

dinotheextinct · 2024-02-21T16:37:32Z

Is there any fix for this? cant run signal-desktop flatpak on wayland.

NiciTheNici · 2024-04-16T17:03:22Z

@dinotheextinct run it using --enable-features=UseOzonePlatform --ozone-platform=wayland

EvanHahn-Signal closed this as completed Jan 5, 2022

EvanHahn-Signal reopened this Jan 6, 2022

EvanHahn-Signal added the Bug label Jan 6, 2022

Ashiix mentioned this issue Jan 12, 2022

[Bug]: segfault on startup at gpu_init.cc under native Wayland electron/electron#32436

Closed

3 tasks

scottnonnenberg-signal added the Upstream Change Needed label Jan 12, 2022

mhwombat mentioned this issue Jan 14, 2022

signal-desktop crashes when using command-line switches to enable wayland NixOS/nixpkgs#155050

Closed

torgeir added a commit to torgeir/nix that referenced this issue Dec 3, 2023

wayland signal-desktop segfaults, remove it for now

96de182

signalapp/Signal-Desktop#5719

torgeir added a commit to torgeir/nix that referenced this issue Dec 3, 2023

wayland signal-desktop segfaults, remove it for now

bc22493

signalapp/Signal-Desktop#5719

5.27 breaks Wayland support #5719

5.27 breaks Wayland support #5719

Comments

sandersteenhoudt commented Jan 5, 2022

Bug Description

Steps to Reproduce

Platform Info

gothmog123 commented Jan 5, 2022

EvanHahn-Signal commented Jan 5, 2022

cherti commented Jan 6, 2022 • edited

EvanHahn-Signal commented Jan 6, 2022

samsapti commented Jan 6, 2022 • edited

ganguin commented Jan 7, 2022

ghost commented Jan 7, 2022

physkets commented Jan 7, 2022

cherti commented Jan 7, 2022

ghost commented Jan 7, 2022 • edited by ghost

mordax7 commented Jan 7, 2022 • edited

samsapti commented Jan 7, 2022

josephdunn commented Jan 7, 2022

mordax7 commented Jan 8, 2022 • edited

samsapti commented Jan 8, 2022

jameskupke commented Jan 8, 2022

jmc-figueira commented Jan 9, 2022

mpsq commented Jan 9, 2022

Ashiix commented Jan 12, 2022

tabell commented Jan 15, 2022

jmc-figueira commented Jan 15, 2022

cherti commented Jan 15, 2022 • edited

jmc-figueira commented Jan 15, 2022

tabell commented Jan 15, 2022

ofcaah commented Aug 12, 2023

sbug0 commented Aug 15, 2023

draptik commented Aug 23, 2023

stickyburn commented Aug 26, 2023

dortonway commented Oct 31, 2023 • edited

kingofdreams777 commented Nov 26, 2023

jm355 commented Nov 26, 2023

kingofdreams777 commented Nov 26, 2023

jm355 commented Nov 26, 2023

kingofdreams777 commented Nov 26, 2023

kingofdreams777 commented Nov 26, 2023

jm355 commented Nov 26, 2023

kingofdreams777 commented Nov 27, 2023

aurelien-brabant commented Dec 11, 2023

scottnonnenberg-signal commented Dec 12, 2023

aurelien-brabant commented Dec 12, 2023 • edited

boredland commented Dec 19, 2023 • edited

justin13888 commented Jan 8, 2024

wmfinck commented Jan 9, 2024

vincentkoevoets commented Jan 18, 2024

stickyburn commented Jan 18, 2024

vincentkoevoets commented Jan 18, 2024

stickyburn commented Jan 18, 2024

vincentkoevoets commented Jan 19, 2024

justin13888 commented Jan 19, 2024

vincentkoevoets commented Jan 19, 2024

dinotheextinct commented Feb 21, 2024

NiciTheNici commented Apr 16, 2024

cherti commented Jan 6, 2022 •

edited

samsapti commented Jan 6, 2022 •

edited

ghost commented Jan 7, 2022 •

edited by ghost

mordax7 commented Jan 7, 2022 •

edited

mordax7 commented Jan 8, 2022 •

edited

cherti commented Jan 15, 2022 •

edited

dortonway commented Oct 31, 2023 •

edited

aurelien-brabant commented Dec 12, 2023 •

edited

boredland commented Dec 19, 2023 •

edited