easyeffects
easyeffects copied to clipboard
wwmm
Unable to open (Flatpak)
EasyEffects Version
7.0.5
What package are you using?
Flatpak (Flathub)
Distribution
Linux Mint 21.1 Cinnamon
Describe the bug
I tried launching it via a shortcut and through a terminal window using flatpak run com.github.wwmm.easyeffects. It only results in Failed to register: Timeout was reached.
Expected Behavior
Launch and show a window.
Debug Log
Debug Log
(process:2): easyeffects-DEBUG: 19:22:25.373: easyeffects.cpp:35 easyeffects version: 7.0.5
(process:2): easyeffects-DEBUG: 19:22:25.373: easyeffects.cpp:45 locale directory: /app/share/locale
(easyeffects:2): easyeffects-DEBUG: 19:22:25.391: presets_manager.cpp:49 system input presets directory: "/app/etc/xdg/easyeffects/input";
(easyeffects:2): easyeffects-DEBUG: 19:22:25.391: presets_manager.cpp:49 system input presets directory: "/etc/easyeffects/input";
(easyeffects:2): easyeffects-DEBUG: 19:22:25.391: presets_manager.cpp:49 system input presets directory: "/etc/xdg/easyeffects/input";
(easyeffects:2): easyeffects-DEBUG: 19:22:25.391: presets_manager.cpp:52 system output presets directory: "/app/etc/xdg/easyeffects/output";
(easyeffects:2): easyeffects-DEBUG: 19:22:25.391: presets_manager.cpp:52 system output presets directory: "/etc/easyeffects/output";
(easyeffects:2): easyeffects-DEBUG: 19:22:25.391: presets_manager.cpp:52 system output presets directory: "/etc/xdg/easyeffects/output";
(easyeffects:2): easyeffects-DEBUG: 19:22:25.391: presets_manager.cpp:194user presets directory already exists: /home/ragraf/.var/app/com.github.wwmm.easyeffects/config/easyeffects/
(easyeffects:2): easyeffects-DEBUG: 19:22:25.391: presets_manager.cpp:194user presets directory already exists: /home/ragraf/.var/app/com.github.wwmm.easyeffects/config/easyeffects/input
(easyeffects:2): easyeffects-DEBUG: 19:22:25.391: presets_manager.cpp:194user presets directory already exists: /home/ragraf/.var/app/com.github.wwmm.easyeffects/config/easyeffects/output
(easyeffects:2): easyeffects-DEBUG: 19:22:25.391: presets_manager.cpp:194user presets directory already exists: /home/ragraf/.var/app/com.github.wwmm.easyeffects/config/easyeffects/autoload/input
(easyeffects:2): easyeffects-DEBUG: 19:22:25.391: presets_manager.cpp:194user presets directory already exists: /home/ragraf/.var/app/com.github.wwmm.easyeffects/config/easyeffects/autoload/output
Failed to register: Timeout was reached
(easyeffects:2): easyeffects-DEBUG: 19:22:50.417: easyeffects.cpp:60 Exitting the main function with status: 1
Program exits.
Additional Information
I'm a new user and just trying to get EasyEffects to run.
Run it in debug mode so we can see more information G_MESSAGES_DEBUG=easyeffects flatpak run com.github.wwmm.easyeffects.
Updated main post with degug log. Sorry for excluding it!
No problems. Under normal circumstances there would be many more lines. So it seems the process is failing in the first initialization phases. Most likely some kind of gtk4 problem. Did you notice anything unusual in the Flatpak package update @vchernin ?
Did you notice anything unusual in the Flatpak package update @vchernin ?
Everything seems normal, so I assume this is particular to this system. Could it be pipewire not working? Since the wrapper script no longer checks for it, and I don't think linux mint uses pipewire by default yet.
Could it be pipewire not working?
Usually there are more lines in the logs in this case. I think that the Failed to register: Timeout was reached is related to gtk.
In this case https://github.com/tchx84/Flatseal/issues/310 someone saw the same timeout message and a reboot solved it. It is worth a try @ReedGraf .
No change after reboot:
(process:2): easyeffects-DEBUG: 21:02:29.034: easyeffects.cpp:35 easyeffects version: 7.0.5
(process:2): easyeffects-DEBUG: 21:02:29.034: easyeffects.cpp:45 locale directory: /app/share/locale
(easyeffects:2): easyeffects-DEBUG: 21:02:29.052: presets_manager.cpp:49 system input presets directory: "/app/etc/xdg/easyeffects/input";
(easyeffects:2): easyeffects-DEBUG: 21:02:29.052: presets_manager.cpp:49 system input presets directory: "/etc/easyeffects/input";
(easyeffects:2): easyeffects-DEBUG: 21:02:29.052: presets_manager.cpp:49 system input presets directory: "/etc/xdg/easyeffects/input";
(easyeffects:2): easyeffects-DEBUG: 21:02:29.052: presets_manager.cpp:52 system output presets directory: "/app/etc/xdg/easyeffects/output";
(easyeffects:2): easyeffects-DEBUG: 21:02:29.052: presets_manager.cpp:52 system output presets directory: "/etc/easyeffects/output";
(easyeffects:2): easyeffects-DEBUG: 21:02:29.052: presets_manager.cpp:52 system output presets directory: "/etc/xdg/easyeffects/output";
(easyeffects:2): easyeffects-DEBUG: 21:02:29.052: presets_manager.cpp:194user presets directory already exists: /home/ragraf/.var/app/com.github.wwmm.easyeffects/config/easyeffects/
(easyeffects:2): easyeffects-DEBUG: 21:02:29.052: presets_manager.cpp:194user presets directory already exists: /home/ragraf/.var/app/com.github.wwmm.easyeffects/config/easyeffects/input
(easyeffects:2): easyeffects-DEBUG: 21:02:29.052: presets_manager.cpp:194user presets directory already exists: /home/ragraf/.var/app/com.github.wwmm.easyeffects/config/easyeffects/output
(easyeffects:2): easyeffects-DEBUG: 21:02:29.052: presets_manager.cpp:194user presets directory already exists: /home/ragraf/.var/app/com.github.wwmm.easyeffects/config/easyeffects/autoload/input
(easyeffects:2): easyeffects-DEBUG: 21:02:29.052: presets_manager.cpp:194user presets directory already exists: /home/ragraf/.var/app/com.github.wwmm.easyeffects/config/easyeffects/autoload/output
Failed to register: Timeout was reached
(easyeffects:2): easyeffects-DEBUG: 21:02:54.063: easyeffects.cpp:60 Exitting the main function with status: 1
This is an article from May 2023: http://techzle.com/pipewire-under-linux-mint-cinnamon
PipeWire is already installed with Linux Mint Cinnamon 21.1. Unfortunately, this version appears to have problems with, among other things, the internal audio interface.
Don't know if it's the reality, but Mint does not seem the best distribution to run EasyEffects.
I have the same issue however I am running Arch linux. I am aware that there is another post which is almost identical (Not a complete duplicate however) in #2455 . I have the same issue. Furthermore, I have tried rebooting and still no window output. I am on XFCE not sway. As far as pipewire goes, I have it installed and configured.
I don't like to post about issues without at least suggesting some sort of solution to get the ball rolling with the developers. So I obviously am not an expert in this but I think that there is some sort of conflict that isn't being recorded. I think that there should be some more verbose logs that show so that there is more room to work with.
Like I said I'm not an expert so don't take offense if my suggestion is wild or stupid I just didn't want to complain without at least trying to help.
Like I said I'm not an expert so don't take offense if my suggestion is wild or stupid I just didn't want to complain without at least trying to help.
No problems. Adding more warnings on our side may not be of much help in this case. For example the warning Failed to register: Timeout was reached is not being printed by EasyEffects but by some library we use. I am not sure if GTK, PipeWire or something else possibly Flatpak related. The thing is that the issue seems to be happening so soon that EasyEffects does not even have time to print most of its logs.
I can confirm that I also have this issue. Running Pop!_OS 22.04 LTS under Wayland GNOME 42.9 and Pipewire 0.3.74 installed.
Ever since I ran apt to update a bunch of pipewire related packages, EasyEffects as well as Sound Output Device Chooser GNOME extension by kgshank stopped working. Not sure if it's directly related to pipewire packages or something else that changed during one of the apt upgrades.
I will try to install older versions of the packages and see if they change anything.
UPDATE: So I checked my apt history and the version of pipewire that I had before was 0.3.72. I can't downgrade to it as the apt source from pop os has frozen this version somehow. I will try to make a backup and run some tests.
UPDATE 2: So apparently Pop!_OS completely erased pipewire 0.3.72 and I can't download it as there is no Pop apt archive that I can find that would have it.
Same issue. Mint 21.2, looking through it, Pipewire is version 3.48-1ubuntu3. Trying to find if a newer version of pipewire will fix it, since it was mentioned in a previous issue.
Okay, Pipewire, needs to be installed! It says it is but it isn't really.
However, I have no audio at the moment, so I need to figure that out now.
Is there anything unusual in the output of sudo journalctl -b | grep -i easyeffects or sudo journalctl -b | grep -i pipe when the problem happens?
It says it is but it isn't really.
That is a problem. But sometimes it also happens that people have only the part of PipeWire that deals with video and not the one that replaces Pulseaudio. So that is something to have in mind. For PipeWire to manage audio Pulseaudio has to be removed.
The no audio was caused by pipewire outputting audio to my controller's HD rumble driver, which I tried to stop but just unplugged it instead.
Mint only comes installed with that one pipewire package, which isn't the entire set, so it doesn't function until you have everything.
-Maybe add a warning to easy effects prompting the user to check if all pipewire modules are installed and enabled if it times out? No idea how feasible that is looking at the first few replies of this thread.
-Maybe add a warning to easy effects prompting the user to check if all pipewire modules are installed and enabled if it times out? No idea how feasible that is looking at the first few replies of this thread.
There used to be a semi helpful warning at least in flatpak builds, but it was removed as it became unreliable and reported false positives. But there might one day be a new warning which hopefully could help for these issues. See https://github.com/wwmm/easyeffects/issues/2327. Maybe it is possible to check if pipewire-pulse is running.
I guess for OP and anyone ever coming across this ever, the process (As of Linux Mint 21) is as follows:
sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream
sudo apt update
sudo apt install pipewire pipewire-media-session pipewire-audio-client-libraries
systemctl --user daemon-reload
systemctl --user --now disable pulseaudio.service pulseaudio.socket
systemctl --user mask pulseaudio
systemctl --user --now enable pipewire pipewire-media-session.service
Then reboot.
Maybe add a warning to easy effects prompting the user to check if all pipewire modules are installed and enabled if it times out?
The problem is that is it is not clear where the freezing is happening. Based on the logs provided so far EasyEffects does not even get to the point where it should print the PipeWire version being used. For the freezing to be happening so soon the only thing I can think of is that the PipeWire call freezing is pw_init. But this is a void function. It does not return a value to be checked or accept a timeout value as argument. If this is really the place where the hang is happening there is not much we can do.
And searching the user computer for PipeWire libraries isn't something viable because different distributions organize files in different ways. it is not going to take long for this approach to cause false positives in some users installations.
Whatever the problem was on my side, it seems that EasyEffects is working now. So at least it was not a problem with that specific version of Pipewire, as I am using the same now and it works.
I also checked /var/log/dpkg.log to see what changed between the time I noticed the bug (the presumed pipewire upgrade) and today, and no pipewire related packages (or gtk for that matter) have changed.
I am experiencing another bug though, for which I will open a new issue if it hasn't been opened already.
Getting this issue right now on Fedora 39. I could fix it by logging out of GNOME. Restarting pipewire didn't help.
Getting this issue right now on Fedora 39. I could fix it by logging out of GNOME. Restarting pipewire didn't help.
As EasyEffects is not able to restart itself automatically when pipewire is restarted it is necessary to kill it easyeffects -q and restart it manually if pipewire dies or is restarted by the user.
Is there anything unusual in the output of
sudo journalctl -b | grep -i easyeffectsorsudo journalctl -b | grep -i pipewhen the problem happens?
I get this: Jan 03 15:50:06 rexommendation-550 dbus-daemon[825]: [session uid=1000 pid=825] Activating service name='com.github.wwmm.easyeffects' requested by ':1.17' (uid=1000 pid=954 comm="/usr/bin/plasmashell --no-respawn") Jan 03 15:50:06 rexommendation-550 dbus-daemon[825]: [session uid=1000 pid=825] Successfully activated service 'com.github.wwmm.easyeffects' Jan 03 15:50:07 rexommendation-550 easyeffects[1499]: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
Jan 03 15:50:07 rexommendation-550 easyeffects[1499]: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
@wereretot this should only affect the app theme. It usually is nor related to it not showing the window.
Do you also have the error Failed to register: Timeout was reached printed in the terminal when you execute EasyEffects in debug mode?
Jan 03 15:50:07 rexommendation-550 easyeffects[1499]: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
@wereretot this should only affect the app theme. It usually is nor related to it not showing the window.
Do you also have the error
Failed to register: Timeout was reachedprinted in the terminal when you execute EasyEffects in debug mode?
No, my notification does though.
For Arch I was able to revert to pipewire-media-session from wireplumber and this seemed to resolve the issue opening easyeffects
Current packages: gst-plugin-pipewire pipewire pipewire-alsa pipewire-jack pipewire-media-session pipewire-pulse
Once I overcame this issue I ran into another which is probably not related but wanted to connect the two in case... https://github.com/wwmm/easyeffects/issues/2954
