Update from Dapper to Edgy results in bug

Bug #73205 reported by Martin
2
Affects Status Importance Assigned to Milestone
update-notifier (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was running Ubuntu 6.06 LTS on an old Compaq 4090US with 512 MB of RAM. I started an unattended update from Dapper to Edgy and let it run. Seems to work OK. I returned to find that it said to report the following as a bug:

Memory status: size: 28286976 vsize: 0 resident: 28286976 share: 0 rss: 10969088 rss_rlim: 0
CPU usage: start_time: 1164347767 rtime: 0 utime: 1033 stime: 0 cutime:659 cstime: 0 timeout: 374 it_real_value: 0 frequency: 2023

Backtrace was generated from '/usr/bin/update-notifier'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb74d6463 in ?? ()
#2 0xb7f84f58 in ?? ()
#3 0xb7f528e6 in ?? ()
#4 0x0000299c in ?? ()
#5 0xbf8a9aa8 in ?? ()
#6 0x00000000 in ?? ()

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Can you please upload the full crash file? It should be in /var/crash.

Thanks,
 Michael

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.