Has anyone else seen this: dpkg slows to a crawl or freezes
For starters, I am really tight on RAM: 256KiB was a big machine when I bought it -- now, it's simply too danged small.
This is intermittent: and I can't figure what is different between failures and successes.
I do most install/remove cycles at a console with Gnome shut down. I run APTITUDE, which in turn calls DPKG. Dpkg goes through reading the package files, changelogs, etc., then prints "Reading database . . . 85%. The percentage clicks right along until 85%. It then might take an hour to get to 90%, another hour or more for 95%. By then, I'm pulling out my hair. If it's bed-time and I can leave the beast to its own misery, I will usually find in the morning [ 6-8 hours later ] that progress has been made, although very possibly it still hasn't finished.
I'm thinking there may be some pathological dependencies, cycles that need to be broken, or the like. That would account for why one package takes forever to install/remove, while another takes a few minutes.
Other than someone else saying they've seen this, and it isn't just my karma. my first question would be: How can I force dpkg to rebuild its database from zero. AVAILABLE seems to be open when things go South.
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Ubuntu dpkg Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask David A. Cobb for more information if necessary.