I have tested 1.8.8-1ubuntu0.6 (bionic) with our existing configuration,
and I cannot find anything wrong it.
We use the default 1024 bit DH-parameters, and override it with better
parameters for some of our frontends using parameters specified directly
in the certificate file (concatenated).
tes
I have done some preliminary testing with 1.8.8-1ubuntu0.5, and most
things look good.
However, in our case we have an old (external) client using java6 that
we sadly still need to support for a while longer. Using the connection
simulation in testssl.sh (and also ssllabs) I can see that connectio
Public bug reported:
haproxy needs to be rebuilt after #1797386 to take advantage of TLSv1.3.
(If that's not desirable for some reason, then maybe TLSv1.3 should be
actively disabled to avoid any surprises in case of a future bug fix
release.)
---
Output of haproxy -vv with stock package:
Buil
Tested OK.
I first reproduced the original bug using 7.0.13-0ubuntu0.16.04.1. I
then upgraded to 7.0.15-0ubuntu0.16.04.1 from -proposed and verified
that the bug was fixed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you ar
Further testing suggests that cherry-picking this particular commit
might be insufficient for our usage scenario. I'll test a bit with the
master branch of ssh2.
What's clear is that the version currently being shipped in xenial is
broken when used with php from xenial-updates.
--
You received t
Public bug reported:
opendir() for a "ssh2.sftp://.."-style url fails after upgrade to php
7.0.13 from xenial-updates.
This is a known bug fixed upstream in php-ssh2, commit
17680cf039f0cfac53b5a2531fdb715b95e9cc42.
I've rebuilt the package locally using the attached patch.
** Affects: php-ssh2
Public bug reported:
After upgrading php7.0 to 7.0.13-0ubuntu0.16.04.1 from xenial-updates,
we had a couple of failed tests in our internal test suite.
I reported php bug #73959, which was then fixed in commit
21ac79e94bd0335bf885b807e09c4d86d75d776a.
** Affects: php7.0 (Ubuntu)
Importance:
I submitted a pull request at https://github.com/lxc/lxd/pull/1964
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576082
Title:
lxd handles cleanup of un-umountable devices badly
To manage notifica
I tried changing cleanup() to properly check for errors from
removeUnixDevices() and removeDiskDevices() and pass these on up the
stack.
This seems to work; the lxc command now reports an error ("error: lstat
/var/lib/lxd/devices/c1/disk.usr-local-nfs: stale NFS file handle") and
the contents of /
** Description changed:
I lost some data last night, and I think the problem has to do with how
lxd cleans up when there are attached devices that can't be umounted.
This is my testcase:
---
# / is ext4
# /home is ext4
# /var/lib/lxd is btrfs
# /usr/local/nfs is a remote nfs
Public bug reported:
I lost some data last night, and I think the problem has to do with how
lxd cleans up when there are attached devices that can't be umounted.
This is my testcase:
---
# / is ext4
# /home is ext4
# /var/lib/lxd is btrfs
# /usr/local/nfs is a remote nfs directory
mkdir -p /ho
I suspect that this fix also broke rabbitmq on one of my servers. For
unimportant reasons this particular server had ipv6 disabled through the
kernel command line ( GRUB_CMDLINE_LINUX="ipv6.disable=1" ). I ran
strace on epmd and this is, I assume, the relevant section:
---
socket(PF_INET6, SOCK_ST
The "readdir loop" problem seems to be fairly widely known (
http://lwn.net/Articles/544520/ ), and an upgrade to the latest 12.04
kernel (3.2.0-60-generic) on the nfs server seems to have fixed the
problem for us.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
We have an NFS server running on ubuntu 12.04, and after upgrading one
client from 10.04 to 12.04 the other day we are hitting a similar
(possibly the same) problem. The server setup has not been touched for
months.
We have a directory with a lot of .xml files (~1009700 of them).
Running an ls on
This bug is unrelated to the Enable menu access keys option under
Keyboard Shortcuts and not limited to Unity. When the menu bar is
hidden, the keys are not intercepted. The problem (for me at least) was
that gnome-terminal didn't seem to respect the "Show menubar by default
in new terminals" optio
Still happens for me here (running gnome-shell).
Enabling and then disabling the menu bar again through the in-window
context menu makes it go away, but this needs to be repeated for every
new window.
Uninstalling appmenu-gtk (having already uninstalled appmenu-gtk3
without improvement) seems to
** Also affects: appmenu-gtk
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875070
Title:
gnome terminal intercepts my alt key combinations when it shouldn
17 matches
Mail list logo
