adept-updater crashes when upgrade is done

Bug #129573 reported by Loye Young
6
Affects Status Importance Assigned to Milestone
adept (Ubuntu)
Fix Committed
Undecided
Unassigned

Bug Description

Binary package hint: adept-updater

Feisty
adept 2.1.2ubuntu26.1
adept-notifier 2.1.2ubuntu26.1
adept-updater 2.1.2ubuntu26.1

adept-notifier in systray indicates upgrades are available.
Click on systray icon brings up adept-updater.
Fetch updates.
Upgrade.
Packages download and install.
adept-updater crashes.

Backtrace shows the following:

(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 -1233410352 (LWP 29593)]
(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 0x0817641b in ?? ()
#7 0x08179df7 in ?? ()
#8 0x08073cde in ?? ()
#9 0x08075345 in ?? ()
#10 0xb704f88b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb7050330 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb73e4afb in QButton::clicked () from /usr/lib/libqt-mt.so.3
#13 0xb70edf30 in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
#14 0xb708665d in QWidget::event () from /usr/lib/libqt-mt.so.3
#15 0xb6fe6a60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#16 0xb6fe8c1e in QApplication::notify () from /usr/lib/libqt-mt.so.3
#17 0xb77abce2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#18 0xb6f7925d in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#19 0xb6f77ec2 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#20 0xb6f75fac in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#21 0xb6f8d180 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#22 0xb7001136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#23 0xb7000f46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#24 0xb6fe8609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#25 0x080727d5 in ?? ()
#26 0xb6800ebc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#27 0x08072501 in ?? ()

Happy Trails,

Loye Young
http://www.iycc.biz
Laredo, Texas

Revision history for this message
Michael D. Stemle, Jr. (manchicken) wrote :

It's kinda hard to work with just this information. I cannot replicate this issue. Could you maybe attach your sources.list or anything else that could help explain this? Could you tell me what packages are being updated when this happens?

Marco Maini (maini10)
Changed in adept:
status: New → Incomplete
Revision history for this message
Marco Maini (maini10) 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!

Changed in adept:
status: Incomplete → Invalid
Revision history for this message
saving (savin-gorup) wrote :

I can reproduce this bug on my system with same backtrace.
The bug occurs at the end of update. Updates are successfully installed, so it is just annoyance and not a serious problem.
If you give me any ideas I can help to debug this as it happens every time a package is updated on my system.

Changed in adept:
status: Invalid → Confirmed
Revision history for this message
Davor Cubranic (cubranic) wrote :

It happens to me on Hardy, too. The updates do seem to be successfully installed, but it's not exactly confidence-inspiring experience to see a system update crash.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Doesn't happen with Adept 3 alpha5 from mornfall's ppa. (Which should hit Intrepid soonish, I'd expect. It'll be in Intrepid final; that much I know.)

Changed in adept:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.