** Changed in: ifenslave (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889324
Title:
ifenslave invalid syntax in hooks
To manage notifications about this
Failure to call reboot, should not trigger rollback to previous suite.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888916
Title:
upgrade from bionic to focal a server with molly-guard moves back
Package looks good, uploaded to -proposed, it'll need SRU team to look
at it now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888749
Title:
sup-mail broken and unusable after Bionic to Focal
We had this problem yesterday on only one of two Ubuntu 18.04 instance
on AWS. We had to rollback to a previous snapshot to make the instance
bootable again.
So we did a quick test with these two AMI:
ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20200408 -
ami-0edd51cc29813e254
** Also affects: ubuntu-release-upgrader (Ubuntu Groovy)
Importance: Medium
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888916
Title:
upgrade from bionic to focal a
Groovy has 1.0-3 currently in it, marking the Groovy task for this as
"Fix Released" while I work on the Focal task. Power outage last night
made me not able to complete my tests, but they're running now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
### uname -a (64-bit ARM, official image):
`Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020
aarch64 aarch64 aarch64 GNU/Linux`
### LSB release (Ubuntu *Server*, focal):
Description:Ubuntu 20.04.1 LTS
### Interesting packages installed
-
@Christian, thx for the preliminary fix and the test.
May I ask if the path is already upstream accepted or if you are working on
that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889059
Title:
> In benchmarking we didn't observe much computational difference
between the too once the CPU is fully loaded. However, cranking up or
cranking down the load one will discover that the performance setting is
more responsive than powersave.
this is exactly the problem in production environments;
** Changed in: rtl8821ce (Ubuntu Groovy)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884648
Title:
rtl8821ce 5.5.2.1-0ubuntu3 ADT test failure with linux-5.8
** Changed in: debootstrap (Ubuntu)
Importance: Undecided => High
** Changed in: debootstrap (Ubuntu Eoan)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772556
** Changed in: pycodestyle (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: pyflakes (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: python-flake8 (Ubuntu Focal)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
> I would suggest switching back to powersave/ondemand either with a new
service or the kernel config.
re: new service, the existing package cpufrequtils (and related package
cpufreqd) provides a configurable service to manage governor settings
(and other related settings). The old ondemand
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Wishlist
** Changed in: procps (Ubuntu Groovy)
Importance: Undecided => Wishlist
** Changed in: util-linux (Ubuntu Groovy)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of
My recreate is with an AWS EC2 instance with an NVMe root device as that
is one known way to trigger an error in cloud-init cc_grub_dpkg so that
it does not write a valid debconf for grub-pc install_devices, however
this is broader than NVMe root with cloud-init.
--
You received this bug
** Changed in: mate-desktop
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889632
Title:
mate-settings-daemon should be compatible with light-locker
To manage
** Changed in: python3.8 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887847
Title:
python3.8 subinterpereters cause use-after-free in asyncio
To
** Changed in: oops (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887828
Title:
Drop Python 2 support
To manage notifications about this bug go to:
--- Comment From christian.r...@de.ibm.com 2020-07-30 10:45 EDT---
Compiled and ran DeInflate.java test program.
# javac DeInflate.java
Without fix encountered the following behaviour:
# java DeInflate.java
Exception in thread "main" java.lang.RuntimeException: De/inflater
Hi Paride,
based on my experience and on what I read on these bug reports, the steps to
repro are:
- have an Ubuntu system with mysql-server-5.7 version 5.7.30 installed
- systemctl stop mysql
- systemctl disable mysql
- apt install mysql-server-5.7 (in order to upgrade it to the latest version,
>From my testing cma-128 is the largest that worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889223
Title:
vc4-kms-v3d boot failure focal armhf preinstalled server
To manage notifications
** Description changed:
Since nodejs 12.18.1 entered groovy-proposed, autopkgtests that rely on
- node-sha to compute SHA-1 hashes started failing reliably on ppc64el.
+ node-sha.js to compute SHA-1 hashes started failing reliably on ppc64el.
This affects the following packages:
-
Adding to my previous report I should have mentioned that
libraspberrypi-bin does not exist and so can not be installed
root@rpi4-ubuntu:/etc/apt/sources.list.d# apt-get install libraspberrypi-bin
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package
This seems to have been fixed on version 2.11.0
https://git.launchpad.net/~ubuntu-server-dev/ubuntu/+source/openvswitch/commit/?id=7b4f5ecb46bf853d8c814f31b8ddb3444dd60289
Unfortunately, that version is not available for Ubuntu 18.04
--
You received this bug notification because you are a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu Bionic)
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/1889556
Just to be sure you didn't miss a few facts here as you really like to
rub it under people's noses:
* Snap mangles Chromium's configuration directory
* Snap-mangled Chromium configuration directory is not backupable
* Snap-mangled Chromium configuration directory is not compliant with
the de
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu Focal)
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/1889556
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu Xenial)
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/1889556
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (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/1889556
Title:
Public bug reported:
Background:
some users (as from https://askubuntu.com/q/1263287/66509 ) do not want to use
mate-screensaver, but want to use light-locker instead
Steps to reproduce:
1. Remove MATE ScreenSaver with
```
sudo apt-get purge mate-screensaver
sudo apt-get autoremove --purge
** Merge proposal linked:
https://code.launchpad.net/~xnox/grub/+git/grub/+merge/388383
--
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
OK, so the issue we're dealing with here is that bug 1877491 fixed the
grub install device for _new_ NVMe instances, but it did not fix it on
existing NVMe instances. So, for existing instances, they will still
have an incorrect grub install device configured (something like
/dev/sda).
grub has
this is a feature request for the docker version in bionic/focal to pick up a
commit from v19.03.9
to allow these syscalls (or update these packages to 19.03.9)
the libseccomp SRU was a necessary condition to allow such a backport
(in other words the syscalls were blocked at the libseccomp
Public bug reported:
In Gujarati Font "Pra" is not proper rednder E.g. Prakash world is not
shown Fadiyto Sha"પ્રકાશ"
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ibus-m17n 1.4.2-1
ProcVersionSignature: Ubuntu 5.4.0-1015.15-raspi 5.4.44
Uname: Linux 5.4.0-1015-raspi aarch64
Please resolve it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889630
Title:
In Gujarati Font "Pra" is not proper rednder E.g. Prakash world is not
shown Fadiyto Sha"પ્રકાશ"
To manage
Hello!
Regarding the comment #8, I didn't get the same positive experience on
my side. It was more closer to what is described in comment #9. See bug
1889479 for more details.
I would suggest switching back to powersave/ondemand either with a new
service or the kernel config. Having a dedicated
> Anything else has little objective value.
That's just your opinion.
> That's not an assumption, it's a fact: https://snapcraft.io/docs
/installing-snapd.
It's an assumption, there are a lot of distributions that stay away from
snap.
> Most (average) users don't care about packaging formats
THanks, the testcase (updated to be a bit slower) is enough to confirm
the issue, the upstream commit also makes the progress correctly
displayed but there is a small issue remaining that the name isn't
updated when decompressing the other parts
** Changed in: file-roller (Ubuntu)
Status:
*** This bug is a duplicate of bug 1885730 ***
https://bugs.launchpad.net/bugs/1885730
Hi Dan,
Oh yes indeed, sorry I looked for issues in systemd and I missed it!
I'm fine with the "duplicate" status.
Cheers,
Matt
--
You received this bug notification because you are a member of Ubuntu
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/388381
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831789
Title:
Add "dis_ucode_ldr" to linux
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/388381
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882663
Title:
Specify flavour ordering
To
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/+merge/388381
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878541
Title:
Grub fails to load kernel from
@raof this is probably true if the path is long, but I can't figure out
how to patch it...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889166
Title:
mir: build failure on s390x
To manage
I will test that with the default .dtbo file and see if it works for us.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889223
Title:
vc4-kms-v3d boot failure focal armhf preinstalled server
To
*** This bug is a duplicate of bug 1575053 ***
https://bugs.launchpad.net/bugs/1575053
> `$XDG_CONFIG_HOME/$SOFTWARE_NAME` is the de facto way
That's different from "does not follow the XDG base directory specification".
A specification (hopefully) is unambiguous. Anything else has little
Caused by https://github.com/microsoft/WSL/issues/4898
** Bug watch added: github.com/microsoft/WSL/issues #4898
https://github.com/microsoft/WSL/issues/4898
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That cleared up the autopkgtest regression.
systemd [bionic/i386]
Version TriggersDateDurationRequester Result
237-3ubuntu10.41kmod/24-1ubuntu3.5 2020-07-29 23:55:56 UTC
1h 03m 06s mfo pass ...
--
You received this bug
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 1889625
and then change the status of the bug to 'Confirmed'.
If, due to the
** Changed in: file-roller (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889447
Title:
Progress dialog looks frozen for multi-file 7z archives
To manage
I’ve also had this thought. I’ve tried this, but the flickering will start
before then, usually during the startup splash and login screen. Makes me
think that you’re right about it being a kernel bug
On Wed, Jul 29, 2020 at 9:15 PM Daniel van Vugt <1888...@bugs.launchpad.net>
wrote:
> Maybe try
Public bug reported:
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
commit 41b14fb8724d5a4b382a63cb4a1a61880347ccb8
Author: Tariq Toukan
I don't know if this adds anything to the discussion, but my private
Lenovo T530, running debian stable, boots into the same error. So not
only Azure systems are affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Cliff,
This is odd, but if I understand correctly you have a setup that
triggers the problem and a slightly different setup that does not, on
the same system. This means we are in a good position already. I'd
follow Christian's suggestion and make them even more and more similar
until you can
Maybe use these steps to create the archives, then double-click on the
first resulting archive file (tmp1.7z.001) and do an extract.
mkdir tmp1
cd tmp1
for f in a b c d e f g h i j
do
for g in a b c d e f g h i j
do
for h in a b c d e f g h
Thanks Andy, that worked fine for me.
I still had 'some' focal kernel git tree lying around on a s390x system,
updated it,
ran 'fakeroot debian/rules updateconfigs' w/o the patch (neg. test) and it
failed.
I then applied your patch to 'debian/scripts/misc/kernelconfig'
did a clean (just to be
For Azure users (the same should work in any cloud, with small changes)
that end up here while looking for this bug, the steps to recover are:
Deploy a recovery VM using AzCli or just attach a copy of the affected OS vm
disk to a rescue VM.
Once done, connected to rescue VM and:
$ sudo su -
#
> I don't think the specification¹ mandates how folders should be
structured under $XDG_DATA_HOME and $XDG_CONFIG_HOME.
`$XDG_CONFIG_HOME/$SOFTWARE_NAME` is the de facto way, snap ignores it.
Technically, yes, you're absolutely free to use hashes instead of your
software's name when you store
Patch submitted
https://lore.kernel.org/linux-fscrypt/20200730093520.26905-1-po-hsu@canonical.com/T/#u
After this got applied, we can revert this temporary fix:
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=a6abc03f78d80b74f0c740af405b3c5f41b5042c
** Changed in:
The update to version 84 is in progress, but as I wrote earlier it's
targetting 16.04 and 18.04 only. You may try to run the 18.04 packages
on 20.04, but there's no guarantee it will run at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Setting Importance to High -- this is breaking many systems in Azure.
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
--
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:
** 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_callow' not found.
+ error: symbol `grub_calloc' not found.
Entering rescue mode...
grub rescue> _
I rebooted 3
Olivier: No, rm -rf ~/snap/chromium/common/.cache does not fix the
problem. Icons still look to me exactly the same as in my screenshot in
comment #21.
Also I just noticed where Fernando said in comment #13 that he thought
probably not many people open the file chooser in a browser. I regularly
Hello Andrew, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.42 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hi Oliver
Yes, I saw chromium-browser-dbgsym on those old releases, but I'm
running 20.04 LTS
https://launchpad.net/ubuntu/bionic/+package/chromium-browser-dbgsym
They seem out of date, the v83 build.
Do you think they would work with 20.04LTS? Is there an easy way to
compile them?
$
Hello Dan, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.42 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Jose, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.42 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello John, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.42 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
As per our discussion, since the changes here are relatively sane and
with a low regression risk, I have accepted this without a clear
reproducer. Please be sure to try and contact someone that has an
affected device/configuration and trying to test it there - if not, your
proposed test of
Hi You-Sheng,
I appreciate your message.
Firstly, I didn't see any messages within dmesg log while network high
latency occurred.
Secondly, I didn't encounter this symptom again after I changed wifi
router to RKUS R750.
Thanks,
Lawrence Chiu
--
You received this bug notification because you
Hello Tim, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.42 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
The issue is old and has been discussed e.g in
https://bugzilla.redhat.com/show_bug.cgi?id=538617
The sounds have been removed in that commit
https://cgit.freedesktop.org/sound-theme-freedesktop/commit/?id=7c4e2f77
Are service-login and logout really supposed to be session login and
logout
Hello guenthert, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.42 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Apparently it's not just us, this is an upstream change. Dave Jones
found this: https://www.raspberrypi.org/blog/latest-raspberry-pi-os-
update-may-2020/
To select headphones, the recommended process is now to create a file called
.asoundrc in your home dir with these contents:
defaults.pcm.card
Looks like this issue is related: https://bugs.launchpad.net/cloud-
init/+bug/1877491
I've verified now that using cloud-init `package_upgrade: true` using an
Ubuntu AMI from later than June 1 avoids the problem described in this
ticket.
--
You received this bug notification because you are a
Hm, I wonder if in postinst, in grub-pc case,
else
break # noninteractive
fi
Should actually be
exit 1, like it is in the UPGRADE_FROM_GRUB_LEGACY case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm not sure this is the proper package.
I installe nvidia-340 which I cannot select
** Package changed: ubuntu => nvidia-graphics-drivers-340 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a security vulnerability ***
Public security bug reported:
Failure to install new grub core to the specified device does not
correctly prevent upgrade to incompatible modules (LP: #1889509)
$ sudo debconf-get-selections |grep sda
grub-pc grub-pc/install_devices_disks_changed
The plot thickens. Can you reliably reproduce this situation, where
unplugging and plugging again the 5C makes it work, but it doesn't after
a reboot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm attaching a full log from the recreate that shows additional details
** Attachment added: "grub_bug_log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556/+attachment/5397176/+files/grub_bug_log
** Description changed:
Failure to install new grub core to the specified
I don't think the specification¹ mandates how folders should be
structured under $XDG_DATA_HOME and $XDG_CONFIG_HOME. Or is there a
follow-up specification that does that?
Hopefully snapd behaves (mostly) the same on all supported
distributions, so distro-hopping shouldn't be a concern either.
** Tags added: regression-release
** Tags added: regression-update
** Also affects: grub2 (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Xenial)
Importance:
Whenever I open an application it is blinking for a while
** Attachment added: "Untitled 9_480p.mp4"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889252/+attachment/5397175/+files/Untitled%209_480p.mp4
--
You received this bug notification because you are a member of Ubuntu
Hmm, actually the default configuration on these images does appear to
contain an error. From the debconf database:
> Name: grub-pc/install_devices
> Template: grub-pc/install_devices
> Value: /dev/sda
> Owners: grub-pc
> Flags: seen
The correct device on newer EC2 instances would be
I have to agree with Maarten. The pattern we ran into it with was using
an Ubuntu base AMI on AWS. It boots fine. If you upgrade interactively,
you get a prompt that can be answered correctly. If you use `cloud-init`
and specify `package_upgrade: true` then the instance will come up
correctly on
*** This bug is a security vulnerability ***
Public security bug reported:
cc_grub_dpkg was fixed to support nvme drives, but didn't clear the
state of cc_grub_dpkg and didn't rerun it on upgrades
However, that only fixed the issue for the newly first-booted instances on nvme.
All existing
There are chromium-browser deb packages with debug symbols (chromium-
browser-dbgsym) published in the Ubuntu archive for Ubuntu 16.04 and
18.04. In newer Ubuntu releases the deb is a wrapper that installs the
chromium snap.
--
You received this bug notification because you are a member of
Further testing showed that the attached rtld-audit-repro.tar.xz did not
reproduce the described behavior.
An updated and much simpler repro in audit.c wich does actually
reproduce the described issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
New repro that actually works.
** Attachment added: "audit.c"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1871762/+attachment/5397174/+files/audit.c
** Attachment removed: "Example reproducing the observed behavior."
** Project changed: intel => ubuntu
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889172
Title:
upgrade ndctl v69
To manage notifications about this bug go to:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
@juliank This happens with the _default_ AWS Ubuntu images, so I highly
doubt it's a bug in anyone's configuration (for example: ami-
05ed2c1359acd8af6 (Ubuntu 16.04) or ami-0d359437d1756caa8 (Ubuntu 18.04)
in AWS region eu-central-1/Frankfurt). Steps to reproduce:
1. Launch new EC2 instances
Hi Mauro,
Thanks for your follow-up comment and analysis in LP: #1605948, we are
however not able to do debugging work or provide support for non-Ubuntu
distributions. If you are able to provide steps to reproduce the issue
in a clean Ubuntu system we'll certainly look into it, being glad to
know
*** This bug is a duplicate of bug 1592669 ***
https://bugs.launchpad.net/bugs/1592669
Replied to LP: #1605948, as this bug report is marked as a duplicate of
it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, normally I'd say it's very risky to include a bugfix for a bug that
does not have a clear testcase, especially for a component such as
systemd (high risk). That being said, looking at the actual change -
fixing an uninitialized pointer - I feel much more confident.
--
You received this bug
*** This bug is a duplicate of bug 1885730 ***
https://bugs.launchpad.net/bugs/1885730
Thanks - I believe this is a duplicate of bug 1885730
** This bug has been marked a duplicate of bug 1885730
Bring back ondemand.service or switch kernel default governor for pstate -
pstate now
** 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/1889552
Title:
package libc6:amd64 2.31-0ubuntu9 failed to install/upgrade: installed
libc6:amd64 package
> Now, when I boot Ubuntu, sometimes wireless card work and sometimes
not.
I do have the same issue with BCM4360. Sometimes my card is working,
sometimes not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Package installation failed when upgrading WSL setup of Ubuntu 18.04 to
20.04.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libc6:amd64 2.31-0ubuntu9
ProcVersionSignature: Microsoft 4.4.0-19041.1-Microsoft 4.4.35
Uname: Linux 4.4.0-19041-Microsoft x86_64
Test package available from:
https://launchpad.net/~waveform/+archive/ubuntu/oops/+packages
Built from branch at:
https://code.launchpad.net/~waveform/ubuntu/+source/oops/+git/oops/+ref
/remove-python2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Right now the queue is full of builds that are doing
Renaming libkf5emoticons-bin-dbgsym_5.72.0-0ubuntu1_arm64.deb to
libkf5emoticons-bin-dbgsym_5.72.0-0ubuntu1_arm64.ddeb
dpkg-deb: building package 'libkf5emoticons-data' in
201 - 300 of 384 matches
Mail list logo
