flathub / org.signal.Signal

https://flathub.org/apps/details/org.signal.Signal
60 stars 33 forks source link

wayland notworking. #512

Open realSConway opened 12 months ago

realSConway commented 12 months ago

Hello experts, I'm having issues running signal on wayland (sway on openSUSE Tumbleweed).

Flatpak 1.14.4 Signal Desktop 6.30.2

flatpak run --user org.signal.Signal Errors:

Debug: Will run signal with the following arguments: --enable-features=WaylandWindowDecorations --ozone-platform=wayland
Debug: Additionally, user gave: 
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 localhost.localdomain
NODE_APP_INSTANCE undefined
SUPPRESS_NO_CONFIG_WARNING undefined
SIGNAL_ENABLE_HTTP undefined
userData: /home/anon/.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
Gtk-Message: 22:10:05.317: Failed to load module "canberra-gtk-module"

(signal-desktop:2): Gdk-WARNING **: 22:10:05.325: Failed to read portal settings: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop
[2:0920/221005.393679:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.InvalidArgs: No such interface “org.freedesktop.portal.FileChooser”
[2:0920/221005.393697:ERROR:select_file_dialog_linux_portal.cc(274)] Failed to read portal version property
(node:93) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `exe --trace-deprecation ...` to show where the warning was created)

Web suggests I need xdg-desktop-portal-wlr, canberra-gtk-module, libcanberra-gtk-module, libcanberra-gtk3-module which I already have. Adding --env=GTK_MODULES= to flatpak run --user --env=GTK_MODULES= org.signal.Signal did not help.

Is there anything else I can try or is xwayland the only solution...? Cheers

David-Else commented 11 months ago

On my Debian 12 system it seems to work fine:

$ flatpak run org.signal.Signal
Debug: Will run signal with the following arguments: --enable-features=WaylandWindowDecorations --ozone-platform=wayland
Debug: Additionally, user gave: 
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/david/.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

I am not using --user, but rather the default install, maybe that could make a difference?

I think there are a lot of Wayland fixes coming with the new Electron 26 version of Signal, so maybe check again when that is out...

dc2xl commented 11 months ago

One Note: my signal was disconnected and on my debian 12 system i got exactly the same result in the command line as David-Else. ... but actually no window was shown.

After reconnecting the account in a X11 session, it signal also started a window... Most of the time

In the signal upstream issues I found a comment that starting a second signal process actually helps if no window comes up. That helped in the cases when no window came up.

It seems there is a race condition upstream where a necessary 'ready' event might be missed sometimes. So starting a second signal instance might help some people. (Note sure where to drop this info)

David-Else commented 11 months ago

After using it a while in Wayland I found that half of the time it does not start, so I switched Wayland off. I am looking forward to going back when they fix the bugs!

ThisNekoGuy commented 10 months ago

I also just noticed that Signal just seems to close itself on Wayland...

I tried running it in gamescope, like I do with Discord, but it somehow still failed:

gamescope --nested-width=1920 --nested-height=1080 --filter=fsr --sharpness=0 --force-windows-fullscreen --hide-cursor-delay --nested-refresh=60 --prefer-vk-device -- flatpak run org.signal.Signal
Terminal Output: ``` Your Wayland compositor does NOT support wp_presentation/presentation-time which is required for VK_KHR_present_wait and VK_KHR_present_id. Please complain to your compositor vendor for support. Falling back to X11 window with less accurate present wait. wlserver: [backend/headless/backend.c:68] Creating headless backend vulkan: selecting physical device 'AMD Radeon Graphics (RADV GFX1101)': queue family 1 (general queue family 0) vulkan: physical device supports DRM format modifiers vulkan: supported DRM formats for sampling usage: vulkan: AR24 (0x34325241) vulkan: XR24 (0x34325258) vulkan: AB24 (0x34324241) vulkan: XB24 (0x34324258) vulkan: RG16 (0x36314752) vulkan: NV12 (0x3231564E) vulkan: AB4H (0x48344241) vulkan: XB4H (0x48344258) vulkan: AB48 (0x38344241) vulkan: XB48 (0x38344258) vulkan: AB30 (0x30334241) vulkan: XB30 (0x30334258) vulkan: AR30 (0x30335241) vulkan: XR30 (0x30335258) vulkan: Creating Gamescope nested swapchain with format 44 and colorspace 0 wlserver: Running compositor on wayland display 'gamescope-0' wlserver: [backend/headless/backend.c:16] Starting headless backend wlserver: [xwayland/sockets.c:65] Failed to bind socket @/tmp/.X11-unix/X0: Address already in use wlserver: [xwayland/server.c:108] Starting Xwayland on :2 wlserver: [types/wlr_compositor.c:673] New wlr_surface 0x5557939c3810 (res 0x5557939bfec0) wlserver: [xwayland/server.c:273] Xserver is ready pipewire: stream state changed: connecting pipewire: stream state changed: paused pipewire: stream available on node ID: 70 Debug: Will run signal with the following arguments: --use-tray-icon --start-in-tray Debug: Additionally, user gave: 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/user/.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 (signal-desktop:2): GLib-GIO-WARNING **: 22:14:06.866: Can't find module 'dconf' specified in GSETTINGS_BACKEND gamescope: children shut down! (EE) failed to read Wayland events: Broken pipe ```
CTR99 commented 7 months ago

Issue Template: Failed to Read Portal Settings

Description:

Signal Desktop version: [6.44.1] Operating System: [Arch Linux-x86_64-(arch3-1)] Error Messages:

(signal-desktop:2): Gdk-WARNING **: 17:51:01.742: Failed to read portal settings: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.Settings” on object at path /org/freedesktop/portal/desktop
[2:0123/175101.804417:ERROR:object_proxy.cc(577)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.InvalidArgs: No such interface “org.freedesktop.portal.FileChooser”
[2:0123/175101.804444:ERROR:select_file_dialog_linux_portal.cc(280)] Failed to read portal version property

Issue: When attempting to save an image, zip file, document..... in Signal, the application freezes, and the image is not saved at all.

Steps to Reproduce:

Install Arch Linux minimal with Hyprland dotfiles. Install Flatpak. Install Signal using Flatpak. Additional Information: By the way, the problem is not in Flatpak; I have other apps, and they work fine.

Troubleshooting Steps Taken:

Gave the app full access to system files and home directory. Uninstalled Flatpak and installed Snap, but the problem persists.

Any help in resolving this matter would be greatly appreciated. Thank you!