[Touch-packages] [Bug 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines
All regressions now cleared after a re-run (thanks!), and verifications done. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1311056 Title: [SRU] apt-add-repository adds duplicate commented/disabled source lines Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Committed Status in python-apt source package in Eoan: Fix Committed Bug description: Impact == Under most circumstances, the impact is minimal (a few extra redundant comment lines in apt sources. However, if users are automating source removal / addition on a machine (as in comment 11), there is the potential to wind up with an excessively large (and thus slow to parse) apt sources configuration. Test packages for the supported releases are available from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/python-apt Built from the source which can be found in the following branches: https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-xenial https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-bionic https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-eoan Test Case = * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the presence of one uncommented "deb" line, and one commented "deb-src" line * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated * sudo add-apt-repository ppa:waveform/python-apt * sudo apt upgrade # update python-apt to fixed version * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note there has been no further duplication of the commented "deb-src" line Regression Potential Minimal; test cases have been added to cover the duplication case, and to cover the enabling of sources (which was not covered by existing tests, but was part of the code altered to fix the duplication case), and insertion of sources at a position (again, not covered by existing tests but modified as part of the fix). The test case has been used successfully on all targeted releases (xenial, bionic, and eoan). Original Description Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1311056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines
Successfully verified fixes on xenial, bionic, and eoan. The autopkgtest regressions on xenial were due to flaky tests on i386 and armhf; these have been re-run successfully. The regressions on bionic look like a transient network failure (would be grateful if someone could attempt a re-run on those). The same is true of one of the regressions on eoan; the other *may* be (would be grateful if someone could attempt a re-run of those too). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1311056 Title: [SRU] apt-add-repository adds duplicate commented/disabled source lines Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Committed Status in python-apt source package in Eoan: Fix Committed Bug description: Impact == Under most circumstances, the impact is minimal (a few extra redundant comment lines in apt sources. However, if users are automating source removal / addition on a machine (as in comment 11), there is the potential to wind up with an excessively large (and thus slow to parse) apt sources configuration. Test packages for the supported releases are available from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/python-apt Built from the source which can be found in the following branches: https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-xenial https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-bionic https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-eoan Test Case = * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the presence of one uncommented "deb" line, and one commented "deb-src" line * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated * sudo add-apt-repository ppa:waveform/python-apt * sudo apt upgrade # update python-apt to fixed version * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note there has been no further duplication of the commented "deb-src" line Regression Potential Minimal; test cases have been added to cover the duplication case, and to cover the enabling of sources (which was not covered by existing tests, but was part of the code altered to fix the duplication case), and insertion of sources at a position (again, not covered by existing tests but modified as part of the fix). The test case has been used successfully on all targeted releases (xenial, bionic, and eoan). Original Description Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1311056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1311056 Title: [SRU] apt-add-repository adds duplicate commented/disabled source lines Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Committed Status in python-apt source package in Eoan: Fix Committed Bug description: Impact == Under most circumstances, the impact is minimal (a few extra redundant comment lines in apt sources. However, if users are automating source removal / addition on a machine (as in comment 11), there is the potential to wind up with an excessively large (and thus slow to parse) apt sources configuration. Test packages for the supported releases are available from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/python-apt Built from the source which can be found in the following branches: https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-xenial https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-bionic https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-eoan Test Case = * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the presence of one uncommented "deb" line, and one commented "deb-src" line * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated * sudo add-apt-repository ppa:waveform/python-apt * sudo apt upgrade # update python-apt to fixed version * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note there has been no further duplication of the commented "deb-src" line Regression Potential Minimal; test cases have been added to cover the duplication case, and to cover the enabling of sources (which was not covered by existing tests, but was part of the code altered to fix the duplication case), and insertion of sources at a position (again, not covered by existing tests but modified as part of the fix). The test case has been used successfully on all targeted releases (xenial, bionic, and eoan). Original Description Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1311056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1311056 Title: [SRU] apt-add-repository adds duplicate commented/disabled source lines Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Committed Status in python-apt source package in Eoan: Fix Committed Bug description: Impact == Under most circumstances, the impact is minimal (a few extra redundant comment lines in apt sources. However, if users are automating source removal / addition on a machine (as in comment 11), there is the potential to wind up with an excessively large (and thus slow to parse) apt sources configuration. Test packages for the supported releases are available from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/python-apt Built from the source which can be found in the following branches: https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-xenial https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-bionic https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-eoan Test Case = * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the presence of one uncommented "deb" line, and one commented "deb-src" line * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated * sudo add-apt-repository ppa:waveform/python-apt * sudo apt upgrade # update python-apt to fixed version * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note there has been no further duplication of the commented "deb-src" line Regression Potential Minimal; test cases have been added to cover the duplication case, and to cover the enabling of sources (which was not covered by existing tests, but was part of the code altered to fix the duplication case), and insertion of sources at a position (again, not covered by existing tests but modified as part of the fix). The test case has been used successfully on all targeted releases (xenial, bionic, and eoan). Original Description Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1311056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870410] Re: wireless does not work on boot on RPi 3s
Confirmed test build in the PPA in comment 13 (245.4-4ubuntu3) fixes the issue on both archs (armhf and arm64) on the Pi 3B, 3A+, and 3B+ (re- tested 4B as well to ensure nothing broken, and it's still working). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1870410 Title: wireless does not work on boot on RPi 3s Status in systemd package in Ubuntu: In Progress Status in systemd source package in Focal: In Progress Bug description: I've setup a wireless config in /etc/netplan/config.yaml and it does not activate on boot. I have to run 'sudo netplan apply' to get my wireless connected. This works fine on an RPi4 but not an RPi3B. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.2-1ubuntu2 ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24 Uname: Linux 5.4.0-1006-raspi2 armv7l ApportVersion: 2.20.11-0ubuntu21 Architecture: armhf Date: Thu Apr 2 19:02:27 2020 Lspci: Lsusb: Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870410] Re: wireless does not work on boot on RPi 3s
I can confirm the behaviour Brian's seeing on the Pi 3B on armhf and arm64 with systemd 245.4-2 from the PPA Balint mentioned (and the same error message which appears to be from a chunk of code slightly beyond where we were last time - so we're moving forward at least :). As before, wifi is working fine on the Pi 4B under armhf and arm64. Interestingly however, the Pi 3B+ (which shares the wifi chip with the 4B but is only slighter faster than the 3B) now has working wifi under armhf, but not arm64 (same error as the 3B on arm64). I was slightly surprised at this, so I double checked it with a couple of reboots - same results each time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1870410 Title: wireless does not work on boot on RPi 3s Status in systemd package in Ubuntu: In Progress Status in systemd source package in Focal: In Progress Bug description: I've setup a wireless config in /etc/netplan/config.yaml and it does not activate on boot. I have to run 'sudo netplan apply' to get my wireless connected. This works fine on an RPi4 but not an RPi3B. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.2-1ubuntu2 ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24 Uname: Linux 5.4.0-1006-raspi2 armv7l ApportVersion: 2.20.11-0ubuntu21 Architecture: armhf Date: Thu Apr 2 19:02:27 2020 Lspci: Lsusb: Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1870410] Re: wireless does not work on boot
Also tested under armhf and arm64 on Raspberry Pi models 3B, 3A+, and
3B+. Results are the same as for bdmurray's tests with armhf on the 3B
above.
My initial suspicion was that this was related to the wifi chipset used
on the 3B (the BCM43430) to the 4B (the BCM43455). However, given the
3A+ and 3B+ also use the BCM43455 (same as the 4B) it's definitely not
that.
Given that the only error ("DHCP4 CLIENT: Failed to attach event...")
occurred in systemd-networkd I attempted to downgrade from version 245.2
to 244.3 (the prior release on Ubuntu). This fixes the issue on the 3B
and 3A+ under armhf and arm64 (I skipped checking the 3B+ for time at
this point).
At this point I'm reasonably confident it's an issue in systemd
introduced sometime between 244.3 and 245.2 - and that it may be timing
sensitive given that the 4B (which is significantly faster than the 3,
3A+ or 3B+) doesn't show the same symptoms but shares a wifi chipset
with the 3A+ and 3B+.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1870410
Title:
wireless does not work on boot
Status in systemd package in Ubuntu:
New
Bug description:
I've setup a wireless config in /etc/netplan/config.yaml and it does
not activate on boot. I have to run 'sudo netplan apply' to get my
wireless connected. This works fine on an RPi4 but not an RPi3B.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.2-1ubuntu2
ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24
Uname: Linux 5.4.0-1006-raspi2 armv7l
ApportVersion: 2.20.11-0ubuntu21
Architecture: armhf
Date: Thu Apr 2 19:02:27 2020
Lspci:
Lsusb:
Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC)
SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC)
SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
|__ Port 1: Dev 7, If 0, Class=Vendor Specific Class,
Driver=smsc95xx, 480M
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870410/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines
** Changed in: python-apt (Ubuntu Eoan) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: python-apt (Ubuntu Xenial) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: python-apt (Ubuntu Bionic) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1311056 Title: [SRU] apt-add-repository adds duplicate commented/disabled source lines Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: New Status in python-apt source package in Bionic: New Status in python-apt source package in Eoan: New Bug description: Impact == Under most circumstances, the impact is minimal (a few extra redundant comment lines in apt sources. However, if users are automating source removal / addition on a machine (as in comment 11), there is the potential to wind up with an excessively large (and thus slow to parse) apt sources configuration. Test packages for the supported releases are available from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/python-apt Built from the source which can be found in the following branches: https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-xenial https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-bionic https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-eoan Test Case = * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the presence of one uncommented "deb" line, and one commented "deb-src" line * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated * sudo add-apt-repository ppa:waveform/python-apt * sudo apt upgrade # update python-apt to fixed version * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note there has been no further duplication of the commented "deb-src" line Regression Potential Minimal; test cases have been added to cover the duplication case, and to cover the enabling of sources (which was not covered by existing tests, but was part of the code altered to fix the duplication case), and insertion of sources at a position (again, not covered by existing tests but modified as part of the fix). The test case has been used successfully on all targeted releases (xenial, bionic, and eoan). Original Description Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1311056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines
** Description changed: Impact == Under most circumstances, the impact is minimal (a few extra redundant comment lines in apt sources. However, if users are automating source removal / addition on a machine (as in comment 11), there is the potential to wind up with an excessively large (and thus slow to parse) apt sources configuration. + + Test packages for the supported releases are available from the + following PPA: + + https://launchpad.net/~waveform/+archive/ubuntu/python-apt + + Built from the source which can be found in the following branches: + + https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git + /python-apt/+ref/sru-dupe-ppa-xenial + + https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git + /python-apt/+ref/sru-dupe-ppa-bionic + + https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git + /python-apt/+ref/sru-dupe-ppa-eoan Test Case = * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the presence of one uncommented "deb" line, and one commented "deb-src" line * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated * sudo add-apt-repository ppa:waveform/python-apt * sudo apt upgrade # update python-apt to fixed version * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note there has been no further duplication of the commented "deb-src" line Regression Potential Minimal; test cases have been added to cover the duplication case, and to cover the enabling of sources (which was not covered by existing tests, but was part of the code altered to fix the duplication case), and insertion of sources at a position (again, not covered by existing tests but modified as part of the fix). The test case has been used successfully on all targeted releases (xenial, bionic, and eoan). Original Description Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1311056 Title: [SRU] apt-add-repository adds duplicate commented/disabled source lines Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: New Status in python-apt source package in Bionic: New Status in python-apt source package in Eoan: New Bug description: Impact == Under most circumstances, the impact is minimal (a few extra redundant comment lines in apt sources. However, if users are automating source removal / addition on a machine (as in comment 11), there is the potential to wind up with an excessively large (and thus slow to parse) apt sources configuration. Test packages for the supported releases are available from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/python-apt Built from the source which can be found in the following branches: https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-xenial https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-bionic https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-eoan Test Case = * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the presence of one uncommented "deb" line, and one commented
[Touch-packages] [Bug 1311056] Re: apt-add-repository adds duplicate commented/disabled source lines
** Description changed: + Impact + == + + Under most circumstances, the impact is minimal (a few extra redundant + comment lines in apt sources. However, if users are automating source + removal / addition on a machine (as in comment 11), there is the + potential to wind up with an excessively large (and thus slow to parse) + apt sources configuration. + + Test Case + = + + * sudo add-apt-repository -y ppa:deadsnakes/ppa + * cat /etc/apt/sources.list.d/deadsnakes*.list + * Note the presence of one uncommented "deb" line, and one commented "deb-src" line + * sudo add-apt-repository -y ppa:deadsnakes/ppa + * cat /etc/apt/sources.list.d/deadsnakes*.list + * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated + * Upgrade python-apt to 1.9.3ubuntu2 (or later) + * sudo add-apt-repository -y ppa:deadsnakes/ppa + * cat /etc/apt/sources.list.d/deadsnakes*.list + * Note there has been no further duplication of the commented "deb-src" line + + Regression Potential + + + Minimal; test cases have been added to cover the duplication case, and + to cover the enabling of sources (which was not covered by existing + tests, but was part of the code altered to fix the duplication case), + and insertion of sources at a position (again, not covered by existing + tests but modified as part of the fix). The test case has been used + successfully on all targeted releases (xenial, bionic, and eoan). + + Original Description + + Trusty Tahr 14.04 - 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list + 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) ** Summary changed: - apt-add-repository adds duplicate commented/disabled source lines + [SRU] apt-add-repository adds duplicate commented/disabled source lines ** Description changed: Impact == Under most circumstances, the impact is minimal (a few extra redundant comment lines in apt sources. However, if users are automating source removal / addition on a machine (as in comment 11), there is the potential to wind up with an excessively large (and thus slow to parse) apt sources configuration. Test Case = * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the presence of one uncommented "deb" line, and one commented "deb-src" line * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated - * Upgrade python-apt to 1.9.3ubuntu2 (or later) + * sudo add-apt-repository ppa:waveform/python-apt + * sudo apt upgrade # update python-apt to fixed version * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note there has been no further duplication of the commented "deb-src" line Regression Potential Minimal; test cases have been added to cover the duplication case, and to cover the enabling of sources (which was not covered by existing tests, but was part of the code altered to fix the duplication case), and insertion of sources at a position (again, not covered by existing tests but modified as part of the fix). The test case has been used successfully on all targeted releases (xenial, bionic, and eoan). Original Description Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository
[Touch-packages] [Bug 1859610] Re: python-gi/arm64 segfaults with the focal-proposed libffi version
> so this is not completely updated to focal-proposed? No, that was just certain focal-proposed packages on a focal image (on a pi4). Have now re-run with a full focal-proposed chroot (under the same focal image), and that doesn't reproduce the issue: (focal-arm64)root@ubuntu:~# cat /etc/apt/sources.list deb http://ports.ubuntu.com/ubuntu-ports focal main restricted universe multiverse deb-src http://ports.ubuntu.com/ubuntu-ports focal main restricted universe multiverse deb http://ports.ubuntu.com/ubuntu-ports focal-updates main restricted universe multiverse deb-src http://ports.ubuntu.com/ubuntu-ports focal-updates main restricted universe multiverse deb http://ports.ubuntu.com/ubuntu-ports focal-proposed main restricted universe multiverse deb-src http://ports.ubuntu.com/ubuntu-ports focal-proposed main restricted universe multiverse deb http://ports.ubuntu.com/ubuntu-ports focal-security main restricted universe multiverse deb-src http://ports.ubuntu.com/ubuntu-ports focal-security main restricted universe multiverse (focal-arm64)root@ubuntu:~# dpkg -l | grep -e "libffi" -e "python3" ii libffi6:arm64 3.2.1-9 arm64 Foreign Function Interface library runtime ii libffi7:arm64 3.3-3 arm64 Foreign Function Interface library runtime ii libpython3-stdlib:arm64 3.7.5-1ubuntu1 arm64 interactive high-level object-oriented language (default python3 version) ii libpython3.7-minimal:arm643.7.6-1ubuntu2 arm64 Minimal subset of the Python language (version 3.7) ii libpython3.7-stdlib:arm64 3.7.6-1ubuntu2 arm64 Interactive high-level object-oriented language (standard library, version 3.7) ii python3 3.7.5-1ubuntu1 arm64 interactive high-level object-oriented language (default python3 version) ii python3-cairo:arm64 1.16.2-2ubuntu1 arm64 Python3 bindings for the Cairo vector graphics library ii python3-gi3.34.0-3build2 arm64 Python 3 bindings for gobject-introspection libraries ii python3-gi-cairo 3.34.0-3build2 arm64 Python 3 Cairo bindings for the GObject library ii python3-goocalendar 0.5-1 all Calendar widget for GTK+ using PyGoocanvas (Python 3) ii python3-minimal 3.7.5-1ubuntu1 arm64 minimal subset of the Python language (default python3 version) ii python3-pkg-resources 44.0.0-1all Package Discovery and Resource Access using pkg_resources ii python3.7 3.7.6-1ubuntu2 arm64 Interactive high-level object-oriented language (version 3.7) ii python3.7-minimal 3.7.6-1ubuntu2 arm64 Minimal subset of the Python language (version 3.7) (focal-arm64)root@ubuntu:~# python3 -c "import goocalendar; print(goocalendar.__version__)" Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused 0.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1859610 Title: python-gi/arm64 segfaults with the focal-proposed libffi version Status in libffi package in Ubuntu: Fix Committed Status in pygobject package in Ubuntu: New Status in libffi source package in Focal: Fix Committed Status in pygobject source package in Focal: New Bug description: Testcase, on focal/arm64 $ sudo apt install python3-goocalendar $ python3 -c "import goocalendar ; print(goocalendar.__version__)" -> works fine install the python3-gi package from focal-proposed it segfaults in libffi Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0xf7390ff8 in ffi_call_SYSV () at ../src/aarch64/sysv.S:114 #2 0xf7390634 in ffi_call_int (cif=0xa12d78, fn=, orig_rvalue=, avalue=0x0, closure=) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1859610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859610] Re: python-gi/arm64 segfaults with the focal-proposed libffi version
> Do you have the new python3.7 installed from focal-proposed? > note, i was running everything from proposed. Since libffi6 & 7 might > be used by python3.7. Ah, no I didn't. However, doesn't seem like it makes much difference: ubuntu@ubuntu:~$ sudo apt install -t focal-proposed python3.7 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libpython3.7 libpython3.7-dbg libpython3.7-minimal libpython3.7-stdlib python3.7-dbg python3.7-minimal Suggested packages: python3.7-venv python3.7-doc python3-gdbm-dbg python3-tk-dbg binfmt-support The following packages will be upgraded: libpython3.7 libpython3.7-dbg libpython3.7-minimal libpython3.7-stdlib python3.7 python3.7-dbg python3.7-minimal 7 upgraded, 0 newly installed, 0 to remove and 72 not upgraded. Need to get 32.9 MB of archives. After this operation, 26.6 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 python3.7-dbg arm64 3.7.6-1ubuntu2 [15.9 MB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 python3.7 arm64 3.7.6-1ubuntu2 [304 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 libpython3.7 arm64 3.7.6-1ubuntu2 [1373 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 libpython3.7-dbg arm64 3.7.6-1ubuntu2 [11.4 MB] Get:5 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 libpython3.7-stdlib arm64 3.7.6-1ubuntu2 [1717 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 python3.7-minimal arm64 3.7.6-1ubuntu2 [1723 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 libpython3.7-minimal arm64 3.7.6-1ubuntu2 [547 kB] Fetched 32.9 MB in 25s (1316 kB/s) (Reading database ... 80531 files and directories currently installed.) Preparing to unpack .../0-python3.7-dbg_3.7.6-1ubuntu2_arm64.deb ... Unpacking python3.7-dbg (3.7.6-1ubuntu2) over (3.7.6-1) ... Preparing to unpack .../1-python3.7_3.7.6-1ubuntu2_arm64.deb ... Unpacking python3.7 (3.7.6-1ubuntu2) over (3.7.6-1) ... Preparing to unpack .../2-libpython3.7_3.7.6-1ubuntu2_arm64.deb ... Unpacking libpython3.7:arm64 (3.7.6-1ubuntu2) over (3.7.6-1) ... Preparing to unpack .../3-libpython3.7-dbg_3.7.6-1ubuntu2_arm64.deb ... Unpacking libpython3.7-dbg:arm64 (3.7.6-1ubuntu2) over (3.7.6-1) ... Preparing to unpack .../4-libpython3.7-stdlib_3.7.6-1ubuntu2_arm64.deb ... Unpacking libpython3.7-stdlib:arm64 (3.7.6-1ubuntu2) over (3.7.6-1) ... Preparing to unpack .../5-python3.7-minimal_3.7.6-1ubuntu2_arm64.deb ... Unpacking python3.7-minimal (3.7.6-1ubuntu2) over (3.7.6-1) ... Preparing to unpack .../6-libpython3.7-minimal_3.7.6-1ubuntu2_arm64.deb ... Unpacking libpython3.7-minimal:arm64 (3.7.6-1ubuntu2) over (3.7.6-1) ... Setting up libpython3.7-minimal:arm64 (3.7.6-1ubuntu2) ... Setting up python3.7-minimal (3.7.6-1ubuntu2) ... Setting up libpython3.7-stdlib:arm64 (3.7.6-1ubuntu2) ... Setting up libpython3.7:arm64 (3.7.6-1ubuntu2) ... Setting up libpython3.7-dbg:arm64 (3.7.6-1ubuntu2) ... Setting up python3.7 (3.7.6-1ubuntu2) ... Setting up python3.7-dbg (3.7.6-1ubuntu2) ... Processing triggers for libc-bin (2.30-0ubuntu3) ... Processing triggers for man-db (2.9.0-2) ... Processing triggers for mime-support (3.64ubuntu1) ... ubuntu@ubuntu:~$ python3 -c "import goocalendar; print(goocalendar.__version__)" Segmentation fault (core dumped) I'll keep the SD card around for a few days if you want me to dig into this any further. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1859610 Title: python-gi/arm64 segfaults with the focal-proposed libffi version Status in libffi package in Ubuntu: Incomplete Status in libffi source package in Focal: Incomplete Bug description: Testcase, on focal/arm64 $ sudo apt install python3-goocalendar $ python3 -c "import goocalendar ; print(goocalendar.__version__)" -> works fine install the python3-gi package from focal-proposed it segfaults in libffi Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0xf7390ff8 in ffi_call_SYSV () at ../src/aarch64/sysv.S:114 #2 0xf7390634 in ffi_call_int (cif=0xa12d78, fn=, orig_rvalue=, avalue=0x0, closure=) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1859610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859610] Re: python-gi/arm64 segfaults with the focal-proposed libffi version
Reproduced on a Pi4 running the current focal daily: ubuntu@ubuntu:~$ python3 -c "import goocalendar; print(goocalendar.__version__)" Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused 0.5 ubuntu@ubuntu:~$ sudo apt install -t focal-proposed python3-gi Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libffi7 python3-gi-cairo The following NEW packages will be installed: libffi7 The following packages will be upgraded: python3-gi python3-gi-cairo 2 upgraded, 1 newly installed, 0 to remove and 85 not upgraded. Need to get 220 kB of archives. After this operation, 60.4 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 python3-gi-cairo arm64 3.34.0-3build2 [8336 B] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 libffi7 arm64 3.3-2.3build1 [17.1 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 python3-gi arm64 3.34.0-3build2 [195 kB] Fetched 220 kB in 2s (114 kB/s) (Reading database ... 79794 files and directories currently installed.) Preparing to unpack .../python3-gi-cairo_3.34.0-3build2_arm64.deb ... Unpacking python3-gi-cairo (3.34.0-3build2) over (3.34.0-3) ... Selecting previously unselected package libffi7:arm64. Preparing to unpack .../libffi7_3.3-2.3build1_arm64.deb ... Unpacking libffi7:arm64 (3.3-2.3build1) ... Preparing to unpack .../python3-gi_3.34.0-3build2_arm64.deb ... Unpacking python3-gi (3.34.0-3build2) over (3.34.0-3) ... Setting up libffi7:arm64 (3.3-2.3build1) ... Setting up python3-gi (3.34.0-3build2) ... Setting up python3-gi-cairo (3.34.0-3build2) ... Processing triggers for libc-bin (2.30-0ubuntu3) ... ubuntu@ubuntu:~$ python3 -c "import goocalendar; print(goocalendar.__version__)" Segmentation fault (core dumped) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1859610 Title: python-gi/arm64 segfaults with the focal-proposed libffi version Status in libffi package in Ubuntu: Incomplete Status in libffi source package in Focal: Incomplete Bug description: Testcase, on focal/arm64 $ sudo apt install python3-goocalendar $ python3 -c "import goocalendar ; print(goocalendar.__version__)" -> works fine install the python3-gi package from focal-proposed it segfaults in libffi Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0xf7390ff8 in ffi_call_SYSV () at ../src/aarch64/sysv.S:114 #2 0xf7390634 in ffi_call_int (cif=0xa12d78, fn=, orig_rvalue=, avalue=0x0, closure=) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1859610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311056] Re: apt-add-repository adds duplicate commented/disabled source lines
I have an updated patch available from the following branch for focal: https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/fix-dupe-ppa Currently building a test package in the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/python-apt/+packages I realize most of the people affected by this are on older distributions, so I'm just in the process of back-porting the patch to bionic, xenial, and trusty, and will provide test builds in the same PPA once that's done. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1311056 Title: apt-add-repository adds duplicate commented/disabled source lines Status in python-apt package in Ubuntu: Triaged Status in software-properties package in Ubuntu: Triaged Bug description: Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1311056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 90085] Re: When /tmp is mounted noexec, preconfigure fails
@jblainemitre indeed - but presumably one can pick any directory? I'm assuming there's no particular requirement that the selected dir is world-writeable like /tmp and /var/tmp (or at least there doesn't seem to be in my setup?) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/90085 Title: When /tmp is mounted noexec, preconfigure fails Status in debconf package in Ubuntu: Triaged Status in debconf package in Debian: Confirmed Bug description: Binary package hint: mysql-server /tmp mounted noexec, this ensues: Preconfiguring packages ... Can't exec "/tmp/mysql-server-5.0.config.89611": Permission denied at /usr/share/perl/5.8/IPC/Open3.pm line 168. open2: exec of /tmp/mysql-server-5.0.config.89611 configure failed at /usr/share/perl5/Debconf/ConfModule.pm line 57 mysql-server-5.0 failed to preconfigure, with exit status 2 ace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/90085/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849435] Re: could not find a distribution template for Ubuntu/focal
Please note for testing: add-apt-repository does not operate without the updated package either, so just download the relevant .debs and install manually with "sudo dpkg -i" for testing. The package that's really needed is python-apt-common (which contains the updated template output), but you may as well update python3-apt as well for the sake of testing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1849435 Title: could not find a distribution template for Ubuntu/focal Status in python-apt package in Ubuntu: In Progress Bug description: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Click on software-properties-gtk icon: I have a message about crash, click on 'send' nothing happen. I attached crash file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1849435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849435] Re: could not find a distribution template for Ubuntu/focal
Updated python-apt package available in the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/pkg Branch from which the package was built: https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/focal-entry -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1849435 Title: could not find a distribution template for Ubuntu/focal Status in python-apt package in Ubuntu: In Progress Bug description: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Click on software-properties-gtk icon: I have a message about crash, click on 'send' nothing happen. I attached crash file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1849435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849435] Re: could not find a distribution template for Ubuntu/focal
** Changed in: python-apt (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: python-apt (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1849435 Title: could not find a distribution template for Ubuntu/focal Status in python-apt package in Ubuntu: In Progress Bug description: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Click on software-properties-gtk icon: I have a message about crash, click on 'send' nothing happen. I attached crash file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1849435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832414] Re: Removing document files spam from cups
For anyone else that encounters this, running "cancel -x -a" to delete everything from the queue (including historical control files) seems to have cured the problem. Sorry for not keeping the evidence around, but I'm afraid after it generated 70Mb of logs in two days I needed to fix it :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1832414 Title: Removing document files spam from cups Status in cups package in Ubuntu: New Bug description: Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last night the CUPS logs have had a considerable number of messages from cupsd stating "Removing document files" - about 3 or 4 a second constantly. Stopping the cups service stops the log-spam, and starting it again immediately resumes it (after a few hundred "Loading from cache..." messages). I've tried removing document files from the cache (there were a couple of ancient ones lying around - it's not a heavily used printer), but this made little difference to the symptoms. I'm pretty confident this is due to the upgrade as: 1. the spam in the logs starts immediately after CUPS reloads (after the upgrade) 2. looking at the diff for 2.1.3-4ubuntu0.9 it does seem to be fiddling with things related to job clean-up (e.g. cupsdUpdateJobs and cupsdCleanJobs in scheduler/job.c) If I can provide any further information, do let me know! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1832414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832414] [NEW] Removing document files spam from cups
Public bug reported: Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last night the CUPS logs have had a considerable number of messages from cupsd stating "Removing document files" - about 3 or 4 a second constantly. Stopping the cups service stops the log-spam, and starting it again immediately resumes it (after a few hundred "Loading from cache..." messages). I've tried removing document files from the cache (there were a couple of ancient ones lying around - it's not a heavily used printer), but this made little difference to the symptoms. I'm pretty confident this is due to the upgrade as: 1. the spam in the logs starts immediately after CUPS reloads (after the upgrade) 2. looking at the diff for 2.1.3-4ubuntu0.9 it does seem to be fiddling with things related to job clean-up (e.g. cupsdUpdateJobs and cupsdCleanJobs in scheduler/job.c) If I can provide any further information, do let me know! ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1832414 Title: Removing document files spam from cups Status in cups package in Ubuntu: New Bug description: Since my server (running xenial) updated to cups 2.1.3-4ubuntu0.9 last night the CUPS logs have had a considerable number of messages from cupsd stating "Removing document files" - about 3 or 4 a second constantly. Stopping the cups service stops the log-spam, and starting it again immediately resumes it (after a few hundred "Loading from cache..." messages). I've tried removing document files from the cache (there were a couple of ancient ones lying around - it's not a heavily used printer), but this made little difference to the symptoms. I'm pretty confident this is due to the upgrade as: 1. the spam in the logs starts immediately after CUPS reloads (after the upgrade) 2. looking at the diff for 2.1.3-4ubuntu0.9 it does seem to be fiddling with things related to job clean-up (e.g. cupsdUpdateJobs and cupsdCleanJobs in scheduler/job.c) If I can provide any further information, do let me know! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1832414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
> /sbin/shutdown, post upgrade not working, imho is a severe bug I suspect no-one's bothered to report it because as soon as the machine is (somehow) rebooted, the issue goes away (and reproduction then involves the pain of going through a trusty install + xenial upgrade cycle). Still, I'm not entirely convinced this *is* a bug; I'll come back to this in a bit below... > I guess the scheduling of timeout is failing, but /sbin/shutdown now works? I thought I'd tested this and concluded it didn't, but it turns out I just didn't wait long enough. When trying "shutdown -r now" there's a fair delay, then it complains about a connection time out, exits with an error, and the system reboots anyway! ubuntu@client1:~$ sudo shutdown -r now Failed to start reboot.target: Connection timed out See system logs and 'systemctl status reboot.target' for details. ubuntu@client1:~$ packet_write_wait: Connection to 10.123.236.170 port 22: Broken pipe So, it is mostly likely the scheduling portion that's failing, and if given an immediate request the operation does still work. I haven't got time to test the -h switch as well, but I'd assume it's probably a similar story. Now consider those two cases from the perspective of a human administrator: If you've typed "shutdown -r now" you're expecting an immediate reboot. Even if some bits of the shutdown command fail, you still expect it to do what you asked: reboot immediately. However, if you've just typed "shutdown -r +5" you're expecting a 5 minute delay before reboot. If it can't schedule that delay would you rather it exit with an error and tell you, or just immediately reboot the system? Probably the former given you're not expecting an immediate reboot. The issue in this case was that it isn't a human scheduling the reboot (directly) and the only reason landscape uses the schedule at all is to determine whether the shutdown command has (likely) worked. Which is a bit of an abuse of the shutdown command's scheduling facility, but I can't think of a better way off the top of my head (that'll reliably work in all implementations). Anyway, in landscape's case we *would* rather the system immediately reboots when shutdown fails because the delay's only there for the Landscape client's benefit, and we can't guarantee the administrator has any other means of accessing the system for the purpose of rebooting it. So in a sense we're dealing with an interface mismatch: shutdown is (understandably) written for the (direct) use of a human administrator, and landscape is (ab)using it to provide reboot/poweroff facilities on (indirect) behalf of a human administrator. So we come back to "I can't think of a better way of doing it" (that'll reliably work in all our aforementioned scenarios of upstart, systemd, and post-upgrade-almost-sort-of-systemd). > Re differences between halt & poweroff, in systemd, eventually it results in: > [snip] Yes, but have a look at the arg parsing earlier on (https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl.c#L8069): case 'h': if (arg_action != ACTION_HALT) arg_action = ACTION_POWEROFF; break; In systemd, the -H and --halt options mean halt, but -h is just an alias for -P and --poweroff (unless -H or --halt also appear in the argument list ... which looks a bit weird to me, but it is what their man-page states as well, so I guess it's intentional?). I haven't dug into upstart's implementation but I assume from your comments that it's different, and that -h actually means halt. Thanks for the link on the differences between halt and power-off - I'd not seen that before! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Incomplete Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Incomplete Bug description: Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
@xnox Scheduling with /sbin/shutdown normally does work ... however, what we're dealing with here is the anomalous situation of an instance which starts off as trusty and is upgraded to xenial. During the upgrade process, the /sbin/shutdown implementation is changed from the upstart one to the systemd one. At the end of the process, /sbin/shutdown is (unsurprisingly) a link to systemctl ... but it doesn't work because it's expecting to be able to talk to systemd which isn't fully operational until a reboot. As Landscape is expecting to be able to reboot via /sbin/shutdown the user relying on Landscape in such a scenario finds themselves in a bit of a bind (having to have some other means of dealing with the server, like SSH). However, /sbin/reboot and /sbin/poweroff *do* work in this (admittedly rare) scenario, hence the patches committed for this issue leave the system using /sbin/shutdown by default but if/when it fails, they fall back to trying /sbin/reboot or /sbin/poweroff (as appropriate) instead. As to why -h is used instead of -P, in systemd's implementation of /sbin/shutdown they're exactly the same thing. In the upstart implementation it's more vague; quoting from the man-page: "Requests that the system be either halted or powered off after it has been brought down, with the choice as to which left up to the system". I'm not sure what that means in practice though! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Incomplete Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Incomplete Bug description: Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
** Changed in: landscape-client (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Incomplete Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Incomplete Bug description: Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
I've now pushed a PR which should alleviate the reboot issue
*partially*. The complexity in fixing this arises from the differing
behaviours of implementations of the shutdown, poweroff, and reboot
commands; upstart's poweroff & reboot commands for example, immediately
return (briefly) permitting the caller to query their exit codes. In
contrast, systemd's don't return at all unless the poweroff or reboot
fails. None of the reboot or poweroff implementations provide a
scheduling facility like the /sbin/shutdown implementation
(unsurprisingly), but systemd's poweroff and reboot commands *do* work
even in the post-trusty upgrade environment (even though systemd's
shutdown command doesn't).
The quandry is as follows: we can reliably detect when the shutdown
command fails (it exits with an exit code and some error messages), and
when it succeeds ... sort of. We currently schedule the shutdown for 4
minutes time and if it hasn't died within 10 seconds we assume it's
going to work; this assumes that the implementation won't fail at the
end of the schedule but so far that seems a reliable assumption under
both upstart and systemd. We cannot *reliably* detect when the poweroff
or reboot commands either succeed or fail, but they do seem reliable in
practice even in aberrant environments like the post-trusty upgrade.
So, the method I've chosen is as follows: treat shutdown and restart
requests as we presently do (schedule /bin/shutdown for 4 minutes time,
monitor for 10 seconds). If it succeeds, nothing changes. If it fails,
report the failure with an extra message indicating we are going to
attempt to force the procedure, then run /sbin/poweroff or /sbin/reboot
as appropriate. The result is that in the post-trusty environment
(testing on containers and VMs) a reboot request does succeed, but is
still reported as failing (albeit with an extended message explaining
we're going to try and force it).
We *could* report it as succeeding, but frankly there's no guarantees so
it's a choice between giving the user bad news ("sorry your reboot
request failed ...") with a possible silver lining ("... but we're going
to try another way which *might* work, however we won't be able to
tell"), or giving the user good news ("your reboot request worked after
we forced it") and hoping we're not lying! The former sounds like the
more sensible approach to me, and hence is what is in the PR
(https://github.com/CanonicalLtd/landscape-client/pull/55).
** Changed in: landscape-client (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: landscape-client (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
Status in landscape-client package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
Incomplete
Status in landscape-client source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
Incomplete
Bug description:
Used Landscape (Paid Canonical Subscription) to upgrade one of my
machines.
Landscape only shows "In Progress" for more than 8 hours now and asked
for a reboot of the machine in a second alert.
In the reboot attempt I get the message:
=
Failed to set wall message, ignoring: Method "SetWallMessage" with signature
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
Failed to call ScheduleShutdown in logind, proceeding with immediate
shutdown: Method "ScheduleShutdown" with signature "st" on interface
"org.freedesktop.login1.Manager" doesn't exist
=
Steps to reproduce:
* Fully updated 14.04.5 machine
* Open Landscape
* Choose the machine
* Choose Packages
* This computer can be upgraded to a newer release
* Apply
* Wait 2 hours
* Alert comes in a seperate Landscape message Machine is ready for reboot
* Choose Info... Power
* Deliver to selected computers as soon as possible
* Error message
I found this thread on reddit about this issue maybe the solution can be
built into the upgrade script
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
Seems like there's two issues here which I'll address in separate PRs to the landscape-client: First is the issue that the landscape-client fails to report the completion (or failure) of the release upgrade process. This turns out to be due to a delayed import in the version of twisted distributed with trusty. Because the import (of twisted.internet.unix) is delayed, by the time we *do* import it (implicitly by calling another twisted method), the twisted version on disk has been replaced with the xenial version and things (unsurprisingly) break. The trivial fix is to pre-emptively import the module prior to starting the release upgrade; I'll push a PR for this in a moment. The second issue is that landscape-client fails to reboot (or shutdown) the machine immediately following the release upgrade procedure. This is due to the fact landscape-client currently relies upon /sbin/shutdown to handle reboot or shutdown requests. This utility operates happily in its upstart variant (in trusty), and systemd variant (in xenial and beyond), but fails in the post-trusty-to-xenial upgrade environment when the system on disk is effectively xenial (so /sbin/shutdown is a link to systemctl), but the running environment is still partially trusty. It transpires that systemctl (without the double --force --force option) requires both systemd and dbus to be operational in order to successfully (and cleanly) shutdown or restart. The fix for this is a little more complex as the landscape-client relies upon the scheduling function of /sbin/shutdown to ensure it can request a shutdown and still report back to the server before the machine actually goes down. I'm still investigating the best method which will work reliably in all potential environments. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Incomplete Bug description: Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1003854] Re: Database upgrade/migration fails with nested db directories (lucid to precise)
My backup was indeed slapcat / slapadd (for both the main directory and
the cn=config stuff). I'd *guess* that if the package state is "ii" you
may not need the patch (incidentally the patch is in bug description at
the top), particularly if the server's starting fine and everything
queries happily. Mine didn't start after the upgrade so I definitely
needed the patch, but I wouldn't like to guess about other situations
(given how variable LDAP setups can be).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1003854
Title:
Database upgrade/migration fails with nested db directories (lucid to
precise)
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Precise:
Confirmed
Status in openldap package in Debian:
Fix Released
Bug description:
Hi,
I've just performed an upgrade of our LDAP server on Ubuntu 10.04.4
LTS to Ubuntu 12.04 (I acknowledge this upgrade path is not officially
supported yet).
The incompatible database upgrading process in the preinst/postinst
files failed in the following scenario.
We have two suffixes/databases at the following paths:-
* /var/lib/ldap
* /var/lib/ldap/accesslog
The preinst database dumping part of the process worked just fine and
created the appropriate LDIF files under
/var/backup/slapd-2.4.21-0ubuntu5.7, however the restore failed
stating:-
"""
Loading from /var/backups/slapd-2.4.21-0ubuntu5.7:
- directory dc=REDACTEDs,dc=co,dc=uk... failed.
Loading the database from the LDIF dump failed with the following
error while running slapadd:
4fbdfebf olcDbDirectory: value #0: invalid path: No such file or directory
4fbdfebf config error processing olcDatabase={2}hdb,cn=config:
olcDbDirectory: value #0: invalid path: No such file or directory
slapadd: bad configuration directory!
"""
This is because when move_incompatible_databases_away() runs it finds
the main database first (/var/lib/ldap) and moves all top level
entries (find -mindepth 1 -maxdepth 1 ...) into the backup directory
and this includes the accesslog subdirectory which then no longer
exists. When slapadd runs it checks config specifying that directory
and bails with the above error given it is indeed missing.
I've tested a tentative fix and that's to patch the two find commands
(one in is_empty_dir() one in move_old_database_away to also specify
-type f so that the directory structure is preserved when moving the
old database away (accesslog will be backed up separately when its
suffx is iterated over in move_incompatible_databases_away()).
The simple and very tentative patch for this is:-
"""
# diff -u slapd.scripts-common.old slapd.scripts-common
--- slapd.scripts-common.old 2012-05-24 10:33:01.746206585 +0100
+++ slapd.scripts-common 2012-05-24 10:33:23.967902747 +0100
@@ -391,7 +391,7 @@
echo -n " - directory $suffix... " >&2
mkdir -p "$backupdir"
find "$databasedir" -mindepth 1 -maxdepth 1\
- -exec mv {} "$backupdir" \;
+ -type f -exec mv {} "$backupdir" \;
echo done. >&2
else
cat >&2 /dev/null`
if [ -n "$output" ]; then
return 1
else
"""
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1003854/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1003854] Re: Database upgrade/migration fails with nested db directories (lucid to precise)
Hi Andre - I did take a backup of the LDAP directory prior to "do-
release-upgrade" (actually I had nightly backups running so I just
grabbed a copy of the last one of those). That's what I was referring to
when I stated "restore the old-version backup...". It's been a few
months now but I vaguely recall that the upgrade procedure needs the
state of the database prior to the (failed) upgrade in order to succeed
after patching.
Hence, if my recollection is accurate, my procedure was:
1. Patch the slapd.postinst script
2. Restore the database to its state prior to the (failed) upgrade
3. Run "dpkg --configure -a" to cause the slapd postinst script to upgrade the
database successfully
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1003854
Title:
Database upgrade/migration fails with nested db directories (lucid to
precise)
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Precise:
Confirmed
Status in openldap package in Debian:
Fix Released
Bug description:
Hi,
I've just performed an upgrade of our LDAP server on Ubuntu 10.04.4
LTS to Ubuntu 12.04 (I acknowledge this upgrade path is not officially
supported yet).
The incompatible database upgrading process in the preinst/postinst
files failed in the following scenario.
We have two suffixes/databases at the following paths:-
* /var/lib/ldap
* /var/lib/ldap/accesslog
The preinst database dumping part of the process worked just fine and
created the appropriate LDIF files under
/var/backup/slapd-2.4.21-0ubuntu5.7, however the restore failed
stating:-
"""
Loading from /var/backups/slapd-2.4.21-0ubuntu5.7:
- directory dc=REDACTEDs,dc=co,dc=uk... failed.
Loading the database from the LDIF dump failed with the following
error while running slapadd:
4fbdfebf olcDbDirectory: value #0: invalid path: No such file or directory
4fbdfebf config error processing olcDatabase={2}hdb,cn=config:
olcDbDirectory: value #0: invalid path: No such file or directory
slapadd: bad configuration directory!
"""
This is because when move_incompatible_databases_away() runs it finds
the main database first (/var/lib/ldap) and moves all top level
entries (find -mindepth 1 -maxdepth 1 ...) into the backup directory
and this includes the accesslog subdirectory which then no longer
exists. When slapadd runs it checks config specifying that directory
and bails with the above error given it is indeed missing.
I've tested a tentative fix and that's to patch the two find commands
(one in is_empty_dir() one in move_old_database_away to also specify
-type f so that the directory structure is preserved when moving the
old database away (accesslog will be backed up separately when its
suffx is iterated over in move_incompatible_databases_away()).
The simple and very tentative patch for this is:-
"""
# diff -u slapd.scripts-common.old slapd.scripts-common
--- slapd.scripts-common.old 2012-05-24 10:33:01.746206585 +0100
+++ slapd.scripts-common 2012-05-24 10:33:23.967902747 +0100
@@ -391,7 +391,7 @@
echo -n " - directory $suffix... " >&2
mkdir -p "$backupdir"
find "$databasedir" -mindepth 1 -maxdepth 1\
- -exec mv {} "$backupdir" \;
+ -type f -exec mv {} "$backupdir" \;
echo done. >&2
else
cat >&2 /dev/null`
if [ -n "$output" ]; then
return 1
else
"""
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1003854/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1003854] Re: Database upgrade/migration fails with nested db directories (lucid to precise)
Ah, no worries - finally figured it out. Needed to apply the patch to
/var/lib/dpkg/info/slapd.postinst (rather than slapd.config - was
confused over package's half-configured state) and restore the old-
version backup prior to retrying "dpkg --configure -a". All good now!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1003854
Title:
Database upgrade/migration fails with nested db directories (lucid to
precise)
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Precise:
Confirmed
Status in openldap package in Debian:
Fix Released
Bug description:
Hi,
I've just performed an upgrade of our LDAP server on Ubuntu 10.04.4
LTS to Ubuntu 12.04 (I acknowledge this upgrade path is not officially
supported yet).
The incompatible database upgrading process in the preinst/postinst
files failed in the following scenario.
We have two suffixes/databases at the following paths:-
* /var/lib/ldap
* /var/lib/ldap/accesslog
The preinst database dumping part of the process worked just fine and
created the appropriate LDIF files under
/var/backup/slapd-2.4.21-0ubuntu5.7, however the restore failed
stating:-
"""
Loading from /var/backups/slapd-2.4.21-0ubuntu5.7:
- directory dc=REDACTEDs,dc=co,dc=uk... failed.
Loading the database from the LDIF dump failed with the following
error while running slapadd:
4fbdfebf olcDbDirectory: value #0: invalid path: No such file or directory
4fbdfebf config error processing olcDatabase={2}hdb,cn=config:
olcDbDirectory: value #0: invalid path: No such file or directory
slapadd: bad configuration directory!
"""
This is because when move_incompatible_databases_away() runs it finds
the main database first (/var/lib/ldap) and moves all top level
entries (find -mindepth 1 -maxdepth 1 ...) into the backup directory
and this includes the accesslog subdirectory which then no longer
exists. When slapadd runs it checks config specifying that directory
and bails with the above error given it is indeed missing.
I've tested a tentative fix and that's to patch the two find commands
(one in is_empty_dir() one in move_old_database_away to also specify
-type f so that the directory structure is preserved when moving the
old database away (accesslog will be backed up separately when its
suffx is iterated over in move_incompatible_databases_away()).
The simple and very tentative patch for this is:-
"""
# diff -u slapd.scripts-common.old slapd.scripts-common
--- slapd.scripts-common.old 2012-05-24 10:33:01.746206585 +0100
+++ slapd.scripts-common 2012-05-24 10:33:23.967902747 +0100
@@ -391,7 +391,7 @@
echo -n " - directory $suffix... " >&2
mkdir -p "$backupdir"
find "$databasedir" -mindepth 1 -maxdepth 1\
- -exec mv {} "$backupdir" \;
+ -type f -exec mv {} "$backupdir" \;
echo done. >&2
else
cat >&2 /dev/null`
if [ -n "$output" ]; then
return 1
else
"""
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1003854/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1003854] Re: Database upgrade/migration fails with nested db directories (lucid to precise)
Also encountered this when upgrading a server from 12.04 to 14.04 (for
reference, wound up filing duplicate bug #1579566). Managed to get slapd
restored happily by creating the accesslog directory (then slapadd to
restore).
Unfortunately as I restored the database, rather than apt handling it,
the slapd package is now in "iF" state (according to dpkg -l).
Attempting to fix this with "apt-get -f install" leads to the original
situation: the package attempts to backup and restore the database
unsuccessfully presumably because the slapd package it's attempting to
update to is 2.4.31 (the current version in trusty) while the fixed
version is the later 2.4.40.
Any hints on how to resolve the situation (e.g. by simply marking the
package "installed"? slapd does appear to be working happily with the
manually restored database)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1003854
Title:
Database upgrade/migration fails with nested db directories (lucid to
precise)
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Precise:
Confirmed
Status in openldap package in Debian:
Fix Released
Bug description:
Hi,
I've just performed an upgrade of our LDAP server on Ubuntu 10.04.4
LTS to Ubuntu 12.04 (I acknowledge this upgrade path is not officially
supported yet).
The incompatible database upgrading process in the preinst/postinst
files failed in the following scenario.
We have two suffixes/databases at the following paths:-
* /var/lib/ldap
* /var/lib/ldap/accesslog
The preinst database dumping part of the process worked just fine and
created the appropriate LDIF files under
/var/backup/slapd-2.4.21-0ubuntu5.7, however the restore failed
stating:-
"""
Loading from /var/backups/slapd-2.4.21-0ubuntu5.7:
- directory dc=REDACTEDs,dc=co,dc=uk... failed.
Loading the database from the LDIF dump failed with the following
error while running slapadd:
4fbdfebf olcDbDirectory: value #0: invalid path: No such file or directory
4fbdfebf config error processing olcDatabase={2}hdb,cn=config:
olcDbDirectory: value #0: invalid path: No such file or directory
slapadd: bad configuration directory!
"""
This is because when move_incompatible_databases_away() runs it finds
the main database first (/var/lib/ldap) and moves all top level
entries (find -mindepth 1 -maxdepth 1 ...) into the backup directory
and this includes the accesslog subdirectory which then no longer
exists. When slapadd runs it checks config specifying that directory
and bails with the above error given it is indeed missing.
I've tested a tentative fix and that's to patch the two find commands
(one in is_empty_dir() one in move_old_database_away to also specify
-type f so that the directory structure is preserved when moving the
old database away (accesslog will be backed up separately when its
suffx is iterated over in move_incompatible_databases_away()).
The simple and very tentative patch for this is:-
"""
# diff -u slapd.scripts-common.old slapd.scripts-common
--- slapd.scripts-common.old 2012-05-24 10:33:01.746206585 +0100
+++ slapd.scripts-common 2012-05-24 10:33:23.967902747 +0100
@@ -391,7 +391,7 @@
echo -n " - directory $suffix... " >&2
mkdir -p "$backupdir"
find "$databasedir" -mindepth 1 -maxdepth 1\
- -exec mv {} "$backupdir" \;
+ -type f -exec mv {} "$backupdir" \;
echo done. >&2
else
cat >&2 /dev/null`
if [ -n "$output" ]; then
return 1
else
"""
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1003854/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579566] Re: Automatic openldap db migration fails on release upgrade when using nested database directories
*** This bug is a duplicate of bug 1003854 ***
https://bugs.launchpad.net/bugs/1003854
Ah, you're absolutely right - that looks like it. Sorry for the
duplicate (don't know why I didn't find that report first)!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1579566
Title:
Automatic openldap db migration fails on release upgrade when using
nested database directories
Status in openldap package in Ubuntu:
New
Bug description:
While attempting to perform an upgrade of my home server from Ubuntu
12.04 to Ubuntu 14.04, I received the following error:
===
Error in function:
A fatal error occurred
Please report this as a bug and include the files
/var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in
your report. The upgrade has aborted.
Your original sources.list was saved in
/etc/apt/sources.list.distUpgrade.
SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
Could not install the upgrades
The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).
Setting up slapd (2.4.31-1+nmu2ubuntu8.2) ...
Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.28-1.1ubuntu4.6...
done.
Moving old database directories to /var/backups:
Loading from /var/backups/slapd-2.4.28-1.1ubuntu4.6:
- directory dc=waveform,dc=org,dc=uk... failed.
Loading the database from the LDIF dump failed with the following
error while running slapadd:
572f946e olcDbDirectory: value #0: invalid path: No such file or directory
572f946e config error processing olcDatabase={2}hdb,cn=config:
olcDbDirectory: value #0: invalid path: No such file or directory
slapadd: bad configuration directory!
dpkg: error processing package slapd (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
slapd
Upgrade complete
The upgrade has completed but there were errors during the upgrade
process.
===
Admittedly, it's rather strange for a home server to use LDAP for
authentication but I don't have a terribly complex setup: openldap
with a fairly normal LDAP layout and SSSD for handling the PAM
interface (no kerberos - I did try it in the past but quickly gave it
up as too complex to maintain). Hence, I was rather expecting the
upgrade to be relatively smooth (as much as server upgrades ever are
:).
As requested in the message I'm attaching /var/log/dist-
upgrade/main.log and /var/log/dist-upgrade/apt.log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1579566/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579566] Re: Automatic openldap db migration fails on release upgrade when using accesslog overlay
I should add: I think the accesslog overlay is implicit in replicated
setups (yes, I know, weird enough that a home server's using LDAP, but
replication too?! I originally set it up to learn about LDAP replication
in order to use it at work :). It seems to be used to ease the burden of
change queries from downstream servers - hence I'm guessing this bug
will apply particularly to openldap installations using syncrepl.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1579566
Title:
Automatic openldap db migration fails on release upgrade when using
accesslog overlay
Status in openldap package in Ubuntu:
New
Bug description:
While attempting to perform an upgrade of my home server from Ubuntu
12.04 to Ubuntu 14.04, I received the following error:
===
Error in function:
A fatal error occurred
Please report this as a bug and include the files
/var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in
your report. The upgrade has aborted.
Your original sources.list was saved in
/etc/apt/sources.list.distUpgrade.
SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
Could not install the upgrades
The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).
Setting up slapd (2.4.31-1+nmu2ubuntu8.2) ...
Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.28-1.1ubuntu4.6...
done.
Moving old database directories to /var/backups:
Loading from /var/backups/slapd-2.4.28-1.1ubuntu4.6:
- directory dc=waveform,dc=org,dc=uk... failed.
Loading the database from the LDIF dump failed with the following
error while running slapadd:
572f946e olcDbDirectory: value #0: invalid path: No such file or directory
572f946e config error processing olcDatabase={2}hdb,cn=config:
olcDbDirectory: value #0: invalid path: No such file or directory
slapadd: bad configuration directory!
dpkg: error processing package slapd (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
slapd
Upgrade complete
The upgrade has completed but there were errors during the upgrade
process.
===
Admittedly, it's rather strange for a home server to use LDAP for
authentication but I don't have a terribly complex setup: openldap
with a fairly normal LDAP layout and SSSD for handling the PAM
interface (no kerberos - I did try it in the past but quickly gave it
up as too complex to maintain). Hence, I was rather expecting the
upgrade to be relatively smooth (as much as server upgrades ever are
:).
As requested in the message I'm attaching /var/log/dist-
upgrade/main.log and /var/log/dist-upgrade/apt.log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1579566/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579566] Re: fatal error while migrating openldap during 12.04 to 14.04 upgrade
After a bit of playing around, it appears the root cause was that I'm
using the accesslog overlay which necessitates having another database
under /var/lib/ldap/accesslog. The migration process backed up
everything under /var/lib/ldap to /var/backups then re-created
/var/lib/ldap - but didn't created the "accesslog" directory under it.
As a result the attempt to restore the database (presumably with
slapadd) failed. After I recreated the /var/lib/ldap/accesslog directory
(with appropriate ownership of openldap:openldap), the database restored
successfully.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1579566
Title:
fatal error while migrating openldap during 12.04 to 14.04 upgrade
Status in openldap package in Ubuntu:
New
Bug description:
While attempting to perform an upgrade of my home server from Ubuntu
12.04 to Ubuntu 14.04, I received the following error:
===
Error in function:
A fatal error occurred
Please report this as a bug and include the files
/var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in
your report. The upgrade has aborted.
Your original sources.list was saved in
/etc/apt/sources.list.distUpgrade.
SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
Could not install the upgrades
The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).
Setting up slapd (2.4.31-1+nmu2ubuntu8.2) ...
Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.28-1.1ubuntu4.6...
done.
Moving old database directories to /var/backups:
Loading from /var/backups/slapd-2.4.28-1.1ubuntu4.6:
- directory dc=waveform,dc=org,dc=uk... failed.
Loading the database from the LDIF dump failed with the following
error while running slapadd:
572f946e olcDbDirectory: value #0: invalid path: No such file or directory
572f946e config error processing olcDatabase={2}hdb,cn=config:
olcDbDirectory: value #0: invalid path: No such file or directory
slapadd: bad configuration directory!
dpkg: error processing package slapd (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
slapd
Upgrade complete
The upgrade has completed but there were errors during the upgrade
process.
===
Admittedly, it's rather strange for a home server to use LDAP for
authentication but I don't have a terribly complex setup: openldap
with a fairly normal LDAP layout and SSSD for handling the PAM
interface (no kerberos - I did try it in the past but quickly gave it
up as too complex to maintain). Hence, I was rather expecting the
upgrade to be relatively smooth (as much as server upgrades ever are
:).
As requested in the message I'm attaching /var/log/dist-
upgrade/main.log and /var/log/dist-upgrade/apt.log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1579566/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579566] [NEW] fatal error while migrating openldap during 12.04 to 14.04 upgrade
Public bug reported:
While attempting to perform an upgrade of my home server from Ubuntu
12.04 to Ubuntu 14.04, I received the following error:
===
Error in function:
A fatal error occurred
Please report this as a bug and include the files
/var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in
your report. The upgrade has aborted.
Your original sources.list was saved in
/etc/apt/sources.list.distUpgrade.
SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
Could not install the upgrades
The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).
Setting up slapd (2.4.31-1+nmu2ubuntu8.2) ...
Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.28-1.1ubuntu4.6...
done.
Moving old database directories to /var/backups:
Loading from /var/backups/slapd-2.4.28-1.1ubuntu4.6:
- directory dc=waveform,dc=org,dc=uk... failed.
Loading the database from the LDIF dump failed with the following
error while running slapadd:
572f946e olcDbDirectory: value #0: invalid path: No such file or directory
572f946e config error processing olcDatabase={2}hdb,cn=config:
olcDbDirectory: value #0: invalid path: No such file or directory
slapadd: bad configuration directory!
dpkg: error processing package slapd (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
slapd
Upgrade complete
The upgrade has completed but there were errors during the upgrade
process.
===
Admittedly, it's rather strange for a home server to use LDAP for
authentication but I don't have a terribly complex setup: openldap with
a fairly normal LDAP layout and SSSD for handling the PAM interface (no
kerberos - I did try it in the past but quickly gave it up as too
complex to maintain). Hence, I was rather expecting the upgrade to be
relatively smooth (as much as server upgrades ever are :).
As requested in the message I'm attaching /var/log/dist-upgrade/main.log
and /var/log/dist-upgrade/apt.log
** Affects: openldap (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "main log from server upgrade"
https://bugs.launchpad.net/bugs/1579566/+attachment/4658825/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1579566
Title:
fatal error while migrating openldap during 12.04 to 14.04 upgrade
Status in openldap package in Ubuntu:
New
Bug description:
While attempting to perform an upgrade of my home server from Ubuntu
12.04 to Ubuntu 14.04, I received the following error:
===
Error in function:
A fatal error occurred
Please report this as a bug and include the files
/var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in
your report. The upgrade has aborted.
Your original sources.list was saved in
/etc/apt/sources.list.distUpgrade.
SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
Could not install the upgrades
The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).
Setting up slapd (2.4.31-1+nmu2ubuntu8.2) ...
Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.28-1.1ubuntu4.6...
done.
Moving old database directories to /var/backups:
Loading from /var/backups/slapd-2.4.28-1.1ubuntu4.6:
- directory dc=waveform,dc=org,dc=uk... failed.
Loading the database from the LDIF dump failed with the following
error while running slapadd:
572f946e olcDbDirectory: value #0: invalid path: No such file or directory
572f946e config error processing olcDatabase={2}hdb,cn=config:
olcDbDirectory: value #0: invalid path: No such file or directory
slapadd: bad configuration directory!
dpkg: error processing package slapd (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
slapd
Upgrade complete
The upgrade has completed but there were errors during the upgrade
process.
===
Admittedly, it's rather strange for a home server to use LDAP for
authentication but I don't have a terribly complex setup: openldap
with a fairly normal LDAP layout and SSSD for handling the PAM
interface (no kerberos - I did try it in the past but quickly gave it
up as too complex to maintain). Hence, I was rather expecting the
upgrade to be relatively smooth (as much as server upgrades ever are
:).
As requested in the
[Touch-packages] [Bug 1579566] Re: fatal error while migrating openldap during 12.04 to 14.04 upgrade
** Attachment added: "apt log from server upgrade"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1579566/+attachment/4658826/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1579566
Title:
fatal error while migrating openldap during 12.04 to 14.04 upgrade
Status in openldap package in Ubuntu:
New
Bug description:
While attempting to perform an upgrade of my home server from Ubuntu
12.04 to Ubuntu 14.04, I received the following error:
===
Error in function:
A fatal error occurred
Please report this as a bug and include the files
/var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in
your report. The upgrade has aborted.
Your original sources.list was saved in
/etc/apt/sources.list.distUpgrade.
SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)
Could not install the upgrades
The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).
Setting up slapd (2.4.31-1+nmu2ubuntu8.2) ...
Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.28-1.1ubuntu4.6...
done.
Moving old database directories to /var/backups:
Loading from /var/backups/slapd-2.4.28-1.1ubuntu4.6:
- directory dc=waveform,dc=org,dc=uk... failed.
Loading the database from the LDIF dump failed with the following
error while running slapadd:
572f946e olcDbDirectory: value #0: invalid path: No such file or directory
572f946e config error processing olcDatabase={2}hdb,cn=config:
olcDbDirectory: value #0: invalid path: No such file or directory
slapadd: bad configuration directory!
dpkg: error processing package slapd (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
slapd
Upgrade complete
The upgrade has completed but there were errors during the upgrade
process.
===
Admittedly, it's rather strange for a home server to use LDAP for
authentication but I don't have a terribly complex setup: openldap
with a fairly normal LDAP layout and SSSD for handling the PAM
interface (no kerberos - I did try it in the past but quickly gave it
up as too complex to maintain). Hence, I was rather expecting the
upgrade to be relatively smooth (as much as server upgrades ever are
:).
As requested in the message I'm attaching /var/log/dist-
upgrade/main.log and /var/log/dist-upgrade/apt.log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1579566/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
