** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1855768
Title:
Ubuntu-security CVE-2019-18224 web page shows incorrect info about
Hey Teppei,
Great to hear that!
After deeper looking over my logs and console buffer, I think this was a
combination of a user error on my part and a UX problem in Trivy
caching.
What I think might have happened:
- I scanned `ubuntu:18.04` tag at some point before the libidn2 fix went in and
Hey Eduardo,
This is the Trivy tool: https://github.com/aquasecurity/trivy. It's used to
scan containers for CVEs and to reproduce you can install trivy and just run
"trivy -quiet ubuntu:18.04" to see the CVE flagged.
I think what is happening is that trivy scans installed packages on the
Got sick and tired of this bug so figured I'd find out what the cause
is. Turns out (for me) because I overwrote multiple versions of Linux
using unetbootin, there were multiple apt folders in dist/ on the drive
(i.e. yakkety, zesty, etc) so when the 40cdrom script came around, it
tried to
Public bug reported:
On Ubuntu 15.10, version 8u91-b14-0ubuntu4~15.10.1 no longer provides
virtual package `java-runtime-headless` while the older version does
(8u66-b01-5):
$ apt-cache show openjdk-8-jre-headless | grep 'Provides\|Version'
Version: 8u91-b14-0ubuntu4~15.10.1
Provides:
Log:
sudo valgrind -v gpartedbin
** Attachment added: valgring_on_gpartedbin
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1450180/+attachment/4388412/+files/log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Probably related: https://bugzilla.gnome.org/show_bug.cgi?id=743466
They seem to have a patch upstream for glibmm
** Bug watch added: GNOME Bug Tracker #743466
https://bugzilla.gnome.org/show_bug.cgi?id=743466
** Also affects: gparted via
https://bugzilla.gnome.org/show_bug.cgi?id=743466
@Philip: Yeah, I found that it runs with a script after the initial post
which is why I hid it but gpartedbin is really having issues and
valgrind log was run on the binary and not the launcher.
$ debsums gparted
/usr/bin/gparted-pkexec OK
gparted (different from gpartedbin code posted above) also doesn't look
like an ELF file:
readelf -a /usr/sbin/gparted
readelf: Error: Not an ELF file - it has the wrong magic bytes at the start
dpkg -l | grep gparted
ii gparted 0.19.0-2
Looks like it might be a bad FD?
** Attachment added: valgrind log
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1450180/+attachment/4388008/+files/log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
sudo gdb gpartedbin
GNU gdb (Ubuntu 7.9-1ubuntu1) 7.9
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
** Also affects: network-manager-pptp
Importance: Undecided
Status: New
** Project changed: network-manager-pptp = network-manager
** Project changed: network-manager = network-manager-applet
** Project changed: network-manager-applet = network-manager
--
You received this bug
My cases of this bug (though it seems like there are different ones with
similar symptoms) happen each time I reset a 14.04 VM to an older state
from a hard shutdown. Localhost ssh connections fail as well with same
output.
Workaround for me is regenerating the host keys (sudo rm /etc/ssh/host_*
Looks to be a No supported key exchange algorithms [preauth] problem.
Regenerating the host RSA key with ssh-keygen -t rsa -f
/etc/ssh/ssh_host_rsa_key fixes the issue
Log of failure (pre-keygen) on host:
$ sudo /usr/sbin/sshd -p -D -d -d -d -e
debug2: load_server_config: filename
I don't know if it's related but this is the log of trying to use that
RSA key to connect to a server:
debug1: Trying private key: /etc/ssh/ssh_host_rsa_key
debug1: key_parse_private2: missing begin marker
debug1: key_parse_private_pem: PEM_read_PrivateKey failed
debug1: read PEM private key
Well, at least in my case, I found that all the sshd host keys were
truncated. I'm guessing that the hard shutdown of the VM was the cause
but I'm not 100% sure.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
My cases of this bug (though it seems like there are different ones with
similar symptoms) happen each time I reset a 14.04 VM to an older state
from a hard shutdown. Localhost ssh connections fail as well with same
output.
Workaround for me is regenerating the host keys (sudo rm /etc/ssh/host_*
Looks to be a No supported key exchange algorithms [preauth] problem.
Regenerating the host RSA key with ssh-keygen -t rsa -f
/etc/ssh/ssh_host_rsa_key fixes the issue
Log of failure (pre-keygen) on host:
$ sudo /usr/sbin/sshd -p -D -d -d -d -e
debug2: load_server_config: filename
I don't know if it's related but this is the log of trying to use that
RSA key to connect to a server:
debug1: Trying private key: /etc/ssh/ssh_host_rsa_key
debug1: key_parse_private2: missing begin marker
debug1: key_parse_private_pem: PEM_read_PrivateKey failed
debug1: read PEM private key
Well, at least in my case, I found that all the sshd host keys were
truncated. I'm guessing that the hard shutdown of the VM was the cause
but I'm not 100% sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@andornaut makes sense. when mine worked, i was doing the manual sudo
update-initramfs -u
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073062
Title:
modprobe: Assertion
@Ronni If you have Radeon cards, I'm curious as to why do you have a
nvidia kernel module? Either way, I think the issue is caused by dkms'
handling of alias off commands so it might be good to grep though
that directory (modprobe.d) to find occurrences of it
--
You received this bug
@Ronni after reading the full thread (my fault for not being diligent
enough) you are correct and post 35 is what I found as well. The fix I
mentioned got my machine hardware configuration in a working state to be
able to use it but it definitively is not the permanent solution.
--
You received
Bug is related to nvidia video drivers;
Commenting out:
alias nouveau off
alias lbm-nouveau off
from /etc/modprobe.d/nvidia-304_hybrid.conf allowed the update-initramfs
to complete
** Also affects: nvidia-drivers-ubuntu
Importance: Undecided
Status: New
--
You received this bug
On ubuntu-nexus7, I don't think this bug applies as the user reports are
caused by /usr/bin/luxd dynamically setting the brightness based on the
light sensor input. I'm adding more info to Nexus 7 bug report
(https://bugs.launchpad.net/ubuntu-nexus7/+bug/1075473)
--
You received this bug
25 matches
Mail list logo
