Ubuntu
adept package

apt_updater crash

Bug #179877 reported by Yuriy Padlyak on 2008-01-02

This bug report is a duplicate of: Bug #162450: adept installer crash. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	adept (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: adept-updater

(no debugging symbols found)
Using host libthread_db library "/lib/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 47357981211088 (LWP 12190)]
(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]
#5 0x00000000004e1906 in ?? ()
#6 0x00000000004e3baf in ?? ()
#7 0x0000000000431547 in ?? ()
#8 0x000000000043316a in ?? ()
#9 0x00002b125f1dcd76 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#10 0x00002b125f1dd910 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#11 0x00002b125f55318f in QButton::clicked () from /usr/lib/libqt-mt.so.3
#12 0x00002b125f2779c3 in QButton::mouseReleaseEvent ()
   from /usr/lib/libqt-mt.so.3
#13 0x00002b125f2114c4 in QWidget::event () from /usr/lib/libqt-mt.so.3
#14 0x00002b125f1782a2 in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#15 0x00002b125f17a400 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#16 0x00002b125de00248 in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#17 0x00002b125f10ad84 in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#18 0x00002b125f10998e in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#19 0x00002b125f107b5a in QApplication::x11ProcessEvent ()
   from /usr/lib/libqt-mt.so.3
#20 0x00002b125f11e43e in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#21 0x00002b125f1917e7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#22 0x00002b125f1915ef in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#23 0x00002b125f179d68 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#24 0x00000000004307bc in ?? ()
#25 0x00002b1262eeab44 in __libc_start_main () from /lib/libc.so.6
#26 0x0000000000430549 in ?? ()
#27 0x00007fff4eb93468 in ?? ()
#28 0x0000000000000000 in ?? ()

Revision history for this message

Iulian Udrea (iulian) wrote on 2008-01-02:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #162450 , so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.