[Touch-packages] [Bug 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress
I confirm the fix works for Bionic. ** 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1820886 Title: Potential inconsistency due to system halt/reboot being allowed when package installation in progress Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] 1. User1 at Ubuntu box issues "sudo apt-get upgrade"; 2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI; 3. System reboots and potentially turns into an inconsistent state. [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+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 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress
** No longer affects: landscape-client ** Description changed: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] Scenario with Landscape: 1. Upgrade triggered from Landscape 2. User at Ubuntu Desktop reboots the box using the GUI 3. System reboots and potentially turns into an inconsistent state Scenario w/o Landscape: 1. User1 at Ubuntu Server issues "sudo apt-get upgrade" 2. User2 at Ubuntu Server issues "shutdown -r" 3. System reboots and potentially turns into an inconsistent state [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. - - As a Plan B, an Ubuntu Server/Desktop with the Landscape Client - installed, should at least display warning the users that packages are - being installed. ** Description changed: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] - Scenario with Landscape: - 1. Upgrade triggered from Landscape - 2. User at Ubuntu Desktop reboots the box using the GUI - 3. System reboots and potentially turns into an inconsistent state - - Scenario w/o Landscape: - 1. User1 at Ubuntu Server issues "sudo apt-get upgrade" - 2. User2 at Ubuntu Server issues "shutdown -r" - 3. System reboots and potentially turns into an inconsistent state + 1. User1 at Ubuntu box issues "sudo apt-get upgrade"; + 2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI; + 3. System reboots and potentially turns into an inconsistent state. [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1820886 Title: Potential inconsistency due to system halt/reboot being allowed when package installation in progress Status in apt package in Ubuntu: New Bug description: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] 1. User1 at Ubuntu box issues "sudo apt-get upgrade"; 2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI; 3. System reboots and potentially turns into an inconsistent state. [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+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 1820886] [NEW] Potential inconsistency due to system halt/reboot being allowed when package installation in progress
Public bug reported: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] Scenario with Landscape: 1. Upgrade triggered from Landscape 2. User at Ubuntu Desktop reboots the box using the GUI 3. System reboots and potentially turns into an inconsistent state Scenario w/o Landscape: 1. User1 at Ubuntu Server issues "sudo apt-get upgrade" 2. User2 at Ubuntu Server issues "shutdown -r" 3. System reboots and potentially turns into an inconsistent state [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. As a Plan B, an Ubuntu Server/Desktop with the Landscape Client installed, should at least display warning the users that packages are being installed. ** Affects: landscape-client Importance: Undecided Status: New ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: sts ** Also affects: landscape-client Importance: Undecided Status: New ** Summary changed: - Inhibit system halt when package installation in progress + System halt/reboot is allowed when package installation in progress ** Summary changed: - System halt/reboot is allowed when package installation in progress + Potential inconsistency due to system halt/reboot being allowed when package installation in progress ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1820886 Title: Potential inconsistency due to system halt/reboot being allowed when package installation in progress Status in Landscape Client: New Status in apt package in Ubuntu: New Bug description: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] Scenario with Landscape: 1. Upgrade triggered from Landscape 2. User at Ubuntu Desktop reboots the box using the GUI 3. System reboots and potentially turns into an inconsistent state Scenario w/o Landscape: 1. User1 at Ubuntu Server issues "sudo apt-get upgrade" 2. User2 at Ubuntu Server issues "shutdown -r" 3. System reboots and potentially turns into an inconsistent state [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. As a Plan B, an Ubuntu Server/Desktop with the Landscape Client installed, should at least display warning the users that packages are being installed. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1820886/+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 1812696] Re: APT doc and manpage uses wrong ubuntu-codename
Package: apt-1.6.10 Series: Bionic OS: Ubuntu 18.04.1 LTS Bug fix verified with success. Package: apt-1.2.31 Series: Xenial OS: Ubuntu 16.04.5 LTS Bug fix verified with success. ** Tags removed: verification-needed-bionic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1812696 Title: APT doc and manpage uses wrong ubuntu-codename Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] APT documentation/example/manpages isn't referencing the current release which could be misleading for certain users. --- APT src code: --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Xenial and late in APT points to 'trusty or 'xenial' which generate the doc example & manpage with the wrong release instead of the actual ubuntu-codename. APT in Xenial point to 'trusty'. APT in Bionic and late to 'xenial' It also affect the man page: Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html [Test Case] With Xenial and late: * Look sources.list(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html * Look apt_preferences(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html * Look /usr/share/doc/apt/examples/sources.list $ lsb_release -cs bionic $ cat /usr/share/doc/apt/examples/sources.list # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu xenial main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial main restricted deb http://security.ubuntu.com/ubuntu xenial-security main restricted deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted deb http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted -- You'll notice they all point to the wrong release. While we understand it's not a "bug' and only a reference/example... I think it's for the best interest of all if the examples/manpage reference the current release. [Regression Potential] * None, it only affect documentation/examples and manpages. No behavior change in the APT code. [Other Info] [Original Description] From APT src code : --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. * ./doc/sources.list.5.xml --- %aptverbatiment; --- It also seems to affect the man page by mentionning 'xenial'. Example took from Bionic:
[Touch-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network
This bug also appeared to me after upgrading to 14.10. Network Manager doesn't connect automatically after boot or after resume from suspend. I followed the previous suggestion (enable All users may connect to this network in the wifi connection setting) and it worked for me. Curiously, I made a few tests and if after enable that option I disable it again Network Manager still reconnects after resume from suspend (but not after reboot). -- 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/1354924 Title: Networkmanager does not autoconnect to wireless network Status in “network-manager” package in Ubuntu: Confirmed Bug description: When adding a net wireless network and enable connect automatically' networkmanager does not automatically connect to the network wenever possible. I'm running kubuntu 14.10 daily. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 10 21:30:03 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-11 (29 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710) IpRoute: default via 192.168.0.2 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.213 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+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
