adept-Updater Crashed

Bug #180608 reported by Kirtan
4
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Fix Committed
Medium
Maia Everett

Bug Description

Binary package hint: adept-manager
i was fetching list of Upgrade packages

(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 -1236134208 (LWP 5984)]
(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)
(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 0xb7854f7a in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string () from /usr/lib/libstdc++.so.6
#7 0x08120efc in ?? ()
#8 0x08120ff8 in ?? ()
#9 0x08121a61 in ?? ()
#10 0x08121cf8 in ?? ()
#11 0x0807bd71 in ?? ()
#12 0x0811fbc2 in ?? ()
#13 0x080e9ae1 in ?? ()
#14 0x0810471b in ?? ()
#15 0xb6c2f893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0xb6c30338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb6fbd9b2 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#18 0xb6c575ba in QTimer::event () from /usr/lib/libqt-mt.so.3
#19 0xb6bc6af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#20 0xb6bc891f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#21 0xb72cecd2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#22 0xb6b59209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#23 0xb6bb953b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#24 0xb6b6dd49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#25 0xb6be11ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#26 0xb6be0fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#27 0xb6bc8699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#28 0x08070345 in ?? ()
#29 0xb765b050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#30 0x08070091 in ?? ()

Revision history for this message
Maia Everett (linneris) wrote :

Thanks for the bug report.

Please attach a crash dump.

Changed in adept:
assignee: nobody → sikon
importance: Undecided → Medium
status: New → Incomplete
Kirtan (kirtan007)
description: updated
Revision history for this message
Kirtan (kirtan007) wrote :

how to get crash dump?

Revision history for this message
silasdm (s-dm-wsnet) wrote :

This might be another crash.

Backtrace + coredump...

#0 0xb7eef424 in __kernel_vsyscall ()
#1 0xb6621860 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xb6623228 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0xb68456c8 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6
#4 0xb68435a5 in ?? () from /usr/lib/libstdc++.so.6
#5 0xb68435e2 in std::terminate () from /usr/lib/libstdc++.so.6
#6 0xb684371a in __cxa_throw () from /usr/lib/libstdc++.so.6
#7 0x08106da8 in ?? ()
#8 0x081075f8 in ?? ()
#9 0x0810411d in ?? ()
#10 0x0814626b in ?? ()
#11 0x080994a2 in ?? ()
#12 0x0807110d in ?? ()
#13 0x080746a0 in ?? ()
#14 0xb6df738a in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0xb7156bfe in QSignal::signal () from /usr/lib/libqt-mt.so.3
#16 0xb6e1422d in QSignal::activate () from /usr/lib/libqt-mt.so.3
#17 0xb6e1b5c3 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#18 0xb6d924f5 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#19 0xb6d93536 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#20 0xb74e4b32 in KApplication::notify () from /usr/lib/libkdecore.so.4
#21 0xb6d87d13 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#22 0xb6d3d147 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#23 0xb6daaf00 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#24 0xb6daadc6 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#25 0xb6d92b8f in QApplication::exec () from /usr/lib/libqt-mt.so.3
#26 0x0806ff37 in ?? ()
#27 0xb660c685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#28 0x0806fb91 in ?? ()

Changed in adept:
status: Incomplete → New
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Should be fixed in Adept 3.0.

Changed in adept:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.