I was under impression that PackageKit was fixed to perform equivalent of "zypper dup" on TW. Well, apparently it is not. I perform updates via GNOME Software (not intentionally, it is what I got as default after installation and just stick with it). It insists on offline updates which is fine as well (this is VM that runs on demand only). Every now and then offline update claims to complete in a couple of seconds and nothing is applied. I finally got a look and what happens: Mar 14 19:05:05 tw pk-offline-update[564]: percentage 0% Mar 14 19:05:05 tw pk-offline-update[564]: percentage 100% Mar 14 19:05:05 tw pk-offline-update[564]: sent msg to plymouth 'Installing Updates - 100%' Mar 14 19:05:05 tw pk-offline-update[564]: status finished Mar 14 19:05:05 tw PackageKit[586]: update-packages transaction /1_becaeadd from uid 0 finished with failed after 4098ms Mar 14 19:05:05 tw pk-offline-update[564]: writing failed results Mar 14 19:05:05 tw pk-offline-update[564]: failed to update system: maven-doxia-module-markdown-1.7-2.1.noarch requires mvn(org.apache.maven.doxia:doxia-core) = 1.7, but this requirement cannot be provided Mar 14 19:05:15 tw pk-offline-update[564]: rebooting But zypper dup happily removes this package without any conflicts ( 12/722) Removing maven-doxia-module-markdown-1.7-2.1.noarch ............[done] So whatever PackageKit offline update does is not the same as what zypper dup does. Secondary problem is that there is no indication of failed updates at all. Neither during offline update nor any notification after system is rebooted. Happy to file bug report if this is unexpected. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org