** Branch linked: lp:~yarmouth-team/grub2/trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage notifications abou
This bug was fixed in the package grub2 - 2.02~beta2-9ubuntu1.4
---
grub2 (2.02~beta2-9ubuntu1.4) trusty; urgency=medium
* Fix overlap check in check_blocklists for load_env (backported patch from
upstream commit 1f6af2a9). (LP: #1311247)
-- Mathieu Trudel-Lapierre Wed, 23 S
This bug was fixed in the package grub2-signed - 1.34.5
---
grub2-signed (1.34.5) trusty; urgency=medium
* Rebuild against grub-efi-amd64 2.02~beta2-9ubuntu1.4 (LP: #1311247)
-- Adam Conrad Mon, 05 Oct 2015 04:23:21 -0600
** Changed in: grub2-signed (Ubuntu Trusty)
Statu
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage notifications about this bug g
Removing verification-failed; this has been an ongoing issue, and it
appears to be unrelated to the bugfix here; grub-efi-amd64 reports an
error on a system on which it isn't supposed to be installed (in bug
1507175).
** Tags removed: verification-failed
--
You received this bug notification bec
I successfully tested this patch.
Here is what I did :
- enabled proposed repository
- ran the following command-line (it might not be the same on different
hardware) :
sudo apt-get install grub-pc
On my computer (no UEFI), it upgraded the following packages :
grub-common grub-pc grub-pc-bin grub
** Changed in: grub2-signed (Ubuntu)
Importance: Undecided => High
** Changed in: grub2-signed (Ubuntu Trusty)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
The trusty-proposed update (to ubuntu1.4) fixed the issue on my laptop with
Linux Mint 17.2. Thank you.
@Brian Murray
It uses the standard grub2:
"grub2:
Installed: (none)
Candidate: 2.02~beta2-9ubuntu1.3
Version table:
2.02~beta2-9ubuntu1.3 0"
--
You received this bug notification
@Steppenwolf - What version of grub2 does Mint 17 use? You can check
with apt-cache policy grub2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press
** Branch linked: lp:ubuntu/trusty-proposed/grub2-signed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage notificati
Hello Rkimber, or anyone else affected,
Accepted grub2-signed into trusty-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/grub2-signed/1.34.5 in a few hours,
and then in the -proposed repository.
Please help us by testing this new package. See
https:
Tested on Mint 17, bug fixed. Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage notifications about thi
** Bug watch removed: GNU Savannah Bug Tracker #42466
http://savannah.gnu.org/bugs/?42466
** Tags removed: regression
** Tags added: regression-release
** Description changed:
[Impact]
- Some users with specific partitioning schemes may see a grub error message
interrupting boot:
+
+ Some
** Branch linked: lp:ubuntu/trusty-proposed/grub2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage notifications abo
Hello Rkimber, or anyone else affected,
Accepted grub2 into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-9ubuntu1.4 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
** Description changed:
+ [Impact]
+ Some users with specific partitioning schemes may see a grub error message
interrupting boot:
+
+ "error: malformed file, press any key to continue"
+
+ It appears to be caused by an invalid check for block overlap in grub2,
+ and only applies to very specif
So it seems all this requires is a SRU of the changes in grub2
2.02~beta2-21 to 14.04. I'm starting this now.
** Also affects: grub2 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu Trusty)
Status: New => In Progress
** Changed in: grub2 (Ubuntu Tru
a way that works for me is setting quick_boot to "0" in /etc/grub.d/10_linux
and running update-grub2
this removes the ubuntu specific save_env command via the recordfail function
this then causes the problematic check_blocklist function to not be called.
you can verify that the save_env calls ar
I've come to notice that this solution is only temporary and I still get
this malformed file warnings from time to time.
Ergo there is no solution for this problem till now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I too am affected by this bug.
"If a developer decides it bothers them enough though, they may go ahead and do
the work to backport it..."
This is the kind of thinking that keeps linux irrelevant to the majority of
computer users. Even the distributions that make an effort to cater to the non
t
I still disagree: being greeted with an error message right after
finishing the installation of a new OS isn't exactly the right way to
start, isn't it?
Cosmetic or not, apart from seasoned users who may have seen worse, this
ain't going to make a great impression on newcomers to Ubuntu- if
anythi
There isn't NO chance... non security bugs will be fixed when they are
deemed critical enough. This particular bug isn't a big deal, which is
why nobody has bothered to backport it yet. If a developer decides it
bothers them enough though, they may go ahead and do the work to
backport it, but sin
If LTS regards only security fixes then probably I'm misinformed!
Actually, after your comment Phillip I searched it a bit and looks you
are right!
So this means that there is no chance this bugfix will be backported to 14.04?
We should not wait anymore?
At least it's better to know that there is
You are misinformed cptX. Ubuntu does not have assigned maintainers the
way debian does. Also LTS does not mean every little annoying bug will
be fixed; it means it gets security fixes so your system won't be
vulnerable.
--
You received this bug notification because you are a member of Ubuntu
B
Maybe this specific issue isn't so critical from a system stability
point of view, but regarding what actually LTS (Long Term Support) in
reality means is more than critical!!! It's not acceptable an LTS system
to not include this kind of bug fixes, especially when a bug is
affecting so many people
Not sure I'd consider this a "major" bug. On the 20+ machines I maintain
if that message is simply ignored for 5 to 10 seconds boot completes
with no user action at all. It's cosmetically nasty - in that it gives
the impression that something is actually borked.
--
You received this bug notificat
I totally agree! The problem though is that the assigned maintainer is
probably too busy with other stuff and is not reading this thread any
more! Either another maintainer should take over or we should bumb this
problem to another thread!!
--
You received this bug notification because you are a
That's not the way to do it: it may work, but this is an Ubuntu (major)
bug and should be solved without adding packages from the Debian package
repositories.
Also, it is worth reiterating that an LTS release such as Ubuntu 14.04
has to be fixed, period.
--
You received this bug notification bec
** Branch linked: lp:debian/jessie/grub2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage notifications about this b
And, of course, I mean grub.cfg - not grub.conf!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage notifications abou
Just in case anyone misunderstands the above as displayed here, that
source entry is:
deb http://ftp.uk.debian.org/debian sid main
NOT just the ftp link part!
(or whatever your locale).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
On Mint 17.1 KDE, here. Yes this bug has been bugging me for the last
few days!
I just installed grub2 - 2.02~beta2-21. Only booted up a couple of times
since, but all seems fine.
Get it here: https://packages.debian.org/sid/grub2-common
On AMD64 you'd then go to:
https://packages.debian.org/sid
Please somebody answer us! We are so many people waiting for this bug to
be solved. Look the subscribers list!!! This is major!!!
Why such a serious bug is not going to be backported to 14.04 that is LTS and
should be supported up to 2019?
What is the point to install an LTS if major bugs like th
Seriously, this isn't going to be backported to 14.04 ? Ubuntu 14.04 is
supported until 2019,and this is a major bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: m
But this problem is so significant that it should be solved in all the versions
that are affected!! I don't get it why it should be only available in 15.04 !!
14.04 is a LTS why isn't corrected there as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have no idea how mint works. In Ubuntu it is only in 15.04, which is
still in development so Ubuntu users have to wait for that. My guess is
that you won't see it in Mint until their next release either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
@ Phillip Susi:
Sorry to bother again but if I understood correctly Ubuntu vivid is
15.04 right? This means that the grub2 - 2.02~beta2-21 will not be
available to Ubuntu 14.04?
How can I added to my system (Linux Mint 17, based on Ubuntu 14.04)?
This update is critical for me! I'm waiting for it
As the previous message said, it was fixed in version 2.02~beta2-21
which is sitting comfortably in the Ubuntu vivid repo. Mint is on their
own update schedule so you will have to take it up with them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Hi, does anybody know when will we see this release in the official
Ubuntu repositories? Until now I haven't see it, yet! I'm actually using
Linux Mint which is based on Ubuntu and I cannot see this update as
available, yet
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package grub2 - 2.02~beta2-21
---
grub2 (2.02~beta2-21) unstable; urgency=medium
[ Mathieu Trudel-Lapierre ]
* Fix overlap check in check_blocklists for load_env (backported patch
from upstream commit 1f6af2a9; LP: #1311247).
[ Steve McIntyre ]
** Branch linked: lp:debian/grub2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage notifications about this bug go t
** Changed in: grub2 (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
This Bug affected me but Bertram (bertram-q)'s solution worked for me
to.
I had a fresh installation of Ubuntu 14.04 64Bit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] er
... go on, you know you want to!
Linux, bringing families together since 1991!
:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to con
Solution in comment #79 worked for me, too. Do I have to fear that the
appearance of a new kernel with new grub entries and so forth will screw
this up again? I need a durable solution, I don't want to make cross-
country support visits to my auntie...
--
You received this bug notification becaus
@msth67
#79 used here; no separate /boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage notifications about this
To clarify, which one of the proposed workarounds fixes the issue ?
Does "fixing" in this case mean that no separate /boot partition is
needed ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
The proposed workaround do the trick, but without it the problem still
exist with the latest vivid's grub.
** Tags added: vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv
I've never seen this in Utopic, only in Trusty. Additionally I've found
that if I just wait an additional 5 to 10 seconds when this appears boot
proceeds as expected with no user action required.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is still a problem in Trusty. Can someone tell us whether it's
fixed in Utopic?
The savannah bug report says fixed. What version of grub fixes it? Will
upgrading grub fix the problem in an existing installation, or is
further action required?
(Note: I'm interested in the official fix, in or
Hi.
Adding:
if [ -f /boot/grub/grubenv ] ; then
mv -f /boot/grub/grubenv /boot/grub/grubenv.old
cp /boot/grub/grubenv.old /boot/grub/grubenv
fi
in /etc/rc.local fixes this issue for me - Ubuntu 14.04.x LTS.
H.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
For me the comment #50 was the solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage notifications about this b
Same for me on 14.04
And several of my customers 14.04 installs. Not great that.
I'm already having to workaround the ibus fiasco with UK keyboard selection
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Same Problem here on ubuntu14.04 recently upgraded from 13.10.
The workarounds setting the grub default option is not possible for me, because
I am using the system with vdr.
The vdr sets a wakeup-time which is programmed in the BIOS with nvram.
My mainboard requires a reboot for making this setti
Same problem on Netrunner 14 (kubuntu fork)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage notifications about thi
I have two kubuntu 14.04 installations and it is appearing on both.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage
Same issue on 14.04 Xubuntu. Posting to bookmark while awaiting a
certified fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to contin
I'm waiting so many months for a new version of grub that will have this bug
fixed. It's strange but I installed linux mint in several computers and only in
one I got this problem. I totally reinstalled linux mint in that pc and it
happened again. According to the link http://savannah.gnu.org/bu
Looking at the upstream bug report, this issue was fixed on 2014-06-21.
The fix is relatively small - see
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=1f6af2a9f8b02a71f213b4717d8e62c8a6b14fc5
- could a distro-patch be considered for it?
--
You received this bug notification because you a
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage n
I have also made that change to the /etc/default/grub file and changed
GRUB_DEFAULT=0
to
GRUB_DEFAULT=1
then ran sudo update-grub
So far after several boots the error message has not reappeared.
I realise this is something of a workaround and not a real solution, but
it does appear to work.
We
Here is what I did
Just like Bertram (bertram-q) ..
1) edit the file
/etc/default/grub
replace
GRUB_DEFAULT=0
With
GRUB_DEFAULT=1
2) sudo update-grub
3) Reboot
Issue fixed.
Thanks .
I hope more people are able to use this fix and get over with this annoying bug.
--
You received this bug no
I faced the bug as well, however none of the reported workarounds worked
for me.
After a bit of testing I found out that the error doesn't appear when
booting a boot-entry from the grub-submenu "Advanced options for Ubuntu"
(see attachements), it only appears when selecting the default entry
"Ubun
Received an auto-update for GRUB last week. Applied it hoping it would
have a fix for this issue. It DID NOT.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed
Response to comment #70: Reinstalling the grub packages did not fix the
problem on my system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1311247
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Here's another strange fact:I've also experimented with a Grub live cd
(Super grub 2disk) and a Grub recovery cd made with grub-mkrescue,they
both have troubles finding the partitions on the disk.
There are three in total:
/boot partition
/root partition
/swap partition
all of them are primary.
An other error getting from time to time, way before the starting grub
process, is:
"xz compression data is corrupted" , and need to reboot in that case.
Wonder if a possible relationship can exist between these two errors.
--
You received this bug notification because you are a member of Ubuntu
Follow up to my comment #69 : what is triggering the random "READ ERROR"
message is apparently rebooting the system:cold boot does now (kinda)
work with a separate boot partition and the workaround from comment #53
to hide the error message,however attempting to reboot the system often
triggers thi
Using Linux mint 17 xfce based on ubuntu 14.04
This bug appeared on my system after attempting to fix a suspend session.
Normally screensaver can be unlocked with a password but somehow my system
froze.
Decided to view help
Pressed Ctrl +Alt+ F1
Then type in the username and password
Then typ
Just a clarification,the error message when trying to reinstall Grub in
the first case ("I was able to boot the system but then it was not
possible to reinstall grub from the running system with the usual sudo
grub-install /dev/sdX command.") was:
Embedding is not possible. GRUB can only be instal
I've run into this issue after installing Lubuntu 14.04 32 bit on an old laptop
upgraded with a new 64GB SSD:the disk had first been partitioned with only a
primary root partition (ext4) and swap, the installation process apparently
went normally,then after installing the system I did get this e
As a hint, hoping it helps.
In my case i had the message after GRUB launching.
I could see inconsistancies in my /home partition which is EXT3 formated but at
install i unthoughfully declare EXT4.
As of parameter were showing format EXT4 and another parameter (one like
EXT_TYPE) was showing EXT3
I have just started seeing this problem on a newly installed Xubuntu 32bit
14.04 on a netbook (Atom cpu, 1GBram, Intel integrated gpu).
It coincided with me enabling hibernation by adding the file as shown in
http://ubuntuforums.org/showthread.php?t=2219403, but that may be pure
coincidence as t
I am living with my brute-force workaraound from #53 now.
I first thought it was because of ext4 file system for /boot, but
switching to ext2 did not help.
My partitioning:
1 32.3kB 5363MB 5363MB primary ext2boot
2 5363MB 9656MB 4294MB primary linux-swap(v1)
3
More comments:
latest grub was built on May 8
latest libc6 built on Jun 19
so it should be a good idea to rebuild grub to take care of the latest
libc6. Please devs do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
@ y-kerb
you are right, it has worked for a while, but since a week or so it
warns out again. Wonder if the latest grub change (2.02~beta-2.10) can
be blamed due to some other upgrades (like libc6 or else) ?
" * Simplify override_dh_install a bit. "
--
You received this bug notification becau
Add to #62 comment:
latest libc6 change: " switching us to glibc " instead of previously
used eglibc (2.19~4ubuntu1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: ma
dino99's trick didn't work for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage notifications about this bug go
Adding these lines into /etc/default/grub
#workaround for "malformed file" error
GRUB_SAVEDEFAULT=false
then, update-grub, will remove that error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
So to resume, what we surely know ?
The "malformed file" appear if more than one block is used : so the
question of multiple blocks
The actual grub used (2.02~beta2.10) has not having that issue when kernel
prior to 3.15 is used
That issue appear with ext4 partition
So this seems related to how
You're right: I hadn't noticed, but my 'grubenv' file contains a
"recordfail=1" line. Also, as you state, there is no time-out on the
GRUB menu.
As a further experiment, I removed the "recordfail" lines on the menu
entries that included them, since I assumed that these were the commands
that were
It is this line:
grub-editenv /boot/grub/grubenv unset recordfail
When you boot, the grub loader writes into the grubenv file that the system
start failed.
When the system is started, this flag is removed.
If the flag is not removed, there will be no countdown to select the
default entry on the
Since it looks like the '/boot/grub/grubenv' file is rewritten upon each
boot, and (as #53 indicates) the '/etc/init.d/grub-common' script
appears to be responsible for this action, I decided to turn off the
'executable' flag on this script--i.e. as root:
chmod -x /etc/init.d/grub-common
As a res
collinger, #54 worked to get rid of the original message, but introduced
a new message:
error: diskfilter writes are not supported
This message, unlike the previous one, allows the server to boot 5
seconds later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Also affects: grub via
http://savannah.gnu.org/bugs/?42134
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed
Addition to #53:
A better because less intrusive workaround is here, using upstart:
1. Create file /etc/init/fix-grub.conf:
sudo vi /etc/init/fix-grub.conf
2. With this content:
start on stopped rc
script
grub-editenv /boot/grub/grubenv unset recordfail
grub-editenv /boot/grub/g
Disregarding #52, which seems to be a completely different thing:
I did some testing and found out that the malfornmed file only occurs when
/etc/init.d/grub-common is executed.
I narrowed it down to the line
grub-editenv /boot/grub/grubenv unset recordfail
If I skip execution of /etc/init.d/g
I was still get 'malformed file' on each cold boot.
And i got the idea to check, with gparted, how was set the boot flag as the
system boot on sda:
- boot flag was set on sdb : with the latest grub2 i am getting the
error 'malformed file'. This was not an issue with the previous grub
2.02~beta2-8
Yes, you're right. Since I don't use sudo, I didn't notice that 'sudo cd'
doesn't work. An there was also a typo in the commands.
I tested the recipe on my three Ubuntu boxes and this solved the issue.
Thanks!
RB
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Thanks roland65, but your script doesn't work as it is.
1. make the script
sudo nano /etc/rc.fixgrub
1b. with this content:
#!/bin/sh
/usr/sbin/grub-set-default 0
2. Make the script executable:
sudo chmod +x /etc/rc.fixgrub
3. Create two links to launch the script at shutdown and reboot:
sud
OK, these issues suggested me a workaround for the bug. Here is the
recipe:
1. Create a script named rc.fixgrub in /etc with the following content:
#!/bin/sh
/usr/sbin/grub-set-default 0
2. Make the script executable:
sudo chmod +x /etc/rc.fixgrub
3. Create two links to launch the script at shu
What I said in #47 is also wrong. It seems that the annoying message disappears
at the first reboot after the command grub-set-default 0, but reappears the
next reboot. So this is not a valid solution... Sorry for the trouble!
RB
--
You received this bug notification because you are a member of
Sorry, I'm wrong: the fix is only temporary... The problem comes back
after an update-grub, g! This is strange because the grubenv file is
the same before and after the update-grub...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
#45 fixed the issue for me on Ubuntu 14.04.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311247
Title:
[Grubenv] error: malformed file, press any key to continue
To manage notifications a
I set it using the command
grub-set-default 0
And this set it to
# GRUB Environment Block
saved_entry=0
#
hi coolinger,
i've never used fai. That installation is a fresh Trusty one upgraded to Utopic
via sources.list upgrade. If i remember that issue first appear around trusty
beta time.
My previous change (#42) does nothing: grub is still set to 0, grubenv is set
to x and is rewriten with a bunch
Hey dino99,
the x is just part of an empty string comparison!
"x${GRUB_DEFAULT}" is compared to "x"
If ${GRUB_DEFAULT} is empty, it is "x" = "x"
Also, I think the "#"s from #35 is just padding because the grubenv file
has to keep a specific file size or at least minimum file size.
Since the pr
AS per /etc/grub.d/00_header, line 38
if [ "x${GRUB_DEFAULT}" = "x" ] ; then GRUB_DEFAULT=0 ; fi
so trying with a new grubenv made with:
oem@dev32:~$ sudo su
[sudo] password for oem:
root@dev32:/home/oem# cd /boot/grub
root@dev32:/boot/grub# rm grubenv
root@dev32:/boot/grub# grub-editenv gruben
Seems the same issue has been fixed some times ago:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/913336
but is back again. Wonder why we still have these 2 packages now: the
old & new versions linked together, i mean: grub-common & grub2-common.
--
You received this bug notification beca
1 - 100 of 103 matches
Mail list logo
