Ubuntu
dpkg package

Synaptic pakketbeheer

Asked by Vincent023

I can not open synaptic pakketbeheer

My computer wrote this...
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
E: _cache->open() failed, please report.

How and where must i write...
sudo dpkg --configure -a

Please can you write the answer in Dutch

Thanks
Vincent

Update: Inmiddels heb ik mijn terminalvenster gevonden
Update: vincent@vincent-desktop:~$ dpkg --configure -a
dpkg: deze bewerking kan alleen uitgevoerd worden door de beheerder
'het lijkt dus te werken, maar het terminalvenster ziet mij niet als beheerder...hoe los ik dit op ?'

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu dpkg Edit question
Assignee:
No assignee Edit question
Solved by:
Vincent023
Solved:
Last query:
Last reply:

This question was originally filed as bug #332972.

Revision history for this message
Dariel Dato-on (odd-rationale) said : 		#1

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We appreciate the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs .

Revision history for this message
Vincent023 (postvak023) said : 		#2

I found the answer:

To correct this problem just open Terminal (Applications → Accessories → Terminal) and type:
sudo dpkg --configure -a

Give your user password when requested. You will not see anything, but type it and press enter.

Then retry to update and/or to install desired package.

Revision history for this message
Vincent023 (postvak023) said : 		#3

Synaptic pakketbeheer werkt nu weer :-)

It works again :-)

Revision history for this message
Tom (tom6) said : 		#4

Brilliant, nicely fixed :)

Thanks for posting the answer in here too. That should help other people with a similar problem in the future

Thanks and regards from
Tom :)