There is autopkgtest that should have stopped the LLVM update that broke
it from migrating, but there is something up with the triggers.
I checked yesterday and @builddeps@ is on the list so i am not sure
what's up with that exactly.
--
You received this bug notification because you are a member
Okay so this is fixed, I'll look at the other one.
** Changed in: grub2 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086619
Title:
Memtest does not sta
** Patch added: "bpftrace_0.21.2-1ubuntu1.1.diff"
https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2086104/+attachment/5835446/+files/bpftrace_0.21.2-1ubuntu1.1.diff
** Changed in: bpftrace (Ubuntu)
Assignee: (unassigned) => Mate Kukri (mkukri)
** Tags added: fou
Affecting grub2 as well because we should pre-build the eltorito and
ieee1275 ppc cdboot images at grub build time.
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
This is caused by two copies of LLVM being linked into the bpftrace
binary: both the shared libraryand the static ones.
I guess if these are the same version this doesnt cause issues, but a
later LLVM update left the static one s out of date.
The patch is to change the build process to only link
This will be looked at.
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086843
Title:
Grub creates spurious entries in the menu
To manage notifications about this bu
** Changed in: update-notifier (Ubuntu)
Assignee: (unassigned) => Mate Kukri (mkukri)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085951
Title:
/usr/lib/update-notifier/package-d
** Changed in: bpftrace (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/2086104
Title:
bpftrace is broken on Oracular
To manage notifications about this bug g
can you update your grub to 2.12-5ubuntu5.1? i think this might be the
same as https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2084104
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086619
Title:
Hmm looks interesting... Can you post what your grub.cfg looks like?
Also are you sure you made no changes /etc/grub.d?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2086843
Title:
Grub creates spu
Public bug reported:
The aim of this bug is to eliminate the cd-boot-images-* packages from
Ubuntu, and do the same work in debian-cd.
Tasks:
- Change debian-cd to not require cd-boot-images-* anymore.
- Remove cd-boot-images-* from the archive.
(This is also described by Canonical Specifi
** Changed in: bpftrace (Ubuntu)
Importance: Undecided => Critical
** Summary changed:
- Option 'debug-counter' registered more than once
+ bpftrace is broken on Oracular
** Tags added: rls-oo-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
This has nothing to do with GRUB2
** Also affects: pulseaudio-dlna (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: grub2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Changed in: grub2 (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080785
Title:
GRUB menu doesn't show with os-prober entries on BIOS
To manage notificati
*** This bug is a duplicate of bug 2080785 ***
https://bugs.launchpad.net/bugs/2080785
** This bug has been marked a duplicate of bug 2080785
GRUB menu doesn't show with os-prober entries on BIOS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you
@bjmi See comment #13 for how to test a proposed package.
It will also be available as a regular update in Oracular once the SRU
team has approved its migration to oracular-updates.
If you don't want to install the proposed package, you should also be
able to boot Windows from your firmware boot
Dmesg is full of disk i/o errors yeah, I suggest replacing your hard
disk.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085601
Title:
Skype freezes and crashes my laptop package grub-common
2.06
I guess it could be ubuntu|build, but yeah this isnt really needed
unless we wanna patch git-buildpackage
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083051
Title:
nose, git-buildpackage FTBFS
T
I guess it could be ubuntu|build, but yeah this isnt really needed
unless we wanna patch git-buildpackage
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083051
Title:
nose, git-buildpackage FTBFS
T
risc-v grub is built by grub2:src, so setting all others to invalid.
** Changed in: grub2-signed (Ubuntu Noble)
Status: New => Invalid
** Changed in: grub2-unsigned (Ubuntu Noble)
Status: New => Invalid
** Changed in: grub2-unsigned (Ubuntu Oracular)
Status: New => Invalid
Okay so this is actually due to the entire loopback file being measured
and only shows up with the TPM enabled, there was a bugfix posted to
grub-devel, so likely not actually fixed until Ubuntu has shipped that.
** Changed in: grub2 (Ubuntu)
Status: Fix Released => Confirmed
** Summary ch
This is built for risc-v now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076651
Title:
[SRU] Crash on RISC-V in virtual machine using KVM
To manage notifications about this bug go to:
https://b
@ubuntu-sru Verified in a clean Windows 10 + Oracular dual boot VM, but
also see previous verifications on real hw above.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
nspr in noble is a build1 of the Debian package. The only delta between
noble and oracular are the frame pointer changes, this patch is a
backport of the oracular changes as nspr - `2:4.35-1.1ubuntu1~24.04`.
Please see my dev PPA for a test build:
https://launchpad.net/~mkukri/+archive/ubuntu/dev
Pillow runs selftest.py from its source tree as autopkgtest, please see
https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/amd64/p/pillow/20240812_134848_fe1da@/log.gz
This code seems to perform a reasonable set of image manipulations which
should confirm at least some level of functi
** Summary changed:
- [SRU] Please enable frame-pointer on Noble Edit
+ [SRU] Please enable frame-pointer on Noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084460
Title:
[SRU] Please enable f
See my dev PPA for test build here
https://launchpad.net/~mkukri/+archive/ubuntu/dev
** Patch added: "pillow_10.2.0-1ubuntu1.1.diff"
https://bugs.launchpad.net/ubuntu/+source/pillow/+bug/2084457/+attachment/5828058/+files/pillow_10.2.0-1ubuntu1.1.diff
--
You received this bug notification be
Public bug reported:
[ Impact ]
In order to help developers with profiling, Ubuntu enabled frame-
pointers for packages in the main archive.
https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame-
pointers-by-default
The `Affects` packages were missed due to the packaging issues. The
Public bug reported:
[ Impact ]
In order to help developers with profiling, Ubuntu enabled frame-
pointers for packages in the main archive.
https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame-
pointers-by-default
The `Affects` packages were missed due to the packaging issues. The
** Description changed:
[ Impact ]
UEFI GRUB2 in Oracular Oriole enforces NX_COMPAT even when used with a
non-NX shim.
Kernels in Oracular Oriole support NX_COMPAT.
The impact is limited to failing to chainload other non-NX compatible
operating systems from GRUB2.
The mos
Hi Ryan,
Thanks for confirming.
I now believe this affects every UEFI machine dual booting Windows 10
and Ubuntu 24.10:
1. You can boot into Ubuntu from GRUB if you don't unsuccessfully attempt to
boot Windows first
2. Windows will fail to boot from GRUB (as a workaround you can boot it fro
*** This bug is a duplicate of bug 2084104 ***
https://bugs.launchpad.net/bugs/2084104
Hi Andrew,
Thanks for reporting. We are aware (see bug marked as a duplicate source
of this) and the fix will be released as soon as processes allow.
Mate
** This bug has been marked a duplicate of bug 20
** Description changed:
- Please also see final comments on
- https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2078307, this whole
- thing stareted there.
+ [ Impact ]
- There are two known affected machines currently, one is confirmed to
- correctly be running the non-NX shim and 2.12-5ubu
Sorry this is very old, and we do not have the hardware or enough
information to take any meaningful action here.
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you
I've also found a machine I own that reproduces this... Looking into the
root cause currently
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084104
Title:
UEFI GRUB2 enforces NX even with a non-NX s
It looks like something is stopping GRUB from recognizing the MokPolicy
variable exported by shim on these machines, and in turn it decides to
enforce NX despite shim telling it not to.
** Summary changed:
- UEFI GRUB2 enforces NX even with a non-NX shim when Secure Boot is disabled
+ UEFI GRUB2
That sounds even more interesting, can you try set debug=peimage with SB
enabled as well?
The current shim you have installed should be telling GRUB to not
enforce NX, and that was tested to work with SB enabled at least, so I
am bit perplexed what's going on here.
I think the graphics problem is
** Changed in: grub2 (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084104
Title:
UEFI GRUB2 enforces NX even with a non-NX shim when Secure Boot is
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Mate Kukri (mkukri)
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oracular did not change how grub-install registers EFI boot entries.
> grub-install: error: failed to register the EFI boot entry: Invalid
argument.
This is usually caused by the firmware returning an error from the
RT->SetVariable() call.
It would be nice if someone could try to add or delete a
@resonic thank you for reporting this, I think you have found a real
issue with the new NX enablement stack in Oracular.
I have created
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2084104, as I am
pretty confident in my theory, and I'll also try to verify the above
theory tomorrow.
Thank
Public bug reported:
This still needs to be verified, but I have a strong hunch that this is
a bug...
Please see final comments on
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2078307
What is likely happening is that shim does not export MokPolicy when
Secure Boot is disabled, thus GRUB
Hmm that looks extremely weird. It seems like GRUB is deciding to
enforce NX policy on your machine despite it clearly booting from the
shim that is requesting it not to...
One hunch I have is that maybe shim doesn't export MokPolicy with UEFI
Secure Boot disabled, and we accidentally always enfor
Also can you check dpkg -l | grep shim?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is unable to boot Windows using chainloader
To manage notifications about
It looks like it is not the asus bug, as it is pointing to the correct
shim entry.
It still is an NX bug, but a different one then what I've expected.
It seems like your machine somehow ended up with the NX enforcing shim
instead of the non-NX one it should have received.
To confirm this theory
Oh I see you are @Canonical, if this is related to some customer project
or something like that please message me on MM
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084071
Title:
grub-mkconfig mis
Do we ship any Ubuntu system where /boot/dtb is a directory?
I understand that this is annoying if you _need_ that directory for some
reason, but we cannot account for every possible case for everything.
I am not against adding this in the future when we do a new GRUB, but it
doesn't seem very im
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is unable to boot Windows using chainloader
To manage notifications about this bug go to:
https://bugs.launchpad.ne
And p.s. /boot/efi/EFI/BOOT/grubx64.efi is likely left over and not
needed if bootx64 and fbx64 are present in that directory and shimx64
and grubx64 are present in EFI\ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
I suspect Windows fails to boot because the NX compatibility check, and
Ubuntu only fails to boot when you've once unsuccessfully tried booting
Windows without restarting GRUB.
Please get the set debug=peimage output from GRUB as explained above.
And also can you get the output of efibootmgr -v f
GRUB console which you can access with c from the grub screen, then go
back the menu with escape
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078307
Title:
Grub 2.12 in Oracular is unable to boot
Sorry to hear that you are having difficulties with Ubuntu 24.10's
bootloader. Given the testing we are doing, I have strong doubts Ubuntu
24.10 doesn't boot "2 out of 3" on the vast majority of machines, so I
suspect there is something going on with your firmware.
Please run `set debug=peimage` p
> $ cat ~/Downloads/config-6.11.0-8-generic.arm64.txt | grep CONFIG_CMDLINE
> CONFIG_CMDLINE="console=ttyAMA0"
> CONFIG_CMDLINE_FROM_BOOTLOADER=y
This is definitely not the right configuration for Desktop, and probably
questionable for server as well, where a specific server might have a
graphical
For my VM the installed system also needs console=tty0, otherwise it
only asks for the passphrase on the serial port.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083919
Title:
Oracular Oriole ARM
https://iso.qa.ubuntu.com/qatracker/milestones/463/builds/315087/testcases
still has this problem partially.
console=tty0 is applied and the console shows when booting the live
system from the ISO, but the resulting installation still has the exact
same problem, and that's where the passphrase iss
I am not sure if this should be release critical, it seems like Noble
does the same thing on my VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083919
Title:
Oracular Oriole ARM64 ISO + install h
** Summary changed:
- ARM64 ISO + install has boot console showing on serial port only
+ Oracular Oriole ARM64 ISO + install has boot console showing on serial port
only
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Public bug reported:
Boot console only shows on serial port. For encrypted installs this
means it is not possible to enter passphrase and unlock installation
without having access to serial console.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You receiv
That is totally understandable, but if the absolutely stability of these
identifiers isn't possible to guarantee at the kernel level, we will
simply have to use something else to permanently identify bootloader
installation targets.
--
You received this bug notification because you are a member o
> CloudArchitecture: x86_64
> CloudBuildName: server
> CloudID: configdrive
> CloudName: configdrive
> CloudPlatform: configdrive
> CloudSerial: 20220902
> CloudSubPlatform: config-disk (/dev/sda5)
Based on this I suspect that to be the case.
** Changed in: grub2 (Ubuntu)
Status: Invalid =
This could also be caused by cloud_style_installation=true on a system
where it shouldnt be and grub-probe returning nonsense.
OP can you post the output of debconf-show grub-pc?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Patch removed: "efitools_1.9.2-3ubuntu4.diff"
https://bugs.launchpad.net/ubuntu/+source/efitools/+bug/2083030/+attachment/5822588/+files/efitools_1.9.2-3ubuntu4.diff
** Patch added: "efitools_1.9.2-3ubuntu4.diff"
https://bugs.launchpad.net/ubuntu/+source/efitools/+bug/2083030/+attachmen
** Changed in: shim (Ubuntu Oracular)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076227
Title:
shim(-signed) NX support feature freeze exception request
This is caused by the grub-customizer binary
/etc/grub.d/bin/grubcfg_proxy
** Also affects: grub-customizer (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: grub2 (Ubuntu)
** Summary changed:
- package grub-pc 2.12-1ubuntu7 failed to install/upgrade: installed grub-pc
@lathiat yes yes, i am aware of all of these, and this being resolved
"for good" will be among top 25.04 priorities for me, these symlinks are
clearly not stable enough.
Also tagging this as affecting "linux" as well to have it noted that it
is at least sometimes caused by the kernel "pulling the
> "Unfortunately backports of this quirk for random SSD models has been
regularly done to linux -stable kernels upstream."
This problem is worse than that, because GRUB packaging assumes that
these symlinks will stay valid across OS upgrades as well.
Getting rid of the reliance on these links wil
@ubuntu-core-dev please upload
https://code.launchpad.net/~mkukri/ubuntu/+source/cd-boot-images-amd64/+git/cd-boot-images-amd64/+merge/474290
https://code.launchpad.net/~mkukri/ubuntu/+source/cd-boot-images-arm64/+git/cd-boot-images-arm64/+merge/474291
--
You received this bug notification becau
Can you provide more details about your system configuration and the
exact boot problem you are running into?
If what you were describing was the case for all installations being
upgraded to Noble, that would obviously be the most catastrophic
regression we hopefully knew about, so I suspect there
This will also need cd-boot-images rebuilt for the two shim based
architectures as well to have that in sync, so tagging to avoid
forgetting
** Also affects: cd-boot-images-arm64 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cd-boot-images-amd64 (Ubuntu)
Importance: Und
** Also affects: git-buildpackage (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083051
Title:
nose, git-buildpackage FTBFS
To manage notificati
Local build test okay, building here now:
https://launchpad.net/~mkukri/+archive/ubuntu/dev
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083030
Title:
efitools FTBFS
To manage notifications about
git-buildpackage was build tested against that local
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083051
Title:
nose, git-buildpackage FTBFS
To manage notifications about this bug go to:
https://
nose ppa build:
https://launchpad.net/~mkukri/+archive/ubuntu/dev/+build/29120282
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083051
Title:
nose, git-buildpackage FTBFS
To manage notifications a
That looks very weird that checking the disk isn't letting you install
GRUB, it should just let the reinstall work.
if just running grub-install after the package upgrade succeeds, the
thing will likely boot successfully, but it's not great that the
postinst gets stuck in a loop when selecting the
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083176
Title:
grub-efi/install_devices becoming stale due to by-id/nvme-eui
I wanna move to UUID based ESP selection instead of this broken fragile
mess anyways, but figuring out the root cause of the symlinks going away
would be nice anyways.
It seems like udev or the kernel are the possible culprits here.
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
So it looks like the real cause is that the nvme-eui.* symlinks
disappear for some reason.
This will need more time for investigation, but i've seen other issues
with those exact symlinks disappearing, so we need to figure out the
root cause.
** Summary changed:
- grub-efi install device being
Or maybe by the off-chance, have you migrated this installation to a
different disk with a different nvme eui than it originally was on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083176
Title:
Hmm I think I see the problem, install_devices isn't empty, so the migration
must have succeeded, but somehow the symlink
/dev/disk/by-id/nvme-eui.ace42e00256632d42ee4ac01-part1
that should point to your ESP doesn't exist?
Can you verify if
/dev/disk/by-id/nvme-eui.ace42e00256632d42ee4
Can you do a `debconf-show grub-pc` (or it is maybe `debconf-show grub-
efi-amd64`)? It seems like the migration code should have handled this
without prompting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Is it possible that devices originally installed before the multiple-ESP
support was introduced don't have grub-efi/install_devices configured at
all?
This was way before my time, but since that key doesn't exist in Debian
(I think Debian grub only has install_devices for grub-pc and EFI just
goes
Yeah I think that fallback already happens if no install device was
configured for grub-efi. What's likely going on is here there was one
that likely became invalid.
Either way I agree that we should fill install_devices automatically in
postinst, even on staleness, with the ESP mounted at /boot/e
is the windows installation also uefi? (dual booting a bios install of
windows from uefi grub is not possible, grub and windows have to match
for that to work)
what is in /etc/default/grub and /boot/grub/grub.cfg?
did you run update-grub? what was its output?
** Changed in: grub2 (Ubuntu)
This dialog box strictly speaking isn't normal or expected, the
installer initially configure grub_{efi,pc}/install_devices, then this
isn't expected to pop up.
It usually shows up when the originally configured install device became
invalid due to some system configuration change, and strictly sp
The problem is grub_error just doesn't work, because grub_errors dont
stack, so the messages from chainloader.c and linux.c would simply hide
the peimages ones completely instead of the desire to always show them
Perhaps it could be grub_printf instead
--
You received this bug notification becau
This stems from the fact that peimage is suddenly present on non-SB
architectures with a monolithic image in the picture, but cannot tell
whether to enforce NX without shim, so it just does for safety.
What we should is only build peimage into monolithic GRUB on amd64 and
arm64, where it has shim
Does the GRUB menu show if you hold down shift while booting? If that's
the case the no, this is still not a bug as explained above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080785
Title:
GRUB
This place is not a place of honor... no highly esteemed deed is
commemorated here... nothing valued is here.
What is here was dangerous and repulsive to us. This message is a
warning about danger.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
https://launchpadlibrarian.net/749543720/buildlog_ubuntu-oracular-amd64.nose_1.3.7-13_BUILDING.txt.gz
https://launchpadlibrarian.net/749204137/buildlog_ubuntu-oracular-amd64.git-buildpackage_0.9.34_BUILDING.txt.gz
** Affects: nose (Ubuntu)
Importance: Undecided
This should make the thing buildable on amd64 and the arms at least.
Makes the userspace part less horrible, and disables the EFI binaries
that never mattered to us and unbuildable with the current toolchain and
the Makefile combo anyways.
** Patch added: "efitools_1.9.2-3ubuntu4.diff"
https:
** Patch removed: "efitools_1.9.2-3ubuntu4.diff"
https://bugs.launchpad.net/ubuntu/+source/efitools/+bug/2083030/+attachment/5822551/+files/efitools_1.9.2-3ubuntu4.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Patch added: "nose_1.3.7-13ubuntu1.diff"
https://bugs.launchpad.net/ubuntu/+source/nose/+bug/2083051/+attachment/5822558/+files/nose_1.3.7-13ubuntu1.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Patch removed: "nose_1.3.7-13ubuntu1.diff"
https://bugs.launchpad.net/ubuntu/+source/nose/+bug/2083051/+attachment/5822558/+files/nose_1.3.7-13ubuntu1.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Rebuild for gbp, but it's setup.py doesnt like build1 suffix, so im
doing ubuntu1 and adding cludge to workaround that
** Patch added: "git-buildpackage_0.9.34ubuntu1.diff"
https://bugs.launchpad.net/ubuntu/+source/nose/+bug/2083051/+attachment/5822587/+files/git-buildpackage_0.9.34ubuntu1.dif
Pick up Setuptools 72+ compat patch from Debian. Should by synced again
after Oracular.
** Patch added: "nose_1.3.7-13ubuntu1.diff"
https://bugs.launchpad.net/ubuntu/+source/nose/+bug/2083051/+attachment/5822557/+files/nose_1.3.7-13ubuntu1.diff
--
You received this bug notification because y
This is still objectively terrible software, even with this patch
applied, but it compiles and works at least...
** Patch added: "efitools_1.9.2-3ubuntu4.diff"
https://bugs.launchpad.net/ubuntu/+source/efitools/+bug/2083030/+attachment/5822551/+files/efitools_1.9.2-3ubuntu4.diff
--
You rece
Also PPA build
https://launchpad.net/~mkukri/+archive/ubuntu/dev/+build/29120121
And yes the new code to locate efivars is tested, but it's C so no
warranty anyway
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Public bug reported:
https://launchpadlibrarian.net/749168659/buildlog_ubuntu-oracular-
amd64.efitools_1.9.2-3ubuntu3_BUILDING.txt.gz
** Affects: efitools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Wrong bug woops
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960457
Title:
Please remove lupin from the archive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
1 - 100 of 821 matches
Mail list logo
