Hello
I'm sorry for the delay.
> Are you able to reliably preoeduce the issue and can bisect it to the
> introducing commit?
I faced this issue on real data but I struggled to find a reliable scenario to
reproduce it. Here is what I just came up with:
sudo mkfs -t ext4 -O
I've just faced this issue on the SSD disk as well, so it seems that the
probability is just lower on a speedier disk.
I'm not using the same hardware and was not upgrading to the same firmware but
I was also able to successfully update my laptop eventually.
I'm not sure what was the issue, I noticed that fwupd has been updated recently
as well.
Hello
I'm having the exact same issue on a ThinkPad T480 : running Bullseye, worked
before and no longer since this summer (I assume this might be related to the
bunch of updates that followed BootHole).
Hello
I'm facing the same issue on Debian Bullseye on a permanent installation (not
live-CD).
I've noticed that the same bug has been reported and fixed on Ubuntu, but the
patch has not yet been pulled in Debian:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848892
This issue has been fixed in the Ubuntu package :
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572
Regarding debirf, my workaround for now is to replace busybox by the Ubuntu
package inside the debirf initrd.
rescue/modules/fix-busybox :
#!/bin/bash -e
latest_version=$(curl -fSsL
dpgk-deb also keeps the permissions of the extracted files, so the fix should
be :
-debirf_exec dpkg -i /var/cache/apt/archives/"$KPKG"
+debirf_exec apt-get install -y binutils xz-utils
+debirf_exec ar x /var/cache/apt/archives/"$KPKG" data.tar.xz
+debirf_exec tar -xp --keep-directory-symlink -f
Hello Noah
the problem does not come from Packer, actually AWS allows one to create images
where the root device is either xvda or /dev/xvda. This does not pose any
problem for booting as you did, but it does triggers this error message from
AWS's API even if there is no actual conflicts. The
Package: udisks2
Version: 2.1.5-3
Severity: normal
Dear Maintainer,
I'm interested in letting a normal user mount certain type of LVM snapshot
(basically to allow free access to backups). As indicated by udisks'
documentation, a normal user is only allowed to mount non-system volumes (cf
Hello.
I encountered the exact same issue on Stretch. I just reinstalled my computer
and then just wanted to move my root LVM volume to another one. I really don't
know what I did wrong since it's not the first time I'm doing such things but
well I may have done something bad that messed it
Package: pgloader
Version: 2.3.3~dev3-1.1
Severity: normal
Tags: upstream
Hello,
I discovered that the log_file configuration file option is not enforced,
pgloader always writes to /tmp/pgloader.log regardless of to what it is set.
The command line parameter --logfile is working properly though.
Package: pgloader
Version: 2.3.3~dev3-1.1
Severity: minor
Dear Maintainer,
when playing with the examples provided along the pgloader package, I noticed a
continuous warning :
$ pgloader -T simple
pgloader WARNING path entry '/usr/share/pyshared/pgloader/reformat' does
not exists, ignored
Package: fio
Severity: important
Tags: patch
Hello,
When I launch fio_generate_plots on a system where gnuplot is not installed I
get this error :
$ fio_generate_plots test
Making bw logs
/usr/bin/fio_generate_plots: 42: /usr/bin/fio_generate_plots: -: not found
That's because the test checking
I did a system update which had solved the issue.
Thanks.
Package: general
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
A recent package update.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Typing the PrintScreen no longer
15 matches
Mail list logo
