• Cethin@lemmy.zip
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 days ago

    It should not be breaking the bootloader. I have a question though. Is Windows installed on that device? Windows absolutely will break your bootloader on an update, if it’s installed on the same drive as Windows. No one knows if it’s malice or a bug, but it’s been a thing forever and they haven’t fixed it, so it has to be desired to an extent.

    • Laurel Raven@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day ago

      I think it’s a little of neither on that one… It’s an effect of always assuming it’s the only thing installed on a machine and not actually caring about not stepping on competition to code the updater to look for and respect dual boot configs

      I’m sure they’d look at it like a happy little accident

      • Cethin@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        That’s what I expect too. It’s technically a bug, but it’s also doing something they want, so they don’t care to fix it. If you aren’t running Windows only, you’re a second class citizen to them. If the update happens to fuck up your bootloader, they aren’t concerned. They are aware of the issue, and they could fix it if they wanted to, but they don’t care because it doesn’t bother them.

      • Cethin@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        Weird. I’ve never heard of this being an issue. I can’t really help more without more knowledge of your system. It is abnormal though. I don’t know what you did, but it isn’t something that you would expect to happen.