Problem with Adept - 'Database Locked'

[ecs_pf5]

I click on 'System' > 'Adept Manager'

> 'Loading Please Wait'

then,

Database Locked - Adept Manager
"""""""""""""""""""""""""""""""""""""""""""
Another process is using the packaging system database (probably some other Adept application or apt-get or aptitude).
Would you like to attempt to resolve this problem? No will enter read-only mode and Cancel to quit and resolve this issue yourself.

I click 'Yes';

Adept Manager - The KDE Crash Handler appears saying:

adept_manager crashed and caused signal 6 (SIGABRT)

the backtrace tab shows all of this:

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47803715209680 (LWP 19286)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5 0x00002b7a2ac0f765 in raise () from /lib/libc.so.6
#6 0x00002b7a2ac111c0 in abort () from /lib/libc.so.6
#7 0x00002b7a2a5097b4 in __gnu_cxx::__verbose_terminate_handler ()
from /usr/lib/libstdc++.so.6
#8 0x00002b7a2a507746 in ?? () from /usr/lib/libstdc++.so.6
#9 0x00002b7a2a507773 in std::terminate () from /usr/lib/libstdc++.so.6
#10 0x00002b7a2a50785a in __cxa_throw () from /usr/lib/libstdc++.so.6
#11 0x00000000004db331 in ?? ()
#12 0x00000000004db9a4 in ?? ()
#13 0x00000000004dbf1d in ?? ()
#14 0x00000000004c7706 in ?? ()
#15 0x0000000000454c6c in ?? ()
#16 0x0000000000435699 in ?? ()
#17 0x0000000000435e57 in ?? ()
#18 0x00002b7a26eedd76 in QObject::activate_signal ()
from /usr/lib/libqt-mt.so.3
#19 0x00002b7a2725be51 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#20 0x00002b7a26f0ceeb in QSignal::activate () from /usr/lib/libqt-mt.so.3
#21 0x00002b7a26f13f1e in QSingleShotTimer::event ()
from /usr/lib/libqt-mt.so.3
#22 0x00002b7a26e892a2 in QApplication::internalNotify ()
from /usr/lib/libqt-mt.so.3
#23 0x00002b7a26e8b031 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#24 0x00002b7a25af9308 in KApplication::notify ()
from /usr/lib/libkdecore.so.4
#25 0x00002b7a26e1bd12 in QApplication::sendEvent ()
from /usr/lib/libqt-mt.so.3
#26 0x00002b7a26e7c55c in QEventLoop::activateTimers ()
from /usr/lib/libqt-mt.so.3
#27 0x00002b7a26e30443 in QEventLoop:rocessEvents ()
from /usr/lib/libqt-mt.so.3
#28 0x00002b7a26ea27e7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#29 0x00002b7a26ea25ef in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#30 0x00002b7a26e8ad68 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#31 0x0000000000431a46 in ?? ()
#32 0x00002b7a2abfbb44 in __libc_start_main () from /lib/libc.so.6
#33 0x0000000000431739 in ?? ()
#34 0x00007fff86e818b8 in ?? ()
#35 0x0000000000000000 in ?? ()

Is there some way I can find and stop the 'Another process' that is 'locking the database'?



This started happening after I used the built-in updater tool to do 164 updates, then was asked if I wanted to upgrade to the newer distribution. It downloaded the 'upgrade tool', the upgrade tool failed (sorry - did not copy down the reason), and now I cannot start anything to do with Adept.. as detailed above.


Any thoughts?

[integr8e]

Re: Problem with Adept - 'Database Locked'

Is there some way I can find and stop the 'Another process' that is 'locking the database'?

There should be; try the following:

sudo dpkg --configure -a

sudo rm /var/lib/dpkg/lock

Adept should open after that

[ecs_pf5]

Re: Problem with Adept - 'Database Locked'

Good Man

It worried over the first two files, said they were present in both my system and also in the package maintainer's archive.. so I asked it to keep my existing version for those.

Then it ran off & did a load of stuff. Completed successfully.

Did your second line.. tried Adept.. yep, all's now well.

Thanks!

[integr8e]

Re: Problem with Adept - 'Database Locked'

Pretty cool!