Comments

379 Comments

This update has been unpushed.

error......is use = i use

Do you give positive karma when is use Recommends: earlyoom?

You can't do systemctl disable earlyoom if you don't like it?

No, this isn't true. I've tested this several times and since f34 systemd-oomd-defaults is installed as default. Please read https://fedoraproject.org/wiki/Changes/EnableSystemdOomd and https://bugzilla.redhat.com/show_bug.cgi?id=1933494 Removing systemd-oomd-defaults will disable systemd-oomd.service. So, Conflicts: systemd-oomd-defaults is needed to remove systemd-oomd-defaults from existing installations, otherwise 2 oom memory services are enabled. And sorry, that you never experience memory problems isn't the point. Here is a user who reported the problem. systemd-oomd kills the whole mate session because of missing cgroups support. https://bugzilla.redhat.com/show_bug.cgi?id=2068699 Please revert your negative karma.

And if you not trust me and all the people from reports. Revert this update, install systemd-oomd-defaults, and try again to install the update :)

BZ#2068699 Disable systemd-oomd when MATE desktop is used

Fact is that you're blocking this well tested change since more than 1.5 years. Start again working on it instead of making noise here.

This is not the place to report an issue! Please use redhat bugzilla. PS: all mounting actions are handled by the gvfs package in the background

karma

Sorry, BZ#1941366 isn't fixed. With default config there is no audio signal on subwoofer speaker.

BZ#1941366 NO sound on subwoofer after update from f32 to f34

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?

Please do not merge! This breaks mate-panel which is the main contributor of libwnk3. See https://github.com/mate-desktop/mate-panel/issues/1230

LGTM

BZ#1435423 Need to fix wallpaper / background packaging situation
karma

LGTM

BZ#1891137 compiz stack needs update to 0.8.18
karma

LGTM, thanks for updating.

BZ#1891137 compiz stack needs update to 0.8.18

LGTM

BZ#1872445 conflict between MATE 33 wallpaper package dependencies

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

BZ#1872445 conflict between MATE 33 wallpaper package dependencies

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)

BZ#1872445 conflict between MATE 33 wallpaper package dependencies

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.

BZ#1872445 conflict between MATE 33 wallpaper package dependencies

This is wrong. Please do not merge!

I have to change a default gsettings key which define the location for the default background.

org.mate.background picture-filename

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

BZ#1872445 conflict between MATE 33 wallpaper package dependencies
karma

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.

BZ#1846742 upgrading to alsa-lib-1.2.3 kills pulseaudio in multi soundcard environment
BZ#1847508 No sound with Creative Soundblaster Z since update to alsa-lib-1.2.3-8