Adept Manager crashing while logging in as root

[Guest]

Whenever I attempt to load up Adept Manager or Adapt Installer (Add/Remove Programs) logging in as root, I get a signal 6 (SIGABRT) crash code and the following backtrace:
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1235900736 (LWP 6387)]
(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)
(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 0xb76a8875 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb76aa201 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb78b46e0 in __gnu_cxx::__verbose_terminate_handler ()
from /usr/lib/libstdc++.so.6
#10 0xb78b1f65 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb78b1fa2 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb78b20ca in __cxa_throw () from /usr/lib/libstdc++.so.6
#13 0x0814d9a6 in ?? ()
#14 0x0814df1a in ?? ()
#15 0x0814df78 in ?? ()
#16 0x0814e7c5 in ?? ()
#17 0x0814c2bd in ?? ()
#18 0x08135ef9 in ?? ()
#19 0x0809ad6d in ?? ()
#20 0x0807349f in ?? ()
#21 0x080755d5 in ?? ()
#22 0xb6c68893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb6ff48ec in QSignal::signal () from /usr/lib/libqt-mt.so.3
#24 0xb6c88842 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#25 0xb6c90258 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#26 0xb6bffaf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#27 0xb6c0191f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0xb7307cd2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0xb6b92209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#30 0xb6bf253b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#31 0xb6ba6d49 in QEventLoop:rocessEvents () from /usr/lib/libqt-mt.so.3
#32 0xb6c1a1ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#33 0xb6c19fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#34 0xb6c01699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#35 0x08070345 in ?? ()
#36 0xb7694050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#37 0x08070091 in ?? ()
Whenever I try logging in from another user account, I don't even get this much, it just doesn't load at all. As a relative newbie, I'm not entirely sure the next direction I should be taking. I am running KDE 3.5.8 on Kubuntu Gutsy Gibbon (7.10) on an Acer Aspire 7720-6102. I went to bugs.kde.org and researched existing posts to find that someone had reported the same thing and the administrator referred that user to you guys. Haven't found this fella posting the same issue on this site, so I thought I'd post it myself and see what suggestions you may have.
Let me know if you need more information.

thanx,
Bo Friggstad

[Guest]

Re: Adept Manager crashing while logging in as root

Further probing into my system reveals that this error first occurred when attempting to upgrade to Hardy Heron (apparently I actually tried it once.) The upgrade crashed with the following traceback:

Traceback (most recent call last):
File "/tmp/kde-sandbox/adept_updater8lbDcc.tmp-extract/dist-upgrade.py",
line 60, in <module>
app.run()
File "/tmp/kde-sandbox/adept_updater8lbDcc.tmp-extract/DistUpgradeController.py",
line 1580, in run
self.fullUpgrade()
File "/tmp/kde-sandbox/adept_updater8lbDcc.tmp-extract/DistUpgradeController.py",
line 1458, in fullUpgrade
if not self.prepare():
File "/tmp/kde-sandbox/adept_updater8lbDcc.tmp-extract/DistUpgradeController.py",
line 352, in prepare
self.openCache()
File "/tmp/kde-sandbox/adept_updater8lbDcc.tmp-extract/DistUpgradeController.py",
line 215, in openCache
self._view.getOpCacheProgress())
File "/tmp/kde-sandbox/adept_updater8lbDcc.tmp-extract/DistUpgradeCache.py",
line 51, in __init__
raise CacheExceptionDpkgInterrupted, e
CacheExceptionDpkgInterrupted: E:dpkg was interrupted, you must
manually run 'dpkg --configure -a' to correct the problem.

This has been reported at https://bugs.launchpad.net/ubuntu/+s...er/+bug/241911, so I'm thinking the upgrade attempt failed and has now buggered up my system. Aside from a blowaway, what options do I have?

[dibl]

Re: Adept Manager crashing while logging in as root

you must manually run 'dpkg --configure -a' to correct the problem.

Did you try that yet? In a Konsole enter

sudo dpkg --configure -a

and see if that fixes the package manager.

[cookie77]

Re: Adept Manager crashing while logging in as root

Maybe your Mouse is set 'too sensitive'?
You think you are only clicking once, but, it is 'clicking' too many times......before you lift your finger OFF.
My Keyboard works in similar fashion. (Hold ever so lightly, on any key, and it runs away...with typing that letter.)
Adept Manager/Adept Installer will 'jam up'...as a result.
Had that 'error' myself.
Would check out the Mouse 'operations'...in System Settings. (make adjustments there,too.)