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
*** 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
Rationale: this is a regression on X11 in eoan (maybe not worth fixing
for it right now), but at least, should be fixed in focal IMHO
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
- Open some non dbus activated apps (so, not terminal for instance) in your dock
- Kill the shell with SIGKILL
- Applications are being killed with the Shell being killed, apart from the
dbus activated ones.
This wasn't the case before 19.10 on X11. (caused by dbus user
** Also affects: grubzfs-testsuite (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: grubzfs-testsuite (Ubuntu)
** Also affects: grub2 (Ubuntu Eoan)
Importance: Undecided
Status: New
** No longer affects: grubzfs-testsuite (Ubuntu Focal)
--
You received this
** Also affects: grub2 (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: grubzfs-testsuite (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: grub2 (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: grubzfs-testsuite (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: grub2 (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: grubzfs-testsuite (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, but I have to close this bug as invalid. It lacks a lot of informations
to be able to debug what went wrong after the upgrade:
- did the upgrade failed for some reasons, but was rebooted?
- did you try starting without quiet splash and see where the boot process is
getting stuck?
*** This bug is a duplicate of bug 1848399 ***
https://bugs.launchpad.net/bugs/1848399
This is a dup, and interestingly, we just fixed this (but adding tests
before pushing the SRU or to focal :)).
However, thanks to your backlog, we finally know where the "This" is
coming from and can fix
zsys/0.2.2 autopkgtests were already failing, so not a regression.
Confirming that installing zsys from -proposed fix the 2 previous use
cases.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of
** Changed in: zsys (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
** Changed in: zsys (Ubuntu Eoan)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: zsys (Ubuntu)
Status: Fix Released => 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/1850052
Title:
installing zsys breaks desktop login
To manage notifications
(Uploaded to focal-proposed)
** Changed in: zsys (Ubuntu)
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/1850052
Title:
installing zsys breaks desktop
** Description changed:
+ [Impact]
+ After installing zsys on 19.10, you can't log in in your desktop. Removing it
won't fix the issue.
+
+ [Test Case]
+ Test A: (migrating broken people)
+ 1. Install 19.10 using experimental ZFS disk partitioning and reboot on
installed system.
+ 2. sudo apt
Indeed, this is planned for later, but not as long as it's in its
current experimental status.
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
zsys is handling this (adduser will try to execute it and creates a
dataset, and if it can't, it fallbacks to traditional directory
creation.
zsys isn't installed by default on 19.10 but should be on 20.04 LTS, so
I encourage you to install and test it! Thanks :)
I'll have to mark the bug as
Thanks for digging into this and finding your root cause!
I'm really wondering what is causing this additional \r on that variable
compared to a standard installation, with multiple kernels and initrds,
which doesn't get this \r. Do you have any specific grub configuration
in /etc/default/grub*
(settings as incomplete until you confirm this is the issue)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849179
Title:
canmount property switches to noauto in user's home dataset
To manage
I think the issue is that you installed before the final release, as the
properties were renamed from `org.zsys` to `com.ubuntu.zsys` for
property. As zsys isn't seeded by default, we were told to not migrate
the handful of users having installed a pre-released.
Can you confirm that canmount is
waow, do you have features enabled on some pools not supported in our
ZFS 0.8.1 version? Would be interesting to know.
|| true is a little bit too much without filtering what was imported. We
can maybe force at least importing a bpool and rpool (whatever it is) to
ensure that grub will install a
I think this is what is creating this issue. Please attach the logs I asked
above, and also a zfs list + zpool list then :)
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848399
Title:
(The issue is only on grub, marking the other tasks as invalid and the
grub one as incomplete until we get feedback)
** Changed in: grub (Ubuntu)
Status: New => Incomplete
** Changed in: zsys (Ubuntu)
Status: New => Invalid
** Changed in: ubiquity (Ubuntu)
Status: New =>
Thx! Can you set -x on 10_linux_zfs and direct stderr the output to some
log file that you attach here so that we can see where 10_linux_zfs is
dying when running update-grub?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Andreas, confirmed as fixed, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847970
Title:
20191012 does remove zfs-initramfs on targetted system
To manage notifications about this bug go
@Daniel, however, this creates "interesting" issues, like when you have a
pulseaudio server on the network. Even if your laptop is connected before the
user session, it will always switch to the server, even if you reverted on this
decision at previous reboot.
However what I describe above
** Summary changed:
- Screen reader isn't enabled on user session after installation
+ Screen reader isn't enabled on login screen or user session after installation
** Description changed:
ISO 20191014
After enabling the screen reader for an installation:
- - the screen reader is
Public bug reported:
ISO 20191014
After enabling the screen reader for an installation:
- the screen reader is enabled on GDM
- it's not enable on the user's session though.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
wrong shortcut, it's actually super+alt+s, my bad
** Tags removed: iso-testing
** Package changed: ubiquity (Ubuntu) => null-and-void
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848141
Title:
Public bug reported:
ISO 20191014
The screen reader isn't started when pressing ctrl+alt+s on maybe-ubiquity or
in the live session.
No crash file on /var/crash.
Note that setting it in isolinux works once booted on live session or
maybe-ubiquity. Only the shortcut is broken.
** Affects:
apport information
** Attachment added: "UbiquityDebug.txt"
https://bugs.launchpad.net/bugs/1847970/+attachment/5296922/+files/UbiquityDebug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UbiquityDm.txt"
https://bugs.launchpad.net/bugs/1847970/+attachment/5296923/+files/UbiquityDm.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847970
apport information
** Attachment added: "UbiquitySyslog.txt"
https://bugs.launchpad.net/bugs/1847970/+attachment/5296925/+files/UbiquitySyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "UbiquityPartman.txt"
https://bugs.launchpad.net/bugs/1847970/+attachment/5296924/+files/UbiquityPartman.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1847970/+attachment/5296921/+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: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1847970/+attachment/5296920/+files/Dependencies.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 eoan ubiquity-19.10.19 ubuntu
** Description changed:
Double checked iso version + ubiquity version (19.10.19):
1. On live:
- zfs-initramfs and zfsutils-linux are both installed
- the ubiquity removal file (live - desktop) under /casper
Public bug reported:
Double checked iso version + ubiquity version (19.10.19):
1. On live:
- zfs-initramfs and zfsutils-linux are both installed
- the ubiquity removal file (live - desktop) under /casper contains both
packages.
2. On installed system:
- ubiquity kept zfsutils-linux, but I can't
** Summary changed:
- The experimental zfs "Write to change disks" shows an ext4 partition will be
created
+ zfs "Write to change disks" message prints that an ext4 partition will be
created
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
(in unapproved)
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Committed
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: grubzfs-testsuite (Ubuntu)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu)
Status: New => Fix Committed
** Changed in: grubzfs-testsuite (Ubuntu)
Status: New =>
Subscribed infinity for tracking the release. Look at the commit why
it's not (yet) added to live-common.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847739
Title:
Make zfs-initramfs and
Here is the change to the ubuntu desktop seed as an example:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/ubuntu/commit/?h=eoan=00192c2d530e6b9a636ac0dcd754c4a80a2319e5.
Ubiquity upload is on the way.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Move those 2 to the live seed to have them available in the installer.
Mark them then manually installed in the installer if needed. Then,
ubiquity will purge them if not used.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Affects:
Public bug reported:
For a smoother transition for people who disabled and enabled secure
boot later on, Steve mentioned to always create the ESP partition.
We can then install grub into the ESP.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received
Public bug reported:
While technically correct, this is confusing to the user. This should be
fixed for 20.04 as hard to fix on 19.10.
Meanwhile, we should release note this for this experimental support.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
You
Public bug reported:
As we are not going to own in the end org.zsys, move our identifier tags
to com.ubuntu.zsys.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: zsys
Do you have a kernel installed on your targetted system? (check its /boot)
It looks like a dup of bug #1847457 to me. Setting as incomplete for now.
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Ubuntu Desktop 20191008
/cdrom is empty in the live session. As a result there is no kernel on
the installed system and can't boot.
It seems to be a regression from
https://launchpad.net/ubuntu/+source/casper/1.423.
** Affects: casper (Ubuntu)
Importance: Critical
** Also affects: ubuntu-mate-meta (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/1847431
Title:
Installing ZFS without network is failing
To
Public bug reported:
We need to:
* seed zfs-initramfs
* remove apt install from ubiquity zfs script.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-meta
We wrote on another bug report BertN45 to not upgrade your bpool. Only
power users will use zpool status command to list and we expect them to
know the implication.
I think I'll retarget this bug for preventing bpool upgrade.
** Summary changed:
- Confusing zpool status in Ubuntu 19.10
*** This bug is a duplicate of bug 1847228 ***
https://bugs.launchpad.net/bugs/1847228
** This bug has been marked a duplicate of bug 1847228
Installer crashes at partitioning stage
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: grub-installer (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/1847228
Title:
Installer crashes at partitioning stage
To manage
Only zsys systems will have rollback, we had to revert rollback in pure
ZFS systems as per this package upload:
https://launchpad.net/ubuntu/+source/grub2/2.04-1ubuntu7.
Indeed, we need to release note that people shouldn't upgrade the bpool
as grub isn't able to read newer zfs pool versions.
--
We should refresh the testsuite as well.
** Also affects: grubzfs-testsuite (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/1845913
Title:
Public bug reported:
Disable history entry on pure zfs systems as we identified multiple
issues due to the mount generator in upstream zfs which makes it
incompatible. Don't show history for now.
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Affects:
Public bug reported:
There is a race between empty cache file for the mount generator and fstab
which contains /boot/grub.
With zfs on root, the generator is the only solution to avoid races. However in
0.8 it misses cache invalidation (when rollbacking or booting on other
datasets).
This is
Marking the zfs-linux task as won't fix after looking more deeply about
cause/consequences of forcing -f on every boot:
- zfs 0.8, as told previously, tag with which system the pool was associated
with and refuse to import previously unexported pool, as they can still be
attached to any systems
** Also affects: zfs
Importance: Undecided
Status: New
** Description changed:
- If /var/lib is a dataset not under /ROOT/, as proposed
- in the ubuntu root on zfs upstream guide
- (https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS), we end up
- with a race where some
Public bug reported:
If /var/lib is a dataset not under /ROOT/, as proposed
in the ubuntu root on zfs upstream guide
(https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS), we end up
with a race where some services, like systemd-random-seed are writing under
/var/lib, while
** Summary changed:
- [FFe] Ubiquity with zsys install option
+ [FFe] Ubiquity with zfs install option
** Description changed:
Part of the 19.10 feature announcement is zfs experimental support in
the installer (https://ubuntu.com/blog/enhancing-our-zfs-support-on-
Can you try to reproduce an upgrade without your 40_custom file?
I don't think your pool manual upgrade has any link to this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843222
Title:
Old Linux
The issue seems to be related to a change in ZFS 0.8 initramfs script.
The initramfs script for ZFS does a normal ZFS import.
ZFS import now forces to export a pool before importing it back again on a
different system. This is a security feature to ensure the same pool isn't
imported on two
+1 on the MIR side
** Changed in: rygel (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/1786489
Title:
[MIR] rygel
To manage notifications about
+1 on the MIR side
** Changed in: gupnp-dlna (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/1785649
Title:
[MIR] gupnp-dlna
To manage notifications
+1 on the MIR side
** Changed in: gupnp-av (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/1785629
Title:
[MIR] gupnp-av
To manage notifications about
The upgrade failed, in your logs, you have:
"/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.2.0-15-generic
I: The initramfs will attempt to resume from /dev/sda2
I: (UUID=bf02ddd4-8d65-40d6-ab24-4fc8a5673dc6)
I: Set the RESUME variable to override this.
Thanks a lot Łukasz! The MIR is available at
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1839271, the MIR
part has been acked, it's pending a security review for now.
Anyway, let's proceed with this so that we can test it early in the
wild, thanks again!
--
You received this bug
attaching shadow build logs
** Attachment added: "shadow_4.5-1.1ubuntu4_amd64.build"
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1842902/+attachment/5287475/+files/shadow_4.5-1.1ubuntu4_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks for testing the upgrade to 19.10. The only reason you would boot
with an older version of a kernel and zfs itself is due to your update
between 19.04 to 19.10 failed. Can you share the upgrade logs
/var/log/upgrade content and /var/log/dist-upgrade?
The weird part is that
Hey Alex! Thanks for looking at it.
Sure, I've added some checks for open/dup2 (and exiting the child).
On execl, I've kept the similar logic than the rest of the code, meaning:
- don't check for execl return value.
- if something bad happen, execl returns.
- we go on the next line which is a
Public bug reported:
Part of the zsys spec is creating/associating one user dataset for each
HOME user.
As zsys is an official experimentation for 19.10, we would like to
include this feature in a safe way, and reachable for any tool creating
users (adduser, gnome-control-center, ubiquity…).
Hey Seth,
While I agree with this goal, I don't feel this is realistic without a focused
effort within the distro itself as a global goal as I explained in detailed in
my answer:
- most of those deps are shared between snapd, juju, ubuntu-report and zsys at
least (like the yaml config parser).
This is a regression for our vast majority of users using the normal
ubuntu product and quite visible one, I wouldn't put it as low.
** Changed in: gnome-shell (Ubuntu)
Importance: Low => High
** Changed in: mutter (Ubuntu)
Importance: Low => High
--
You received this bug notification
Note that the fix is a random crash fix. I didn't get the crash myself
but upstream applied the fix upstream, which is supposed to remove the
crash.
As testing it, I didn't get any new crash at least, marking as
verification-done.
** Tags removed: removal-candidate verification-needed
Public bug reported:
GNOME Shell & mutter on 3.33.91
When pressing volume up or down on Xorg and keeping it pressed, only the first
key event is sent, so the volume only goes up or down once, and doesn't scale
up/down as long as you keep the button pressed.
ProblemType: Bug
DistroRelease:
** Changed in: rygel (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/1786489
Title:
[MIR] rygel
To manage notifications about this bug go to:
Now that all remarks have been addressed, I'm happy to give an official
+1 from the MIR team side.
** Changed in: rygel (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the review Christian! Sorry for the delayed answer, I'm just back
from holidays :)
Thanks also for the details and summary. I think I have some resolved, some
questions and some with no actions. I copy this back here so that we can track
them. Let me know how this feels.
[Summary]
401 - 500 of 16202 matches
Mail list logo
