[Bug 1547927] Re: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS
Oh, and if you're wondering, the ldaps:// results are the correct ones: an untrusted CA (self signed) should be rejected. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1547927 Title: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1547927/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
There is a work around for this issue currently in place. The change was to remove one of the 10 ipv6 addresses that were returned in a query for security.ubuntu.com or archive.ubuntu.com. Now there are only 9 ipv6 addresses in place. This works around the issue and users should not see this error when using squid as a apt mirror. We will work on diagnosing the fix and getting the proper change SRU'd into the archive. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1547640/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
I tried downgrading libc6 and restarting squid (heck, even rebooting the container), but it still happened. Scott IIRC also tried that. Still, it's a heck of a coincidence. Squid in debug mode shows it's getting 10 IPv4 and 10 IPv6 addresses back for the archive, and trying each one in turn. But once it crosses over to the ipv4 ones the log gets a bit confusing for me: 2016/02/20 22:18:32.559| ipcache.cc(497) ipcacheParse: ipcacheParse: 20 answers for 'security.ubuntu.com' 2016/02/20 22:18:32.559| ipcache.cc(566) ipcacheParse: ipcacheParse: security.ubuntu.com #0 [2001:67c:1360:8001::17] 2016/02/20 22:18:32.559| ipcache.cc(566) ipcacheParse: ipcacheParse: security.ubuntu.com #1 [2001:67c:1562::15] 2016/02/20 22:18:32.559| ipcache.cc(566) ipcacheParse: ipcacheParse: security.ubuntu.com #2 [2001:67c:1360:8c01::19] 2016/02/20 22:18:32.559| ipcache.cc(566) ipcacheParse: ipcacheParse: security.ubuntu.com #3 [2001:67c:1360:8c01::18] 2016/02/20 22:18:32.559| ipcache.cc(566) ipcacheParse: ipcacheParse: security.ubuntu.com #4 [2001:67c:1562::14] 2016/02/20 22:18:32.559| ipcache.cc(566) ipcacheParse: ipcacheParse: security.ubuntu.com #5 [2001:67c:1562::17] 2016/02/20 22:18:32.559| ipcache.cc(566) ipcacheParse: ipcacheParse: security.ubuntu.com #6 [2001:67c:1560:8001::13] 2016/02/20 22:18:32.559| ipcache.cc(566) ipcacheParse: ipcacheParse: security.ubuntu.com #7 [2001:67c:1562::13] 2016/02/20 22:18:32.559| ipcache.cc(566) ipcacheParse: ipcacheParse: security.ubuntu.com #8 [2001:67c:1562::16] 2016/02/20 22:18:32.559| ipcache.cc(566) ipcacheParse: ipcacheParse: security.ubuntu.com #9 [2001:67c:1560:8001::11] 2016/02/20 22:18:32.559| ipcache.cc(555) ipcacheParse: ipcacheParse: security.ubuntu.com #10 91.189.91.13 2016/02/20 22:18:32.559| ipcache.cc(555) ipcacheParse: ipcacheParse: security.ubuntu.com #11 91.189.88.153 2016/02/20 22:18:32.559| ipcache.cc(555) ipcacheParse: ipcacheParse: security.ubuntu.com #12 91.189.91.15 2016/02/20 22:18:32.559| ipcache.cc(555) ipcacheParse: ipcacheParse: security.ubuntu.com #13 91.189.91.23 2016/02/20 22:18:32.559| ipcache.cc(555) ipcacheParse: ipcacheParse: security.ubuntu.com #14 91.189.88.152 2016/02/20 22:18:32.559| ipcache.cc(555) ipcacheParse: ipcacheParse: security.ubuntu.com #15 91.189.88.149 2016/02/20 22:18:32.559| ipcache.cc(555) ipcacheParse: ipcacheParse: security.ubuntu.com #16 91.189.92.201 2016/02/20 22:18:32.559| ipcache.cc(555) ipcacheParse: ipcacheParse: security.ubuntu.com #17 91.189.91.24 2016/02/20 22:18:32.559| ipcache.cc(555) ipcacheParse: ipcacheParse: security.ubuntu.com #18 91.189.92.200 2016/02/20 22:18:32.559| ipcache.cc(555) ipcacheParse: ipcacheParse: security.ubuntu.com #19 91.189.91.14 Marks :17 as bad: 2016/02/20 22:18:32.560| ipcache.cc(1075) ipcacheMarkBadAddr: ipcacheMarkBadAddr: security.ubuntu.com [2001:67c:1360:8001::17]:80 Decides to check :15 2016/02/20 22:18:32.560| ipcache.cc(1039) ipcacheCycleAddr: ipcacheCycleAddr: security.ubuntu.com now at [2001:67c:1562::15] (2 of 20) 2016/02/20 22:18:32.560| AsyncCall.cc(85) ScheduleCall: ConnOpener.cc(132) will call fwdConnectDoneWrapper(local=[::] remote=[2001:67c:1360:8001::17]:80 flags=1, errno=101, flag=-8, data=0x555c4de451b8) [call23] (...) last ipv6 one, starting ipv4: 2016/02/20 22:18:32.568| ipcache.cc(1075) ipcacheMarkBadAddr: ipcacheMarkBadAddr: security.ubuntu.com [2001:67c:1560:8001::11]:80 2016/02/20 22:18:32.568| ipcache.cc(1039) ipcacheCycleAddr: ipcacheCycleAddr: security.ubuntu.com now at 91.189.91.13 (11 of 20) 2016/02/20 22:18:32.568| AsyncCall.cc(85) ScheduleCall: ConnOpener.cc(132) will call fwdConnectDoneWrapper(local=[::] remote=[2001:67c:1560:8001::11]:80 flags=1, errno=101, flag=-8, data=0x555c4de451b8) [call68] (...) I don't see it trying the ipv4 address, just considering it, but no connection attempt: 2016/02/20 22:18:32.577| ConnOpener.cc(346) connect: local=[::] remote=[2001:67c:1562::15]:80 flags=1: * - ERR tried too many times already. 2016/02/20 22:18:32.577| ipcache.cc(1039) ipcacheCycleAddr: ipcacheCycleAddr: security.ubuntu.com now at 91.189.91.15 (13 of 20) 2016/02/20 22:18:32.577| AsyncCall.cc(85) ScheduleCall: ConnOpener.cc(132) will call fwdConnectDoneWrapper(local=[::] remote=[2001:67c:1562::15]:80 flags=1, errno=101, flag=-8, data=0x555c4de451b8) [call83] That's how far I got. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1547640/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
I'm unfamiliar with the squid codebase but if it does use the normal socket library, it would be doing a getaddrinfo, then iterate over the results, those results would begin with IPv6 records as IPv6 is always to be preferred over IPv4 when available, but any attempt to connect would result in a Network unreachable error and so cause a fallback to the next result. Assuming squid uses the normal resolving code, the only normal situations in which this behavior would happen is if the host does have a route to the target IPv6 subnet (such as a default route) OR if getaddrinfo is only returning records. With getaddrinfo being provided by glibc and in the very codepath which was modified for the security update, it'd be my first bet that this is somehow related. It would be pretty trivial to check too for someone with an affected system, just downgrade glibc to the previous version (right before this week's security fix), then restart squid and see if it behaves normally. If it does, upgrade glibc again, restart squid again and confirm that it's again misbehaving. I can't easily do that check myself as my home network is IPv6 only and so I can't possibly be affected by this bug as all my squid servers run in IPv6-only mode (and are still all working as expected). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1547640/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
** Package changed: squid (Ubuntu) => squid3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1547640/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1546788] Re: Fresh install of Postfix 3.0.3-1~build1 will not start with instance conflict error
Fixed in 3.0.3-2 ** Changed in: postfix (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1546788 Title: Fresh install of Postfix 3.0.3-1~build1 will not start with instance conflict error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1546788/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1538198] Re: python in xenial cloud image
Fixed in 3.0.3-1 ** Changed in: postfix (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1538198 Title: python in xenial cloud image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1538198/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547910] Re: package libhcrypto4-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to install/upgrade: package libhcrypto4-heimdal:i386 is already installed and configured
*** This bug is a duplicate of bug 1407757 *** https://bugs.launchpad.net/bugs/1407757 ** This bug has been marked a duplicate of bug 1407757 multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1547910 Title: package libhcrypto4-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to install/upgrade: package libhcrypto4-heimdal:i386 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1547910/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547927] [NEW] LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS
Public bug reported: Tested with vivid and wily... also logged with openldap as http://www.openldap.org/its/index.cgi/Incoming?id=8374 The handling of the LDAP_OPT_X_TLS_REQUIRE_CERT option appears to be different between servers accessed via ldaps:// and ldap:// (plus STARTTLS) URIs. When accessing server with a self-signed certificate, the results are: ldaps:// neverOK hard Error: can't contact LDAP server demand Error: can't contact LDAP server allowOK try Error: can't contact LDAP server ldap:// plus explicit ldap_start_tls_s() neverOK hard OK demand OK allowOK try OK ** Affects: openldap (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1547927 Title: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1547927/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435157] Re: runtime-gdb.py incompatible version with gdb
14.10 is EOL ** Changed in: golang (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1435157 Title: runtime-gdb.py incompatible version with gdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1435157/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
Does someone know yet what happened? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1547640/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
On my 14.04 LTS system the workaround was to add 'dns_v4_first on' to /etc/maas/maas-proxy.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1547640/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547910] Re: package libhcrypto4-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to install/upgrade: package libhcrypto4-heimdal:i386 is already installed and configured
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1547910 Title: package libhcrypto4-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to install/upgrade: package libhcrypto4-heimdal:i386 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1547910/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547910] [NEW] package libhcrypto4-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to install/upgrade: package libhcrypto4-heimdal:i386 is already installed and configured
Public bug reported: Trying to install World of warships via PlayOnLinux when this problem occured ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libhcrypto4-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CrashReports: 600:0:115:153451:2016-02-20 16:48:41.722852706 +0100:2016-02-20 16:48:42.722852706 +0100:/var/crash/libasn1-8-heimdal:i386.0.crash 600:0:115:153455:2016-02-20 16:48:41.762852430 +0100:2016-02-20 16:48:42.762852430 +0100:/var/crash/libhcrypto4-heimdal:i386.0.crash 600:0:115:153453:2016-02-20 16:48:41.670852899 +0100:2016-02-20 16:48:42.670852899 +0100:/var/crash/libroken18-heimdal:i386.0.crash Date: Sat Feb 20 16:48:42 2016 DuplicateSignature: package:libhcrypto4-heimdal:i386:1.6~rc2+dfsg-10ubuntu1:package libhcrypto4-heimdal:i386 is already installed and configured ErrorMessage: package libhcrypto4-heimdal:i386 is already installed and configured InstallationDate: Installed on 2015-12-21 (60 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: heimdal Title: package libhcrypto4-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to install/upgrade: package libhcrypto4-heimdal:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 need-duplicate-check wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1547910 Title: package libhcrypto4-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to install/upgrade: package libhcrypto4-heimdal:i386 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1547910/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1362766] Re: ConnectionFailed: Connection to XXXXXX failed: 'HTTPSConnectionPool' object has no attribute 'insecure'
** Changed in: nova Status: Incomplete => Invalid ** Changed in: python-neutronclient Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-glanceclient in Ubuntu. https://bugs.launchpad.net/bugs/1362766 Title: ConnectionFailed: Connection to XX failed: 'HTTPSConnectionPool' object has no attribute 'insecure' To manage notifications about this bug go to: https://bugs.launchpad.net/keystonemiddleware/+bug/1362766/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547858] [NEW] Cannot switch back from dual-screen to single-screen 2:10.0.0-3000743-3ubuntu1
Public bug reported: Guest: Ubuntu xenial latest Host: VMWare: 12.1 Pro, Windows 8.1 Pro Expected behavior (from vmware-tools) -Cycle multiple monitors button: toggles dualscreen, singlescreen mode -Exit fullscreen mode: if dualscreen is activated, then it swithes back automatically to singlescreen, then exits fullscreen mode Experienced faulty behavior (with open-vm-tools-desktop) -Cycle multiple monitors: single to dual: OK. Dual to single: the content of the secondary display freezes, any mouse action there is committed on the primary display using the same mouse position. -Exit fullscreen mode: it exits from fullscreen, but remains dualscreen, if it was in that mode. Thanks, Balint ** Affects: open-vm-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1547858 Title: Cannot switch back from dual-screen to single-screen 2:10.0.0-3000743-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1547858/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547854] [NEW] package amavisd-new 1:2.10.1-2ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Public bug reported: Lendo listas de pacotes... Pronto Construindo árvore de dependências... 50Construindo árvore de dependências... 50Construindo árvore de dependências Lendo informação de estado... Pronto Calculando atualização... Pronto Os pacotes a seguir serão mantidos em suas versões atuais: usb-modeswitch-data 0 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 1 não atualizados. 1 pacotes não totalmente instalados ou removidos. Depois desta operação, 0 B adicionais de espaço em disco serão usados. Você quer continuar? [S/n] Configurando amavisd-new (1:2.10.1-2ubuntu1) ... Creating/updating amavis user account... Job for amavis.service failed because the control process exited with error code. See "systemctl status amavis.service" and "journalctl -xe" for details. invoke-rc.d: initscript amavis, action "start" failed. dpkg: erro ao processar o pacote amavisd-new (--configure): sub-processo script post-installation instalado retornou estado de saída de erro 1 Erros foram encontrados durante o processamento de: amavisd-new ProblemType: Package DistroRelease: Ubuntu 16.04 Package: amavisd-new 1:2.10.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Feb 20 10:08:00 2016 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-02-08 (11 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: amavisd-new Title: package amavisd-new 1:2.10.1-2ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: amavisd-new (Ubuntu) Importance: Undecided Assignee: william (tree-yellow60) Status: New ** Tags: amd64 apport-package xenial ** Changed in: amavisd-new (Ubuntu) Assignee: (unassigned) => william (tree-yellow60) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in Ubuntu. https://bugs.launchpad.net/bugs/1547854 Title: package amavisd-new 1:2.10.1-2ubuntu1 failed to install/upgrade: sub- processo script post-installation instalado retornou estado de saída de erro 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1547854/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547853] [NEW] commission fails after swapping HDD
Public bug reported:
maas 1.10.0+bzr4578-0ubuntu2
After commissioning the node, I've replaced its HDD.
Now commission fails with this error:
b'{"__all__": ["Block device with this Node and Name already exists."]}'
This happens when uploading 00-maas-07-block-devices.out.
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1547853
Title:
commission fails after swapping HDD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1547853/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547801] Re: package sa-compile 3.4.1-3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 25
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1547801 Title: package sa-compile 3.4.1-3 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1547801/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547801] [NEW] package sa-compile 3.4.1-3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 25
Public bug reported: after an upgrade of 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sa-compile 3.4.1-3 ProcVersionSignature: Ubuntu 3.13.0-78.122-generic 3.13.11-ckt33 Uname: Linux 3.13.0-78-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Sat Feb 20 09:18:26 2016 DuplicateSignature: package:sa-compile:3.4.1-3:le sous-processus script post-installation installé a retourné une erreur de sortie d'état 25 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 25 InstallationDate: Installed on 2015-06-10 (254 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: spamassassin Title: package sa-compile 3.4.1-3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 25 UpgradeStatus: Upgraded to xenial on 2016-02-19 (0 days ago) ** Affects: spamassassin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1547801 Title: package sa-compile 3.4.1-3 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1547801/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
