** Also affects: linux-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1440608
Title:
/etc/kernel/postinst.d/apt-auto-remova
The problem is that on purge/removal the linux-image-extra package runs
all the kernel post-*install*-hooks in /etc/kernel/postinst.d (as its
postrm hook), including the /etc/kernel/postinst.d/apt-auto-removal
hook. The 'to-be-removed'-version of the kernel is given as an argument
and thereby adde
The fix of running all the kernel-post-install hooks on removal of a
linux-image-extra package causes another bug (#1440608) with the
autoremoval feature. Please see my comment on
https://bugs.launchpad.net/bugs/1440608 .
--
You received this bug notification because you are a member of Kernel
Pa
Jarno Suni, thanks for the reply.
First I would like to stress, that I still don't think that running all
the KERNELS postINSTALL hooks while REMOVING the -extra package is the
right thing todo. The only thing I can see that is really needed is the
recreation of the initrd on installation and revm
Hi all,
sorry, the apt-auto-removal script attached above contained some debug
echo statements. Which were harmless, but unnessecary.
Testing and thinking a bit more about the problem I have come to the
conclusion, that upon removal of a linux-image-extra package the only
right thing to do is not
@ Andy Whitcroft:
- in the commit d7235802d7735e53936c5ccfbe9e071021b394fb you write regarding
linux-image-extra:
"As it also depends on linux-image we know that linux-image will have been
installed before it, and will be removed after it."
The last part is not correct. We have no way of knowing,
w this
problem and the cifs shares work as expected.
other Info:
lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release:16.04
uname -r
4.4.0-38-generic
If you need any further info or testing, please let me know.
Thanks,
Robert Euhus
ProblemType: Bug
DistroRelease: Ubuntu 16
kernel gets the environment variables
wrong.
Running an older Kernel like linux-image-4.4.0-36-generic does not show this
problem and the cifs shares work as expected.
other Info:
lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
uname -r
4.4.0-38-generic
cription:Ubuntu 16.04.1 LTS
Release:16.04
uname -r
4.4.0-38-generic
If you need any further info or testing, please let me know.
Thanks,
Robert Euhus
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-38-generic 4.4.0-38.57
Pr
res work as expected.
other Info:
lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
uname -r
4.4.0-38-generic
If you need any further info or testing, please let me know.
Thanks,
Robert Euhus
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux
ted.
other Info:
lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
uname -r
4.4.0-38-generic
If you need any further info or testing, please let me know.
Thanks,
Robert Euhus
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.
17:03:20 pcXX automount[7557]: failed to mount /mnt/cifs/joe
So for some reason autofs with this kernel gets the environment variables
wrong.
Running an older Kernel like linux-image-4.4.0-36-generic does not show this
problem and the cifs shares work as expected.
other Info:
lsb_rele
/joe
So for some reason autofs with this kernel gets the environment variables
wrong.
Running an older Kernel like linux-image-4.4.0-36-generic does not show this
problem and the cifs shares work as expected.
other Info:
lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:
image-4.4.0-36-generic does not show this
problem and the cifs shares work as expected.
other Info:
lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
uname -r
4.4.0-38-generic
If you need any further info or testing, please let me know.
Thanks,
Robert Euhu
I can confirm that the 0001-autofs4-Use-real_cred-for-uid-gid-in-
packets.patch fixes the problem.
I have tried the kernel located here:
http://people.canonical.com/~sforshee/lp1629204/
And I have also applied the patch an top of the 4.4.0-38 kernel (commit
be687e48ba9778ab2f28513bd50e1b274ba31f6
Just a note: 4.4.0-41.61 from xenial-proposed is still broken.
--
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/1629204
Title:
Autofs parameter substitution broken in kernel 4.4.0-38 and 4
I am very disappointed that another broken "stable" kernel (4.4.0-42.62)
was just released for xenial, even though this problem and the fix have
been known for about a week!
Why?
What can I do to speed up the progress?
I really need a working kernel on xenial! Or do I have to build it
myself and
I really don't understand what's going on here. It's been another 6 days
now. There has been another (broken) kernel update for xenial (4.4.0-43)
which did not include this fix, and which also did not go through
-proposed. Instead xenial-proposed is still at at 4.4.0-41, which is
broken as well.
T
The -proposed kernel works for me and fixes the problem.
Thanks!
Robert
--
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/1629204
Title:
Autofs parameter substitution broken in kernel 4.4.
This is unbelieveable:
- Ubuntu Xenial is shipping new broken kernels with a known REGRESSION !
- For more than two weeks a fix is known and "InProgress" (whatever this
means). That does however not prevent new broken kernels from being
released (4.4.0-42 and 4.4.0-43).
- Moreover all of these b
20 matches
Mail list logo
