Bug 120261 - Adept crashes while fetching updates
Summary: Adept crashes while fetching updates
Status: RESOLVED FIXED
Alias: None
Product: adept
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Rockai
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-16 20:26 UTC by Steve Przybylski
Modified: 2006-01-26 01:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Przybylski 2006-01-16 20:26:40 UTC
Version:           1.88 (using KDE KDE 3.5.0)
Installed from:    Ubuntu Packages
OS:                Linux

Using Adept under Kubuntu Dapper (Flight-2/ppc), on a Powerbook 17" (5,3).  Adept crashes immediately upon clicking the "Fetch Updates" button.  The problem did not occur with the original install of Flight 2, but began after the first time I upgraded using Adept, about a week ago.  I can still run apt-get update from the terminal, have not yet tried upgrading packages with Adept after doing so.  The only non-Kubuntu piece of software I'm using is the bcm43xx wireless driver.

Backtrace:

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".

[KCrash handler]
#3  0x0e44cbc0 in pkgAcquire::Run ()
   from /usr/lib/libapt-pkg-libc6.3-6.so.3.11
#4  0x100b49e4 in operator+ ()
#5  0x1001b760 in std::operator+<char, std::char_traits<char>, std::allocator<char> > ()
#6  0x1001d5c0 in std::operator+<char, std::char_traits<char>, std::allocator<char> > ()
#7  0x0ed9bce0 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#8  0x0ed9cbfc in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#9  0x0f970e38 in KAction::activated () from /usr/lib/libkdeui.so.4
#10 0x0f9afc94 in KAction::slotActivated () from /usr/lib/libkdeui.so.4
#11 0x0f9afc30 in KAction::slotButtonClicked () from /usr/lib/libkdeui.so.4
#12 0x0f9d5c88 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4
#13 0x0ed9bce0 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#14 0x0f9b9b98 in KToolBarButton::buttonClicked () from /usr/lib/libkdeui.so.4
#15 0x0f9b9e0c in KToolBarButton::mouseReleaseEvent ()
   from /usr/lib/libkdeui.so.4
#16 0x0edeb7fc in QWidget::event () from /usr/lib/libqt-mt.so.3
#17 0x0fa1fbe4 in KToolBarButton::event () from /usr/lib/libkdeui.so.4
#18 0x0ed08d0c in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#19 0x0ed0943c in QApplication::notify () from /usr/lib/libqt-mt.so.3
#20 0x0f732cd0 in KApplication::notify () from /usr/lib/libkdecore.so.4
#21 0x0ec70330 in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#22 0x0ec69cc0 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#23 0x0ec67c84 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#24 0x0ec8c2d8 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#25 0x0ed2b148 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#26 0x0ed2af94 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#27 0x0ed06ce4 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#28 0x10016534 in ?? ()
#29 0x0e05c90c in __libc_init_first () from /lib/libc.so.6
#30 0x0e05c90c in __libc_init_first () from /lib/libc.so.6
#31 0x0e05c90c in __libc_init_first () from /lib/libc.so.6
Comment 1 Peter Rockai 2006-01-22 09:52:09 UTC
This is the infamous stack corruption bug -- and i can't seem to be able to reproduce it reliably nor track down the cause. But it is being worked on.
Comment 2 Keith Gregory 2006-01-26 01:05:05 UTC
Version:           1.88 (using KDE KDE 3.5.0) 
Installed from:    Kubuntu Downloaded .iso 
OS:                Linux

As above, Clean install last night with Kubuntu Dapper i386  on a HP (Compaq)
Presario R3000, both packet manager and update wizard crash when fetching updates

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)

[KCrash handler]
#4  0xb6b5e534 in pkgAcquire::Run ()
   from /usr/lib/libapt-pkg-libc6.3-6.so.3.11
#5  0x08106653 in tut::test_object<tut::manager_shar>::test<1> ()
#6  0x080869af in aptFront::exception::Error::~Error ()
#7  0x0808844e in aptFront::exception::Error::~Error ()
#8  0xb715926d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#9  0xb7159d08 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#10 0xb7a3d7b7 in KAction::activated () from /usr/lib/libkdeui.so.4
#11 0xb7a73484 in KAction::slotActivated () from /usr/lib/libkdeui.so.4
#12 0xb7a7342e in KAction::slotButtonClicked () from /usr/lib/libkdeui.so.4
#13 0xb7a8ee20 in KAction::qt_invoke () from /usr/lib/libkdeui.so.4
#14 0xb715926d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0xb7a7a26d in KToolBarButton::buttonClicked () from /usr/lib/libkdeui.so.4
#16 0xb7a7a429 in KToolBarButton::mouseReleaseEvent ()
   from /usr/lib/libkdeui.so.4
#17 0xb7193a11 in QWidget::event () from /usr/lib/libqt-mt.so.3
#18 0xb7ad024f in KToolBarButton::event () from /usr/lib/libkdeui.so.4
#19 0xb70ef65a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#20 0xb70efbda in QApplication::notify () from /usr/lib/libqt-mt.so.3
#21 0xb786e6ad in KApplication::notify () from /usr/lib/libkdecore.so.4
#22 0xb70809d5 in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#23 0xb707c099 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#24 0xb707a584 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#25 0xb7093cc7 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#26 0xb7108153 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#27 0xb7108076 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#28 0xb70ee169 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#29 0x08082ad8 in ?? ()
#30 0xb68dfea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#31 0x08082911 in ?? ()
Comment 3 Peter Rockai 2006-01-26 01:08:48 UTC
Fixed in current svn and in 1.88.1 (by an unfortunate twist of events, the ubuntu version to give this fix will be something like 1.89ubuntu3 and should appear shortly).