Hmm, where are the config files with 0.3.25-2.fc34.x86_64 ?
[root@mother rave]# dnf provides /etc/pipewire/client.conf Last metadata expiration check: 0:24:58 ago on Fri Jul 2 13:08:10 2021. pipewire-libs-0.3.25-1.fc34.i686 : Libraries for PipeWire clients Repo : fedora Matched from: Filename : /etc/pipewire/client.conf pipewire-libs-0.3.25-1.fc34.x86_64 : Libraries for PipeWire clients Repo : fedora Matched from: Filename : /etc/pipewire/client.conf [root@mother rave]# dnf provides /etc/pipewire/client-rt.conf Last metadata expiration check: 0:25:11 ago on Fri Jul 2 13:08:10 2021. pipewire-libs-0.3.25-1.fc34.i686 : Libraries for PipeWire clients Repo : fedora Matched from: Filename : /etc/pipewire/client-rt.conf pipewire-libs-0.3.25-1.fc34.x86_64 : Libraries for PipeWire clients Repo : fedora Matched from: Filename : /etc/pipewire/client-rt.conf [root@mother rave]# dnf provides /etc/pipewire/pipewire-pulse.conf Last metadata expiration check: 0:25:20 ago on Fri Jul 2 13:08:10 2021. pipewire-pulseaudio-0.3.25-1.fc34.x86_64 : PipeWire PulseAudio implementation Repo : fedora Matched from: Filename : /etc/pipewire/pipewire-pulse.conf [root@mother rave]# rpm -qa pipewire-libs pipewire-libs-0.3.31-2.fc34.x86_64 [root@mother rave]# rpm -qa pipewire-pulseaudio pipewire-pulseaudio-0.3.31-2.fc34.x86_64
Is this the expected behaviour?
I tested it for myself. Installing Mate desktop environment from Cinnamon-spin-installation works like a charm when using the correct command, and f33-backgrounds-base-33.0.2-1.fc33.noarch f33-backgrounds-gnome-33.0.2-1.fc33.noarch are installed See my post at https://bugzilla.redhat.com/show_bug.cgi?id=1872445#c7
I found the real cause of the issue, see https://bugzilla.redhat.com/show_bug.cgi?id=1872445#c6 The user installs the mate-desktop package and the mate-desktop environment, which can be produce conflicts in this early stage of development (before beta).
(sudo dnf install mate-desktop @mate).
So, this update isn't needed because it doesn't fix the real problem (using wrong command line)
The default of Mate is using a static xml background since f23. And this file is removed! So shipping only mate-background-properties/f33.xml which isn't a static background is wrong. We need a static xml background file which was /usr/share/backgrounds/mate/default.xml
So, this update breaks the common usage of a background for MATE.
This is wrong. Please do not merge!
I have to change a default gsettings key which define the location for the default background.
This key is defined by a gsettings override from mate-desktop package.
What is the problem with using /usr/share/backgrounds/mate/default.xml ? I mean which file does conflict with /usr/share/backgrounds/mate/default.xml ?.
With the new dir /usr/share/mate-background-properties/f33.xml i have to change the gesettings key again every 6 month with a new fedora release, because of using a number in name! Sorry , i can't except that.
If you really want to change the location, can you please use /usr/share/mate-background-properties/default.xml ? This should be a symlink to /usr/share/backgrounds/f33/default/f33.xml
Works fine for. It fixes the issue with using alsa direct with external (dmix) plugin and Creative soundblaster Z. And i saw no issues with using pulseaudio with on onboard and soundblaster card in a quick test.
LGTM, Can this be pushed to stable please. We need this to fix our travis CI builds at github. https://travis-ci.org/github/mate-desktop/libmateweather/builds/690141817 Thank you.