| 2018-11-21 23:38:18 |
Tateru Nino |
bug |
|
|
added bug |
| 2018-11-22 16:41:01 |
Robie Basak |
bind9 (Ubuntu): status |
New |
Incomplete |
|
| 2018-12-27 14:10:20 |
Jon Schewe |
attachment added |
|
etc-bind.tar.gz https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1804542/+attachment/5225332/+files/etc-bind.tar.gz |
|
| 2018-12-27 14:10:37 |
Jon Schewe |
bug |
|
|
added subscriber Jon Schewe |
| 2019-01-23 13:48:25 |
Andreas Hasenack |
bind9 (Ubuntu): status |
Incomplete |
Triaged |
|
| 2019-01-23 13:48:26 |
Andreas Hasenack |
bind9 (Ubuntu): importance |
Undecided |
Medium |
|
| 2019-01-23 13:48:31 |
Andreas Hasenack |
tags |
amd64 apport-bug bionic |
amd64 apport-bug bionic server-next |
|
| 2019-01-23 13:49:02 |
Andreas Hasenack |
bug |
|
|
added subscriber Ubuntu Server |
| 2019-02-08 11:50:55 |
Roberto S. Galende |
bug |
|
|
added subscriber Roberto S. Galende |
| 2019-02-11 21:26:11 |
Alex Tomlins |
bug |
|
|
added subscriber Alex Tomlins |
| 2019-05-10 18:28:46 |
hard |
bug |
|
|
added subscriber hard |
| 2019-06-03 16:16:01 |
Bryce Harrington |
summary |
Multiple intermittent socket failures during name resolutions |
[SRU] Multiple intermittent socket failures during name resolutions |
|
| 2019-06-04 13:32:17 |
Andreas Hasenack |
tags |
amd64 apport-bug bionic server-next |
amd64 apport-bug bionic |
|
| 2019-06-07 23:08:43 |
Bryce Harrington |
attachment added |
|
The upstream commit https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1804542/+attachment/5269458/+files/49f90025a07be39d1236504d46db3ce73f1578ee.patch |
|
| 2019-06-08 00:11:43 |
Bryce Harrington |
description |
Multiple instances like:
Nov 22 09:36:09 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 09:36:09 mound named[1510]: internal_send: 10.0.2.11#54580: Invalid argument
Nov 22 09:36:09 mound named[1510]: client @0x7fba00513820 10.0.2.11#54580 (brave-sync.s3.dualstack.us-west-2.amazonaws.com): error sending response: invalid file
Nov 22 09:51:35 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 09:51:35 mound named[1510]: internal_send: ************:88fd:b31b:3e3:7082#60042: Invalid argument
Nov 22 09:51:35 mound named[1510]: client @0x7fb9f8117180 ***********:88fd:b31b:3e3:7082#60042 (cdn.onenote.net): error sending response: invalid file
[public ipv6 address partially elided for privacy]
Nov 22 05:58:24 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 05:58:24 mound named[1510]: internal_send: 10.0.2.11#63851: Invalid argument
Nov 22 05:58:24 mound named[1510]: client @0x7fba000c7690 10.0.2.11#63851 (discordapp.com): error sending response: invalid file
Not sure if these represent some genuine failure delivering to the client, or if it is an artifact of some normal condition being overreported.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bind9 1:9.11.3+dfsg-1ubuntu1.3
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Nov 22 10:31:02 2018
InstallationDate: Installed on 2017-07-18 (491 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: bind9
UpgradeStatus: Upgraded to bionic on 2018-11-15 (6 days ago)
modified.conffile..etc.bind.named.conf.local: [modified]
modified.conffile..etc.bind.named.conf.options: [modified]
mtime.conffile..etc.bind.named.conf.local: 2018-04-18T18:22:39.428390
mtime.conffile..etc.bind.named.conf.options: 2018-11-21T21:03:19.292677 |
[Impact]
Socket failures due to uninitialized memory during name resolution.
[Test Case]
TBD
[Regression Potential]
Things to watch for would include memory-related issues and faults relating to long names or addresses. The patch changes memory management for a data buffer used in socket communication. There could be behavioral differences between handling of ipv4 and ipv6 addresses.
[Fix]
See comment #7
This will need to be backported.
[Discussion]
[Original Report]
Multiple instances like:
Nov 22 09:36:09 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 09:36:09 mound named[1510]: internal_send: 10.0.2.11#54580: Invalid argument
Nov 22 09:36:09 mound named[1510]: client @0x7fba00513820 10.0.2.11#54580 (brave-sync.s3.dualstack.us-west-2.amazonaws.com): error sending response: invalid file
Nov 22 09:51:35 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 09:51:35 mound named[1510]: internal_send: ************:88fd:b31b:3e3:7082#60042: Invalid argument
Nov 22 09:51:35 mound named[1510]: client @0x7fb9f8117180 ***********:88fd:b31b:3e3:7082#60042 (cdn.onenote.net): error sending response: invalid file
[public ipv6 address partially elided for privacy]
Nov 22 05:58:24 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 05:58:24 mound named[1510]: internal_send: 10.0.2.11#63851: Invalid argument
Nov 22 05:58:24 mound named[1510]: client @0x7fba000c7690 10.0.2.11#63851 (discordapp.com): error sending response: invalid file
Not sure if these represent some genuine failure delivering to the client, or if it is an artifact of some normal condition being overreported.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bind9 1:9.11.3+dfsg-1ubuntu1.3
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Nov 22 10:31:02 2018
InstallationDate: Installed on 2017-07-18 (491 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: bind9
UpgradeStatus: Upgraded to bionic on 2018-11-15 (6 days ago)
modified.conffile..etc.bind.named.conf.local: [modified]
modified.conffile..etc.bind.named.conf.options: [modified]
mtime.conffile..etc.bind.named.conf.local: 2018-04-18T18:22:39.428390
mtime.conffile..etc.bind.named.conf.options: 2018-11-21T21:03:19.292677 |
|
| 2019-06-08 00:20:47 |
Ubuntu Foundations Team Bug Bot |
tags |
amd64 apport-bug bionic |
amd64 apport-bug bionic patch |
|
| 2019-06-08 00:33:35 |
Bryce Harrington |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-06-08 00:33:35 |
Bryce Harrington |
bug task added |
|
bind9 (Ubuntu Bionic) |
|
| 2019-06-08 00:35:25 |
Bryce Harrington |
bind9 (Ubuntu Bionic): status |
New |
Triaged |
|
| 2019-06-08 00:35:27 |
Bryce Harrington |
bind9 (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2019-06-08 00:42:18 |
Bryce Harrington |
description |
[Impact]
Socket failures due to uninitialized memory during name resolution.
[Test Case]
TBD
[Regression Potential]
Things to watch for would include memory-related issues and faults relating to long names or addresses. The patch changes memory management for a data buffer used in socket communication. There could be behavioral differences between handling of ipv4 and ipv6 addresses.
[Fix]
See comment #7
This will need to be backported.
[Discussion]
[Original Report]
Multiple instances like:
Nov 22 09:36:09 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 09:36:09 mound named[1510]: internal_send: 10.0.2.11#54580: Invalid argument
Nov 22 09:36:09 mound named[1510]: client @0x7fba00513820 10.0.2.11#54580 (brave-sync.s3.dualstack.us-west-2.amazonaws.com): error sending response: invalid file
Nov 22 09:51:35 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 09:51:35 mound named[1510]: internal_send: ************:88fd:b31b:3e3:7082#60042: Invalid argument
Nov 22 09:51:35 mound named[1510]: client @0x7fb9f8117180 ***********:88fd:b31b:3e3:7082#60042 (cdn.onenote.net): error sending response: invalid file
[public ipv6 address partially elided for privacy]
Nov 22 05:58:24 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 05:58:24 mound named[1510]: internal_send: 10.0.2.11#63851: Invalid argument
Nov 22 05:58:24 mound named[1510]: client @0x7fba000c7690 10.0.2.11#63851 (discordapp.com): error sending response: invalid file
Not sure if these represent some genuine failure delivering to the client, or if it is an artifact of some normal condition being overreported.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bind9 1:9.11.3+dfsg-1ubuntu1.3
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Nov 22 10:31:02 2018
InstallationDate: Installed on 2017-07-18 (491 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: bind9
UpgradeStatus: Upgraded to bionic on 2018-11-15 (6 days ago)
modified.conffile..etc.bind.named.conf.local: [modified]
modified.conffile..etc.bind.named.conf.options: [modified]
mtime.conffile..etc.bind.named.conf.local: 2018-04-18T18:22:39.428390
mtime.conffile..etc.bind.named.conf.options: 2018-11-21T21:03:19.292677 |
[Impact]
Socket failures due to uninitialized memory during name resolution.
[Test Case]
TBD
[Regression Potential]
Things to watch for would include memory-related issues and faults relating to long names or addresses. The patch changes memory management for a data buffer used in socket communication. There could be behavioral differences between handling of ipv4 and ipv6 addresses.
[Fix]
See comment #7
This will need to be backported for bionic. Other releases either don't need it or already have it:
bind9 | 1:9.8.1.dfsg.P1-4ubuntu0.22 | precise-updates | ×
bind9 | 1:9.9.5.dfsg-3ubuntu0.19 | trusty-updates | ×
bind9 | 1:9.10.3.dfsg.P4-8ubuntu1.14 | xenial-updates | ×
bind9 | 1:9.11.3+dfsg-1ubuntu1.7 | bionic-updates | [ ] Needs fix
bind9 | 1:9.11.4+dfsg-3ubuntu5.3 | cosmic-updates | √ has fix
bind9 | 1:9.11.5.P1+dfsg-1ubuntu2.4 | disco-updates | √ has fix
bind9 | 1:9.11.5.P4+dfsg-4ubuntu1 | eoan | √ has fix
[Discussion]
[Original Report]
Multiple instances like:
Nov 22 09:36:09 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 09:36:09 mound named[1510]: internal_send: 10.0.2.11#54580: Invalid argument
Nov 22 09:36:09 mound named[1510]: client @0x7fba00513820 10.0.2.11#54580 (brave-sync.s3.dualstack.us-west-2.amazonaws.com): error sending response: invalid file
Nov 22 09:51:35 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 09:51:35 mound named[1510]: internal_send: ************:88fd:b31b:3e3:7082#60042: Invalid argument
Nov 22 09:51:35 mound named[1510]: client @0x7fb9f8117180 ***********:88fd:b31b:3e3:7082#60042 (cdn.onenote.net): error sending response: invalid file
[public ipv6 address partially elided for privacy]
Nov 22 05:58:24 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 05:58:24 mound named[1510]: internal_send: 10.0.2.11#63851: Invalid argument
Nov 22 05:58:24 mound named[1510]: client @0x7fba000c7690 10.0.2.11#63851 (discordapp.com): error sending response: invalid file
Not sure if these represent some genuine failure delivering to the client, or if it is an artifact of some normal condition being overreported.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bind9 1:9.11.3+dfsg-1ubuntu1.3
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Nov 22 10:31:02 2018
InstallationDate: Installed on 2017-07-18 (491 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: bind9
UpgradeStatus: Upgraded to bionic on 2018-11-15 (6 days ago)
modified.conffile..etc.bind.named.conf.local: [modified]
modified.conffile..etc.bind.named.conf.options: [modified]
mtime.conffile..etc.bind.named.conf.local: 2018-04-18T18:22:39.428390
mtime.conffile..etc.bind.named.conf.options: 2018-11-21T21:03:19.292677 |
|
| 2019-06-08 00:48:51 |
Bryce Harrington |
bind9 (Ubuntu): status |
Triaged |
Fix Released |
|
| 2019-06-08 00:52:49 |
Bryce Harrington |
bug task added |
|
bind |
|
| 2019-06-08 00:53:32 |
Bryce Harrington |
bind: status |
New |
Fix Released |
|
| 2019-06-08 02:21:23 |
Bryce Harrington |
attachment added |
|
Backport of the upstream fixes https://bugs.launchpad.net/bind/+bug/1804542/+attachment/5269472/+files/fix-socket-failures-during-name-resolution.patch |
|
| 2019-06-09 20:51:59 |
Bryce Harrington |
tags |
amd64 apport-bug bionic patch |
amd64 apport-bug bionic patch server-next |
|
| 2019-07-19 07:32:58 |
Alex Tomlins |
removed subscriber Alex Tomlins |
|
|
|
| 2019-07-19 07:33:02 |
Alex Tomlins |
bug |
|
|
added subscriber Alex Tomlins |
| 2019-08-14 04:49:24 |
Juri Haberland |
bug |
|
|
added subscriber Juri Haberland |
| 2019-09-19 15:03:11 |
Christian Ehrhardt |
bind9 (Ubuntu Bionic): assignee |
|
Lucas Kanashiro (lucaskanashiro) |
|
| 2019-09-30 20:18:02 |
Lucas Kanashiro |
description |
[Impact]
Socket failures due to uninitialized memory during name resolution.
[Test Case]
TBD
[Regression Potential]
Things to watch for would include memory-related issues and faults relating to long names or addresses. The patch changes memory management for a data buffer used in socket communication. There could be behavioral differences between handling of ipv4 and ipv6 addresses.
[Fix]
See comment #7
This will need to be backported for bionic. Other releases either don't need it or already have it:
bind9 | 1:9.8.1.dfsg.P1-4ubuntu0.22 | precise-updates | ×
bind9 | 1:9.9.5.dfsg-3ubuntu0.19 | trusty-updates | ×
bind9 | 1:9.10.3.dfsg.P4-8ubuntu1.14 | xenial-updates | ×
bind9 | 1:9.11.3+dfsg-1ubuntu1.7 | bionic-updates | [ ] Needs fix
bind9 | 1:9.11.4+dfsg-3ubuntu5.3 | cosmic-updates | √ has fix
bind9 | 1:9.11.5.P1+dfsg-1ubuntu2.4 | disco-updates | √ has fix
bind9 | 1:9.11.5.P4+dfsg-4ubuntu1 | eoan | √ has fix
[Discussion]
[Original Report]
Multiple instances like:
Nov 22 09:36:09 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 09:36:09 mound named[1510]: internal_send: 10.0.2.11#54580: Invalid argument
Nov 22 09:36:09 mound named[1510]: client @0x7fba00513820 10.0.2.11#54580 (brave-sync.s3.dualstack.us-west-2.amazonaws.com): error sending response: invalid file
Nov 22 09:51:35 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 09:51:35 mound named[1510]: internal_send: ************:88fd:b31b:3e3:7082#60042: Invalid argument
Nov 22 09:51:35 mound named[1510]: client @0x7fb9f8117180 ***********:88fd:b31b:3e3:7082#60042 (cdn.onenote.net): error sending response: invalid file
[public ipv6 address partially elided for privacy]
Nov 22 05:58:24 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 05:58:24 mound named[1510]: internal_send: 10.0.2.11#63851: Invalid argument
Nov 22 05:58:24 mound named[1510]: client @0x7fba000c7690 10.0.2.11#63851 (discordapp.com): error sending response: invalid file
Not sure if these represent some genuine failure delivering to the client, or if it is an artifact of some normal condition being overreported.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bind9 1:9.11.3+dfsg-1ubuntu1.3
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Nov 22 10:31:02 2018
InstallationDate: Installed on 2017-07-18 (491 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: bind9
UpgradeStatus: Upgraded to bionic on 2018-11-15 (6 days ago)
modified.conffile..etc.bind.named.conf.local: [modified]
modified.conffile..etc.bind.named.conf.options: [modified]
mtime.conffile..etc.bind.named.conf.local: 2018-04-18T18:22:39.428390
mtime.conffile..etc.bind.named.conf.options: 2018-11-21T21:03:19.292677 |
[Impact]
Socket failures due to uninitialized memory during name resolution.
[Test Case]
There is no known self contained test case for this bug. However, after the feedback of the bug reporter [1][2] looks the proposed patch is properly fixing the bug.
[1] https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1804542/comments/12
[2] https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1804542/comments/13
[Regression Potential]
Things to watch for would include memory-related issues and faults relating to long names or addresses. The patch changes memory management for a data buffer used in socket communication. There could be behavioral differences between handling of ipv4 and ipv6 addresses.
[Fix]
See comment #7
This will need to be backported for bionic. Other releases either don't need it or already have it:
bind9 | 1:9.8.1.dfsg.P1-4ubuntu0.22 | precise-updates | ×
bind9 | 1:9.9.5.dfsg-3ubuntu0.19 | trusty-updates | ×
bind9 | 1:9.10.3.dfsg.P4-8ubuntu1.14 | xenial-updates | ×
bind9 | 1:9.11.3+dfsg-1ubuntu1.7 | bionic-updates | [ ] Needs fix
bind9 | 1:9.11.4+dfsg-3ubuntu5.3 | cosmic-updates | √ has fix
bind9 | 1:9.11.5.P1+dfsg-1ubuntu2.4 | disco-updates | √ has fix
bind9 | 1:9.11.5.P4+dfsg-4ubuntu1 | eoan | √ has fix
[Discussion]
[Original Report]
Multiple instances like:
Nov 22 09:36:09 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 09:36:09 mound named[1510]: internal_send: 10.0.2.11#54580: Invalid argument
Nov 22 09:36:09 mound named[1510]: client @0x7fba00513820 10.0.2.11#54580 (brave-sync.s3.dualstack.us-west-2.amazonaws.com): error sending response: invalid file
Nov 22 09:51:35 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 09:51:35 mound named[1510]: internal_send: ************:88fd:b31b:3e3:7082#60042: Invalid argument
Nov 22 09:51:35 mound named[1510]: client @0x7fb9f8117180 ***********:88fd:b31b:3e3:7082#60042 (cdn.onenote.net): error sending response: invalid file
[public ipv6 address partially elided for privacy]
Nov 22 05:58:24 mound named[1510]: ../../../../lib/isc/unix/socket.c:2135: unexpected error:
Nov 22 05:58:24 mound named[1510]: internal_send: 10.0.2.11#63851: Invalid argument
Nov 22 05:58:24 mound named[1510]: client @0x7fba000c7690 10.0.2.11#63851 (discordapp.com): error sending response: invalid file
Not sure if these represent some genuine failure delivering to the client, or if it is an artifact of some normal condition being overreported.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bind9 1:9.11.3+dfsg-1ubuntu1.3
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Nov 22 10:31:02 2018
InstallationDate: Installed on 2017-07-18 (491 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: bind9
UpgradeStatus: Upgraded to bionic on 2018-11-15 (6 days ago)
modified.conffile..etc.bind.named.conf.local: [modified]
modified.conffile..etc.bind.named.conf.options: [modified]
mtime.conffile..etc.bind.named.conf.local: 2018-04-18T18:22:39.428390
mtime.conffile..etc.bind.named.conf.options: 2018-11-21T21:03:19.292677 |
|
| 2019-09-30 21:25:13 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/bind9/+git/bind9/+merge/373431 |
|
| 2019-10-01 21:44:09 |
Bryce Harrington |
bind9 (Ubuntu Bionic): status |
Triaged |
In Progress |
|
| 2019-10-24 15:27:18 |
Łukasz Zemczak |
bind9 (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2019-10-24 15:27:21 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-10-24 15:27:25 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2019-10-24 15:27:34 |
Łukasz Zemczak |
tags |
amd64 apport-bug bionic patch server-next |
amd64 apport-bug bionic patch server-next verification-needed verification-needed-bionic |
|
| 2019-11-04 13:26:25 |
Roberto S. Galende |
tags |
amd64 apport-bug bionic patch server-next verification-needed verification-needed-bionic |
amd64 apport-bug bionic patch server-next verification-done-bionic verification-needed |
|
| 2019-11-04 13:38:04 |
Robert Williams |
removed subscriber Robert Williams |
|
|
|
| 2019-11-06 15:41:44 |
Launchpad Janitor |
bind9 (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-11-06 15:41:51 |
Robie Basak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
