Hi Robie and others,
Sorry guys, since I reported this bug 2 years ago, I gradually switched
to Debian system and pass/gopass password manager (even deleted lastpass
account). So, currently I don't use neither Ubuntu nor lastpass daily
(not because they are any bad, but due personal preferences).
Please disregard last paragraph in my comment #1. I've found that I was
not able to boot with recurse=1 not due of read-only /var, but due of
script's attempt to remount absent cdrom for which I have an entry in my
/etc/fstab (added by system installer).
Nevertheless, I found new configuration use
Simplified conditional logic and allowed to negate expression.
** Patch added: "0001-Allow-to-list-affected-filesystems-in-recurse.patch"
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1758389/+attachment/5091398/+files/0001-Allow-to-list-affected-filesystems-in-recurse.p
** Patch removed: "0001-Allow-to-list-affected-filesystems-in-recurse.patch"
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1758389/+attachment/5089305/+files/0001-Allow-to-list-affected-filesystems-in-recurse.patch
--
You received this bug notification because you are a
I attached a patch, illustrating changes I propose.
I amended "recurse" option so that it take a regexp of filesystem names to work
on, besides old values "0" and "1". That is, old values keep their meaning, but
if recurese is set to something like "boot|backup" it will work only on those
filesy
Public bug reported:
I'm experimenting with overlayroot in VirtualBox.
In my setup I have separate /boot, /var, /home and / (root) partitions.
I want /boot and / (root) partitions be protected with overlayroot=tmpfs, but
others be mounted normally as rw. There is an option 'recurse', but it allow
Sorry, I've forgot about this one.
I built package from github sources, it works well. So, I suppose it just
enough to rebuild it for the repository.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555
Public bug reported:
When I try to login into my account using lastpass-cli (lpass login
usern...@server.com), it respond with error:
Error: Peer certificate cannot be authenticated with given CA
certificates.
Several day ago it worked.
I found this ticket at their project site:
https://github
No, I've updated several times since then, all updates went smooth.
I'm on 3.13.0-57-generic now and it also works fine.
Probably, it's safe to close this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Well, just for information, 3.13.0-45-generic works fine for me (and 3.13.0-44
wasn't):
uname -a
Linux tnl-N76VJ 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13 19:36:28 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
This one works: http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.18-rc2-vivid/
uname -a
Linux tnl-N76VJ 3.18.0-031800rc2-generic #201410281737 SMP Tue Oct 28 21:38:57
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Please provide me with a list of kernels I should try, if you think it
may help.
--
Yo
The same issue again with new kernel from repository (3.13.0-39-generic
#66-Ubuntu). See attachment above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380881
Title:
Kernel panic - not syncing: VF
** Attachment added: "BSOD - 3.13.0-39-generic #66"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380881/+attachment/4248860/+files/DSCN0243.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Strangely for me, when I re-installed kernel packages from -proposed above the
same versions from ppa:canonical-kernel-team/ppa, they do work (I rebooted
system several times hot and cold):
$ uname -a
Linux tnl-N76VJ 3.13.0-38-generic #65-Ubuntu SMP Thu Oct 9 11:36:50 UTC 2014
x86_64 x86_64 x8
This kernel works: /~kernel-ppa/mainline/v3.13.11.9-trusty
$ uname -a
$ Linux tnl-N76VJ 3.13.11-03131109-generic #201410141735 SMP Tue Oct 14
21:37:14 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Attachment added: "/etc/fstab content"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380881/+attachment/4235173/+files/fstab.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380881
Ti
** Attachment added: "/etc/mtab content"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380881/+attachment/4235172/+files/mtab.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380881
Titl
** Attachment added: "lshw output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380881/+attachment/4235171/+files/lshw.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380881
Title:
K
** Attachment added: "BSOD 3.13.0-38"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380881/+attachment/4235169/+files/DSCN0236.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380881
Tit
Public bug reported:
I've recently updated to the kernel 3.13.0-37 from the main repository
and got this issue again (I had similar issue before with 3.11.0-15, see
Bug #1265971). I tried to update to 3.13.0-38 from ppa:canonical-kernel-
team/ppa, but the issue remains.
I'm not sure, but suspect
** Attachment added: "BSOD 3.13.0-38 in recovery mode"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1380881/+attachment/4235170/+files/DSCN0239.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
sudo add-apt-repository ppa:canonical-kernel-team/ppa
sudo apt-get update
sudo apt-get dist-upgrade
sudo reboot now
nick@tnl-N76VJ:~$ uname -r
3.11.0-16-generic
Probably not exactly the build you pointed to, but latest for the moment
from ppa, does work.
So, it seems that I'll get working stock
Kernels:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10.1-saucy/
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10.2-saucy/
work as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265
All 3 kernels work like a charm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265971
Title:
Kernel panic during boot 3.11.0-15-generic
To manage notifications about this bug go to:
https://bugs.l
** Attachment added: "Photo of the screen with Call Trace"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265971/+attachment/3940303/+files/IMGP1973.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Public bug reported:
I've updated to 3.11.0-15-generic via aptitude and tried to reboot. During boot
I've got a kernel panic with messages:
uncompression error
UFS: cannot open root device "..." or unknown-block(0,0): error -6
Please append a correct "root=" boot option
Previous version (3.11.0-
26 matches
Mail list logo
