ERPID ACCESS COMMAND
/dev/snd/controlC0: richard1511 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-07-12 (735 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Rel
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard1511 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-07-12 (735 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS &qu
ortVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard1511 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-07-12 (73
ERPID ACCESS COMMAND
/dev/snd/controlC0: richard1511 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-07-12 (735 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Rel
e:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard1511 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-07-12 (735 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver&quo
cesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard1511 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-07-12 (735 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic B
e:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard1511 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-07-12 (735 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver&quo
cesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard1511 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-07-12 (735 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic B
e:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard1511 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-07-12 (735 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver&quo
cesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard1511 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-07-12 (735 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic B
ERPID ACCESS COMMAND
/dev/snd/controlC0: richard1511 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-07-12 (735 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Rel
cesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard1511 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-07-12 (735 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic B
rtVersion: 2.20.11-0ubuntu27.3
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: richard1511 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2018-0
ERPID ACCESS COMMAND
/dev/snd/controlC0: richard1511 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-07-12 (735 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release
Public bug reported:
The same as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636.
kaihengfeng closed that one "Because there's no response from the
original bug reporter." and asked to file a report for all devices
affected, so here I am, duplicating the report.
On Ubuntu MATE
See also this upstream PR: https://github.com/openzfs/zfs/pull/9414
and the one before it: https://github.com/openzfs/zfs/pull/8667
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
While I have not upgraded to 5.3.0-59, I upgraded to 5.4.0-37, as the
5.4.0 kernel has finally been made available in 18.04. This version and
possibly later fixed the issue I originally had.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I have submitted this upstream:
https://github.com/openzfs/zfs/pull/10388
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1875577
Title:
Encrypted swap won't load on 20.04 with zfs
seth-arnold, the ZFS default is actltype=off, which means that ACLs are
disabled. (I don't think the NFSv4 ACL support in ZFS is wired up on
Linux.) It's not clear to me why this is breaking with ACLs off.
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
user@user-Lenovo-V15-IIL:~$ cat /proc/bus/input/devices
I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0
B: PROP=0
B: EV=21
B:
There is another AES-GCM performance acceleration commit for systems
without MOVBE.
--
Richard
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881107
Title:
zfs: backport AES-GCM
I have confirmed that the fix in -proposed fixes the issue for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1872863
Title:
QEMU/KVM display is garbled when booting from kernel EFI
Yes, that's correct. This the reason why Kwin's opengl compositor +
suspend-resume combination causes it. What I wrote is just a
workaround/trick to disable opengl compositor on resume.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Can you share a bit more details about how you have yours setup? What
does your partition table look like, what does the MD config look like,
what do you have in /etc/fstab for swap, etc.? I'm running into weird
issues with this configuration, separate from this bug.
@didrocks: I'll try to get
I think it used to be the case that zfsutils-linux depended on zfs-dkms
which was then provided by the kernel packages. That seems like a way to
solve this. Given that dkms is for dynamic kernel modules, it was always
a bit weird to see the kernel providing that. It should probably be that
I didn't get a chance to test the patch. I'm running into unrelated
issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1875577
Title:
Encrypted swap won't load on 20.04 with zfs
This is a tricky one because all of the dependencies make sense in
isolation. Even if we remove the dependency added by that upstream
OpenZFS commit, given that modern systems use zfs-mount-generator,
systemd-random-seed.service is going to Require= and After= var-
lib.mount because of its
John Gray: Everything else aside, you should mirror your swap instead of
striping it (which I think is what you're doing). With your current
setup, if a disk dies, your system will crash.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
brian-willoughby (and pranav.bhattarai):
The original report text confirms that "The exit code is 0, so update-
grub does not fail as a result." That matches my understanding (as
someone who has done a lot of ZFS installs maintaining the upstream
Root-on-ZFS HOWTO) that this is purely cosmetic.
I have the exactly same problem I think, this script should work! I'm
trying to figure out what could be wrong with your systemctl.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849084
Hi khitschler,
I have the default Ubuntu 20.04 kernel and the freeze still occurs. My
assumption about the correct behavior was wrong however I think I have
just found a workaround could somebody you/somebody test it?
>From here (by tbg - Admired ): https://forum.manjaro.org/t/kde-nvidia-
Hi, is this issue still present? 20.04 seems OK for me. No freezes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1849084
Title:
Freeze on system-resume caused by kwin and amdgpu
I just installed the the 04/17 daily build of 20.04, and the problem
still exists.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1870208
Title:
adding GUI to Ubuntu Server 20.04
Here's a screenshot with output devices:
** Attachment added: "output_devices.png"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1872641/+attachment/5353851/+files/output_devices.png
--
You received this bug notification because you are a member of Kernel
Packages, which is
I've removed the config file and restarted the session, but no luck. :(
There's nothing under input devices in pavucontrol, see attached
screenshot.
** Attachment added: "input_devices.png"
Thanks your the quick reply. I've attached the requested log.
Unfortunately, it doesn't work anywhere.
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1872641/+attachment/5353732/+files/journalctl.log
--
You received this bug notification because
Public bug reported:
I can choose the headphone as an input device, but it doesn't work.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1870208
Title:
adding GUI to Ubuntu Server 20.04 results in no log in
wait a minute... is this bug existend about 5 years, and nobody fixed
it? same crap here,
i built 5.3 kernel month ago, but problem is not with kernel, maybe
with usb driver module, or something.
dmesg -l err:
[ 11.456051] ccp :27:00.2: sev command 0x4 timed out, disabling PSP
[
Public bug reported:
My chromium browser what was installed by snap is constantly causing
this system error message:
[ 3754.402424] audit: type=1400 audit(1582978393.441:96):
apparmor="DENIED" operation="open" profile="snap.chromium.chromium"
name="/etc/pulse/client.conf.d/" pid=6082
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd/controlC0: richard2533 F pulseaudio
CurrentDesktop
und from the front left
and right speakers is the workaround.
This step should not be required for speakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard253
The AES-GCM performance improvements patch has been merged to master. This also
included the changes to make encryption=on mean aes-256-gcm:
https://github.com/zfsonlinux/zfs/commit/31b160f0a6c673c8f926233af2ed6d5354808393
--
You received this bug notification because you are a member of Kernel
What was the expected result? Are you expecting to be able to just
install ZFS in a container (but not use it)? Or are you expecting it to
actually work? The user space tools can’t do much of anything without
talking to the kernel.
--
You received this bug notification because you are a member
** Changed in: zfs-linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862661
Title:
zfs-mount.service and others fail inside unpriv
on: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd/controlC0: richard2533 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Dis
correction: I don't have any testing kernels installed NOW. In December
2019 I tried your kernels and failed to uninstall them correctly. In the
end I had to go back to a system backup. If you tell me how to
unload/reload the HD-audio driver and what to do afterwards I'd be
willing to help. But
** Bug watch added: Github Issue Tracker for ZFS #9443
https://github.com/zfsonlinux/zfs/issues/9443
** Also affects: zfs via
https://github.com/zfsonlinux/zfs/issues/9443
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
Ok, I'm just a user and don't have access to that mailing list but what
I CAN say, is, that my affected system doesn't run radeon or nouveau
driver but amdgpu.
Takashi Iwai wrote in November 2019 'amdgpu driver already got the
audio-component binding recently, so this problem shouldn't be
Hi Hui Wang,
just wanted to remind you that this patch (meant for better usability)
broke audio completely for many users out there. I'd really like to see
any progress in the corresponding bug report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771
Meanwhile I came across many
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd/controlC0: richard2533 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
for speakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd/controlC0: richard
There does seem to be a real bug here. The problem is that we don’t know
if it is on the ZoL side or the FreeBSD side. The immediate failure is
that “zfs recv” on the FreeBSD side is failing to receive the stream. So
that is the best place to start figuring out why. If it turns out that
ZoL is
The FreeBSD bug report:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243730
Like I said, boiling this down to a test case would likely help a lot.
Refusing to do so and blaming the people giving you free software and
free support isn’t helpful.
** Bug watch added: bugs.freebsd.org/bugzilla/
** Changed in: zfs-linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1854982
Title:
Lost compatibilty for backup between Ubuntu 19.10
In terms of a compact reproducer, does this work:
# Create a temp pool with large_dnode enabled:
truncate -s 1G lp1854982.img
sudo zpool create -d -o feature@large_dnode=enabled lp1854982
$(pwd)/lp1854982.img
# Create a dataset with dnodesize=auto
sudo zfs create -o dnodesize=auto lp1854982/ldn
e required for speakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd
eakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd/controlC0: richard
e required for speakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd
e required for speakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd/controlC0
eakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd/controlC0: richa
AND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd/controlC0: richard2533 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2020-01-28 (2 days
eakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd/controlC0: richa
e required for speakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd
eakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd/controlC0: richard
e required for speakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd
tep should not be required for speakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
eakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd/controlC0: richard
e required for speakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd
e required for speakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd/controlC0
r speakers 5.1 to work.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: richard2533 F pulseaudio
/dev/snd/controlC1: richard2533 F pulseaudio
/dev/snd/controlC0
ACCESS COMMAND
+ /dev/snd/controlC2: richard2533 F pulseaudio
+ /dev/snd/controlC1: richard2533 F pulseaudio
+ /dev/snd/controlC0: richard2533 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2020-01-28 (2 days
So, one of two things is true:
A) ZFS on Linux is generating the stream incorrectly.
B) FreeBSD is receiving the stream incorrectly.
I don't have a good answer as to how we might differentiate those two.
Filing a bug report with FreeBSD might be a good next step. But like I
said, a compact
The last we heard on this, FreeBSD was apparently not receiving the send
stream, even though it supports large_dnode:
https://zfsonlinux.topicbox.com/groups/zfs-
discuss/T187d60c7257e2eb6-M14bb2d52d4d5c230320a4f56/feature-
incompatibility-between-ubuntu-19-10-and-freebsd-12-0
That's really
I think there are multiple issues here. If it's just multipath, that
issue should be resolved by adding After=multipathd.service to zfs-
import-{cache,scan}.service.
For other issues, I wonder if this is cache file related. I'd suggest
checking that the cache file exists (I expect it would), and
@gustypants: Sorry, the other one is scan, not pool. Are you using a
multipath setup? Does the pool import fine if you do it manually once
booted?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
zfs-linux (0.6.5.6-2) unstable; urgency=medium
...
* Scrub all healthy pools monthly from Richard Laager
So Debian stretch, but not Ubuntu 16.04.
Deleting the file should be safe, as dpkg should retain that. It sounds
like you never deleted it, as you didn’t have it before this upgrade. So
This was added a LONG time ago. The interesting question here is: if you
previously deleted it, why did it come back? Had you deleted it though?
It sounds like you weren’t aware of this file.
You might want to edit it in place, even just to comment out the job.
That would force dpkg to give you a
You original scrub took just under 4.5 hours. Have you let the second
scrub run anywhere near that long? If not, start there.
The new scrub code uses a two-phase approach. First it works through
metadata determining what (on-disk) blocks to scrub. Second, it does the
actual scrub. This allows ZFS
We discussed this at the January 7th OpenZFS Leadership meeting. The
notes and video recording are now available.
The meeting notes are in the running document here (see page 2 right now, or
search for this Launchpad bug number):
> It is not appropriate to require the user to type a password on every
> boot by default; this must be opt-in.
Agreed.
The installer should prompt (with a checkbox) for whether the user wants
encryption. It should default to off. If the user selects the checkbox,
prompt them for a passphrase.
I've given this a lot of thought. For what it's worth, if it were my
decision, I would first put your time into making a small change to the
installer to get the "encryption on" case perfect, rather than the
proposal in this bug.
The installer currently has:
O Erase disk an install Ubuntu
Try adding "After=multipathd.service" to zfs-import-cache.service and
zfs-import-pool.service. If that fixes it, then we should probably add
that upstream.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
This script also works for me. Like Michael I added a larger sleep
duration and execute it as startup app. Will put this script on every of
our office PCs. Thanks Martin for sharing this workaround. As already
mentioned I'd very much appreciate a real fix coming in the near future.
Wish you all a
I put these questions to Tom Caputi, who wrote the ZFS encryption. The
quoted text below is what I asked him, and the unquoted text is his
response:
> 1. Does ZFS rewrite the wrapped/encrypted master key in place? If
>not, the old master key could be retrieved off disk, decrypted
>with
I have come up with a potential security flaw with this design:
The user installs Ubuntu with this fixed passphrase. This is used to
derive the "user key", which is used to encrypt the "master key", which
is used to encrypt their data. The encrypted version of the master key
is obviously written
Here are some quick performance comparisons:
https://github.com/zfsonlinux/zfs/pull/9749#issuecomment-569132997
In summary, "the GCM run is approximately 1.15 times faster than the CCM
run. Please also note that this PR doesn't improve AES-CCM performance,
so if this gets merged, the speed
This is an interesting approach. I figured the installer should prompt
for encryption, and it probably still should, but if the performance
impact is minimal, this does have the nice property of allowing for
enabling encryption post-install.
It might be worthwhile (after merging the SIMD fixes)
This has been tested with live ubuntu 19.10 as suggested by Daniel and
the mouse problem persists for intel braswell. xdotool reveals that X
reports a vertical position of zero, even when the mouse is painted with
an offset to the right, which seems to indicate this is could be a
compositor
Should it set KEYMAP=y too, like cryptsetup does?
I've created a PR upstream and done some light testing:
https://github.com/zfsonlinux/zfs/pull/9723
Are you able to confirm that this fixes the issue wherever you were
seeing it?
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1854798 ***
https://bugs.launchpad.net/bugs/1854798
Confirmed this is fixed by test kernel described in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854798/comments/11
from that bug. Thanks.
--
You received this bug notification because you are a
I can report that the test kernel in #11 fixes this issue for my HP
Stream 11 laptop, confirming that
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856042 is a
duplicate of this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
The trackpad on my HP Stream 11 laptop stopped working when I upgraded
the kernel to linux-image-4.15.0-72-generic. It works fine with linux-
image-4.15.0-70-generic. An external USB mouse also works fine.
I reported this bug with "ubuntu-bug linux" under linux-
I've also installed the testing kernels but without success. No audio at all :(
@hui.wang: I saw some dmesg outputs being uploaded. Do you need more samples to
fix this bug?
Can you please give us a status update on this? I'm dealing with this
situation for months now and half of the PCs in our
I received the email of your latest comment, but oddly I’m not seeing it
here.
Before you go to all the work to rebuild the system, I think you should
do some testing to determine exactly what thing is breaking the send
stream compatibility. From your comment about your laptop, it sounds
like you
I'm not sure if userobj_accounting and/or project_quota have
implications for send stream compatibility, but my hunch is that they do
not. large_dnode is documented as being an issue, but since your
receiver supports that, that's not it.
I'm not sure what the issue is, nor what a good next step
This is probably an issue of incompatible pool features. Check what you
have active on the Ubuntu side:
zpool get all | grep feature | grep active
Then compare that to the chart here:
http://open-zfs.org/wiki/Feature_Flags
There is an as-yet-unimplemented proposal upstream to create a features
If the pool has an _active_ (and not "read-only compatible") feature
that GRUB does not understand, then GRUB will (correctly) refuse to load
the pool. Accordingly, you will be unable to boot.
Some features go active immediately, and others need you to enable some
filesystem-level feature or take
** Changed in: zfs-linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852854
Title:
Update of zfs-linux fails
Status in zfs-linux
Which specific filesystems are failing to mount?
Typically, this situation occurs because something is misconfigured, so
the mount fails, so files end up inside what should otherwise be empty
mountpoint directories. Then, even once the original problem is fixed,
the non-empty directories prevent
201 - 300 of 952 matches
Mail list logo
