adept_manager crashes reproducible when another process is using dpkg database

[Christian González]

steps to reproduce in Kubuntu hardy beta:

1. start adept_manager (or another process like "apt-get update" or synaptic
2. start another adept_manager
2. it tells you that another process is using the db, and you have 3 options:
yes (fix the problem)
no (read only mode)
cancel (cancel)

if you click yes, the "fix" of the problem is a crash of adept_manager
This also is seen with adept_batch.

[SK (stephantom)]

Assigning to the adept source package.

[Emanuel Goscinski (emu--deactivatedaccount)]

Can confirm this.

Start one adept-manager.
Then start another -> The second one asks you the questions (like described by the reporter).
Click on yes and the second adept manager crashes.

A backtrace of the is attached.

kubuntu hardy up-to-date
KDE 3.5.9
adept package: 2.1.3ubuntu24