Open realSConway opened 12 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...
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)
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!
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
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!
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: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=
toflatpak 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