Same thing here
...
Dec 1 06:42:11 lx-dev3 containerd[845]:
time="2020-12-01T06:42:11.225821304-05:00" level=info msg="Stop CRI service"
Dec 1 06:42:11 lx-dev3 containerd[845]:
time="2020-12-01T06:42:11.242385111-05:00" level=info msg="Stop CRI service"
Dec 1 06:42:11 lx-dev3 containerd[845]:
Good findings!
Thank you so much for testing the rdrand theory.
I guess a read fix would require a new ISO, which could easily be made
as a dot release (19.04.1).
Regards,
Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
I have yet to see any issue (i.e. it's working fine) with 4.15.0.46 (I
used xenial-proposed to upgrade).
As the rest of you, I had constant issue with this in 4.15.0-45
So yes, maybe it is related to the tty bug. This does seem to be
consistent with the behavior I was seeing with current kernel.
I verified by installing x11vnc-data and x11vnc .deb packages from
Cosmic (over the already installed Bionic version) and there's no more
crash.
This is not the recommended solution though, we should have an official
backport for Bionic. x11vnc is pretty much unusable with this issue
though...
This is fixed in 0.19.13-6
The fix is in Cosmic, but this would need to be backported to Bionic
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881632
Regards,
Eric
** Bug watch added: Debian Bug tracker #881632
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881632
--
You received
I mean, 0.9.13-6 :)
Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686084
Title:
x11vnc on zesty terminates with **stack smashing detected** error
To manage notifications about this bug go to
Ok, I just tried with this version, and the issue I am seeing sadly does
persist. So, this does not resolve it. Please ignore the last comment.
Sorry,
Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Thanks for porting this to Xenial. Should the Xenial Ubuntu Base
release be updated? The Ubuntu Base 16.04.3 does come with the
problematic systemd, and on some systems, like the armhf, booting to a
bare rootfs is impossible (always get the issue, which manifest itself
as 'A start job is running
*** This bug is a duplicate of bug 228624 ***
https://bugs.launchpad.net/bugs/228624
I just looked at dmesg, and yes, it seem to be that bug.
(from dmesg on my system)
[ 39.510447] ata2.00: ATAPI: HL-DT-STDVD-RAM GSA-H22N, 1.02, max UDMA/66
[ 39.686305] ata2.00: configured for UDMA/66
Co
I had the same problem.
I ended-up 'fixing' it by replacing my DVD cable (40-pin) with an 80-pin
cable.
It could have problem detecting/using ATA33 mode. In my case, changing
the cable let the driver run properly in ATA66 mode (bug#275335).
--
8.10 alpha4 / Kernel gives I/O error on CD(?)
htt
Public bug reported:
Setup:
Asus A8N5X
2GB RAM
320GB SATA HD (1st sata)
80GB SATA (2nd sata)
eVGA GeForce 7900 GT
LG GSA-H22N DVD writer (using a 40-pin cable)
Kubuntu AMD64 LiveCD. Although this apply to all the Ubuntu flavors.
In fact, from what I read, this seem to apply to 2.6.26 (and later
11 matches
Mail list logo
