Olivier, I am not sure what is the reasoning here.
That you obviously want to land this in a non-LTS version has nothing to
do with the fact the base product is not ready and that the change was
announced unacceptably late here. The Flutter-based installer is a nice
example. You can obviously
Honestly, to announce this one month before release without feature
parity, is baffling.
As it looks this puts us in a position where we probably have to stop
supporting Ubuntu after more than a decade, as the available browsers
can't work with our Belgian Identity Card.
And this because of a
See https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918080
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881442
Title:
grub-initrd-fallback.service should RequiresMountsFor=/boot/grub
To
Public bug reported:
Since a few weeks update-grub was no longer detecting my root-on-zfs
install. This system does not follow the bpool/rpool logic as it got
installed a long time ago.
I was able to pinpoint the issue to this part of the 10_linux_zfs
script:
if [ -n "$(ls ${candidate_path}
I have run into this with root on zfs. If for some reason the grub
directory with grubenv is created on the root pool, then update-grub
will no longer work (10_linux_zfs will no longer find valid /boot
directories for the root fs).
I would definitely tune this to avoid that as trying to boot into
This should no longer be the case? Everything in /etc/zfs/zfs-
list.cache/* should be dynamically handled by systemd, does it contain
entries for your pool?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Mainline apparently does not have zfs modules, this is a root-on-zfs
system.
However I tried 5.4.0-65 from the repository, which indeed does not show
this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I can confirm this problem: https://askubuntu.com/questions/1306700
/fixing-gpu-hang-caused-by-i915-driver
Symptom: unable to launch any application after login on to the system,
login screen etc works fine. The system thus becomes completely unusable
for regular users. I
On my (upgraded from LTS) Groovy install:
systemctl status sssd.service
● sssd.service - System Security Services Daemon
Loaded: loaded (/lib/systemd/system/sssd.service; enabled; vendor preset:
enabled)
Active: failed (Result: exit-code) since Wed 2020-12-30 01:42:46 CET; 9h
ago
Public bug reported:
The systemd file that was shipped in focal contains:
...
[Service]
Type=forking
ExecStart=/usr/lib/virtualbox/vboxweb-service.sh start
PIDFile=/run/vboxweb.pid
...
But the script that it calls uses a different file for PID:
cat /usr/lib/virtualbox/vboxweb-service.sh:
...
Thank you for your detailed reply, I really appreciate it and I totally
understand your reasoning. Also, many thanks for a great 20.04 release
and congratulations to yourself and the team for your know-how as well
as your attitude. It's refreshing.
Just to illustrate my use case a bit further.
-
Public bug reported:
I have always relied on snapshots taken during boot when rolling back a
system since I started using zfs years ago, because I know the system is
in a consistent state while booting (no open files, no VM or containers
running etc.). With zsysctl this has become even easier.
I
As kernels 5.2.0-x will bring zfs 0.8.x to Bionic LTS, I'd like to draw
some attention to this request. People will get the 0.8.x zfs module via
HWE but won't be able to do much with the major new features without the
userland tools.
I tried to install the debs from Eoan, but they require a
** Changed in: nvidia-graphics-drivers-340 (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/1838867
Title:
Bionic HWE kernel 5.0.0.23 breaks nvidia driver
** Changed in: linux (Ubuntu)
Status: Fix Committed => 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/787210
Title:
ath9k drivers freeze the system when changing state
To manage
Issue no longer present with kernel 5.0.0-25.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838867
Title:
Bionic HWE kernel 5.0.0.23 breaks nvidia driver 340.107
To manage notifications about
Closing remark: the new systemd generators from upstream zfsonlinux fix
this. Version 0.8.x has it (Ubuntu kernel 5.2.0 needed or compile zfs
separately).
** Changed in: snapd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
When updating my system, I got the new 5.0.0.23 kernel (coming from
4.18.0-25). DKMS fails for the nvidia 340 driver. I need to use this for
my generation card (ION). Make log included.
X starts, but low-res.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nvidia-340
Check out https://wiki.ubuntu.com/Kernel/LTSEnablementStack. This is the
formal way Ubuntu provides newer kernels (and as such newer zfs
versions) during the lifecycle of an LTS release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: zfs-linux (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/1772412
Title:
zfs 0.7.9 fixes a bug (https://github.com/zfsonlinux/zfs/pull/7343)
The flatpak build got 60 and was reverted back within days. It is still
on 52.x...
I had and would cautious. See
https://github.com/flathub/org.mozilla.Thunderbird/issues/46.
** Bug watch added: github.com/flathub/org.mozilla.Thunderbird/issues #46
Fixed by comment #3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760621
Title:
Tab freezes when I exit the shell
To manage notifications about this bug go to:
My main reason for suggesting this is that it seems Canonical is easier
on snaps wrt. having rolling upgrades. I don't see a reason debs can't
do it, but I notice over and over again Canonical is very conservative
upgrading major software versions on debs (which is no criticism, just a
Public bug reported:
This circumvents the need to keep it on the same major version
throughout the LTS cycle. LXD is doing snaps, perhaps for zfs this is
the best approach as well.
Xenial still has zfsutils on generation 0.6, with the module on 0.7.
Even when patches are applied as needed that
Closing this old bug. Newer versions should not see this issue anymore.
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/787210
I don't see the confirmation for Bionic in this bug report. Any update
when the 4.17 kernel lands in bionic-proposed? Or do I need another
kernel version for Bionic? What do I need exactly for my Bionic server?
This bug prevents me from updating my lxd containers, it will hang the
system
Confirmed duplicate and working with the proposed version. Not sure how
I missed 1767559, sorry!
** Changed in: libinput (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I have had quite some issues with the touchpad on my 2013 DELL XPS 13
since installing 18.04. It worked fine on previous versions.
Typical observations:
- lag
- cursor movements being interrupted
- more lag
- single/double tap not being detected consistently
- did I
Public bug reported:
I have experienced the problems fixed by this commit
https://github.com/zfsonlinux/zfs/pull/7343 a few times on my NAS. The
system hangs completely when it occurs. It looks like 0.7.9 brings other
interesting bug fixes that potentially freeze the system.
** Affects:
I think the answer does not cover my question, as the ZFS driver is
linked to the kernel, which evolves with point releases and/or HWE
kernels on LTS versions.
To make it as practical as possible, let's assume ZFS 0.8 gets released
in June. I think I now can conclude it will not get backported to
Public bug reported:
Ubuntu Artful, fully upgraded, standard flavor.
Error when running telegram or hello-world snap:
"failed to create prefix path:
/tmp/snap.rootfs_xUQUrs/var/lib/snapd/lib/vulkan/icd.d: Permission
denied"
Relevant entry appearing in dmesg:
[ 1212.813285] audit: type=1400
The workaround keeps on breaking in a VM. I'm on the point I can't
assist further without guidance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750059
Title:
snaps appear broken when
So 2 questions still remain:
- if we executed the preliminary work around to disable the profiles, do we
need to take action to revert those and go back to "stock" configuration?
- what about the snap version of LO? As I mentioned it does not honor "classic"
confinement
--
You received this
Public bug reported:
If we consider the zfs 0.x releases as being major (0.6, 0.7, 0.8), is
the assumption correct that LTS releases will not receive a new major
ZFS release ?
To be as practical as possible: Bionic will be stuck at zfs 0.7.x,
Xenial at zfs 0.6.x ?
If my assumption is wrong,
Small update: I can't get the workaround to reproduce consistently in a
VM. While the directories are all mounted as they should and snapd is
started and running, snaps still appear "broken". I'm investigating
further.
With everything I tried so far I'm not sure this makes a lot of sense
though.
I have the libreoffice snap installed using classic confinement, yet I
seem to have this issue. By comparison the Atom snap works as expected.
Is the libreoffice snap version impacted by this as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
If AppArmor configuration is needed for mounted directories, I think we
need better information pushed to the users. If you say "add all your
mountpoints with user files need to be in file X" I am fine with that. I
just need to know.
Goes for snaps as well.
And I still think AppArmor provides
Yep, I will test that. /var can be tricky because of /var/run, so I'll
use a VM for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750059
Title:
snaps appear broken when /var/lib/snapd is a zfs
First a question for clarity: is this apparmor issue related to having
libreoffice installed as a snap, or is this native to the archive
version as well?
Second: I honestly can't grasp these kind of policy changes are rolled
out without having the slightest idea on what impact this might cause on
Hi, I tried this over noon and I have some good news. The workaround
seems successful (I did a few reboots, and snaps did not break again).
However, I can imagine this to be a difficult call to make: not
everybody has zfs installed, let alone be /var/lib/snapd be a zfs
dataset (although that
The problem is this becomes quite breakable when snaps get updated and
all. The mount units are specific to a snap version.
I was thinking of the following workaround (to test the basic
principle). I could create a mount unit for /var/lib/snapd. That should
tick all boxes: it should be taken into
I just pinned it down.
ZFS does not use systemd mount units. Both zfs(.target) and
snapd(.service) are wanted by multi-user.target.
Snaps are mounted before the zfs dataset is mounted by zfs-
mount.service, resulting in non-mounted snaps and therefore broken
snaps.
I have not yet found a
So far no luck. I added a After=local-fs.target to the snapd unit file,
but it still appears broken:
[Unit]
Description=Snappy daemon
Requires=snapd.socket
After=local-fs.target
[Service]
# Disabled because it breaks lxd
# (https://bugs.launchpad.net/snapd/+bug/1709536)
#Nice=-5
I'll see if I have that available. ZFS scripts might do things a bit
differently, I know there are a few outstanding actions wrt. systemd
mount compatibility ("native generators").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I assume it has to do something with the mount times as well.
It's stock/default behaviour. I see no direct link between snapd and zfs
looking at the unit files. Both are wanted by the multi-user target but
that's about it.
I have created a local copy (in /etc/systemd/system) of the snapd
Public bug reported:
ProblemType: Bug
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 22:00:59 2018
DistroRelease: Ubuntu 17.10
Package: snapd 2.29.4.2+17.10
PackageArchitecture: amd64
I have a separate ZFS dataset mounted at /var/lib/snapd.
Yes, but what does that mean wrt. supporting ZFS releases? Are major
upgrades considered for all currently supported HWE kernels? The current
LTS kernels? Only future/next LTS kernels? What is the policy?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
What is the policy for ZFS release updates? Are they limited to LTS
releases? Will all HWE kernels get upgraded eventually?
As an example, would Xenial eventually see ZFS 0.7 or even 0.8 or 0.9 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Bug and workaround https://bugs.launchpad.net/ubuntu/+source/nvidia-
graphics-drivers-340/+bug/1741671/comments/14 confirmed on older NVidia
ION machine with nvidia-340 on kernel 4.13.0-26.
Thanks guys!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Can't reproduce the crash as described before (consistently failed on a
heavy export job in virtualbox W10 guest).
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
** Description changed:
Upgraded to zesty about a week ago. Ran into this on latest kernel.
@brad-figg Thanks, that's good to hear!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To manage notifications about this bug
@matthias-opennomad
I use sudo apt install /directory-with-the-debs/*.deb. Use absolute
paths for this.
It warns about downgrading, after which the install runs fine.
@mstucki
Are you running on HWE ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@chihchun
Out of interest: could you give the procedure how you build this (I've
seen various recipes online)?
On my system, your debs are considered a lower version to the
repositories that have 4.10.0-28 as well and will offer to "upgrade" it
to the official ones every apt upgrade cycle.
So I
** Also affects: linux-hwe (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/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
Public bug reported:
ZFS 0.7.0 has been released: http://list.zfsonlinux.org/pipermail/zfs-
announce/2017-July/15.html.
It is important to note it will require an update of the userland tools
(zpool command). This can be an issue especially for the HWE kernel
stack if ZFS module versions
@flipvb
The main issue is not that this bug exists and that it is not the fault
of Canonical. The issue is that the 16.04 stable HWE LTS stack rolled to
4.10 despite this bug being known and being critical, with 16.04.3 not
even released yet.
--
You received this bug notification because you
I can consistently reproduce this issue doing a heavy mail export job in
a VirtualBox guest I use for work.
Just having done first run after applying the deb files provided per
comment 52, I was not able to reproduce the issue. Thank you @chihchun !
Canonical needs to apply these asap if they
I can now confirm this bug landed on the LTS HWE kernel.
Honestly, I get Ubuntu for free (well I support them but by no means
this is comparable to certain other license schemes out there) but I
have never been so disappointed. All my systems are now at risk. I don't
know who does QA at Canonical
Ok, I'll give it a go.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To manage notifications about this bug go to:
@chihchun does your build contain zfs modules?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To manage notifications about
I was not expecting the 4.10 kernel to land in the HWE stack for LTS
without seeing a fix here, so I am genuinely worried about the LTS+HWE
stability now.
Can we get confirmation on the state of the HWE 4.10 kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I noticed the HWE kernel rolled from 4.8 to 4.10.0-27-generic, and I
wondered if someone knows whether this bug was addressed in that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
I need zfs and it fails on the proprietary nvidia driver too. I'll see
if I can get it running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL
Can't we upstream the Xenial zfs script instead of fixing the "new" one?
It supports the same syntax, and does what it needs to do? And it does
not try to mount datasets I explicitly configured not to be mountable ;)
Seems like the faster solution, no?
--
You received this bug notification
So experiencing several crashes a day (hard lock) I decided to install
the HWE 4.8 kernel using the Xenial deb files. No more lock ups have
occured since.
This seems to me an extremely critical issue at the heart of the OS. I
would have expected more visibility on this TBH.
--
You received this
After a few days of using the patched kernel: the patch is not a 100%
fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680904
Title:
zesty unable to handle kernel NULL pointer dereference
To
I have implemented the workaround from #7
(https://bugs.freedesktop.org/show_bug.cgi?id=99295#c22) using the
attached patchfile on kernel 4.10.0-20.
My system crashed consistently when doing a resource heavy export job on
a VirtualBox Windows 10 guest. First try after patching this no longer
is
I have this issue and can provide logs if needed. Kernel
4.10.0-20-generic on Zesty. Very, very nasty bug causing very frequent
hard crashes. I think the importance ought to be raised on this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs
script might overrule canmount and mountpoint options for a dataset,
causing other mount operations and with them the boot process to fail.
Experienced this with Ubuntu Zesty. Xenial seems to ship with a
69 matches
Mail list logo
