Created attachment 1147609 [details]
Output of sudo dnf erase  audacious-devel --debugsolver

Created attachment 1147611 [details]
/var/log/dnf.log

See events:

Apr 14 16:03:03 DDEBUG Command: dnf install audacious-devel

and:

Apr 14 16:22:14 DDEBUG Command: dnf erase audacious-devel

Created attachment 1147612 [details]
/var/log/dnf.rpm.log

See events at Apr 14 16:03:34 and Apr 14 16:22:23

# rpm -q --whatrequires mesa-dri-drivers
tigervnc-server-minimal-1.6.0-1.fc23.x86_64
# rpm -q --whatrequires mesa-dri-drivers.x86_64
no package requires mesa-dri-drivers.x86_64
# rpm -q --whatrequires mesa-dri-drivers.i686
no package requires mesa-dri-drivers.i686

That dependency in tigervnc-server-minimal seems broken, it should require the x86_64 package, no?

Created attachment 1147614 [details]
dnf history userinstalled

(In reply to Jonathan Wakely from comment #4)
> That dependency in tigervnc-server-minimal seems broken, it should require
> the x86_64 package, no?

The problem does seem related to this, and to having both the i686 and x86_64 versions of mesa-dri-drivers installed.

The 32-bit mesa drivers were installed as a dependency of steam.i686 (from rpmfusion), but that meant that the 'mesa-dri-drivers' capability was being provided by two packages, and so the x86_64 package appeared to be redundant. In fact it's not redundant, it's needed by tigervnc-server-minimal which is needed by anaconda-gui, which is needed by anaconda (and is presumably what prevented me starting X? That seems odd though).

If I 'dnf erase steam' then it also removes the mesa-dri-drivers.i686 package that was installed as a dependency, and then after that if I do 'dnf -y install audacious-devel && dnf -y erase audacious-devel' then it doesn't remove mesa-dri-drivers.x86_64

However, after reinstalling steam (and so the mesa-dri-drivers.i686 dependency) I can't reproduce the problem now. Installing and erasing audacious-devel no longer removes the mesa-dri-drivers.x86_64 package.

(In reply to Jonathan Wakely from comment #6)
> However, after reinstalling steam (and so the mesa-dri-drivers.i686
> dependency) I can't reproduce the problem now. Installing and erasing
> audacious-devel no longer removes the mesa-dri-drivers.x86_64 package.

Ignore that, if I 'dnf mark remove mesa-dri-drivers' then I can reproduce the problem again.

I can reproduce the problem reliably with the following (note only audacious-libs is needed, not audacious-devel):

dnf -y install mesa-dri-drivers.i686
dnf -y install audacious-libs
dnf -y erase audacious-libs

This simulates my original setup, where the 32-bit package was required explicitly (by steam.i686) but the 64-bit package was only needed in order to provide the mesa-dri-drivers capability, which was also provided by the 32-bit package.

When removing audacious-libs the mesa-dri-drivers.x86_64 package is judged to be redundant because of the userinstalled i686 package, and so is removed.

Hi, have you used packagekit for package upgrades?

Yes, sometimes, but that shouldn't matter, should it?

Bug 1259865 is about packages *installed* from PK, not updated. Neither DNF nor PK should mark upgraded packages with 'mark install'. That flag should be set on the initial install of the package, to say if it was userinstalled or a dependency, it should not get changed by later updates to existing packages.

The problem seems simple: mesa-dri-drivers.x86_64 is apparently necessary for plymouth to show the login screen on x86_64, but nothing prevents mes-dri-drivers.x86_64 being removed if the 32-bit package is present.

That seems like a packaging bug to me: something should explicitly require mesa-dri-drivers.x86_64 so that DNF doesn't autoremove it.

@Jonathan, I am pretty sure I've had major system components like selinux-policy-targeted being marked for autoremove because they were upgraded by PK.

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

*** This bug has been marked as a duplicate of bug 1259865 ***