** Changed in: systemd (Ubuntu Artful)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Title:
systemd-resolved is not finding a domain
To manage notificati
** Changed in: systemd (Ubuntu Xenial)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1487679
Title:
Breaking ordering cycle by deleting job NetworkManager.service/sta
** Changed in: systemd (Ubuntu Artful)
Status: Confirmed => Won't Fix
** Changed in: systemd (Ubuntu Xenial)
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/bug
** Changed in: systemd (Ubuntu Xenial)
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 Xenial)
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/1762385
Title:
dell_wmi: Unknown key codes
To manage notifications about
** Changed in: systemd (Ubuntu Xenial)
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/1773148
Title:
/lib/systemd/systemd-
journald:6:fsync:fsync_directory_
** Changed in: systemd (Ubuntu Xenial)
Status: Triaged => 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/1795658
Title:
xenial systemd reports 'inactive' instead of 'failed' for se
I'm confused about this backport to xenial, given that xenial's mount-
setup.c does not try to neither mount nor use /sys/fs/cgroup/unified.
It wants to instead use /sys/fs/cgroup (for unified case).
And it has no capability to use hybrid cgroups.
Is this backport really needed back to xenial? I
** Description changed:
[Impact]
- /var/log's Permission is going back to 755
- after upgrading systemd
- if there are rsyslog's configuration on /var/lib/tmpfiles.d/
+ /var/log's Permission is going back to 755 after upgrading systemd
+ if rsyslog is installed (default)
- Affected X, A, B
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784964
Title:
Regression due to CVE-2018-1116 (processes not inheriting user's
supplementary groups )
To manage not
Bionic and later are fix released.
Xenial & Trusty are still affected, as far as I believe based on debian
bug report fixed versions metadata.
** Also affects: os-prober (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: os-prober (Ubuntu Trusty)
Importance: Undecide
95-dm-notify.rules in dmsetup is only shipped in bionic and up. So I
suspect that xenial, does not have udev synchronisation in dmsetup
package.
xenial:
https://packages.ubuntu.com/search?suite=xenial&arch=any&searchon=contents&keywords=95
-dm-notify.rules
bionic:
https://packages.ubuntu.com/sear
** Changed in: ubuntu
Assignee: Łukasz Zemczak (sil2100) => (unassigned)
** Changed in: ubuntu-power-systems
Assignee: Canonical Foundations Team (canonical-foundations) => bugproxy
(bugproxy)
** Changed in: ubuntu
Assignee: (unassigned) => bugproxy (bugproxy)
--
You received th
Could you please download and install
https://launchpad.net/ubuntu/+source/finalrd/3/+build/15227702/+files/finalrd_3_all.deb
(this is a link from
https://launchpad.net/ubuntu/+source/finalrd/3/+build/15227702 )
And check if that helps with reboots? This should perform pivot-root
from rootfs to i
Well there are two types of messages..
if it is a pretty one, it will able to reboot
if it is the ugly one, it tells the user to reboot - meaning manual
hard reset.
if there is no message, that's bad.
I'm curious what needs to be done, when no message is shown? bios or
uefi b
Public bug reported:
RM superseeded by curl4
** Affects: curl3 (Ubuntu)
Importance: Undecided
Status: Triaged
** Changed in: curl3 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: initramfs-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/1796822
Title:
Desktop live cd boots corrupted screen in Virtualbo
wrong bug number typpo!
--
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/+source/open
do we need and want to enable udev synchronisation in dmsetup package in
xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780332
Title:
vaultlocker does not ensure that udev is triggered to cr
Ideally, we'd want to bisect and fix the kernel itself to reliably
shutdown. yanking ahci sounds like a large hammer. Invalidating systemd
task, and pinging kernely people.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are
Public bug reported:
$ find /etc/rc*.d -name '*lxd'
/etc/rc0.d/K01lxd
/etc/rc1.d/K01lxd
/etc/rc2.d/K01lxd
/etc/rc3.d/K01lxd
/etc/rc4.d/K01lxd
/etc/rc5.d/K01lxd
/etc/rc6.d/K01lxd
Please call `update-rc.d lxd remove` in upgrade scripts.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: lxd 1:
Marking cosmic task as fix-released; but keeping a bionic task open.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774141
Title:
(In)compatibility library libcurl3
To manage notifications about th
curl3 was removed in cosmic; but this may still affect bionic; marking
cosmic as fix-released and keeping bionic task open.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770917
Title:
package libcu
15.04 to 18.04 is not a supported upgrade path.
One must upgrade to 16.04 first, reboot, then upgrade to 18.04. Or is
that a typo?
** Also affects: curl3 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: curl3 (Ubuntu)
Status: New => Fix Released
--
You received
curl3 was a temporary hack in the archive to "fix" xmltooling.
curl3 has now been removed in cosmic, cause the newly upgraded xmltooling stack
works with curl4 and the new openssl now.
** Also affects: curl3 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: curl3 (Ubuntu
Wait, so you are reporting as the bug report of the manifest, not
actually as a result of anything broken?
What is mfdiff?
https://packages.ubuntu.com/search?suite=bionic&arch=any&searchon=contents&keywords=mfdiff
brings up nothing.
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Inv
I mean if you cloned some random junk branch from launchpad, maybe
contact the owner of said junk branch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803162
Title:
non-dpkg information and bro
No, that's not how it works. Lots of people are free to do whatever they
want and consume whatever they want. Consumers, are only those that we
care about. I have now been pointed to at least 4 forks of mfdiff, and
well, maxsplit=1 should be enough to fix the linesplits there.
The production code
Why are you using a development image used for validating SRUs? This
image is specifically built and tested to ensure that SRUs between
point-releases, do not regress the installer media and it's not meant
for production or general use. This has never been the case.
To install Ubuntu please use ht
*** This bug is a duplicate of bug 1778219 ***
https://bugs.launchpad.net/bugs/1778219
Hi, your system appears to have an invalid init.d script which is
causing boot ordering failures
insserv: warning: script 'S65nifi' missing LSB tags and overrides
insserv: warning: script 'nifi' missing LSB
that's really really really bad!
_systemctl try-restart systemd-journald.service || true
_must_ not hang, it should either succeed or fail. that is the whole
point of try-restart
I wonder if `--no-block` would help here, but that's also a bandaid.
Imho systemctl/systemd itself shouldn't be a
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Disco)
Importance: High
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
You received this bug notification because
@ Security team please consider uploading the attached debdiff as
237-3ubuntu10.7 into security pocket to resolve hangs on shutdown when
applying updates on shutdown.
** Changed in: systemd (Ubuntu Disco)
Status: New => Fix Committed
** Changed in: systemd (Ubuntu Cosmic)
Status: Ne
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803391
Title:
Systemd update installation hangs in unattended-upgrades
InstallOnShutdown m
** Also affects: netty-tcnative-1.1 (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #872885
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872885
** Also affects: netty-tcnative-1.1 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug
@cborntra
At the moment, fix committed is the kernel only for bionic & cosmic.
Please check and comment if the kernels look sane to be released into
-updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Description changed:
- Installation of latest systemd update in -security hangs with current
+
+ [Impact]
+
+ * Installation of latest systemd update in -security hangs with current
versions of unattended-upgrades in supported releases. The u-u-side fix
is tracked in LP: #1778219.
+
+
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787405
Title:
[FEAT] Guest-dedicated Crypto Adapters
To manage notifications about this bug go to:
https://bug
** Description changed:
[Impact]
- * Some systems fail to upgrade due to conflicts between systemd and the
+ * 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 prob
Setting up ubuntu-keyring (2018.09.18.1~18.04.0) ...
# apt-key list
...
/etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
--
pub rsa4096 2018-09-17 [SC]
F6EC B376 2474 EDA9 D21B 7022 8719 20D1 991B C93C
uid [ unknown] Ubunt
sudo is enabled by default for the first installed user.
In sudoers we do specify secure_path as
Defaults
secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin"
We do not include the current working directory in PATH.
Thus the recommendation is to fork&exec, rather
@hws
Thank you. However 10.8 got trumped by security upload 10.9, hence we
are re-doing the upload with 10.10. Sorry about the noise, but -security
uploads always trump the inflight -proposed uploads.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Are you deploying zkey/zkey-cryptsetup with setuid bit on?
Do you allow calls to zkey/zkey-cryptesetup with sudoers?
Do you allow to elevate to root whilst executing zkey/zkey-cryptsetup with
policykit?
as in opening it up to execute zkey/zkey-cryptsetup with escalated
privileges by otherwise non
I feel like I misunderstand the security implication here. Especially
since it is my understanding, the binary requires to be executed by a
priviledged user, and despite user-controlled PATH would not allow a
non-priviledged user to escalate to root or execute arbitrary code.
--
You received this
** Changed in: atlas (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => 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/1803077
Title:
libatlas
Ok, so we are now awaiting for this to be accepted into the -proposed
from the queue, as I do see crash in bionic unapproved queue at
https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=crash
** Changed in: crash (Ubuntu Bionic)
Status: Incomplete => Confirmed
--
You recei
Hi, I'm looking through the atlas code. In 2017, I did contribute
changes to packaging to compile atlas with the ARCHS set to z12 on
ubuntu (up from z9, and provided the matching archdefs).
Looking at the upstream code I do not see any z13 or z14 specific code
in atlas - are there any? do we need
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792957
Title:
Provide mode where all vCPUs on a core must be the sa
** Also affects: systemd (Ubuntu Disco)
Importance: Low
Assignee: Dimitri John Ledkov (xnox)
Status: Triaged
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Disco)
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/1799364
Title:
The wlan/bt hotkey doesn't work for all Dell Latitude and Preci
** 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/1803391
Title:
Systemd update installation hangs in unattended-upgrades
Install
** Changed in: systemd (Ubuntu Disco)
Status: Triaged => 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/1804584
Title:
LG screen reported as being a Goldstar one
To manage notif
stemd/commit/?id=4ab5b8275a0487e301553fb6de6a905abb7ea833
-- Dimitri John Ledkov Thu, 22 Nov 2018 16:30:28
+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804584
Title:
LG screen reported as be
@mvo
Security wants to trump this again... Can you please validate this? I'm
not sure how to boot a core18 system.
--
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
stemd/commit/?id=4ab5b8275a0487e301553fb6de6a905abb7ea833
-- Dimitri John Ledkov Thu, 22 Nov 2018 16:30:28
+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799364
Title:
The wlan/bt hotkey doesn&#
@seb128
Ok, let's sync tomorrow. I thought we already took parts of these
patches in =/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799364
Title:
The wlan/bt hotkey doesn't work for all Dell Lat
As discussed on
https://github.com/ibm-s390-tools/s390-tools/commit/9100327092c470c2e5b5819087c8094822a1c751
it is agreed that it is sufficient if the default configurations of sudo
and su (or anything similar) set a predefined secured path. Which has
always been true on Ubuntu. Thus, on Ubuntu, on
** Also affects: s390-tools (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: s390-tools (Ubuntu)
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/
Public bug reported:
s390x qemu vt220 terminal, tput cols and lines is reported as 80x24,
whilst that's not true.
The number of columns is semi-true, as the shell wraps them, however,
one can print things beyond 80 cols.
Ideally resizing qemu window, should manage to report the actual number
of
tput reset -> breaks the terminal
resizing the qemu window -> fixes things
Thus e.g. SIGWINCH is probably handled correctly. However it seems like
there is terminal definitions missing or something.
** Tags added: s390x
--
You received this bug notification because you are a member of Ubuntu
B
@SRU team, actually we will cherrypick more things into systemd, to make
systemd & xkeyboard-config play nice with each other, as is destined to
be upstream and in disco.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xkeyboard-config (Ubuntu Disco)
** Changed in: python-diskimage-builder (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640186
Title:
No source repository for 'debian' part of the package
** Changed in: python-diskimage-builder (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458660
Title:
python-diskimage-builder contain link to 'Broken-2014
Public bug reported:
[Impact]
* Newly added testcase in a security upload used a traditional GNU
patch format, instead of using extended git patch format, as supported
by GNU patch. Therefore, executable bits on shells scripts were lost,
resulting in autopkgtest failures.
[Test Case]
* `upstr
** Changed in: valgrind (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799696
Title:
[19.04 FEAT] Valgrind z13 support
To manage notifications about this bu
In v3.15.0 in master I see following s390x bugfixes staged:
400490 s390x: VRs allocated as if separate from FPRs
400491 s390x: Operand of LOCH treated as unsigned integer
397187 z13 vector register support for vgdb gdbserver
401277 More bugs in z13 support
However, https://bugs.kde.org/show_
It's not even my patch =) just something that was done by maintainers in
Debian = so obfuscating++
** Also affects: libpam-mount (Ubuntu Disco)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: Fix Committed
** Also affects: libpam-mount (Ubunt
Confirming libvirt task back on, as there are appear to be a few small
patches for libvirt.
** Changed in: libvirt (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Public bug reported:
disco installer crashed
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 18.10.12
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu14
Architecture: amd64
CasperVersion: 1.399
CurrentDes
Nov 2 19:27:57 ubuntu /plugininstall.py: Exception during installation:
Nov 2 19:27:57 ubuntu /plugininstall.py: Traceback (most recent call last):
Nov 2 19:27:57 ubuntu /plugininstall.py: File
"/usr/share/ubiquity/plugininstall.py", line 1718, in
Nov 2 19:27:57 ubuntu /plugininstall.py:
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
St
Public bug reported:
As part of Ubuntu key rotation strategy, we rely on dual-signing
(inline, or detached) such that validation with at least one key
available in a keyring should be trusted, without using web-of-trust.
However, it seems to be only correctly so far implemented by the apt's
gpgv
Public bug reported:
Setting up python3-django-maas (2.5.0~beta2-7291-gd0345ced5-0ubuntu1) ...
File "/usr/lib/python3/dist-packages/maasserver/clusterrpc/boot_images.py",
line 30
from maasserver.utils import async
^
SyntaxError: invalid syntax
File "/
Public bug reported:
Removed from testing for perl transition
https://tracker.debian.org/news/1000655/libextutils-parsexs-perl-removed-from-testing/
rc buggy
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912682
Subject: libextutils-parsexs-perl: version is older than Replaces+Breaks
in perl-
** Changed in: ubiquity (Ubuntu)
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/1801408
Title:
disco installer crashed with usr-merge
To manage notifications
Thank you for the quick fix! I will cherrypick this in disco, such that
we can start building server iso images.
Obviously will be trumped in the next upload to disco which has a new
upstream release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Note this bug is mentioned in the changelog for adding disco, whilst the
rest of releases appear to be using
https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1800945
bugnumber.
Adding just the symlink is not good enough for disco+ as one also needs
to backport MERGED_USR=yes stanza, and/
ubuntu@xnoxtest:~$ ls -latr foo/ | grep sbin
drwxr-xr-x 2 root root 4096 Nov 7 12:39 sbin
ubuntu@xnoxtest:~$ dpkg-query -W debootstrap
debootstrap 1.0.95ubuntu0.2
Which is bad, as sbin should be -> usr/sbin
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Adding just the symlink is not good enough for disco+ as one also needs
to backport MERGED_USR=yes stanza, and/or MERGED_USR support, depending
on how far back one wants to go. Otherwise, older releases will
bootstrap disco non-usr-merged.
Hence e.g. bionic's upload is bad. (which by the way was d
** Changed in: maas (Ubuntu)
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/1801899
Title:
cannot install with python3.7 as default async is a reserved keyword
To
Cosmic is good:
ubuntu@xnoxcosmic:~$ ls -latr foo | grep sbin
lrwxrwxrwx 1 root root 8 Nov 7 12:47 sbin -> usr/sbin
ubuntu@xnoxcosmic:~$ dpkg-query -W debootstrap
debootstrap 1.0.108ubuntu1.1
** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-
again, out of scope.
also, yes we do attempt to build all packages, and we try not to remove
architectures without reason. as we assume that eventually upstreams can
get their ducks in a row to make things work, cause they should.
but more importantly which release are you looking at? what is the
** Branch unlinked: lp:~xnox/britney/hints-ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790513
Title:
kdump-config status - not ready to kdump with v4.18 kernel
To manage notifications abo
cosmic is fine
bionic needs to default to merged_usr, and fix up to the -k option
older than bionic need merged_usr setup backport and -k option fix working on
the updates
re: -k option, see https://salsa.debian.org/installer-
team/debootstrap/commit/316b677defc78f8e4410d047bc1e1a314abcd666
--
Can you please explain the bug report more?
I cannot understand your question, nor title. What is vrms?
In ubuntu this package is in main, for definition of main please see our
documentation.
** Changed in: glibc-doc-reference (Ubuntu)
Status: New => Incomplete
--
You received this bug
reconserver has multiple ftbfs issues / bugs.
** Also affects: cfengine2 (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #851087
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851087
** Also affects: cfengine2 (Debian) via
https://bugs.debian.
Public bug reported:
RM openssl1.0 from Ubuntu
** Affects: cfengine2 (Ubuntu)
Importance: Undecided
Status: New
** Affects: ekiga (Ubuntu)
Importance: Undecided
Status: New
** Affects: opal (Ubuntu)
Importance: Undecided
Status: New
** Affects: openssl
This has regressed, somehow boost1.62 got autosynced back into disco.
Please remove and blacklist?!
** Changed in: boost1.62 (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Do this also need a removal request in Debian? Whilst checkbox-ng was
removed from testing, it is still present in unstable. See
https://tracker.debian.org/pkg/checkbox-ng
Maybe an RM, RoM bug needs to be filed there too?
--
You received this bug notification because you are a member of Ubuntu
B
** Changed in: cfengine2 (Ubuntu)
Status: New => Confirmed
** Changed in: openssl1.0 (Ubuntu)
Status: New => Incomplete
** Changed in: ekiga (Ubuntu)
Status: New => Confirmed
** Changed in: t38modem (Ubuntu)
Status: New => Confirmed
** Changed in: reconserver (Ubuntu
** Also affects: cqrlog (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #867140
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867140
** Also affects: cqrlog (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867140
Importance: U
** Also affects: linux-ftpd-ssl (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #912123
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912123
** Also affects: linux-ftpd-ssl (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912123
It's been extended in a backwards compatible manner.
Is this just an observation, or is something broken?
You correctly state what the format was, what the format has become, but
I don't see an actual bug report stated anywhere as to anything being
broken by this.
Because yes, the format of the
Note to self.
umount.target
A special target unit that unmounts all mount and automount points
on system shutdown.
Mounts that shall be unmounted on system shutdown shall add
Conflicts dependencies to this unit for their mount unit, which is implicitly
done
Logging out of session [sid: 1, target: tgt-boot-test-34LfbG, portal:
10.1.1.2,3260]
[ 591.782918] sd-execu[1804]:
/usr/lib/systemd/system-shutdown/open-iscsi.finalrd failed with exit status 141.
[ 591.828276] reboot: Power down
h
--
You received this bug notification because you are a m
** Changed in: xe-guest-utilities (Ubuntu)
Status: Triaged => Fix Released
** Changed in: xe-guest-utilities (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm not sure what vaultlocker is.
trigger might be appropriate together with a '--settle' flag, if/where
available.
instead of manually opening things, i'd expect crypttab to be adjusted
with `systemctl daemon-reload` re-run to regenerated systemd-cryptsetup@
units and "open" the encrytped device
mailman-suite / mailman3-web should change packaging to launch as
python3, not python2 webapp.
** Also affects: mailman-suite (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Also affects: glibc (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/1792947
Title:
OSError: [Errno 22] failed to open netns (bionic-rocky)
To m
Public bug reported:
Merge openssl 1.1.1 from debian unstable.
OpenSSL 1.1.1 is now out, with TLS1.3 support, and is the new upstream
LTS release.
Preserving existing delta:
- Replace duplicate files in the doc directory with symlinks.
- debian/libssl1.1.postinst:
+ Display a system restart re
701 - 800 of 9094 matches
Mail list logo
