cd /tmp also helps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673438
Title:
update-grub: cannot restore the original directory
To manage notifications about this bug go to:
I can reproduce it with `grub-efi 2.04-1ubuntu26.7`
$ apt-cache policy grub-efi
grub-efi:
Installed: 2.04-1ubuntu26.7
Candidate: 2.04-1ubuntu26.7
Version table:
*** 2.04-1ubuntu26.7 500
500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
100
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673438
Title:
A nicer error message would be nice. Or use /tmp for tempfiles instead
of current working directory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673438
Title:
update-grub: cannot restore the
@Yozen, thanks for adding that comment that was exactly what was
happening to me, as I was receiving the same described failure message.
I was attempting to run sudo update-grub from my nfs mounted home at
work. I cd'd into /tmp and re-ran the command and it completed without
any issues.
--
You
Not sure if this is your problem Martin, but this could happen if you
are updating grub-pc, or running update-grub, as a user with a
Kerberized NFS home directory. If you are anywhere in the home
directory, and use sudo to run those commands, then you will get errors
like the above (if local root
That sounds like you were running update-grub from a directory that had
been removed. Try making sure that the directory exists first (e.g. run
'cd $PWD', which will fail in much the same kind of way if that isn't
the case).
The package you probably have installed is 'grub-pc'. grub2 is a
