Ubuntu
adept package

Adept crash (proboperbly when its copyng files)

Bug #120076 reported by James_Blond
100
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: adept-updater

The new Adept version, and some others updates was nearly completed (the crash came just after the new image? was generated??)
I am using the new kubuntu 7.04

KDE-crash report:

(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 -1233582384 (LWP 5823)]
(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 0x0817641b in ?? ()
#7 0x08179df7 in ?? ()
#8 0x08073cde in ?? ()
#9 0x08075345 in ?? ()
#10 0xb702588b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb7026330 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb73baafb in QButton::clicked () from /usr/lib/libqt-mt.so.3
#13 0xb70c3f30 in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
#14 0xb705c65d in QWidget::event () from /usr/lib/libqt-mt.so.3
#15 0xb6fbca60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#16 0xb6fbec1e in QApplication::notify () from /usr/lib/libqt-mt.so.3
#17 0xb7780ce2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#18 0xb6f4f25d in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#19 0xb6f4dec2 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#20 0xb6f4bfac in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#21 0xb6f63180 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#22 0xb6fd7136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#23 0xb6fd6f46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#24 0xb6fbe609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#25 0x080727d5 in ?? ()
#26 0xb67d6ebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#27 0x08072501 in ?? ()

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

James,

thanks for taking the time to report this bug. Unfortunately the crash report isn't much use with the debugging symbols missing. Is this crash reproducible, i.e. does it always occur if you repeat the same steps. If so it would be a big help if you could install the debugging symbols and generate a new backtrace as described in https://wiki.ubuntu.com/Backtrace and https://wiki.kubuntu.org/DebuggingProgramCrash

thanks for helping to improve kubuntu,
Rich

Changed in adept:
assignee: nobody → rbirnie
status: New → Incomplete
Revision history for this message
bmorency (bmorency) wrote :

I am using kubuntu 7.10. Adept manager crashes for me also near the end when the copying files window pops up. it does not happen every time though. here is my backtrace.

(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)
[Thread debugging using libthread_db enabled]
[New Thread -1235712320 (LWP 6385)]
[KCrash handler]
#6 0x081322c9 in ?? ()
#7 0x08135bce in ?? ()
#8 0x0806f751 in ?? ()
#9 0x08071545 in ?? ()
#10 0xb6e33893 in QObject::activate_signal (this=0x8260828, clist=0x8b21fa8,
    o=0xbfad701c) at kernel/qobject.cpp:2356
#11 0xb6e34338 in QObject::activate_signal (this=0x8260828, signal=4)
    at kernel/qobject.cpp:2325
#12 0xb71c8907 in QButton::clicked (this=0x8260828)
    at .moc/debug-shared-mt/moc_qbutton.cpp:152
#13 0xb6ed1f8c in QButton::mouseReleaseEvent (this=0x8260828, e=0xbfad7490)
    at widgets/qbutton.cpp:836
#14 0xb6e6a681 in QWidget::event (this=0x8260828, e=0xbfad7490)
    at kernel/qwidget.cpp:4702
#15 0xb6dcaaf0 in QApplication::internalNotify (this=0xbfad7a28,
    receiver=0x8260828, e=0xbfad7490) at kernel/qapplication.cpp:2635
#16 0xb6dcccae in QApplication::notify (this=0xbfad7a28, receiver=0x8260828,
    e=0xbfad7490) at kernel/qapplication.cpp:2421
#17 0xb7590ca2 in KApplication::notify (this=0xbfad7a28, receiver=0x8260828,
    event=0xbfad7490)
    at /build/buildd/kdelibs-3.5.8/./kdecore/kapplication.cpp:550
#18 0xb6d5d27d in QApplication::sendSpontaneousEvent (receiver=0x8260828,
    event=0xbfad7490) at kernel/qapplication.h:523
#19 0xb6d5bee2 in QETWidget::translateMouseEvent (this=0x8260828,
    event=0xbfad78e8) at kernel/qapplication_x11.cpp:4304
#20 0xb6d59fcc in QApplication::x11ProcessEvent (this=0xbfad7a28,
    event=0xbfad78e8) at kernel/qapplication_x11.cpp:3481
#21 0xb6d711a4 in QEventLoop::processEvents (this=0x81d8db0, flags=4)
    at kernel/qeventloop_x11.cpp:192
#22 0xb6de51ce in QEventLoop::enterLoop (this=0x81d8db0)
    at kernel/qeventloop.cpp:198
#23 0xb6de4fde in QEventLoop::exec (this=0x81d8db0)
    at kernel/qeventloop.cpp:145
#24 0xb6dcc699 in QApplication::exec (this=0xbfad7a28)
    at kernel/qapplication.cpp:2758
#25 0x0806e7b5 in ?? ()
#26 0xb65cf050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#27 0x0806e501 in ?? ()

Revision history for this message
bmorency (bmorency) wrote :
Download full text (11.4 KiB)

adept_manager has crashed on me again while installing a new package called libupnp2. it crashed at the end after configuration. I am using kubuntu 7.10 with the latest updates. i'm not sure what other debugging symbols to install, I have kdelibs-dbg,kdeaddons-dbg, kdebase-dbg, kdenetwork-dbg and kdeutils-dbg installed. Here is my back trace.

(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)
[Thread debugging using libthread_db enabled]
[New Thread -1235847488 (LWP 7188)]
[New Thread -1284928624 (LWP 7262)]
[New Thread -1258529904 (LWP 7260)]
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb683a17b in ?? () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb68adb2e in ?? () from /usr/lib/libX11.so.6
#3 0x00000003 in ?? ()
#4 0x081c6ed0 in ?? ()
#5 0x00002618 in ?? ()
#6 0xb710e116 in ~QGListIterator (this=0x81c5c48) at tools/qglist.cpp:1145
#7 0xb68ad67f in _X11TransWrite () from /usr/lib/libX11.so.6
#8 0xb68a54d7 in ?? () from /usr/lib/libX11.so.6
#9 0x081c5c48 in ?? ()
#10 0x081c6ed0 in ?? ()
#11 0x00002618 in ?? ()
#12 0xb6da9af0 in QApplication::internalNotify (this=0x81c67f8,
    receiver=0xb72da8d0, e=0xbfdc8bb8) at kernel/qapplication.cpp:2635
#13 0xb68a600a in _XEventsQueued () from /usr/lib/libX11.so.6
#14 0xb6894dc2 in XPending () from /usr/lib/libX11.so.6
#15 0xb6d501e4 in QEventLoop::processEvents (this=0x81f3e20, flags=0)
    at kernel/qeventloop_x11.cpp:147
#16 0xb6dc4140 in QEventLoop::processEvents (this=0x81f3e20, flags=0,
    maxTime=3000) at kernel/qeventloop.cpp:258
#17 0xb6dab704 in QApplication::processEvents (this=0xbfdcc3a8, maxtime=3000)
    at kernel/qapplication.cpp:2693
#18 0xb6dab72f in QApplication::processEvents (this=0xbfdcc3a8)
    at kernel/qapplication.cpp:2677
#19 0x080e124b in ?? ()
#20 0x0810f5c5 in ?? ()
#21 0x08123475 in ?? ()
#22 0xb6e12893 in QObject::activate_signal (this=0x85479a8, clist=0xb4563b80,
    o=0xbfdc9688) at kernel/qobject.cpp:2356
#23 0xb719e8ec in QSignal::signal (this=0x85479a8, t0=@0x85479d0)
    at .moc/debug-shared-mt/moc_qsignal.cpp:100
#24 0xb6e32842 in QSignal::activate (this=0x85479a8) at kernel/qsignal.cpp:212
#25 0xb6e3a258 in QSingleShotTimer::event (this=0x8547980)
    at kernel/qtimer.cpp:286
#26 0xb6da9af0 in QApplication::internalNotify (this=0xbfdcc3a8,
    receiver=0x8547980, e=0xbfdc99d8) at kernel/qapplication.cpp:2635
#27 0xb6dab91f in QApplication::notify (this=0xbfdcc3a8, receiver=0x8547980,
    e=0xbfdc99d8) at kernel/qapplication.cpp:2358
#28 0xb756fca2 in KApplication::notify (this=0xbfdcc3a8, receiver=0x8547980,
    event=0xbfdc99d8)
    at /build/buildd/kdelibs-3.5.8/./kdecore/kapplication.cpp:550
#29 0xb6d3c209 in QApplication::sendEvent (receiver=0x8547980,
    event=0xbfdc99d8) at ../include/qapplication.h:520
#30 0xb6d9c53b in QEventLoop::activateTimers (this=0x81f3e20)
    at kernel/qeventloop_unix.cpp:556
#31 0xb6d50d49 in QEventLoop::processEvents (this=0x81f3e20, flags=0)
    at kernel/qeventloop_x11.cpp:389
#32 0xb6dc4140 in QEventLoop::proc...

Richard Birnie (rbirnie-deactivatedaccount)
Changed in adept:
assignee: rbirnie → nobody
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

This should be fixed in Adept 3, the new version for KDE4. It is not offically released yet, but is on its way into intrepid and likely hardy-backports. Marking "In Progress" until it is actually available in official repositories.

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

Fixed in adept3.0~beta1 in Intrepid.

Changed in adept:
status: In Progress → Fix Released
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.