Comment 21 for bug 949992

That's meant to be update-manager -d of course.

On 03/09/2012 01:31 PM, Rick McBride wrote:
> Actually, during the dist-manager -d install, I did get a dialog that
> was all "unknown character" blocks in the message and on the buttons. I
> don't know what it was asking. It didn't appear to block (I never
> answered it, not being able to read it), but it was perhaps that
> message. I HAVE seen it in the past, but not during this testing session.
>
> I had meant to reproduce and document that weird dialog, but got
> distracted by this problem. I'll go back and get more info on that
> either over the weekend or Monday, when I have capacity on my VM host to
> make another pre-update clone and run the process again.
>
> The only dialog that I recall, apart from the typical "remove these
> packages?" type things, was to do with restarting services.
>
>
>
> On 03/09/2012 11:48 AM, Colin Watson wrote:
>> You should run 'sudo dpkg-reconfigure grub-pc' and instruct it to
>> install the boot loader somewhere, probably /dev/vda.
>>
>> The debconf database shows that the following question was presented to
>> you at some point:
>>
>> You chose not to install GRUB to any devices. If you continue, the
>> boot loader may not be properly configured, and when this computer next
>> starts up it will use whatever was previously in the boot sector. If
>> there is an earlier version of GRUB 2 in the boot sector, it may be
>> unable to load modules or handle the current configuration file.
>>
>> If you are already using a different boot loader and want to carry on
>> doing so, or if this is a special environment where you do not need a
>> boot loader, then you should continue anyway. Otherwise, you should
>> install GRUB somewhere.
>>
>> Continue without installing GRUB?
>>
>> Do you remember seeing this question? It was intended to strongly
>> discourage setups like this ...
>>
>