Description of problem: 

I had an older version of vagrant on my laptop which was not working for some reason, so I ran "dnf remove vagrant". It came up with a list of 47 other packages to remove, most of which seemed to be ruby packages. I let it go without checking too closely, and one of the packages it removed was sqlite, meaning dnf stopped working after that.

I got the binaries for sqlite off another box and dnf happily installed the latest version of vagrant (which I'd already downloaded), and it required no dependencies.

I then tried to use rpm -ql on a package, and rpm wouldn't work as nss was missing. I checked back (same xterm open luckily), and nss was not in the list of packages dnf was supposed to remove. Everything else seemed to be working, it was getting towards hometime in the office so I thought I'd get back to it in the morning.

I work in a government office, so my laptop has an encrypted drive. This morning it wouldn't boot. Type in the disk password, see it crash with a kernel panic. I booted from a fedora-live image on a USB stick and had a look around (cryptsetup open worked ok with the password, so it hasn't been trashed). libbd_crypto was missing, so I copied over the library files into /usr/lib64 on the mounted disk. That's another package which hadn't been listed to be removed by dnf. Still wouldn't boot from the hard disk though.

My guess is that something else important has been removed by stealth. It would be nice to know what!


Version-Release number of selected component (if applicable): Fedora 23 latest


How reproducible: Only tried once, that was enough!

Steps to Reproduce:
1. Install Fedora 23 with encrypted hard disk
1. use dnf to install vagrant from local rpm package
2. use dnf to remove vagrant, with list of dependencies
3. reboot

Actual results:

Kernel panic on boot, presumably due to some other missing dependencies that dnf removed

Expected results:

Usable system

Additional info:

Output from boot log follows:
...
[ OK ] Reached target Switch Root.
[ OK ] Started Plymouth switch root service.
       Starting Switch Root...
[  17.230869] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[  17.230869] 
[  17.231183] CPU: 0 PID: 1 Comm: systemd Not tainted 4.3.5-300.fc23.x86_64 #1
[  17.231183] Hardware name: TOSHIBA SATELLITE C50D-B/ZBWAE, BIOS 1.0 04/13/2014
[  17.231183]  0000000000000000 00000000c098e8de ffff88042d6c7e00 ffffffff813a643f
[  17.231183]  ffffffff81a4e420 ffff88042d6c7e88 ffffffff811a4521 ffff880400000010
[  17.231183]  ffff88042d6c7e98 ffff88042d6c7e30 00000000c098e8de 0000000000000001
[  17.231183] Call Trace:
[  17.231183]  [<ffffffff813a643f>] dump_stack+0x44/0x55
[  17.231183]  [<ffffffff811a4521>] panic+0xd3/0x20b
[  17.231183]  [<ffffffff810a3c13>] do_exit+0xad3/0xae0
[  17.231183]  [<ffffffff810a3ca7>] do_group_exit+0x47/0xb0
[  17.231183]  [<ffffffff810a3d24>] SyS_exit_group+0x14/0x20
[  17.231183]  [<ffffffff81781e2e>] entry_SYSCALL_64_fastpath+0x12/0x71
[  17.231183] Kernel Offset: disabled
[  17.231183] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[  17.231183]