adept locks software database if it crashes

Bug #117345 reported by cjseyfried
4
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: adept-installer

A number of times, using various releases of kubuntu. Went to add applications using the add/remove applications menu option. During the installation of apps process there was an error and adept could not continue. I exit the application and from then forward can not add / remove or update applications because "some other application is using the database, please close this app." Except there is no version of adept running. The only way I have found to resolve this is to re-install the O/S

Is there another way to unlock the database so adept or the update manager can be used?

Curtis Seyfried
<email address hidden>

Tags: none
Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

cjseyfried,

Thanks for reporting this issue. The solution to the database locking is to run the following from the commandline:

sudo dpkg -configure -a

That should unlock the database for you and get adept working again without a complete reinstall.

If you would like to help us improve Kubuntu you could help us figure out what caused adept to crash in the first place. Could you attach /var/log/dpkg.log from after the crash so we can see if there are any clues in there.

Next some questions:
Any there common features when you observe these crashes?
What were you trying to install when it occurred this time and previous times?
Is it reproducible? Try unlocking the database with the command above then installing whatever caused the crash this time. Does it crash again and if you repeat the process does it crash every time?

Keep an eye on dpkg.log while trying these things and see if there is anything that occurs repeatedly when adept crashes. You can view dpkg.log while adept is installing by clicking the 'show details' button next to the progress bar.

Sorry for all the questions, just trying to diagnose the problem. Thanks for helping to improve Kubuntu.
Richard

Changed in adept:
assignee: nobody → rbirnie
status: Unconfirmed → Needs Info
Revision history for this message
cjseyfried (curtis-seyfried) wrote :

thank you for your reply. the command you gave sudo dpkg -configure -a does not unlock the database, it only give other options for dpkg.

The crash occurred while I was trying to install a number of packages. The problem package seemed to be Sun Java jre, but it has crashed at other times. This has been a problem with the last three relaeses.

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

my mistake there was a typo in the command sorry. It should be 'sudo dpkg --configure -a' Note the second - on the configure option.

The problem with the Sun Java jre packages is a known issue caused by adept failing to display the Java license agreement correctly. I thought this had been fixed. I will investigate and try to find out what is happening.

Richard

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

cjseyfried,

I am told you also need to have the package libperl-qt installed for the handling of the license agreement. Could you check if this is the case on your system. Do you see any kind of dialog asking you to accept a license agreement when you try to install Java? You might need to hit the 'show details' button while adept is installing packages to see it.

If you say that it also happens with other packages then it could be that there is more than one bug here but lets deal with things one at a time.

Richard

Revision history for this message
cjseyfried (curtis-seyfried) wrote :

thank you, that command worked fine now. It proceeded to install all of the remaining packages starting with the sun jre.

Originally when it got to the sun jre the license agreementy box came up, but when I clicked on "Next" it went away and did not proceed to the next screen.

Revision history for this message
cjseyfried (curtis-seyfried) wrote :

Oh, it was the jre mozilla plugin that caused the problem

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

I'm not quite clear, have you got all the packages you wanted installed now. In which case this bug could be closed. Do you still need help with the mozilla plugin? If I remember rightly on the Java license there is a box you have to check labelled 'I accept' or similar. If you don't tick the box adept crashes.

If you have resolved everything let us know and I'll close the bug.

Richard

Revision history for this message
cjseyfried (curtis-seyfried) wrote :

I looked to see if libperl-qt was installed. No it is not, it is not even in the package list as available to be installed

Revision history for this message
cjseyfried (curtis-seyfried) wrote :

Every thing is working fine now. I do not need to install the jre mozilla plug-in

Thank you for all of the assistance.

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

I was misinformed, it's libqt-perl rather than libperl-qt, oops. However, if you've got everything working I will close the bug.

Richard

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

Issue resolved, closing the bug

Changed in adept:
status: Needs Info → Rejected
Revision history for this message
revans (ron-evans) wrote :

I hit this bug too with while installing the Sun Java packages. The problems seems to be caused by my not checking the "I agree" on the license. Execution continued until installation started and I told that I hadn't agreed to the license. Another license agreement came up and I agreed. Shortly after the window closed, adept crashed

Revision history for this message
Michael D. Stemle, Jr. (manchicken) wrote :

This is being worked on.. This is a duplicate of issue #48627.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.