Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

signal desktop does not work on fedora 40! #658

Open
mctoraman opened this issue May 22, 2024 · 11 comments
Open

signal desktop does not work on fedora 40! #658

mctoraman opened this issue May 22, 2024 · 11 comments

Comments

@mctoraman
Copy link

after upgrading fedora 40 signal does not work!.
when signal opened QR code could no tbe displayed. it says check internet connection but there is no problem with the internet.

@mctoraman
Copy link
Author

signal fedora40

@serial02
Copy link

Taking advantage of your post, the same situation occurs here.

Here, the application no longer opens via the desktop link and the store link.

Captura de tela de 2024-05-24 12-28-20

If we hide the background icon that always crashes everything, the app won't open either.

Captura de tela de 2024-05-24 12-39-00

@serial02
Copy link

Hello everybody!

Can this information help solve the problem of not opening the Signal application via flatpak on Fedora 40?

edson@fedora:~$ flatpak run org.signal.Signal
Debug: Will run signal with the following arguments:
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/edson/.var/app/org.signal.Signal/config/Signal
config/get: Successfully read user config file
config/get: Successfully read ephemeral config file
making app single instance
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings

@serial02
Copy link

In openSuse TW the same thing happens.

Awaiting correction, as the application does not open at all.

edson@localhost:~> flatpak run org.signal.Signal
Debug: Will run signal with the following arguments:
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/edson/.var/app/org.signal.Signal/config/Signal
config/get: Successfully read user config file
config/get: Successfully read ephemeral config file
making app single instance
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
Gtk-Message: 18:12:16.716: Failed to load module "canberra-gtk-module"
Gtk-Message: 18:12:16.883: Failed to load module "canberra-gtk-module"
Gtk-Message: 18:12:17.000: Failed to load module "canberra-gtk-module"
edson@localhost:~> 

@bermeitinger-b
Copy link
Collaborator

Did any of you activate the required Wayland environment variable?

@serial02
Copy link

Did any of you activate the required Wayland environment variable?

Hello

Can you explain to us how this is done?

I currently use X11 instead of Wayland.

After updating the flatpak groups, the message that appears is the following:

edson@fedora:~$ flatpak run org.signal.Signal
Debug: Will run signal with the following arguments:
Debug: Additionally, user gave: 

The app still won't open

@Mikaela
Copy link

Mikaela commented May 27, 2024

Signal works fine for me on Fedora 40.

Can you explain to us how this is done?

I haven't done this in a while, but the command should be flatpak override --socket=wayland --socket=fallback-x11 --nosocket=x11 --env=ELECTRON_OZONE_PLATFORM_HINT=auto org.signal.Signal --user. Remove --user and prepend sudo if you have multiple users and would like to use it for all of them.

--socket=wayland allows Signal to use wayland, --nosocket=x11 is reduntant since --socket=fallback-x11 will let Signal only use X11 if the current session isn't using wayland (avoids fallback to xwayland).

@serial02
Copy link

Hey guys

I solved the problem by removing all content and reinstalling again

Flatpak remove flathub org.signal.Signal --delete-data

Captura de tela de 2024-05-27 13-05-20

@secretmango
Copy link

@serial02 that means likely you could have just removed the app data.

rm -rf ~/.var/app/org.signal.Signal

@beryl-33
Copy link

beryl-33 commented Aug 7, 2024

I am not at all technical - so if I should not be here please tell me.

Searching for answers to my Signal problem in Fedora Linux 40 that has suddenly arisen and getting worse.
I can usually start Signal OK, but when I try to open a message thread sometimes it works, but increasingly it gives the error, quits and then I can do nothing with it. Have to re-start laptop to try again with signal.

I haven't reinstalled Signal but will do so. But any tips or suggestions before I do that please?

Unhandled Error. TypeError [Err_Invalid_State] Controller is already closed
and then a list of Readstreams.

Apologies if this is not helpful or relevant nformation.

@liamreoch
Copy link

@serial02 that means likely you could have just removed the app data.

rm -rf ~/.var/app/org.signal.Signal

I don't believe this works as a fix, it opens once, but on closing and reopening, the exact same error appears.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants