Argh. For some reason which I can NOT explain. my libuuid.so.1 symlink
was not pointing to libuuid.so.1.3.0 but to a file called
libuuid.so.1.3.0.original
And i just found libblkid is similarly redirected. I remade the
symlinks (and deleted those bogus files) and it all works now.
Sorry for th
steven@steven-ge40:~$ ldd -v `which uuidgen`
/usr/bin/uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not
found (required by /usr/bin/uuidgen)
linux-vdso.so.1 (0x7ffdf0ce4000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f6f9a079000)
libc.
Public bug reported:
I execute uuidgen and get:
$ uuidgen
uuidgen: /lib/x86_64-linux-gnu/libuuid.so.1: version `UUID_2.31' not found
(required by uuidgen
I tried:
steven@steven-ge40:~$ sudo apt-get clean
steven@steven-ge40:~$ sudo apt-get install --reinstall libuuid1
Reading package lists... D
Public bug reported:
I just upgraded from 18.10 to 19.04 and then to 19.10.
I have had ZFS installed in this machine for years. My Root pool is on
LUKS encrypted SSD's which are morrored by ZFS.
The upgrade from 18.10 to 19.04 worked as expected with no errors. And
I was able to reboot, unlock
Public bug reported:
Upgrading from Ubuntu 18.04 to 18.10 when using LUKS encrypted root
volumes for ZFS can lead to a system that is unable to boot.
To reproduce, have a LUKS+ZFS setup with the root volume encrypted
working in 18.04 and upgrade to 18.10. When the initramfs is generated,
the fol
So, how will we know when this patch drops into a distribution kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
kernel BUG at /build/linux-
7LGLH_/linux-4.10.0/include/linux/sw
@Joseph Salisbury;
Touchwood, using your test kernel, I have been running for 2 days, 20
hours without a problem. (havent shutdown once in that time) Been using
firefox and thunderbird the whole time. The stock kernels wouldn't run
for me for more than an hour or two. I see other people still g
@Joseph Salisbury;
I have been testing your kernel all night and not a single problem has
occurred. Before this, I couldn't run for two hours without a lock up.
So far my uptime on this kernel is 15 hours 30 minutes. With a problem
like this its difficult to say categorically "its fixed" but it
