Ubuntu
adept package

Adept Manager crashes with a SIGSEGV after update

Bug #177228 reported by Simon Blakely
20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Adept Manager launches fine. Clicking the Update button is OK - updates are downloaded. When Adept Manager redraws the list boxes, it fails with a Signal 11 (SIGSEGV). This is repeatable. Error also occurs after package install. Crash trace follows

 (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 -1235241280 (LWP 6994)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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 0x08146cb9 in ?? ()
#7 0x0814a5be in ?? ()
#8 0x080724a4 in ?? ()
#9 0x080740d4 in ?? ()
#10 0xb6ea6893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb6ea7338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb77f6389 in KAction::activated () from /usr/lib/libkdeui.so.4
#13 0xb7838bb2 in KAction::slotActivated () from /usr/lib/libkdeui.so.4
#14 0xb7838b4c in KAction::slotButtonClicked () from /usr/lib/libkdeui.so.4
#15 0xb7936a76 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4
#16 0xb6ea6893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb782c320 in KToolBarButton::buttonClicked () from /usr/lib/libkdeui.so.4
#18 0xb782c626 in KToolBarButton::mouseReleaseEvent ()
   from /usr/lib/libkdeui.so.4
#19 0xb6edd681 in QWidget::event () from /usr/lib/libqt-mt.so.3
#20 0xb78a70d1 in KToolBarButton::event () from /usr/lib/libkdeui.so.4
#21 0xb6e3daf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#22 0xb6e3fcae in QApplication::notify () from /usr/lib/libqt-mt.so.3
#23 0xb7603ca2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#24 0xb6dd027d in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#25 0xb6dceee2 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#26 0xb6dccfcc in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#27 0xb6de41a4 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#28 0xb6e581ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#29 0xb6e57fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#30 0xb6e3f699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#31 0x0806f75e in ?? ()
#32 0xb6642050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#33 0x0806f401 in ?? ()

Revision history for this message
Koen (koen-beek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in adept

Revision history for this message
Francisco T. (leviatan1) wrote :

I have the same problem. When I activate or desactivate a repository (always with backports for example), adept updates and then crashes with a similar report:

Crash SIGSEGV 11

Report in attachment.

Revision history for this message
Francisco T. (leviatan1) wrote :
Revision history for this message
Emanuel Goscinski (emu--deactivatedaccount) wrote :

The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Hardy Heron. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at http://www.ubuntu.com/testing/

Revision history for this message
Jonathan Thomas (echidnaman) 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!

P.S. This bug is probably fixed in Adept 3.0 alpha5 or greater, which is set to be included in Intrepid.

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