Bug 2301642 - sddm-wayland-plasma and sddm-x11 conflict on upgrade from F39 to F40
Summary: sddm-wayland-plasma and sddm-x11 conflict on upgrade from F39 to F40
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: sddm
Version: 40
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Neal Gompa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-07-30 13:56 UTC by Tarulia
Modified: 2025-01-19 02:36 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-01-19 02:36:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tarulia 2024-07-30 13:56:22 UTC
Finally got some time to do my system upgrade. I'm currently on Fedora KDE 39, upgrading to 40. However I am running into a package conflict:

Error: 
 Problem: conflicting requests
  - package sddm-wayland-plasma-6.0.3-2.fc40.noarch from fedora conflicts with sddm-greeter-displayserver provided by sddm-x11-0.21.0-4.fc40.noarch from fedora
  - package sddm-x11-0.21.0-4.fc40.noarch from fedora conflicts with sddm-greeter-displayserver provided by sddm-wayland-plasma-6.0.3-2.fc40.noarch from fedora
  - package sddm-x11-0.21.0-4.fc40.noarch from fedora conflicts with sddm-greeter-displayserver provided by sddm-wayland-plasma-6.1.3-2.fc40.noarch from updates
  - package sddm-wayland-plasma-6.1.3-2.fc40.noarch from updates conflicts with sddm-greeter-displayserver provided by sddm-x11-0.21.0-4.fc40.noarch from fedora
  - problem with installed package sddm-x11-0.20.0-4.fc39.noarch
  - sddm-x11-0.20.0-4.fc39.noarch from @System  does not belong to a distupgrade repository

I'm not entirely sure whether sddm-x11 is still required in any way. If it isn't, it should be obsoleted by the new package so it is uninstalled automatically.
OFC --allowerasing is an option, but I'd rather not mess up my system testing it out on the Display Manager :)

Reproducible: Always

Steps to Reproduce:
1. Run Fedora KDE 39
2. dnf system-upgrade download --releasever=40
Actual Results:  
DNF runs into a package conflict for sddm-wayland-plasma and sddm-x11

Expected Results:  
DNF should be able to cleanly download and upgrade packages

This particular install was installed as F37 and upgraded one at a time. So this may or may not be an earlier remnant as well. But considering the changes for defaulting to Wayland, I assume this is connected.

Also I filed this under Fedora 40 because the F40 packages are what's affected, but obviously I'm running F39.

Comment 1 Neal Gompa 2024-07-30 16:29:29 UTC
There's not a straightforward way to resolve this automatically. You should be able to resolve it yourself with "dnf swap sddm-x11 sddm-wayland-plasma" though.

Comment 2 Tarulia 2024-07-30 16:32:41 UTC
Hm, would an Obsoletes on the sddm-wayland-plasma package not do that?

This is a bit unfortunate as it currently is. I mean, I can handle this without much of a problem but for less experienced users that's quite a roadblock...

Comment 3 Neal Gompa 2024-07-31 15:10:57 UTC
The problem is that it would affect *every* Fedora variant that uses SDDM. I tried this once before and it resulted in strange problems for the LXQt spin, for example.

Comment 4 Tarulia 2024-07-31 21:37:46 UTC
Hm OK that is unfortunate. Didn't realise other spins were using the plasma SDDM package. I thought they'd use the generic one (sddm-wayland-generic). That's a headscratcher then 😅

Comment 5 Neal Gompa 2024-08-01 08:50:28 UTC
The hope is to move them to a Wayland implementation for SDDM with F41 with LXQt 2.x. :)

Comment 6 Sergio Basto 2024-12-23 00:14:15 UTC
why we artificially conflicts sddm-wayland-plasma with sddm-x11 ?

Comment 7 Conrad Meyer 2025-01-19 01:25:18 UTC
What's even injecting sddm-wayland-plasma into the system-upgrade flow?  Fedora 40 sddm-x11 works; Fedora 39 sddm-x11 works; but system-upgrade injects this conflicting requirement for seemingly no reason.

Comment 8 Conrad Meyer 2025-01-19 01:27:44 UTC
FYI, adding 'exclude=sddm-wayland-plasma' to /etc/dnf/dnf.conf seems to fix the problem.


Note You need to log in before you can comment on or make changes to this bug.