adept signal 11

[SammIam]

Binary package hint: adept

I started Adept, clicked the 'Fetch Updates', and it crashed with a SIGSEGV

(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 -1233869104 (LWP 14048)]
(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 0x08188f0b in ?? ()
#7 0x0818c6fc in ?? ()
#8 0x08076006 in ?? ()
#9 0x080773c4 in ?? ()
#10 0xb6ff2813 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb6ff32b8 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb793d4c9 in KAction::activated () from /usr/lib/libkdeui.so.4
#13 0xb7975cc2 in KAction::slotActivated () from /usr/lib/libkdeui.so.4
#14 0xb7975c5c in KAction::slotButtonClicked () from /usr/lib/libkdeui.so.4
#15 0xb7a43356 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4
#16 0xb6ff2813 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb7972970 in KToolBarButton::buttonClicked () from /usr/lib/libkdeui.so.4
#18 0xb7972c76 in KToolBarButton::mouseReleaseEvent ()
   from /usr/lib/libkdeui.so.4
#19 0xb70295e5 in QWidget::event () from /usr/lib/libqt-mt.so.3
#20 0xb79ee9a1 in KToolBarButton::event () from /usr/lib/libkdeui.so.4
#21 0xb6f899e8 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#22 0xb6f8bba6 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#23 0xb774ece2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#24 0xb6f1c25d in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#25 0xb6f1aec2 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#26 0xb6f18fac in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#27 0xb6f30180 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#28 0xb6fa40be in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#29 0xb6fa3ece in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#30 0xb6f8b591 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#31 0x08073375 in ?? ()
#32 0xb67aaebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#33 0x080730a1 in ?? ()

ProblemType: Bug
Architecture: i386
Date: Fri Mar 30 08:38:08 2007
DistroRelease: Ubuntu 7.04
Uname: Linux sammlinux 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

[Richard Birnie (rbirnie-deactivatedaccount)]

Sammlam,

thanks for reporting this bug. What version of Kubuntu were you using when this occurred? Also, are you able to reproduce this crash consistently? If you are it would be a big help if you could follow the steps here https://wiki.kubuntu.org/Backtrace to generate a more informative backtrace. With all the debugging symbols missing it is hard for the developers to do anything with this.

thanks,
Rich

[platypuss72 (luke-platypuss)]

hi i had the same problem .... and keeep getting it every time i try to update ....

have ran backtrace on the adept and the one from the wiki and attached ..

many thanks luke

[Richard Birnie (rbirnie-deactivatedaccount)]

luke

Thanks for your efforts on debugging this problem. If you can reproduce this bug reliably it would be a big help if you can generate a backtrace with the appropriate debugging symbols installed as described here https://wiki.ubuntu.com/DebuggingProgramCrash

After adding the appropriate repositories if you search for 'adept' in adept manager you will see new packages with names like adept-foo-dbg. If you install those and then generate the backtrace it should replace all those 'no debugging symbols found' messages with useful information. I can't replicate your problem unfortunately or I'd do it myself.

thanks,
Rich

[platypuss72 (luke-platypuss)]

thanks richard :-)

but after i posted that i had a mess about and opened adept manager from system (not the updater) and felched update ok then i had the FULL update button highlighted so i did that and all good have now got updated kernal.... so i will leave it a while now and next time i get an update will try and break it again .... then i will do the surjested help to get all data

many thanks again

LUKE

[platypuss72 (luke-platypuss)]

hi richard ...

have just got an auto update ......

so just ran straight from adept updater and NO problems .....

just worked as it should do .... so may that the full update stuff has fixed it ????

sorry can't crash it again so far ... BUT if i do will post all info

thanks again ... luke

[Richard Birnie (rbirnie-deactivatedaccount)]

Luke,

Thanks for following up on this. It sounds like the bug was a fluke. It happens sometimes, don't worry about it. If it's not reproducable in a controllable way it's difficult to do anything. I'm going to close this report. If it ever happens again it's probably better to start a new thread, it would just be confusing to add to this one.

thanks again
Rich

[platypuss72 (luke-platypuss)]

  http://conradmartens.com/wp-content/plugins/akismet/google235.html