Ubuntu
adept package

adept crash

Bug #121861 reported by Yuriy Padlyak
4
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: adept-manager

(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)
[Thread debugging using libthread_db enabled]
[New Thread -1233635632 (LWP 6798)]
(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 0x0818ab0b in ?? ()
#7 0x0818e4e7 in ?? ()
#8 0x0807647a in ?? ()
#9 0x08077c9e in ?? ()
#10 0xb701888b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb769ff0e in KProcess::processExited () from /usr/lib/libkdecore.so.4
#12 0xb76a013f in KProcess::processHasExited () from /usr/lib/libkdecore.so.4
#13 0xb769ac8f in KProcessController::slotDoHousekeeping ()
   from /usr/lib/libkdecore.so.4
#14 0xb769adb2 in KProcessController::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#15 0xb701888b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0xb70191a2 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb73a5877 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#18 0xb703b44a in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#19 0xb6fafa60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#20 0xb6fb188f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#21 0xb7774c32 in KApplication::notify () from /usr/lib/libkdecore.so.4
#22 0xb6f421e9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#23 0xb6fa1e59 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#24 0xb6f56d07 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#25 0xb6fca136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#26 0xb6fc9f46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#27 0xb6fb1609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#28 0x0807375e in ?? ()
#29 0xb67c9ebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#30 0x08073471 in ?? ()

Revision history for this message
Vincent Legout (vlegout) wrote :

Thanks for taking the time to report this bug. 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" 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. 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!

Vincent Legout (vlegout)
Changed in adept:
status: New → Incomplete
Revision history for this message
Vincent Legout (vlegout) 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:
importance: Undecided → Medium
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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