Bug 1774975 - DNF wants to remove kernel-core
Summary: DNF wants to remove kernel-core
Keywords:
Status: CLOSED DUPLICATE of bug 1769788
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 31
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-21 10:59 UTC by Erik Skultety
Modified: 2019-11-22 07:31 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-11-22 07:31:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Erik Skultety 2019-11-21 10:59:46 UTC
This bug was initially created as a copy of Bug #1741381

I am copying this bug because: 
This issue still persists on Fedora 31 and after updating all packages and issuing `dnf autoremove` afterwards still results in the same error with the kernel-core package.


Description of problem:
I installed Fedora Workstation 30, opened a terminal and ran `dnf update`. After all updates were installed, I rebooted the machine and ran dnf autoremove. I was then shown this error:

```
Error: 
 Problem: The operation would result in removing the following protected packages: kernel-core
(try to add '--skip-broken' to skip uninstallable packages)
```

`dnf autoremove` will no longer work because of this error. Using --skip-broken doesn't change the output, the same error shows up again.

I ran `dnf update` next, but it was all up to date.

Version-Release number of selected component (if applicable):
4.2.7

How reproducible:
Always, after a fresh install with all updates applied.


Steps to Reproduce:
1. Install F30 Workstation
2. Install all updates
3. Reboot
4. Try to run `dnf autoremove`

This is a regression. I've installed F30 Workstation a couple of weeks ago and this was not reproducible back then.

I did not remove any packages. The steps described to reproduce it are precisely the things I did.

Comment 1 Jaroslav Mracek 2019-11-22 07:31:00 UTC

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


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