Adept Manager (SIGABRT)

Bug #194320 reported by P@iN on 2008-02-22
8
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

http://img45.imageshack.us/img45/9601/snapshot1rz0.png

BackTrace details:

(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 -1235912496 (LWP 6085)]
(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 0xb65b2875 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb65b4201 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb67bd6e0 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb67baf65 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb67bafa2 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb67bb0ca 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 0xb6e02893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb718e8ec in QSignal::signal () from /usr/lib/libqt-mt.so.3
#24 0xb6e22842 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#25 0xb6e2a258 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#26 0xb6d99af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#27 0xb6d9b91f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0xb755fcd2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0xb6d2c209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#30 0xb6d8c53b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#31 0xb6d40d49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#32 0xb6db41ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#33 0xb6db3fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#34 0xb6d9b699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#35 0x0806f75e in ?? ()
#36 0xb659e050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#37 0x0806f401 in ?? ()

banquo (kris-carlson) wrote :

I'm getting the exact same problem. Now Adept will do nothing but crash when I run it and try to fix the problem.

Is anyone at Kubuntu working to resolve this problem? My distro is 7.10 AMD64.

banquo (kris-carlson) wrote :

I found this at bugs.kde.org, and it worked for me
Solved for me!

 Ran the commands in this order:
 1. sudo dpkg --configure -a (When asked i selected "n")
 2. sudo apt-get update
 3. sudo apt-get install

 Thanks!

Hello P@iN, could you try the workaround of banquo and tell if it solves your problem?
Thanks in advance.

Changed in update-manager:
status: New → Incomplete
Eric Samray (eric-samray) wrote :

Problem seems to be linked with an availability issue of the server.
So... problem solved

Changed in update-manager:
status: Incomplete → Fix Committed
Changed in update-manager:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers