> I will attempt to upstream this fix to klibc, but I believe the change
to Bionic should happen in parallel/independently since the upstream
patch will not make its way back to Bionic (which is stuck at 2.0.4, as
mentioned above).
Yes that is the plan to SRU the fix on top of what is currently
And let them judge if it's worth an upstream adoption or not as a first
exercise. Then we can take a decision for Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
I still believe, it would be a good practice to submit the patch to
upstream.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour
And let them judge if it's worth the adoption or not as a first
exercise. Then we can take a decision for Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Khaled El Mously (kmously),
Thanks for the update. I'll review this and talk with sil2100, an SRU
verification member.
Could you please help to fill the SRU template in the description above.
Extra documentations can be found here:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
** Description changed:
+ ** SRU TEMPLATE DRAFT **
+
+ [Impact]
+
+
+ [Test Plan]
+
+
+ [Where problems could occur]
+
+
+ [Other Info]
+
+
+ [Original Description]
+
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c,
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in
@Khaled El Mously (kmously)
I don't see this piece of code in the klibc upstream project[0]
Is this something you only reproduce in Bionic/18.04LTS ?
Since your fix is not found anywhere else, I would be tempted to assume that it
could be affecting other releases of Ubuntu and possibly more.
[Verification Focal]
This has been brought to my attention by an impacted user:
"
I was able to apply the fixed procps package from the focal-proposed repo on
servers in a test cluster. The fix resolved the issue with free -V and the
related DataStax OpsCenter error.
Thanks
"
- Eric
** Tags
[autopkg regression]
All tests are now fine. They needed a second retry.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1917148
Title:
ps version is UNKNOWN in
I totally get your concern. In the same time, other procps pkkg in
Ubuntu groovy, ... uses the same approach.
But I leave you to decide what is best for this particular bug.
Let us know.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Tags removed: sts-sponsors-slashd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1917148
Title:
ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
Status in procps
[sts-sponsors]
Sponsored in Focal upload queue, now waiting for SRU verification team
approval.
Thanks for your contribution, Kellen.
Test case validation (before upload):
root@procpsf:/tmp# pgrep --version
pgrep from procps-ng 3.3.16
root@procpsf:/tmp# ps --version
ps from procps-ng
** Description changed:
[Impact]
* Breakage of tools expecting the version number or the number to
substantially match the Debian package version.
* May confuse users expecting the version to substantially match the Debian
package version.
* Restores behavior to that provided in
[sts-sponsors]
Debian uses autopkgtest for 'version' w/ restriction superficial as
follows:
Tests: version
Restrictions: superficial
https://people.debian.org/~eriberto/README.package-tests.html
superficial
The test does not provide significant test coverage, so if it passes, that does
not
** Tags added: sts-sponsors-slashd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1917148
Title:
ps version is UNKNOWN in procps 2:3.3.16-1ubuntu2
Status in procps
** Tags added: seg sts
** Also affects: procps (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: procps (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: procps (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects:
I'll be reviewing the change with my colleague Kellen.
In the meanwhile ...
What is the concern/impact behind not having the version available in ps ?
(Outside it should output/report it) ?
The version can be found in the package version (dpkg -l procps)
Is it for integrity purposes in order
systemd reaches day 7 wo/ autopkgtest failure nor negative
outcome/feedbacks.
I have asked 'sil2100' to promote the package into bionic-updates.
Stay tuned ...
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Thanks Maanus for all the testing. Much appreciated.
I'll take care of the rest in a couple of days with Lukasz.
Package needs to stay in proposed for a couple more days (minimum 7 days)
- Eric
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received
Hi Maanus,
Would you mind perform the 'test cases' now against the systemd's
bionic-proposed package ? And report any outcome.
This is one of the last steps for Lukasz to approve the proposed package
after the baking minimum aging period (7 days) in verification phase.
- Eric
--
You received
Uploaded into bionic upload queue, now waiting for SRU approval.
- Eric
** Changed in: systemd (Ubuntu Bionic)
Status: Incomplete => In Progress
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification b
Good catch Dan.
Maanus could you repeat the testing with what Dan brought up ?
--
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/1815101
Title:
[master] Restarting
Thanks @Maanus.
So the outcome is positive here then.
- Eric
--
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/1815101
Title:
[master] Restarting systemd-networkd breaks
@maanus, That is a first iteration.
sudo add-apt-repository ppa:slashd/keepconfiguration
sudo apt-get update
Let me know the outcome.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Any volunteer to test a package in Bionic in the attempt to support
keepconfiguration ?
--
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/1815101
Title:
[master] Restarting
I think 'backports' would have been a great place to have this behavior
change in Bionic while keep the current one in -updates.
I just came across an email about 'backports' about to die (from
rbasak). Let's see what is the outcome and rely on the flock()
alternative for now.
I'll monitor the
I'm on the same page.
Maybe we should leave the package in -update as is and go with the
flock() alternative.
OR evaluate if, let's say, the Focal's iptables could be backported
(if feasible) in bionic-backports.
That way, one who wants the 'wait' and 'wait-interval' to be available
could
New testpackage: iptables - 1.6.1-2ubuntu2+testpkg20210706b8
Note: If that works as expected for Andreas. The only things that needed
would be to update the manpage, which I didn't do on this current test
pkg.
--
You received this bug notification because you are a member of Ubuntu
Touch
Both 'iptables' and 'ip*tables-restores' sleep and wait until the lock
is released if no 'wait' option. If 'wait' option is set, it wait for
the amount of time instructed and stop waiting.
I think the printed message make more sense now :
# time cat /etc/rules.v4 | iptables-restore -c
Another
I'll work to re-arrange the fprintf if 'wait' option is used or not and
see the outcome of it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
Version in comment #12 is "iptables - 1.6.1-2ubuntu2+testpkg20210706b4"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
iptables-restore is missing -w
I have a new test pkg:
This pkg keeps the same behavior for 'iptables'
# Hold the lock:
flock /run/xtables.lock sleep 36000
# It holds and wait until flock() finishes or get killed, and then get executed.
iptables -L
# With 'wait' option, it waits until the wait time is ended:
time iptables
What about "iptables - 1.6.1-2ubuntu2+testpkg20210629b3" ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
iptables-restore is missing -w option
Status in
Thanks Andreas. I'll be working on a minimalistic patch set (if
feasible)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
iptables-restore is missing -w
Thanks Andreas. I'll be working on a minimalistic patch set
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
iptables-restore is missing -w option
Status
Look like a potential patchset to backport without having to bump
version in stable release:
6e2e169eb iptables: remove duplicated argument parsing code
24f81746 xshared: do not lock again and again if "-w" option is not specified
72bb3dbf0 xshared: using the blocking file lock request when we
Look like a potential patchset to backport without having to bump
version in stable release:
I'll test it, and then will alk w/ the SRU verification team to see if
eligible for SRU.
commit 6e2e169eb66b63d2991e1c7ada931e3cdb0ced32
Author: Lorenzo Colitti
Date: Thu Mar 16 16:55:01 2017 +0900
Look like a potential patchset to backport without having to bump
version in stable release:
21ba5b38 ip{,6}tables-restore: Don't accept wait-interval without wait
d89dc47a iptables-restore/save: exit when given an unknown option
65801d02 iptables-restore.8: document -w/-W options
999eaa24
** Description changed:
[Impact]
Here's what has been brought to my attention by a UA customer:
* Release:
Xenial/16.04LTS
* Openssh version:
7.2p2-4ubuntu2.10
* Fuzzer tool used:
https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html
debdiff to go over the ESM process by security team.
Thanks
- Eric
** Patch added: "xenial_lp1930286.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1930286/+attachment/5502934/+files/xenial_lp1930286.debdiff
--
You received this bug notification because you are a member
** Changed in: openssh (Ubuntu Xenial)
Status: New => In Progress
** Description changed:
+ [Impact]
Here's what has been brought to my attention by a UA customer:
* Release:
Xenial/16.04LTS
* Openssh version:
7.2p2-4ubuntu2.10
* Fuzzer tool used:
UA customer test pkg outcome:
"
We ran the Defensics test suite before and after installing the test packages.
We could observe two core dumps before the test package installation.
But after test package installation, core dumps were not generated.
Can you provide this package as the fix?
"
This
Hello Seth,
So far no production impact has been reported, for now it is only
reproducible using that particular fuzzer on xenial's openssh version.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
I have produced a test pkg including the potential fix candidate above
for the impacted UA customer to test in their lab.
Unfortunately, I have no access to a reproducer since this fuzzer is
proprietary and need to be purchased.
Meaning, the testing will rely on UA customer end.
- Eric
**
Potential fix candidate:
https://github.com/openssh/openssh-portable/commit/2adbe1e63bc313d03e8e84e652cc623af8ebb163
** Tags added: seg sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Public bug reported:
I'm reporting this bug to keep track of it, as of today I'm still
collecting informations.
Here's what I have gathered so far:
Release: Xenial/16.04LTS
Openssh version :7.2p2-4ubuntu2.10
Fuzzer tool used:
** Changed in: linux (Ubuntu)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
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/1856871
Title:
i/o error if n
** Description changed:
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot
reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
** Changed in: systemd (Ubuntu Groovy)
Assignee: (unassigned) => Ioanna Alifieraki (joalif)
--
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/1911187
Title:
scheduled
** Tags added: sts-sponsors-ddstreet
** Changed in: systemd (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: systemd (Ubuntu Groovy)
Status: Confirmed => In Progress
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in:
The upstream proposal fix that mfo and I worked on has been applied:
https://patchwork.kernel.org/project/linux-
block/patch/20210222154123.61797-1-...@canonical.com/
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
d/rules:
91 CONFFLAGS_deb = \
92 -Dselinux=true \
93 -Dhwdb=true \
=> 94 -Dsysusers=true \
Would it make sense to turn this off ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
** Bug watch added: Debian Bug tracker #982976
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982976
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982976
Importance: Unknown
Status: Unknown
--
You received this bug notification
Right, but it doesn't seem right to have it set by default to "/".
--
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/1915936
Title:
systemd-coredump user is created by
** Summary changed:
- systemd-coredump user is create by something other than its derived systemd
packages
+ systemd-coredump user is created by something other than its derived systemd
packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Home Directory¶
The home directory for a new system user. If omitted, defaults to the root
directory.
Only applies to lines of type u and should otherwise be left unset (or
"-"). It is recommended to omit this, unless software strictly requires
a home directory to be set.
systemd-sysusers only
https://www.freedesktop.org/software/systemd/man/sysusers.d.html#
u
Create a system user and group of the specified name should they not exist yet.
The user's primary group will be set to the group bearing the same name unless
the ID field specifies it. The account will be created disabled, so
sudo /bin/systemd-sysusers --cat-config
# /usr/lib/sysusers.d/systemd.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either
Public bug reported:
systemd-coredump binary package is instructed as follows:
#debian/systemd-coredump.postinst:
adduser --quiet --system --group --no-create-home --home /run/systemd \
--gecos "systemd Core Dumper" systemd-coredump
But one doesn't need this package to be installed to have the
This is fixed in active development release (hirsute):
python-apt (2.1.7) unstable; urgency=medium
* SECURITY UPDATE: various memory and file descriptor leaks (LP: #1899193)
- python/arfile.cc, python/generic.h, python/tag.cc, python/tarfile.cc:
fix file descriptor and memory leaks
@julian, thanks for the quick reply. Will do.
** Changed in: python-apt (Ubuntu)
Status: New => Fix Released
** Description changed:
[Impact]
USN-4668-1 introduced a regression in python-apt when using certain APIs
with a file handle.
[Test case]
# Landscape scenario:
This package is 'native' and I don't want for instance to introduce
'quilt' before talking to the maintainer.
@julian, how do you want to proceed to fix this bug in python-apt ?
- Eric
** Description changed:
[Impact]
USN-4668-1 introduced a regression in python-apt when using certain
** Description changed:
+ [Impact]
+
USN-4668-1 introduced a regression in python-apt when using certain APIs
with a file handle.
+ [Test case]
+
+ # Landscape scenario:
+ 1) On the Landscape server, create a package profile that installs a single
package, 'hello' is enough.
+ 2) On
The current situation of python-apt is somewhat critical as no packages
can be pushed via Landscape to machines at the moment. This is causing
landscape-package-changer to segfault as follows:
[apport-retrace]
Core was generated by `/usr/bin/python3 /usr/bin/landscape-package-changer
--quiet'.
All regression failures, PASSED after a retry. There is no autopkgtest
regression (failures) anymore.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1906627
Title:
I have retried all the FAILED tests.
* postfix/3.3.0-1ubuntu0.3 (amd64) PASSED the 2nd time:
http://autopkgtest.ubuntu.com/packages/p/postfix/bionic/amd64
* kimap/17.12.3-0ubuntu1 (armhf, ppc64el, arm64) are queued and waiting to
retry.
Stay tune ...
- Eric
--
You received this bug
[sts-sponsors]
cyrus-sasl2 has been sponsored in Bionic.
I have already pinged sil2100 for its SRU verification.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
[sts-sponsors]
adcli option #1 has been sponsored in Bionic with the following
nitpicking:
* Changed version from "0.8.2-1ubuntu2.1" to "0.8.2-1ubuntu1.1"
* Changed debian/control to d/control.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Matthew,
I was thinking about possibly to declare some package relationships to
not allow the offending packages' combination to occur, when I came
across the exact same thought from cpaelzer.
I don't know if you notice it, here it goes[0]:
"
One suggestion for the coming related uploads.
Do
Matthew,
I was thinking about possibly to declare some package relationships to
not allow the offending packages' combination to occur, when I came
across the exact same thought from cpaelzer.
I don't know if you notice it, here it goes:
"
One suggestion for the coming related uploads.
Do you
** Changed in: systemd (Ubuntu Bionic)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
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/1815101
Title:
[mas
(I have ping sil2100 internally for him to provide his 2 cents on this
bug.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1865226
Title:
gdm-smartcard pam config needs to
Lukasz (sil2100) can we have your SRU team input on this bug with regard
to Bionic/18.04lTS ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1865226
Title:
gdm-smartcard pam
I unfortunately don't have a smartcard device handy to test/debug/
but if I compare with RHEL which is known to be working...
Redhat has the following configuration "gdm-smarcard" which includes
"smartcard-auth", a symlink pointing to "smartcard-auth-local"
I think we should 'mimic' this (at
# git clone https://gitlab.gnome.org/GNOME/gdm.git
# find . -name "gdm-smartcard*"
./data/pam-arch/gdm-smartcard.pam
./data/pam-redhat/gdm-smartcard.pam
./data/pam-exherbo/gdm-smartcard.pam
./data/pam-lfs/gdm-smartcard.pam
It seems like Ubuntu/Debian will have to start by having a 'compatible'
** Changed in: gdm3 (Ubuntu Groovy)
Importance: Medium => High
** Also affects: pam (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: gdm3 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: pam (Ubuntu Bionic)
Importance: Undecided
I have a first iteration of a package:
It's not a final solution nor a long term solution. It is only made to
determine if its fix the problem before considering an SRU: (Ideally one
would test this package in non-production area)
Adding this PPA to your system
sudo add-apt-repository
The above test package has been made for 'systemd' in bionic ^
--
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/1815101
Title:
[master] Restarting systemd-networkd breaks
[sts-sponsors]
I have sponsored it in bionic.
Thanks for your contribution Heitor
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1895757
Title:
Terminal hangs
** Description changed:
[Impact]
sudo commands can hang when IO logging is enabled
[Description]
When doing cleanup in pty_close(), sudo can leave file descriptors and events
behind that would later cause poll() to wait on a "dead" pty. This can cause
sudo to hang when IO logging
** Changed in: gdm3 (Ubuntu Groovy)
Importance: Low => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1865226
Title:
gdm-smartcard pam config needs to be updated
It has been brought to my attention by a UA customer that they are
suffering from which seems a similar situation:
"
Our only currently working SmartCard access from Linux, over SSSD, to AD, is on
RHEL7.
I was able to get SSH access on Ubuntu 20.04LTS, after adding
"ad_gpo_access_control =
I'll retry the test before we investigate further.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1879980
Title:
Fail to boot with LUKS on top of RAID1 if the
Autopkgtest failure found:
autopkgtest for systemd/246.4-1ubuntu1: amd64: Regression ♻ , arm64:
Pass, armhf: Pass, ppc64el: Pass, s390x: Ignored failure
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
[sts-sponsors]
Sponsored and uploaded into groovy.
Let's now wait until the package lands in groovy-releases before proceeding
with the SRU.
Thanks mfo and gpiccoli for your contributions.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
@gpiccoli,
Can you break down everything this debdiff does per file being modified
in the d/changelog along with the summary you have already provided ?
It would ease for future reference and make the d/changelog more
accurate about the changes.
* d/cryptsetup-initramfs.install:
-
*
I'm having the same stack trace from groovy, when trying to unpack
ii apport 2.20.11-0ubuntu45 all
automatically generate crash reports for debugging
ii apport-symptoms0.23 all
symptom
$ lsb_release -cs
bionic
$ apport-unpack /var/tmp/_usr_bin_.0.crash /tmp/
Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 74, in
pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 270, in
extract_keys
[item for
[sts-sponsor]
Sponsored in Focal/Bionic.
Thanks for your contribution.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1879980
Title:
Fail to boot with LUKS on
[sts-sponsor]
Sponsored in Focal/Bionic.
Thanks for your contribution.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1879987
Title:
machine get stuck at boot
[sts-sponsor]
Sponsored in Bionic.
Thanks for your contribution.
--
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/1820929
Title:
netplan should consider adding more udev
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
@zack
You could wait until the logrotate happen and restart rsyslog or you
could simply do manual restart using 'systemctl restart rsyslog' and
then look in /var/log/syslog.
What triggers the error is at rsyslog startup from what I have notice
during my test.
- Eric
--
You received this bug
@zack
You could wait until the logrotate happen that will then restart rsyslog
itself or you could simply do a manual restart using 'systemctl restart
rsyslog' and then look in /var/log/syslog.
What triggers the error is at rsyslog startup from what I have notice
during my test.
- Eric
--
You
The apport (2.20.11-0ubuntu27.6) security channel build haven't been caught in
that FTBFS situation because it was tested against the former pycodestyle
package:
Get:310 http://ftpmaster.internal/ubuntu focal/universe amd64 pycodestyle all
2.5.0-2 [5092 B]
--
You received this bug
[sts-sponsor note]
Package doesn't build due to new pycodestyle (2.6.0-1~20.04.1) found in
focal-proposed as opposed to its former version (2.5.0-2) that now
detects the following during the test:
Running pycodestyle...
./setup.py:78:33: E741 ambiguous variable name 'l'
[sts-sponsor note]
Package doesn't build due to new pycodestyle (2.6.0-1~20.04.1) found in
focal-proposed as opposed to its former version (2.5.0-2) that now
detects the following during the test:
Running pycodestyle...
./setup.py:78:33: E741 ambiguous variable name 'l'
I have retried the autpkgtest test on ppc64el. It is failing on
'systemd-fsckd'.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1890177
Title:
rsyslogd: file
1 - 100 of 769 matches
Mail list logo
