All the patches is in Groovy-5.8. Nothing to fix.
** Changed in: linux (Ubuntu Groovy)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876707
Title:
NULL pointer
Ubuntu 14.04 reached end of standard support in April 2019:
https://wiki.ubuntu.com/Releases
If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.
If you would like to continue with Ubuntu 14.04 then there is a
Public bug reported:
Xenial Package: linux-image-generic (4.4.0.186.192)
Since Xenial Kernel upgrade to version linux: 4.4.0-186.216, there is a
problem with the NFS mounts, when the NFS Server has a timeout.
The journal and syslog are reporting thousands of the following messages per
second
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742089
Title:
Third unkown screen
To manage notifications about this bug go to:
https://lkml.org/lkml/2020/7/31/28
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889446
Title:
DELL LATITUDE 5491 touchscreen doesn't work
To manage notifications about this bug go to:
Sorry I still can't see what the issue is/was from that link.
Worth noting that @3v1n0 continues to fix bugs in that patch with every
update, including in 3.36.4-0ubuntu0.20.04.1 which is in focal-proposed.
But if you don't need a fix anymore and don't need to discuss it further
then this bug
Verified 7906-0ubuntu4~18.04.2 from bionic-proposed against following kernels:
* 4.15.0-1093-oem
* 4.15.0-112-generic
* 4.18.0-25-generic
* 5.0.0-1065-oem-osp1
* 5.0.0-53-generic
* 5.3.0-62-generic
* 5.4.0-42-generic
** Tags removed: verification-needed verification-needed-bionic
** Tags added:
Hello Robert, or anyone else affected,
Accepted grub2 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu3.27 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883012
Title:
CPU stuck for 22s
To manage notifications about this bug go to:
Hello Robert, or anyone else affected,
Accepted grub2 into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.17
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
An upload of grub2 to xenial-proposed has been rejected from the upload
queue for the following reason: "cruft in debdiff".
** Description changed:
[SRU Justification]
SRU regression triggered by latent misconfiguration of grub on the host
system, leading to a failure to boot due to ABI
An upload of grub2 to bionic-proposed has been rejected from the upload
queue for the following reason: "noise in debdiff, will repload".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
** Description changed:
- [Justification]
+ [SRU Justification]
SRU regression triggered by latent misconfiguration of grub on the host
system, leading to a failure to boot due to ABI mismatch between
/boot/grub/i386-pc which is updated, and the grub image in the MBR which is not
+ [Test
[Expired for kde-runtime (Ubuntu) because there has been no activity for
60 days.]
** Changed in: kde-runtime (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am having the same issue
** Attachment added: "terminal_logs_ubuntu20-04.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1877878/+attachment/5397305/+files/terminal_logs_ubuntu20-04.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (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/1877878
We (System76) were able to replicate the issue on most of our NVIDIA
laptops in NVIDIA mode, with the exception of the addw1. We've therefore
repackaged mutter in Pop without the patch, so it's no longer a problem
for us.
You can find screenshots of the problem in this issue:
This took down one of my Digital Ocean droplets running Debian 10 (because I
was an idiot and said "yes" to continue when grub reported a failure).
But I was able to fix it similar to Bernd by booting the DO recovery ISO (that
runs Ubuntu), mount my root disk at /mnt, chroot, and then run:
> How do I tell whether my grub is ok (without rebooting)?
I too would like to know this. I have a linode server with OS on
/dev/sda, that grub-install doesn't like:
root@radish-linode:~# grub-install /dev/sda
Installing for i386-pc platform.
grub-install: warning: File system `ext2' doesn't
** Also affects: oem-priority/focal
Importance: Undecided
Status: New
** No longer affects: oem-priority/focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/134
Title:
[MIR]
For the first time, I also encountered the same issue. I'm in Ubuntu
20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776030
Title:
Backup fails with "an unknown error"
To manage notifications
I executed the apport-collect 1889114 command as instructed. It appears
that a number of txt files were uploaded.
However, the instructions also said to change the status to "Confirmed".
I was not able to change the status. The "status" info pulldown seems
to indicate that the "reporter" can
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889704
Title:
package grub-efi-amd64-signed 1.66.26+2.02~beta2-36ubuntu3.26 failed
to install/upgrade:
How do I tell whether my grub is ok (without rebooting)?
My machine still hasn't rebooted since the grub2 upgrade, and I'm too
afraid to do so now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
??
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: grub-efi-amd64-signed 1.66.26+2.02~beta2-36ubuntu3.26
ProcVersionSignature: Ubuntu 4.4.0-186.216-lowlatency 4.4.228
Uname: Linux 4.4.0-186-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: amd64
Please attach a screenshot/photo of the problem and also run this
command to collect more system information:
apport-collect 1889686
** Tags added: focal xrandr-scaling
** Tags added: nvidia
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug
Here is the log relevant to this bug.
** Attachment added: "prevboot-1.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1889541/+attachment/5397285/+files/prevboot-1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1768543 ***
https://bugs.launchpad.net/bugs/1768543
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1768543, so it is being marked as such. Please
Please attach a photo (or video) of the problem, because I am not sure
what the "purple screen" is that you refer to.
Please also run this command to collect more system information
apport-collect 1889541
** Tags added: focal
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Also, it appears you've at least partially disabled some graphics
drivers with this kernel parameter:
nomodeset
If you don't know the reason for that then please remove it from
/etc/default/grub and then run:
sudo update-grub
and reboot.
After rebooting please run:
dmesg > dmesg1.txt
Thanks. Please also run this command:
gsettings list-recursively org.gnome.shell > settings.txt
and then attach the resulting text file here.
** Tags added: amdgpu
** Summary changed:
- app blinking
+ [amdgpu] app blinking
--
You received this bug notification because you are a member of
Thanks. It looks like Xorg is the cause of this problem and Wayland
(used on the login screen) works better. Please try selecting 'Ubuntu on
Wayland' on the login screen (button at the bottom right) before
entering your password and tell us if that improves the situation.
** Summary changed:
-
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889114
Title:
Ubuntu 18.04 Update Breaks KVM Wireless Mouse
To manage
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1889114/+attachment/5397279/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1889114/+attachment/5397283/+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/1889114
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1889114/+attachment/5397284/+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/1889114
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1889114/+attachment/5397282/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889114
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1889114/+attachment/5397275/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1889114/+attachment/5397278/+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/1889114
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1889114/+attachment/5397281/+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/1889114
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1889114/+attachment/5397277/+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/1889114
Title:
apport information
** Tags added: apport-collected
** Description changed:
I installed Ubuntu 18.04 updates on July 21st. This was a relatively
small update with kernel related files from what I remember when
installing the update. Since the update, my KVM connected Logitech G305
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1889114/+attachment/5397276/+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/1889114
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1889114/+attachment/5397274/+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/1889114
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1889114/+attachment/5397280/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In the past "ice-lake-flicker" issues have been related to the audio
system(!). That was supposedly fixed in bug 1875254, but your log shows
some errors in the same area:
[ 117.852074] sof-audio-pci :00:1f.3: error: no reply expected, received
0x0
[ 117.944970] sof-audio-pci :00:1f.3:
Roman,
Please run the following commands on the affected machine:
lspci -k > lspcik.txt
journalctl -b0 > journal.txt
and then attach the resulting text files here.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: mesa (Ubuntu)
Status:
** Changed in: linux-oem (Ubuntu Focal)
Status: Confirmed => Invalid
** No longer affects: linux-oem (Ubuntu Focal)
** Changed in: linux (Ubuntu Focal)
Importance: Critical => High
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Triaged
** Changed in: linux-oem
This bug was fixed in the package zthreads - 2.3.2-10
---
zthreads (2.3.2-10) unstable; urgency=medium
* QA upload.
* Upload to unstable.
* debian/libzthread-2.3-2.symbols: removed. It was breaking the construction
on other architectures and there's a recommendation of not
** Description changed:
- The bellow upstream commit fixes a bug in Ktls feature.
- It is applied cleanly above the ubuntu-focal tree and passed basic sanity
testing.
- We would like it to be backported ubuntu-focal
- Thanks,
- Amir
+ [IMPACT]
- commit
Hello Robert, or anyone else affected,
Accepted grub2 into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.04-1ubuntu26.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I can confirm the same, 0.9.22 on Ubuntu 20.04 had a game-stopping fault
at startup that was solved by upgrading to 0.9.24 with no regressions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873944
Patches refreshed for update-notifier 3.192.30, as published in Ubuntu
20.04 (focal).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246364
Title:
regression: update-notifier stopped showing a tray
** Patch added: "restore_reboot.patch"
https://bugs.launchpad.net/update-notifier/+bug/1246364/+attachment/5397271/+files/restore_reboot.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246364
** Patch removed: "restore_icon.patch"
https://bugs.launchpad.net/update-notifier/+bug/1246364/+attachment/5038130/+files/restore_icon.patch
** Patch removed: "restore_reboot.patch"
https://bugs.launchpad.net/update-notifier/+bug/1246364/+attachment/5038131/+files/restore_reboot.patch
**
Hello,
I installed the proposed smart-notifier (0.28-6~ubuntu20.04.1) package.
It worked for me when I ran "/usr/bin/smart-notifier --notify <<< 'hi
there'"
Thanks!
Jason
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Justification]
+ SRU regression triggered by latent misconfiguration of grub on the host
system, leading to a failure to boot due to ABI mismatch between
/boot/grub/i386-pc which is updated, and the grub image in the MBR which is not
+
+
Failure to install new
** Merge proposal linked:
https://code.launchpad.net/~fmarier/ubuntu/+source/apparmor/+git/apparmor/+merge/388439
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889699
Title:
Brave is not
I fixed it locally by changing the following files in /etc:
diff --git a/apparmor.d/abstractions/ubuntu-browsers
b/apparmor.d/abstractions/ubuntu-browsers
index 0d67682..22f151d 100644
--- a/apparmor.d/abstractions/ubuntu-browsers
+++ b/apparmor.d/abstractions/ubuntu-browsers
@@ -40,3 +40,4 @@
Public bug reported:
The Brave browser is not included in /etc/apparmor.d/abstractions
/ubuntu-browsers and /etc/apparmor.d/abstractions/ubuntu-helpers which
means that when it's set as a default browser by a user, profiles like
/etc/apparmor.d/usr.bin.evince break.
In this case, it means that
Will those changes be merged into the 20.04.1 release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870736
Title:
[nvidia] Screen scaling 125% gives 200%
To manage notifications about this bug
** Description changed:
[Impact]
On the LENOVO AMD renoir machines, there is a digital mic directly
connected to the APU instead of the codec, so there are two separate
sound cards in the system, one is for analogue codec driven by hda
driver, the other is for the dmic driven by ASoC
none
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551599
Title:
Remove button missing after package installation
To manage notifications about this bug go to:
none
** Changed in: hundredpapercuts
Assignee: (unassigned) => Lawrence Young (lorenzojoven)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551599
Title:
Remove button missing after package
I didn't quite have Dan's patience, but FWIW my system successfully
rebooted 25/25 times with the systemd package (237-3ubuntu10.42) from
bionic-proposed in combination with libseccomp2:amd64
(2.4.3-1ubuntu3.18.04.3) installed and syscall filtering enabled in
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/388437
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
grub-install failure does not
Also affects my desktop Ubuntu 18.04.4 LTS. Took me ages because the original
desktop boot disk for bionic just gave a blank monitor but here is a fix:
I downloaded the boot/repair iso
(https://sourceforge.net/projects/boot-repair-cd/) and created a bootable USB
disk with the startup disk
This bug was fixed in the package budgie-desktop-environment - 0.14.0
---
budgie-desktop-environment (0.14.0) groovy; urgency=medium
* Enforce asking when deleting and moving to trash so that
inadvertent deleting files is not possible
* Remove shutdown/logout/restart/suspend
Digging into it further just installing python-pyqt5-dbg causes the
upgrade to fail to calculate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887544
Title:
can not upgrade from 18.04 to 20.04
** Description changed:
After updating grub2 (to 2.02~beta2-36ubuntu3.26) and rebooting, my
server does not boot:
Booting from Hard Disk 0...
error: symbol `grub_calloc' not found.
Entering rescue mode...
grub rescue> _
I rebooted 3 servers in this way (all running Ubuntu
I was able to recreate the upgrade failure by installing the following
packages:
python-pyqt5.qtwebchannel
python-pyqt5.qtsensors-dbg
python-pyqt5.qtopengl-dbg
I'm not sure if all three are required if a subset will also produce the
error.
--
You received this bug notification because you are
I confirm the bug.
Upgrading to 0.9.4 did the trick, and it is now running as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873944
Title:
[SRU] Upgrade rapid-photo-downloader to version
I mean "upgrading to 0.9.24 did the trick"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873944
Title:
[SRU] Upgrade rapid-photo-downloader to version 0.9.24
To manage notifications about this
I recently added nerd-fonts to my system. I placed them in
~/.local/share/fonts directory.
https://github.com/ryanoasis/nerd-fonts
And now I have this bug.
I removed that directory and copied all those fonts to ~/.fonts and the
bug is gone. I'm not sure if some programs need the fonts to be in
This bug was fixed in the package ark - 4:20.04.3-1
---
ark (4:20.04.3-1) unstable; urgency=medium
* Team upload.
* New upstream release.
* Backport upstream commit 0df592524fed305d6fbe74ddf8a196bc9ffdb92f to fix
vulnerability to path traversal attacks (CVE-2020-16116);
#19 and forward assume kernel 5.3.0-61 is good, according to bug
description; however, it may worthwhile to give it:
https://people.canonical.com/~alexhung/LP1888570/Ubuntu-5.3.0-61.55/
Especially, all tries were bad kind of worrying...
If it is good, the next one is
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/388432
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
grub-install failure does not
Can confirm for Ubuntu Server 20.04.
First Aid:
https://www.reddit.com/r/Ubuntu/comments/i0vlf0/repair_grub_boot_error_symbol_grub_calloc_not/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889509
This could have the same reason as the bug filed by me:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1882797
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845793
Title:
Since upgrade to
We've recently updated the release upgrader and it includes a change
which may resolve the failure to calculate the release upgrade which you
encountered. Please try the upgrade again and report back. Thanks in
advance!
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New =>
There is a new version of the release upgrader available which may
resolve the failure to calculate the upgrade issue you encountered.
Could you please try upgrading again and report back? Thanks in advance.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Confirmed => Incomplete
There is a new version of the release upgrader available which may
address the failure to calculate an upgrade which you encountered. Could
you please try the upgrade again and report back? Thanks in advance.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
Yes, I have just crashed into this.
My system is now totally secure. To the point where it is impossible to get
past this boot up screen to actually log in.
I can't do anything. I can't upgrade anything. I can't fix anything. I can't
access the boot disk. The box is not bricked.
Great work
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/388423
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
Title:
grub-install failure does not
Thomas - Thank you very much for reviewing, sponsoring, adding to the
focal-proposed upload queue, and subscribing ~ubuntu-sru.
Mathew - Thanks for tidying up the bug details.
SRU Team - Thank you in advance for reviewing, and of course don't
hesitate to ask if you have any questions for me.
--
All autopkgtests for the newly accepted pulseaudio (1:11.1-1ubuntu7.10) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
ffmpeg/7:3.4.8-0ubuntu0.2 (arm64, i386, s390x, ppc64el, armhf, amd64)
Please visit the excuses page listed
** Attachment added: "grub-pc.0.crash"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556/+attachment/5397267/+files/grub-pc.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889556
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Jeff Lane (bladernr)
--
You received this bug notification because you are a member of
Installing for i386-pc platform.
grub-install: error: cannot find a GRUB drive for /dev/sda. Check your
device.map.
dpkg: error processing package grub-pc (--configure):
subprocess installed post-installation script returned error exit status 1
...
Errors were encountered while processing:
Thank you @ianchanning for the recovery notes through the portal.
I'll also add in a few links that might help.
For users looking for general recovery steps :
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass#Recovery
For users looking how to mitigate this before
This change was made by a bot.
** Changed in: linux (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/1889692
Title:
touchpad not working
To manage
** Changed in: linux-aws (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864669
Title:
overlayfs regression - internal getxattr operations
A bug from 2015 and still "new". Nice – Here's a fix:
Edit the systemd unit file with `sudo systemctl edit --full
transmission-daemon.service` and replace the line
> After=network.target
with the lines
> After=network-online.target
> Wants=network-online.target
With this, systemd should wait
Hi Sebastien,
The type of key is a 2048-bit RSA key.
Additional notes:
- The issue occurs with both password & passwordless keys.
- The issue only occurs when importing. (Creating a new SSH key via the
Seahorse UI works fine)
There are no warnings or journalctl output.
--
You received this
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885271
Title:
kernel oops xr-usb-serial
To manage notifications
--- Comment From i...@de.ibm.com 2020-07-30 17:13 EDT---
Unfortunately zlib does not accept patches at the moment, so it is unlikely
that this fix will be accepted in the strict sense of the word anytime soon.
However, I will include
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887990
Title:
Bionic update: upstream stable patchset 2020-07-17
To
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859756
Title:
[hns3-0115] add 8 BD limit for tx flow
To manage
Upgrade has started correctly.
Still running ...
On 30/07/2020 22:13, Brian Murray wrote:
> There is a new version of the distribution upgrader which should resolve
> your issue. Can you please try the release upgrade process again and
> report back? Thanks in advance.
>
> ** Changed in:
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886710
Title:
Bionic update: upstream stable patchset 2020-07-07
To
1 - 100 of 384 matches
Mail list logo
