Adept Package Manager problems

[RFKirb]

Firstly,

I want thank all those in the community that volunteer their expertise and time to help us linux noobs...
OK here is my problem: I perform a clean install of Kubuntu 7.10 on a partition of my 60GB laptop hard disk. I experience zero problems during installation, and zero problems after first boot. Once OS has fully loaded, I get the update/upgrade icon in the 'system tray.' I click on it, and adept successfully loads. It populates the upgrade/update list with no problems. I initiate the downloads, and it turns out that two of the 30+ files don't completely download ( sorry but I wasn't able to get the names in time). It then goes into the installation process, which errors out after a few minutes. From then on out, I can't start the adept package manager, or any package manager for that matter, even from a cold boot. How do I fix this?

Here's the debug log after that happens:

(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 -1235839296 (LWP 6167)]
(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 0xb65c4875 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb65c6201 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb67d06e0 in __gnu_cxx::__verbose_terminate_handler ()
from /usr/lib/libstdc++.so.6
#10 0xb67cdf65 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb67cdfa2 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb67ce0ca 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 0xb6e14893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb71a08ec in QSignal::signal () from /usr/lib/libqt-mt.so.3
#24 0xb6e34842 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#25 0xb6e3c258 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#26 0xb6dabaf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#27 0xb6dad91f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0xb7571cd2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0xb6d3e209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#30 0xb6d9e53b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#31 0xb6d52d49 in QEventLoop:rocessEvents () from /usr/lib/libqt-mt.so.3
#32 0xb6dc61ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#33 0xb6dc5fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#34 0xb6dad699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#35 0x0806f75e in ?? ()
#36 0xb65b0050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#37 0x0806f401 in ?? ()

[dibl]

Re: Adept Package Manager problems

Sometimes that kind of thing happens when there's some connectivity problem with the repository server/mirror.

To unlock/fix the package manager, just make sure Adept is closed, then in Konsole enter

sudo dpkg --configure -a

then

sudo apt-get update

then

sudo apt-get install

while you're at it, you might as well do

sudo apt-get upgrade

and

sudo apt-get install

and finish with

sudo apt-get autoclean

I think that will put you back in business. If you have a problem starting the KDE desktop (aka the "login loop" problem), there are several posts in the past 2 days that tell you which package needs to be removed. But it may be fixed already.

[RFKirb]

Re: Adept Package Manager problems

thanks for your help!

[monte48lowes]

Re: Adept Package Manager problems

I have had an error more than once similar to this. It involves an update to a qt package. The reason it fails, is that it includes configuration changes that require your input. For some reason Adept does not display this when updating packages. The only way to answer the question is to use the command line.

Simply running 'sudo dpkg --configure -a' will show the question.

Mike