---
title: "Package is in a very bad inconsistent state"
url: https://michalasobczak.pl/posts/package-is-in-a-very-bad-inconsistent-state.html
author: "Michał Sobczak"
description: "Aborting Ubuntu packages update via Ansible gave me some weird state of libatk-wrapper-java-jni package. My playbook installs default-jre and it was painfully slow so I thought that there is some lockup, but there was not."
published: 2022-09-02T10:17:57.000Z
updated: 2022-09-06T10:42:36.000Z
language: en
categories: ["Technology"]
tags: ["Ubuntu"]
license: CC BY-NC-ND 4.0 (https://creativecommons.org/licenses/by-nc-nd/4.0/)
---
# Package is in a very bad inconsistent state

Aborting Ubuntu packages update via Ansible gave me some weird state of `libatk-wrapper-java-jni` package. My playbook installs `default-jre` and it was painfully slow so I thought that there is some lockup, but there was not. My VM performed poorly at that moment, probably due to the fact that it came from a HDD with badblocks which got migrated to another one. It just works, but I’m not 100% sure if it is healhty. So… in case you have some broken package installation try:

```bash
sudo apt-get install --reinstall libatk-wrapper-java-jni
```

And now you are good to go with autoclean, update and possibly upgrade to check whether really there is no problem still dangling on your system. On mine, it is fine now.