[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2023-10-22 Thread Milachew
This can also be fixed by a simple build of pulseeffects version 4.8.7. I tried to do it on Ubuntu 22.04 and autorun worked. A minor update of the pulseeffects version should fix the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-10-12 Thread soonan
I wrote a solution on this GitHub thread:https://github.com/wwmm/easyeffects/issues/1644 However I think this package should get an update to fix this. Thanks! ** Bug watch added: github.com/wwmm/easyeffects/issues #1644 https://github.com/wwmm/easyeffects/issues/1644 -- You received this

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-08-31 Thread Jo Grey
Can someone explain in a noob friendly way how to install the 4.8.7-1 version from the kinetic testing repo? I am experiencing this bug on Linux Mint 21 XFCE (Jammy) and PulseEffects 4.8.4-1 and don't know enough to be able to figure it out on my own... can you post the terminal commands to

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-07-13 Thread Anon
Version 4.8.7-1 from kinetic fixes this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1948882 Title: PulseEffects does not properly initialize on startup Status in

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-06-19 Thread Roman
I am very unfamiliar with flatpak, but I noticed that current Debian sid includes PulseEffects 4.8.7. I've downloaded the following set from there: pulseeffects main package, the supporting set of gstreamer1.0-*-pulseffects packages, and also newer versions of libglibmm-2.4-1v5 and

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-06-18 Thread carlosgs
I have switched to the flatpak version as @del00m proposed and indeed it starts correctly. That version of PulseEffects is 4.8.5 while the repository's is 4.8.4. Changelog for 4.8.5 just says "Improved compatibility with dconf 0.40. Now our plugins should be enabled when using this version.", so

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-06-18 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseeffects (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu.

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-04-26 Thread Roman
Just confirming that the issue moved to Ubuntu Jammy stable relese. The workaround with downgrading DConf to the Hirsute version still works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu.

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-03-16 Thread Roman
An update: I've noticed that my PE had the button "Global Bypass" occasionally activated (somehow without my consent), and after unpressing it the entire chain now works again. But the initial bug is unfortunately there, that is PE does not get activated on sturtup properly. So in 22.04 devel, the

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-03-16 Thread Roman
OK, in devel 22.04 the sound restored after an update, though PE does not actually perform any transformation from the chain... I just hope that after all it will be fixed in the final release, and will work well like it worked in 20.04... If not it seems we have to use the flatpak version. --

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-03-14 Thread DeL00M
Today I tried flatpak version of PulseEffects and it's work for me. Only issue with autostart, but fixed with manually added autostart entry: /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=pulseeffects com.github.wwmm.pulseeffects --gapplication-service -- You received this bug

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-03-14 Thread Roman
After a recent daily update Pulseeffects just stopped working entirely (literal silence from the PE(apps) stream). No idea if this is related to this bug in any way. Difficult to say which package update was responsible for that, seemingly nothing obviously related. I tried to upgrade the system

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-01-14 Thread DeL00M
I can't imagine how did you found this, but thank you so much for this workaround! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1948882 Title: PulseEffects does not

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-01-14 Thread Roman
** Also affects: pulseeffects (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1948882 Title: PulseEffects does not

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

2022-01-14 Thread Roman
Changing this to d-conf because its downgrade helps to eliminate the issue ** Package changed: pulseeffects (Ubuntu) => d-conf (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu.