I tried to reproduce this in an up-to-date bionic VM as follows:
# inside the bionic VM
sudo snap install lxd
sudo lxd init # accept defauls
sudo lxc launch ubuntu-daily:hirsute hirsute
sudo lxc exec hirsute /bin/bash
# then inside the hirsute container install livecd-rootfs
apt update
apt
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You
Public bug reported:
Approximately two weeks ago after leaving the computer alone the display
turned off like normal but did not come back.The system is working in
the background but the display wont show. I've gotten it to work
sometimes by pulling out the display port cable out and putting it
Thanks for the bug report. Please try uninstalling/disabling all
extensions you might have added via the 'Extensions' app. Then reboot
and tell us if the problem still happens.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Tags added: amdgpu
** Changed in: mutter (Ubuntu)
** Summary changed:
- [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all
+ [ASUS X441SA] No sound at all
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: focal
** Summary changed:
- [ASUS X441SA] No sound at all
+ [ASUS X441SA] [8086:2284]
** Summary changed:
- no sound when upgrading to Kubuntu-20.04
+ [8086:27d8] No sound when upgrading to Kubuntu-20.04
** Package changed: ubiquity (Ubuntu) => pulseaudio (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
*** This bug is a duplicate of bug 1875259 ***
https://bugs.launchpad.net/bugs/1875259
** Summary changed:
- Bluetooth sound card not detected
+ [Sony VGN-TZ150N] Bluetooth sound card not detected
** This bug has been marked a duplicate of bug 1875259
[8086:27d8] No sound when upgrading
You have been subscribed to a public bug:
Since I upgraded to Kubuntu-20.04, there is no sound. Everything worked fine
with Kubuntu-19.10.
pacmd list-cards
1 card(s) available.
index: 0
name:
driver:
owner module: 7
properties:
alsa.card =
*** This bug is a duplicate of bug 1918033 ***
https://bugs.launchpad.net/bugs/1918033
** Tags added: fixed-in-40 fixed-upstream
** Changed in: mutter (Ubuntu)
Status: Triaged => Fix Committed
** This bug has been marked a duplicate of bug 1918033
gnome-shell crashed with
Should be fixed by
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1651
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
** Changed in: mutter (Ubuntu)
Status: New => Triaged
--
You received
Upstream are not totally sure that fix also addresses this crash so
reopened for now.
** Changed in: mesa (Ubuntu)
Status: Fix Committed => Confirmed
** Changed in: mesa (Ubuntu)
Importance: Undecided => High
** No longer affects: linux (Ubuntu)
** No longer affects: xorg-server
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.2) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
snapd/2.48.3+20.10 (amd64)
nut/2.7.4-12ubuntu1 (ppc64el)
Please visit the excuses page listed below and
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.2) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
snapd/2.48.3+20.10 (amd64)
nut/2.7.4-12ubuntu1 (ppc64el)
Please visit the excuses page listed below and
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.2) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
snapd/2.48.3+20.10 (amd64)
nut/2.7.4-12ubuntu1 (ppc64el)
Please visit the excuses page listed below and
> Do you plan releasing this version on PPA
that was for the hirsute release - are you able to test that
(development) release to ensure the problem is fixed? it's the same
patches as for focal, so it may not be fixed there.
Alternately if you have a test environment (NOT some system that you
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
prometheus-apache-exporter/0.7.0+ds-1 (arm64)
udisks2/2.8.4-1ubuntu1 (amd64, ppc64el)
munin/2.0.56-1ubuntu1 (arm64)
This bug was fixed in the package systemd - 247.3-1ubuntu4
---
systemd (247.3-1ubuntu4) hirsute; urgency=medium
[ Dimitri John Ledkov ]
*
d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch:
Patch updated to reduce log level to debug
** No longer affects: dbus (Ubuntu)
** No longer affects: dbus (Ubuntu Bionic)
** No longer affects: gnome-terminal (Ubuntu)
** No longer affects: gnome-terminal (Ubuntu Bionic)
** Project changed: nautilus => ubuntu-translations
** No longer affects: ubuntu-translations
** Project changed:
This bug was fixed in the package systemd - 247.3-1ubuntu4
---
systemd (247.3-1ubuntu4) hirsute; urgency=medium
[ Dimitri John Ledkov ]
*
d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch:
Patch updated to reduce log level to debug
** No longer affects: lxd (Ubuntu)
--
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/1914062
Title:
NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start
in
*** This bug is a duplicate of bug 1888598 ***
https://bugs.launchpad.net/bugs/1888598
if I add blacklist= to load-module module-switch-on-connect, switching
to HDMI is no longer inhibited, and the HDMI output is listed first in
pavucontrol, but the output still disappears for good when the
@3v1n0 (Marco Trevisan) has pointed out
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1651 as a
possible fix
** Description changed:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the
Just confirming that this is still an issue in Ubuntu 20.10 groovy.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcre3 in Ubuntu.
https://bugs.launchpad.net/bugs/1818027
Title:
cinnamon-sessio: segfault at ip sp
** Changed in: rhythmbox (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1542471
Title:
Playing mp3 files causes:
*** This bug is a duplicate of bug 1888598 ***
https://bugs.launchpad.net/bugs/1888598
Here is what happens as seen by pulseaudio - during the monitor
sleep/wake cycle leading to disappearance of the HDMI output:
D: [pulseaudio] alsa-util.c: ELD info empty (for device=3)
D: [pulseaudio]
As a workaround for anyone, you can use nmcli to bring up a VPN
connection.
Run `nmcli c` to get a list of connections, once you have the name you
can enable it with `nmcli c up $name` or disable it with `nmcli c down
$name`.
--
You received this bug notification because you are a member of
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
corosync/2.4.3-0ubuntu1.1 (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
corosync/2.4.3-0ubuntu1.1 (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
corosync/2.4.3-0ubuntu1.1 (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
corosync/2.4.3-0ubuntu1.1 (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
corosync/2.4.3-0ubuntu1.1 (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
corosync/2.4.3-0ubuntu1.1 (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
corosync/2.4.3-0ubuntu1.1 (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
corosync/2.4.3-0ubuntu1.1 (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
corosync/2.4.3-0ubuntu1.1 (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el,
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
corosync/2.4.3-0ubuntu1.1 (armhf)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el,
This looks to be around the time of the issue where I disabled a VPN
connection (from syslog):
Mar 8 14:11:54 splat gnome-shell[677801]: **
Mar 8 14:11:54 splat gnome-shell[677801]:
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
assertion failed:
Public bug reported:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04
$
*** This bug is a duplicate of bug 1888598 ***
https://bugs.launchpad.net/bugs/1888598
Hi!
Affected by this bug, but not exactly bug #1888598.
Config: Asus Extreme Omega integrated HDA Intel PCH as Card 1 + ASUS Nvidia
3090 as Card 2.
Card 0 is an USB webcam and only an audio input.
Problem
Public bug reported:
Just happened, didn't really do anything.
ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: tracker 2.3.6-2
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
Thank you for taking the time to file a bug report.
>From what you described it seems that Network Manager is the one
responsible for adding the unexpected routing rule, so this might not
affect OpenVPN itself. I quickly tried to reproduce your setup but did
not notice the bug there. Could you
Do you plan releasing this version on PPA (for 20.04, which I use)? I'd
be glad to test…
--
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/1906331
Title:
systemd-resolve
*** This bug is a duplicate of bug 1915579 ***
https://bugs.launchpad.net/bugs/1915579
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package systemd - 247.3-1ubuntu4
---
systemd (247.3-1ubuntu4) hirsute; urgency=medium
[ Dimitri John Ledkov ]
*
d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch:
Patch updated to reduce log level to debug
This bug was fixed in the package systemd - 247.3-1ubuntu4
---
systemd (247.3-1ubuntu4) hirsute; urgency=medium
[ Dimitri John Ledkov ]
*
d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch:
Patch updated to reduce log level to debug
*** This bug is a duplicate of bug 1913763 ***
https://bugs.launchpad.net/bugs/1913763
This bug was fixed in the package systemd - 247.3-1ubuntu4
---
systemd (247.3-1ubuntu4) hirsute; urgency=medium
[ Dimitri John Ledkov ]
*
Thanks for reply. I remove pipewire by using `Muon package manager` and
then restart computer. Still no sound and dummy output.
Daniel van Vugt <1916...@bugs.launchpad.net>, 8 Mar 2021 Pzt, 03:35
tarihinde şunu yazdı:
> This sounds like bug 1897965, which might now be affecting 20.04.2.
> Please
Thanks for the review Robie,
I have tested the package on the proposed pocket by using this script:
#!/bin/sh
set -x
series=trusty
name=$series-upgrade
multipass delete $name
multipass purge
multipass launch $series --name $name
multipass exec $name -- sudo sh -c "cat
** Also affects: wireshark (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1916705
Title:
glib2.0 >=2.67.3 breaks
Hi Dimitri,
These are the dkms packages which had the build failure fixed after the
-hwe switch in Focal from 5.4 to 5.8:
bcmwl=6.30.223.271+bdcom-0ubuntu7~20.04.1
nvidia-graphics-drivers-340=340.108-0ubuntu5.20.04.1
virtualbox-hwe=6.1.16-dfsg-6ubuntu1.20.04.1
And this is the list of all the
The issue with the dkms package has been fixed via bug 1915051.
** Changed in: dkms (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Verification procedure on Focal:
$ lxc launch focal lp1902236-f
Creating lp1902236-f
Starting lp1902236-f
$ lxc exec lp1902236-f bash
root@lp1902236-f:~# getent passwd | grep root
root:x:0:0:root:/root:/bin/bash
root:x:0:0:root:/root:/bin/sh
root@lp1902236-f:~# getent passwd | grep nobody
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cron (Ubuntu Groovy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: anacron (Ubuntu Groovy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cron (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: anacron (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cron (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: anacron (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: anacron (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1918122
Title:
Background picture not changed correctly
Status in xorg package in
You have been subscribed to a public bug:
I have changed my background picture to a external picture
everything is good but when I changed my screen to the bottom one(super+pate
down) my prevision background coming back
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
systemd-resolved still crashing more-or-less every 10 minutes.
Some update arrived (I installed it 15 minutes ago) -
245.4-4ubuntu3.5~202103051349~ubuntu20.04.1 - it also crashed few mins
since the installation.
I tried various approaches to kernel.core_pattern, but nothing is
gathered. As I
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1916485
Title:
test -x fails inside shell scripts in containers
Status in docker.io package
Forwarded to upstream open-vm-tools as
https://github.com/vmware/open-vm-tools/issues/500
Uploaded a fix for Ubuntu in
https://launchpad.net/ubuntu/+source/open-vm-tools/2:11.2.5-2ubuntu1
** Bug watch added: github.com/vmware/open-vm-tools/issues #500
LGTM!
--
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/1883447
Title:
nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to
focal in containers
Status
We're actually not backporting this to stable releases just future
stable one :)
** Changed in: apt (Ubuntu Groovy)
Status: New => Won't Fix
** Changed in: apt (Ubuntu Focal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
[Impact]
Merge request https://salsa.debian.org/apt-team/apt/-/merge_requests/159 has a
bunch of fixes for empty pdiff files, cleaning up pdiff files, as well as
correcting some bugs with index files in the mirror method.
While we don't use pdiffs ourselves, third party
Indeed, I'm running the daily build and toggling the percentage setting
on and off has the expected result.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1766108
Hello Etienne, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dimitri, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Kai-Heng, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello MarcH, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Steve, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dan, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Gauthier, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Ioanna, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Kleber, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Daniel, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
@ddstreet Well, after thinking about it, I'm actually not sure if this
is an issue after all. Or if this should/must be handled by the system
administrator itself, when using NIS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Hello Dimitri, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello MarcH, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Simon, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Ioanna, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Kleber, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Daniel, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Gauthier, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Ioanna, or anyone else affected,
Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello MarcH, or anyone else affected,
Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Gauthier, or anyone else affected,
Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hiya,
This was fixed in Debian via 5.1.6-4, which is merged in Hirsute release
(5.1.6-4ubuntu1). Therefore, I am marking this as "Fix Released" for
Hirsute. Should you have any questions or problems wrt this, let me
know!
Thanks.
** Changed in: autofs (Ubuntu)
Status: New => Fix Released
> Also open-vm-tools is also FTBFS by this, so I need to add a task and
work on that as well.
You want this kind of thing minimally to get over the FTBFS:
--- open-vm-tools-11.2.5.orig/open-vm-tools/configure.ac
+++ open-vm-tools-11.2.5/open-vm-tools/configure.ac
@@ -503,6 +503,9 @@
This bug was fixed in the package qemu - 1:5.2+dfsg-6ubuntu2
---
qemu (1:5.2+dfsg-6ubuntu2) hirsute; urgency=medium
* d/p/u/lp-1916705-disas-Fix-build-with-glib2.0-2.67.3.patch: Fix FTFBS due
to glib2.0 >=2.67.3 (LP: #1916705)
qemu (1:5.2+dfsg-6ubuntu1) hirsute; urgency=medium
This sounds like bug 1897965, which might now be affecting 20.04.2.
Please try the suggestions in bug 1897965.
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu)
--
You received this bug notification because you
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1917624
When reporting bugs in the future please use apport by using 'ubuntu-
1 - 100 of 101 matches
Mail list logo
