Thanks a lot yamato, let us know how it goes =)
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869672
Title:
Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load
T
Hi yamato, did you have an opportunity to test the new package, to check
if that fixes the problem for you?
Thanks in advance,
Guilherme
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
List of somewhat duplicate bugs:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/120375
(after comment #74)
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/251164
(propose some alternative solutions we can think about, like failure hooks)
https://bugs.launchpad.net/ubuntu/+source/d
** Patch added: "initramfs-tools patch"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879980/+attachment/5375735/+files/0001-scripts-local-Allow-local-block-looping-as-Debian.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Patch added: "mdadm patch"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879980/+attachment/5375736/+files/0001-script.local-block-Improve-last-resort-mechanism.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Not a debdiff - I found easier to just add the patches as in my local
git repository of the packages.
** Patch added: "cryptroot patch"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879980/+attachment/5375734/+files/0001-d-initramfs-cryptroot-script-Allow-some-retries-on-l.pa
The issue basically is about a failure in mounting root if we have a
stacked setup of LUKS on top of RAID1, when RAID1 is degraded (like a
member missing). What happens in detail is a conjuncture of factors
leading to this problem:
(a) The initramfs script for cryptroot currently is present in two
*** This bug is a duplicate of bug 1573095 ***
https://bugs.launchpad.net/bugs/1573095
Sorry, dup of LP #1573095.
** This bug has been marked a duplicate of bug 1573095
Cloud images fail to boot when a serial port is not available
--
You received this bug notification because you are a m
*** This bug is a duplicate of bug 1573095 ***
https://bugs.launchpad.net/bugs/1573095
Eric, I'll close this LP as dup of #1879987 - seems it's the same issue.
I'll try also the Debian release top see what's different there...we can
comment in the other bug about Debian status and what are the
Sorry for the bad formatting of last comment, I should had the line breaks
fixed before submitting.
I'd like to point another duplicate one which was reported by a colleague: LP
#1879987.
I'll close that one to keep the effort in this single LP.
Cheers,
Guilherme
--
You received this bug not
First, I'd like to thank Scott (for comment #43) and Alejandro (comment #45) -
it seems
there's a bunch of LP bugs orbiting around the same issue: Ubuntu isn't bootable
if we set an invalid serial console on kernel command-line (and have no "quiet"
option there), it seems.
Specially, I'd like to
This was greatly debugged by LP user WGH in https://bugs.launchpad.net
/cloud-images/+bug/1573095/comments/46 - it's really a flaw on
initramfs, I managed to workaround the issue with "quiet" parameter
(system boots normally ,even with the wrong serial console).
Investigation continues... I guess
** Attachment added: "console_issue.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879987/+attachment/5375272/+files/console_issue.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879
I've managed to reproduce in 4.4, 4.15, 5.4 (all from Ubuntu releases)
and 5.7-rc4-next; also, I think bare-metal usually doesn't reproduce.
Seems like a live-lock situation, I'll attach some calltraces I gathered using
sysrqs.
Cheers,
Guilherme
--
You received this bug notification because y
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member
Public bug reported:
Description will be saved for further SRU template, the details of the
issue will be exposed in comments
** Affects: cryptsetup (Ubuntu)
Importance: Medium
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: initramfs-tools (Ubuntu
I've confirmed that, as of focal, the /boot/efi/EFI/ubuntu/ directory no
longer needs to be present in order for the grub-efi-amd64 package to
install the bootloader files. Even /boot/efi/EFI/ does not need to be
there; it will be created. This issue still appears to exist on the
Debian side, howev
Public bug reported:
This concerns grub-efi-amd64 2.04-1ubuntu26 in Ubuntu focal.
Currently, when grub-efi-amd64 (or grub-efi-amd64-signed) is installed
or reconfigured, the following steps occur:
1. Package postinst script runs
2. postinst checks if /boot/grub/x86_64-efi/core.efi is presen
Hi yamato, the kernel with the fix was released to -proposed pocket.
Could you give it a try? The instructions to install a proposed kernel
are available at https://wiki.ubuntu.com/Testing/EnableProposed.
The version in -proposed containing the fix for this issue is 4.15.0-102 .
Thanks in advance,
Public bug reported:
This concerns grub-pc 2.04-1ubuntu26 in Ubuntu focal.
I have the following packages installed. Note that grub-pc has been
removed but not yet purged:
root@xubuntu:/# dpkg -l | grep grub
ii grub-common 2.04-1ubuntu26
amd
*** Bug 1637153 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263505
Title:
Wishlist: add "use input as a search term" to "address not found" page
To
That's why I hedged on having something like "apparmor unload". What
you're saying explains why "restart" and "reload" are distinct actions
(I'd never been clear on this), so having a new action that is "like
'stop' but actually does stop apparmor, even though that is not usually
what you want" mak
A related issue: "/etc/init.d/apparmor stop" should invoke aa-
teardown(8). Depending on the semantics of the apparmor "service," this
could also be "/etc/init.d/apparmor unload" or the like. I was surprised
to find that "apparmor stop" was not actually unloading the profiles, as
I had assumed.
>F
Thanks. I am in complete agreement.
I don't need (or even want) AppArmor to automagically update the kernel
state right after changing something under /etc/apparmor.d/, because
having to do a SIGHUP/restart/etc. is already normal practice. But I do
expect that a reboot/reload will take care of tha
Aaaand the upstream has decided they can't/won't fix this issue.
One thing that bothers me about this whole situation is that, in order
for background services like this one to be cleaned up after logout,
they need to behave "correctly." From my point of view, this is
backwards.
When the system i
Hello John,
I did not take any specific action to unload a profile from the kernel.
Instead, I rebooted the system, under the assumption that this would
wipe the slate clean, with everything reloading cleanly from
/etc/apparmor.d/.
The new profile I developed was under a new filename, because I d
Public bug reported:
This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal.
If I delete a profile from /etc/apparmor.d/, reboot the system, and then
look in /var/cache/apparmor/.0/, I still see a file for the
compiled form of the profile.
The same occurs if the profile is "deleted" by o
Thanks for being on top of this, Sergio. I'm surprised that a LP search
for "boot_id" in this project did not turn up this existing bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872564
Ti
Public bug reported:
This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal.
I have AppArmor actively enforcing policy on my system. In
/var/log/syslog, I see a number of the following two sorts of messages:
May 12 04:44:21 image-ubuntu64 kernel: [ 26.667094] audit: type=1400
audit(1589273061.
This bug was reported three years ago in Debian:
https://bugs.debian.org/863227
** Bug watch added: Debian Bug tracker #863227
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863227
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
SRU just submitted to kernel team mailing-list:
https://lists.ubuntu.com/archives/kernel-team/2020-May/109698.html
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877858
Title:
I
linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassign
Public bug reported:
To be elaborated soon.
** Affects: linux (Ubuntu)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Tags: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1817918
Title:
Hard lockups due to unrestricted lapic timer delay
To manage noti
SRU submitted to kernel mailing-list: https://lists.ubuntu.com/archives
/kernel-team/2020-May/109697.html
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/187
Title:
Bionic ubu
e a ringparam was given an illegal value.
-
- Reproduction steps in AWS:
-
- 1. Create new c5.4xlarge instance with the ubuntu 18.04 official ami (uses
the ENA network driver) and update to latest kernel using apt-get dist-upgrade
and reboot for the new kernel to load.
2. Run ethtool -g ens5
outpu
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linu
Thank you legioner, let's see how Debian maintainers respond to that. Keep us
posted :)
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852747
Title:
mdcheck_start.service trying
I wouldn't expect dpkg to know about the database files, but they should
at least be deleted by a package script (prerm?) when the package is
removed/purged.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
This issue persists in lightdm 1.30.0-0ubuntu3.1 in Ubuntu focal.
I see the warnings not only for pam_kwallet.so, but also its successor
pam_kwallet5.so, as well as pam_gnome_keyring.so (which I do not have
installed). All three of these are referenced in /etc/pam.d/lightdm and
/etc/pam.d/lightdm-
Public bug reported:
This concerns onboard 1.4.1-2ubuntu7 in Ubuntu focal.
Seen during package installation:
[...]
Setting up onboard (1.4.1-2ubuntu7) ...
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning:
'str' object is not callable; perhaps you missed a comma?
ra
Public bug reported:
This concerns lightdm-gtk-greeter-settings 1.2.2-3 in Ubuntu focal.
Seen during package installation:
[...]
Setting up lightdm-gtk-greeter-settings (1.2.2-3) ...
/usr/lib/python3/dist-packages/lightdm_gtk_greeter_settings/helpers.py:281:
SyntaxWarning: "is" with a literal.
Public bug reported:
This concerns command-not-found 20.04.2 in Ubuntu focal.
The apt-get invocation largely tells the story:
# apt-get --purge --autoremove remove command-not-found
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following pack
For me it affects IMAP mail retrieval from imap.aol.com.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876286
Title:
Evolution reports "Error performing TLS handshake: Internal error in
memory al
This bug has LP: 1871726 as a quasi-parent.
Those two processes shown in session-status are deceptive; ps(1) shows a
much larger number of processes still remaining from the login session.
When the two processes go away, however, all the others follow. The
impact of this issue, then, is not limite
This bug has LP: 1871726 as a quasi-parent.
That one system-config-printer process shown in session-status is
deceptive; ps(1) shows a much larger number of processes still remaining
from the login session. When the s-c-p process goes away, however, all
the others follow. The impact of this issue,
Also related: LP: #1877532
It's possible that all the lingering processes are due to a couple of
misbehaving applications.
This isn't a great state of affairs (the cleanup process should not be
so fragile that non-cooperative processes can stop it completely), but
it might explain what's going on
Public bug reported:
This concerns at-spi2-core 2.36.0-2 in Ubuntu focal.
I log into the Xfce desktop as "skunk" via xrdp, and then logout.
A few minutes later, "loginctl list-sessions" shows the following:
SESSION UID USER SEAT TTY
9 0 root
c10 1000 skunk
Related: LP: #1877528
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871726
Title:
"systemd --user" and child processes fail to exit when user logs out
To manage notifications about this bug go to:
Public bug reported:
This concerns system-config-printer 1.5.12-0ubuntu1 in Ubuntu focal.
I log into the Xfce desktop, and then logout. The screen returns to the
LightDM login screen.
A few minutes later, "loginctl list-sessions" shows the following:
SESSION UID USERSEAT TTY
Oliver and Łukasz, thank you for following this up.
So that I understand, in focal, is the fix part of the transitional
package, not in the snap?
The former is described as "This is a transitional dummy package. It can
safely be removed," but would removing it then remove Chromium as an x
-www-br
Public bug reported:
While running software updater I am getting this error "failed to
download repository information Check your internet connection" but my
internet connection is OK. Please help to fix this error
I am using Ubuntu 20.04 LTS
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
Public bug reported:
Clipgrap could not be installed in Ubuntu 20.04 LTS
** Affects: ubuntu-release-upgrader (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.launch
Hi Alexey, thanks for your report! And thanks legioner for your comment and
patch. I think this is indeed a bug, we have systemd services for mdcheck but
the script itself is not in the package.
For Bionic, neither the script or systemd services are present.
Debian came-up with the "checkarray"
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because
** Also affects: linux (Ubuntu Focal)
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/1749961
Title:
xhci_hcd: TRB DMA errors reported with ASMedia ASM1142
Awesome Bryan, thanks for your kind words!!
I'll nominate this bug for Focal then.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749961
Title:
xhci_hcd: TRB DMA errors reported
(In reply to Filip Š from comment #84)
> However, there are some TLDs that aren't present in the Public Suffix List,
> which means that users who want to visit such domains will instead be
> redirected to search. Example of such domains are local/reserved TLDs (like
> `.local` or `.test`) which
(In reply to Filip Š from comment #87)
> Would it be possible to have something like this (additional pref), but only
> for searches that contain (at least one) dot? This would be useful because
> most commonly, searches without dots are not used as domains (except
> `localhost` which is handled
(In reply to Anthony Ramine [:nox] from comment #90)
> My use case is helping family members troubleshot their Internet problems
You can use an autoconfig file with specific prefs set to whitelist
domains. We'll provide a suffixes whitelist in bug 1634650 to simplify
managing that. I'll check also
you can also use browser.fixup.dns_first_for_single_words to force a dns
lookup before searching.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263505
Title:
Wishlist: add "use input as a search ter
Hi John and all, thanks for updating logs and enhancing the report! Due
to a lot of other work, and the nature of this problem (being a FW issue
that we'd try to alleviate using a hack in linux), I wasn't able to work
the tentative hack approach yet.
The issue was "resolved" through a FW update by
Thanks for your advice, I'll try to get the journal next time.
Unfortunately, this bug appearing not so often, and changing my desktop
environment and be awaiting it around a couple of couple weeks is not
very convenient for me. I'd suggest thinking about other ways of testing
than the first two.
@Robie
Thank you for the response. If I were interested in taking on
maintenance of this package, where would you recommend I start? I have
some python experience, but don't understand the inner workings of
Ubuntu (e.g. I wouldn't even know how to install this package after I
download it so I'm
Perhaps I'm too late on this, but powernap is exactly the application
that I'm looking for. I am running a headless Ubuntu home server as a
NAS and web server. The server is typically only being accessed 1-2
hours a day so I would prefer that it go into a lower power state when
not being used. M
It looks like visual bell goes crazy (but I'm not sure in that). And
yes, I love visual bell and usually do enable visual bell instead of
audio bell.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18764
Public bug reported:
I've seen this error on Dell Latitude E7270 (with an internal video
card) as well as Dell Precision 7540 (with NVidia card).
I've seen this error on Ubuntu 18.04 and now on 20.04
I've never reported it yet but I think the time has come.
In a random time (~ once a couple of
Hi yamato, the kernel release schedule is available at:
kernel.ubuntu.com
You can see the next cycle as the last of the 3 "columns", so the kernel
with this patch should get released to -proposed pocket around May 25th
and to the -updates pocket around Jun 8th, subject to delays due to
security is
Thank you yamato, for confirming! So, the patch was sent to kernel team
mailing-list, and will be present in next cycle of kernel release -
unfortunately we've lost the current cycle.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Disco)
Importance: Medium => Low
** Changed in: linux (Ubuntu Disco)
Status: Opinion => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Changed in: linux (Ubuntu Eoan)
Status: Fix Committed => 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/1857922
Title:
hpet lost interrupts on kdump
To manage notifications ab
Clearly a bug to me, deleted content is still gone even when TC is on
(comment 19, option 1). Don't see need for input from UX.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1126858
Title:
[upstream
Hi, A beginner user with almost the same laptop here (SF314-57G, just an extra
graphics card).
I'm encountering the same bug with all ubuntu based distro's. The wierd thing
is it will work just fine right after installation. The sound goes off right
after the first update of the OS and a reboot.
** Also affects: sound-2.6
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/1856366
Title:
PCI/internal sound card not detected on a Swift SF314-57
To manag
Hello,
There is no semicolon in the file but I still have same problem.
Do you want to continue? [Y/n] y
Setting up grub-efi-amd64-signed (1.142+2.04-1ubuntu26) ...
dpkg: error processing package grub-efi-amd64-
Ubuntu 20.04 will install fine on the XPS15 9560. However you will need
to set nouveau.modeset=0 and disconnect any monitor connected to HDMI.
Also after 20.04 is installed, you still cannot boot when a monitor is
connected to HDMI. You will stay at the Ubuntu splash screen with the spinner
spin
I was upgrading from version 18.04 to 20.04 when this bug has appeared.
2020-04-25 11:47:59,154 DEBUG Start checking for obsolete pkgs
2020-04-25 12:37:11,877 DEBUG Finish checking for obsolete pkgs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
SRU submitted this morning [0], unfortunately we're not going to make
this cycle, the fix will need to wait for the next cycle.
Cheers,
Guilherme
[0] https://lists.ubuntu.com/archives/kernel-team/2020-April/109324.html
--
You received this bug notification because you are a member of Ubuntu
I wish i could add some more info regarding this problem. @guiverc
apport-collect 1874194 just says No additional information collected.
If anyone from the Ubuntu team needs more information and can tell me
how to provide them, i am more than happy to provide the needed
information.
--
You recei
** No longer affects: makedumpfile (Ubuntu Bionic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869672
Title:
Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load
To manage notifica
** Description changed:
- Thank you for reading this report.
- This may caused by bugs in kernel, not in kdump. If so, I will report this to
kernel team.
- I need your comment to solve this.
+ [Impact]
+ * Kdump kernel can't be loaded using Linux kernel 4.15.0-65 and newer on
Bionic; kexec fails
** Patch added:
"0001-UBUNTU-SAUCE-x86-purgatory-Fix-Makefile-to-prevent-u.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869672/+attachment/5359499/+files/0001-UBUNTU-SAUCE-x86-purgatory-Fix-Makefile-to-prevent-u.patch
--
You received this bug notification because you are a me
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869672
Title:
Kdump broken since 4.15.0-65 on secureboot - purgatory cannot load
To manage notifications about this bug go to:
http
ogress
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigne
I've noticed that this bug appears only on several instance types such
as t3, r5 but t2 instances are not affected by this bug.
The fresh installation of Ubuntu Server 18.04 LTS (HVM), SSD Volume Type
(64-bit x86) (ami-0d1cd67c26f5fca19) causes error while `apt-get
upgrade` with pc-grub on the t3
Hi yamato, I'm sorry but I found yet another issue that I need to take
care in my fix, hopefully by tomorrow I'll have a new test kernel.
Also, I've noticed that in order to test PPA kernels on secure boot
systems, you'll need to enroll the PPA sign key on shim, to make the
kernel bootable - I'll
Hi yamato, thank you for the great report! I think I found the problem -
can you test my fix proposal? It's just a matter of adding the following
PPA to your system and installing the kernel:
launchpad.net/~gpiccoli/+archive/ubuntu/test1869672
You can run the following commands in order to achiev
Status: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu)
Status: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: makedumpfile (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (
apport-collect 1874194 is not really effective since this problem
happens before ubuntu is even booted up. Like i mentioned ubuntu is
stuck at the splash screen only showing a spinning circle and the ubuntu
logo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Project changed: launchpad => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874194
Title:
Ubuntu 20.04 HDMI connected, no boot
To manage notifications about this bug go to:
https://bugs.
This is the VNC screenshot of a failing boot with seabios 1.10 - it
eventually booted the commission kernel via iPXE. If using 1.13, the
screen is quite similar, but it gets stuck on "Booting from SAN device
0x81".
** Attachment added: "seabios_1.10_maas_ipxe_failure.png"
https://bugs.launchpa
After building Focal OVMF with (verbose) debug enabled, got this log.
** Attachment added: "ovmf-boot-dbg.gz"
https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1873662/+attachment/5356742/+files/ovmf-boot-dbg.gz
--
You received this bug notification because you are a member of Ubuntu
Bu
** Attachment added: "seabios-1.13-blank-failure.log"
https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1873662/+attachment/5356741/+files/seabios-1.13-blank-failure.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
This could well be a MAAS bug (or even iPXE), as I'm not really sure in
which component the flaw is. But given that MAAS+OVMF works, and I've
confirmed both seabios and OVMF are using the same ipxe ROM, I believe
this is a seabios issue.
MAAS PXE message sent to deployed guests is like below:
$ c
** Attachment added: "seabios-1.10-failure.log"
https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1873662/+attachment/5356740/+files/seabios-1.10-failure.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
more
updated versions).
Next steps would be to test PCI-PT NVMe boot and upstream
qemu+seabios+ipxe on Focal, to determine if the issue is present
upstream.
** Affects: seabios (Ubuntu)
Importance: Medium
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Tags
(In reply to Jacob Bundgaard from comment #14)
> I ended up making an extension that tries to detect the language used in each
> input field, then switches the spell checking to the correct language for
> that field:
> https://addons.mozilla.org/da/firefox/addon/automatic-spelling-language/
>
>
Hi yamato, I have good news! Managed to reproduce this in a secure boot
guest (after fighting with the keys hehe). There is an hypothesis of
what's going on: one patch that was merged in -65 changed the way flags
are set on purgatory, a piece of code used on kexec process. If we use
kexec in a secu
This is getting far too confusing because multiple patches for multiple
bugs are being conflated. I produced a fairly straightforward patch that
fixed an issue I directly saw in people's backtraces, and other issues I
identified that are similar. This is what this bug report is for.
The later patc
I'm not sure that this new title is accurate, as the error condition is
brought about specifically by an unusual (albeit legal) way of starting
the X session. My scenario involved xrdp, but I could see this happening
with an older display manager (xdm?) that does not recognize XDG
xsession files.
801 - 900 of 7560 matches
Mail list logo
