** Also affects: maas-cert-server
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2105769
Title:
[UBUNTU 24.04] hardwa
I'm attaching complete boot logs (IPMI SoL output) from three boot
attempts. The failed-sb-enabled.txt and failed-sb-disabled.txt logs are
from attempts that failed with Secure Boot enabled and disabled,
respectively, in the firmware settings. (Both are from attempts to
deploy Ubuntu 22.04.) After
The machine in question dates from 2022, according to my records. It's a
Gigabyte R242-P30-JG, which is an ARM64 server. As Stamatis relates, the
problem occurs with Ubuntu 24.04, but not with 22.04 or 20.04, so a full
NVRAM seems like an unlikely cause, unless something in 24.04 is causing
it to t
I'm gdisk's upstream author. I'm pretty busy with other things right
now, so I don't really have the time to invest in implementing floating-
point support in gdisk's inputs. Done poorly, that's the sort of thing
that could create additional bugs. Thus, I don't recommend holding off
on implementing
I've reset this from "Won't Fix" to "Confirmed" because I believe
Filofel's analysis merits another look at the issue.
** Changed in: ubiquity (Ubuntu)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I've tried to reproduce this problem in a VirtualBox VM, with no
succcess. My suspicion is that there's been a regression somewhere (most
likely in GRUB 2 or the Linux kernel) that's causing partial
incompatibility with the older UEFI version used on your motherboard,
Michael. I say "partial incomp
This problem disappeared for me when I upgraded my kernel from
5.15.0-22-generic to 5.15.0-23-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965302
Title:
Text-mode console is unavailable i
Public bug reported:
I recently updated a system from Focal to Jammy pre-release, and I've
found that the text-mode console (obtained by hitting Ctrl+Alt+F1) is
blank. It still seems to accept keyboard input; I can log in "blind" and
enter commands that have effects, but I see nothing on the scree
I've now released GPT fdisk version 1.0.8, which incorporates this bug
fix, as well as a new feature in gdisk and sgdisk that enables
correcting partition names that have already been corrupted by the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I'm the author of GPT fdisk, and I intend to release a version 1.0.8
with this fix within a day or two. The only major change since 1.0.7 is
the MR linked by Christian above. If patching earlier versions of GPT
fdisk, then the following commit should be included, too:
https://sourceforge.net/p/gpt
I can confirm that the PPA described in post #2, above, works on a
MacBook Air 6,2. Please get this fixed prior to Hirsute's final release!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909369
Title:
Public bug reported:
I own a MacBook Air 6,2 on which I've installed several versions of
Ubuntu. I recently updated to the hirsute (21.04) pre-release, but WiFi
has stopped working. Some web searching suggested re-installing the
bcmwl-kernel-source package, which produced the following output:
$
I'm the original bug reporter, and in that context (of MAAS
deployments), this fix does nothing helpful -- it literally does not
change the original observed problem in any way. Thus, I'm marking this
verification-failed-focal. (I've not tested under other Ubuntu
versions.)
** Tags added: verifica
I may have installed it incorrectly, but what I've got is not working.
It boots fine with Secure Boot disabled, but it shuts down with the same
message about a compromised system as the stock GRUB. What I did to
test:
1) Installed grub-efi-amd64-signed (version
1.142.10+2.04-1ubuntu26.8)
2) Cop
I agree with Seth Arnold; assuming that the user won't make a mistake is
a recipe for disaster.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466150
Title:
grub-install breaks when ESP is on raid
@Georg Sauthoff wrote:
> Can you name _one_ UEFI implementation that actually does write to an
ESP?
Offhand, I don't know of an EFI that will write to the ESP
automatically; HOWEVER, there are cases when it can happen because of
user actions and/or EFI applications' operation. For instance:
* Th
*** This bug is a duplicate of bug 1900668 ***
https://bugs.launchpad.net/bugs/1900668
It turns out that "normal" does work, although I could swear it didn't
work earlier. Perhaps I mis-typed the command. In any event, I'm marking
this bug report as a duplicate now.
** This bug has been marke
Ah, I thought the fact that "net_bootps" returned a different error
meant this was a different bug; but if that's a typo, then perhaps not.
Also, typing "normal" (as in comment #5 there) doesn't work. Still, it
does look like it's likely a duplicate.
--
You received this bug notification because
** Attachment added: "Diagnostics at the "grub>" prompt"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1904588/+attachment/5435180/+files/iKVM_capture%20%281%29.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Public bug reported:
On SOME (but not all) boots via MAAS, GRUB hangs at the "grub>" prompt.
This happens about 10% or 20% of the time on affected servers (at least
ostwald and meitner, two Supermicro servers).
The MAAS rackd.log file shows that the node has requested and received
GRUB:
2020-11-
** Changed in: checkbox-support (Ubuntu)
Status: In Progress => 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/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not bein
FWIW, I tried a deployment on an AMD64-architecture server using an
ASRock MT-C224 motherboard (one of the experimental Orange Box v3 nodes
in 18T), and it failed. I can provide additional logs if required. I
have not attempted to install any of the branches associated with this
bug report. (I'm no
As I said, the EFI/foo/grubx64.efi is taken from MAAS. It's presumably
netboot-enabled, but can't seem to find its config file, hence the need
for the manual entry in steps 9-11. Note that I'm not a MAAS developer,
so my understanding of its internals is limited.
--
You received this bug notifica
FWIW, I'm having this problem, too, specifically with the icons files,
as noted in comment #12, on my mirror running on Ubuntu 18.04. Oddly,
some installations using my mirror are fine with this, whereas others
complain. Applying the patch linked in comment #12 fixed it for me.
--
You received th
I've managed to create a procedure that duplicates this problem without
the involvement of MAAS, except for one file pulled from MAAS. The
procedure is awkward, but it reproduces the problem. Here's the
procedure:
1) Ensure that Secure Boot is enabled.
2) Install Ubuntu. (I used 20.04 LTS server.)
Unfortunately, capella in 1SS is not currently accessible by our team.
You can test on jehan in 18T, though; I'm sending you an e-mail with
details.
I don't know what you mean by "remote artifacts" and "local artifacts."
The steps to reproduce the problem is simply to enable Secure Boot and
attemp
This problem still exists in Ubuntu 20.04 Desktop. Selecting either
"primary" or "logical" partition types works fine, but the distinction
is meaningless for GPT, and asking for the partition type could be
confusing to users who aren't expecting it -- they might not understand
the difference or the
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328497/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328508/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328494/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
Unit
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328505/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328500/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/186
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328490/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328503/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "upstart.unity-panel-service.log.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328507/+files/upstart.unity-panel-service.log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328492/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Ti
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328498/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328504/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328496/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328499/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328489/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328509/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
apport information
** Attachment added: "xserver.outputs.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328510/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328491/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Tags added: apport-collected focal third-party-packages ubuntu
** Description changed:
My system has been upgraded through several Ubuntu versions, and I'm now
(15 Feb 2020) on a pre-release version of Ubuntu 20.04 (Focal Fossa).
I've been using Unity on this system s
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328502/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
Un
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328493/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
Unit
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328501/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328495/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1863422/+attachment/5328506/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863422
Title:
Un
Public bug reported:
My system has been upgraded through several Ubuntu versions, and I'm now
(15 Feb 2020) on a pre-release version of Ubuntu 20.04 (Focal Fossa).
I've been using Unity on this system since Ubuntu's installation years
ago, and it's worked fine, including when I first installed the
Public bug reported:
Permissions problem creating file in /tmp. I worked around it by
temporarily removing the sticky bit on /tmp; this enabled the package to
install, but is obviously unacceptable in a release package.
This occurred on upgrading a MythTV frontend box from Eoan to Focal
developme
If this is the same fix that Colin posted earlier and that I tested,
then it's fine; I reported my test results in post #11.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851316
Title:
Failures of
I've tested the PPA in the application that originally prompted my bug
report, and it's working fine. Will this be merged into Ubuntu's version
of lshw before 20.04 is released?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
I managed to check the PPA version just now, and it's working fine.
Thanks for the quick fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848556
Title:
qemu-img check failing on remote image in E
I tried qemu from git, but I get an "unknown protocol" error when I try
to access an image via HTTP:
$ ./qemu-img check http://10.193.37.117/cloud/eoan-server-cloudimg-amd64.img
qemu-img: Could not open
'http://10.193.37.117/cloud/eoan-server-cloudimg-amd64.img': Unknown protocol
'http'
Is ther
Public bug reported:
On a fresh Ubuntu 18.04 server installation, running sosreport creates
root-owned files in ~/.config. Specifically, I'm using the following
command:
sudo sosreport --batch --tmp-dir /tmp/
Prior to running this command, ~/.config did not exist. After running
the command, ~/.c
Public bug reported:
Beginning with Ubuntu 19.10 (Eoan) pre-release versions, the "lshw
-json" output appears to be invalid, and can't be parsed with either
Python's json library or the jq stand-alone command:
$ sudo lshw -json | jq .
parse error: Expected separator between values at line 25, col
I've tested this on three nodes on two MAAS servers (my own home MAAS
server and maastiff, our MAAS server in the certification lab), using
both 18.04 and 19.04. It looks good to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Public bug reported:
The command to delete a container is:
lxc delete {container}/{snapshot}
Unfortunately, if the "/" is omitted, this command deletes {container}
without any sort of prompting. It would be very helpful to add a
prompt/verification when deleting the entire container to avoid mis
*** This bug is a duplicate of bug 1396379 ***
https://bugs.launchpad.net/bugs/1396379
** This bug has been marked a duplicate of bug 1396379
installer uses first EFI system partition found even when directed otherwise
--
You received this bug notification because you are a member of Ubun
This looks to me as if Ubuntu (the kernel, Wayland, and/or the X server,
depending on when the problem occurs) is delivering a video mode that
the display device can't handle. (With VGA, the display should deliver
its capabilities to the computer via EDID, but this doesn't always work
correctly.) T
The easiest workaround seems to be to use the slic3r-prusa package
rather than the slic3r package. This changes the Slic3r version to be
Prusa's fork, which might or might not be your preference; but at least
the slic3r-prusa version's display works as expected. Note that the
binary name changes fr
*** This bug is a duplicate of bug 1437353 ***
https://bugs.launchpad.net/bugs/1437353
** This bug has been marked a duplicate of bug 1437353
UEFI network boot hangs at grub for adapter 82599ES 10-Gigabit SFI/SFP+
--
You received this bug notification because you are a member of Ubuntu
Bu
FWIW, I've run into what I believe to be this bug with MAAS 2.4 and
Bionic, minus the juju aspect -- I'm unable to deploy when nodes must
rely on a proxy for PPA access. It works without PPAs or when I enable
NAT so that the nodes can retrieve the GPG keys without using a proxy.
** Tags added: hwc
Public bug reported:
I don't know; I got an automated error report after updating from Xenial
to Bionic.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: kdevelop-data 4:5.2.1-1ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportV
This may be a duplicate of bug #1437353.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752687
Title:
Quanta D52B-1U unable to PXE-boot in EFI mode
To manage notifications about this bug go to:
htt
** Also affects: checkbox (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
** Changed in: checkbox (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
My bug #1766637, regarding recent MAAS deployments of Bionic, has been
marked a duplicate of this one. The MAAS logs in that bug seem to
indicate that there's a problem accessing /sys/firmware/efi:
Setting up shim (13-0ubuntu2) ...
Setting up libefivar1:amd64 (34-1) ...
Processing triggers for lib
This version did NOT fix the problem for me; VirtualBox is still hanging
the computer with 4.13-series kernels.
$ dpkg -s kbuild | grep Version
Version: 1:0.1.9998svn2814+dfsg-2~ubuntu16.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I've tested kernel 4.13.0-38-generic #43-Ubuntu from artful-proposed and
the problem does not occur with that kernel.
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1754909/+attachment/5075507/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754909
** Attachment added: "Screen shot showing the problem"
https://bugs.launchpad.net/ubuntu/+source/slic3r/+bug/1754909/+attachment/5075508/+files/slic3r.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1754909/+attachment/5075505/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17549
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1754909/+attachment/5075506/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1754909/+attachment/5075504/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754909
Public bug reported:
After upgrading from Ubuntu 16.04 to the latest Bionic build (as of 10
March 2018), I tried launching Slic3r, and it did run; however, the
Plater view shows no boundary for the build plate. I'm attaching a
screen shot to show the problem (with a 20mm test cube loaded). The
pri
Sorry it's taken me so long to get back to you; the affected system is
my main work computer, so I can't just go rebooting it constantly, and
I've been busy with other things.
In any event, I'm afraid I haven't had much luck with these newer
kernels. The bottom line is that to get the VirtualBox m
Andres, the fragments you're seeing in the pcap file look like GRUB code
to me. Keep in mind that's just a raw capture of EVERYTHING that passed
over the MAAS server's local interface for the time during which I was
booting the node, so that includes the GRUB binary that was passed from
the MAAS se
I've perused the tcpdump output. It looks like jehan is requesting TFTP
data (GRUB) from weavile (the MAAS server), and that goes OK; then
there's a LONG string of exchanges like this (copied from the wireshark
summary screen):
6399109.865912 QuantaCo_f2:96:c5 Broadcast ARP
Oh, this was all with Secure Boot disabled, as far as I can tell. (I see
no Secure Boot options in the server's setup screens.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752687
Title:
Quanta D5
Here's a tcpdump capture of a commissioning attempt. I don't know what
you mean by "full console log." The original bug report includes a full
capture of the IPMI SOL console, and there is no "logs" tab in the MAAS
web UI for the node.
** Attachment added: "tcpdump capture of an EFI-mode commissio
Jeff,
The Cisco C-240 M4 (boldore) that originally produced this bug seems to
have been returned to OIL, so I can't test with it, at least not
quickly; however, I did just run a test with feebas, a Cisco C220 M4. I
was able to deploy Ubuntu 16.04 and boot it with Secure Boot enabled,
and verified
The workaround in #36 is now working for me on my home network, too.
Perhaps when I tested it in December (comment #39) I had different
software versions; or maybe I didn't correctly reproduce the changes in
comment #36.
I did a diff on what you posted in #48, Jeff, and it exactly matches
what I'm
I've recently encountered this on an HP ProBook 6470b. This system
doesn't seem to be able to "remember" its BootOrder variable; typing
"sudo efibootmgr" returns results similar to this:
BootCurrent:
Timeout: 0 seconds
No BootOrder is set; firmware will attempt recovery
Boot* ubuntu
Boot0
Mathieu, the workaround of chainloading GRUB rather than shim that you
suggested in comment #36 does not work; see my comment #39.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203
Title:
Deploy
Every other system I've run through this round has shown the same
failure on this test. I suspect it's simply a very high false alarm
rate, as Jeff suggests, so I'm closing this out as "invalid."
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notifica
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1749818/+attachment/5056222/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749818
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1749818/+attachment/5056224/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/174
>From Jeff Lane via e-mail:
> Hi. I can’t see the details right now because I’m on my phone and away from
> my desk. That said,
> that check is very basic, it fails on any call traces.
>
> Stress-ng might trigger some call traces if it triggers the OOM Killer which
> is fine, and
> should be ex
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1749818/+attachment/5056226/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749818
Title:
Ca
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1749818/+attachment/5056223/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1749818/+attachment/5056227/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749818
Ti
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1749818/+attachment/5056225/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749818
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1749818/+attachment/5056217/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749818
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1749818/+attachment/5056220/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749818
Title:
Call
apport information
** Attachment added: "Card0.Codecs.codec.3.txt"
https://bugs.launchpad.net/bugs/1749818/+attachment/5056216/+files/Card0.Codecs.codec.3.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1749818/+attachment/5056218/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17498
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1749818/+attachment/5056221/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17498
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1749818/+attachment/5056215/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749818
Title:
Call T
1 - 100 of 284 matches
Mail list logo
