Thanks for the head’s up baudlord!
I think there are 2 things:
- the high CPU usage on garbage collection
- you have a lot of datasets (probably related to docker, can you confirm?)
Definitively, your override.conf will be of help to have logs the next
time you get this high CPU so that we can
signed) => 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/1879473
Title:
hundreds of snapshots created by docker zfs lead to zsys timeout
To manage notifications about th
** Description changed:
[Rationale]
- ZFS module of docker creates many snapshots under /var/lib/. These
snapshots are processed by zsys and lead to timeout.
+ ZFS module of docker creates many snapshots under
/ROOT/machineid/var/lib/. These snapshots are processed by zsys and
lead to
An instance of the issue:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867542 (not
dupping because GRUB needs to be fixed there)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876334
Title:
The ZSys part of the issue (garbage collection not being agressive
enough when reaching bpool or rpool size limit) is handled on bug
#1876334.
I’ll just add a reference there and remove the ZSys task instead of
dupping so that the foundation team can handle the grub side of it.
** No longer
It’s not expected of course, but we tried to stick to POSIX syntax to
avoid breakages.
However, reading
https://pubs.opengroup.org/onlinepubs/009695399/utilities/echo.html, it
seems that escape sequences in echo are not POSIX: "It is not possible
to use echo portably across all POSIX systems
Thanks for reporting this bug and help making ubuntu better!
I doubt the issue is due to anything you have made on snapshots.
echo from dash (our default /bin/sh) has no -e option and \t are interpreted as
expected.
echo from bash has this -e to interpret special characters.
Can you tell what’s
Great to hear John! Thanks for confirming and thanks to Richard for the
patch.
I’m happy to SRU it to focal once it’s proposed upstream. (Keep me
posted Richard, you can drop a link here and I will monitor)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On an installed packaged system, the files are in different directories
(and don’t have the .in extension as they have been built with the
prefix replacement). Their names and locations are:
/lib/systemd/system/zfs-mount.service
/lib/systemd/system-generators/zfs-mount-generator
--
You received
Ack, committed upstream FYI and planned for next ZSys release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875420
Title:
zsys causes apt install to output a confusing message
To manage
Your patch makes sense Richard and I think it will be a good upstream
candidates. In all approaches you proposed, this is my prefered one
because this is the most flexible IMHO.
Tell me when you get a chance to test it and maybe John, you can confirm
this fixes it for you?
--
You received this
May 01 10:53:13 mcp systemd[1]: boot.mount: Mount process exited, code=exited,
status=1/FAILURE
May 01 10:53:13 mcp systemd[1]: boot.mount: Failed with result 'exit-code'.
and your ZFS mounts confirms that bpool isn‘t mounted.
How old if your installation? It seems to be from the 1st of March.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2716
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2716
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2716
Importance: Unknown
Status: Unknown
--
You received this bug
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2715
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2715
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2715
Importance: Unknown
Status: Unknown
--
You received this bug
Public bug reported:
As stated on bug #1876052, the default acceleration mode option is none
of the 3 nvidia settings option.
It’s displayed as "Performance mode" when you launch it for the first time,
however:
- default launch is Intel (so no performance mode)
- there is a "Use dedicated card"
Public bug reported:
Fresh install of 20.04 LTS with nvidia binary driver from our archive.
(dual Intel/Nvidia setup)
No setting change has been done. The card supports "On demand".
Tested with Firefox (about:support) and Chrome (config:cpu). Both are showing
the same result:
- default launch
Public bug reported:
I think the menu should rather be a checkbox which pins/unpins using a
dedicated card option. That way, people can always launch, for instance,
their browser with nvidia hardware acceleration for instance.
Something to discuss upstream of course.
ProblemType: Bug
Public bug reported:
Once you select manually performance mode in nvidia-settings, GNOME
Shell shouldn’t display "Use dedicated card option".
Launching directly any app, in this mode, starts your application using
the nvidia card already.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
Public bug reported:
The client can timeout while the daemon is still doing a lot of active
work.
There are 3 cases to take into account:
- daemon not started: give a timeout for the daemon to start before the client
exits. Ideally, we would pulse back to the client, but the entrypoint isn’t
Thanks for your suggestion!
Actually, zsys does it a little bit differently:
- snapshots (state save) are taken everytime you modify your system by apt or
other things.
- In addition to this, everytime you reach graphical.target, we stamp the
current state (which can also be a clone) as the
True that we can craft a better message or maybe prepend another one
just before the Updating GRUB menu (which will be reused in diverse part
of the stack).
Maybe something like:
INFO Taking into account the new system snapshot
INFO Updating GRUB menu
would work? any suggestion appreciated
**
Confirming
** Changed in: ubiquity (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856410
Title:
ubiquity prompts for a MOK password that it then does
Hey,
It’s a little bit hard to debug as you opened the bug without using
ubuntu-bug tools which collects a lot of information (you can run
apport-collect to attach more of them).
Some tracks of though to get this going:
- do you mind checking that zfs-initramfs and zfsutils-linux are both
I just got it as well.
Did a first normal and successful install with ZFS. Booted successfully
Reused the disk with an ext4 "Erase disk" installation -> failed.
This is using the image 20200423.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug
** Package changed: zsys (Ubuntu) => gnome-settings-daemon (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874191
Title:
Brightness setting too high
To manage notifications about this bug
Public bug reported:
When doing an entire disk installation, ubiquity (showing up partman output) is
showing incomplete partition layout.
It’s displaying:
- partition #1 of Virtual disk 1 (vda) as
- partition #5 of Virtual disk 1 (vda) as ext4
(see screenshot attached)
-> Note the empty first
Public bug reported:
There is no more check disks for detects entry.
The QA tracker should be updated as this is intended IIRC.
** Affects: live-build (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
d => High
** Changed in: shadow (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Also affects: shadow (Ubuntu)
Importance: Undecided
Status: New
** Also affects: adduser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
There is no more zsys integration for this part of the stack.
Fix regression from disco due to useradd merge with debian.
** Affects: zsys (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Setting to incomplete until we get more feedback
** Changed in: zsys (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870461
Title:
zsysd uses more than
** Changed in: zsys (Ubuntu)
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/1871550
Title:
Bug with apport report
To manage notifications about this bug go to:
** Changed in: zsys (Ubuntu)
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/1871576
Title:
apport hook test 2
To manage notifications about this bug go to:
Public bug reported:
Test 2
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: zsys 0.4.2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu22
Architecture:
Public bug reported:
Test bug with apport content
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: zsys 0.4.2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
** Changed in: zsys (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870057
Title:
Ensure we collect failed reverted state
To manage notifications
** Description changed:
- Untag them as part of GC so that we can clean them up later
+ Ideally, we would untag them as part of GC so that we can clean them up
+ later. However, those can be linked to states on other pools with same
+ pool name than targetted one, and it will be hard to match
Public bug reported:
Apport is trying to bring terminator to main:
https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
We agreed that terminator isn’t desirable in main and needs to be fixed.
bdmurray told he will look at it.
** Affects: terminator (Ubuntu)
Importance:
** Changed in: zsys (Ubuntu Focal)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870052
Title:
warning when mountpoint source is set to default
To manage
** Changed in: zsys (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870054
Title:
warning issues for swap dataset mounpoint source property being ""
To
Hum, I’m puzzled, the command ended correctly, right?
---
DEBUG [[c16b1021:d77ab6fb]] No more user states left for pass #2.
DEBUG [[c16b1021:d77ab6fb]] Unassociated user datasets GC
DEBUG Reset idle timeout to 1m0s
DEBUG Idle timeout expired
DEBUG
Hey David,
Thanks for reporting this bug and help making ubuntu better.
The issue was in the installation setup in the images produced before beta was
out. (The ones from the 2nd).
Those installations are really complex to fix and it’s better to reinstall
using the beta official image (the
None, just don’t upgrade at worst before doing the operation on Monday
:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870461
Title:
zsysd uses more than half of CPU and disk IO
To manage
Great! I'll look on Monday.
But if you don't mind, please keep the broken state in case further
testing is needed. As long as you keep zsys disabled, you should be
fine!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Excellent, thanks!
3. shows up that you are having a broken installation (because you
installed in the bad period of previous days before beta). Today’s image
is good, but before you reinstall (reverting to a good state is quite
challenging, see my instructions on
Thanks for reporting this bug and sorry you have an issue with zsys.
It seems that zsys is going crazy in an infinite loop, I would be interested to
know why:
1. can you try running manually "sudo zsysd -vv" and see paste the logs here?
Do you have the spinning loops in that way as well?
2. if
Fixed at the same time that I fixed bug #1868523
** Changed in: zsys (Ubuntu)
Status: New => Fix Committed
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: ubuntu-report (Ubuntu Focal)
Status: Confirmed => 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/1870084
Title:
ubuntu-report ftbfs in focal (armhf & arm64)
To
See my previous comment: this is only related to zfs-linux with the
version I mentioned. Also, we didnt’ make any change to grub for ZFS
since 26 February, and if you have an empty grub.cfg, this may be due to
other bugs, like multiple rpool/bpool, which isn’t what this one was
about. Ensure that
This is probably because your bpool is not in the zfs cache file.
Either reinstall from the beta image which has a fix in the installer, or:
- clean up any files and directories (after unmounting /boot/grub and
/boot/efi) under /boot (not /boot itself)
- zpool import bpool
- zpool set cachefile=
** Changed in: zsys (Ubuntu)
Status: Confirmed => Fix Committed
** 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.launchp
Public bug reported:
Similar to https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1870052,
the source can be "" for canmount. It seems to happen on swap dataset.
We should evaluates what we consider it (maybe inherited to avoid
setting it)
** Affects: zsys (Ubuntu)
Importance: Undecided
Public bug reported:
Two kind of datasets we should collect in the GC:
- root and children datasets if reverting failed (initramfs cloned -> failed in
generator)
- states that don’t have a valid LastUsed
To evaluate:
- main dataset for a machine is never cleaned up, so ok
- only consider (and
Public bug reported:
Untag them as part of GC so that we can clean them up later
** Affects: zsys (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- Run that as part of GC so that we can clean them up later
+ Untag them as part of GC so that we can clean them up
Public bug reported:
This is a valid source that we should consider "inherit".
Example in log: https://github.com/ubuntu/zsys/issues/62 and
https://gist.github.com/nirvdrum/67b9e496b215276538cbcf7bce6d3a4b.
The bet is that it’s the case when the pool itself doesn’t have any
mountpoint set. (and
Thanks for your bug report! This is now fixed in zfs-linux
0.8.3-1ubuntu10 in focal.
** Package changed: zsys (Ubuntu) => zfs-linux (Ubuntu)
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Right, this is expected. We should just remove the Saving state message
here and don’t issue an error visible to the user.
** Summary changed:
- "ERROR couldn't save system state: Current machine isn't Zsys, nothing to
create"
+ "ERROR couldn't save system state: Current machine isn't Zsys,
Is your system a zfs one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868523
Title:
"ERROR couldn't save system state: Current machine isn't Zsys, nothing
to create"
To manage notifications
Hey Balint. I just added the task post ZFS upload (the upload was
yesterday and I added the task this morning) so indeed, there is some
work needed, part of it being in systemd.
Basically, systemd isn’t capable of mounting datasets when pool names are
duplicated on a machine
zfs-mount-generator
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867007
Title:
zfs-initramfs fails with multiple rpool on separate disks
Retargetting to correct project with tag
** Package changed: zsys (Ubuntu) => gnome-disk-utility (Ubuntu)
** Tags added: zfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869444
Title:
Task
Hey BertN45,
as stated on the other bug report, those aren’t necessarily snapshots as
clones can be a state. Using the terminology snapshots will be confusing
like advanced users like you are.
Manual snapshots on system state saving won’t be considered as a valid
reverting state to zsys, as you
Just an additional note: user system states are revertable way more
safely and are useful checkpoint for the users. This is why we consider
manual snapshots ok on them and will present them for revert/cherry-
pick.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850130
Title:
zpools fail to import after reboot on fresh install of eoan
Sorry BertN45, but you are using a development version and should know
what you do as such.
First, the garbage collection of snapshots is just entering ubuntu in
the next few hours (remember that you are using a development version
currently, not everything was hooked up/bug fixed yet), so most
** Changed in: zsys (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867067
Title:
ERROR context deadline exceeded
To manage notifications about this
Everything looks good with this upload (well, very very small nitpick: no
trailing comma on recommend, but I will take a breath and survive :)).
Ack from the MIR perspective
** Changed in: gamemode (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you
Closing right now as no new feedback report. Feel free to reopen if this
didn’t fix the issue.
** Changed in: zsys (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for reporting this bug and help making ubuntu better.
The local cache (of software-updater) isn’t refreshed yet but will be
for the release. Note that the zsys command doesn’t exist since the
split is daemon (zsysd) / client (zsysctl).
Closing the zsys task of bug as invalid as there is
** Changed in: zsys (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867067
Title:
ERROR context deadline exceeded
To manage notifications about this bug go
(Not bad in the way that the service-side ends up, just not report the
status to the client)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867067
Title:
ERROR context deadline exceeded
To manage
Hey Alan, I think this is due when rebuilding the grub entry.
How long update-grub is taking?
(Note: we delayed to post-apt in the incoming release and should increase the
30s timeout),
If I’m correct, it’s not bad, but we should fix it with a longer timeout.
--
You received this bug
Ack on both. Simple configuration files, simple packaging and build
system. All good +1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862776
Title:
[MIR] alsa-ucm-conf & alsa-topology-conf (b-d of
$ ./change-override -c main -S alsa-ucm-conf
Override component to main
alsa-ucm-conf 1.2.2-1 in focal: universe/misc -> main
alsa-ucm-conf 1.2.2-1 in focal amd64: universe/libs/optional/100% -> main
alsa-ucm-conf 1.2.2-1 in focal arm64: universe/libs/optional/100% -> main
alsa-ucm-conf 1.2.2-1 in
$ ./change-override -c main -S zsys
Override component to main
zsys 0.3.3 in focal: universe/admin -> main
zsys 0.3.3 in focal amd64: universe/admin/optional/100% -> main
zsys 0.3.3 in focal arm64: universe/admin/optional/100% -> main
zsys 0.3.3 in focal armhf: universe/admin/optional/100% -> main
tepl 4.3.1-1 in focal: universe/misc -> main
gir1.2-tepl-4 4.3.1-1 in focal amd64: universe/introspection/optional/100% ->
main
gir1.2-tepl-4 4.3.1-1 in focal arm64: universe/introspection/optional/100% ->
main
gir1.2-tepl-4 4.3.1-1 in focal armhf: universe/introspection/optional/100% ->
main
amtk 5.0.2-1 in focal: universe/misc -> main
gir1.2-amtk-5 5.0.2-1 in focal amd64: universe/introspection/optional/100% ->
main
gir1.2-amtk-5 5.0.2-1 in focal arm64: universe/introspection/optional/100% ->
main
gir1.2-amtk-5 5.0.2-1 in focal armhf: universe/introspection/optional/100% ->
main
** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu Bionic)
Assignee: Didier Roche (didrocks) => (unassigned)
** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu Cosmic)
Assignee: Didier Roche (didrocks) => (unassigned)
--
You received this bug notification becau
can follow up on
the rest meanwhile.
** Changed in: gamemode (Ubuntu)
Assignee: Didier Roche (didrocks) => Canonical Security Team
(canonical-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Perfect! Ack for me then, feel free to ping me or promote directly once
the new gedit hit the archives. Thanks
** Changed in: tepl (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ack, fine by me. +1 on promoting once the new gedit lands.
** Changed in: amtk (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862174
Title:
[MIR] amtk
Strong packaging practice: despite the missing trailing comma, dh has
fail-missing, la files are removed, dh_autoreconf with --as-needed and symbols
files present with makeshlibs with -c4. Hardening flags are enabled.
The code was part of the upstream gedit code, so OK.
Testsuite is executed
** Changed in: gamemode (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853830
Title:
[MIR] gamemode
To manage notifications about this bug go to:
Depends on amtk (MIR bug #) -> Rejected, miss the other ref :p
Ok, more seriously:
Strong packaging practice: despite the missing trailing comma, dh has
fail-missing, la files are removed, dh_autoreconf with --as-needed and symbols
files present with makeshlibs with -c4. Hardening flags are
Good packaging practice: despite the missing trailing comma, dh has
fail-missing, la files are not shipped, upstream is called with --as-
needed. Hardening flags are enabled.
1/ One lintian warning that I’m fine to ignore (but will be better to
fix it in lintian or have an override): W: gamemode
Override component to main
fonts-urw-base35 20170801.1-3 in focal: universe/misc -> main
fonts-urw-base35 20170801.1-3 in focal amd64: universe/fonts/optional/100% ->
main
fonts-urw-base35 20170801.1-3 in focal arm64: universe/fonts/optional/100% ->
main
fonts-urw-base35 20170801.1-3 in focal
Promotion done.
Till, as ghostscript doesn’t need any promotion if I‘m correct, I let you close
the bug in the changelog for your corresponding ghostscript upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Promoted
$ ./change-override -c main -t openjpeg2
Override component to main
openjpeg2 2.3.1-1 in focal: universe/misc -> main
Override [y|N]? y
1 publication overridden.
$ ./change-override -c main libopenjp2-7
Override component to main
libopenjp2-7 2.3.1-1 in focal amd64:
No worry! I'll promote it once we have something pulling it in the
archive
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/711061
Title:
[MIR] openjpeg2
To manage notifications about this bug go to:
** Changed in: openjpeg2 (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/711061
Title:
[MIR] openjpeg2
To manage
** Changed in: gamemode (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/1853830
Title:
[MIR] gamemode
To manage notifications ab
for reference, this might be a duplicate of 1848856 as the error message
is one of the fix we made.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855605
Title:
ubuntu 19.10 zfs on root, grub2
One last thing: I think we should test this on rotational disk and
assess the performance impacts before pushing it as a default. This will
give us a good baseline to decide if this should be pushed or if we need
to add even more warnings on the ZFS install option.
--
You received this bug
Thanks Richard for digging in, the performance comparison and the valuable
upstream feedback and pointers.
Good catch about retrieving the master key written in old blocks with the
previous (fix) passphrase even if changed later on. It seems that trimming
could help. Do you think that we should
This is to be expected, zsys isn't installed on your system:
"Package: zsys (not installed)"
Try installing zsys and this shouldn't happen. Then, your annotations
will be migrated to new annotations automatically.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Now that the 0.3 series is published, it has the finale structure:
- split between daemon and server. Calls are done via GRPC over an Unix socket.
- use polkit for authorization with various levels of actions. Full spec is at
*** This bug is a duplicate of bug 1848399 ***
https://bugs.launchpad.net/bugs/1848399
** This bug has been marked a duplicate of bug 1848399
update-grub fails if a pool fails to import
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1853864 ***
https://bugs.launchpad.net/bugs/1853864
** This bug has been marked a duplicate of bug 1853864
Installer crashes everytime, ZFS selected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Can you try running "zfs get all " on all your USERDATA sets? I
wonder if an annotation hasn't disappear while you were playing/adding
the SMB sharing.
--
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 1848399 ***
https://bugs.launchpad.net/bugs/1848399
The extra } is a consequence of multiple things, like no good recover
found, or invalid linux entry data. I guess your bug should rather be a
duplicate of bug #1848856.
In any case, both of them are fixed
301 - 400 of 14912 matches
Mail list logo
