Since this bug originally showed itself when installing 'gdm', I thought the best way to test it now would be to revert to the previous version of gdm and then let the update-manager install the current version again. But I don't have the previous version of 'gdm', and I don't see it in the package pool at archive.ubuntu.com either.
So instead I reverted to an old version of the kernel and let the update-notifier reinstall the current version. I left the embedded terminal window hidden while the kernel package installed, and when it got to the question about whether to install a boot block using /etc/lilo.conf the embedded terminal was opened up, showing the question. I was working in a different window at the time, so I didn't see the question for quite a long time. I could quite easily have missed it.
Since this bug originally showed itself when installing 'gdm', I thought the best way to test it now would be to revert to the previous version of gdm and then let the update-manager install the current version again. But I don't have the previous version of 'gdm', and I don't see it in the package pool at archive.ubuntu.com either.
So instead I reverted to an old version of the kernel and let the update-notifier reinstall the current version. I left the embedded terminal window hidden while the kernel package installed, and when it got to the question about whether to install a boot block using /etc/lilo.conf the embedded terminal was opened up, showing the question. I was working in a different window at the time, so I didn't see the question for quite a long time. I could quite easily have missed it.
When I came to writing this response, I wanted to copy/paste the question from the embedded terminal, but couldn't, so I raised a new bug ( https:/ /launchpad. net/distros/ ubuntu/ +source/ update- notifier/ +bug/31396 ) about that.
I think the question needs to be brought to the front so the user can see it and answer it before this bug can be considered fixed.