"..., so now when I reattempt I get a message the the data base is in use most likely by a another running copy of the program ( no not really )"
Did you try to see the whether apt or adept process is not still locking the database?
Could You please try something like "ps aux | grep adept" or "ps aux | grep apt" in konsole? It is possible that adept's crash brought down the gui, but left a process locking the db....
For what regards the initial part of your report, it is a known issue, reported in bug #85800 and #85864, so I'll mark it as a duplicate of them. I also agree this is a showstopper.
"..., so now when I reattempt I get a message the the data base is in use most likely by a another running copy of the program ( no not really )"
Did you try to see the whether apt or adept process is not still locking the database?
Could You please try something like "ps aux | grep adept" or "ps aux | grep apt" in konsole? It is possible that adept's crash brought down the gui, but left a process locking the db....
For what regards the initial part of your report, it is a known issue, reported in bug #85800 and #85864, so I'll mark it as a duplicate of them. I also agree this is a showstopper.
Best Regards,
Witold