[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713770
Sorry everyone, this is a mandos problem and it's in universe, so I
shouldn't have reported the problem here. Building a 1.7.16 mandos-
client package fixed my issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713770
Title:
USN-3405-1 kernel cause kernel panic when using mandos
To manage notifications about this
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
I grabbed the newest mandos sources, 1.7.16, and the client doesn't
kernel panic, but I get no response from the server. I'll see if I can
find a spare machine to set up as a mandos 1.7.16 server. I'd rather
not have to build .debs for the newer version, but we can't stay
4.4.0-92 kernel forever
