Another +1 for what it's worth, this fixes things nicely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879692
Title:
[SRU] Strongswan pki creates CA certificates with invalid Key Usage
flags
I can confirm the python3-nova and associated dependencies from cloud-
archive:stein-proposed have stopped the errors like these ones form the
original report:
2018-12-18 07:41:55.364 26870 ERROR nova.api.openstack [Previous line repeated
280 more times]
2018-12-18 07:41:55.364 26870 ERROR
*** This bug is a duplicate of bug 1808951 ***
https://bugs.launchpad.net/bugs/1808951
I hit this as well. It looks like it is fixed over in
https://bugs.launchpad.net/nova/+bug/1808951
I've tested, and at least for bionic-stein, the problem is resolved with
those proposed packages.
** This
A bit of follow up on this:
strace on the thread in question shows the following:
13:35:47 poll([{fd=23, events=POLLIN}], 1, 0) = 0 (Timeout) <0.18>
13:35:47 epoll_wait(42, [{EPOLLIN, {u32=3, u64=3}}], 9, 0) = 1 <0.18>
13:35:47 recvmsg(417, {msg_namelen=0}, MSG_DONTWAIT) = -1 EAGAIN
Public bug reported:
I have an ovs-vswitchd process consuming 100% CPU in a very lightly used
Openstack Rocky cloud running on Bionic. The version in question is
openvswitch-switch 2.10.0-0ubuntu2~cloud0
ovs-vswitchd is running alongside various neutron processes
(lbaasv2-agent, metadata-agent,
Public bug reported:
I'm not clear on how to trigger the set of installed packages that leads
to this bug, but in any case, I ran into an issue where neutron-dhcp-
agent would refuse to work. Logs looked like this:
Apr 22 14:51:48 juju-df624b-4-lxd-10 neutron-dhcp-agent[1999891]: 2019-04-22
Public bug reported:
This is to track the upstream Squid 3.x bug in https://bugs.squid-
cache.org/show_bug.cgi?id=4477
Briefly, squid will consume all available CPU when it is used to request
large files using memory or disk caches.
If/when that bug is fixed, the fix should be backported to
Sure, here's term.log:
Log started: 2018-01-08 14:59:40
Log ended: 2018-01-08 15:00:02
Log started: 2018-01-10 14:53:41
Log ended: 2018-01-10 14:53:52
Log started: 2018-01-17 18:01:43
Log ended: 2018-01-17 18:01:59
And here's history.log from the same host:
Start-Date: 2018-01-17
I ran into this as well, with the same host's cron daemon reaching ~8GB
RSS memory after a month.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702785
Title:
High memory and "can't fork" on heavy
Public bug reported:
An automatic update of maas-dhcp via landscape triggered alerts that
DHCP was down on all controller nodes. The update appeared to stop any
running dhcpd process, and failed to start the installed isc-dhcp-server
dhcp.
Logs show messages like this:
Apr 3 13:40:18 kernel:
I've had a go with linux-
image-4.8.0-040800rc3-generic_4.8.0-040800rc3.201608212032_amd64 and the
behaviour is the same, suspend immediately wakes up.
I also tried last week with linux-
image-4.7.0-040700-generic_4.7.0-040700.201608021801_amd64 and it was
present there.
Marked as confirmed and
I opened a new bug about those over in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616214
It is still affecting me using 16.04 on a Macbook Air 6.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Based on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311724 I
am opening this bug to tackle the issue of a Macbook Air that resumes
immediately after suspending.
I have the exact same symptoms as those described in the first bug. The
first suspend on battery power
Public bug reported:
When using an intermediate layer (nodejs) to install an extra apt
repository, I've run into an issue where the default config.yaml options
from the intermediate layer are not being rendered into the final built
charm.
Specifically, I'm using the nodejs charm here:
This bug breaks monitoring for me on over 30 production 12.04 servers.
The patch should be reviewed for SRU inclusion since nagios3 (in main)
and icinga (universe) are both affected by it. It requires manual
intervention to bring the service back on each individual host, so this
patch is fairly
Public bug reported:
The /usr/bin/ejabberd2prosody migration tool does not run with a default
install on 12.04.1. The package.path needs to read:
package.path = package.path
../usr/lib/prosody/util/?.lua;/usr/lib/prosody/?.lua;
Otherwise it will throw an error like the following:
This is occuring in VirtualBox as well, so while the initial report
shows NonfreeKernelModules: nvidia, it isn't specific to the video card
in use, or proprietary driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Affecting me when run as a Virtualbox guest here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/960757
Title:
whoopsie crashed with SIGSEGV in g_object_newv()
To manage notifications about this
This also applies to solr-jetty on 10.04. It is not just searches
containing '.' either - we were seeing it with searches containing '/',
so I'm guessing it can be triggered using a variety of non alpha numeric
characters.
It was fixed upstream in Debian, and Natty according to
@colan, I've run into this problem as well. I have only logged in using
one computer (ever) and am seeing the same problem as you, where the
alias changes back after clicking the 'Close' button.
What is even more troubling is that editing ~/.mission-
control/accounts/accounts.cfg to use a
Here's a capture of Empathy's debug output when changing an Alias
To reproduce:
Edit-Personal Information
Clear Debug log
Change Alias
Click 'Close'
Edit-Personal Information
Click 'Close'
The attached output corresponds to those steps.
** Attachment added: empathy.txt
21 matches
Mail list logo
