Thanks for looking into this.
Testing is done in VMs, using dnsmasq for name resolution.
I set use_fully_qualified_names = False because I suspect a name
resolution issue, and wanted to try another setting than the default set
when the configuration file is created by realm. True or False doesn't
** Description changed:
Tested on Ubuntu Desktop 20.04.1 and Groovy up-to-date.
The setup in one ADC running on Windows Server 2019 and 3 clients,
Ubuntu Desktop 20.04.1, Ubuntu Deskop Groovy, Fedora 32.
On Ubuntu clients, after following the documentation at
https://discourse.ubun
** Attachment added: "sssd.logs.tgz"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1893438/+attachment/5405445/+files/sssd.logs.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893438
Titl
Public bug reported:
Tested on Ubuntu Desktop 20.04.1 and Groovy up-to-date.
The setup in one ADC running on Windows Server 2019 and 3 clients,
Ubuntu Desktop 20.04.1, Ubuntu Deskop Groovy, Fedora 32.
On Ubuntu clients, after following the documentation at
https://discourse.ubuntu.com/t/service-
** Attachment added: "sssd.conf"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1893438/+attachment/5405446/+files/sssd.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893438
Title:
Can
Thanks for your report.
It seems to match the list of package to remove for a minimal
installation and I cannot reproduce with a normal installation.
Can you please confirm that you did a minimal installation? If so which
package do you think should be kept on a minimal installation?
** Changed
*** This bug is a duplicate of bug 1893260 ***
https://bugs.launchpad.net/bugs/1893260
** This bug has been marked a duplicate of bug 1893260
Ubiquity removes too many applications
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
This is fixed in 0.4.7.
** Changed in: zsys (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/1885234
Title:
package zsys 0.4.6 failed to install/upgrade: in
** 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/1892040
Title:
US keyboard layout even if a non english language is selected in
ubiquity-dm
To manage notifications
Public bug reported:
Last known good version: 20.04
This regression appeared in 20.04.1 and 20.10.
= Test Case =
1. Boot to ubiquity-dm
2. In the list of languages select 'French'
3. Boot to the live session
= Expected result =
* Verify that there is a keyboard indicator in the indicator area
** Changed in: autopilot-gtk (Ubuntu)
Status: In Progress => 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/1856574
Title:
removal of various autopilot packages
To manage notifi
Sorry it has completely fallen through the cracks.
Here is the fix: https://git.launchpad.net/autopilot-
gtk/commit/?id=00d7a3d7111cdca00b949bfa9c315781e6701328
It builds successfully on groovy/amd64 (waiting for armhf)
https://launchpad.net/~autopilot/+archive/ubuntu/ap-unstable-rel-
testing/+so
** Changed in: autopilot-gtk (Ubuntu)
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/1856574
Title:
removal of various autopilot packages
To manage notification
I tried again and it's working now. Closing this report.
** Changed in: debian-installer (Ubuntu Xenial)
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/1890824
Title:
[
** Summary changed:
- [xenial] mini and pxe installations fails with 'sh' segfault
+ [xenial] mini and pxe installations fail with 'sh' segfault
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890824
** Summary changed:
- mini and pxe installations fails with 'sh' segfault
+ [xenial] mini and pxe installations fails with 'sh' segfault
** Description changed:
- d-i 20101020ubuntu451
+ Xenial d-i 20101020ubuntu451
Installation in qemu with mini.iso or with PXE fails in 'detect disks' with
Public bug reported:
d-i 20101020ubuntu451
Installation in qemu with mini.iso or with PXE fails in 'detect disks' with a
segfault of sh in libc (cf screenshot)
It's similar to bug 1560456.
Host is Groovy up to date with qemu 5.0-5ubuntu3
** Affects: debian-installer (Ubuntu)
Importance: U
SRU verification for Focal:
I have reproduced the problem with zsys 0.4.6 in focal-updates and have
verified that the version of zsys 0.4.7 in -proposed fixes the issue.
Marking as verification-done
For reference this is the script I used to create the snapshots:
==
#!/bin/sh
timedatect
SRU verification for Focal:
I have reproduced the problem with zsys 0.4.6 in focal-updates and have
verified that the version of zsys 0.4.7 in -proposed fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done
This has been fixed on server side and should be on all the releases. I
checked with Ubuntu Desktop 20.04.1.
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
The issue is that http://start.ubuntu.com/connectivity-check.html
returns a 404. I'll chase why.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890392
Title:
xubuntu 20.04.1 qa-test install, unable
And kubuntu/focal which worked yesterday since I triaged and fixed a bug
related to the release notes link.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890392
Title:
xubuntu 20.04.1 qa-test insta
I observed the same issue on several releases of Ubuntu (xenial, focal
and groovy) It's more likely something going on server side.
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notific
It's reproducible in a VM. There is no related message in the journal.
** Package changed: ubuntu => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Thanks for your report.
Does the same happen with groovy?
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** This bug is no longer a duplicate of bug 1890173
[kubuntu] "Release notes" link doesn't open
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709492
Title:
lubuntu-next has broken website link i
> Jean-Baptiste Lallement (jibel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890173
Title:
[kubuntu] "Release notes" link doesn't open
To manage notifications abo
*** This bug is a duplicate of bug 1890173 ***
https://bugs.launchpad.net/bugs/1890173
** This bug has been marked a duplicate of bug 1890173
[kubuntu] "Release notes" link doesn't open
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
** This bug is no longer a duplicate of bug 1681144
Clicking on URLs in Kubuntu Installer Slideshow does nothing
** This bug has been marked a duplicate of bug 1890173
[kubuntu] "Release notes" link doesn't open
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Actually the KDE_SESSION_VERSION is set to 4 instead of 5 in kde_ui.py.
I'll submit a fix.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1890173
Title:
[kubuntu] "Release notes" link do
@Marco, it's likely the same root cause.
You can check if in /var/log/installer/debug there is an error similar to :
/usr/bin/xdg-open: 604: kde-open: not found
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
I filed bug 1890173 for the "release notes link doesn't work issue" but
your crash is something different.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890137
Title:
ubiquity crashes when "release
Public bug reported:
On Kubuntu (20200731), the release notes link doesn't open on click.
xdg-open uses the following call: kde-open${KDE_SESSION_VERSION} "$1"
but KDE_SESSION_VERSION is not set when xgd-open is executed and it executes
kde-open (which doesn't exist) instead of kde-open5.
Prob
** Changed in: ubiquity (Ubuntu)
Importance: Medium => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890137
Title:
ubiquity crashes when "release notes" selected
To manage notifications abo
I tried on kubuntu, the "release notes" link does nothing because xdg-
open uses kde-open which doesn't exist (kde-open5 does) but the
installer doesn't crash.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.l
>From syslog:
Exception in KDE frontend (invoking crash handler):
Traceback (most recent call last):
File "/usr/lib/ubiquity/plugins/ubi-language.py", line 485, in
on_release_notes_link
self.openURL(url)
File "/usr/lib/ubiquity/plugins/ubi-language.py", line 512, in openURL
misc
** Description changed:
- root@tmp:/home/pgray# zfs list -t snapshot -o name -S creation
+ ** SRU **
+ [Impact]
+ For yet unknown reasons, bpool is sometimes not imported. This causes the
upgrade script to fail because then /boot is not a mount point.
+ The fix just ignores the return status of
** Also affects: zsys (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: zsys (Ubuntu Focal)
Status: New => Triaged
** Changed in: zsys (Ubuntu Focal)
Importance: Undecided => High
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Jean
It probably fails on flavours and not ubuntu desktop because grub-efi-
amd64 is not seeded on Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885414
Title:
on flavours ubiquity: bootloader fa
** Changed in: ubiquity (Ubuntu Groovy)
Status: Fix Released => Triaged
** Summary changed:
- ubiquity: bootloader failed on /dev/vda
+ on flavours ubiquity: bootloader failed on /dev/vda
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Thanks for your report.
This is an old image and already fixed in latest. It is not yet
published to current due to unrelated issues with the installer but
should be tomorrow.
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you a
This is fixed with Ubuntu Desktop 20200707.1. Other builds will be done
automatically tomorrow.
** Changed in: ubiquity (Ubuntu Groovy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
*** This bug is a duplicate of bug 1886214 ***
https://bugs.launchpad.net/bugs/1886214
** This bug has been marked a duplicate of bug 1886214
zsys package post-installation failed when boot pool is not imported
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks for your report. This is already fixed but groovy images have not
been promoted for a while due to other issues with the installer. Please
try again when there is a new image in current/
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
--
You received this bug notificat
Thanks for the data.
for some reason bpool is not imported on your system, and the postinst
script fails in this case.
** Summary changed:
- apt-get upgrade fails on zsys package
+ apt-get upgrade fails on zsys package when boot pool is not imported
** Changed in: zsys (Ubuntu)
Importance: U
*** This bug is a duplicate of bug 1886214 ***
https://bugs.launchpad.net/bugs/1886214
I think it's the same situation than bug 1886214.
The message "trimming already in progress" is a red herring. The call to
zpool trim is protected by a || true and cannot make the postinst script
fail.
How
** Changed in: zsys (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886214
Title:
apt-get upgrade fails on zsys package
To manage notifications about
Thanks for the update. I'm closing this report then. There is not enough
information to understand what happened.
Do not hesitate to submit any new bug you may find.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
Thanks for your report.
Could you please run:
apport-collect 1886214
It will gather useful information that will help us understand why the
upgrade failed.
Thanks.
** Changed in: zsys (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a membe
Thanks for your report. There was a bug in the calculation of the
partition number with zfs installations. This bug is now fixed and will
be released as soon as there is an installable build of groovy. It
currently fails with bug 1885414.
** Changed in: ubiquity (Ubuntu)
Status: New => Inco
Thanks for your report.
We enable autotrim in postinst but it's failing because trimming is
already running according to this message:
Setting up zsys (0.4.6) ...
cannot trim '/dev/sda4': currently trimming
dpkg: error processing package zsys (--configure):
installed zsys package post-instal
*** This bug is a duplicate of bug 1885414 ***
https://bugs.launchpad.net/bugs/1885414
** This bug has been marked a duplicate of bug 1885414
ubiquity: bootloader failed on /dev/vda
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
*** This bug is a duplicate of bug 1885414 ***
https://bugs.launchpad.net/bugs/1885414
** This bug has been marked a duplicate of bug 1885414
ubiquity: bootloader failed on /dev/vda
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
*** This bug is a duplicate of bug 1885414 ***
https://bugs.launchpad.net/bugs/1885414
** This bug is no longer a duplicate of bug 1885976
Kubuntu groovy gorilla installer crash
** This bug has been marked a duplicate of bug 1885414
ubiquity: bootloader failed on /dev/vda
--
You receiv
This patch from mwhudson fixes the issue:
diff --git a/d-i/source/grub-installer/grub-installer
b/d-i/source/grub-installer/grub-installer
index 2329f0e801..ac9fd37ff3 100755
--- a/d-i/source/grub-installer/grub-installer
+++ b/d-i/source/grub-installer/grub-installer
@@ -641,7 +641,7 @@ db_progr
Syslog from a failed installation with 20200701.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1885414/+attachment/5388693/+files/syslog
** Summary changed:
- ubiquity: bootloader failed on /dev/vda, ubuntu-mate groovy 2020-06-28
+ ubiquity: bootloader
This is actually not fixed with ubiquity 20.10.7 and image 20200701.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885414
Title:
This is fixed with Ubiquity 20.10.6 currently in groovy proposed and
will be available when it migrates to the release pocket.
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
** Changed in: ubiquity (Ubuntu)
Status: Fix Released => Triaged
** Changed in: ubiquity (Ubun
** Attachment added: "dmesg.out"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881699/+attachment/5388089/+files/dmesg.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881699
Title:
** Attachment added: "pactl list cards"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881699/+attachment/5388090/+files/pactl.list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881699
No difference with this option.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881699
Title:
No analog output
To manage notific
SRU verification for Focal:
I have reproduced the problem with ubiquity 20.04.15 in focal and have verified
that the version of ubiquity 20.04.15.1 in -proposed fixes the issue.
I tested on a VM with 3 disks, and it boots from 3rd disk when I set it
as the first disk to try. Otherwise it doesn't
SRU verification for Focal:
I have reproduced the problem with ubiquity 20.04.15 in focal and have verified
that the version of ubiquity 20.04.15.1 in -proposed fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
** Tags added: verificati
SRU verification for Focal:
I have reproduced the problem with ubiquity 20.04.15 in focal and have verified
that the version of ubiquity 20.04.15.1 in -proposed fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
** Tags added: verificati
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883686
Title:
zfs should enable
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880869
Title:
Use persistent de
SRU verification for Focal:
I have reproduced the problem with ubiquity 20.04.15 in focal and have verified
that the version of ubiquity 20.04.15.1 in -proposed fixes the issue.
Marking as verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
SRU verification for Focal:
I have reproduced the problem with ubiquity 20.04.15 in focal and have verified
that the version of ubiquity 20.04.15.1 in -proposed fixes the issue.
Marking as verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
SRU verification for Focal:
I have reproduced the problem with ubiquity 20.04.15 in focal and have verified
that the version of ubiquity 20.04.15.1 in -proposed fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
** Tags added: verificati
** Description changed:
[Impact]
- * Ubuntu enables automatic TRIM / DISCARD on all filesystems that
+ * Ubuntu enables automatic TRIM / DISCARD on all filesystems that
support it, such that on SSD-like storage devices the performance over
time is improved. ZFS, as setup by ubiquity, di
** Description changed:
[Impact]
* ZFS pools were created with device names such as /dev/sdX,
/dev/vdX,... However, these names are not stable and may change on each
reboot, leading to an unbootable system.
- * "zpool create" now uses persistent device names with PARTUUID
+ * "zpo
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ * ZFS pools were created with device names such as /dev/sdX,
+ /dev/vdX,... However, these names are not stable and may change on each
+ reboot, leading to an unbootable system.
- * justificatio
** Also affects: ubiquity (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu Focal)
Status: New => Triaged
** Changed in: ubiquity (Ubuntu Focal)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubu
** Changed in: ubiquity (Ubuntu Focal)
Status: New => Triaged
** Changed in: ubiquity (Ubuntu Focal)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875045
Title
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Low
** Also affects: ubiquity (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu Focal)
Status: New => Triaged
** Chang
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ * Ubiquity unmounts everything that could be mounted on the target file
+ system when it starts and on tear down. For ZFS it exports all the
+ pools.
- * justification for backporting the fix to
SRU verification for Focal:
I have reproduced the problem with zsys 0.4.5 in focal and have verified that
the version of zsys 0.4.6 in -proposed fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verifica
SRU verification for Focal:
I have reproduced the problem with zsys 0.4.5 in focal and have verified that
the version of zsys 0.4.6 in -proposed fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verifica
SRU verification for Focal:
I have reproduced the problem with zsys 0.4.5 in focal and have verified that
the version of zsys 0.4.6 in -proposed fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verifica
** Summary changed:
- [Focal] zsys still offer auto snapshotting when reach near full disk space
+ [Focal] zsys still offers auto snapshotting when reach near full disk space
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
SRU verification for Focal:
I have reproduced the problem with zsys 0.4.5 in focal and have verified that
the version of zsys 0.4.6 in -proposed fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verifica
SRU verification for Focal:
I have reproduced the problem with zsys 0.4.5 in focal and have verified that
the version of zsys 0.4.6 in -proposed fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verifica
SRU verification for Focal:
I have reproduced the problem with zsys 0.4.5 in focal and have verified that
the version of zsys 0.4.6 in -proposed fixes the issue.
Note that on a fresh installation, without the update of Ubiquity,
autotrim is not enabled with 0.4.6 and you have to reinstall zsys to
** Tags removed: verification-needed
** Tags added: verification-done
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881536
Title:
Update LastUsed o
No improvements with latest version in groovy (1:13.99.1-1ubuntu7)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881699
Title:
No analog output
To manage notifications about this bug go to:
https:
SRU verification for Focal:
I have reproduced the problem with zsys 0.4.5 in focal and have verified that
the version of zsys 0.4.6 in -proposed fixes the issue.
Note that updating last-used fails with docker but this is a different
issue.
Marking as verification-done
--
You received this bug
SRU verification for Focal:
I have reproduced the problem with zsys 0.4.5 in focal and have verified that
the version of zsys 0.4.6 in -proposed fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verifica
SRU verification for Focal:
I have reproduced the problem with zsys 0.4.5 in focal and have verified that
the version of zsys 0.4.6 in -proposed fixes the issue.
Marking as verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
SRU verification for Focal:
I have reproduced the problem with zsys 0.4.5 in focal and have verified that
the version of zsys 0.4.6 in -proposed fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verifica
SRU verification for Focal:
I have reproduced the problem in focal and have verified that the version of
zsys 0.4.6 and shadow 1:4.8.1-1ubuntu5.20.04 in -proposed fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
** Tags added: verifica
SRU verification for Focal:
I have reproduced the problem with docker.io 19.03.8-0ubuntu1 in focal and have
verified that the version of docker.io 19.03.8-0ubuntu1.20.04 in -proposed
fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
**
Thanks for the patch. In Ubuntu we proposed a patch based on your idea
and also followed the recommendations of Debian's maintainer
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902449) which
resulted in the slightly different implementation.
The package has just been uploaded to groovy.
**
** Changed in: docker.io (Ubuntu)
Status: New => Triaged
** Changed in: docker.io (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/1882942
Title:
mv: c
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => High
** Changed in: linux (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/1881699
Title:
No an
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379671/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881699
Title:
No
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379662/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881699
Title:
No a
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379661/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881699
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379664/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881699
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379665/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
301 - 400 of 33249 matches
Mail list logo
