I was able to install 4.4.0-43-generic and extras, and it works. Will
test on 4.4.0-59 and 4.8.0 and report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611831
Title:
Can't boot from new ker
While I'm not using encryption, I am using LVM and am experincing this
same problem on 4.4.0-59 and 4.8.0, upgrading from 3.19.0-79 which was
previously working.
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ub
Ryan Budney, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611831/comments/25
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow l
kernel 4.4.0-43-generic is working fine. Installed it today. Encryptfs
seems to be back to being fully operational.
So, I haven't tried 4.8.1 but it appears the bug was fixed before then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Should I convert to "fix released" ? There is no "resolved" tag.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611831
Title:
Can't boot from new kernel 4.4.0-34. Old kernel 4.4.0-31 is fine.
To
I have kernel 4.4.16-040416-generic running and the problem is still
there. It appears that encryptfs is partially broken and this is a
known bug. I can change into directories and open files. The only
problem now is that when I use a command like ls, I get responses such
as:
ls: cannot open d
Ryan Budney, to keep this relevant to upstream, one would want check
for, and test the latest mainline kernel (now 4.8.1) as it is released.
Could you please advise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Regarding post number 18, I spoke too soon about kernel:
Linux rybu-ThinkPad-W530 4.4.16-040416-generic #201607271333 SMP Wed Jul
27 17:35:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
That kernel boots and I can log into Ubuntu with it, even into my
account. But all the files in my home directory
The bios-outdated-2.65 tag, what does this mean? I tried clicking on
it but there's no description as far as I can tell.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611831
Title:
Can't boot fro
The bug is only semi-fixed upstream. With kernels 4.4.0-36 and 38 there
is still a bug but it is different than what I originally reported.
With these two kernels, I can boot up the system and even log in, but
once I log in my home directory appears to be empty. I imagine this is
because it rema
** Tags removed: kernel-fixed-upstream
** Tags added: bios-outdated-2.65 kernel-fixed-upstream-4.4.15
needs-reverse-bisect regression-update
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
That indicates the bug is either already fixed in upstream 4.4.16 or
it's an Ubuntu specific bug.
To confirm it's now fixed upstream, can you test 4.4.15. It should
contain the bug, since Ubuntu 4.4.0-34 had those stable updates and not
the 4.4.16 stable updates.
The 4.4.15 kernel can be downloa
I just booted to:
uname -a
Linux rybu-ThinkPad-W530 4.4.16-040416-generic #201607271333 SMP Wed Jul 27
17:35:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
So I think this means the problem is not in 4.4.16.
So I will add the kernel-fixed-upstream tag, and confirmed.
** Changed in: linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
**
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 d
apport information
** Tags added: apport-collected xenial
** Description changed:
Greetings,
I recently upgraded from the 4.4.0-31 to 4.4.0-34 kernel in Ubuntu
16.04. If I try booting from 4.4.0-34, my system freezes just after I
enter my password to decrypt my hard-drive. If I ask
** 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/1611831
Title:
Can't boot from new kernel 4.4.0-34. Old kernel 4.4.0-31 is fine.
To manage notifications
17 matches
Mail list logo
