Update notifier crashed on dapper->edgy upgrade

Thanks for your bugreport.

Is this crash reproducable? What did you do before it crashed?

Thanks,
 Michael

it was right after edgy had been updated from dapper.. and it was doing extra updates, and i recieved a message that it crash, and that file was saved on my desktop. after a few minutes of waiting.. the update manager restore itself.

After the upgrade there should have been a "Please reboot" message. Did the crash happend before you rebootet or after?

Thanks,
 Michael

I saw this as well during my most recent upgrade, which was:

The following NEW packages will be installed:
  x11proto-print-dev
The following packages will be upgraded:
  bsh console-setup deskbar-applet dpkg dpkg-dev dselect
  edgy-community-wallpapers epiphany-browser firefox firefox-dbg
  firefox-gnome-support gaim gaim-data gaim-dbg gnome-screensaver gthumb
  initramfs-tools irssi irssi-text libdb4.4 libgd2-xpm libgd2-xpm-dev
  libmono-cairo1.0-cil libmono-corlib1.0-cil libmono-data-tds1.0-cil
  libmono-peapi1.0-cil libmono-relaxng1.0-cil libmono-security1.0-cil
  libmono-sharpzip0.84-cil libmono-sqlite1.0-cil libmono-system-data1.0-cil
  libmono-system-runtime1.0-cil libmono-system-web1.0-cil
  libmono-system1.0-cil libmono0 libmono1.0-cil libnautilus-extension1
  libnspr-dev libnspr4 libnss-dev libnss3 libxp-dev libxp6
  linux-restricted-modules-2.6.17-10-generic linux-restricted-modules-common
  mono-common mono-gac mono-jit mono-mcs mono-runtime mono-utils nautilus
  nautilus-data nvidia-kernel-common python-central python-glade2
  python-gobject python-gtk2 rhythmbox startup-tasks system-services upstart
  upstart-compat-sysv upstart-logd xchat-gnome xchat-gnome-common

The only new notification I see is the one from firefox.

Hi,

I'm here to repport the same bug.

I did an Dapper installation, and I used this method to upgrade my system because the live cd couldn't do an functionnal installation..

gksu “update-manager -c -d”

Before:
I was a NEW install of Dapper
I didn't install any package exepted the linux-image-generic for my processor Sempron because I't wasn't by default.... (The "genric" kernel appear to be better than K7)
I did an update too (sudo apt-get update && sudo apt-get upgrade) without any unofficial and Edgy repository.

It was a new installation.

Hardware configuration:

Asus a7n8x
sempron 2200
1Go RAM
ATI x800pro

---------------------------------------------------------------
Error message :

Memory status: size: 30101504 vsize: 0 resident: 30101504 share: 0 rss: 12488704 rss_rlim: 0
CPU usage: start_time: 1161468722 rtime: 0 utime: 343 stime: 0 cutime:205 cstime: 0 timeout: 138 it_real_value: 0 frequency: 210

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 0xb7449463 in ?? ()
#2 0xb7ef7f58 in ?? ()
#3 0xb7ec58e6 in ?? ()
#4 0x0000657f in ?? ()
#5 0xbf91ae18 in ?? ()
#6 0x00000000 in ?? ()

I experienced that same "update-notifier" crash, with the same error log during upgrade from Dapper to Edgy. This error occured before "Please reboot" message.

We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

On Tue, Dec 30, 2008 at 09:18:33PM -0000, Martin Mai wrote:
> We were wondering if this is still an issue for you. Can you try with
> the latest Ubuntu release? Thanks in advance.
>
> ** Changed in: update-notifier (Ubuntu)
> Status: Confirmed => Incomplete

I haven't seen this in subsequent upgrades, but this bug hasn't yet been
analyzed, so it's hard to say whether anything has been fixed. The original
problem was confirmed by others, so it seems to have been a valid bug.

In order to diagnose the problem, we would need debug symbols from the
Dapper version of update-notifier, which may not be feasible to get at this
time.

--
 - mdz

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!

Thank you for taking the time to report this bug and helping to make Ubuntu better. My apologies as I should not have marked this Invalid. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

[Expired for update-notifier (Ubuntu) because there has been no activity for 60 days.]