** 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
I have retry the test, it is failing on 'systemd-fsckd'.
Let's see.
--
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 '/dev/console': open
** Description changed:
[Impact]
At the moment rsyslog cannot have access /dev/console due to a mismatch
permission/ownership between '/dev/console' and the Privilege Drop User
and Group 'syslog' in rsyslog.
[Test Case]
- * Deploy focal/20.04LTS
+ * Deploy focal/20.04LTS
Thanks @sil2100 for your pre-approval comment.
I have uploaded it into focal upload queue.
It is now waiting for the official SRU team approval in order to start building
in focal-proposed for the verification test phase.
- Eric
--
You received this bug notification because you are a member
** Description changed:
+ [Impact]
+
+ At the moment rsyslog cannot have access /dev/console due to a mismatch
+ permission/ownership between '/dev/console' and the Privilege Drop User
+ and Group 'syslog' in rsyslog.
+
+ [Test Case]
+
+ * Deploy focal/20.04LTS
+ * Install rsyslog
+ *
** Changed in: rsyslog (Ubuntu Focal)
Status: New => In Progress
** Changed in: rsyslog (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: rsyslog (Ubuntu Focal)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification be
One easy fix would possibly be the following:
# debian/rsyslog.postinst
case "$1" in
configure)
adduser --system --group --no-create-home --quiet syslog || true
adduser syslog adm || true
+adduser syslog tty || true
I have tested it in a PPA, and it works just fine:
https://wiki.debian.org/SystemGroups
tty: TTY devices are owned by this group. This is used by write and wall
to enable them to write to other people's TTYs, but it is not intended
to be used directly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
One easy fix would possibly be the following:
# debian/rsyslog.postinst
case "$1" in
configure)
adduser --system --group --no-create-home --quiet syslog || true
adduser syslog adm || true
+adduser syslog tty || true
I'll give it a try and test.
--
You received this
Public bug reported:
The Privilege Drop options ($PrivDrop*) in focal's rsyslog both point to
'syslog' for the user and group, and don't match the
ownership/permission of '/dev/console' generating the following:
syslog:Aug 3 15:16:58 rsyslogd: file '/dev/console': open
error: Permission denied
** Bug watch added: Debian Bug tracker #966621
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966621
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966621
Importance: Unknown
Status: Unknown
--
You received this bug notification
[sts-sponsor]
Sponsored in active development release (groovy)
** Changed in: apport (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
[sts-sponsor]
@dgadomski
I don't think you can add a runtime dependency from universe to a
package found in main
apport-gtk | 2.20.11-0ubuntu42 | groovy
konsole | 4:20.04.3-0ubuntu1 | groovy/universe
This would most likely require an MIR for konsole first.
** Changed in: systemd (Ubuntu Xenial)
Status: In Progress => Won't Fix
** Changed in: systemd (Ubuntu Xenial)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
I tested with debian buster and I wasn't able to reproduce (w/o quiet
parameter)
I'm not yet too sure if it's a pure initramfs-tools or something
introduced by a package hooks.
I first thought that plymouth could have beeb a potential candidate, but
I disabled it and even purge it and problem
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Guilherme
** Summary changed:
- kernel get stuck at boot if specified 'console=ttyS* ' doesn't exist.
+ machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
** Description changed:
[Impact]
In Xenial/16.04LTS, one can't generate network interface name from
"phys_port_name" attribute.
"phys_port_name" indicates the interface physical port name within the
NIC.
[Test Case]
Check that udev (systemd-udevd) provides the phys_port_name
** Description changed:
[Impact]
In Xenial/16.04LTS, one can't generate network interface name from
"phys_port_name" attribute.
"phys_port_name" indicates the interface physical port name within the
NIC.
[Test Case]
Check that udev (systemd-udevd) provides the phys_port_name
** Changed in: json-c (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to json-c in Ubuntu.
https://bugs.launchpad.net/bugs/1878723
Title:
Kernel panic when used with upstart
** Description changed:
[Impact]
In Xenial/16.04LTS, one can't generate network interface name from
"phys_port_name" attribute.
"phys_port_name" indicates the interface physical port name within the
NIC.
[Test Case]
Check that udev (systemd-udevd) provides the phys_port_name
** Description changed:
[Impact]
In Xenial/16.04LTS, one can't generate network interface name from
"phys_port_name" attribute.
"phys_port_name" indicates the interface physical port name within the
NIC.
[Test Case]
Check that udev (systemd-udevd) provides the phys_port_name
https://git.centos.org/rpms/systemd/c/83b94d10951d79445f7975bff835a88261c11a4e?branch=83b94d10951d79445f7975bff835a88261c11a4e
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Centos had to revert the patch in their systemd package via:
commit 83b94d10951d79445f7975bff835a88261c11a4e
SOURCES/0499-Revert-udev-net_id-add-support-for-phys_port_name-at.patch
They workaround (differing from upstream) the regression installing script and
udev rule to add phys_port_name
Right, @ddstreet it's a very good point to validate/verify.
Definitely worth looking at that aspect pre-SRU.
Bionic and late has the fix since release time ... meaning that patch
has never been introduced via SRU yet.
- Eric
--
You received this bug notification because you are a member of
** Description changed:
+ [Impact]
+ In Xenial/16.04LTS, one can't generate network interface name from
"phys_port_name" attribute.
+
+ "phys_port_name" indicates the interface physical port name within the
+ NIC.
+
+ [Test Case]
+
+ Check that udev (systemd-udevd) provides the phys_port_name
** Description changed:
It has been brought to my attention that systemd in Xenial/16.04LTS
doesn't have support for phys_port_name[0] attribute.
The support has been first introduced in systemd version "232" via:
be --contains db24a9044ee1
v4.1-rc1
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: systemd (Ubuntu Xenial)
Importance: Medium
Assignee: Eric Desrochers (slashd)
Status: In Progress
** Tags: sts
** Also affects: systemd (Ub
** Tags added: sosreport sts
--
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/1870585
Title:
Not cleaning /var/tmp by default
Status in systemd package in Ubuntu:
New
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1863414
Title:
Have many "/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line
Sponsored by dgadomski. Unsubscribing sts-sponsor team.
Thanks for your contribution Seyeong.
Thanks for the sponsoring Dariusz.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1758529
Title:
landscape-package-changer crashed with
** Changed in: network-manager (Ubuntu Bionic)
Status: Confirmed => In Progress
** Tags added: sts-sponsor-dgadomski
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
@xtrusia,
Is this ready for sponsorship ?
I'll have a look when ready.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1794478
Title:
Automatic ipv4 not
util-linux uploaded in focal.
Thanks Mauricio !
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862846
Title:
Crash and failure installing focal
Status in subiquity:
The sosreport juju plugin refactoring has been simplified.
For now, we don't expect the juju plugin to drop privileges any time
soon.
Thanks !
** Changed in: util-linux (Ubuntu Xenial)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of
** Description changed:
+
+ [Impact]
+ [Test Case]
+ [Potential Regression]
+
+ [Other informations]
+
+ * Upstream bug[0] and fix[1]:
+
+ https://bugzilla.redhat.com/show_bug.cgi?id=1575944
+ https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35
+
+ * Only affectinb
Thanks for reporting the outcome of your test.
We will start the SRU process in order to update network-manager package
next week.
Regards,
Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
This look like a similar issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1575944
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35
A test package (including the above fix) is available on my PPA:
sudo add-apt-repository ppa:slashd/lp1794478
sudo apt-get update
You can find it here:
https://www.ubuntuupdates.org/package/core/bionic/universe/updates/systemd?id=1401429=2
-
Version: 237-3ubuntu10.23 2019-06-21 00:06:25 UTC
systemd (237-3ubuntu10.23) bionic; urgency=medium
* d/p/resolved-do-not-hit-CNAME-in-NODATA.patch:
- fix stub
sed
** 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/1822416
Title:
resol
** Changed in: systemd (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Tags added: st
** Tags removed: st
** Tags added: sts
--
You received this bug notification because you are a
Seems like Disco and late already have the requested fix.
$ git describe --contains 3740146a4cbd99883af79e375ee4836206dcea4e
v240
$ rmadison systemd
systemd | 204-5ubuntu20| trusty | source
systemd | 204-5ubuntu20.31 | trusty-security | source, amd64, arm64, armhf,
i386, powerpc,
I reproduced the behaviour using 5.5 upstream kernel by:
1) Mounting a loop device
2) Setup frace for all loop function for capture purposes
3) Then umount the loop device
trace_pipe reveal the following:
"umount-1850 [000] 471.727511: loop_release_xfer <-__loop_clr_fd"
As cascardo
I reproduced the behaviour using 5.5 upstream kernel by:
1) Mounting a loop device
2) Setup frace for all loop function for capture purposes
3) Then umount the loop device
trace_pipe reveal the following:
"umount-1850 [000] 471.727511: loop_release_xfer <-__loop_clr_fd"
As cascardo
Sponsored in focal.
* Fix approved upstream
* Bug reported and patch submitted to upstream Debian.
Please keep an eye on the excuses page for util-linux.
- Eric
** Tags removed: sts-sponsor-slashd-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Tags added: sts-sponsor-slashd-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1858802
Title:
libblkid: no bcache UUID due to ambivalent detection of bcache
so 2 things come to my mind right now
Does the kernel (loop driver) do the right thing by not clear/reset the
loop device' stats after the umount/detached operation ?
and/or
Does parted need to be smarter and not only based is detection on stat()
to assume if its a legit device or not to be
so 2 things come to my mind right now
Does the kernel (loop driver) do the right thing by not clear/reset the
loop device' stats after the umount/detached operation ?
and/or
Does parted need to smarter and not only based is detection only on
stat() ?
Let's circle back on Jan 2020.
** Also
1 - 100 of 721 matches
Mail list logo
