Description of problem: update the packages rtkit with dnf in the cleaning process occurs and error Version-Release number of selected component (if applicable): Upgrade rtkit-0.11-20.fc29.x86_64 @fedora ** Upgraded rtkit-0.11-19.fc29.x86_64 @@System How reproducible: always Steps to Reproduce: 1. dnf update 2. 3. Actual results: error Expected results: cleaning process works well Additional info: Ejecutando prueba de operaciones [1835/1887] Prueba de operación exitosa. Ejecutando operación Preparando : 1/1 Ejecutando scriptlet: blivet-data-1:3.1.1-2.fc29.noarch 1/1 Upgrading : blivet-data-1:3.1.1-2.fc29.noarch 1/8 Upgrading : python3-blivet-1:3.1.1-2.fc29.noarch 2/8 Ejecutando scriptlet: rtkit-0.11-20.fc29.x86_64 3/8 Upgrading : rtkit-0.11-20.fc29.x86_64 3/8 Ejecutando scriptlet: rtkit-0.11-20.fc29.x86_64 3/8 Upgrading : lollypop-master-20181013-1.fc29.noarch 4/8 Limpieza : python3-blivet-1:3.1.1-1.fc29.noarch 5/8 Limpieza : blivet-data-1:3.1.1-1.fc29.noarch 6/8 Limpieza : lollypop-master-20181012-1.fc29.noarch 7/8 Ejecutando scriptlet: rtkit-0.11-19.fc29.x86_64 8/8 /var/tmp/rpm-tmp.mmJtW1: línea 1: fg: no hay control de trabajos error: %preun(rtkit-0.11-19.fc29.x86_64): macro de ejecución de guión fallido, e stado de terminación 1 Error in PREUN scriptlet in rpm package rtkit Error in PREUN scriptlet in rpm package rtkit error: rtkit-0.11-19.fc29.x86_64: borrar falló Verificando : lollypop-master-20181013-1.fc29.noarch 1/8 Verificando : lollypop-master-20181012-1.fc29.noarch 2/8 Verificando : blivet-data-1:3.1.1-2.fc29.noarch 3/8 Verificando : blivet-data-1:3.1.1-1.fc29.noarch 4/8 Verificando : python3-blivet-1:3.1.1-2.fc29.noarch 5/8 Verificando : python3-blivet-1:3.1.1-1.fc29.noarch 6/8 Verificando : rtkit-0.11-20.fc29.x86_64 7/8 Verificando : rtkit-0.11-19.fc29.x86_64 8/8 Actualizado: lollypop-master-20181013-1.fc29.noarch blivet-data-1:3.1.1-2.fc29.noarch python3-blivet-1:3.1.1-2.fc29.noarch rtkit-0.11-20.fc29.x86_64 Fallido: rtkit-0.11-19.fc29.x86_64 Error: Falló la transacción ======================================================================== Transaction ID : 766 Begin time : Sat Oct 13 08:47:06 2018 Begin rpmdb : 3274:d1e5df521be6dea9ae1bbad639157919828263b5 End time : Sat Oct 13 08:47:27 2018 (21 seconds) End rpmdb : 3276:bb38cd1a4381e1a92f64bf714ff1850baa86984c User : H H L P <hhlp> Return-Code : Success Releasever : 29 Command Line : upgrade Packages Altered: Upgrade lollypop-master-20181013-1.fc29.noarch @gnumdk-lollypop Upgraded lollypop-master-20181012-1.fc29.noarch @@System Upgrade blivet-data-1:3.1.1-2.fc29.noarch @fedora Upgraded blivet-data-1:3.1.1-1.fc29.noarch @@System Upgrade python3-blivet-1:3.1.1-2.fc29.noarch @fedora Upgraded python3-blivet-1:3.1.1-1.fc29.noarch @@System Upgrade rtkit-0.11-20.fc29.x86_64 @fedora ** Upgraded rtkit-0.11-19.fc29.x86_64 @@System Scriptlet output: 1 /var/tmp/rpm-tmp.mmJtW1: línea 1: fg: no hay control de trabajos 2 error: %preun(rtkit-0.11-19.fc29.x86_64): macro de ejecución de guión fallido, estado de terminación 1 3 error: rtkit-0.11-19.fc29.x86_64: borrar falló =============================================== rpm -qa rtkit* rtkit-0.11-19.fc29.x86_64 rtkit-0.11-20.fc29.x86_64 ================================================ Reinstalling: rtkit x86_64 0.11-20.fc29 fedora 54 k replacing rtkit.x86_64 0.11-20.fc29 Transaction Summary =============================================================================== Total size: 54 k Is this ok [y/N]: y Downloading Packages: [SKIPPED] rtkit-0.11-20.fc29.x86_64.rpm: Already downloaded Running transaction check Transaction check succeeded. Running transaction test The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Transaction check error: file /usr/libexec/rtkit-daemon from install of rtkit-0.11-20.fc29.x86_64 conflicts with file from package rtkit-0.11-19.fc29.x86_64 file /usr/sbin/rtkitctl from install of rtkit-0.11-20.fc29.x86_64 conflicts with file from package rtkit-0.11-19.fc29.x86_64 Error Summary -------------
*** This bug has been marked as a duplicate of bug 1637496 ***