Bug#871229: Acknowledgement (/usr/sbin/update-grub: running update-grub segment faults)

[Thing]

Same thing happens while attempting to upgarde to debian9

On 7 August 2017 at 14:54, Thing  wrote:

> What led up to the situation?
>
> Attempting to convert machine from 32bit to 64bit 
> (https://wiki.debian.org/CrossGrading).
> I found that attempting to make the amd64 kernel the default boot kernel 
> failed.
>
>
>  * What exactly did you do (or not do) that was effective (or
>  ineffective)?
>
> Goolged the segfault message, no joy.
>
>  * What was the outcome of this action?
>
> The boot order in grub does not get updated.
>
>  * What outcome did you expect instead?
>
> That the boot order gets updated.
>
>
> On 7 August 2017 at 14:30, Debian Bug Tracking System <
> ow...@bugs.debian.org> wrote:
>
>> Thank you for filing a new Bug report with Debian.
>>
>> You can follow progress on this Bug here: 871229:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871229.
>>
>> This is an automatically generated reply to let you know your message
>> has been received.
>>
>> Your message is being forwarded to the package maintainers and other
>> interested parties for their attention; they will reply in due course.
>>
>> Your message has been sent to the package maintainer(s):
>>  GRUB Maintainers 
>>
>> If you wish to submit further information on this problem, please
>> send it to 871...@bugs.debian.org.
>>
>> Please do not send mail to ow...@bugs.debian.org unless you wish
>> to report a problem with the Bug-tracking system.
>>
>> --
>> 871229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871229
>> Debian Bug Tracking System
>> Contact ow...@bugs.debian.org with problems
>>
>
>

Bug#871229: Acknowledgement (/usr/sbin/update-grub: running update-grub segment faults)

[Thing]

What led up to the situation?

Attempting to convert machine from 32bit to 64bit
(https://wiki.debian.org/CrossGrading).
I found that attempting to make the amd64 kernel the default boot
kernel failed.


 * What exactly did you do (or not do) that was effective (or
 ineffective)?

Goolged the segfault message, no joy.

 * What was the outcome of this action?

The boot order in grub does not get updated.

 * What outcome did you expect instead?

That the boot order gets updated.


On 7 August 2017 at 14:30, Debian Bug Tracking System  wrote:

> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 871229:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871229.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  GRUB Maintainers 
>
> If you wish to submit further information on this problem, please
> send it to 871...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 871229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871229
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>