[Touch-packages] [Bug 1911637] Re: Another app is currently holding the xtables lock
Patch from https://bugs.launchpad.net/ufw/+bug/1923079 which is a dup ** Patch added: "status-wait-flag.patch" https://bugs.launchpad.net/ufw/+bug/1911637/+attachment/5526213/+files/status-wait-flag.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1911637 Title: Another app is currently holding the xtables lock Status in ufw: Triaged Status in ufw package in Ubuntu: Confirmed Status in ufw package in Debian: New Bug description: Version: ufw 0.36 (via Debian buster 0.36-1 deb-package) I'm using ufw together with fail2ban, and often I get an error while fail2ban is trying to ban an ip: ``` ERROR: initcaps [Errno 2] Another app is currently holding the xtables lock. Perhaps you want to use the -w option? ``` it seems that in utils.py, get_netfilter_capabilities(...) iptables is called without "-w" flag to wait for the table lock perhaps the checks should include this parameter to avoid leaving temporary tables behind (and breaking fail2ban, but thats a different story ...)? To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1911637/+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 1393729] Re: package avahi-daemon 0.6.31-4ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
The same thing happens with 0.6.32~rc+dfsg-1ubuntu2.1 As a work around running `systemctl disable avahi-daemon.service` before the upgrade then `systemctl enable avahi-daemon.service` after the upgrade resolves the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1393729 Title: package avahi-daemon 0.6.31-4ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in avahi package in Ubuntu: Confirmed Bug description: Updating a Vivid Vervet system (on Virtual Box v. 4.3.18) by running sudo apt-get update && sudo apt-get dist-upgrade at TTY1. Several packages where successfully upgraded. The only error I got was with avahi-daemon getting the following: Preparing to unpack .../avahi-daemon_0.6.31-4ubuntu4_i386.deb ... Job for avahi-daemon.service canceled. invoke-rc.d: initscript avahi-daemon, action "stop" failed. dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... Job for avahi-daemon.service canceled. invoke-rc.d: initscript avahi-daemon, action "stop" failed. dpkg: error processing archive /var/cache/apt/archives/avahi-daemon_0.6.31-4ubuntu4_i386.deb (--unpack): subprocess new pre-removal script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: avahi-daemon 0.6.31-4ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 Date: Tue Nov 18 09:27:13 2014 DuplicateSignature: package:avahi-daemon:0.6.31-4ubuntu3:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-07-15 (125 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140506) SourcePackage: avahi Title: package avahi-daemon 0.6.31-4ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1393729/+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 1589005] Re: After update DNS work unstable
I had an issue that sounds like this, after disconnecting from an OpenVPN session my DNS would fail, killing dnsmasq and restarting network manager would resolve the problem. To fix it I removed all network interfaces (lan/wifi/vpn etc) from network manager, rebooted, then re-added the interfaces, the problem appears to have gone away. Hopefully others find this helpful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1589005 Title: After update DNS work unstable Status in network-manager package in Ubuntu: Confirmed Bug description: Today I have updated network-manager from update repo and chrome have started get err_name_resolution_failed apt started get network errors. W: Failed to fetch http://by.archive.ubuntu.com/ubuntu/pool/main/n/network-manager/network-manager_1.1.93-0ubuntu4_amd64.deb Temporary failure resolving 'by.archive.ubuntu.com' I got same error when previously update network-manager from ubuntu- proposed, so I think this packet with regression moved to normal update. workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and install it using sudo dpkg -i network-manager_1.1.93-0ubuntu4_amd64.deb and lock version echo "network-manager hold" | sudo dpkg --set-selections "apt update" going to show network-manager as upgradable but "apt upgrage" going to ignore it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 4 01:39:17 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-05-01 (33 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.100.1 dev enp8s0 proto static metric 100 169.254.0.0/16 dev enp8s0 scope link metric 1000 192.168.100.0/24 dev enp8s0 proto kernel scope link src 192.168.100.9 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Проводное соединение 1 34318290-4c71-4b1f-9154-d0f134b91440 802-3-ethernet 1464993435 Sat 04 Jun 2016 01:37:15 MSK yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 yes enp8s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 HUAWEI-KpW2 1 8087b7e0-51dc-43c4-8928-4d03c85a5762 802-11-wireless 1464546384 Sun 29 May 2016 21:26:24 MSK yes 0 no/org/freedesktop/NetworkManager/Settings/1 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp8s0 ethernet connected/org/freedesktop/NetworkManager/Devices/1 Проводное соединение 1 34318290-4c71-4b1f-9154-d0f134b91440 /org/freedesktop/NetworkManager/ActiveConnection/0 wlp9s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589005/+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