Tested on x86 xenial-hwe. `update-initramfs` works and no ehci-platform
in initrd. System works fine after reboot.
ubuntu@zwicky:~$ sudo update-initramfs -k all -u
update-initramfs: Generating /boot/initrd.img-4.15.0-65-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
update-initramfs:
[Expired for ntp (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ntp (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
** Changed in: xserver-xorg-video-intel
Status: Confirmed => Unknown
** Bug watch added: gitlab.freedesktop.org/mesa/drm/issues #8
https://gitlab.freedesktop.org/mesa/drm/issues/8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
Seems to work fine on disco:
sarnold@millbarge:~$ sudo apt install libssl1.1 openssl
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
linux-image-5.0.0-20-generic
Seems to work fine from disco:
sarnold@millbarge:~$ sudo apt install libssl1.1 openssl
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
linux-image-5.0.0-20-generic
This bug was fixed in the package grep - 3.1-2build1
---
grep (3.1-2build1) bionic; urgency=medium
* No change rebuild. (LP: #1844524)
-- Tiago Stürmer Daitx Wed, 18 Sep 2019
15:00:16 +
** Changed in: grep (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
The verification of the Stable Release Update for grep has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Has there been any testing performed on the architectures on which the
module is compiled in please, for example amd64? It seems to me that
this is a particularly important code path to test, since it is
identified as different and a bug could render regressed systems
unbootable.
--
You received
*** This bug is a duplicate of bug 1814611 ***
https://bugs.launchpad.net/bugs/1814611
This is a duplicate of bug 1814611 which we are planning on fixing. If
you want to be able to use ubuntu-bug in the interim you'll need to set
"Send error reports to Canonical" to On.
** This bug has been
Public bug reported:
Can't run wine64. I googled and they told me i have problem with my
graphic card drivers
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
Uname: Linux 4.15.0-64-generic x86_64
@laney maybe you know if the armhf testbeds were recently moved from lxd
to lxc containers?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1845337
Title:
Disco
** Changed in: ibus (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1844853
Title:
IBus no longer works in Qt applications after
The 'good' tests have a dir being mounted '/dev/.lxd-mounts' while the 'bad'
tests have a dir being mounted '/dev/.lxc' as well as '/dev/.lxc/proc'. In the
'bad' case, the test is making sure there are no unexpected writable
directories other than the single one it's expecting (and other
@tf8 the patch in
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/comments/8
against a live server has been working fine for us on AWS for almost a
year now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
jik@jik5:~$ sudo systemctl is-enabled whoopsie
disabled
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1843630
Title:
ubuntu-bug not opening anything in the browser
Can you run 'systemctl is-enabled whoopsie' and paste the output? Thanks
again!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1843630
Title:
ubuntu-bug not opening
** Changed in: systemd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1845314
Title:
udisks2 fails to install in a container with systemd
On Ubuntu 18.04 with noexec on /tmp running 'apt-get install -y selinux'
and then doing a required reboot will give you a non-booting host.
As an aside, the same security guidance (CIS Benchmarks for one) about
noexec on /tmp should be applied to /var/tmp, so changing
On thinking about this, it does seem the behavior change of udevadm will
be highly disruptive to existing callers of udevadm trigger, so I opened
upstream bug to try to address it without needing all callers to ignore
its return code.
** Bug watch added: github.com/systemd/systemd/issues #13652
Public bug reported:
Kindly help me to rid of this problem.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
Uname: Linux 4.15.0-65-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.7
Thanks for your report!
Hmm... That wiki page you referred to was last edited 11 years ago and
is obsolete to a large extent.
Today, on an Ubuntu system, it's normally GTK (not IBus, so I'm closing
this bug report) which deals with rules in the ~/.XCompose file. I can
confirm that GTK does not
** Changed in: snapd
Status: New => Triaged
** Changed in: snapd
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1840375
Title:
** Attachment added: "bad case - short log"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+attachment/5291156/+files/bad-short.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Attachment added: "good case - short log"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+attachment/5291157/+files/good-short.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Attachment added: "good case - full log"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+attachment/5291155/+files/good.log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
Since the recent few weeks systemd autopkgtest @ armhf @ disco fail [1].
The log is very (very) long and partially interwoven due to concurrent
execution.
Somewhere in between we see this subcase is the one failing: root-unittests
Of this test (which again has many
** Attachment added: "bad case - full log"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1845337/+attachment/5291153/+files/bad.log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Also add a qemu task which is blocked by it from migrating through an
SRU
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1845337
Title:
Disco autopkgtest @ armhf fails
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ibus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
I can confirm this issue on 2 of our VMs running Ubuntu 18.04.
Today I lost a secondary IP on one of the interfaces, after unattended upgrades
installed a new systemd package.
Any updates on this issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1845317
Title:
Add new pci-id's for CML-S, ICL
Status
Public bug reported:
According to manual https://wiki.ubuntu.com/ComposeKey it is possible to define
sequences to type characters and strings with Compose key.
In Ubuntu 18.04 sequences work for characters but not for strings, line like
this:
: "by the way" # Compose b t w
seems to be
Alright,
As this is a problem that does not only affect keepalived, but, all
cluster-like softwares dealing with aliases in any existing interface,
managed or not by systemd, I have tested the same test case in a
pacemaker based cluster, with 3 nodes, having 1 virtual IP + a lighttpd
instance
The binutils-2_33-branch branch has been updated by Alan Modra
:
https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;h=a11b3493ca2d5aabdc218197b92026098d7e2f57
commit a11b3493ca2d5aabdc218197b92026098d7e2f57
Author: Alan Modra
Date: Mon Sep 23 08:53:07 2019 +0930
PR25018, readelf
Also, startlingly, I seem to have thousands of ipv6 addresses assigned
to enp0s8:
ip addr
3: enp0s8: mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether 08:00:27:47:xx:xx brd ff:ff:ff:ff:ff:ff
inet 10.169.110.168/21 brd 10.169.111.255 scope global dynamic
noprefixroute
** Tags added: id-5d6fba2cac409d12ddb60a25
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1845245
Title:
Behaviour change in systemd 243 breaks netplan.io ethernets
** Tags added: id-5d6fba2cac409d12ddb60a25
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1845314
Title:
udisks2 fails to install in a container with systemd 243
Status
Hi, I'm hitting this quite consistently on Pop!_OS 19.04 in Virtualbox
(Windows 10 host) on Lenovo T460.
Essentially, the CPU usage goes up to 100% for avahi-daemon, and the
strace shows it stuck in a loop, reading/writing to a named pipe, like
so:
poll([{fd=6, events=POLLIN}, {fd=14,
** Tags added: id-5d8a536c3eb49122f14145aa
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1832050
Title:
chrony autopkgtest "time-sources-from-dhcp-servers" fails
Hey BTW, I suspect this 'error' is due to upstream commit
97afc0351a96e0daa83964df33937967c75c644f which changed udevadm's
behavior; previously it silently ignored errors writing to
/sys/devices/*/uevent files, but now it logs error and returns error
code. So this is likely not *actually* a new
Oh, and a better fix would be not calling udevadm when 'systemd-detect-
virt --private-users' is true. It's a bit annoying that every udevadm
caller would need to know that, however.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
And yeah, ignoring the udevadm return value with ||: could be one way to
avoid the error.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1845314
Title:
udisks2 fails to
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 1845317
and then change the status of the bug to 'Confirmed'.
If, due to the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
3. How we could fix it?
Well, given the data I posted above, my *guess* is that we could safely
ignore the udevadm non-zero exit status in the udisks2 postinst script
with something like this:
if [ "$1" = "configure" ]; then
# we ship udev rules, so trigger an update
udevadm trigger
2. Why this is happening?
First of all, the udisks2 installation fails because the postinst script
fails. Inspecting the postinst script of udisks2, we can see these
lines:
if [ "$1" = "configure" ]; then
# we ship udev rules, so trigger an update
udevadm trigger --subsystem-match=block
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
Hi, I'm the santa_ above, so, to explain the full picture I'm going to
write 3 separate messages below trying to answer these 3 questions:
1. How to reproduce the issue?
2. Why this is happening?
3. How we could fix it?
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- Add new pci-id's for CML-S
+ Add new pci-id's for CML-S, ICL
** Description changed:
[Impact]
Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL,
CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new
pci-id's that need
1. How to reproduce the issue?
Very easy, you just have to create an eoan LXD container, add the ppa with
systemd 243:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3801/+packages
and then just do "apt dist-upgrade" to upgrate to systemd 243 and "apt
install udisks2", the udisks2
Public bug reported:
[Impact]
Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, CFL,
WHL). There are new CML-S desktop cpu's on the way, and they add three new
pci-id's that need to be added across the stack in order to use the GPU
properly.
[Test case]
The proper way
FYI: We have identified a behavioral change in libvirt, but while I'll address
that it was not the reason for the issue reported here.
Upstream discussion on the systemd issue continues ...
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You
Public bug reported:
santa_ | rbalint: hey while systemd 243 was available in eoan I still
got one of "my" issues (udisks2 fails to install in a container)
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Description changed:
+ [Impact]
+ Warning messages when using suffixes in intervals such as d for day
+
+ /usr/lib/apt/apt.systemd.daily: 87: [: Illegal number: 20h
+
+ [Test case]
+ Create 99local in apt.conf.d with
+ APT::Periodic::Update-Package-Lists "1d";
+ and run
Well, it is failing with 241, too, so it is not a regression.
Will triage it later.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1845201
Title:
systemd root-unittests
Failing with 241-7ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1845201
Title:
systemd root-unittests autopkgtest is failing on armhf
Status in systemd package
This still looks like an issue in Ubuntu 18.04 LTS. At least on systems
that was upgraded from 14.04 release. I will disable systemd-resolved
and revert to good old resolv.conf but what is the actual recommended
workaround while the fix is not released?
--
You received this bug notification
thanks a ton for the quick fixes!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1845190
Title:
binutils nm wrong output format breaks i386 nm work
Status in binutils:
See above, I ran several thousand reboot tests on a lot of Basic_A3
instances, ranging from 50, 250 to 500 reboots. Only one failed. So
this is *really* hard to reproduce.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
IP addr Mac AddrKernel Reboots
13.64.67.18600:0d:3a:3a:dd:04 5.0.0-1016-azure50
104.42.152.115 00:0d:3a:35:b1:e6 5.0.0-1016-azure50
65.52.121.205 00:0d:3a:3b:0f:52 5.0.0-1016-azure50
13.88.28.42 00:0d:3a:3b:c7:da
On 2019-09-25 03:13, Bug Watch Updater wrote:
> ** Changed in: ibus
> Status: New => Fix Released
There is no upstream fix yet. The upstream issue was closed by mistake.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1845294
Title:
package libpython2.7-stdlib:i386 2.7.12-1ubuntu0~16.04.8 failed to
Public bug reported:
once I've switched on the PC there was a notice: segnalazione crash. Si è
verificato un problema durante l'installazione del software.
Pacchetto: libpython2.7-stdlib:i386 2.7.12-1ubuntu0-16.04.8
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package:
** Summary changed:
- [FFe] Ubiquity with zsys install option
+ [FFe] Ubiquity with zfs install option
** Description changed:
Part of the 19.10 feature announcement is zfs experimental support in
the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
65 matches
Mail list logo
