Public bug reported:
upgrading grub, modifies GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub
if one has makedumpfile installed. the setting from /etc/default/grub.d
/kdump-tools.cfg which imho should not have leaked into
/etd/default/grub.
See screenshot.
Also,
grub-efi-amd64 grub2/linux_cmd
Public bug reported:
RM mandos, useless with gnutls28 3.6.x, as it needs removed OpenPGP
certificates support.
Please remove, as gnutl28 with tlsv1.3 support is more important.
** Affects: mandos (Ubuntu)
Importance: Undecided
Status: Triaged
** Affects: mandos (Debian)
Impor
@jibel
you really should clear all the boot entries, you may be overflowing.
@steve
it is quite easy to give an nvram to the VM, but i think we have a spare
laptop here that can do legacy & uefi, we'll retest this there.
--
You received this bug notification because you are a member of Ubuntu
with persistent uefi vars, it rebooted into uefi system fine.
I'd recommend clearing all of your boot entries
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you
So https://launchpad.net/ubuntu/+source/casper/1.399 this upload should
make things better and drop the user to the plymouth splash more often.
There is a race between casper script and show-splash, as show-splash
command is an ExecStartPost command.
Please confirm if existing machines that used
** Description changed:
+ [Impact]
+
+ * Cannot configure race-free generic-ccw devices to be onlined on boot.
+
+ [Test Case]
+
+ # on a z/VM
+
+ $ sudo chzdev -d 0.0.000c 0.0.000d 0.0.000e
+ $ sudo chzdev -e 0.0.000c 0.0.000d 0.0.000e
+ $ sudo update-initramfs -u
+ $ sudo reboot
+ $ lszdev
Yes, but older distros were dual signed with that key. So it should be
still shipped.
** Changed in: ubuntu-keyring (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/bu
*** This bug is a security vulnerability ***
Public security bug reported:
[Impact]
* For LTS releases to be able to bootstrap dual and single signed
future releases, and validate all signatures, 2018 archive signing key
should be SRUed back
* Also build process has improved documentation and
So we have zeroed these out. And we have now done bios-mbr install, and
then side-by-side install in uefi mode with mok util.
1) mok util did not register a `correct` esp boot path, it pointed at
\efi\boot\mmx64.efi but that is a wrong path, as it should be at
\efi\ubuntu\mmx64.efi.
2) the b
So i don't think efibootmgr generates "right" entries for ESP on
extended mbr partition.
or maybe it should learn to generate HD(2,MBR)/HD(1,MBR)
And/or maybe we shouldn't put ESP on the extended partition if we can /
have primary partitions available.
** Also affects: efibootmgr (Ubuntu
and when it doesn't like HD(5,MBR...) entry and has no other entries it
tries to "autogenerate" the entry and injects it into bootorder and
then boot loops and then the entries pile up
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Also affects: partman-auto (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796260
Title:
UEFI install onto an MBR disk, with a pre-existing os/
Public bug reported:
[SRU] nodejs should use openssl1.0 in testing as well
Previous SRU in #1779863 reverted to using openssl1.0 for the runtime,
but it should also use openssl1.0 in test.
This allows to execute more test cases and is future-proof against using
tls1.3 capable openssl 1.1.1 by ac
Public bug reported:
Provide curtin-requirements and server-ship-live seeds
and make cdimage use them for server live images.
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: ubuntu-meta (Ubuntu)
Assignee: (unassigned) => Adam Conrad (adconrad)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798457
Title:
Provide curtin-requirements and server-ship-liv
the deb can be started as root, be previously it would work as non-root
too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798996
Title:
Cannot use it at all...
To manage notifications about this
Public bug reported:
$ gnome-system-monitor
cannot perform readlinkat() on the mount namespace file descriptor of the init
process: Permission denied
And it does not start at all.
** Affects: gnome-system-monitor (Ubuntu)
Importance: Critical
Status: Confirmed
** Tags: regressi
looks like .deb is bad too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798996
Title:
Cannot use it at all...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
** Also affects: s390-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: s390-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
** Description changed:
- Description: only when trying to change some attributes chzdev fails because
it cant find modprobe under Ubuntu 18.04
-
- root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5
- sh: 1: /usr/sbin/modprobe: not found
-
** Changed in: s390-tools (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: s390-tools (Ubuntu Xenial)
Status: Fix Committed => In Progress
** Changed in: s390-tools (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a
Also reading above comments, did we verify that Bionic is correctly
synchronized, and needs no workaround? It would be nice to reliably
confirm that these things operate race-free in bionic and up, and then
mark this bug to affect only xenial and below.
--
You received this bug notification becau
Given that python2 is effectively EOL soon, and python3 has been
available since forever... the switch must happen. Including stable
releases of kernel, imho.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Description changed:
+ [Impact]
+
+ * Valgrind is unable to execute certain binaries, or executes them
+ incorrectly on ppc64el platform in bionic.
+
+ [Test Case]
+
+ * Compile the following test cases, they should execute correctly
+ normally and under valgrind; without illegal opcodes a
root@subtle-cobra:~# dpkg-query -W systemd
systemd 229-4ubuntu21.4
root@subtle-cobra:~# systemctl mask systemd-logind
Created symlink from /etc/systemd/system/systemd-logind.service to /dev/null.
root@subtle-cobra:~# systemctl stop systemd-logind
root@subtle-cobra:~# shutdown +1
Failed to set wall
No journald watchdog kills yet for the xenial SRU.
https://errors.ubuntu.com/?release=Ubuntu%2016.04&package=systemd&period=month&version=229-4ubuntu21.5
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received thi
Public bug reported:
mount options for /run should be the same as initramfs tools
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu Bionic)
Importance:
H... not sure if /run should be limited to 10%, or if runtime
journald should be limited to 1%.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799251
Title:
mount options for /run should be the
** Also affects: systemd (Ubuntu Dd-series)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Description changed:
- Just instal
Tested xenial live session with stock systemd/udev and upgraded one from
proposed. My dell laptop is not affected by this issue. But at least
rfkill keys still work for me with both old and new systemd/udevd and
there are no error messages in dmesg.
** Tags removed: verification-needed verificatio
this should have had ubuntu task added. Has this been verified yet?
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Xenial)
Status
To launch the deb I use $ /usr/bin/gnome-system-monitor, from a gnome-
terminal.
After a reboot, deb works, snap doesn't.
List of interfaces http://paste.ubuntu.com/p/qxcMzGY8PF/
I do get denies http://paste.ubuntu.com/p/cJhj7rCvZB/
Is my system somehow misconfigured / not stock? =(
--
Yo
$ snap version
snap2.35.5+18.10
snapd 2.35.5+18.10
series 16
ubuntu 18.10
kernel 4.18.0-10-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798996
Title:
cannot perform readlinkat() o
@racb
unknown is a placeholder, which is now assigned to wlan. Without unknown, there
would be debugging error kernel messages `unknown key pressed`. So previously
we knew the physical key exists and is pressable, but dind't know what it
should do, but now we do know what it does.
--
You recei
Either this change will make the rfkill button work (good), or not
(current behaviour). Given the code paths, validating similar SKUs for
non-regression is a good enough confidence level that this change
doesn't regress other/unrelated machines. It's a low risk to accept this
change as is, because
Public bug reported:
python3 from python3-defaults is 3.6.5-3ubuntu1
python3-lib2to3 from python3-stdlib-extensions Depends: python3 (>=
3.6.6-1~)
Either python3-stdlib-extensions dep should be lowered, or
python3-defaults should be rebuilt.
** Affects: python3-defaults (Ubuntu)
Importance
@Chat Smith, so are the test results good? Are you going to "change the
tag from verification-needed-bionic to verification-done-bionic" as is
required to release this sru?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
@Chat Smith, so are the test results good? Are you going to "change the
tag from verification-needed-bionic to verification-done-bionic" as is
required to release this sru?
And ditto the xenial tags.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
nodejs autopkgtests now pass, with the extra enabled tests also passing.
there are minimal amount of node packages "regressions" in reverse deps
triggered, which do not show any grave problems with interpreter itself
and are good to skiptest/release this sru, as was done with nodejs
uploads during
** Changed in: friendly-recovery (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799839
Title:
not possible to use "Repair broken packages"
To manage notif
** Changed in: friendly-recovery (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799839
Title:
not possible to use "Repair broken packages"
To manage notif
Upon upgrading to 1.325.1 on trusty, ubuntu-minimal pulled in ubuntu-
advantage-tools which got installed and ubuntu-advantage command became
present and operational.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Upon upgrading to 1.361.2 on xenial, ubuntu-minimal pulled in ubuntu-
advantage-tools which got installed and ubuntu-advantage command became
present and operational.
** Tags removed: verification-needed verification-needed-trusty
verification-needed-xenial
** Tags added: verification-done verifi
Reproduced the issue with valgrind 1:3.13.0-2ubuntu2, two core dumps and
short timebase output (instead of long one when executed not under
valgrind).
Upgrading to 1:3.13.0-2ubuntu2.1 first and third test case now pass.
Thus it is an improvement.
The following test case is still generating Illega
root group is irrelevant here, and should not be used to enforce ACLs.
On Ubuntu, root user is disabled by default. Instead, regular user
accounts are treated as admin accounts if they have the permission to
`sudo` into root. This is done, by default, by adding user accounts to
`sudo` group. This
It appears that it was intended to upgrade librados2 to 13.2.1 but that
did not happen during cosmic release cycle, thus it ended up release
with 12.2.4, whilst bionic got 12.2.7 and is about to get 12.2.8.
A bit of a mess.
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1636503 ***
https://bugs.launchpad.net/bugs/1636503
@Tihomir
It has been fix released in all systemd-based LTS releases have you
retested this with uptodate friendly-recovery?
--
You received this bug notification because you are a member of Ubuntu
Bug
please retest with 229-4ubuntu21.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636503
Title:
recovery mode gets borked after some time out
To manage notifications about this bug go to:
https://
bah
** Also affects: friendly-recovery (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
** Changed in: friendly-recovery (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a mem
nothing to do with systemd, purely a friendly-recovery induced issue
which should have been fixed across all stable releases now. Please
retest, if this is still a problem for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Public bug reported:
open-iscsi should not leave around the stamp file if no connections were
made
open-iscsi finalrd hook is sensitive to /run/initramfs/open-iscsi.interface as
an indicator that rootfs might have been an iscsi mount, and thus logout needs
to happen inside finalrd.
However, i
Hi,
On Tue, 30 Oct 2018 at 20:31, Clemens Fuchslocher
wrote:
>
> Are there any workarounds for Ubuntu 16.04?
By default, networkd is not used on 16.04; unless one manually opted
into it, or uses particular SKUs/images that choose to use networkd by
default (e.g. Core images, and some cloud image
I expect /bin/true to use to heap. As it should be effectively `int
main(){return 0;}`.
Valgrind in general does work, with heap allocating apps.
I'm not sure yet what's up with xvnegsp. As i don't see anything
explicit to either fix it, or break it, or otherwise missing to support
it.
--
You r
I did retest of the xvnegsp test case.
It's broken in bionic, bionic-proposed, cosmic, and disco.
Disco-proposed has updated valgrind, but it FTBFS.
So to answer robbies question - no, this SRU was never meant to fix the
second testcase as that is still broken everywhere. But this SRU did
meant to
sufficiently large swapfile should be enough, as systemd has support to
hibernate to a file offset.
However, none-the-less, I did not manage to resume off that myself yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
There is an autopkgtest now, is it sufficient?
** Changed in: asterisk (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677747
Title:
Missing dep8 tests
To
On cosmic, after fresh install of asterisk, there are no undefined
symbols. Some modules failed to load due to lack of configuration files.
But otherwise there are no underlinked modules it seems.
** Changed in: asterisk (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Looking at
https://www.boost.org/doc/libs/1_68_0/libs/context/doc/html/context/architectures.html
I still do not see boost-context support for s390x.
Has there been any progress w.r.t. to this in the toolchain team at IBM?
--
You received this bug notification because you are a member of Ubuntu
** Also affects: s390-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794346
Title:
check and fix zkey required kernel modules locations in
imitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu Xenial)
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/1795658
Title:
xenial systemd reports 'inacti
** Changed in: s390-tools (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794346
Title:
check and fix zkey required kernel modules locations in debs, udebs,
** Changed in: s390-tools (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794290
Title:
zkey requires a new system group
To manage notifications about this
Joseph Salisbury (jsalisbury) why did you move it from linux src to
autopkgtest src?
the unpacked src tree is there and it linux kernel source package that
needs fixing!
Specifically the code that is cloned from and executed by debian/tests/*
in the src:linux
** Also affects: linux (Ubuntu)
I
Public bug reported:
python-cryptography fails tests on arm64 with python3.7
See
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-cosmic/cosmic/arm64/p/python-
cryptography/20181002_184625_d53df@/log.gz
** Affects: python-cryptography (Ubuntu
* Temporarily disable ZFS tests on s390x due to conflict between
zfsutils-linux and s390-tools (LP: #1788314)
however bionic was never affected, and cosmic has been long fixed
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-failed verification-f
** Changed in: unity-api (Ubuntu)
Status: Confirmed => Triaged
** Changed in: unity-api (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/1795635
Title:
Should hopefully land today... here be dragons
** Tags removed: block-proposed needs-debian-merge
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793092
Title:
[FFe] openssl 1.1.1
To manage notific
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793092
Title:
[FFe] openssl 1.1.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
Public bug reported:
$ autopkgtest-buildvm-ubuntu-cloud --arch i386
put system under load; e.g. pull-lp-source boost1.67; cd boost1.67;
DEB_BUILD_OPTIONS=parallel=12 ./debian/rules build should do it, on an
4core/8hypercore system
$ autopkgtest -s --shell --apt-pocket=proposed --apt-upgrade pyth
** Description changed:
$ autopkgtest-buildvm-ubuntu-cloud --arch i386
put system under load; e.g. pull-lp-source boost1.67; cd boost1.67;
DEB_BUILD_OPTIONS=parallel=12 ./debian/rules build should do it, on an
4core/8hypercore system
$ autopkgtest -s --shell --apt-pocket=proposed -
** Tags removed: block-proposed
** Changed in: openssl (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: python2.7 (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: python3.6 (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification beca
Public bug reported:
libkf5purpose-bin is shipped on Kubuntu live desktop image.
It has 'Recommends: nodejs' i'm not sure if nodejs is really needed or
required here. It would be nice for nodejs to drop out of kubuntu
desktop images, and thus not be `supported'. Maybe it makes sense to
downgrade
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Bug watch added: github.com/systemd/systemd/issues #9079
https://github.com/systemd/systemd/issues/9079
** Also affects: systemd via
https://github.com/systemd/systemd/issues/9079
Importance: Unknown
** No longer affects: systemd (Ubuntu Cosmic)
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776654
Title:
systemd upstream sysusers tests fails
To manage notifications about
Hi,
I recommend you to change your test system.
For example, you can modify /etc/systemd/system.conf and change DefaultTasksMax
there. But that is for the systemd started units...
Note that TasksMax these days can accept % values of kernel configured max
tasks too, meaning i.e. one can set it t
** Changed in: systemd (Ubuntu Cosmic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773148
Title:
/lib/systemd/systemd-
journald:6:fsync:fsync_directory_of_f
How is reboot requested/triggered?
Systemd has 30min timeout on the reboot, so things must timeout and
force-self-reboot after 30min.
** No longer affects: systemd (Ubuntu Bionic)
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
systemd-shim removed from the archive, so cannot be fixed really.
** Changed in: systemd-shim (Ubuntu Bionic)
Status: Confirmed => Won't Fix
** Changed in: systemd-shim (Ubuntu)
Status: Incomplete => Won't Fix
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
** Changed in: klibc (Ubuntu Cosmic)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760106
Title:
FFe: Enable configuring resume offset
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773148
Title:
/lib/systemd/systemd-
journald:6:fsync:fsync_directory_of_fil
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773859
Title:
upgrades to 18.04 fail
To manage notifications about this
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778936
Title:
please re-add Support-system-image-read-only-etc.patch
To manag
** Also affects: cryptsetup (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771858
Title:
/snap/bin not in default PATH for units, snapd should ship
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to rebo
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671951
Title:
networkd should allow configuring IPV6 MTU
To manage notificati
This is won't fix at the moment, please see comments at
https://code.launchpad.net/~vorlon/debian-cd/lp.1576353/+merge/348112
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Won't Fix
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Won't Fix
--
You received this bug notifi
fixed released, as part of openssl 1.1.1 ffe.
** Changed in: ruby-openssl (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759179
Title:
autopkgtest fails with
** Description changed:
+ [Impact]
+
+ * Some systems fail to upgrade due to conflicts between systemd and the
+ (now removed from the archive) systemd-shim / upstart.
+
+ * Instead of trying to work out what's the problem in ordering /
+ removal of diverts, ensure that systemd is never unpack
** Description changed:
+ [Impact]
+
+ * systemd aborts journald, upon watchdog expiry and generates lots of crash
reports
+ * it appears that journald is simply stuck in fsync
+ * it has been agreed to disable watchdog timer on journald
+
+ [Test Case]
+
+ * watch drop-off of errors w.r.t
** Description changed:
+ [Impact]
+
+ * cryptsetup in bionic supports creating luks volumes with a non-
+ standard sector-size option, and thus this option also needs to be used
+ when activating the LUKS volumes. Add sector-size= option support to
+ /etc/crypttab.
+
+ [Test Case]
+
+ * Crea
** Description changed:
- This means that software installed via snap isn't transparently
+ [Impact]
+
+ * This means that software installed via snap isn't transparently
available for units to use. As snaps are first-class citizens in
Ubuntu, we should update the PATH.
- Specifically, t
** Description changed:
+ = systemd =
+
+ [Impact]
+
+ * IPv6 traffic failing to send/receive due to incompatible/low MTU
+ setting. Specifically, IPv6 traffic may have higher MTU requirements
+ than IPv4 traffic and thus may need to be overridden and/or set to a
+ higher value than IPv6 traffi
** Description changed:
+ [Impact]
+
+ * core18 systems fail to update hostname
+ * this happens due to /etc/hostname actually being a symlink to a file under
/etc/writable/, adjust hostnamed to take that into account when trying to
update /etc/hostname
+
+ [Test Case]
+
+ * run a core18 s
** Changed in: systemd (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/1762385
Title:
dell_wmi: Unknown key codes
To manage notifications about this bu
** Changed in: systemd (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/1773148
Title:
/lib/systemd/systemd-
journald:6:fsync:fsync_directory_of_file:
So, is there anything requested to be done with Xenial's systemd in this
bug?
** Changed in: systemd (Ubuntu Xenial)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750
601 - 700 of 9094 matches
Mail list logo
