"Another process is using the packaging system database..." = crash

[Karl]

When I try to use Adept Manager, I get this message:

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.

Then, when I click "yes" it crashes. And when I do the traceback it does this:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/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 -1235802432 (LWP 5604)]
(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)
[KCrash handler]
#6 0xffffe410 in __kernel_vsyscall ()
#7 0xb65cd875 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb65cf201 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb67d96e0 in __gnu_cxx::__verbose_terminate_handler ()
from /usr/lib/libstdc++.so.6
#10 0xb67d6f65 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb67d6fa2 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb67d70ca in __cxa_throw () from /usr/lib/libstdc++.so.6
#13 0x0812b916 in ?? ()
#14 0x0812be8a in ?? ()
#15 0x0812bee8 in ?? ()
#16 0x0812c735 in ?? ()
#17 0x0812a22d in ?? ()
#18 0x08114379 in ?? ()
#19 0x080951ed in ?? ()
#20 0x0807378d in ?? ()
#21 0x0807408e in ?? ()
#22 0xb6e1d893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb71a98ec in QSignal::signal () from /usr/lib/libqt-mt.so.3
#24 0xb6e3d842 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#25 0xb6e45258 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#26 0xb6db4af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#27 0xb6db691f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0xb757aca2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0xb6d47209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#30 0xb6da753b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#31 0xb6d5bd49 in QEventLoop:rocessEvents () from /usr/lib/libqt-mt.so.3
#32 0xb6dcf1ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#33 0xb6dcefde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#34 0xb6db6699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#35 0x0806f75e in ?? ()
#36 0xb65b9050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#37 0x0806f401 in ?? ()

I have no idea what this means. But it is really annoying. Before I would just keep installing and reinstalling the OS until I could grab firefox and gimp BEFORE it started doing this all the time. But now I'm thinking that's really lame and I don't want to destroy my harddrive. I mean, there should be a way to fix it.

So, what is going on? >__<

Thanks!

[Snowhog]

Re: &quot;Another process is using the packaging system database...&quot; = crash

To fix Adept errors:
Open a console and type:

sudo dpkg --configure -a

should fix it, else continue with

sudo apt-get clean

sudo apt-get update

sudo apt-get install

This should resolve the problem.

[Karl]

Re: &quot;Another process is using the packaging system database...&quot; = crash

How do I open the console? Is that just the ALT+F2 thing?

PS. It randomly started working again, so it's no biggie. Thanks!!!

[Snowhog]

Re: &quot;Another process is using the packaging system database...&quot; = crash

How do I open the console? Is that just the ALT+F2 thing?

K Menu | System | Konsole

[eggbanjo]

Re: &quot;Another process is using the packaging system database...&quot; = crash

Probably find its Adept updater,

If it happens again just go into ksysguard and kill adept-notifier process

[blackjack72]

Re: &quot;Another process is using the packaging system database...&quot; = crash

This is the same problem I had. Add/Remove now works (mostly), but when I enter the above set of commands I get the message:

E:could not get lock /var/lib/dpkg/lock- open (11 Resource temporarily unavailable)

E: Unable to lock the administration directory (var/lib/dpkg/) is another process using it?

[Snowhog]

Re: &quot;Another process is using the packaging system database...&quot; = crash

If you leave Adept Manager running when/if you issue these command from the command line, that would explain it. Only one instance of Adept can be running. So, when you have this problem with Adept Manager, close the program and then open a console and type the commands.

[blackjack72]

Re: &quot;Another process is using the packaging system database...&quot; = crash

I thought of that, but this message happens right after I reboot.