** Merge proposal linked:
https://code.launchpad.net/~daniel-thewatkins/ubuntu/+source/tmux/+git/tmux/+merge/369731
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to tmux in Ubuntu.
https://bugs.launchpad.net/bugs/1835439
Title:
Memory
** Changed in: ubuntu-advantage-tools (Ubuntu Trusty)
Status: New => In Progress
** Changed in: ubuntu-advantage-tools (Ubuntu Trusty)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Server,
** Changed in: ubuntu-advantage-tools (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subs
Uploaded to the unapproved queue, next step is from the SRU team.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ruby2.3 in Ubuntu.
https://bugs.launchpad.net/bugs/1834072
Title:
Puppet agent using 100% CPU, in sched_yield() loop.
The bash completion bug was fixed.
I'm inclined to say that if character classes are needed, gawk should be
used. It looks like mawk has stalled, and the call to switch to Thomas
Dickey's fork isn't mine to make. We are following debian on this one.
** Changed in: mawk (Ubuntu)
Importance:
The apache2 DEP8 tests are now clear across the board for bionic and
cosmic:
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#apache2
https://people.canonical.com/~ubuntu-archive/proposed-
migration/cosmic/update_excuses.html#apache2
--
You received
Thanks for filing this bug in Ubuntu.
I understand you are having issues with dovecot and mysql authentication
when talking over the localhost interface, and not a unix socket.
It would help a lot if you could attach relevant configuration files and
reproduction steps. How is your database
There are dozens of cosmic tests still running
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Title:
18.04/Apache2: rejecting client initiated renegotiation due to openssl
I'm checking.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Title:
18.04/Apache2: rejecting client initiated renegotiation due to openssl
1.1.1
To manage notifications about
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
-
- * justification for backporting the fix to the stable release.
-
- * In addition, it is helpful, but not required, to include an
-explanation of how the upload fixes this bug.
+ Ruby
** Changed in: ruby2.3 (Ubuntu)
Status: Triaged => In Progress
** Changed in: ruby2.3 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justifi
I was just waiting for some feedback, as this is hard to reproduce. I
tried the script for a few minutes but nothing out of the ordinary
happened.
I see two +1s now, so I'll proceed with the SRU.
--
You received this bug notification because you are a member of Ubuntu
Server, which is
Packages uploaded to their respective -proposed queues, it's up to the
SRU team now.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Title:
18.04/Apache2: rejecting client
Can you check if this comment and the one after it helps?
https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1652525/comments/14
https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1652525/comments/15
--
You received this bug notification because you are a member of Ubuntu
Server, which
** Changed in: apache2 (Ubuntu Cosmic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: apache2 (Ubuntu Bionic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: apache2 (Ubuntu Bionic)
Importance: Undecided => High
** Changed in
** Description changed:
[Impact]
Under the following conditions, https connections using client cert
authentication will suffer a long delay (about 15s if modreqtimeout is enabled,
more if it is disabled):
* TLSv1.2
* client certificate authentication in use
* a Location, Directory,
** Description changed:
[Impact]
Under the following conditions, https connections using client cert
authentication will suffer a long delay (about 15s if modreqtimeout is enabled,
more if it is disabled):
* TLSv1.2
* client certificate authentication in use
* a Location, Directory,
** Description changed:
[Impact]
Under the following conditions, https connections using client cert
authentication will suffer a long delay (about 15s if modreqtimeout is enabled,
more if it is disabled):
* TLSv1.2
* client certificate authentication in use
* a Location, Directory,
** Description changed:
[Impact]
- Under the following conditions, https connections using client cert
authentication will suffer a long delay (15s or more if modreqtimeout is
disabled):
+ Under the following conditions, https connections using client cert
authentication will suffer a long
client certificate
** Attachment added: "client-auth.pem"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274495/+files/client-auth.pem
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
client key
** Attachment added: "client-auth.key"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274496/+files/client-auth.key
** Description changed:
[Impact]
Under the following conditions, https connections using client cert
authentication will suffer a
fake CA
** Description changed:
[Impact]
+ Under the following conditions, https connections using client cert
authentication will suffer a long delay (15s or more if modreqtimeout is
disabled):
+ * TLSv1.2
+ * client certificate authentication in use
+ * a Location, Directory, or other such
server key
** Attachment added: "ubuntu.key"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274494/+files/ubuntu.key
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
server certificate
** Attachment added: "ubuntu.pem"
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039/+attachment/5274493/+files/ubuntu.pem
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [Test
The PPA has cosmic and bionic packages. I tested with the prefork,
worked and event MPMs, and also ran the apache DEP8 tests. All passed.
I'll prepare MPs, update this bug with the SRU template and testing
instructions, and get ready to release this early next week.
--
You received this bug
Public bug reported:
This is mostly a place holder bug, as more information becomes
available.
What is known so far is that a certain configuration of client
certificate authentication using TLSv1.3 is not working with most (all
at this point?) browsers, resulting in the server returning this
** Also affects: apache2 (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: apache2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Bionic)
*** This bug is a duplicate of bug 1833039 ***
https://bugs.launchpad.net/bugs/1833039
Discussion is happening in bug #1833039, so I'm marking this as a
duplicate of that one.
** This bug has been marked a duplicate of bug 1833039
18.04/Apache2: rejecting client initiated renegotiation
I think this patch worked:
https://github.com/apache/httpd/commit/bbedd8b80e50647e09f2937455cc57565d94a844
Could you please try the build from my ppa:
https://launchpad.net/~ahasenack/+archive/ubuntu/apache2-client-cert-1833039
--
You received this bug notification because you are a member of
https://bz.apache.org/bugzilla/show_bug.cgi?id=62691#c5
"Moving "SSLVerifyClient require" outside of the block instantly
returns the document. So it does appear to be ONLY the renegotiation case.
"
That works here too, in my simple test case. I had this location directive:
I can try some or all of the patches mentioned in
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689/comments/2
That bug might be a duplicate, btw. (or this one)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in
This is confusing, I'm seeing the timeout with a TLSv1.2 connection, and
the commit pointed out in comment #9 mentions TLSv1.3.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Same thing. Another, or an additional, fix is needed.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Title:
18.04/Apache2: rejecting client initiated renegotiation due to
I can reproduce this with stock bionic (plus updates applied).
==> /var/log/apache2/error.log <==
[Thu Jun 27 19:37:43.049064 2019] [ssl:error] [pid 3084:tid 140343919978240]
[client 10.0.100.1:45036] AH02261: Re-negotiation handshake failed
It's a bit complicated to setup, as usual with SSL
Since it's fixed in cosmic and later, marking the main task as fix
released.
** Changed in: sssd (Ubuntu Bionic)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to sssd in Ubuntu.
Quick test case, to be used in the sru template later on:
sudo apt update
sudo apt install sssd winbind
create this /etc/samba/smb.conf:
[global]
log file = /var/log/samba/log.%m
map to guest = Bad User
max log size = 1000
panic action =
Ok, reproduced:
[2019/06/27 17:35:46.930548, 0]
../source3/winbindd/idmap.c:328(smb_register_idmap)
Failed to register idmap module.
The module was compiled against SMB_IDMAP_INTERFACE_VERSION 5,
current SMB_IDMAP_INTERFACE_VERSION is 6.
Please recompile against the current version of
Thanks for filing this bug in Ubuntu.
While I try to reproduce this, it would speed things up if you had a
sample config that shows the problem. We could then also use this as a
test case to verify the fix.
--
You received this bug notification because you are a member of Ubuntu
Server, which
The packages from the ppa finally built overnight, so you can also just
add the ppa. Instructions are at
https://launchpad.net/~ahasenack/+archive/ubuntu/ruby-cpu-busy-
loop-1834072/, but it boils down to this command:
sudo add-apt-repository ppa:ahasenack/ruby-cpu-busy-loop-1834072
Then:
sudo
Thanks for your testing!
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ruby2.3 in Ubuntu.
https://bugs.launchpad.net/bugs/1834072
Title:
Puppet agent using 100% CPU, in sched_yield() loop. Looks like an
issue with ruby2.3 which has
Thanks!
The arm builders are slow, so apt won't see that ppa as populated just
yet, but you can download the individual packages. Here are the amd64
ones, for example: https://launchpad.net/~ahasenack/+archive/ubuntu
/ruby-cpu-busy-loop-1834072/+build/17190313
--
You received this bug
I built xenial packages in this ppa with the above patch, if you could
give them a try:
https://launchpad.net/~ahasenack/+archive/ubuntu/ruby-cpu-busy-
loop-1834072/
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ruby2.3 in Ubuntu.
Upstream commit in the 2.3 branch:
https://github.com/ruby/ruby/commit/c5a99cf3c0d493e911f499fdecdd0db68019af98
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ruby2.3 in Ubuntu.
https://bugs.launchpad.net/bugs/1834072
Title:
Puppet
** Tags added: server-next
** Changed in: ruby2.3 (Ubuntu)
Status: New => Triaged
** Changed in: ruby2.3 (Ubuntu)
Importance: Undecided => High
** Bug watch added: Debian Bug tracker #876377
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876377
** Also affects: ruby2.3 (Debian)
https://salsa.debian.org/ruby-
team/ruby/commit/50d860d0bd7834e95214a2b1ff5b8e0ede7910a1 seems to be
the fix
If I build packages in a ppa, can you test for us, prior to the upload
to proposed?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed
No worries, thanks for following up
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1778322
Title:
gvfs-smb-browse can't browse samba/smb tree
To manage notifications about this bug go
Let's leave the bug at "incomplete", and if new information arises, it
can be added here.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1833812
Title:
package bind9
@bloodyiron, you said in
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/comments/81
that you had SMB1 disabled in your network, and I confirmed that with
SMB1 disabled there is still a bug, and that bug is
https://bugs.launchpad.net/gvfs/+bug/1828107, and it affects all ubuntu
Thanks for filing this bug in Ubuntu.
Indeed the complaint was that bind couldn't write to /var/cache/bind. Do
you happen to know what it was set to? That would help in debugging how
it reached that state.
The attached logs unfortunately do not have more information about that,
only the failure
** Attachment added: "disco-connect-to-pub.png"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272829/+files/disco-connect-to-pub.png
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
Disco works out of the box wrt this bug specifically. Which is expected
since it has the same fix.
windows network tab is populated (see disco-windows-network-
populated.png)
Connecting to the pub share (see disco-connect-to-pub.png).
smbstatus shows smb3.11 in the pub connection, and NT1 for
** Attachment added: "cosmic-connecting-to-pub-after-test.png"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272234/+files/cosmic-connecting-to-pub-after-test.png
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received
Cosmic verification
First reproducing the bug with these packages:
Version table:
*** 1.38.1-0ubuntu1.2 500
500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64
Packages
windows network tab is empty (see screenshot
cosmic-empty-windows-network-before-test.png)
Now
** Attachment added: "cosmic-empty-windows-network-before-test.png"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272232/+files/cosmic-empty-windows-network-before-test.png
--
You received this bug notification because you are a member of Ubuntu
Server, which is
** Attachment added: "cosmic-populated-windows-network-after-test.png"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272233/+files/cosmic-populated-windows-network-after-test.png
--
You received this bug notification because you are a member of Ubuntu
Server, which
Bionic desktop verification
With gvfs-backends from the release pocket:
ubuntu@bionic-desktop:~$ apt-cache policy gvfs-backends
gvfs-backends:
Installed: 1.36.1-0ubuntu1.3
Candidate: 1.36.1-0ubuntu1.3
Version table:
*** 1.36.1-0ubuntu1.3 500
500 http://br.archive.ubuntu.com/ubuntu
** Attachment added: "populated-windows-network-after-test.png"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272226/+files/populated-windows-network-after-test.png
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed
** Attachment added: "connecting-to-pub-after-test.png"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272227/+files/connecting-to-pub-after-test.png
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug
** Attachment added: "empty-windows-network-before-test.png"
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+attachment/5272225/+files/empty-windows-network-before-test.png
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to
Xenial verification
First, reproducing the bug with the current package:
ubuntu@xenial-berification-sssd-sudo:~$ apt-cache policy libsss-sudo
libsss-sudo:
Installed: (none)
Candidate: 1.13.4-1ubuntu1.14
Version table:
1.13.4-1ubuntu1.14 500
500
Bionic verification
First, confirming the bug:
ubuntu@bionic-verification-sssd-sudo:~$ apt-cache policy libsss-sudo
libsss-sudo:
Installed: 1.16.1-1ubuntu1.2
Candidate: 1.16.1-1ubuntu1.2
Version table:
*** 1.16.1-1ubuntu1.2 500
500 http://br.archive.ubuntu.com/ubuntu
Can you see if this config helps?
https://github.com/rigred/sensor_config/blob/master/X470/ASRock/ASRock-X470
-Tachi-Ultimate
lm-sensors upstream doesn't seem to have a config specifically for the
x470, just the x370.
--
You received this bug notification because you are a member of Ubuntu
Possibly related, yes, specially now that openssl 1.1.1 arrived. If you
downgrade to 1.1.0g from bionic-security, does the problem still happen?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
This can be overridden in /etc/nagios-plugins/config/disk.cfg, right? By
adding the parameter you suggested.
** Changed in: monitoring-plugins (Ubuntu)
Status: New => Triaged
** Changed in: monitoring-plugins (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification
Another suggestion would be to use systemd @service files, like the
openvpn package does. You will get one daemon per vpn (in the openvpn
case), and one per fetchmail config, if done properly.
** Changed in: fetchmail (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug
** Merge proposal unlinked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/sg3-utils/+git/sg3-utils/+merge/368981
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to sg3-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1823436
Title:
** Changed in: ubuntu-advantage-tools (Ubuntu)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: In Progress => Triaged
** Also affects: ubuntu-advantage-tools (Ubuntu Trusty)
Importance: Undecided
Statu
** Description changed:
[Impact]
This is a major rewrite of ubuntu-advantage-client. This version introduces
an updated command line interface (UA Client) to simplify some interaction with
Ubuntu Advantage support offerings, and interacts with a new service backend
built specifically for
** Description changed:
[Impact]
This is a major rewrite of ubuntu-advantage-client. This version introduces
an updated command line interface (UA Client) to simplify some interaction with
Ubuntu Advantage support offerings, and interacts with a new service backend
built specifically for
** Description changed:
[Impact]
This is a major rewrite of ubuntu-advantage-client. This version introduces
an updated command line interface (UA Client) to simplify some interaction with
Ubuntu Advantage support offerings, and interacts with a new service backend
built specifically for
** Description changed:
[Impact]
This is a major rewrite of ubuntu-advantage-client. This version introduces
an updated command line interface (UA Client) to simplify some interaction with
Ubuntu Advantage support offerings, and interacts with a new service backend
built specifically for
** Description changed:
[Impact]
+ This is a major rewrite of ubuntu-advantage-client. This version introduces
an updated command line interface (UA Client) to simplify some interaction with
Ubuntu Advantage support offerings, and interacts with a new service backend
built specifically for
Public bug reported:
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Case]
* detailed
Bionic verification
First, reproducing the bug, following the test steps:
Version used:
*** 6.3.26-3build1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
Bug reproduced:
root@bionic-fetchmail-sni:~# fetchmail -d0 -vk --sslcertck pop.gmail.com
fetchmail: WARNING:
Uploaded, it's in the SRU bionic queue
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1798786
Title:
can't retrieve gmail emails. fetchmail: OU=No SNI provided; please fix
your
** Changed in: fetchmail (Ubuntu Bionic)
Status: New => In Progress
** Changed in: fetchmail (Ubuntu Bionic)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug
Confirmed it's now happening in bionic, thanks for the heads up!
** Also affects: fetchmail (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: fetchmail (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. There have been many changes in Ubuntu
and samba since that time you reported the bug and your problem may have
** Changed in: apache2 (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1832182
Title:
systemd unable to detect running apache if invoked via
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1832182
Title:
systemd unable to detect running apache if invoked via "apache2ctl
graceful"
To manage
** Changed in: apache2 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1832182
Title:
systemd unable to detect running apache if invoked via
Thanks for the detailed report. It looks like it's the same issue as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927302, so I'm linking
them both together.
** Bug watch added: Debian Bug tracker #927302
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927302
** Also affects: apache2
Note that this has the potential of breaking existing scripts, so it's
probably not a good SRU candidate.
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1661745
Upstream commit in 8.0:
commit c2c18a39683db382a15b438632afab3f551d50ce
Author: d...@openbsd.org
Date: Sat Jan 26 22:35:01 2019 +
upstream: make ssh-keyscan return a non-zero exit status if it
finds no keys. bz#2903
OpenBSD-Commit-ID:
You can increase the samba verbosity dynamically with "smbcontrol smbd
debug ", where "n" is the level. I would start with 3
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1831345
Title:
Can you catch something in the samba logs perhaps, when you enable
advanced features?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1831345
Title:
Attribute-Editor is missing when
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
We are sorry that we do not always have the capacity to look at all reported
bugs in a timely manner. There have been many changes in Ubuntu since that time
you reported the bug and your problem may have been
** Changed in: samba (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: samba (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1831441
Looks like the patch that was applied is https://gitlab.isc.org/isc-
projects/bind9/merge_requests/409, but it doesn't apply cleanly, so it's
not an immediate candidate for the server-next queue.
** Tags removed: server-next
--
You received this bug notification because you are a member of
See where the $(PROJECT_VERSION) makefile variable is defined, as that
is used in the sed to replace the %string%, and go from there.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1773324
I browsed the WHATSNEW.txt file looking for something to indicate how
and when this was addressed, but didn't find it. Would you be able to
take a look, since you are more familiar with this feature?
Here are some links:
https://github.com/samba-team/samba/blob/v4-7-test/WHATSNEW.txt
Ok, so it's a new feature in samba 4.10. That's unlikely to get
backported to bionic, which has 4.7.x.
** Changed in: samba (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: samba (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a
Still in the queue.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1795420
Title:
Keepalived update from 1.2.19 to 1.2.24 breaks support for /dev/tcp
health check
To manage
Thanks for filing this bug in Ubuntu.
The error message is:
SSHDConfig:
Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255:
/etc/ssh/sshd_config: line 88: Bad configuration option: Y
/etc/ssh/sshd_config: terminating, 1 bad configuration options
That means that there is a
** Changed in: keepalived (Ubuntu)
Assignee: Karl Stenerud (kstenerud) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1795420
Title:
Keepalived update from 1.2.19 to
Can you please try the same with Ubuntu Disco 19.04? It has samba
4.10.0. Also, if you compare smb.conf between the one you got in
fedora's 4.10.0, and ubuntu's 4.7.6, are they the same? After
profisioning, that is.
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
You received
Is the above what you meant?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1831306
Title:
squid-deb-proxy is a python2 script
To manage notifications about this bug go to:
Which script do you mean, exactly? And on which ubuntu release?
/usr/share/squid-deb-proxy-client/apt-avahi-discover perhaps?
** Changed in: squid-deb-proxy (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server, which is
root@bionic-squid-deb-proxy-py2:~#
/usr/share/squid-deb-proxy-client/apt-avahi-discover
http://10.0.100.136:8000/
root@bionic-squid-deb-proxy-py2:~# python3
/usr/share/squid-deb-proxy-client/apt-avahi-discover
File "/usr/share/squid-deb-proxy-client/apt-avahi-discover", line 130
print
601 - 700 of 4057 matches
Mail list logo
