Public bug reported:
I was trying to install Xpra when I found the error "El paquete
«libavcodec57» no tiene un candidato para la instalación" after trying
to reinstall the package, the problem is persistent although it says
that other package makes reference to it.
** Affects: ffmpeg (Ubuntu)
I double Martin Malec's observation that the Ubuntu package since 19.04
doesn't contain GNU Barcode. It works on Debian however.
I contacted the package maintainer about this. Hopefully it will be
updated soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
It appears Red Hat fixed this problem with a kernel patch in RHEL 7.5
that was not upstreamed.
https://access.redhat.com/errata/RHSA-2018:1062
BZ - 1471875 - soft lockups during unmount when dentry cache is very
large
https://bugzilla.redhat.com/show_bug.cgi?id=1471875
** Bug watch added: Red
Performance degrades can also related to power saving. Try kernel
parameter "pcie_aspm=off" to verify whether it improves
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/194
Title:
Qualcomm
Daniel,
As requested, I enabled Wayland and logged in with 'Ubuntu on Wayland'.
The second monitor is now working.
Thank you. I am very impressed with the quick turn around and support.
Jim Battis
On 7/30/20 10:11 PM, Daniel van Vugt wrote:
> Thanks. It looks like Xorg is the cause of this
Public bug reported:
I can't login in system
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub-efi-amd64-signed 1.142.4+2.04-1ubuntu26.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture:
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Triaged => In Progress
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Qt responded and thinks cma-128 will work for our application.
I modified our Pi test unit to use the original Ubuntu 20.04 .dtbo file
and booted successfully when I used the dtoverlay=vc4-kms-v3d,cma-64
setting.
I will test our UI with this configuration early next week.
--
You received this
Issue did return for me. You can always take a picture of the screen
with your phone if screenshot does not capture the cursor. I did take a
picture of it happening in 19.10 as well (attached)
** Attachment added: "IMG_6554.jpg"
The freeze happened again, despite the UEFI setting "Typical Current Idle".
It happened after display energy saving after the wakeup.
** Attachment added: "freeze_31_july_2020.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883012/+attachment/5397562/+files/freeze_31_july_2020.txt
Hi, Lili. I think this new problem is caused by the older qemu version
that we have in trusty. Does it work without the -cpu host argument?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882624
You seem to have some python3.8 packages installed with version numbers
that are greater than ones in the release to which you are trying to
upgrade. This is causing the failure to calculate the upgrade so please
remove them and try the upgrade again.
libpython3.8-minimal 3.8.3-1+bionic1 1
I will add this is also reported as a problem on github so I am not the
only one seeing this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888970
Title:
V20.2 Fails to start Telescope/EQMOD
To
There was an issue communicating with the mirror of the Ubuntu archive
which you use. This is an issue you will need to sort out before you can
upgrade to the new release of Ubuntu.
2019-10-27 16:15:33,625 DEBUG examining: 'deb
http://in.archive.ubuntu.com/ubuntu/ disco main restricted'
There was an error communicating with the mirror of the Ubuntu archive
which you use. This is an issue you'll need to resolve before you can
complete your upgrade.
2019-10-27 16:15:33,625 DEBUG examining: 'deb
http://in.archive.ubuntu.com/ubuntu/ disco main restricted'
2019-10-27 16:15:33,625
This is likely due to one or some of the PPAs you have enabled. Please
use the tool ppa-purge from the ppa-purge package to remove the PPAs and
try the upgrade again.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
This bug was fixed in the package ubuntu-release-upgrader - 1:20.10.8
---
ubuntu-release-upgrader (1:20.10.8) groovy; urgency=medium
* DistUpgrade/DistUpgradeCache.py: Ensure that the linux metapackage is
never removed during a distribution upgrade. (LP: #1889449)
-- Brian
This bug was fixed in the package oops - 0.0.14-0ubuntu3
---
oops (0.0.14-0ubuntu3) groovy; urgency=medium
* Drop Python 2 support (LP: #1887828)
-- Dave Jones Thu, 16 Jul 2020 17:22:35
+0100
** Changed in: oops (Ubuntu)
Status: New => Fix Released
--
You received
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gvfs (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/1798828
Title:
There was a failure communicating with the mirror of the Ubuntu archive
which you use. This is something you'll need to sort out as the mirror
is available now.
2020-07-03 15:50:12,824 DEBUG examining: 'deb
http://us.archive.ubuntu.com/ubuntu/ bionic main restricted'
2020-07-03 15:50:12,824
There was an issue communicating with the mirror of the Ubuntu which you
use. You'll need to sort this out so that you can complete the upgrade.
2020-05-14 13:59:09,305 DEBUG examining: 'deb
http://in.archive.ubuntu.com/ubuntu/ eoan main restricted'
2020-05-14 13:59:09,306 DEBUG
There was an error communicating with the mirror of the Ubuntu archive
which you use. This is something you'll need to resolve so that you can
upgrade.
2020-05-20 20:28:12,333 DEBUG examining: 'deb https://archive.ubuntu.com/ubuntu
bionic main restricted'
2020-05-20 20:28:12,333 DEBUG found
There was a problem communicating with the mirror of the Ubuntu archive
which you use This is something you'll need to sort out so you can
complete the upgrade.
2020-06-27 17:45:31,643 DEBUG examining: 'deb
http://in.archive.ubuntu.com/ubuntu/ disco main restricted'
2020-06-27 17:45:31,643 DEBUG
The package chrome-remote-desktop is not one provided by the Ubuntu
archive and subsequently there is not thing we, the developers of
Ubuntu, can do about the issue.
** Package changed: ubuntu-release-upgrader (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: Confirmed => Invalid
--
You
If the installer is crashing you'll want to include log files about the
installation method you are using. For example if you are using ubiquity
you would want to use 'ubuntu-bug ubiquity' to gather log files about
the crash.
** Package changed: ubuntu-release-upgrader (Ubuntu) => ubuntu
**
Unluckily this commit breaks hibernation:
0a14dbaa0736 ("video: hyperv_fb: Fix hibernation for the deferred IO feature"):
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/focal/commit/?h=Ubuntu-azure-5.4.0-1022.22=0a14dbaa0736a6021c02e74d42cf3a7ca5438da6
We should
hplip 3.20.6 does not resolve these issues for me.
I'm getting the same errors regarding pyqt4 as w/ the earlier versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879649
Title:
Since I
The workaround for me was to disable vt_handoff in /etc/grub.d/10_linux*
(i.e. set vt_handoff=0 in both places near the top of the file).
That resolved the issue completely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After further investigation I've discovered this is actually due to the
wine packages you have installed with version 5.0.1~bionic. If you
remove those you should be able to upgrade to the next release of
Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
It seems the bug that actually describes the "cannot rotate monitor to
portrait mode" issue is 1874567, and a fix is in hand. Apologies for the
noise here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ubuntu LTS 16.04.6
118K files in trash
gvfs-trash consumes both CPUs and 100% of available memory
"empty trash" goes into prepare phase, but nothing appears to happen,
presumably because of the large number of files, so I closed the window
by clicking the
rm -rf ~/.local/share/Trash/*
copied from Bug 1798828
--
Ubuntu LTS 16.04.6
118K files in trash
gvfs-trash consumes both CPUs and 100% of available memory
"empty trash" goes into prepare phase, but nothing appears to happen,
presumably because of the large number of files, so I closed the window
by clicking the
rm -rf
Brian,
Thank you for the update.
I was able to update and upgrade the machine and after logging into Ubuntu One,
I was able to complete the upgrade to 19.10 and 20.04 successfully.
I commented this information in the ticket.
Thanks again,
Joe Sergi
Sent from Yahoo Mail on Android
On Fri,
Could it have anything to do with the patch being applied in node-
sha.js, 0002-Fix-FTBFS-in-32-bits-arch.patch?
var hash = new Sha1()
- var bigData = Buffer.alloc(0x1 / 8)
+ var bigData = Buffer.alloc(0x1fff8 / 8)
I wonder if this patch were disabled for ppc64el, if the test
Public bug reported:
bug
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: mysql-server-8.0 8.0.21-0ubuntu0.20.04.3
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
AptOrdering:
mysql-client-8.0:amd64:
Public bug reported:
upgrade bug from 18.04 to 20.04
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: friendly-recovery 0.2.41
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
** 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/1889950
Title:
package mysql-server-8.0 8.0.21-0ubuntu0.20.04.3 failed to
install/upgrade: installed
after reboot the Trash icon shows empty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798828
Title:
gvfsd-trash fills up memory (uses about 1 GB) if Trash contains
thousands of files
To manage
** 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/1889949
Title:
package friendly-recovery 0.2.41 failed to install/upgrade: installed
friendly-recovery package
** Also affects: linux (Fedora)
Importance: Undecided
Status: New
** Changed in: linux (Arch Linux)
Status: New => Confirmed
** Changed in: linux (Fedora)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Can confirm, using nvidia-driver-450 seems to resolve the issue. I
installed from here: https://launchpad.net/~graphics-
drivers/+archive/ubuntu/ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
reported upstream at https://gitlab.com/gitlab-
org/gitlab/-/issues/233169
** Bug watch added: gitlab.com/gitlab-org/gitlab/-/issues #233169
https://gitlab.com/gitlab-org/gitlab/-/issues/233169
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
So do we still have the following commits needed to patches to Ubuntu
kernel ?
vmxnet3: prepare for version 4 changes
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=123db31d01219a4f794f3769e7bca6649d65ecb1
vmxnet3: add support to get/set rx flow hash
** Also affects: sssd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: sssd (Ubuntu Focal)
Status: New => Triaged
** Changed in: sssd (Ubuntu)
Status: New => Triaged
** Changed in: sssd (Ubuntu)
Importance: Undecided => Medium
** Changed in: sssd
thank you Sebastien for being a kind person
but there is no need for the requested info
see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790249
and https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027
--
You received this bug notification because you are a
Ok I just did a quick test. It is writing to my xorg.conf.
Also I noticed that when ubuntu starts up, on the login screen both
screens have the purple background color - it's only after that when it
gets to the desktop does the second display turn off.
--
You received this bug notification
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
This bug is present in Debian as well and Ubuntu currently does not make any
changes to the Debian package. Therefore, this bug would be best fixed
directly in Debian, and then Ubuntu will pick up the fix
Public bug reported:
Trackpad does not work and is not present in cat /proc/bus/input/devices
System Information
Manufacturer: LENOVO
Product Name: 20RV
Version: Lenovo ThinkBook 14-IML
SKU Number: LENOVO_MT_20RV_BU_idea_FM_Lenovo ThinkBook 14-IML
Family:
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/1889952
Title:
Trackpad undetected Lenovo ThinkBook
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881534
[Expired for mysql-8.0 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: mysql-8.0 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877890
[Expired for mysql-5.7 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: mysql-5.7 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for Ubuntu because there has been no activity for 60 days.]
** Changed in: ubuntu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881301
Title:
q
To
Same problem on Ubuntu 20.04 desktop.
The fix was as described above: boot from USB, mount boot disk, chroot,
reinstall grub.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889509
Title:
grub boot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1889721
and then change the status of the bug to 'Confirmed'.
If, due to the
Apologies for the noise. It did work after a reboot/relogin; the
assignment was not immediate as with other global shortcuts I've set.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/661829
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1889721/+attachment/5397326/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1889721/+attachment/5397327/+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/1889721
Title:
FWIW whenever this happened to me, `/boot` was not empty, so ZFS refused
to mount it. Not sure if there's a way, or if it's advisable, to force
it to mount over non-empty…
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I ran tcpdump 'host ubuntu20 and port domain' on my router and looked at
all the other NXDOMAIN at boot time besides this one.
1. PTR request on the IPv4 address of my virbr0 interface. Gone after
uninstalling a couple libvirt-* packages
2. PTR request on ONE of my IPv6 addresses. It's not
https://thehackernews.com/2020/07/grub2-bootloader-
vulnerability.html?fbclid=IwAR0QDfYoo_wLhamrGvv-
yO8qIhAi1jlmiYQ92Uw7PwYRCvbJfpHDyoJxcg4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734147
Hello!
Would like to let you know that this issue is relevant for me as well.
I have ThinkPad 14-IIL, ELAN06034 touchpad is not working.
Upgrading the kernel from default 5.4.?? to both 5.6 (linux-oem-20.04) and
5.7.11 (latest available for Ubuntu right now) did not work.
Would love to share
I used htop to kill deluge but I kept looking and found LOTS of instances of
deluge STILL running!
https://i.imgur.com/0ZzqUCq.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889660
Title:
Public bug reported:
select torrent
click on Files
crash
reproducible!
screengrab
https://i.imgur.com/F5z5jH6.png
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: deluge-gtk 2.0.3-2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
video
https://youtu.be/H4fd2fri2VE
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889660
Title:
deluge not responding to close mouse or key commands
To manage notifications about this bug go to:
https://youtu.be/M24Ivv2z550
deluge-gtk 2.0.3
libtorrent: 1.1.13.0
Python: 3.8.2
OS: Linux Ubuntu 20.04 focal
521 htop (F9 didn't work)
522 apport-bug deluge-gtk (reported bug)
523 kill 1069956 (didn't work)
524 kill 1070006 (didn't work)
525 pkill deluge-gtk (didn't work)
526
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1889721/+attachment/5397332/+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/1889721
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1889721/+attachment/5397329/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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 mismatch between
/boot/grub/i386-pc which is updated, and the grub image in the MBR which is not
[Test case]
1. Boot a
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1889721/+attachment/5397333/+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/1889721
Title:
apport information
** Tags added: apport-collected
** Description changed:
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
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1889721/+attachment/5397330/+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/1889721
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1889721/+attachment/5397334/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1889721/+attachment/5397331/+files/ProcInterrupts.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/1889721/+attachment/5397328/+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/1889721
I've done more research and this may be related to xorg from what I've
been reading. This has also been an issue since ubuntu 17. So many
people have this problem and it's not been fixed 3 ubuntu versions down;
google search xorg media key lag. In summary short spike of cpu usage
when
I have tried using fix provided by @hazrpg
(https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-
dock/+bug/1768543/comments/5) at the
https://askubuntu.com/questions/1183065/windows-not-aligned-properly-in-
the-preview-in-dock-on-ubuntu-19-10/1232740#1232740 and it was fixed.
*** This bug is a duplicate of bug 1835660 ***
https://bugs.launchpad.net/bugs/1835660
Unfortunately, Ubuntu developers forgot something. I have been building
my optimized kernel with lz4 for 5 years ... and here it is necessary to
compile or upload lz4 and only then e.g. sudo
** Tags added: sts
--
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 fail package upgrade (and does not roll
back to matching modules)
To manage
@axt thank you for the update. But the problem is my BIOS has now become read
only. Earlier last year, I tried to upgrade ubuntu from 17 to 19 and since then
the BIOS has become read only. If I make any changes it will not get saved.
That's my main issue.
I cannot boot from USB,
I cannot boot
Looks like Canonical and RedHat have both acknowledged the incident.
Canonical link with full RCA and solution:
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass?WUwbDVmRWk5RCtJZ2IyNUU2SyJ9#Recovery
RedHat link:
That does not meet the criteria for an explicit warning.
The process showed about 150 "packages to be removed".
Voice of the general user:
- What is a package? (I install "apps" or "software")
- What is: idle-python3.7 libgcc1:i386 かきくけこ鬱食飲酒運転踵眉毛 ... ?
- You expect me to check 150 packages to
Any recommendations to fix this in a non-interactive way for those with
more than a handful of servers?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889509
Title:
grub boot error : "symbol
Problem no longer happens with kernel 5.4.0-42-generic.
all previous kernels do not have corresponding headers in the repository:
*Error! Your kernel headers for kernel 5.4.0-40-generic cannot be found.*
so problem cannot be reproduced and can therefore be closd.
--
You received this bug
bionic-verification:
Tested with version 1.93.19+2.02-2ubuntu8.17 from -proposed using the test case
in the description.
Boots successfully in BIOS mode.
Timestamps were updated in EFI mode.
** Tags removed: sts verification-needed-bionic
** Tags added: verification-done-bionic
--
You
Public bug reported:
TBD
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1889735
and then change the status of the bug to 'Confirmed'.
If, due to the
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872383
Title:
blk_update_request error when mount nvme partition
To
Thanks. That's very interesting. I've only ever seen Ubuntu get stuck on
that purple screen when there was a graphics driver bug (it was the
VMware driver last time - bug 1832138). So that makes me think there's a
problem with the nvidia-340 driver, OR it could mean some fallback
codepath in
Hello all! somebody have this issue on Ubuntu 18.04 desktop with
encrypted lvm partition? because i am installed these updates yesterday,
but without reboot. I will glad for your advices about this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Checked the module name, it is changed. and could be loaded on the
machine.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- TBD
+ [Impact]
+
+ If the socket buffer array of a tap queue is full, a received package
+ needs to be dropped. Currently, the check for the array being full is
+ performed lockless, which might lead to use-after-free errors if the
+ socket buffer array has been
I actually think it must be somehow related to my configuration, because
in my previous installation in the same machine (I had to install a
fresh new Ubuntu around 2 weeks ago after an HDD major crash), I was
able to install nvidia-340 drivers.
The only difference between the old and the new
Thanks, but there is another error relates to snaps please see
attachment ,should I continue and don't bother with this error
** Attachment added: "snap- error"
I don't think your choice of hard drive is causing this problem. And
your kernel log reports no errors with the Crucial SSD...
When it was working 2 weeks ago, was that Ubuntu 20.04 or an older
version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@roman-shipovskij, i don't have an installed grub-pc in my system, when
i try to install it i see next:
sudo apt install grub-pc
Чтение списков пакетов… Готово
Построение дерева зависимостей
Чтение информации о состоянии… Готово
Будут установлены следующие дополнительные пакеты:
focal verification:
Tested with version 1.142.4+2.04-1ubuntu26.2 from -proposed using the above
test case.
Boots successfully in BIOS mode.
Timestamps updated in EFI mode.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification
Public bug reported:
== Comment: #0 - Heinz-Werner Seeck -
2020-07-31 03:28:30 ==
On z13 we have that vector alignment hints are already accepted. This backport
enables GAS to accept such hints not only for target z14 but also for z13.
Since GCCs default target on Ubuntu is z13 for s390x, we
201 - 300 of 337 matches
Mail list logo
