add --setopt protected_packages=
There is huge amout of red colored packages before zxing-cpp but terminal is overloaded so that can not be copied, the rest is this:
zxcvbn-c x86_64 2.5-5.fc42 <unknown> 3.3 MiB
zxing-cpp x86_64 2.2.1-3.fc42 <unknown> 1.3 MiB
Downgrading:
eom x86_64 1.28.1-1.fc43 updates 7.8 MiB
replacing eom x86_64 1.28.1-6.fc42 updates 7.8 MiB
kquickimageeditor-qt6 x86_64 0.6.0-1.fc43 updates 1.2 MiB
replacing kquickimageeditor-qt6 x86_64 0.6.0-4.fc42 updates 1.2 MiB
strongswan x86_64 6.0.2-6.fc43 fedora 4.3 MiB
replacing strongswan x86_64 6.0.4-2.fc42 updates 4.3 MiB
strongswan-charon-nm x86_64 6.0.2-6.fc43 fedora 80.2 KiB
replacing strongswan-charon-nm x86_64 6.0.4-2.fc42 updates 84.3 KiB
Upgrading:
python-unversioned-command noarch 3.14.3-2.fc43 updates 23.0 B
replacing python-unversioned-command noarch 3.14.3-1.fc43 <unknown> 23.0 B
replacing python-unversioned-command noarch 3.13.12-1.fc42 <unknown> 23.0 B
python3 x86_64 3.14.3-2.fc43 updates 28.9 KiB
replacing python3 x86_64 3.14.3-1.fc43 <unknown> 28.9 KiB
replacing python3 x86_64 3.13.12-1.fc42 <unknown> 28.7 KiB
python3-libs x86_64 3.14.3-2.fc43 updates 43.2 MiB
replacing python3-libs x86_64 3.14.3-1.fc43 <unknown> 43.2 MiB
replacing python3-libs x86_64 3.13.12-1.fc42 <unknown> 40.2 MiB
python3-ply noarch 3.11-33.fc43 updates 564.3 KiB
replacing python3-ply noarch 3.11-30.fc43 <unknown> 575.2 KiB
replacing python3-ply noarch 3.11-26.fc42 <unknown> 565.1 KiB
python3-tkinter x86_64 3.14.3-2.fc43 updates 2.1 MiB
replacing python3-tkinter x86_64 3.14.3-1.fc43 <unknown> 2.1 MiB
replacing python3-tkinter x86_64 3.13.12-1.fc42 <unknown> 1.9 MiB
Transaction Summary:
Upgrading: 5 packages
Replacing: 14 packages
Removing: 2144 packages
Downgrading: 4 packages
Total size of inbound packages is 14 MiB. Need to download 14 MiB.
After this operation, 6 GiB will be freed (install 59 MiB, remove 6 GiB).
Operation aborted by the user.
pipe the output to fpaste and post the URL here.
also how many f42 packages are still reported by rpm?
rpm -qa | grep -c 'fc42'
and the same for fc43 pls: rpm -qa | grep -c 'fc43'
fpaste:
fpaste
rpm -qa | grep -c 'fc42': 2161
rpm -qa | grep -c 'fc43': 3153
looks good. run the distro-sync w/o --assumeno
It outputs the same, with or without those two options: --skip-broken --setopt protected_packages=
I said no because it wants to delete 6gb of stuff so the system might get broken.
it should. But you can accept and continue removing the f42 packages
1 Like
So to do it with --skip-broken --setopt protected_packages= included?
without skip-broken
Okay, it is going to remove 2169 packages so it is going to take a while.
Deleting done, sudo dnf install @lxqt-desktop-environment now outputs this so there is still conflict with packages for f43:
Problem: problem with installed package
- installed package sddm-wayland-plasma-6.6.3-1.fc43.noarch conflicts with sddm-greeter-displayserver provided by sddm-wayland-miriway-25.10-1.fc43.noarch from fedora
- package sddm-wayland-plasma-6.6.3-1.fc43.noarch from updates conflicts with sddm-greeter-displayserver provided by sddm-wayland-miriway-25.10-1.fc43.noarch from fedora
- package sddm-wayland-miriway-25.10-1.fc43.noarch from fedora conflicts with sddm-greeter-displayserver provided by sddm-wayland-plasma-6.4.5-4.fc43.noarch from fedora
- conflicting requests
- installed package sddm-wayland-plasma-6.6.3-1.fc43.noarch conflicts with sddm-greeter-displayserver provided by sddm-wayland-miriway-25.12-1.fc43.noarch from updates
- package sddm-wayland-miriway-25.12-1.fc43.noarch from updates conflicts with sddm-greeter-displayserver provided by sddm-wayland-plasma-6.6.3-1.fc43.noarch from updates
- package sddm-wayland-miriway-25.12-1.fc43.noarch from updates conflicts with sddm-greeter-displayserver provided by sddm-wayland-plasma-6.4.5-4.fc43.noarch from fedora
You may try 2 things:
01/ add the --allowerasing option to dnf
- this may remove
sddm-wayland-plasma - not sure that it will work seen:
- Sddm package conflicts while trying to upgrade to Fedora 41 via dnf
- but it was with
dnf4
or:
02/ add --exclude={lxqt-wayland-session-default-compositor-miriway,sddm-wayland-miriway}
- this will keep
sddm-wayland-plasmaas thesddm-greeter-displayserver - guessing that using:
dnf -q environment info lxqt-desktop-environmentdnf -q group info lxqt-desktop
1 Like
You may also try:
03/ sudo dnf swap sddm-wayland-plasma sddm-wayland-miriway
- then verify that you still can log in in MATE (eventually also KDE)
- if yes, install
@lxqt-desktop-environment
1 Like
And just so you know, both MATE and XFCE are maintained and in development. I don’t know about MATE, but XFCE is even in a transition to be wayland compatible. And at least XFCE has the latest packages in fedora (for example, Thunar, the XFCE file manager, is already in version 4.20.8).
1 Like
Thanks for suggestions! I think I’ll try 2) or 3) and write what happened.
On their respective sites both have last release from 2024. Mate works very well on this pc and I was moved to try something else only because of news that Ubuntu Mate maintainer is stepping away from project. Anyway on your suggestion I’ll try to add xfce also and see what happens. If xfce can be added and has basic stuff I need on this pc then it is great option for me and I’ll be happy to use it, and not only for this pc but also on one more I plan to put in to action.
Those are the main version releases, but they receive regular updates on the individual components, especially XFCE.
1 Like
I tried to add xfce and it went smooth and fine and works well! Thanks! So it is another option besiedes Mate. Now I have to think if I’m going to mess with system at all to try to enable lxqt and risk breaking it in the process. Next thing is to find a way to play youtube videos in 720p from one of them.