i dont know what happened but Adept Crashed

Bug #173592 reported by Kirtan
2
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: adept

(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 -1235167552 (LWP 7961)]
[New Thread -1296458864 (LWP 8068)]
(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)
0xb681411b in std::_Rb_tree_increment () from /usr/lib/libstdc++.so.6
#0 0xb681411b in std::_Rb_tree_increment () from /usr/lib/libstdc++.so.6
#1 0x0812d68d in ?? ()
#2 0x0812d8ff in ?? ()
#3 0x0812dbdf in ?? ()
#4 0x080a8262 in ?? ()
#5 0x080cfdcd in aptFront::predicate::remove<aptFront::predicate::Predicate<aptFront::cache::entity::Entity> > ()
#6 0x080bb9e2 in ?? ()
#7 0x080bf4ec in ?? ()
#8 0x080bf764 in ?? ()
#9 0x080d0b00 in ?? ()
#10 0x080cfe37 in aptFront::predicate::remove<aptFront::predicate::Predicate<aptFront::cache::entity::Entity> > ()
#11 0x080d9821 in ?? ()
#12 0x080f7497 in ?? ()
#13 0xb6eb8893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#14 0x080f71d1 in ?? ()
#15 0x080d84ed in ?? ()
#16 0x080f6ea3 in ?? ()
#17 0x080e890a in ?? ()
#18 0x080ee326 in ?? ()
#19 0xb6eb8893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#20 0xb6eb8bed in QObject::activate_signal_bool () from /usr/lib/libqt-mt.so.3
#21 0xb724d8ce in QButton::toggled () from /usr/lib/libqt-mt.so.3
#22 0xb6f55d21 in QButton::nextState () from /usr/lib/libqt-mt.so.3
#23 0xb6f56f76 in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
#24 0xb6eef681 in QWidget::event () from /usr/lib/libqt-mt.so.3
#25 0xb6e4faf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#26 0xb6e51cae in QApplication::notify () from /usr/lib/libqt-mt.so.3
#27 0xb7615ca2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#28 0xb6de227d in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#29 0xb6de0ee2 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#30 0xb6ddefcc in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#31 0xb6df61a4 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#32 0xb6e6a140 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#33 0xb6e51704 in QApplication::processEvents () from /usr/lib/libqt-mt.so.3
#34 0xb6e5172f in QApplication::processEvents () from /usr/lib/libqt-mt.so.3
#35 0x080e124b in ?? ()
#36 0x080b167b in ?? ()
#37 0x080ef3f6 in ?? ()
#38 0xb6eb8893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#39 0xb72448ec in QSignal::signal () from /usr/lib/libqt-mt.so.3
#40 0xb6ed8842 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#41 0xb6ee0258 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#42 0xb6e4faf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#43 0xb6e5191f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#44 0xb7615ca2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#45 0xb6de2209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#46 0xb6e4253b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#47 0xb6df6d49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#48 0xb6e6a1ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#49 0xb6e69fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#50 0xb6e51699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#51 0x0806f75e in ?? ()
#52 0xb6654050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#53 0x0806f401 in ?? ()

Revision history for this message
Nanley Chery (nanoman) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" [WWW] http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems. [WWW] http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

Changed in adept:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in adept:
status: Incomplete → Invalid
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.