@manjaro-team
can you check status mirrors ?
I you want to continue to use PulseEffects, you require Pipewire indeed. On another side there is PulseEffects Legacy which uses PulseAudio.
I guess that depends on how you ‘replace’ things.
I don’t believe so, Pipewire is not a Flatpak dependency.
TLDR: read PulseEffect development announces, especially the last one when they made their big move from Pulseaudio to PipeWire, and also the forum where this has been discussed a lot, and the simple solution back then was to not replace PulseAudio with the new, to me experimental, PipeWire thing, but using PulseEffects Legacy which was the previous version before the big change.
pipewire is a dependency of xdg-desktop-portal which flatpak depends on.
1 Like
this Testing is now on mirrors after 24h ,
only 1/3 are in Green ( ok) , all others (2/3) are not synchronized in UE
The mirrors with IPv6 can’t sync anymore. I guess because AAAA DNS records were added to all manjaro servers. Now the IPv6 addresses of mirror servers are not whitelisted in the firewall of the repo server it seems.
I’ll create another thread.
edit
1 Like
GRUB-update ===> ERROR: Warnung: os-prober was executed to detect other bootable partitions.
As I start Wind**fs from /etc/grub.d/40_custom
AND have: GRUB_DISABLE_OS_PROBER=true in /etc/default/grub (wird missachtet!!!/ is disregarded !!!)
.
Solution: root-edit the file /usr/bin/os-prober and uncomment line 11: # ./usr/share/os-prober/common..sh
pamac-tray-icon-plasma 0.1.2-4 now opens up pamac to a correct Featured view! 
1 Like
Exactly.
Well, I’m just gonna put the first sentence of the post which you so thoroughly cite:
And indeed, afterwards, I installed pulseeffects-legacy (cos’, you know, before posting, I try stuff, read here and there and so on…).
If people want to install pamac-flatpak-plugin, they will end up having to install pipewire as a dependency. This being the testing branch, I thought it would be useful to let the devs know of that problem (pulseeffects requiring pipewire-pulse which conflicts with pulseaudio) when these packages get pushed to stable. But what do I know, right?
I can confirm here. As I only have one system to start on this computer, it is not necessary to run os-prober so I also had set GRUB_DISABLE_OS_PROBER=true in /etc/default/grub.
Nevertheless, os-prober is enabled by this update. I am sure that there are very sophisticated reasons for this decision. Hence, I’d greatly appreciate some clarification why this step was necessary in order to allow me to understand.
For the time being, I have followed the advice and commented out ./usr/share/os-prober/common.sh in /usr/bin/os-prober on line 11.
3 Likes
@Berneri (and all): if you experience “cracky” sound when using pipewire (especially if you use pulseeffects), then try to play around with these parameters inside /etc/pipewire/pipwire.conf:
default.clock-quantum=32
that fixed it for me.
1 Like
Using latest Gnome, no issues with update. Smooth and stable
Thanks mate
Just curious: How much RAM do you have installed on your machine?
I am asking this because I have been told that in order to run Gnome, it is recommended to have at least 64 GBytes of RAM installed. As you are even saying that it is running “smooth”, I assume that you have more than that, for example, 128 GB RAM, correct?
3 Likes
Where do those (huge) numbers come from? That sounds outright ridiculus.
If the machine mentioned here was used, that would be 8GB.
My machine equipped with 32GB uses (running gnome) 9% of RAM running Firefox…
Somebody jokes on you 
You can run it in 2GB no problem. In order to surf and have some programs open at least 4, and some swap.
Yes, 8 GB RAM
And that’s indeed sufficient for running Gnome? I thought that this is not enough to use anything beyond XFCE…
I’ve been running Gnome on my five years old Asus with 6 gb no problem, buttery smooth bu I’d say an ssd is essential. Switched to KDE though since I value the configurability, eqally smooth.