*** 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
@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.
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
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.
** 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
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.
>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
** 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
-Baptiste Lallement (jibel)
** Changed in: zsys (Ubuntu Focal)
Assignee: (unassigned) => Jean-Baptiste Lallement (jibel)
** Changed in: zsys (Ubuntu Focal)
Milestone: None => focal-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
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
** 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
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
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.
*** 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
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
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:
*** 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.
** 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
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 =>
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
*** 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
*** 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
*** 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
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 @@
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:
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
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
** 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
** 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.
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
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:
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:
** 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
** 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
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:
** 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,
** 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
+ *
** 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.
- *
** 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
** 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
** 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
**
** 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
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
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
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
** 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.
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
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
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
** 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.
** 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
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:
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
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
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
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:
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:
** 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
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:
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
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
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.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379667/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379672/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379669/+files/PulseList.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
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379668/+files/ProcModules.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
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379663/+files/Lsusb-t.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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379666/+files/ProcEnviron.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
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379670/+files/RfKill.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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379660/+files/Lspci.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: "CRDA.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379656/+files/CRDA.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: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379658/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379657/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
After a fresh boot and login, there is no analog output. Only HDMI and
bluetooth are available.
It becomes available when I kill pulseaudio with 'pulseaudio -k' but the
sound indicator only shows 'dummy' output and
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1881699/+attachment/5379659/+files/IwConfig.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
Public bug reported:
After a fresh boot and login, there is no analog output. Only HDMI and
bluetooth are available.
It becomes available when I kill pulseaudio with 'pulseaudio -k' but the sound
indicator only shows 'dummy' output and I cannot control the output from the
sound settings or the
Yes this is the plan together with several fixes and enhancements of
zsys. The SRU work is 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/1880869
Title:
Use persistent device name for
** Changed in: zsys (Ubuntu)
Importance: Undecided => High
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870461
*** This bug is a duplicate of bug 1876334 ***
https://bugs.launchpad.net/bugs/1876334
** This bug has been marked a duplicate of bug 1876334
[Focal] zsys still offer auto snapshotting when reach near full disk space
--
You received this bug notification because you are a member of
** Changed in: ubiquity (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/1875045
Title:
Ubiquity 20.04 exports existing ZFS pools
To manage
I'm working on a patch to only unmount pools that we've mounted as part
of the installation to prevent unmounting pools that don't belong to us.
Regarding your other issue, it is possible that using /dev/sdX for vdev
causes it. Depending on the type of block device these names are not
stable and
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) => 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/1875045
Title:
Ubiquity 20.04 exports existing
** Description changed:
- ZFS pools are currently created with device names. However, this name is not
stable and may change.
+ ZFS pools are currently created with device names such as /dev/sdX,
/dev/vdX,... However, this name is not stable and may change on each reboot.
"zpool create" must
lpha amd64 (20140520)
SourcePackage: ubiquity
UpgradeStatus: Upgraded to groovy on 2018-03-24 (794 days ago)
** Affects: ubiquity
Importance: Unknown
Status: Unknown
** Affects: ubiquity (Ubuntu)
Importance: High
Assignee: Jean-Baptiste Lallement (jibel)
Status: In Progress
*
sorry, wrong bug.
** Changed in: gfxboot-theme-ubuntu (Ubuntu)
Status: Opinion => 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/1880394
Title:
20.10 iso syslinux menu screen
** Changed in: gfxboot-theme-ubuntu (Ubuntu)
Status: Fix Released => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880394
Title:
20.10 iso syslinux menu screen unreadable
To manage
The bug automagically fixed itself. Setting to incomplete until it
expires or can be reproduced.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Rationale]
ZFS module of docker creates many snapshots under
/ROOT/machineid/var/lib/. These snapshots are processed by zsys and
lead to timeout.
This patch migrates the snapshots created by docker under the persistent
dataset /var/lib/docker/ so they are
Public bug reported:
[Rationale]
ZFS module of docker creates many snapshots under
/ROOT/machineid/var/lib/. These snapshots are processed by zsys and
lead to timeout.
This patch migrates the snapshots created by docker under the persistent
dataset /var/lib/docker/ so they are scanned and then
301 - 400 of 32050 matches
Mail list logo
