Bug 166345

Summary:	SIGSEV following updates through Adept updater -- new box in upper left corner of screen running
Product:	[Unmaintained] adept	Reporter:	Penny L. Crook <dewclaw82>
Component:	general	Assignee:	Peter Rockai <me>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	gustyaquino
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Penny L. Crook 2008-07-12 04:40:17 UTC

Version:           adept 2.1 Cruiser (using KDE 3.5.8)
Installed from:    Ubuntu Packages
Compiler:          KDE 3.5.8 on Kubuntu Gutsy Gibbon 
OS:                Linux

This problem appears similar to 156749, but it was not a first-time update.
The Adept Updater showed a number of updates available (I can't recall the exact number but it was in the 20-35 range).  I opened Adept and fetched the list of updates (including the DNS update).  I accepted all of the suggestions for updates and a few new installs.  All updates downloaded and I thought they all installed.  I then saw a small box in the upper left corner of the screen which appeared to be tracking some (new?) portion of the update process.  At that point, Adept crashed.
Here is the 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)
(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 -1235196224 (LWP 7533)]
(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  0x081322c9 in ?? ()
#7  0x08135bce in ?? ()
#8  0x0806f751 in ?? ()
#9  0x08071545 in ?? ()
#10 0xb6eb1893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb6eb2338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb7246907 in QButton::clicked () from /usr/lib/libqt-mt.so.3
#13 0xb6f4ff8c in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
#14 0xb6ee8681 in QWidget::event () from /usr/lib/libqt-mt.so.3
#15 0xb6e48af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#16 0xb6e4acae in QApplication::notify () from /usr/lib/libqt-mt.so.3
#17 0xb760ecd2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#18 0xb6ddb27d in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#19 0xb6dd9ee2 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#20 0xb6dd7fcc in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#21 0xb6def1a4 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#22 0xb6e631ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#23 0xb6e62fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#24 0xb6e4a699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#25 0x0806e7b5 in ?? ()
#26 0xb664d050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#27 0x0806e501 in ?? ()

Thank you.

Comment 1 Peter Rockai 2008-08-03 14:30:27 UTC

*** Bug 159802 has been marked as a duplicate of this bug. ***

Comment 2 Peter Rockai 2008-08-08 14:59:55 UTC

Could you please elaborate what kind of new window that was? The backtrace is useless as well : - (. In best case, you could try to reproduce with Adept 3 alpha 6 to see if it is still a problem (see http://web.mornfall.net/adept.html for instructions).

Comment 3 Penny L. Crook 2008-08-08 18:19:03 UTC

I believe that the little box displays the database update after changes have been through Adept, although it does go by so quickly that I can't even read the title, let alone the particulars.  I've only had this problem one more time, so I have to assume that it was corrected during an update or it was related to something that I had done incorrectly.

Thank you for following up, Peter.  Since I no longer have the problem, I'll mark this as Resolved.