[Touch-packages] [Bug 1921766] Re: Output device not remembered after connecting/disconnecting another
So I did look at those options, but disabling them did not provide the experience I was looking for, and required me to do as much or more manual switching of audio devices. To be clear, I don't want to disable the functionality that these options provide. I am happy with the audio switching to hotplug devices (such as my headphones) automatically when they connect, and I'm happy with the audio switching to new ports as well. This bug is with the behavior of switching _back_ to the original device when a hotplug device disconnects. It should remember the original device, or at least allow me to set a default to switch back to, instead of deciding for itself. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1921766 Title: Output device not remembered after connecting/disconnecting another Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 20.10 running pulseaudio version 13.99.2 is my daily driver for development work. I run it on a Lenovo X1 Carbon 8th Generation connected to dual monitors via a Lenovo dock. Both monitors are capable of outputting sound via HDMI. I use bluetooth headphones frequently with my Ubuntu 20.10 system, but I don't leave them on -- I turn them on and off as needed for Zoom calls. When I'm not on a call, however, I prefer to use my laptop's speakers for audio -- not my monitor speakers. Turning the bluetooth headphones on works fine, they connect and pulseaudio correctly identifies the new connection and switches to the headphones as the audio device. However, when I turn the headphones off, pulseaudio always selects an HDMI audio device as the sound device to use, not the internal speaker device that I was using prior to turning on the headphones. I must manually open Sound Settings and select the speaker device every time I turn my headphones off. My expectation is that the device I was using prior to connecting the headphones is remembered and switched back to by default after I disconnect my bluetooth headphones. I've tried using the pavucontrol app to disable the HDMI audio devices, but the hardware device disable settings are not granular enough to let me target the HDMI devices independently of the speaker device. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1921766/+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 1921766] [NEW] Output device not remembered after connecting/disconnecting another
Public bug reported: Ubuntu 20.10 running pulseaudio version 13.99.2 is my daily driver for development work. I run it on a Lenovo X1 Carbon 8th Generation connected to dual monitors via a Lenovo dock. Both monitors are capable of outputting sound via HDMI. I use bluetooth headphones frequently with my Ubuntu 20.10 system, but I don't leave them on -- I turn them on and off as needed for Zoom calls. When I'm not on a call, however, I prefer to use my laptop's speakers for audio -- not my monitor speakers. Turning the bluetooth headphones on works fine, they connect and pulseaudio correctly identifies the new connection and switches to the headphones as the audio device. However, when I turn the headphones off, pulseaudio always selects an HDMI audio device as the sound device to use, not the internal speaker device that I was using prior to turning on the headphones. I must manually open Sound Settings and select the speaker device every time I turn my headphones off. My expectation is that the device I was using prior to connecting the headphones is remembered and switched back to by default after I disconnect my bluetooth headphones. I've tried using the pavucontrol app to disable the HDMI audio devices, but the hardware device disable settings are not granular enough to let me target the HDMI devices independently of the speaker device. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1921766 Title: Output device not remembered after connecting/disconnecting another Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 20.10 running pulseaudio version 13.99.2 is my daily driver for development work. I run it on a Lenovo X1 Carbon 8th Generation connected to dual monitors via a Lenovo dock. Both monitors are capable of outputting sound via HDMI. I use bluetooth headphones frequently with my Ubuntu 20.10 system, but I don't leave them on -- I turn them on and off as needed for Zoom calls. When I'm not on a call, however, I prefer to use my laptop's speakers for audio -- not my monitor speakers. Turning the bluetooth headphones on works fine, they connect and pulseaudio correctly identifies the new connection and switches to the headphones as the audio device. However, when I turn the headphones off, pulseaudio always selects an HDMI audio device as the sound device to use, not the internal speaker device that I was using prior to turning on the headphones. I must manually open Sound Settings and select the speaker device every time I turn my headphones off. My expectation is that the device I was using prior to connecting the headphones is remembered and switched back to by default after I disconnect my bluetooth headphones. I've tried using the pavucontrol app to disable the HDMI audio devices, but the hardware device disable settings are not granular enough to let me target the HDMI devices independently of the speaker device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1921766/+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 1888575] Re: Split motd-news config into a new package
All parts of case k) verified by repeating the steps described above against -proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Status in livecd-rootfs source package in Xenial: Fix Committed Status in ubuntu-meta source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Released Status in livecd-rootfs source package in Bionic: Invalid Status in ubuntu-meta source package in Bionic: Fix Released Status in base-files source package in Focal: Fix Released Status in livecd-rootfs source package in Focal: Invalid Status in ubuntu-meta source package in Focal: Fix Released Status in base-files source package in Groovy: Fix Released Status in livecd-rootfs source package in Groovy: Invalid Status in ubuntu-meta source package in Groovy: Fix Released Bug description: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains disabled j) Perform a release upgrade from the previous ubuntu release to the one being tested while having ubuntu-server NOT installed (or use a desktop install). At the end, motd-news should be disabled. Verify with: $ sudo /etc/update-motd.d/50-motd-news --force $ (no output) k) Test that supporting changes for xenial are in place: i) verify grub-legacy-ec2 is not in the xenial server seed ii) verify that the rootfs manifest built from the ubuntu-cpc project contains the ubuntu-server package iii) verify that images built from the ubuntu-cpc project which purge grub-legacy-ec2 have retained ubuntu-server iv) verify that the base ubuntu-cpc image continues to have grub-legacy-ec2 installed. [Regression Potential] This update is about config file ownership transfer: /e/d/motd-news belonged to base-files, now it belongs to motd-news-config. We tried to handle two important cases here: a) /e/d/motd-news config was changed while it belonged to base-files. For example, an user could have set ENABLED=0. We need to transfer that change to the motd-news-config package when it is inst
[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package
Ok, I wasn't building from -proposed, I'll try again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Status in livecd-rootfs source package in Xenial: Fix Committed Status in ubuntu-meta source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Released Status in livecd-rootfs source package in Bionic: Invalid Status in ubuntu-meta source package in Bionic: Fix Released Status in base-files source package in Focal: Fix Released Status in livecd-rootfs source package in Focal: Invalid Status in ubuntu-meta source package in Focal: Fix Released Status in base-files source package in Groovy: Fix Released Status in livecd-rootfs source package in Groovy: Invalid Status in ubuntu-meta source package in Groovy: Fix Released Bug description: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains disabled j) Perform a release upgrade from the previous ubuntu release to the one being tested while having ubuntu-server NOT installed (or use a desktop install). At the end, motd-news should be disabled. Verify with: $ sudo /etc/update-motd.d/50-motd-news --force $ (no output) k) Test that supporting changes for xenial are in place: i) verify grub-legacy-ec2 is not in the xenial server seed ii) verify that the rootfs manifest built from the ubuntu-cpc project contains the ubuntu-server package iii) verify that images built from the ubuntu-cpc project which purge grub-legacy-ec2 have retained ubuntu-server iv) verify that the base ubuntu-cpc image continues to have grub-legacy-ec2 installed. [Regression Potential] This update is about config file ownership transfer: /e/d/motd-news belonged to base-files, now it belongs to motd-news-config. We tried to handle two important cases here: a) /e/d/motd-news config was changed while it belonged to base-files. For example, an user could have set ENABLED=0. We need to transfer that change to the motd-news-config package when it is installed, otherwise this SRU would j
[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package
My initial guess at why this has failed is that the ubuntu-server package appears to still depend on grub-legacy-ec2 [1]. [1] https://packages.ubuntu.com/xenial/ubuntu-server -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Status in livecd-rootfs source package in Xenial: Fix Committed Status in ubuntu-meta source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Released Status in livecd-rootfs source package in Bionic: Invalid Status in ubuntu-meta source package in Bionic: Fix Released Status in base-files source package in Focal: Fix Released Status in livecd-rootfs source package in Focal: Invalid Status in ubuntu-meta source package in Focal: Fix Released Status in base-files source package in Groovy: Fix Released Status in livecd-rootfs source package in Groovy: Invalid Status in ubuntu-meta source package in Groovy: Fix Released Bug description: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains disabled j) Perform a release upgrade from the previous ubuntu release to the one being tested while having ubuntu-server NOT installed (or use a desktop install). At the end, motd-news should be disabled. Verify with: $ sudo /etc/update-motd.d/50-motd-news --force $ (no output) k) Test that supporting changes for xenial are in place: i) verify grub-legacy-ec2 is not in the xenial server seed ii) verify that the rootfs manifest built from the ubuntu-cpc project contains the ubuntu-server package iii) verify that images built from the ubuntu-cpc project which purge grub-legacy-ec2 have retained ubuntu-server iv) verify that the base ubuntu-cpc image continues to have grub-legacy-ec2 installed. [Regression Potential] This update is about config file ownership transfer: /e/d/motd-news belonged to base-files, now it belongs to motd-news-config. We tried to handle two important cases here: a) /e/d/motd-news config was changed while it belonged to base-files. For example, an user could have set ENA
[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package
Also as to verification of k.i), I've verified that the "deployed" server seed [1] matches the seed configuration in VCS linked in the last comment. [1] https://people.canonical.com/~ubuntu- archive/seeds/ubuntu.xenial/server -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Status in livecd-rootfs source package in Xenial: Fix Committed Status in ubuntu-meta source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Released Status in livecd-rootfs source package in Bionic: Invalid Status in ubuntu-meta source package in Bionic: Fix Released Status in base-files source package in Focal: Fix Released Status in livecd-rootfs source package in Focal: Invalid Status in ubuntu-meta source package in Focal: Fix Released Status in base-files source package in Groovy: Fix Released Status in livecd-rootfs source package in Groovy: Invalid Status in ubuntu-meta source package in Groovy: Fix Released Bug description: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains disabled j) Perform a release upgrade from the previous ubuntu release to the one being tested while having ubuntu-server NOT installed (or use a desktop install). At the end, motd-news should be disabled. Verify with: $ sudo /etc/update-motd.d/50-motd-news --force $ (no output) k) Test that supporting changes for xenial are in place: i) verify grub-legacy-ec2 is not in the xenial server seed ii) verify that the rootfs manifest built from the ubuntu-cpc project contains the ubuntu-server package iii) verify that images built from the ubuntu-cpc project which purge grub-legacy-ec2 have retained ubuntu-server iv) verify that the base ubuntu-cpc image continues to have grub-legacy-ec2 installed. [Regression Potential] This update is about config file ownership transfer: /e/d/motd-news belonged to base-files, now it belongs to motd-news-config. We tried to handle two important cases here: a) /e/d/motd-news config was changed while it belonged to b
[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package
My attempts to verify test case k) seem to indicate there is still a problem somewhere. I've verified i) that grub-legacy-ec2 is no longer in the server seed [1] iv) that the livecd.ubuntu-cpc.manifest contains grub-legacy-ec2 and ubuntu-server. However, ii) the rootfs manifest has not retained ubuntu-server iii) cpc "secret sauce" hooks which purge grub-legacy-ec2 have not retained ubuntu-server. The failure of ii) occurred in a livefs-build of the ubuntu-cpc project in the xenial branch livecd-rootfs at version 2.408.61 (02ea8c93). The failure of iii) occurred in a build of CPC "secret sauce" hooks using the Ubuntu Old Fashioned tool [2] and the same branch/revision of livecd-rootfs described above. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/tree/server?h=xenial [2] https://github.com/chrisglass/ubuntu-old-fashioned -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Status in livecd-rootfs source package in Xenial: Fix Committed Status in ubuntu-meta source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Released Status in livecd-rootfs source package in Bionic: Invalid Status in ubuntu-meta source package in Bionic: Fix Released Status in base-files source package in Focal: Fix Released Status in livecd-rootfs source package in Focal: Invalid Status in ubuntu-meta source package in Focal: Fix Released Status in base-files source package in Groovy: Fix Released Status in livecd-rootfs source package in Groovy: Invalid Status in ubuntu-meta source package in Groovy: Fix Released Bug description: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains disabled j) Perform a release upgrade from the previous ubuntu release to the one being tested while having ubuntu-server NOT installed (or use a desktop install). At the end, motd-news should be disabled. Verify with: $ sudo /etc/update-motd.d/50-motd-news --force $ (no output) k) Test that supporting changes for xenial are in place: i)
[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package
** Description changed: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config-news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd- news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains disabled j) Perform a release upgrade from the previous ubuntu release to the one being tested while having ubuntu-server NOT installed (or use a desktop install). At the end, motd-news should be disabled. Verify with: $ sudo /etc/update-motd.d/50-motd-news --force $ (no output) + + k) Test that supporting changes for xenial are in place: + + i) verify grub-legacy-ec2 is not in the xenial server seed + ii) verify that the rootfs manifest built from the ubuntu-cpc project contains the ubuntu-server package + iii) verify that images built from the ubuntu-cpc project which purge grub-legacy-ec2 have retained ubuntu-server [Regression Potential] This update is about config file ownership transfer: /e/d/motd-news belonged to base-files, now it belongs to motd-news-config. We tried to handle two important cases here: a) /e/d/motd-news config was changed while it belonged to base-files. For example, an user could have set ENABLED=0. We need to transfer that change to the motd-news-config package when it is installed, otherwise this SRU would jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's configure case. b) /e/d/motd-news config file was *removed* while it belonged to base-files. In such a case, a normal upgrade of the package (base-files in this example) would not reinstate the file. Much less this upgrade here, which has an explicit rm_conffile maintscript-helper for it. But the motd-news-config package that could be installed in the transaction would place the default config file back, and the default is ENABLED=1. Thus, a system that had motd-news disabled via removing the config file would now have it re-enabled after the upgrade. This was trickier to handle, and we do it in base-files's postinst and motd-news-config's postinst. The drawback is that in one scenario, where just base-files is upgraded and /e/d/motd-news was manually removed by the user, there will be a /e/d/motd-news.wasremoved leftover empty file (see "other info" below for details). In general, the regression risks here are: - have motd-news enabled again on a system where it was previously disabled. We tried to envision two ways it would have been disabled (set ENABLED=0, and remove the config file). There are probably others - differences i
[Touch-packages] [Bug 1861905] [NEW] New terminal windows appear in the background
Public bug reported: Ubuntu release: 20.04 Focal Fossa Package version: gnome-shell 3.34.3-1ubuntu1, firefox 72.0.2+build1-0ubuntu1 Expected Behavior: new Terminal window would be foregrounded/focused on creation via ctrl-alt-t when another terminal window not already focused Actual Behavior: if Firefox, e.g., is currently selected/focused, ctrl- alt-t produces a Terminal window that is backgrounded (usually behind the Firefox window), along with a pop-up desktop notification stating "Terminal is ready". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20200123 (Ubuntu 9.2.1-25ubuntu1) ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 4 09:19:33 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-29-generic, x86_64: installed nvidia, 435.21, 5.4.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1070] [3842:6173] InstallationDate: Installed on 2018-09-26 (495 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=75a21605-578a-4b4b-ac2e-14e6aa2f5b02 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0505 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX CODE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd11/08/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXCODE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal possible-manual-nvidia-install regression reproducible third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1861905 Title: New terminal windows appear in the background Status in xorg package in Ubuntu: New Bug description: Ubuntu release: 20.04 Focal Fossa Package version: gnome-shell 3.34.3-1ubuntu1, firefox 72.0.2+build1-0ubuntu1 Expected Behavior: new Terminal window would be foregrounded/focused on creation via ctrl-alt-t when another terminal window not already focused Actual Behavior: if Firefox, e.g., is currently selected/focused, ctrl-alt-t produces a Terminal window that is backgrounded (usually behind the Firefox window), along with a pop-up desktop notification stating "Terminal is ready". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode
