adept installer crashed and caused a signal 6

Bug #191298 reported by Adam
2
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

error occurred after giving admin password, and after message saying another application was using the process. When selecting resolve from the dialog box options, this error message was generated.

Revision history for this message
Adam (adamsgubar) wrote :
Download full text (3.5 KiB)

here is the backtrace from crash handler:

(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 -1235798336 (LWP 5694)]
(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 0xb76c1875 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb76c3201 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb78cd6e0 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb78caf65 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb78cafa2 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb78cb0ca 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 0xb6c81893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb700d8ec in QSignal::signal () from /usr/lib/libqt-mt.so.3
#24 0xb6ca1842 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#25 0xb6ca9258 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#26 0xb6c18af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#27 0xb6c1a91f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0xb7320cd2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0xb6bab209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#30 0xb6c0b53b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#31 0xb6bbfd49 in QEventLoop::processEvents () from /usr/lib/libq...

Read more...

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.