[Bug 1966923] Re: exiqgrep -r and -f options match all messages if no

[EOLE team]

** Tags added: verification-done-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966923

Title:
  exiqgrep -r and -f options match all messages if no

To manage notifications about this bug go to:
https://bugs.launchpad.net/exim/+bug/1966923/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966923] [NEW] exiqgrep -r and -f options match all messages if no

[EOLE team]

Public bug reported:

On jammy, exiqgrep command shows syntax errors :

root@eolebase:~# exiqgrep 
syntax error at /usr/sbin/exiqgrep line 56, near ") {"
syntax error at /usr/sbin/exiqgrep line 56, near ";}"
syntax error at /usr/sbin/exiqgrep line 57, near ";}"
syntax error at /usr/sbin/exiqgrep line 58, near ";}"
Execution of /usr/sbin/exiqgrep aborted due to compilation errors.

Version 4.95-4ubuntu1 uses patch 
75_35-Exiqgrep-check-arg-parsing.-Bug-2821.patch to fix bug 2821.
This patch reflects upstream commit df618101a5ea15dc90c4a2968798ef2be9dba16f.
This upstream commit introduced a syntax error and have been fixed by a later 
commit 42ed39da5af85552a35626348bb77e5576e18aa4.

The patch 75_35-Exiqgrep-check-arg-parsing.-Bug-2821.patch should be
amended to reflect this late fix in order to avoid syntax error with
command exiqgrep.

Upstream bug : https://bugs.exim.org/show_bug.cgi?id=2821

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: exim4 4.95-4ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Mar 29 12:37:59 2022
InstallationDate: Installed on 2022-01-06 (81 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211229)
PackageArchitecture: all
SourcePackage: exim4
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: exim
 Importance: Unknown
 Status: Unknown

** Affects: exim4 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

** Bug watch added: bugs.exim.org/ #2821
   http://bugs.exim.org/show_bug.cgi?id=2821

** Also affects: exim via
   http://bugs.exim.org/show_bug.cgi?id=2821
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966923

Title:
  exiqgrep -r and -f options match all messages if no

To manage notifications about this bug go to:
https://bugs.launchpad.net/exim/+bug/1966923/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912750] Re: samba-tool domain provision crash with "password hash userPassword schemes" parameter

[EOLE team]

But it's OK on jammy with actual package :

root@eolebase:~# apt policy samba
samba:
  Installé : 2:4.15.5~dfsg-0ubuntu2
  Candidat : 2:4.15.5~dfsg-0ubuntu2
 Table de version :
 *** 2:4.15.5~dfsg-0ubuntu2 500
500 http://test-eole.ac-dijon.fr/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status

So this bug can be closed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912750

Title:
  samba-tool domain provision crash with "password hash userPassword
  schemes" parameter

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1912750/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912750] Re: samba-tool domain provision crash with "password hash userPassword schemes" parameter

[EOLE team]

The bug is still there on focal with the latest package :

root@eolebase:~# apt policy samba
samba:
  Installé : 2:4.13.17~dfsg-0ubuntu0.21.04.1
  Candidat : 2:4.13.17~dfsg-0ubuntu0.21.04.1
 Table de version :
 *** 2:4.13.17~dfsg-0ubuntu0.21.04.1 500
500 http://test-eole.ac-dijon.fr/ubuntu focal-security/main amd64 
Packages
500 http://test-eole.ac-dijon.fr/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2:4.11.6+dfsg-0ubuntu1 500
500 http://test-eole.ac-dijon.fr/ubuntu focal/main amd64 Packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912750

Title:
  samba-tool domain provision crash with "password hash userPassword
  schemes" parameter

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1912750/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1943536] Re: Number filedescriptors allowed too low for squid on Focal

[EOLE team]

Thank you for your answers.

I confirm that using the Squid configuration directive
max_filedescriptors gives the same result and avoid overriding the
systemd unit.

root@eolebase:~# echo "max_filedescriptors 65535" >> /etc/squid/squid.conf
root@eolebase:~# systemctl restart squid.service
root@eolebase:~# squidclient mgr:info | grep descriptors
stub time| WARNING: BCP 177 violation. Detected non-functional IPv6 loopback.
Maximum number of file descriptors:   65535
Available number of file descriptors: 65530
Reserved number of file descriptors:   100
root@eolebase:~#

We will apply this solution.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943536

Title:
  Number filedescriptors allowed too low for squid on Focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/squid/+bug/1943536/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1943536] [NEW] Number filedescriptors allowed too low for squid on Focal

[EOLE team]

Public bug reported:

On Ubuntu Bionic the maximum number of file descriptors was set to 65535
in system V initscript :

root@eolebase:~# cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.6 LTS"
root@eolebase:~# squidclient mgr:info | grep descriptors
Maximum number of file descriptors:   65535
Available number of file descriptors: 65529
Reserved number of file descriptors:   100
root@eolebase:~# grep 65535 /etc/init.d/squid 
ulimit -n 65535
ulimit -n 65535
root@eolebase:~# 


On Ubuntu Focal the maximum number of file descriptors is not modified by the 
(new) systemd initscript and errors like *WARNING! Your cache is running out of 
filedescriptors* ends up happening :

root@eolebase:~# cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS"
root@eolebase:~# squidclient mgr:info | grep descriptors
stub time| WARNING: BCP 177 violation. Detected non-functional IPv6 loopback.
Maximum number of file descriptors:   1024
Available number of file descriptors: 1019
Reserved number of file descriptors:   100
root@eolebase:~# 


It is possible to bypass that by overriding the unit but this adaptation should 
be in native squid systemd unit because it's a regression regression compared 
to Bionic :

root@eolebase:~# cat >>/etc/systemd/system/squid.service.d/override.conf 

[Bug 1934997] Re: Authentication fails after upgrading sssd to 2.2.3-3ubuntu0.6

[EOLE team]

We found issues too and work around it by using 'access_provider =
permit' instead of 'access_provider = ad'.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934997

Title:
  Authentication fails after upgrading sssd to 2.2.3-3ubuntu0.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1934997/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934187] Re: lxd exec fails

[EOLE team]

I tested LXD and lxc for #1934187.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934187

Title:
  lxd exec fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934187/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934099] Re: 4.15.0-149-generic: lxc-attach lsm/lsm.c: lsm_process_label_set_at: 174 Operation not permitted - Failed to set AppArmor label "lxc-container-default-cgns"

[EOLE team]

*** This bug is a duplicate of bug 1934187 ***
https://bugs.launchpad.net/bugs/1934187

Tester on 4.15.0-150

  lxc-create -n bidule -t ubuntu
  […]
  lxc-start -n bidule -d
  lxc-attach -n bidule
  root@bidule:~# 

Thanks.

** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934099

Title:
  4.15.0-149-generic: lxc-attach lsm/lsm.c: lsm_process_label_set_at:
  174 Operation not permitted - Failed to set AppArmor label "lxc-
  container-default-cgns"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934099/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934099] [NEW] 4.15.0-149-generic: lxc-attach lsm/lsm.c: lsm_process_label_set_at: 174 Operation not permitted - Failed to set AppArmor label "lxc-container-default-cgns"

[EOLE team]

Public bug reported:

Hello.

When testing with the bionic-proposed repository, we found that the
4.15.0-149-generic break the lxc-attach command with the following
error:

  lxc-attach: bidule: lsm/lsm.c: lsm_process_label_set_at: 174 Operation
not permitted - Failed to set AppArmor label "lxc-container-default-
cgns"

We don't have this issue with the current 4.15.0-147.

There is no issue using the --elevated-privileges option of lxc-attach.

I join the debug log of “lxc-attach -n bidule -l debug”.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-149-generic 4.15.0-149.153
ProcVersionSignature: Ubuntu 4.15.0-149.153-generic 4.15.18
Uname: Linux 4.15.0-149-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 juin  30 10:15 seq
 crw-rw 1 root audio 116, 33 juin  30 10:15 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.24
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Jun 30 10:21:54 2021
HibernationDevice: RESUME=/dev/mapper/bionic--vg-swap_1
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
 
ProcEnviron:
 TERM=screen.xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-149-generic 
root=/dev/mapper/hostname--vg-root ro console=tty1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-149-generic N/A
 linux-backports-modules-4.15.0-149-generic  N/A
 linux-firmware  1.173.20
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.12.0-1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-3.1
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-3.1
dmi.sys.vendor: QEMU

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic package-from-proposed

** Attachment added: "lxc-attach.debug.log"
   
https://bugs.launchpad.net/bugs/1934099/+attachment/5508086/+files/lxc-attach.debug.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934099

Title:
  4.15.0-149-generic: lxc-attach lsm/lsm.c: lsm_process_label_set_at:
  174 Operation not permitted - Failed to set AppArmor label "lxc-
  container-default-cgns"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934099/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912750] Re: samba-tool domain provision crash with "password hash userPassword schemes" parameter

[EOLE team]

Thank you for taking care of this problem.
I confirm we don't use FIPS mode.
And unfortunately, the PPA provided doesn't fix the bug for us.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912750

Title:
  samba-tool domain provision crash with "password hash userPassword
  schemes" parameter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1912750/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912750] [NEW] samba-tool domain provision crash with "password hash userPassword schemes" parameter

[EOLE team]

Public bug reported:

On focal, when I try to initialize samba (2:4.11.6+dfsg-0ubuntu1.6
amd64) with this parameter in my smb.conf, I always get an error.

root@eolebase:~# grep schemes /etc/samba/smb.conf 
  password hash userPassword schemes = CryptSHA256 CryptSHA512

root@eolebase:~# samba-tool domain provision --use-rfc230   
--realm="AC-TEST.FR" --domain="AC-TEST" --adminpass="By65Killer" 
--server-role=dc --host-ip=192.168.0.24
INFO 2021-01-22 09:59:58,050 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #2145: Looking up 
IPv6 addresses
WARNING 2021-01-22 09:59:58,050 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #2152: No IPv6 
address will be assigned
INFO 2021-01-22 09:59:58,323 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #2319: Setting up 
share.ldb
INFO 2021-01-22 09:59:58,357 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #2323: Setting up 
secrets.ldb
INFO 2021-01-22 09:59:58,381 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #2329: Setting up 
the registry
INFO 2021-01-22 09:59:58,462 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #2332: Setting up 
the privileges database
INFO 2021-01-22 09:59:58,504 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #2335: Setting up 
idmap db
INFO 2021-01-22 09:59:58,534 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #2342: Setting up 
SAM db
INFO 2021-01-22 09:59:58,542 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #898: Setting up 
sam.ldb partitions and settings
INFO 2021-01-22 09:59:58,543 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #910: Setting up 
sam.ldb rootDSE
INFO 2021-01-22 09:59:58,550 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #1339: Pre-loading 
the Samba 4 and AD schema
Unable to determine the DomainSID, can not enforce uniqueness constraint on 
local domainSIDs

INFO 2021-01-22 09:59:58,589 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #1417: Adding 
DomainDN: DC=ac-test,DC=fr
INFO 2021-01-22 09:59:58,602 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #1449: Adding 
configuration container
INFO 2021-01-22 09:59:58,653 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #1464: Setting up 
sam.ldb schema
INFO 2021-01-22 10:00:01,208 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #1482: Setting up 
sam.ldb configuration data
INFO 2021-01-22 10:00:01,350 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #1523: Setting up 
display specifiers
INFO 2021-01-22 10:00:03,204 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #1531: Modifying 
display specifiers and extended rights
INFO 2021-01-22 10:00:03,239 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #1538: Adding users 
container
INFO 2021-01-22 10:00:03,240 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #1544: Modifying 
users container
INFO 2021-01-22 10:00:03,241 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #1547: Adding 
computers container
INFO 2021-01-22 10:00:03,242 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #1553: Modifying 
computers container
INFO 2021-01-22 10:00:03,243 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #1557: Setting up 
sam.ldb data
INFO 2021-01-22 10:00:03,376 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #1587: Setting up 
well known security principals
INFO 2021-01-22 10:00:03,417 pid:4529 
/usr/lib/python3/dist-packages/samba/provision/__init__.py #1601: Setting up 
sam.ldb users and groups
ERROR(ldb): uncaught exception - setup_primary_userPassword: generation of a 
CryptSHA256 password hash failed: (Numerical result out of range)
  File "/usr/lib/python3/dist-packages/samba/netcmd/__init__.py", line 186, in 
_run
return self.run(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/samba/netcmd/domain.py", line 519, in run
result = provision(self.logger,
  File "/usr/lib/python3/dist-packages/samba/provision/__init__.py", line 2371, 
in provision
provision_fill(samdb, secrets_ldb, logger, names, paths,
  File "/usr/lib/python3/dist-packages/samba/provision/__init__.py", line 1958, 
in provision_fill
samdb = fill_samdb(samdb, lp, names, logger=logger,
  File "/usr/lib/python3/dist-packages/samba/provision/__init__.py", line 1602, 
in fill_samdb
setup_add_ldif(samdb, setup_path("provision_users.ldif"), {
  File "/usr/lib/python3/dist-packages/samba/provision/common.py", line 55, in 
setup_add_ldif
ldb.add_ldif(data, controls)
  File "/usr/lib/python3/dist-packages/samba/__init__.py", line 230, in add_ldif
self.add(msg, controls)

It seems to be the same as the upstream bug :
https://bugzilla.samba.org/show_bug.cgi?id=14424

[Bug 1908512] Re: VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso

[EOLE team]

I confirm that it's working with version 1.13.0-1ubuntu1.1.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908512

Title:
  VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1908512/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908512] Re: VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso

[EOLE team]

Thanks a lot

> a) do use a more modern default than cirrus (recommended anyway), QXL
being the most common one

Maybe libvirt should switch the default?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908512

Title:
  VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seabios/+bug/1908512/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908512] Re: VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso

[EOLE team]

I don't have issue to boot the debian-10.7.0-amd64-DVD-1.iso

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908512

Title:
  VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1908512/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908512] Re: VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso

[EOLE team]

I tested on hirsute and it's working fine.

I don't see meaningful differences between focal and hirsute:

- For the XML

--- ubuntu-server-20.04.1-on-focal.xml  2020-12-17 15:02:28.678279263 +0100
+++ ubuntu-server-20.04.1-on-hirsute.xml2020-12-17 14:47:50.790210994 
+0100
@@ -1,6 +1,6 @@
 
   ubuntu-server-20.04.1
-  65166cc6-7cec-47e3-bd85-390f60a71d01
+  48ce4792-c557-4e02-a946-a23d23cabf85
   ubuntu-server-20.04.1
   2097152
   2097152
@@ -12,7 +12,7 @@
 /machine
   
   
-hvm
+hvm
   
   
 
@@ -88,8 +88,8 @@
 
   
   
-libvirt-65166cc6-7cec-47e3-bd85-390f60a71d01
-libvirt-65166cc6-7cec-47e3-bd85-390f60a71d01
+libvirt-48ce4792-c557-4e02-a946-a23d23cabf85
+libvirt-48ce4792-c557-4e02-a946-a23d23cabf85
   
   
 +64055:+108

- For the QEMU command lines

--- qemu-cmdline-focal.txt  2020-12-17 15:04:52.973631013 +0100
+++ qemu-cmdline-hirsute.txt2020-12-17 14:46:24.018597093 +0100
@@ -2,12 +2,12 @@
 -name guest=ubuntu-server-20.04.1,debug-threads=on
 -S
 -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-ubuntu-server-20.04./master-key.aes
--machine pc-i440fx-focal,accel=kvm,usb=off,dump-guest-core=off
+-machine pc-i440fx-hirsute,accel=kvm,usb=off,dump-guest-core=off
 -cpu qemu64
 -m 2048
 -overcommit mem-lock=off
 -smp 4,sockets=4,cores=1,threads=1
--uuid 65166cc6-7cec-47e3-bd85-390f60a71d01
+-uuid 48ce4792-c557-4e02-a946-a23d23cabf85
 -no-user-config
 -nodefaults
 -chardev socket,id=charmonitor,fd=31,server,nowait

So, it may be a qemu issue?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908512

Title:
  VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1908512/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908531] [NEW] lemonldap-ng doesn't handle ldap attribute equal to 0

[EOLE team]

Public bug reported:

Hello,

There is a bug with the provided lemonldap-ng focal package, it doesn't handle 
ldap attribute equal to 0.
We reported the issue to Lemonldap 
(https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/issues/2403).
They aknoledged the issue and fixed it in the master branch.
Could you apply the following patch in the package ?

Patch to apply : https://gitlab.ow2.org/lemonldap-ng/lemonldap-
ng/-/commit/8793a5b6a128657556674daa1d9b5090c2b70c11

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lemonldap-ng 2.0.7+ds-2
ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
Uname: Linux 5.4.0-59-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Dec 17 14:32:08 2020
InstallationDate: Installed on 2020-12-02 (14 days ago)
InstallationMedia: EOLE 2.8.0-rc1 "Focal Fossa" - Release amd64 (20201202)
PackageArchitecture: all
SourcePackage: lemonldap-ng
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lemonldap-ng (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908531

Title:
  lemonldap-ng doesn't handle ldap attribute equal to 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lemonldap-ng/+bug/1908531/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908512] RelatedPackageVersions.txt

[EOLE team]

apport information

** Attachment added: "RelatedPackageVersions.txt"
   
https://bugs.launchpad.net/bugs/1908512/+attachment/564/+files/RelatedPackageVersions.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908512

Title:
  VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1908512/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908512] ProcCpuinfoMinimal.txt

[EOLE team]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1908512/+attachment/563/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908512

Title:
  VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1908512/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908512] KernLog.txt

[EOLE team]

apport information

** Attachment added: "KernLog.txt"
   
https://bugs.launchpad.net/bugs/1908512/+attachment/562/+files/KernLog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908512

Title:
  VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1908512/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908512] Dependencies.txt

[EOLE team]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1908512/+attachment/561/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908512

Title:
  VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1908512/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908512] [NEW] VNC unusable when booting ubuntu-20.04.1-live-server-amd64.iso

[EOLE team]

Public bug reported:

Hello.

I can't boot ubuntu-20.04.1-live-server-amd64.iso with VNC graphic
using libvirt, there is an error message:

  graphics initialization failed
  Error setting up gfxboot
  boot:

after a moment, I see some other messages:


  graphics initialization failed
  Error setting up gfxboot
  boot:
  Could not allocate memory.
  boot
  Could not allocate memory.
  boot
  Could not allocate memory.
  boot

To reproduce:

- download ubuntu-20.04.1-live-server-amd64.iso to
  /var/lib/libvirt/images

- create a qcow2 image /var/lib/libvirt/images/disk0.qcow2

- create the following libvirt XML definition file


ubuntu-server-20.04.1
ubuntu-server-20.04.1


205

2097152

hvm

























- define the domaine with: virsh define ubuntu-server.xml

- start the domain with: virsh start ubuntu-server-20.04.1

- connect to the VNC port 5901

It's working fine when I try the following:

  qemu-system-x86_64 -m 2048 -smp 1 -vnc 0.0.0.0:1 -k fr -name test-boot
-monitor pty -boot order=d -drive
file=/var/lib/libvirt/images/disk0.qcow2,media=disk -drive
file=/var/lib/libvirt/images/ubuntu-20.04.1-live-server-
amd64.iso,media=cdrom


The non working qemu command line used by libvirt is:

  /usr/bin/qemu-system-x86_64 -name 
guest=ubuntu-server-20.04.1,debug-threads=on -S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-7-ubuntu-server-20.04./master-key.aes
 -machine pc-i440fx-focal,accel=kvm,usb=off,dump-guest-core=off -cpu qemu64 -m 
2048 -overcommit mem-lock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 
503e911c-f7a5-48ef-8241-36bdbc75b9a3 -no-user-config -nodefaults -chardev 
socket,id=charmonitor,fd=31,server,nowait -mon 
chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -no-acpi 
-boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device 
lsi,id=scsi0,bus=pci.0,addr=0x3 -blockdev 
{"driver":"file","filename":"/var/lib/libvirt/images/disk0.qcow2","node-name":"libvirt-2-storage","cache":{"direct":true,"no-flush":false},"auto-read-only":true,"discard":"unmap"}
 -blockdev 
{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":true,"no-flush":false},"driver":"qcow2","file":"libvirt-2-storage","backing":null}
 -device 
scsi-hd,bus=scsi0.0,scsi-id=0,device_id=drive-scsi0-0-0,drive=libvirt-2-format,id=scsi0-0-0,bootindex=1,write-cache=on
 -blockdev 
{"driver":"file","filename":"/var/lib/libvirt/images/ubuntu-20.04.1-live-server-amd64.iso","node-name":"libvirt-1-storage","cache":{"direct":true,"no-flush":false},"auto-read-only":true,"discard":"unmap"}
 -blockdev 
{"node-name":"libvirt-1-format","read-only":true,"cache":{"direct":true,"no-flush":false},"driver":"raw","file":"libvirt-1-storage"}
 -device 
ide-cd,bus=ide.0,unit=0,drive=libvirt-1-format,id=ide0-0-0,bootindex=2,write-cache=on
 -vnc 0.0.0.0:1 -k fr -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -sandbox 
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg 
timestamp=on
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
Package: libvirt-daemon-system 6.0.0-0ubuntu8.5
PackageArchitecture: amd64
ProcCmdline: BOOT_IMAGE=/vmlinuz-5.4.0-58-generic 
root=/dev/mapper/vggrichka-root ro quiet splash vt.handoff=7
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Tags:  focal
Uname: Linux 5.4.0-58-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [modified]
modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [modified]
modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [modified]
modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [modified]
modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [modified]
modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [modified]
modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [modified]
modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: [modified]
modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: [modified]
modified.conffile..etc.libvirt.nwfilter.no-arp-spoofing.xml: [modified]
modified.conffile..etc.libvirt.nwfilter.no-ip-multicast.xml: [modified]

[Bug 1904166] Re: chpasswd can't change password with libpam-passwdqc enabled

[EOLE team]

The solution is to provide a dedicated pam configuration for chpasswd
without the ask_oldauthtok option.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904166

Title:
  chpasswd can't change password with libpam-passwdqc enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1904166/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904166] Re: chpasswd can't change password with libpam-passwdqc enabled

[EOLE team]

To reproduce:

apt install libpam-passwdqc
sed -i -e 's/\(pam_passwdqc.so\)/\1 ask_oldauthtok/' 
/etc/pam.d/common-password
echo 'root:hearth=mirth-Double' | chpasswd

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904166

Title:
  chpasswd can't change password with libpam-passwdqc enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1904166/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904166] Re: chpasswd can't change password with libpam-passwdqc enabled

[EOLE team]

It may be due to the libpam-passwdqc configuration using ask_oldauthtok
and similar=deny.

It was working fine on Bionic but fails with Focal.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904166

Title:
  chpasswd can't change password with libpam-passwdqc enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1904166/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904166] [NEW] chpasswd can't change password with libpam-passwdqc enabled

[EOLE team]

Public bug reported:

Hello.

We are unable to change user password using chpasswd with libpam-
passwdqc, it seems to miss detect old password:

root@server:~# echo 'root:hearth=mirth-Double' | chpasswd
[…]
Weak password: is the same as the old one.
Try again.

root@server:~# echo $?
1

I tried the following to make sure the old password was not the same:

root@server:~# echo 'root:foo' | chpasswd -c SHA512
root@server:~# echo 'root:hearth=mirth-Double' | chpasswd
[…]
Weak password: is the same as the old one.
Try again.

root@server:~# echo $?
1

** Affects: shadow (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904166

Title:
  chpasswd can't change password with libpam-passwdqc enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1904166/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794523] Re: lxc-net.service is not properly ordered with network-online.target

[EOLE team]

There is still a problem :-/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794523

Title:
  lxc-net.service is not properly ordered with network-online.target

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1794523/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1861880] Re: lxc-attach command does not return error exit code if the command is failed

[EOLE team via ubuntu-bugs]

OK for us with 1:4.0.1-0ubuntu2 package on focal :

root@scribe:~# lxc-start --version
4.0.1
root@scribe:~# lxc-attach --logpriority=DEBUG --name=addc -- exit
lxc-attach: addc: attach.c: lxc_attach_run_command: 1452 No such file or 
directory - Failed to exec "exit"
root@scribe:~# echo $?
127

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861880

Title:
  lxc-attach command does not return error exit code if the command is
  failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1861880/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794523] Re: lxc-net.service is not properly ordered with network-online.target

[EOLE team via ubuntu-bugs]

Hello.

Only the Requires= will make it fail, no Wants=

A weaker version of Requires=. Units listed in this option will be started 
if the
configuring unit is. However, if the listed units fail to start or cannot 
be added to
the transaction, this has no impact on the validity of the transaction as a 
whole.
This is the recommended way to hook start-up of one unit to the start-up of 
another
unit.

https://manpages.ubuntu.com/manpages/bionic/en/man5/systemd.unit.5.html

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794523

Title:
  lxc-net.service is not properly ordered with network-online.target

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1794523/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1857252] Re: chromium 79 remote display broken

[EOLE team via ubuntu-bugs]

** Bug watch added: Debian Bug tracker #949440
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949440

** Also affects: chromium (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949440
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857252

Title:
  chromium 79 remote display broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1857252/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1861880] [NEW] lxc-attach command does not return error exit code if the command is failed

[EOLE team via ubuntu-bugs]

Public bug reported:

lxc-attach command does not return error exit code if the command is
failed on Ubuntu Focal :

root@scribe:~# lxc-start --version
3.0.4
root@scribe:~# lxc-attach --logpriority=DEBUG --name=addc -- exit
lxc-attach: addc: attach.c: lxc_attach_run_command: 1489 No such file or 
directory - Failed to exec "exit" 
root@scribe:~# echo $?
0

The problem is fixed upstream : https://github.com/lxc/lxc/issues/3104
and by Debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934983

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lxc-utils 3.0.4-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
Date: Tue Feb  4 16:01:30 2020
InstallationDate: Installed on 2020-01-10 (25 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200105)
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
 lxc.net.0.type = veth
 lxc.net.0.link = lxcbr0
 lxc.net.0.flags = up
 lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx
lxc-net.default:
 USE_LXC_BRIDGE="true"
 LXC_BRIDGE="br0"
 LXC_ADDR="192.0.2.1"
 LXC_NETMASK="255.255.255.0"
 LXC_NETWORK="192.0.2.0/24"

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: lxc (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apparmor apport-bug focal uec-images

** Bug watch added: Debian Bug tracker #934983
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934983

** Also affects: lxc (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934983
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861880

Title:
  lxc-attach command does not return error exit code if the command is
  failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1861880/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1835714] [NEW] no CDROM labels in udevadm info since 4.4.0-155.182

[EOLE team]

Public bug reported:

When I upgrade a xenial server with the kernel in proposed, my CDROM are
not linked anymore under /dev/disk/by-label/.

My ext4 filesystems are present under /dev/disk/by-label/.

Before the upgrade:

uname -a
Linux eolebase 4.4.0-154-generic #181-Ubuntu SMP Tue Jun 25 05:29:03 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

# OpenNebula provides a context CDROM to configure the VM, the LABEL is reported
udevadm info /dev/sr0
P: /devices/pci:00/:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sr0
N: sr0
L: -100
S: cdrom
S: disk/by-id/ata-QEMU_DVD-ROM_QM1
S: disk/by-label/CONTEXT
S: disk/by-path/pci-:00:01.1-ata-1
S: disk/by-uuid/2019-07-08-09-47-08-00
S: dvd
E: DEVLINKS=/dev/dvd /dev/disk/by-path/pci-:00:01.1-ata-1 /dev/cdrom 
/dev/disk/by-uuid/2019-07-08-09-47-08-00 /dev/disk/by-label/CONTEXT 
/dev/disk/by-id/ata-QEMU_DVD-ROM_QM1
E: DEVNAME=/dev/sr0
E: 
DEVPATH=/devices/pci:00/:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sr0
E: DEVTYPE=disk
E: ID_ATA=1
E: ID_BUS=ata
E: ID_CDROM=1
E: ID_CDROM_DVD=1
E: ID_CDROM_MEDIA=1
E: ID_CDROM_MEDIA_CD=1
E: ID_CDROM_MEDIA_SESSION_COUNT=1
E: ID_CDROM_MEDIA_TRACK_COUNT=1
E: ID_CDROM_MEDIA_TRACK_COUNT_DATA=1
E: ID_CDROM_MRW=1
E: ID_CDROM_MRW_W=1
E: ID_FOR_SEAT=block-pci-_00_01_1-ata-1
E: 
ID_FS_APPLICATION_ID=GENISOIMAGE\x20ISO\x209660\x2fHFS\x20FILESYSTEM\x20CREATOR\x20\x28C\x29\x201993\x20E.YOUNGDALE\x20\x28C\x29\x201997-2006\x20J.PEARSON\x2fJ.SCHILLING\x20\x28C\x29\x202006-2007\x20CDRKIT\x20TEAM
E: ID_FS_LABEL=CONTEXT
E: ID_FS_LABEL_ENC=CONTEXT
E: ID_FS_SYSTEM_ID=LINUX
E: ID_FS_TYPE=iso9660
E: ID_FS_USAGE=filesystem
E: ID_FS_UUID=2019-07-08-09-47-08-00
E: ID_FS_UUID_ENC=2019-07-08-09-47-08-00
E: ID_FS_VERSION=Joliet Extension
E: ID_MODEL=QEMU_DVD-ROM
E: 
ID_MODEL_ENC=QEMU\x20DVD-ROM\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_PATH=pci-:00:01.1-ata-1
E: ID_PATH_TAG=pci-_00_01_1-ata-1
E: ID_REVISION=2.5+
E: ID_SERIAL=QEMU_DVD-ROM_QM1
E: ID_SERIAL_SHORT=QM1
E: ID_TYPE=cd
E: MAJOR=11
E: MINOR=0
E: SUBSYSTEM=block
E: TAGS=:uaccess:systemd:seat:
E: USEC_INITIALIZED=2519001


After the upgrade:

uname -a
Linux eolebase 4.4.0-155-generic #182-Ubuntu SMP Tue Jul 2 14:43:15 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

# There is no more LABEL
udevadm info /dev/sr0
P: /devices/pci:00/:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sr0
N: sr0
L: -100
S: cdrom
S: disk/by-id/ata-QEMU_DVD-ROM_QM1
S: disk/by-path/pci-:00:01.1-ata-1
S: dvd
E: DEVLINKS=/dev/disk/by-id/ata-QEMU_DVD-ROM_QM1 
/dev/disk/by-path/pci-:00:01.1-ata-1 /dev/dvd /dev/cdrom
E: DEVNAME=/dev/sr0
E: 
DEVPATH=/devices/pci:00/:00:01.1/ata1/host0/target0:0:0/0:0:0:0/block/sr0
E: DEVTYPE=disk
E: ID_ATA=1
E: ID_BUS=ata
E: ID_CDROM=1
E: ID_CDROM_DVD=1
E: ID_CDROM_MEDIA=1
E: ID_CDROM_MRW=1
E: ID_CDROM_MRW_W=1
E: ID_FOR_SEAT=block-pci-_00_01_1-ata-1
E: ID_MODEL=QEMU_DVD-ROM
E: 
ID_MODEL_ENC=QEMU\x20DVD-ROM\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_PATH=pci-:00:01.1-ata-1
E: ID_PATH_TAG=pci-_00_01_1-ata-1
E: ID_REVISION=2.5+
E: ID_SERIAL=QEMU_DVD-ROM_QM1
E: ID_SERIAL_SHORT=QM1
E: ID_TYPE=cd
E: MAJOR=11
E: MINOR=0
E: SUBSYSTEM=block
E: TAGS=:uaccess:systemd:seat:
E: USEC_INITIALIZED=1540484


# The LABEL is set on the filesystem
blkid /dev/sr0 
/dev/sr0: UUID="2019-07-08-09-47-08-00" LABEL="CONTEXT" TYPE="iso9660"


lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.6 LTS
Release:16.04
Codename:   xenial

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-155-generic 4.4.0-155.182
ProcVersionSignature: Ubuntu 4.4.0-155.182-generic 4.4.181
Uname: Linux 4.4.0-155-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Mon Jul  8 09:57:30 2019
InstallationDate: Installed on 2018-07-02 (370 days ago)
InstallationMedia: EOLE 2.6.2.1 "Xenial Xerus" - Release amd64 (20180702)
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug package-from-proposed xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835714

Title:
  no CDROM labels in udevadm info since 4.4.0-155.182

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1835714/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823332] Re: salt --versions-report broken in bionic/cosmic with openssl 1.1.1

[EOLE team]

Hello.

Is there any blocking thing for Bionic?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823332

Title:
  salt --versions-report broken in bionic/cosmic with openssl 1.1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/salt/+bug/1823332/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

[EOLE team]

Thank @xnox, I just made the test and I have the same issue with rebuilt
python3.6.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797386

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

[EOLE team]

The libssl1.1 version 1.1.1-1ubuntu2.1~18.04.1 breaks salt package
version 2017.7.4+dfsg1-1:

root@server:~# salt-key -L
Error: unknown error (_ssl.c:2788)

root@server:~# salt --versions-report
Traceback (most recent call last):
  File "/usr/bin/salt", line 10, in 
salt_main()
  File "/usr/lib/python3/dist-packages/salt/scripts.py", line 476, in salt_main
client.run()
  File "/usr/lib/python3/dist-packages/salt/cli/salt.py", line 33, in run
import salt.client
  File "/usr/lib/python3/dist-packages/salt/client/__init__.py", line 31, in 

import salt.cache
  File "/usr/lib/python3/dist-packages/salt/cache/__init__.py", line 18, in 

import salt.loader
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 26, in 
import salt.utils.event
  File "/usr/lib/python3/dist-packages/salt/utils/event.py", line 70, in 

import tornado.iostream
  File "/usr/lib/python3/dist-packages/tornado/iostream.py", line 40, in 

from tornado.netutil import ssl_wrap_socket, ssl_match_hostname, 
SSLCertificateError, _client_ssl_defaults, _server_ssl_defaults
  File "/usr/lib/python3/dist-packages/tornado/netutil.py", line 57, in 
ssl.Purpose.SERVER_AUTH)
  File "/usr/lib/python3.6/ssl.py", line 502, in create_default_context
context = SSLContext(PROTOCOL_TLS)
  File "/usr/lib/python3.6/ssl.py", line 391, in __new__
self = _SSLContext.__new__(cls, protocol)
ssl.SSLError: unknown error (_ssl.c:2788)

Seems to be python3.6 which is impacted.

Regards.

** Also affects: salt (Ubuntu)
   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/1797386

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1813873] Re: Userspace break as a result of missing patch backport

[EOLE team]

I tested the kernel 4.4.0-143 from xenial-proposed on 16.04 and from
trusty-proposed on 14.04 and it fix the problem for these 2 releases.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813873

Title:
  Userspace break as a result of missing patch backport

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1814261] [NEW] gpm prevents loging to the console: spurious “Enter” events seems inserted

[EOLE team]

Public bug reported:

Hello,

When our servers boot, We can't login because of spurious “enter”.

We have this problem on virtual and physical machines since:

* kernel linux-image-4.15.0-44-generic on bionic
* kernel linux-image-4.4.0-142-generic on xenial

To reproduce:

1. start an ubuntu server with the specific kernel
2. install GPM
3. on a console
   1. type the user name “root”
   2. hit “enter”
   3. wait few seconds => spurious “Enter” are send to the console
4. Stop gpm.service
5. retry to login on a console => no problem


lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic

** Affects: gpm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814261

Title:
  gpm prevents loging to the console: spurious “Enter” events seems
  inserted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1814261/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1795343] Re: netplan backported on bionic (0.40~18.04.1) crash when there is an empty YAML configuration file

[EOLE team]

OK with 0.40.1~18.04.3

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795343

Title:
  netplan backported on bionic (0.40~18.04.1) crash when there is an
  empty YAML configuration file

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1795343/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1795343] Re: netplan backported on bionic (0.40~18.04.1) crash when there is an empty YAML configuration file

[EOLE team]

It's working fine with version 0.40.1~18.04.1.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795343

Title:
  netplan backported on bionic (0.40~18.04.1) crash when there is an
  empty YAML configuration file

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1795343/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600164] Re: Mysql server take 10 minutes to stop without message after time drift

[EOLE team]

Yes, it will delay the start of MySQL server but the consequence of
going backward in time after MySQL is started are important enough to
me.

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600164

Title:
  Mysql server take 10 minutes to stop without message after time drift

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1600164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600164] Re: Mysql server take 10 minutes to stop without message after time drift

[EOLE team]

I just made the test to be sure: using Wants= does not prevent MySQL to
start event if the system never reaches “time-sync.target”.

I added an ntpdate.service:

  # /etc/systemd/system/ntpdate.service
  [Unit]
  Description=Force synchronisation of time
  ConditionPathExists=/etc/default/ntpdate
  DefaultDependencies=no
  Conflicts=shutdown.target
  After=network-online.target
  Before=time-sync.target shutdown.target
  Wants=network-online.target time-sync.target
  
  [Service]
  Type=oneshot
  Environment="NTPSERVERS=pool.ntp.org"
  EnvironmentFile=/etc/default/ntpdate
  ExecStart=/usr/sbin/ntpdate -v $NTPSERVERS
  RemainAfterExit=yes
  
  [Install]
  WantedBy=sysinit.target

And an override for MySQL:

  # /etc/systemd/system/mysql.service.d/override.conf
  [Unit]
  After=network-online.target time-sync.target
  Wants=network-online.target time-sync.target

ntpdate.service is failed:

  systemctl status ntpdate.service
  ● ntpdate.service - Force synchronisation of time
 Loaded: loaded (/etc/systemd/system/ntpdate.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Mon 2018-10-15 16:51:25 CEST; 40s 
ago
Process: 1129 ExecStart=/usr/sbin/ntpdate -v $NTPSERVERS (code=exited, 
status=1/FAILURE)
   Main PID: 1129 (code=exited, status=1/FAILURE)

But MySQL is started:

  systemctl status mysql.service
  ● mysql.service - MySQL Community Server
 Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: 
enabled)
Drop-In: /etc/systemd/system/mysql.service.d
 └─override.conf
 Active: active (running) since Mon 2018-10-15 16:51:27 CEST; 3min 17s ago
Process: 1600 ExecStart=/usr/sbin/mysqld --daemonize 
--pid-file=/run/mysqld/mysqld.pid (code=exited, status=0/SUCCESS)
Process: 1550 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre 
(code=exited, status=0/SUCCESS)
   Main PID: 1602 (mysqld)
  Tasks: 30 (limit: 4915)
 CGroup: /system.slice/mysql.service
 └─1602 /usr/sbin/mysqld --daemonize 
--pid-file=/run/mysqld/mysqld.pid


Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600164

Title:
  Mysql server take 10 minutes to stop without message after time drift

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1600164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600164] Re: Mysql server take 10 minutes to stop without message after time drift

[EOLE team]

I think the problem can be solved with:

* recent systemd fixes https://github.com/systemd/systemd/issues/5097 (with a 
workaround for older versions)
* fixing mysql.service to use After=time-sync.target and Wants=time-sync.target

Regards.

** Bug watch added: github.com/systemd/systemd/issues #5097
   https://github.com/systemd/systemd/issues/5097

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600164

Title:
  Mysql server take 10 minutes to stop without message after time drift

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1600164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1794523] [NEW] lxc-net.service is not properly ordered with network-online.target

[EOLE team]

Public bug reported:

I made several tests and I figure out that the lxc-net.service is
missing a Wants= directive to be properly ordered against network-
online.target.

As I understand the systemd.unit manpage, to be properly ordered a unit
must define a Requires=/Wants= in addition to an After=/Before=.

Regards.

Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794523

Title:
  lxc-net.service is not properly ordered with network-online.target

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1794523/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1724895] Re: MTU not applied on private ethernet interfaces

[EOLE team]

I have the same here.

Netplan creates .link with

[Match]
OriginalName=ens4

Which can't be used since the network interface was already renamed

[...]
Jul 02 15:46:09 eolebase kernel: virtio_net virtio1 ens4: renamed from eth0
[...]
Jul 02 15:46:09 eolebase systemd-udevd[310]: Config file 
/run/systemd/network/10-netplan-ens4.link matches device based on renamed 
interface name 'ens4', ignoring

I see two options:

1) Match on the MACAddress
2) Define the link properties in the .network file

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895

Title:
  MTU not applied on private ethernet interfaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1724895/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1757125] [NEW] DHCP relay doesn't work on boot when a lot of VLAN network interfaces

[EOLE team]

Public bug reported:

1) lsb_release -rd
Description:Ubuntu 14.04.5 LTS
Release:14.04

2) apt-cache policy isc-dhcp-relay
isc-dhcp-relay:
  Installé : 4.2.4-7ubuntu12.13
  Candidat : 4.2.4-7ubuntu12.13


We are using isc-dhcp package on Ubuntu trusty server.
The server has 4 physical network interfaces and several VLAN on eth2 interface.
dhcrelay is configured to relay dhcp requests from eth3 to VLAN interfaces.

On boot, depending on hardware velocity, the DHCP relay doesn't work.
In /etc/init/isc-dhcp-relay.conf, we can see "start on runlevel [2345]", but if 
all network interfaces are not ready, some errors appear in log file :
"2018-03-20T10:58:45.229688+01:00 amon.etb1.lan dhcrelay: Error getting 
hardware address for "eth2.4": No such device"
We must restart isc-dhcp-relay service once all network interfaces are ready.

To resolve this problem, we added /etc/init/isc-dhcp-relay.override file
containing "start on (runlevel [2345] and static-network-up)" to make
sure that isc-dhcp-relay starts when all network interfaces are ready.

Can we hope that you integrate this hotfix ?

** Affects: isc-dhcp (Ubuntu)
 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/1757125

Title:
  DHCP relay doesn't work on boot when a lot of VLAN network interfaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1757125/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576618] Re: Unable to install sympa with dbconfig-no-thanks

[EOLE team]

The problem exists on Bionic too.

** Tags added: bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576618

Title:
  Unable to install sympa with dbconfig-no-thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sympa/+bug/1576618/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749143] Re: BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad address

[EOLE team]

Hello,

I just made the test with the latest v4.4 stable kernel and it's
working.

Then I tried an upgrade since I saw the linux-image-4.4.0-116-generic
from -proposed and fping is working with this kernel.

Regards.

** Tags added: kernel-fixed-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749143

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749143] ProcInterrupts.txt

[EOLE team]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1749143/+attachment/5054380/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749143

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749143] WifiSyslog.txt

[EOLE team]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1749143/+attachment/5054383/+files/WifiSyslog.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749143

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749143] ProcModules.txt

[EOLE team]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1749143/+attachment/5054381/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749143

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749143] UdevDb.txt

[EOLE team]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1749143/+attachment/5054382/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749143

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749143] ProcEnviron.txt

[EOLE team]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1749143/+attachment/5054379/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749143

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749143] Lspci.txt

[EOLE team]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1749143/+attachment/5054376/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749143

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749143] ProcCpuinfoMinimal.txt

[EOLE team]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1749143/+attachment/5054378/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749143

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749143] ProcCpuinfo.txt

[EOLE team]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1749143/+attachment/5054377/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749143

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749143] Re: BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad address

[EOLE team]

apport information

** Tags added: apport-collected

** Description changed:

  Hello,
  
  We test the -proposed packages before our ±25000 user servers get a
  chance to download it when it's in stable and we have an issue since the
  package linux-image-4.4.0-113-generic and linux-image-4.4.0-115-generic.
  
  We tried on KVM virtual machines
  
  To reproduce the problem, execute:
  
  # fping -t50 -r2 127.0.0.1
  127.0.0.1: error while sending ping: Bad address
  127.0.0.1: error while sending ping: Bad address
  127.0.0.1: error while sending ping: Bad address
  127.0.0.1 is unreachable
  
  We have no problem with ping:
  
  # ping -c 1 127.0.0.1
  PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
  64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.046 ms
  
  --- 127.0.0.1 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.046/0.046/0.046/0.000 ms
  
  fping is working fine under kernel 4.4.0-112:
  
  # fping -t50 -r2 127.0.0.1
  127.0.0.1 is alive
  
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 févr. 13 16:40 seq
+  crw-rw 1 root audio 116, 33 févr. 13 16:40 timer
+ AplayDevices: Error: [Errno 2] Aucun fichier ou dossier de ce type
+ ApportVersion: 2.20.1-0ubuntu2.15
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] Aucun fichier ou dossier de ce type
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=/dev/mapper/eolebase--vg-swap_1
+ IwConfig: Error: [Errno 2] Aucun fichier ou dossier de ce type
+ Lsusb:
+  Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
+  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-115-generic 
root=/dev/mapper/hostname--vg-root ro rootdelay=90
+ ProcVersionSignature: Ubuntu 4.4.0-115.139-generic 4.4.98
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-115-generic N/A
+  linux-backports-modules-4.4.0-115-generic  N/A
+  linux-firmware 1.157.16
+ RfKill: Error: [Errno 2] Aucun fichier ou dossier de ce type
+ Tags:  xenial
+ Uname: Linux 4.4.0-115-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 04/01/2014
+ dmi.bios.vendor: SeaBIOS
+ dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: QEMU
+ dmi.chassis.version: pc-i440fx-xenial
+ dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
+ dmi.product.name: Standard PC (i440FX + PIIX, 1996)
+ dmi.product.version: pc-i440fx-xenial
+ dmi.sys.vendor: QEMU

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1749143/+attachment/5054373/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749143

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749143] JournalErrors.txt

[EOLE team]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1749143/+attachment/5054375/+files/JournalErrors.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749143

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749143] CurrentDmesg.txt

[EOLE team]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1749143/+attachment/5054374/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749143

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749143] Re: BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad address

[EOLE team]

** Tags added: amd64

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749143

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1749143] [NEW] BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad address

[EOLE team]

Public bug reported:

Hello,

We test the -proposed packages before our ±25000 user servers get a
chance to download it when it's in stable and we have an issue since the
package linux-image-4.4.0-113-generic and linux-image-4.4.0-115-generic.

We tried on KVM virtual machines

To reproduce the problem, execute:

# fping -t50 -r2 127.0.0.1
127.0.0.1: error while sending ping: Bad address
127.0.0.1: error while sending ping: Bad address
127.0.0.1: error while sending ping: Bad address
127.0.0.1 is unreachable

We have no problem with ping:

# ping -c 1 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.046 ms

--- 127.0.0.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.046/0.046/0.046/0.000 ms

fping is working fine under kernel 4.4.0-112:

# fping -t50 -r2 127.0.0.1
127.0.0.1 is alive

Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: regression-proposed xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749143

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749143/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1617220] Re: Bad alias in ejabberd.service

[EOLE team]

Is there any plan to backport to LTS Xenial?

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617220

Title:
  Bad alias in ejabberd.service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1617220/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1712817] Re: postinst fails if the service is disabled via systemd

[EOLE team]

Ok, so it looks like the following policy-rc.d will do the job for that
particular case:

#!/bin/sh

skip_disabled() {
local service="${1}"

if [ -d /run/systemd ] && ! systemctl is-enabled "${service}" 2>&1 
/dev/null
then
exit 101
fi
}

case "${1}-${2}" in
freeradius-reload)
skip_disabled "${1}"
;;
esac

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712817

Title:
  postinst fails if the service is disabled via systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1712817/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1712817] Re: Error when update from 2.2.8+dfsg-0.1build2 to 2.2.8+dfsg-0.1ubuntu0.1

[EOLE team]

Yes, we provide an Ubuntu GNU/Linux derivatives for french national
education, the software is installed and the admin can
activate/desactivate it as wanted.

So the software is installed but can be disabled if the admin does not
want it.

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712817

Title:
  postinst fails if the service is disabled via systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1712817/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1712817] Re: Error when update from 2.2.8+dfsg-0.1build2 to 2.2.8+dfsg-0.1ubuntu0.1

[EOLE team]

Instead of adding “|| true”, it may have the possibility to check if the
service is active and running?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712817

Title:
  postinst fails if the service is disabled via systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1712817/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1712817] Re: Error when update from 2.2.8+dfsg-0.1build2 to 2.2.8+dfsg-0.1ubuntu0.1

[EOLE team]

In fact the problem is that freeradius is stoped and disabled:

  systemctl stop freeradius.service
  systemctl disable freeradius.service

So, the freeradius.postinst can not start it, then the freeradius-
ldap.postinst fail.

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712817

Title:
  Error when update from 2.2.8+dfsg-0.1build2 to 2.2.8+dfsg-0.1ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1712817/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1712817] [NEW] Error when update from 2.2.8+dfsg-0.1build2 to 2.2.8+dfsg-0.1ubuntu0.1

[EOLE team]

Public bug reported:

When updating my Xenial with freeradius installed but not active I got
the following error:

Setting up freeradius-common (2.2.8+dfsg-0.1ubuntu0.1) ...
Setting up libfreeradius2 (2.2.8+dfsg-0.1ubuntu0.1) ...
Setting up freeradius-utils (2.2.8+dfsg-0.1ubuntu0.1) ...
Setting up freeradius (2.2.8+dfsg-0.1ubuntu0.1) ...
Setting up freeradius-ldap (2.2.8+dfsg-0.1ubuntu0.1) ...
freeradius.service is not active, cannot reload.
invoke-rc.d: initscript freeradius, action "force-reload" failed.
dpkg: error processing package freeradius-ldap (--configure):
 subprocess installed post-installation script returned error exit status 1


lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04

apt-cache policy freeradius-ldap # before update
freeradius-ldap:
  Installed: 2.2.8+dfsg-0.1build2
  Candidate: 2.2.8+dfsg-0.1ubuntu0.1
  Version table:
 2.2.8+dfsg-0.1ubuntu0.1 500
500 http://fr.archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
 *** 2.2.8+dfsg-0.1build2 500
500 http://fr.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status

** Affects: freeradius (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712817

Title:
  Error when update from 2.2.8+dfsg-0.1build2 to 2.2.8+dfsg-0.1ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1712817/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1701199] ProcEnviron.txt

[EOLE team]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1701199/+attachment/4936372/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701199

Title:
  ACLs are not correctly inherited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1701199/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1701199] ProcCpuinfoMinimal.txt

[EOLE team]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1701199/+attachment/4936371/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701199

Title:
  ACLs are not correctly inherited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1701199/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1701199] Re: ACLs are not correctly inherited

[EOLE team]

apport information

** Tags added: apport-collected xenial

** Description changed:

  This bug is reported upstream and Ubuntu needs just a new package from the 
fixed version.
  http://bugs.proftpd.org/show_bug.cgi?id=4303
  
  
  The defaut ACLs of a parent directory are not correctly replicated on created
  children. Actually, the mask is not correct.
  
  user:k:rwx  #effective:r-x
  
  root@kls2:~# dpkg -l|grep proftp
  ii  proftpd-basic  1.3.5a-1ubuntu2
  amd64Versatile, virtual-hosting FTP daemon - binaries
  
  root@kls2:~# proftpd -v
  ProFTPD Version 1.3.5a
  
  root@kls2:/etc/proftpd# grep -ri acl *
  modules.conf:ModuleControlsACLs insmod,rmmod allow user root
  modules.conf:ModuleControlsACLs lsmod allow user *
  modules.conf:LoadModule mod_facl.c
  
  root@kls2:/etc/proftpd# grep modules.conf * -ri
  proftpd.conf:Include /etc/proftpd/modules.conf
  
  root@kls2:~# getfacl /home/workgroups/
  getfacl: Removing leading '/' from absolute path names
  # file: home/workgroups/
  # owner: root
  # group: root
  user::rwx
  user:k:rwx
  group::r-x
  group:vnstat:rwx
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:k:rwx
  default:group::r-x
  default:group:vnstat:rwx
  default:mask::rwx
  default:other::r-x
  
  root@kls2:~# getfacl /home/workgroups/New/
  getfacl: Removing leading '/' from absolute path names
  # file: home/workgroups/New/
  # owner: k
  # group: k
  user::rwx
  user:k:rwx  #effective:r-x
  group::r-x
  group:vnstat:rwx#effective:r-x
  mask::r-x   <= the mask has switched from "rwx" to "r-x" !?
  other::r-x
  default:user::rwx
  default:user:k:rwx
  default:group::r-x
  default:group:vnstat:rwx
  default:mask::rwx
  default:other::r-x
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.10
+ Architecture: amd64
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2017-05-22 (91 days ago)
+ InstallationMedia: EOLE 2.6.1 "Xenial Xerus" - Beta amd64 (20170522)
+ Package: proftpd-basic 1.3.5a-1build1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
+ Tags:  xenial
+ Uname: Linux 4.4.0-87-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ modified.conffile..etc.pam.d.proftpd:
+  #%PAM-1.0
+  auth sufficient /lib/security/pam_cas.so -sftp://192.168.0.26 
-f/etc/pam_cas.conf
+  auth sufficient  pam_ldap.so
+  @include login
+ mtime.conffile..etc.pam.d.proftpd: 2017-07-21T22:08:01.730215

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1701199/+attachment/4936369/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701199

Title:
  ACLs are not correctly inherited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1701199/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1701199] JournalErrors.txt

[EOLE team]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1701199/+attachment/4936370/+files/JournalErrors.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701199

Title:
  ACLs are not correctly inherited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1701199/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1701199] [NEW] ACLs are not correctly inherited

[EOLE team]

Public bug reported:

This bug is reported upstream and Ubuntu needs just a new package from the 
fixed version.
http://bugs.proftpd.org/show_bug.cgi?id=4303


The defaut ACLs of a parent directory are not correctly replicated on created
children. Actually, the mask is not correct.

user:k:rwx  #effective:r-x

root@kls2:~# dpkg -l|grep proftp
ii  proftpd-basic  1.3.5a-1ubuntu2
amd64Versatile, virtual-hosting FTP daemon - binaries

root@kls2:~# proftpd -v
ProFTPD Version 1.3.5a

root@kls2:/etc/proftpd# grep -ri acl *
modules.conf:ModuleControlsACLs insmod,rmmod allow user root
modules.conf:ModuleControlsACLs lsmod allow user *
modules.conf:LoadModule mod_facl.c

root@kls2:/etc/proftpd# grep modules.conf * -ri
proftpd.conf:Include /etc/proftpd/modules.conf

root@kls2:~# getfacl /home/workgroups/
getfacl: Removing leading '/' from absolute path names
# file: home/workgroups/
# owner: root
# group: root
user::rwx
user:k:rwx
group::r-x
group:vnstat:rwx
mask::rwx
other::r-x
default:user::rwx
default:user:k:rwx
default:group::r-x
default:group:vnstat:rwx
default:mask::rwx
default:other::r-x

root@kls2:~# getfacl /home/workgroups/New/
getfacl: Removing leading '/' from absolute path names
# file: home/workgroups/New/
# owner: k
# group: k
user::rwx
user:k:rwx  #effective:r-x
group::r-x
group:vnstat:rwx#effective:r-x
mask::r-x   <= the mask has switched from "rwx" to "r-x" !?
other::r-x
default:user::rwx
default:user:k:rwx
default:group::r-x
default:group:vnstat:rwx
default:mask::rwx
default:other::r-x

** Affects: proftpd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: acl acls

** Description changed:

+ This bug is reported upstream and Ubuntu needs just a new package from the 
fixed version.
+ http://bugs.proftpd.org/show_bug.cgi?id=4303
+ 
+ 
  The defaut ACLs of a parent directory are not correctly replicated on created
  children. Actually, the mask is not correct.
  
  user:k:rwx  #effective:r-x
  
- 
  root@kls2:~# dpkg -l|grep proftp
- ii  proftpd-basic  1.3.5a-1ubuntu2
 
- amd64Versatile, virtual-hosting FTP daemon - binaries
+ ii  proftpd-basic  1.3.5a-1ubuntu2
+ amd64Versatile, virtual-hosting FTP daemon - binaries
  
  root@kls2:~# proftpd -v
  ProFTPD Version 1.3.5a
  
  root@kls2:/etc/proftpd# grep -ri acl *
  modules.conf:ModuleControlsACLs insmod,rmmod allow user root
  modules.conf:ModuleControlsACLs lsmod allow user *
  modules.conf:LoadModule mod_facl.c
  
  root@kls2:/etc/proftpd# grep modules.conf * -ri
  proftpd.conf:Include /etc/proftpd/modules.conf
  
  root@kls2:~# getfacl /home/workgroups/
  getfacl: Removing leading '/' from absolute path names
  # file: home/workgroups/
  # owner: root
  # group: root
  user::rwx
  user:k:rwx
  group::r-x
  group:vnstat:rwx
  mask::rwx
  other::r-x
  default:user::rwx
  default:user:k:rwx
  default:group::r-x
  default:group:vnstat:rwx
  default:mask::rwx
  default:other::r-x
  
  root@kls2:~# getfacl /home/workgroups/New/
  getfacl: Removing leading '/' from absolute path names
  # file: home/workgroups/New/
  # owner: k
  # group: k
  user::rwx
  user:k:rwx  #effective:r-x
  group::r-x
  group:vnstat:rwx#effective:r-x
  mask::r-x   <= the mask has switched from "rwx" to "r-x" !?
  other::r-x
  default:user::rwx
  default:user:k:rwx
  default:group::r-x
  default:group:vnstat:rwx
  default:mask::rwx
  default:other::r-x

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701199

Title:
  ACLs are not correctly inherited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/proftpd/+bug/1701199/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1397278] Re: Fencing is not reported to DLM

[EOLE team]

We switched to Xenial servers.

We do not need this backport anymore.

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397278

Title:
  Fencing is not reported to DLM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1397278/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1474682] Re: package tftpd-hpa 5.2+20140608-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[EOLE team]

Here is our configuration:

# rgrep ipv6 /etc/sysctl.*
/etc/sysctl.conf:net.ipv6.conf.all.disable_ipv6=1
/etc/sysctl.conf:net.ipv6.conf.default.disable_ipv6=1
/etc/sysctl.conf:net.ipv6.conf.lo.disable_ipv6=1
/etc/sysctl.conf:net.ipv6.conf.all.forwarding=0
/etc/sysctl.d/10-ipv6-privacy.conf:net.ipv6.conf.all.use_tempaddr = 2
/etc/sysctl.d/10-ipv6-privacy.conf:net.ipv6.conf.default.use_tempaddr = 2

# rgrep ipv6 /etc/modprobe*
/etc/modprobe.d/blacklist-eole.conf:blacklist ipv6

The problem is fixed in Xenial with the following changelog:

tftp-hpa (5.2+20150808-1ubuntu1.16.04.1) xenial; urgency=medium

  * Replace the default value of TFTP_ADDRESS to :69 instead of [::]:69.
The previous default caused a failure to start when the NIC is not
available at startup time (LP: #1342580)

 -- Louis Bouchard   Tue, 07 Mar 2017 12:00:08 
+0100

and in Trusty with the following changelog:

tftp-hpa (5.2-7ubuntu3.1) trusty; urgency=medium

  * Replace the default value of TFTP_ADDRESS to :69 instead of [::]:69.
The previous default caused a failure to start when the NIC is not
available at startup time (LP: #1342580)

 -- Louis Bouchard   Thu, 09 Feb 2017 18:13:54 
+0100


# apt install tftpd-hpa
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Suggested packages:
  pxelinux
The following NEW packages will be installed:
  tftpd-hpa
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 39,1 kB of archives.
After this operation, 115 kB of additional disk space will be used.
Get:1 http://eole.ac-dijon.fr/ubuntu xenial-updates/main amd64 tftpd-hpa 
amd64 5.2+20150808-1ubuntu1.16.04.1 [39,1 kB]
Fetched 39,1 kB in 0s (2 799 kB/s)   
Preconfiguring packages ...
Selecting previously unselected package tftpd-hpa.
(Reading database ... 110622 files and directories currently installed.)
Preparing to unpack .../tftpd-hpa_5.2+20150808-1ubuntu1.16.04.1_amd64.deb 
...
Unpacking tftpd-hpa (5.2+20150808-1ubuntu1.16.04.1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu17) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up tftpd-hpa (5.2+20150808-1ubuntu1.16.04.1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu17) ...

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1474682

Title:
  package tftpd-hpa 5.2+20140608-3ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1474682/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1604160] Re: Unicode decode error in noninteractive frontend on t->x

[EOLE team]

We have a hundred trusty servers with the same configuration and need to 
upgrade them without question.
The "do-release-upgrade -m server -f DistUpgradeViewNonInteractive" always ends 
with the traceback written in the Bug Description.
Is there a workaround for this bug or an another way to upgrade without 
question ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604160

Title:
  Unicode decode error in noninteractive frontend on t->x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1604160/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1629241] Re: crash strongSwan in Ubuntu Trusty

[EOLE team]

Hello,

Yesterday, I have installed the trusty-proposed packages on the test server and 
the production server.
There is no problem with them.

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629241

Title:
  crash strongSwan in Ubuntu Trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1629241/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1629241] Re: crash strongSwan in Ubuntu Trusty

[EOLE team]

Hello,

I have installed the new built package on a test server and a production server 
friday.
No crash happened with it.

Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629241

Title:
  crash strongSwan in Ubuntu Trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1629241/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1629256] Re: proftpd-mod-clamav doesn't work in Ubuntu Xenial

[EOLE team]

** Description changed:

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  
  $ apt-cache policy proftpd-mod-clamav
  proftpd-mod-clamav:
-   Installé : 0.10-1build5
-   Candidat : 0.10-1build5
-  Table de version :
-  *** 0.10-1build5 500
- 500 http://eole.ac-dijon.fr/ubuntu xenial/universe amd64 Packages
- 100 /var/lib/dpkg/status
+   Installé : 0.10-1build5
+   Candidat : 0.10-1build5
+  Table de version :
+  *** 0.10-1build5 500
+ 500 http://eole.ac-dijon.fr/ubuntu xenial/universe amd64 Packages
+ 100 /var/lib/dpkg/status
  
  The proftpd-mod-clamav version provided in Ubuntu 16.04 doesn't work.
  It reports "error: Can not stat file (9): Bad file descriptor" on a new file 
coming to ftp folder.
  
  This bug[1] is already reported in Debian bugtracker.
  It seems to be fixed upstream[2].
  
  We have build a new package to test the last release (0.14rc2), and it
  works.
  
- It would be great if you provides a this package with a working version.
+ It would be great if you provide this package with a working version.
  
  Regards,
  EOLE Team.
  
  [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755992
  [2] 
https://github.com/jbenden/mod_clamav/commit/ee6e8e20421e4eb1e521d1afca9e361640f6f9e3

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629256

Title:
  proftpd-mod-clamav doesn't work in Ubuntu Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/proftpd/+bug/1629256/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1629256] [NEW] proftpd-mod-clamav doesn't work in Ubuntu Xenial

[EOLE team]

Public bug reported:

$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

$ apt-cache policy proftpd-mod-clamav
proftpd-mod-clamav:
  Installé : 0.10-1build5
  Candidat : 0.10-1build5
 Table de version :
 *** 0.10-1build5 500
500 http://eole.ac-dijon.fr/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status

The proftpd-mod-clamav version provided in Ubuntu 16.04 doesn't work.
It reports "error: Can not stat file (9): Bad file descriptor" on a new file 
coming to ftp folder.

This bug[1] is already reported in Debian bugtracker.
It seems to be fixed upstream[2].

We have build a new package to test the last release (0.14rc2), and it
works.

It would be great if you provides a this package with a working version.

Regards,
EOLE Team.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755992
[2] 
https://github.com/jbenden/mod_clamav/commit/ee6e8e20421e4eb1e521d1afca9e361640f6f9e3

** Affects: proftpd (Ubuntu)
 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/1629256

Title:
  proftpd-mod-clamav doesn't work in Ubuntu Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/proftpd/+bug/1629256/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1629241] [NEW] crash strongSwan in Ubuntu Trusty

[EOLE team]

Public bug reported:

$ lsb_release -rd
Description:   Ubuntu 14.04.5 LTS
Release:14.04

$ apt-cache policy strongswan
strongswan:
  Installé : 5.1.2-0ubuntu2.4
  Candidat : 5.1.2-0ubuntu2.4
 Table de version :
 *** 5.1.2-0ubuntu2.4 0
500 http://eole.ac-dijon.fr/ubuntu/ trusty-security/main amd64 Packages
500 http://eole.ac-dijon.fr/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
 5.1.2-0ubuntu2 0
500 http://eole.ac-dijon.fr/ubuntu/ trusty/main amd64 Packages

We have several production servers running with the same configuration. 
When the plugin revocation is loaded, the daemon crashes in most every IKE_SA 
reauthentication (not each time).

You can see in this thread[1] what Tobias Brunner answers about our problem.
   
So, we have recompile the source package version including the joined patch 
(quilt), and all is OK now.

We would be grateful if you provide a new package including this patch.

Regards,
EOLE Team

[1] https://lists.strongswan.org/pipermail/users/2016-September/009991.html
[2] https://git.strongswan.org/?p=strongswan.git;a=commitdiff;h=8ca9a67f

** Affects: strongswan (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "fix-several-auth-crash"
   
https://bugs.launchpad.net/bugs/1629241/+attachment/4751596/+files/fix-several-auth-crash

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629241

Title:
  crash strongSwan in Ubuntu Trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1629241/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1625544] [NEW] Add preseed to disable signed grub and shim installation

[EOLE team]

Public bug reported:

Hello,

To work around
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1625200 we would
like to disable the installation of grub-efi-amd64-signed and shim-
signed.

The signed grub is installed as soon as we are on EFI 64bits (I did not
find the sources for Xenial but here is something similar for Wily
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/grub-installer
/wily-proposed/view/head:/grub-installer#L443)

I think a preseed could be added to disable the automatic selection of
the signed version.

Regards.

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625544

Title:
  Add preseed to disable signed grub and shim installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1625544/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1625200] Re: Permit to define bootloader_id in grub configuration

[EOLE team]

Another way could be to setup a EFI/ubuntu/grub.cfg to set the real
prefix to EFI/$(GRUB_DISTRIBUTOR).

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625200

Title:
  Permit to define bootloader_id in grub configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1625200/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1625200] [NEW] Permit to define bootloader_id in grub configuration

[EOLE team]

Public bug reported:

Hello,

For a derivative we want to set GRUB_DISTRIBUTOR, unfortunately, when
building -alternate images, shim-signed and grub-efi-amd64-signed are
installed by default.

I think a proper fix for #1242417 could be to set bootloader_id from a
new variable like GRUB_EFI_DISTRIBUTOR.

This way we could define GRUB_DISTRIBUTOR='FOO' and
GRUB_EFI_DISTRIBUTOR='ubuntu'.

Regards.

** Affects: grub2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625200

Title:
  Permit to define bootloader_id in grub configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1625200/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1595105] Re: bareos-director segfault when using mysql

[EOLE team]

To rebuild the package we need to regenerate the configure script
after patching db.m4, but here it fails with the message:

configure.in:372: the top level
autoreconf: configure.in: AM_GNU_GETTEXT is used, but not AM_GNU_GETTEXT_VERSION
autoreconf: cannot create ${BUILD_DIR}/autoconf: No such file or directory
libtoolize:   error: cannot expand unknown variable in AC_CONFIG_AUX_DIR 
argument.
autoreconf: libtoolize failed with exit status: 1
dh_autoreconf: autoreconf -f -i autoconf returned exit code 1

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595105

Title:
  bareos-director segfault when using mysql

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bareos/+bug/1595105/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1595105] Re: bareos-director segfault when using mysql

[EOLE team]

This is not sufficient, now the service starts but I have the following
error:

Unable to load any shared library for libbareoscats-mysql.so
BAREOS interrupted by signal 11: Segmentation violation
Kaboom! bareos-dir, bareos-dir got signal 11 - Segmentation violation. 
Attempting traceback.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595105

Title:
  bareos-director segfault when using mysql

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bareos/+bug/1595105/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1595105] Re: bareos-director segfault when using mysql

[EOLE team]

Here is a patch against the 14.2.6 package to fix this issue.

** Patch added: "Allow-libmysqlclient-instead-of-libmysqlclient_r.patch"
   
https://bugs.launchpad.net/ubuntu/+source/bareos/+bug/1595105/+attachment/4736011/+files/Allow-libmysqlclient-instead-of-libmysqlclient_r.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595105

Title:
  bareos-director segfault when using mysql

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bareos/+bug/1595105/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1617220] [NEW] Bad alias in ejabberd.service

[EOLE team]

Public bug reported:

Hello,

Making an alias on itself result in the following error during
successive enable.

systemctl enable ejabberd
Synchronizing state of ejabberd.service with SysV init with 
/lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable ejabberd
Failed to execute operation: Too many levels of symbolic links

The “Alias=ejabberd.service” is bogus since it point to itself.

I attach a fixed debian/patches/ejabberd.service.template.patch.

Regards.

Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial

** Affects: ejabberd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial

** Attachment added: "Fixed ejabberd.service.template.patch"
   
https://bugs.launchpad.net/bugs/1617220/+attachment/4728243/+files/ejabberd.service.template.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1617220

Title:
  Bad alias in ejabberd.service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1617220/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1614529] [NEW] Unable to start LVM agent due to a syntax error

[EOLE team]

Public bug reported:

Hello,

I try to configure an ocf:heartbeat:LVM ressource but I got an “invalid
parameter” error message and an exit status “2”.

Adding ”set -x” to the RA, I found the following log:

Aug 18 15:11:22 [11355] nebula4   lrmd:   notice: operation_finished:   
p_vg-one_start_0:14672:stderr [ + options=-aly --monitor y ]
Aug 18 15:11:22 [11355] nebula4   lrmd:   notice: operation_finished:   
p_vg-one_start_0:14672:stderr [ + echo -aly --monitor y ]
Aug 18 15:11:22 [11355] nebula4   lrmd:   notice: operation_finished:   
p_vg-one_start_0:14672:stderr [ + local vgchange_options=-aly --monitor y ]
Aug 18 15:11:22 [11355] nebula4   lrmd:   notice: operation_finished:   
p_vg-one_start_0:14672:stderr [ /usr/lib/ocf/resource.d/heartbeat/LVM: 416: 
local: --monitor: bad variable name ]
Aug 18 15:11:22 [11355] nebula4   lrmd:debug: operation_finished:   
p_vg-one_start_0:14672:stdout [ -- empty -- ]
Aug 18 15:11:22 [11358] nebula4   crmd:   notice: process_lrm_event:
Operation p_vg-one_start_0: invalid parameter (node=nebula4, call=155, rc=2, 
cib-update=241, confirmed=true)

Regards.

Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial

** Affects: resource-agents (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial

** Patch added: "LVM.patch"
   https://bugs.launchpad.net/bugs/1614529/+attachment/4723411/+files/LVM.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614529

Title:
  Unable to start LVM agent due to a syntax error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1614529/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600240] [NEW] plymouth does not switch to tty1 on Xenial server

[EOLE team]

Public bug reported:

Hello,

On a Xenial server, I installed plymouth and plymouth-theme-ubuntu-logo.

When the server boots:

* the logo is displayed correctly
* after some time, the logo disappear and display some text

  lvmetad is not active yet, using direct activation during sysinit
  lvmetad is not active yet, using direct activation during sysinit
/: clean, 28973/187680 files, 199081/749568 blocks

I need to manually switch to tty1 with Alt-F1 to get the login prompt,
on Trusty the switch is automatic.

I tried every console to found the text displayed above, it is
displayed on tty7.

Regards.

Distributor ID: Ubuntu
Description:Ubuntu 16.04 LTS
Release:16.04
Codename:   xenial

LANG=C apt policy plymouth
plymouth:
  Installed: 0.9.2-3ubuntu13.1
  Candidate: 0.9.2-3ubuntu13.1
  Version table:
 *** 0.9.2-3ubuntu13.1 500
500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 0.9.2-3ubuntu13 500
500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

** Affects: plymouth (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600240

Title:
  plymouth does not switch to tty1 on Xenial server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1600240/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600164] [NEW] Mysql server take 10 minutes to stop without message after time drift

[EOLE team]

Public bug reported:

Hello,

I figure out an issue and it took time to understand what happened:

* hardware clock is 2 hours in future
* during system boot: mysql start at the same time than ntp
* ntp fix clock which does a drift of 2 hours in past

Now, stopping mysql with “service mysql stop”:

* take 10 minutes
* provides no no information of what's happening to the user
* process is killed by the way (no clean stop)

To solve this issue, mysql should be started after ntp.

Distributor ID: Ubuntu
Description:Ubuntu 16.04 LTS
Release:16.04
Codename:   xenial

Here are the logs:

root@xenial:~# LANG=C journalctl -u mysql.service
-- Logs begin at Fri 2016-07-08 14:33:07 CEST, end at Fri 2016-07-08 11:46:00 
CEST. --
Jul 08 14:34:11 xenial systemd[1]: Starting MySQL Community Server...
Jul 08 14:34:12 xenial systemd[1]: Started MySQL Community Server.
Jul 08 11:36:00 xenial systemd[1]: Stopping MySQL Community Server...
Jul 08 11:46:00 xenial systemd[1]: mysql.service: State 'stop-sigterm' timed 
out. Killing.
Jul 08 11:46:00 xenial systemd[1]: mysql.service: Main process exited, 
code=killed, status=9/KILL
Jul 08 11:46:00 xenial systemd[1]: Stopped MySQL Community Server.
Jul 08 11:46:00 xenial systemd[1]: mysql.service: Unit entered failed state.
Jul 08 11:46:00 xenial systemd[1]: mysql.service: Failed with result 'signal'.


root@xenial:~# cat /var/log/mysql/error.log 
2016-07-08T09:36:00.656993Z 0 [Note] Giving 0 client threads a chance to die 
gracefully
2016-07-08T09:36:00.657033Z 0 [Note] Shutting down slave threads
2016-07-08T09:36:00.657041Z 0 [Note] Forcefully disconnecting 0 remaining 
clients
2016-07-08T09:36:00.657049Z 0 [Note] Event Scheduler: Purging the queue. 0 
events
2016-07-08T09:36:00.657164Z 0 [Note] Binlog end
2016-07-08T09:36:00.657596Z 0 [Note] Shutting down plugin 'ngram'
2016-07-08T09:36:00.657609Z 0 [Note] Shutting down plugin 'ARCHIVE'
2016-07-08T09:36:00.657614Z 0 [Note] Shutting down plugin 'partition'
2016-07-08T09:36:00.657618Z 0 [Note] Shutting down plugin 'BLACKHOLE'
2016-07-08T09:36:00.657623Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'
2016-07-08T09:36:00.657628Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2016-07-08T09:36:00.657631Z 0 [Note] Shutting down plugin 
'INNODB_SYS_TABLESPACES'
2016-07-08T09:36:00.657635Z 0 [Note] Shutting down plugin 
'INNODB_SYS_FOREIGN_COLS'
2016-07-08T09:36:00.657639Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2016-07-08T09:36:00.657643Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2016-07-08T09:36:00.657646Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2016-07-08T09:36:00.657650Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2016-07-08T09:36:00.657653Z 0 [Note] Shutting down plugin 
'INNODB_SYS_TABLESTATS'
2016-07-08T09:36:00.657657Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2016-07-08T09:36:00.657660Z 0 [Note] Shutting down plugin 
'INNODB_FT_INDEX_TABLE'
2016-07-08T09:36:00.657664Z 0 [Note] Shutting down plugin 
'INNODB_FT_INDEX_CACHE'
2016-07-08T09:36:00.657667Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2016-07-08T09:36:00.657671Z 0 [Note] Shutting down plugin 
'INNODB_FT_BEING_DELETED'
2016-07-08T09:36:00.657674Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED'
2016-07-08T09:36:00.657677Z 0 [Note] Shutting down plugin 
'INNODB_FT_DEFAULT_STOPWORD'
2016-07-08T09:36:00.657681Z 0 [Note] Shutting down plugin 'INNODB_METRICS'
2016-07-08T09:36:00.657684Z 0 [Note] Shutting down plugin 
'INNODB_TEMP_TABLE_INFO'
2016-07-08T09:36:00.657702Z 0 [Note] Shutting down plugin 
'INNODB_BUFFER_POOL_STATS'
2016-07-08T09:36:00.657706Z 0 [Note] Shutting down plugin 
'INNODB_BUFFER_PAGE_LRU'
2016-07-08T09:36:00.657709Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
2016-07-08T09:36:00.657713Z 0 [Note] Shutting down plugin 
'INNODB_CMP_PER_INDEX_RESET'
2016-07-08T09:36:00.657717Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
2016-07-08T09:36:00.657720Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
2016-07-08T09:36:00.657724Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM'
2016-07-08T09:36:00.657728Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET'
2016-07-08T09:36:00.657731Z 0 [Note] Shutting down plugin 'INNODB_CMP'
2016-07-08T09:36:00.657735Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
2016-07-08T09:36:00.657739Z 0 [Note] Shutting down plugin 'INNODB_LOCKS'
2016-07-08T09:36:00.657742Z 0 [Note] Shutting down plugin 'INNODB_TRX'
2016-07-08T09:36:00.657746Z 0 [Note] Shutting down plugin 'InnoDB'
2016-07-08T09:36:00.657901Z 0 [Note] InnoDB: FTS optimize thread exiting.
2016-07-08T09:36:00.657993Z 0 [Note] InnoDB: Starting shutdown...
2016-07-08T09:36:00.758259Z 0 [Note] InnoDB: Dumping buffer pool(s) to 
/var/lib/mysql/ib_buffer_pool
2016-07-08T09:36:00.758430Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 
160708 11:36:00
2016-07-08T09:37:01.641619Z 0 [Note] InnoDB: Waiting for page_cleaner to finish 
flushing of buffer pool
2016-07-08T09:38:01.820902Z 0 

[Bug 1595105] [NEW] bareos-director segfault when using mysql

[EOLE team]

Public bug reported:

This bug is a bareos bug and bareos dev team is aware of it :
https://groups.google.com/forum/#!topic/bareos-users/7_bTpp1DKCk

The problem is that libmysqlclient_r has been renamed to libmysqlclient.

 bareos-dir JobId 0: Error: Unable to load shared library: 
/usr/lib/bareos/backends/libbareoscats-mysql.so ERR=
 bareos-dir ABORTING due to ERROR#012Unable to load any shared library for 
libbareoscats-mysql.so
 bareos-dir ABORTING due to ERROR
 Unable to load any shared library for libbareoscats-mysql.so
 BAREOS forced SEG FAULT to obtain traceback.
 BAREOS interrupted by signal 11: Segmentation violation

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bareos 14.2.6-3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Jun 22 11:26:48 2016
InstallationDate: Installed on 2016-05-26 (27 days ago)
InstallationMedia: EOLE 2.6-unstable "Xenial Xerus" - Release amd64 (20160513)
SourcePackage: bareos
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: bareos (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Description changed:

+ This bug is a bareos bug and bareos dev team is aware of it :
+ https://groups.google.com/forum/#!topic/bareos-users/7_bTpp1DKCk
+ 
+ The problem is that libmysqlclient_r has been renamed to libmysqlclient.
+ 
   bareos-dir JobId 0: Error: Unable to load shared library: 
/usr/lib/bareos/backends/libbareoscats-mysql.so ERR=
-  bareos-dir ABORTING due to ERROR#012Unable to load any shared library for 
libbareoscats-mysql.so
-  bareos-dir ABORTING due to ERROR
-  Unable to load any shared library for libbareoscats-mysql.so
-  BAREOS forced SEG FAULT to obtain traceback.
-  BAREOS interrupted by signal 11: Segmentation violation
+  bareos-dir ABORTING due to ERROR#012Unable to load any shared library for 
libbareoscats-mysql.so
+  bareos-dir ABORTING due to ERROR
+  Unable to load any shared library for libbareoscats-mysql.so
+  BAREOS forced SEG FAULT to obtain traceback.
+  BAREOS interrupted by signal 11: Segmentation violation
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bareos 14.2.6-3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 22 11:26:48 2016
  InstallationDate: Installed on 2016-05-26 (27 days ago)
  InstallationMedia: EOLE 2.6-unstable "Xenial Xerus" - Release amd64 (20160513)
  SourcePackage: bareos
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595105

Title:
  bareos-director segfault when using mysql

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bareos/+bug/1595105/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1474682] Re: package tftpd-hpa 5.2+20140608-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[EOLE team]

The problem is still present on Xenial with tftpd-hpa
5.2+20150808-1ubuntu1 version.

** Attachment added: "tftpd-hpa package installation failure on Ubuntu Xenial"
   
https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1474682/+attachment/4675179/+files/dpkg-xenial.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1474682

Title:
  package tftpd-hpa 5.2+20140608-3ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1474682/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1474682] Re: package tftpd-hpa 5.2+20140608-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[EOLE team]

** Tags added: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1474682

Title:
  package tftpd-hpa 5.2+20140608-3ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1474682/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1579653] [NEW] Too many dependencies when installing postgresql-9.5-postgis-2.2

[EOLE team]

Public bug reported:

Hello,

When installing postgresql-9.5-postgis-2.2 (2.2.1+dfsg-2) on a Xenial I
see many graphical packages.

I looked on Debian Sid and there are not in the dependency list.

APT is configured to not installed Recommends packages on both Xenial
and Sid.

I don't see where is the difference.

Regards.

Description:Ubuntu 16.04 LTS
Release:16.04

** Affects: postgis (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial

** Attachment added: "Difference of dependencies between Xenial and Sid"
   
https://bugs.launchpad.net/bugs/1579653/+attachment/4659017/+files/dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579653

Title:
  Too many dependencies when installing postgresql-9.5-postgis-2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgis/+bug/1579653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572122] Re: Samba upgrade to 3.6.25-0ubuntu0.12.04.2 break domain authentication

[EOLE team]

I just make the test and the windows-7 workstation can login with the
new 2:3.6.25-0ubuntu0.12.04.3 samba package.

For the record, I made a test with and without the microsoft patch
https://www.microsoft.com/en-us/download/confirmation.aspx?id=51829.

Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572122

Title:
  Samba upgrade to 3.6.25-0ubuntu0.12.04.2 break domain authentication

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1572122/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576618] Re: Unable to install sympa with dbconfig-no-thanks

[EOLE team]

The upgrade of the database should be protected too:

https://anonscm.debian.org/cgit/collab-
maint/sympa.git/tree/debian/sympa.postinst#n398

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576618

Title:
  Unable to install sympa with dbconfig-no-thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sympa/+bug/1576618/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576618] Re: Unable to install sympa with dbconfig-no-thanks

[EOLE team]

As reported on dbconfig-common mailing list[1], the code in postinst
should be protected by a test.


[1] 
https://lists.alioth.debian.org/pipermail/dbconfig-common-devel/2016-April/000831.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576618

Title:
  Unable to install sympa with dbconfig-no-thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sympa/+bug/1576618/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576618] [NEW] Unable to install sympa with dbconfig-no-thanks

[EOLE team]

Public bug reported:

Hello,

I'm trying to install sympa automatically, without database management
(done later by another tool), so I installed dbconfig-no-thanks before
installing sympa and it fails with the following error :

Adding system user: sympa.
/etc/sympa/sympa.conf file has been created
/etc/sympa/wwsympa.conf file has been created
Unknown database type .
dpkg: erreur de traitement du paquet sympa (--configure) :
 le sous-processus script post-installation installé a retourné une erreur 
de sortie d'état 1

I think the sympa postinst should take care of this case, as describe in
dbconfig-common documentation.

Regards.

lsb_release -a
Distributor ID: Ubuntu
Description:Ubuntu 16.04 LTS
Release:16.04
Codename:   xenial

** Affects: sympa (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576618

Title:
  Unable to install sympa with dbconfig-no-thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sympa/+bug/1576618/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572122] Re: Samba upgrade to 3.6.25-0ubuntu0.12.04.2 break domain authentication

[EOLE team]

It looks like a regression fix is available upstream
https://git.samba.org/?p=asn/samba.git;a=commit;h=82fa625540abf8b8ec23d43c41e2ca906a9928a5

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572122

Title:
  Samba upgrade to 3.6.25-0ubuntu0.12.04.2 break domain authentication

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1572122/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572122] Re: Samba upgrade break LDAP authentification only for my w7 clients

[EOLE team]

Finally we have the solution:

The windows machines must be up-to-date, with the samba up-to-date,
without the configuration

allow dcerpc auth level connect = yes

If the windows machine is not up-to-date, the configuration "allow
dcerpc auth level connect = yes" does not permit to connect.

If the windows machine is up-to-date, the configuration "allow dcerpc
auth level connect = yes" block the connection.

Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572122

Title:
  Samba upgrade break LDAP authentification only  for my w7 clients

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1572122/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1572122] Re: Samba upgrade break LDAP authentification only for my w7 clients

[EOLE team]

If it can help, we do not have the issue with package 2:4.3.8+dfsg-
0ubuntu0.14.04.2 from Trusty.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572122

Title:
  Samba upgrade break LDAP authentification only  for my w7 clients

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1572122/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs