Sorry I am a newbie here. But is it possible this was meant to be under
Apache2 project?
In which case it might be a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1708426
Sorry for noise if I am totally wrong.
--
You received this bug notification because you are a
udev source package last existed in precise. systemd-udevd is now
shipped in src:systemd, please file all future udev bugs against systemd
as a starting point.
** Package changed: udev (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Assignee: Dimitri John Ledkov (x
** Changed in: ubuntu-meta (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1873867
Title:
ubuntu-drivers changes
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1873867
Title:
ubuntu-drivers changes
Oh, and online too, doesn't install any nvidia in target.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1873867
Title:
ubuntu-drivers changes kernel flavour when
with old pool (missing right modules)
1. offline install "succeeds" but doesn't install any nvidia stuff in
target, no errors otherwise.
2. online install "stalls", generates crashreport pop-up (failing to
install lowlatency).
Possible workarounds:
- fix ubuntu-drivers to detect kernel flavour
also we have wrong / non-matching lrm modules in the pool seed.
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
I ran the software updater and noticed that it installed a new
pulseaudio:
pulseaudio:
Installed: 1:13.99.1-1ubuntu3
Candidate: 1:13.99.1-1ubuntu3
After rebooting the system, I'm running this version.
You will be happy to learn that pulseaudio doesn't crash with this
version, and it shows
I ran the software updater and noticed that it installed a new
pulseaudio:
pulseaudio:
Installed: 1:13.99.1-1ubuntu3
Candidate: 1:13.99.1-1ubuntu3
After rebooting the system, I'm running this version.
You will be happy to learn that pulseaudio doesn't crash with this
version, and it shows
OK, that's bug #1873630.
We don't actually know that this current crasher bug is correctly solved
by the above patch, since pulseaudio is not yet working. Perhaps the
new bug was there all along, but perhaps it was introduced by this patch
being an incomplete fix.
--
You received this bug
Public bug reported:
I have a Gigabyte motherboard that gives pulseaudio fits in Ubuntu 20.04
beta. (It worked fine in 18.04.4 LTS.) It produced pulseaudio crashes
with bug #1870833 until a proposed fix was brought in from upstream:
** Also affects: pulseaudio (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1853374
Title:
pulseaudio disables
i've just begun seeing this in debian 5.5.0-2 (linux 5.5.17-1) and
5.5.0-1 (5.5.13-1)
pulseaudio -k fixes it for a while, and all i see that's relevant in the
logs/dmesg is
snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 0
booting back into 5.4.0-4 (5.4.19-1) and i have no
** Attachment added: "Here's the alsa-info output for this system, in case it
helps."
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870833/+attachment/5356402/+files/alsa-info.txt.QsoAGgtfAU
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
With the -1ubuntu2 package, I no longer get a crash dump, but the audio
is still not working. pulseaudio is aborting. Here is what is in
syslog from bootup:
Apr 18 01:13:09 shh dbus-daemon[1218]: [system] Activating via systemd: service
name='org.freedesktop.RealtimeKit1'
** Attachment added: "syslog from Ubuntu 18.04.4 from the same system, with
working sound and working pulseaudio, in case it helps."
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870833/+attachment/5355971/+files/syslog-18.04.4
--
You received this bug notification because you
I forgot to note (and the attachments don't apparently say) that I am also
running this on a Gigabyte Aorus GA-AX370-Gaming 5" motherboard. I have an AMD
Ryzen 7 2700 Eight-Core Processor,
and 16GB of DRAM. I'll enclose dmesg output so you can see what audio chips
the kernel found when
Public bug reported:
I was running Ubuntu 20.04 beta x86_64 desktop without installing it.
Went into Settings, to About, clicked "Software Updates", and up popped
this window. My LAN has public IPv6 connectivity but this machine's
ethernet address was configured with an IPv4 address that doesn't
Just for fun I tried to start it manually.
$ pulseaudio --start --log-level=debug --verbose
D: [pulseaudio] conf-parser.c: Parsing configuration file
'/etc/pulse/client.conf'
D: [pulseaudio] conf-parser.c: Failed to open configuration file
'/etc/pulse/client.conf.d/01-enable-autospawn.conf': No
Besides this Whoopsie catch of pulseaudio crashing, the result is that
audio doesn't work at all on the system. Settings -> Sound shows no
options for the output or input devices, the "Test" button says to click
on a speaker to test it but then shows zero speakers, just the icon of a
person, etc.
This happened for me yesterday, when booting the main Ubuntu 20.04 beta
x86_64 iso on real hardware (not a virtual machine). It has a graphical
splash screen but in the upper left corner I get this "console" message.
Then eventually in a few seconds, after it has fully booted, that splash
screen
I don't think that implementing just subiquity is enough. Ubiquity was
the last piece of ubuntu-drivers integration on the Desktop, as update-
manager continiously was already checking for any new drivers that are
available for the systems' hardware, and continiously providing
notifications to
Failed to reproduce in a chroot with `apt full-upgrade`.
Failed to reproduce in a lxd container with `apt full-upgrade`.
Can reproduce in a lxd container with do-release-upgrade -d
```
Calculating the changes
MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > FU=1
** Changed in: apt (Ubuntu)
Status: New => Invalid
** Changed in: virtualbox (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Something is wrong
On my bionic system:
# dpkg -L python-minimal | grep usr/bin/python
/usr/bin/python
/usr/bin/python2
Can you try:
$ sudo apt install --reinstall python-minimal
** Package changed: python2.7 (Ubuntu) => python-defaults (Ubuntu)
--
You received this bug notification
and one more typo
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
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/1868246
** Description changed:
The directory size limits for systemd journal files are much too large.
The rules woud work for a small[ish] partition dedicated to /var/log but
when (as is usual) /var/log is on the main systm partition the size
limits are too big.
For example I have a
** Changed in: apport (Ubuntu)
Importance: Undecided => Critical
** Branch linked: lp:~xnox/ubuntu/focal/apport/apport-on-powerpc-
crashes-subiquity-during-crash-reporting
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Or like we should disable subiquity crash-handler, during apport crash
reporting?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1871439
Title:
subiquity should detect
Public bug reported:
apport i think needs a crash handler, to stop apport crashes, when it
crahes during crash collection.
not sure if subiquity can detect that.
see https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871434
** Affects: subiquity
Importance: Undecided
Status:
Public bug reported:
During subiquity, apport seems to be crashing
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Tags: ppc64el
** Attachment added: "Screenshot from 2020-04-07 17-00-05.png"
maybe we can specify format padding around '%s'
--
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/1863532
Title:
Invoking "python" brings inappropriate response
@vorlon
I've played with output about a dozen times. All other output from
command not found is always aligned. It looks very odd when the output
looks like a Christmas tree, without breaking translations.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
We currently believe that the decoding error reported in dmesg is
actually harmless and has no impact on usability on the system.
Switching from lz4 to gzip compression, simply papers over the warning,
without any benefits, and slows down boot.
Kernel should be fixed to correctly parse lz4
Well I am not sure what happened here . I recently made the jump from
Fedora/KDESpin to kubuntu and am still struggling with some of the not so
subtle differences (Used Fedora since its inception) .
So now I want to close this .
Thanks for your prompt response
** Changed in: dnsmasq (Ubuntu)
Public bug reported:
In /etc/dnsmasq.conf a runtime group of 'dnsmasq' is specified
The initd start script is creating a pid file and changing its ownership
to dnsmasq:nogroup
This causes the pid file to not be found (though I'm not sure why since
the pid file is owned by user 'dnsmasq')
** Description changed:
casper-md5check should leave a breadcrumb which apport & ubiquity can
pick up. (subiquity too)
There will be a file called:
- /run/casper-md5check.yaml
+ /run/casper-md5check.json
If it does not exist, or is empty the check did not run enough to
validate
Updated implementation.
** Description changed:
casper-md5check should leave a breadcrumb which apport & ubiquity can
pick up. (subiquity too)
There will be a file called:
- /run/casper-md5check.failed
+ /run/casper-md5check.yaml
- or
- /run/casper-md5check.passed
-
** Changed in: casper (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1870408
Title:
casper-md5check should leave a breadcrumb
** Description changed:
casper-md5check should leave a breadcrumb which apport & ubiquity can
pick up. (subiquity too)
There will be a file called:
/run/casper-md5check.failed
+
+ or
+ /run/casper-md5check.passed
+ /run/casper-md5check.skipped
--
You received this bug
Public bug reported:
casper-md5check should leave a breadcrumb which apport & ubiquity can
pick up. (subiquity too)
There will be a file called:
/run/casper-md5check.failed
** Affects: subiquity
Importance: Undecided
Status: New
** Affects: apport (Ubuntu)
Importance:
I see that init/initramfs.c in the kernel tries to unpack our initrd as
rootfs image, which is well, not going to happen, as it is not rootfs
image but early,early2,main(lz4 compat) initramfs.
I wonder if kernel is tripping up on such mixed compression initrd.
However, it still boots fine. So
Public bug reported:
FTBFS please drop python build-dep, or change it to python2
not uploading this package, as my previous upload has been reverted in
the past.
** Affects: indicator-power (Ubuntu)
Importance: Critical
Assignee: Sebastien Bacher (seb128)
Status: Confirmed
Not quite, I pulled Rich's patch from here and pushed it through
upstream first so we could have an official commit.
That way debian can pick it up as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
This is a debdiff for focal applicable to apparmor_2.13.3-7ubuntu2
It is picked from upstream, and has been through upstream build and
checks.
** Patch added: "apparmor-mdns-fix.patch"
** Also affects: gnome-calculator (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1868409
Title:
So, in addition to the contact: field on all seeded snaps / canonical
snaps.
Re: installers
We generally do have special cases in ubuntu-bug for "debian-installer",
"ubiquity", and "subiquity", as anybody should be able file bug reports against
"installation". Whether or not, they are
Please provide the udevadm database dump about the device in question a)
when it has correct group b) when it does not.
** Changed in: udev (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
udev source package is obsolete and is not used since precise.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
pulseaudio doesn't ship any udev rules that change group permissions of
devices. Plus it doesn't run as root, but as an unprivileged user.
** Changed in: pulseaudio (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1867607
Title:
fail to reinstall all packages
Public bug reported:
Chroot chroot dpkg-query -f '${binary:Package}\n' -W | Chroot chroot
xargs apt-get install --reinstall
Fails in focal with:
Processing triggers for libc-bin (2.31-0ubuntu6) ...
E: Could not configure 'libc6:amd64'.
E: Could not perform immediate configuration on
Public bug reported:
See libfido MIR
https://bugs.launchpad.net/ubuntu/+source/libfido2/+bug/1864439
** Affects: openssh (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
https://salsa.debian.org/cpython-team/python2/-/merge_requests/2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1867157
Title:
Improve command-not-found package
https://salsa.debian.org/cpython-team/python3/-/merge_requests/5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1867157
Title:
Improve command-not-found package
https://salsa.debian.org/cpython-team/python-defaults/-/merge_requests/1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1867157
Title:
Improve command-not-found
https://salsa.debian.org/cpython-
team/python3-defaults/-/merge_requests/3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1867157
Title:
Improve command-not-found
** Also affects: systemd via
https://github.com/systemd/systemd/issues/14322
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I'm not sure that will work, when browsers are shipped as a snap.
Does this package work with chromium as a snap?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1866841
Public bug reported:
Improve command-not-found package headers
command-not-found uses package metadata, and to improve the UX of the
misspelled commands / proposed packages.
python2.7-minimal should gain XB-Cnf-Visible-Pkgname: python2.7
python3.8-minimal should gain XB-Cnf-Visible-Pkgname:
$ python
Command 'python' not found, did you mean:
command 'python3' from deb python3
Is the new behaviour
** Changed in: python3-defaults (Ubuntu Focal)
Status: Triaged => Invalid
** Changed in: command-not-found (Ubuntu Focal)
Status: Triaged => Fix Committed
--
You
Expected behaviour is:
$ python
Command 'python' not found, did you mean:
command 'python3' from deb python3 (3.8.2-0ubuntu1)
Try: sudo apt install
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
** Changed in: openssl (Ubuntu)
Status: New => Invalid
** Changed in: openssl (Ubuntu Bionic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
I've now opened upstream issues about this on the OpenSSL bug tracker.
However, todoodle.com could refresh their certificate chain with an up
to date G2 godaddy SSL certificate chain, instead of the one that ends
on a CA Root certificate which is no longer trustworthy.
** Changed in: openssl
** Bug watch added: github.com/openssl/openssl/issues #11236
https://github.com/openssl/openssl/issues/11236
** Also affects: openssl via
https://github.com/openssl/openssl/issues/11236
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
So, in their chain of certs that they present there is still an RSA-SHA1
certificate. It shouldn't affect validation, as the other certs in the
chain are sufficient (for example gnutls-cli toodledo.com connects fine)
but it does trip up openssl:
- Certificate[3] info:
- subject `OU=Go Daddy
Lifetimes of more than a year is only implemented by Apple on their
products. Longevity of the certifications do not matter on Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
I can not speak to specifics but there are a lot of potential reason's a
packager (not firefox specific) might not be updating the profile.
- They don't use the profile / or maybe apparmor. (package
maintainership evolves and not everyone who might even be aware of it
without digging in)
- The
AppArmor does not currently cache denials except an extremely limited
dedup for capabilities. Currently apparmor is relying on the audit
subsystems rate limiting for it logging which you have rightly noted is
insufficient.
AppArmor will continue to report a denial for the error until the
profile
aa-status needs a major update. It doesn't support several things
- profile stacks
- newer profile modes
- additional profile info available in kernel (revision etc)
- it doesn't deal with namespaces
- can't identify when userspace and kernel policy are out of sync
- doesn't take
Package splits are pain, simply downgrade the python3 Depends to
Recommends or Suggests, as appropriate.
Do buildd images install recommends?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
** Changed in: abootimg (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to abootimg in Ubuntu.
https://bugs.launchpad.net/bugs/1846208
Title:
[MIR] abootimg (dependency of
About the server:
- It's certificate is valid for 2 years, and Apple has started to
rejecting any servers for which certificate is valid for more than 13
months.
- It has a SHA1withRSA certificate in its chain, which will be rejected
by all clients soon.
- It supports many weak TLSv1.2
The browsers will require SECLEVEL=2 from April 2020, the change in
libraries has already landed.
You can override this via command-line, a system config file, or a local
config file + environment variable pointing to it.
On Ubuntu 20.04 LTS:
man SSL_CTX_get_security_level.3ssl
does have:
--
** Changed in: openssl (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1856428
Title:
Disable TLS below 1.2 by default
aha, so:
$ snap info --verbose git-ubuntu | grep contact
contact: https://bugs.launchpad.net/usd-importer/+filebug
I wonder, if we can improve apport to actually upload / start filing a
bug report on launchpad, if it points to a launchpad +filebug url?
Can we enforce for contact to be set to
So, snaps in the snapstore can declare a contact url, where one can file
bug reports.
I don't see these to be exposed on the system, but maybe I don't know
the localhost APIs for that.
I do wonder if there can be some standartesation done, for example, if
the contact url is +filebug on a
This is due to how the VAR is expanded
assuming
@{HOME}=/home/*/
then
@@{HOME}/.cache/ibus/dbus-*"
expands to
/home/*//.cache/ibus/dbus-*"
and currently the secondary pass to cleanup // is not being done because the
code is treating addr as a profile name where // is a hierarchy
I should further note that this needs kernel patches to be fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1861408
Title:
firefox apparmor messages
Status in
Firefox uses cap sys_admin to set up its sandbox, which is extremely
unfortunate but required on linux to be able to set up the
user_namespace, do the chroot etc. Current the LSM and user namespaces
don't interact as well as they should.
AppArmor can NOT properly determine the policy namespace
Setting up printer-driver-hpcups (3.19.12+dfsg0-3ubuntu1) ...
Setting up gir1.2-freedesktop:amd64 (1.62.0-4ubuntu3) ...
Setting up ubuntu-drivers-common (1:0.7.7) ...
/usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering
(buffering=1) isn't supported in binary mode, the default
Public bug reported:
py3compile should compile without emitting python runtime warnings
on dist-upgrade from bionic to focal a tonne of RuntimeWarnings are
emitted during apt upgrade, due to buffering=1 being deprecated.
We will not fix all the packages, and these warnings are not helpful to
3.20180325ubuntu2~cloud1 in the cloud archive and everywhere else.
** Changed in: dh-python (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
** Changed in: sqlite3 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sqlite3 in Ubuntu.
https://bugs.launchpad.net/bugs/1862267
Title:
sqlite3 3.31.1-1 is broken on s390x
Removed keys, which are no longer in use by the current series by have
been used by previous series are always shipped in the
/usr/share/keyrings/ubuntu-archive-removed-keys.gpg and similar, which
are not trusted by the new systems by default.
So I'm not sure what you are asking for
Public bug reported:
add-apt-repository should use signed-by
apt sources.list syntax supports limiting which keys are used to sign a
given repo.
It would be nice for add-apt-repository to import the key somewhere else
but trusted.gpg.d and then specify path to it, using the "signed-by"
field.
** Changed in: openssl (Ubuntu)
Status: New => Fix Released
** Changed in: cmake (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: nodejs (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: python2.7 (Ubuntu)
Status: Fix Committed => Fix
Public bug reported:
sqlite3 3.31.1-1 is broken on s390x
for example building orthanc against 3.30.1-1ubuntu1 is successful without any
errors,
whilst upgrading sqlite3 to 3.31.1-1 and reruning the orthanc testsuite
without rebuilding results in segfaults.
please remove 3.31.1-1 sqlite3
This SRU needs to be reuploaded, due to security update that trumped
this in progress SRU.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1671951
Title:
networkd should
This SRU needs to be reuploaded, due to security update that trumped
this in progress SRU.
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => In Progress
** Changed in: systemd (Ubuntu Eoan)
Status: Fix Committed => In Progress
** Tags removed: verification-done
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => In Progress
--
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/1836695
Title:
systemd fails to setup
This SRU needs to be reuploaded, due to security update that trumped
this in progress SRU.
** Changed in: systemd (Ubuntu Eoan)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This SRU needs to be reuploaded, due to security update that trumped
this in progress SRU.
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: systemd (Ubuntu Eoan)
Status: Fix Committed => In Progress
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => In Progress
** Changed in: systemd (Ubuntu Eoan)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => In Progress
--
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/1859862
Title:
networkd doesn't
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => In Progress
--
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/1831459
Title:
'storage' test needs to
This SRU needs to be reuploaded, due to security update that trumped
this in progress SRU.
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => In Progress
** Tags removed: verification-done-bionic verification-needed
** Tags added: verification-failed
This SRU needs to be reuploaded, due to security update that trumped
this in progress SRU.
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => In Progress
** Tags removed: verification-done verification-done-bionic
** Tags added: verification-failed verification-failed-bionic
autopilot-touch is now green in NBS, after that autopilot-qt can be
removed from Ubuntu Archive.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to autopilot-qt in Ubuntu.
https://bugs.launchpad.net/bugs/1757600
Title:
RM:
901 - 1000 of 4696 matches
Mail list logo
