[Touch-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
** Patch removed: "pulseaudio_13.99.1-1ubuntu9.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1891461/+attachment/5401382/+files/pulseaudio_13.99.1-1ubuntu9.debdiff -- 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/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: In Progress Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: In Progress Status in alsa-lib source package in Groovy: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: In Progress Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+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 1891565] Re: oss4 does not build on ppc64el on groovy
** Also affects: binutils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1891565
Title:
oss4 does not build on ppc64el on groovy
Status in binutils package in Ubuntu:
New
Status in oss4 package in Ubuntu:
In Progress
Bug description:
When building the focal version of oss4 with groovy version of
binutils, it fails with:
/tmp/ccoZchTf.s: Assembler messages:
/tmp/ccoZchTf.s: Error: invalid attempt to declare external version name as
default in symbol `.snd_pcm_hw_params_set_rate_near@@ALSA_0.9.0rc4'
make[1]: *** [Makefile:16: pcm.lo] Error 1
Downgrading binutils to 2.34-6ubuntu1 fixes the problem. This works
with gcc-9 9.3.0-10ubuntu2. Upgrading to groovy gcc-9 9.3.0-17ubuntu1
will force the upgrade of binutils, so can't be tested with the
working version of binutils. Using the latest version of gcc-9 or
gcc-10 from groovy with the broken binutils is still broken, so a
complete upgrade does not fix the problem.
The following diff does fix the problem with binutils 2.35-2ubuntu1, though:
$ diff -u lib/libsalsa/alsa-symbols.h.old lib/libsalsa/alsa-symbols.h
--- lib/libsalsa/alsa-symbols.h.old 2020-08-13 22:47:28.249358919 +
+++ lib/libsalsa/alsa-symbols.h 2020-08-13 22:43:35.730423956 +
@@ -35,7 +35,7 @@
__asm__ (".symver ." #real ",." #name "@" #version)
# define default_symbol_version(real, name, version) \
__asm__ (".symver " #real "," #name "@@" #version); \
- __asm__ (".symver ." #real ",." #name "@@" #version)
+// __asm__ (".symver ." #real ",." #name "@@" #version)
#else
# define symbol_version(real, name, version) \
__asm__ (".symver " #real "," #name "@" #version)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1891565/+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 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
Repository can be accessed via: git://git.launchpad.net/~ubuntu-audio-dev/pulseaudio git+ssh://git.launchpad.net/~ubuntu-audio-dev/pulseaudio https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio -- 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/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: In Progress Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: In Progress Status in alsa-lib source package in Groovy: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: In Progress Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+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 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
Please also remember to commit to git early. You should have full access... https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/log/?h=ubuntu- focal ** Tags added: focal groovy ** Changed in: pulseaudio (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: alsa-lib (Ubuntu Groovy) Status: Incomplete => New ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: Incomplete => 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/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: In Progress Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: In Progress Status in alsa-lib source package in Groovy: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: In Progress Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions --
[Touch-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
Please remove pulseaudio_13.99.1-1ubuntu9.debdiff from comment #3 because that version already exists. And create a new version 13.99.1-1ubuntu10 rebased on: https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/log/ https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu9 -- 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/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Incomplete Status in alsa-ucm-conf package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: In Progress Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: In Progress Status in alsa-lib source package in Groovy: Incomplete Status in alsa-ucm-conf source package in Groovy: Incomplete Status in pulseaudio source package in Groovy: In Progress Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
** Changed in: pulseaudio (Ubuntu Focal) Status: New => In Progress ** Changed in: pulseaudio (Ubuntu Groovy) Status: Incomplete => In Progress ** Changed in: pulseaudio (Ubuntu Focal) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: pulseaudio (Ubuntu Groovy) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Incomplete Status in alsa-ucm-conf package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: In Progress Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: In Progress Status in alsa-lib source package in Groovy: Incomplete Status in alsa-ucm-conf source package in Groovy: Incomplete Status in pulseaudio source package in Groovy: In Progress Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package
This bug was fixed in the package base-files - 11ubuntu11 --- base-files (11ubuntu11) groovy; urgency=medium * Move the /etc/default/motd-news conffile to the motd-news-config package (LP: #1888575): - d/base-files.maintscript: remove /etc/default/motd-news config file on upgrade - d/control: break on ubuntu-server << 1.453 to force an upgrade if it is installed, which will pull motd-news-config and the conffile back in - d/motd-news-config.postinst: + handle the upgrade case where the motd-news config file was changed while it belonged to base-files + disable motd-news if the config file was removed by hand before the upgrade - d/postinst.in: signal the motd-news-config package if the motd-news config file was removed manually before the upgrade - d/control: new motd-news-config package, carrying the configuration file for the /etc/update-motd.d/50-motd-news script. - d/rules, d/motd-news-config.install: /e/d/motd-news is in the motd-news-config package now -- Andreas Hasenack Mon, 10 Aug 2020 21:02:37 + ** Changed in: base-files (Ubuntu Groovy) Status: In Progress => Fix Released -- 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 ubuntu-meta package in Ubuntu: In Progress Status in base-files source package in Xenial: In Progress Status in ubuntu-meta source package in Xenial: In Progress Status in base-files source package in Bionic: In Progress Status in ubuntu-meta source package in Bionic: In Progress Status in base-files source package in Focal: In Progress Status in ubuntu-meta source package in Focal: In Progress Status in base-files source package in Groovy: Fix Released Status in ubuntu-meta source package in Groovy: In Progress 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 [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
[Touch-packages] [Bug 1891527] Re: systemd unit tests need updates for Linux 5.8 and later
** Changed in: systemd Status: Unknown => New -- 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/1891527 Title: systemd unit tests need updates for Linux 5.8 and later Status in systemd: New Status in systemd package in Ubuntu: New Bug description: Linux 5.8 allows unprivileged creation of whiteout devices, causing a couple of test failures in systemd: == test-fs-util === /* test_chase_symlinks */ /* test_unlink_noerrno */ /* test_readlink_and_make_absolute */ /* test_var_tmp */ /* test_dot_or_dot_dot */ /* test_access_fd */ /* test_touch_file */ Assertion 'mknod(a, 0775 | S_IFBLK, makedev(0, 0)) >= 0' failed at src/test/test-fs-util.c:637, function test_touch_file(). Aborting. FAIL: test-fs-util (code: 134) ... == test-stat-util === Assertion 'stat(path, ) >= 0' failed at src/test/test-stat-util.c:126, function test_device_path_make_canonical_one(). Aborting. FAIL: test-stat-util (code: 134) test-fs-util succeeds in making a character device with major/minor 0,0, and thus assumes it will be able to create other devices, but it cannot. test-stat-util assumes that because /run/systemd/inaccessible/chr exists /run/systemd/inaccessible/blk should also exist, but it does not for the same reason. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1891527/+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
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/389300 -- 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: In Progress Status in ubuntu-meta package in Ubuntu: In Progress Status in base-files source package in Xenial: In Progress Status in ubuntu-meta source package in Xenial: In Progress Status in base-files source package in Bionic: In Progress Status in ubuntu-meta source package in Bionic: In Progress Status in base-files source package in Focal: In Progress Status in ubuntu-meta source package in Focal: In Progress Status in base-files source package in Groovy: In Progress Status in ubuntu-meta source package in Groovy: In Progress 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 [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
[Touch-packages] [Bug 1886572] Re: Remove uptime from the motd-news user agent
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/389300 -- 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/1886572 Title: Remove uptime from the motd-news user agent Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: In Progress Status in base-files source package in Bionic: In Progress Status in base-files source package in Focal: In Progress Bug description: [Impact] The uptime value in the user-agent string sent to the motd-news server is unused and not necessary. It should be removed. [Test Case] Inspect the /etc/update-motd.d/50-motd-news script and verify that uptime is no longer used. Previous version: $ grep uptime /etc/update-motd.d/50-motd-news # Some messages may only be pertinent before or after some amount of uptime read up idle < /proc/uptime uptime="uptime/$up/$idle" USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id" Updated version: $ grep uptime /etc/update-motd.d/50-motd-news (no output) [Regression Potential] The server side, if it were checking this value, could be surprised by this change. [Other Info] N/A [Original Description] I don't why that was included but it shouldn't be. Please remove it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+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 1888572] Re: motd-news: use wget instead of curl
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/389300
--
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/1888572
Title:
motd-news: use wget instead of curl
Status in base-files package in Ubuntu:
Fix Released
Status in base-files source package in Xenial:
In Progress
Status in base-files source package in Bionic:
In Progress
Status in base-files source package in Focal:
In Progress
Bug description:
[Impact]
The motd-news script is using curl, but since that is an optional package,
there is no guarantee that it will be installed. The script correctly checks
for its presence before trying to use it, though, so it won't fail. As we don't
want to add such a dependency to the base-files package, we should switch to
wget, which is standard.
[Test Case]
wget has a different behavior than curl in some areas, one of which is
crucial for the motd-per-cloud feature. While curl will only complain about a
404 from the server if given a specific parameter (-f), wget does that by
default, and needs special handling.
a) With curl, base-files and ubuntu-server installed, first verify motd-news
works:
$ sudo /etc/update-motd.d/50-motd-news --force
* Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
sudo snap install microk8s --channel=1.19/candidate --classic
https://microk8s.io/ has docs and details.
Now remove curl, and retry. It should exit immediately with no output:
$ sudo /etc/update-motd.d/50-motd-news --force
Install the updated base-files package and the new motd-news-config
package from proposed:
$ sudo apt install base-files motd-news-config
Note curl is still not available:
$ curl
Command 'curl' not found, but can be installed with:
sudo apt install curl
Re-run the motd-news script, this time it should produce output again:
$ sudo /etc/update-motd.d/50-motd-news --force
* Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
sudo snap install microk8s --channel=1.19/candidate --classic
https://microk8s.io/ has docs and details.
b) Verify motd-news per cloud remains working.
If you have /usr/bin/cloud-id, copy it to a backup:
sudo cp /usr/bin/cloud-id{,.orig}
Create a new one, per supported cloud. For aws, for example:
echo -e '#!/bin/sh\necho aws' | sudo tee /usr/bin/cloud-id
Confirm by running it:
$ cloud-id
aws
And confirm motd-news keeps working (it might return different content):
$ sudo /etc/update-motd.d/50-motd-news --force
* Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
sudo snap install microk8s --channel=1.19/candidate --classic
https://microk8s.io/ has docs and details.
Repeat for the gce and azure clouds, by changing the cloud-id script
accordingly.
To confirm the right cloud_id is being used, use sh -x and grep for
its output:
$ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1 | grep -wE 'wget
.*cloud_id/[a-z]+'
+ wget --timeout 60 -U wget/1.20.3-1ubuntu1 Ubuntu/20.04.1/LTS
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz
cloud_id/azure -O- --content-on-error https://motd.ubuntu.com
This also verifies again it's using wget instead of curl.
[Regression Potential]
Possible regressions will likely be tied to a difference in behavior between
curl and wget. In fact, one was caught[1] in the development release and the
fix is included here, with a test.
[Other Info]
N/A
1. https://bugs.launchpad.net/bugs/1889117
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1888572/+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 1886050] Re: initramfs-tools 0.137ubuntu10 ADT test failure with linux-5.8 5.8.0-3.4
I'm getting an oops from launchpad trying to attach a debdiff to update the package to fix the problem, so supplying a link instead: https://people.canonical.com/~sforshee/initramfs- tools_0.137ubuntu11.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1886050 Title: initramfs-tools 0.137ubuntu10 ADT test failure with linux-5.8 5.8.0-3.4 Status in initramfs-tools package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/i/initramfs-tools/20200702_083751_cff4d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1886050/+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 1886572] Re: Remove uptime from the motd-news user agent
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/388922 -- 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/1886572 Title: Remove uptime from the motd-news user agent Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: In Progress Status in base-files source package in Bionic: In Progress Status in base-files source package in Focal: In Progress Bug description: [Impact] The uptime value in the user-agent string sent to the motd-news server is unused and not necessary. It should be removed. [Test Case] Inspect the /etc/update-motd.d/50-motd-news script and verify that uptime is no longer used. Previous version: $ grep uptime /etc/update-motd.d/50-motd-news # Some messages may only be pertinent before or after some amount of uptime read up idle < /proc/uptime uptime="uptime/$up/$idle" USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id" Updated version: $ grep uptime /etc/update-motd.d/50-motd-news (no output) [Regression Potential] The server side, if it were checking this value, could be surprised by this change. [Other Info] N/A [Original Description] I don't why that was included but it shouldn't be. Please remove it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+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 1891486] Re: vim ftbfs in focal (armhf, ppc64el)
** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1891486 Title: vim ftbfs in focal (armhf, ppc64el) Status in vim package in Ubuntu: Confirmed Status in vim source package in Focal: New Bug description: seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19801040 https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19801038 --- Executed: 2257 Tests Skipped:31 Tests FAILED: 1 Tests Failures: From test_debugger.vim: Found errors in Test_Debugger(): function RunTheTest[40]..Test_Debugger[157]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..59 line 1: Expected 'No breakpoints defined' but got 'cmd: echo Foo()' function RunTheTest[40]..Test_Debugger[185]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..71 line 1: Expected '19' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[188]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..72 line 1: Expected 'E161: Breakpoint not found: 2' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..73 line 1: Expected 'Entering Debug mode. Type "cont" to continue.' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..74 line 1: Expected 'function Bazz' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..75 line 1: Expected 'line 2: let var1 = 3 + a:var' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[199]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..76 line 1: Expected ' 3 func Bazz line 2' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[199]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..77 line 1: Expected ' 4 expr var3' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..78 line 1: Expected 'Breakpoint in "Bazz" line 5' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..79 line 1: Expected 'Oldval = "''another var''"' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..80 line 1: Expected 'Newval = "''value2''"' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..81 line 1: Expected 'function Bazz' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..82 line 1: Expected 'line 5: catch' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[208]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..83 line 1: Expected 'No breakpoints defined' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..84 line 1: Expected 'Error detected while processing function Bazz:' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..85 line 1: Expected 'line5:' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..86 line 1: Expected 'E475: Invalid argument: abcd' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[215]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..87 line 1: Expected 'E475: Invalid argument: func' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[216]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..88 line 1: Expected 'E475: Invalid argument: func 2' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[217]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..89 line 1: Expected 'E475: Invalid argument: func a()' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[218]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..90 line 1: Expected 'E475: Invalid argument: abcd' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[219]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..91 line 1: Expected 'E475: Invalid argument: func' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[220]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..92 line 1:
[Touch-packages] [Bug 1888572] Re: motd-news: use wget instead of curl
** Description changed:
- The motd-news script is using curl, but since that is an optional
- package, there is no guarantee that it will be installed. The script
- correctly checks for its presence before trying to use it, though, so it
- won't fail. As we don't want to add such a dependency to the base-files
- package, we should switch to wget, which is standard.
+ [Impact]
+ The motd-news script is using curl, but since that is an optional package,
there is no guarantee that it will be installed. The script correctly checks
for its presence before trying to use it, though, so it won't fail. As we don't
want to add such a dependency to the base-files package, we should switch to
wget, which is standard.
+
+ [Test Case]
+ wget has a different behavior than curl in some areas, one of which is
crucial for the motd-per-cloud feature. While curl will only complain about a
404 from the server if given a specific parameter (-f), wget does that by
default, and needs special handling.
+
+ a) With curl, base-files and ubuntu-server installed, first verify motd-news
works:
+ $ sudo /etc/update-motd.d/50-motd-news --force
+
+ * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
+sudo snap install microk8s --channel=1.19/candidate --classic
+
+https://microk8s.io/ has docs and details.
+
+ Now remove curl, and retry. It should exit immediately with no output:
+
+ $ sudo /etc/update-motd.d/50-motd-news --force
+
+ Install the updated base-files package and the new motd-news-config
+ package from proposed:
+
+ $ sudo apt install base-files motd-news-config
+
+ Note curl is still not available:
+ $ curl
+
+ Command 'curl' not found, but can be installed with:
+
+ sudo apt install curl
+
+ Re-run the motd-news script, this time it should produce output again:
+ $ sudo /etc/update-motd.d/50-motd-news --force
+
+ * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
+sudo snap install microk8s --channel=1.19/candidate --classic
+
+https://microk8s.io/ has docs and details.
+
+ b) Verify motd-news per cloud remains working.
+ If you have /usr/bin/cloud-id, copy it to a backup:
+ sudo cp /usr/bin/cloud-id{,.orig}
+
+ Create a new one, per supported cloud. For aws, for example:
+ echo -e '#!/bin/sh\necho aws' | sudo tee /usr/bin/cloud-id
+
+ Confirm by running it:
+ $ cloud-id
+ aws
+
+ And confirm motd-news keeps working (it might return different content):
+ $ sudo /etc/update-motd.d/50-motd-news --force
+
+ * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
+sudo snap install microk8s --channel=1.19/candidate --classic
+
+https://microk8s.io/ has docs and details.
+
+ Repeat for the gce and azure clouds, by changing the cloud-id script
+ accordingly.
+
+ To confirm the right cloud_id is being used, use sh -x and grep for its
+ output:
+
+ $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1 | grep -wE 'wget
.*cloud_id/[a-z]+'
+ + wget --timeout 60 -U wget/1.20.3-1ubuntu1 Ubuntu/20.04.1/LTS
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz
cloud_id/azure -O- --content-on-error https://motd.ubuntu.com
+
+ This also verifies again it's using wget instead of curl.
+
+
+ [Regression Potential]
+ Possible regressions will likely be tied to a difference in behavior between
curl and wget. In fact, one was caught[1] in the development release and the
fix is included here, with a test.
+
+
+ [Other Info]
+ N/A
+
+ 1. https://bugs.launchpad.net/bugs/1889117
--
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/1888572
Title:
motd-news: use wget instead of curl
Status in base-files package in Ubuntu:
Fix Released
Status in base-files source package in Xenial:
In Progress
Status in base-files source package in Bionic:
In Progress
Status in base-files source package in Focal:
In Progress
Bug description:
[Impact]
The motd-news script is using curl, but since that is an optional package,
there is no guarantee that it will be installed. The script correctly checks
for its presence before trying to use it, though, so it won't fail. As we don't
want to add such a dependency to the base-files package, we should switch to
wget, which is standard.
[Test Case]
wget has a different behavior than curl in some areas, one of which is
crucial for the motd-per-cloud feature. While curl will only complain about a
404 from the server if given a specific parameter (-f), wget does that by
default, and needs special handling.
a) With curl, base-files and ubuntu-server installed, first verify motd-news
works:
$ sudo /etc/update-motd.d/50-motd-news --force
* Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
sudo snap install microk8s --channel=1.19/candidate --classic
https://microk8s.io/ has docs and details.
Now remove
[Touch-packages] [Bug 1891486] Re: vim ftbfs in focal (armhf, ppc64el)
** Also affects: vim (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1891486 Title: vim ftbfs in focal (armhf, ppc64el) Status in vim package in Ubuntu: Confirmed Status in vim source package in Focal: New Bug description: seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19801040 https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19801038 --- Executed: 2257 Tests Skipped:31 Tests FAILED: 1 Tests Failures: From test_debugger.vim: Found errors in Test_Debugger(): function RunTheTest[40]..Test_Debugger[157]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..59 line 1: Expected 'No breakpoints defined' but got 'cmd: echo Foo()' function RunTheTest[40]..Test_Debugger[185]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..71 line 1: Expected '19' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[188]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..72 line 1: Expected 'E161: Breakpoint not found: 2' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..73 line 1: Expected 'Entering Debug mode. Type "cont" to continue.' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..74 line 1: Expected 'function Bazz' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..75 line 1: Expected 'line 2: let var1 = 3 + a:var' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[199]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..76 line 1: Expected ' 3 func Bazz line 2' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[199]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..77 line 1: Expected ' 4 expr var3' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..78 line 1: Expected 'Breakpoint in "Bazz" line 5' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..79 line 1: Expected 'Oldval = "''another var''"' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..80 line 1: Expected 'Newval = "''value2''"' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..81 line 1: Expected 'function Bazz' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..82 line 1: Expected 'line 5: catch' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[208]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..83 line 1: Expected 'No breakpoints defined' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..84 line 1: Expected 'Error detected while processing function Bazz:' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..85 line 1: Expected 'line5:' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..86 line 1: Expected 'E475: Invalid argument: abcd' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[215]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..87 line 1: Expected 'E475: Invalid argument: func' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[216]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..88 line 1: Expected 'E475: Invalid argument: func 2' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[217]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..89 line 1: Expected 'E475: Invalid argument: func a()' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[218]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..90 line 1: Expected 'E475: Invalid argument: abcd' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[219]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..91 line 1: Expected 'E475: Invalid argument: func' but got '~\[ occurs 74 times]' function
[Touch-packages] [Bug 1891527] [NEW] systemd unit tests need updates for Linux 5.8 and later
Public bug reported: Linux 5.8 allows unprivileged creation of whiteout devices, causing a couple of test failures in systemd: == test-fs-util === /* test_chase_symlinks */ /* test_unlink_noerrno */ /* test_readlink_and_make_absolute */ /* test_var_tmp */ /* test_dot_or_dot_dot */ /* test_access_fd */ /* test_touch_file */ Assertion 'mknod(a, 0775 | S_IFBLK, makedev(0, 0)) >= 0' failed at src/test/test-fs-util.c:637, function test_touch_file(). Aborting. FAIL: test-fs-util (code: 134) ... == test-stat-util === Assertion 'stat(path, ) >= 0' failed at src/test/test-stat-util.c:126, function test_device_path_make_canonical_one(). Aborting. FAIL: test-stat-util (code: 134) test-fs-util succeeds in making a character device with major/minor 0,0, and thus assumes it will be able to create other devices, but it cannot. test-stat-util assumes that because /run/systemd/inaccessible/chr exists /run/systemd/inaccessible/blk should also exist, but it does not for the same reason. ** Affects: systemd Importance: Unknown Status: Unknown ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/systemd/systemd/issues #16721 https://github.com/systemd/systemd/issues/16721 ** Also affects: systemd via https://github.com/systemd/systemd/issues/16721 Importance: Unknown Status: Unknown -- 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/1891527 Title: systemd unit tests need updates for Linux 5.8 and later Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: Linux 5.8 allows unprivileged creation of whiteout devices, causing a couple of test failures in systemd: == test-fs-util === /* test_chase_symlinks */ /* test_unlink_noerrno */ /* test_readlink_and_make_absolute */ /* test_var_tmp */ /* test_dot_or_dot_dot */ /* test_access_fd */ /* test_touch_file */ Assertion 'mknod(a, 0775 | S_IFBLK, makedev(0, 0)) >= 0' failed at src/test/test-fs-util.c:637, function test_touch_file(). Aborting. FAIL: test-fs-util (code: 134) ... == test-stat-util === Assertion 'stat(path, ) >= 0' failed at src/test/test-stat-util.c:126, function test_device_path_make_canonical_one(). Aborting. FAIL: test-stat-util (code: 134) test-fs-util succeeds in making a character device with major/minor 0,0, and thus assumes it will be able to create other devices, but it cannot. test-stat-util assumes that because /run/systemd/inaccessible/chr exists /run/systemd/inaccessible/blk should also exist, but it does not for the same reason. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1891527/+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 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
After commenting the corresponding lines /lib/udev/hwdb.d/60-keyboard.hwdb out, issuing # systemd-hwdb update and rebooting, the middle slider up/down keys stopped producing any effect completely at least in Firefox (i.e., it got worse). The "Failed to call ..." error is gone from the output of journalctl -b, though. Running evtest and checking event8 produces absolutely no effect for the slider keys. Running evtest and checking event9 produces the following effect for the slider keys up (+) followed by down (-): Event: time 1597336850.366186, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022d Event: time 1597336850.366186, type 1 (EV_KEY), code 418 (KEY_ZOOMIN), value 1 Event: time 1597336850.366186, -- SYN_REPORT Event: time 1597336850.510185, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022d Event: time 1597336850.510185, type 1 (EV_KEY), code 418 (KEY_ZOOMIN), value 0 Event: time 1597336850.510185, -- SYN_REPORT Event: time 1597336851.454182, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022e Event: time 1597336851.454182, type 1 (EV_KEY), code 419 (KEY_ZOOMOUT), value 1 Event: time 1597336851.454182, -- SYN_REPORT Event: time 1597336851.526184, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022e Event: time 1597336851.526184, type 1 (EV_KEY), code 419 (KEY_ZOOMOUT), value 0 Event: time 1597336851.526184, -- SYN_REPORT I'll revert to the prior default setting of /lib/udev/hwdb.d/60-keyboard.hwdb in the meantime. -- 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/1890186 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Status in systemd package in Ubuntu: New Bug description: I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel 5.4.0-42-generic on Dell Latitude E6440. Upon examining the output of journalctl -b, I see this: Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288 Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn acpi driver for receiving events Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument "Invalid argument" means that something goes wrong there, and I don't know what it is. On my laptop, event8 seems to be keyboard-related: $ sudo cat /proc/bus/input/devices | grep -C 5 event8 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-:00:14.0-13.1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9 U: Uniq= H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=107 The issue report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is probably related but marked as a duplicate of a no longer existing issue report (#1750855). The report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415 describes a similar issue for older kernels; the differences pertain to error message, error code, input..., and, opposed to #19 there, I have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine is not a dual-boot machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+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 1891527] Re: systemd unit tests need updates for Linux 5.8 and later
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/amd64/s/systemd/20200812_210502_aa555@/log.gz -- 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/1891527 Title: systemd unit tests need updates for Linux 5.8 and later Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: Linux 5.8 allows unprivileged creation of whiteout devices, causing a couple of test failures in systemd: == test-fs-util === /* test_chase_symlinks */ /* test_unlink_noerrno */ /* test_readlink_and_make_absolute */ /* test_var_tmp */ /* test_dot_or_dot_dot */ /* test_access_fd */ /* test_touch_file */ Assertion 'mknod(a, 0775 | S_IFBLK, makedev(0, 0)) >= 0' failed at src/test/test-fs-util.c:637, function test_touch_file(). Aborting. FAIL: test-fs-util (code: 134) ... == test-stat-util === Assertion 'stat(path, ) >= 0' failed at src/test/test-stat-util.c:126, function test_device_path_make_canonical_one(). Aborting. FAIL: test-stat-util (code: 134) test-fs-util succeeds in making a character device with major/minor 0,0, and thus assumes it will be able to create other devices, but it cannot. test-stat-util assumes that because /run/systemd/inaccessible/chr exists /run/systemd/inaccessible/blk should also exist, but it does not for the same reason. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1891527/+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 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
The attachment "pulseaudio_13.99.1-1ubuntu9.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Incomplete Status in alsa-ucm-conf package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: Incomplete Status in alsa-ucm-conf source package in Groovy: Incomplete Status in pulseaudio source package in Groovy: Incomplete Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to:
[Touch-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu2 --- alsa-ucm-conf (1.2.2-1ubuntu2) groovy; urgency=medium * d/p/0003-ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch * d/p/0004-ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch * d/p/0005-sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch * d/p/0006-ucm.conf-add-support-for-the-kernel-module-name-tree.patch * d/p/0007-sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch * d/p/0008-sof-soundwire-initial-UCM2-version.patch * d/p/0009-sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch * d/p/0010-sof-soundwire-rewrite-for-syntax-3.patch * d/p/0011-HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch * d/p/0012-hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch * d/p/0013-amd-renoir-acp-use-the-machine-driver-s-name-for-top.patch * d/p/0014-amd-renoir-acp-add-syntax-in-the-Linked.patch * d/p/0015-HDA-Intel-only-bind-the-acp-dmic-to-the-soundcard-wi.patch * d/p/0016-Fix-invalid-Regex-Type-in-various-Condition-blocks.patch Make digital mic on the AMD Renoir machines work under gnome desktop (LP: #1889217) -- Hui Wang Thu, 13 Aug 2020 16:18:58 +0200 ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Committed Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch
[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
# udevadm info /dev/input/event9 P: /devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.1/0003:045E:00DB.0003/input/input10/event9 N: input/event9 L: 0 S: input/by-path/pci-:00:14.0-usb-0:13.1:1.1-event-kbd S: input/by-id/usb-Microsoft_Natural®_Ergonomic_Keyboard_4000-if01-event-kbd E: DEVPATH=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.1/0003:045E:00DB.0003/input/input10/event9 E: DEVNAME=/dev/input/event9 E: MAJOR=13 E: MINOR=73 E: SUBSYSTEM=input E: USEC_INITIALIZED=4185161 E: KEYBOARD_KEY_c022d=up E: KEYBOARD_KEY_c022e=down E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_VENDOR=Microsoft E: ID_VENDOR_ENC=Microsoft E: ID_VENDOR_ID=045e E: ID_MODEL=Natural®_Ergonomic_Keyboard_4000 E: ID_MODEL_ENC=Natural®\x20Ergonomic\x20Keyboard\x204000 E: ID_MODEL_ID=00db E: ID_REVISION=0173 E: ID_SERIAL=Microsoft_Natural®_Ergonomic_Keyboard_4000 E: ID_TYPE=hid E: ID_BUS=usb E: ID_USB_INTERFACES=:030101:03: E: ID_USB_INTERFACE_NUM=01 E: ID_USB_DRIVER=usbhid E: ID_PATH=pci-:00:14.0-usb-0:13.1:1.1 E: ID_PATH_TAG=pci-_00_14_0-usb-0_13_1_1_1 E: XKBMODEL=pc105 E: XKBLAYOUT=de E: BACKSPACE=guess E: LIBINPUT_DEVICE_GROUP=3/45e/db:usb-:00:14.0-13 E: DEVLINKS=/dev/input/by-path/pci-:00:14.0-usb-0:13.1:1.1-event-kbd /dev/input/by-id/usb-Microsoft_Natural®_Ergonomic_Keyboard_4000-if01-event-kbd E: TAGS=:power-switch: -- 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/1890186 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Status in systemd package in Ubuntu: New Bug description: I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel 5.4.0-42-generic on Dell Latitude E6440. Upon examining the output of journalctl -b, I see this: Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288 Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn acpi driver for receiving events Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument "Invalid argument" means that something goes wrong there, and I don't know what it is. On my laptop, event8 seems to be keyboard-related: $ sudo cat /proc/bus/input/devices | grep -C 5 event8 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-:00:14.0-13.1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9 U: Uniq= H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=107 The issue report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is probably related but marked as a duplicate of a no longer existing issue report (#1750855). The report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415 describes a similar issue for older kernels; the differences pertain to error message, error code, input..., and, opposed to #19 there, I have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine is not a dual-boot machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+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 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
# evemu-describe /dev/input/event8 # EVEMU 1.3 # Kernel: 5.4.0-42-generic # DMI: dmi:bvnDellInc.:bvrA21:bd02/01/2018:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn02P3T1:rvrA00:cvnDellInc.:ct9:cvr: # Input device name: "Microsoft Natural® Ergonomic Keyboard 4000" # Input device ID: bus 0x03 vendor 0x45e product 0xdb version 0x111 # Supported events: # Event type 0 (EV_SYN) # Event code 0 (SYN_REPORT) # Event code 1 (SYN_CONFIG) # Event code 2 (SYN_MT_REPORT) # Event code 3 (SYN_DROPPED) # Event code 4 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event code 15 (SYN_MAX) # Event type 1 (EV_KEY) # Event code 1 (KEY_ESC) # Event code 2 (KEY_1) # Event code 3 (KEY_2) # Event code 4 (KEY_3) # Event code 5 (KEY_4) # Event code 6 (KEY_5) # Event code 7 (KEY_6) # Event code 8 (KEY_7) # Event code 9 (KEY_8) # Event code 10 (KEY_9) # Event code 11 (KEY_0) # Event code 12 (KEY_MINUS) # Event code 13 (KEY_EQUAL) # Event code 14 (KEY_BACKSPACE) # Event code 15 (KEY_TAB) # Event code 16 (KEY_Q) # Event code 17 (KEY_W) # Event code 18 (KEY_E) # Event code 19 (KEY_R) # Event code 20 (KEY_T) # Event code 21 (KEY_Y) # Event code 22 (KEY_U) # Event code 23 (KEY_I) # Event code 24 (KEY_O) # Event code 25 (KEY_P) # Event code 26 (KEY_LEFTBRACE) # Event code 27 (KEY_RIGHTBRACE) # Event code 28 (KEY_ENTER) # Event code 29 (KEY_LEFTCTRL) # Event code 30 (KEY_A) # Event code 31 (KEY_S) # Event code 32 (KEY_D) # Event code 33 (KEY_F) # Event code 34 (KEY_G) # Event code 35 (KEY_H) # Event code 36 (KEY_J) # Event code 37 (KEY_K) # Event code 38 (KEY_L) # Event code 39 (KEY_SEMICOLON) # Event code 40 (KEY_APOSTROPHE) # Event code 41 (KEY_GRAVE) # Event code 42 (KEY_LEFTSHIFT) # Event code 43 (KEY_BACKSLASH) # Event code 44 (KEY_Z) # Event code 45 (KEY_X) # Event code 46 (KEY_C) # Event code 47 (KEY_V) # Event code 48 (KEY_B) # Event code 49 (KEY_N) # Event code 50 (KEY_M) # Event code 51 (KEY_COMMA) # Event code 52 (KEY_DOT) # Event code 53 (KEY_SLASH) # Event code 54 (KEY_RIGHTSHIFT) # Event code 55 (KEY_KPASTERISK) # Event code 56 (KEY_LEFTALT) # Event code 57 (KEY_SPACE) # Event code 58 (KEY_CAPSLOCK) # Event code 59 (KEY_F1) # Event code 60 (KEY_F2) # Event code 61 (KEY_F3) # Event code 62 (KEY_F4) # Event code 63 (KEY_F5) # Event code 64 (KEY_F6) # Event code 65 (KEY_F7) # Event code 66 (KEY_F8) # Event code 67 (KEY_F9) # Event code 68 (KEY_F10) # Event code 69 (KEY_NUMLOCK) # Event code 70 (KEY_SCROLLLOCK) # Event code 71 (KEY_KP7) # Event code 72 (KEY_KP8) # Event code 73 (KEY_KP9) # Event code 74 (KEY_KPMINUS) # Event code 75 (KEY_KP4) # Event code 76 (KEY_KP5) # Event code 77 (KEY_KP6) # Event code 78 (KEY_KPPLUS) # Event code 79 (KEY_KP1) # Event code 80 (KEY_KP2) # Event code 81 (KEY_KP3) # Event code 82 (KEY_KP0) # Event code 83 (KEY_KPDOT) # Event code 86 (KEY_102ND) # Event code 87 (KEY_F11) # Event code 88 (KEY_F12) # Event code 89 (KEY_RO) # Event code 92 (KEY_HENKAN) # Event code 93 (KEY_KATAKANAHIRAGANA) # Event code 94 (KEY_MUHENKAN) # Event code 95 (KEY_KPJPCOMMA) # Event code 96 (KEY_KPENTER) # Event code 97 (KEY_RIGHTCTRL) # Event code 98 (KEY_KPSLASH) # Event code 99 (KEY_SYSRQ) # Event code 100 (KEY_RIGHTALT) # Event code 102 (KEY_HOME) # Event code 103 (KEY_UP) # Event code 104 (KEY_PAGEUP) # Event code 105 (KEY_LEFT) # Event code 106 (KEY_RIGHT) # Event code 107 (KEY_END) # Event code 108 (KEY_DOWN) # Event code 109 (KEY_PAGEDOWN) # Event code 110 (KEY_INSERT) # Event code 111 (KEY_DELETE) # Event code 113 (KEY_MUTE) # Event code 114 (KEY_VOLUMEDOWN) # Event code 115 (KEY_VOLUMEUP) # Event code 116 (KEY_POWER) # Event code 117 (KEY_KPEQUAL) # Event code 119 (KEY_PAUSE) # Event code 121 (KEY_KPCOMMA) # Event code 122 (KEY_HANGEUL) # Event code 123 (KEY_HANJA) # Event code 124 (KEY_YEN) # Event code 125 (KEY_LEFTMETA) # Event code 126 (KEY_RIGHTMETA) # Event code 127 (KEY_COMPOSE) # Event code 128 (KEY_STOP) # Event code 129 (KEY_AGAIN) # Event code 130 (KEY_PROPS) # Event code 131 (KEY_UNDO) # Event code 132 (KEY_FRONT) # Event code 133 (KEY_COPY) # Event code 134 (KEY_OPEN) # Event code 135 (KEY_PASTE) # Event code 136 (KEY_FIND) # Event code 137 (KEY_CUT) # Event code 138 (KEY_HELP) # Event code 183 (KEY_F13) #
[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
I rebooted once again to ensure that `sudo evtest` returns /dev/input/event8: Microsoft Natural® Ergonomic Keyboard 4000 /dev/input/event9: Microsoft Natural® Ergonomic Keyboard 4000 The results of # udevadm info /dev/input/event8 # udevadm info /dev/input/event9 # evemu-describe /dev/input/event8 # evemu-describe /dev/input/event9 with the original file /lib/udev/hwdb.d/60-keyboard.hwdb will be attached or posted in short. -- 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/1890186 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Status in systemd package in Ubuntu: New Bug description: I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel 5.4.0-42-generic on Dell Latitude E6440. Upon examining the output of journalctl -b, I see this: Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288 Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn acpi driver for receiving events Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument "Invalid argument" means that something goes wrong there, and I don't know what it is. On my laptop, event8 seems to be keyboard-related: $ sudo cat /proc/bus/input/devices | grep -C 5 event8 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-:00:14.0-13.1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9 U: Uniq= H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=107 The issue report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is probably related but marked as a duplicate of a no longer existing issue report (#1750855). The report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415 describes a similar issue for older kernels; the differences pertain to error message, error code, input..., and, opposed to #19 there, I have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine is not a dual-boot machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+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 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
# evemu-describe /dev/input/event9 # EVEMU 1.3 # Kernel: 5.4.0-42-generic # DMI: dmi:bvnDellInc.:bvrA21:bd02/01/2018:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn02P3T1:rvrA00:cvnDellInc.:ct9:cvr: # Input device name: "Microsoft Natural® Ergonomic Keyboard 4000" # Input device ID: bus 0x03 vendor 0x45e product 0xdb version 0x111 # Supported events: # Event type 0 (EV_SYN) # Event code 0 (SYN_REPORT) # Event code 1 (SYN_CONFIG) # Event code 2 (SYN_MT_REPORT) # Event code 3 (SYN_DROPPED) # Event code 4 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event code 15 (SYN_MAX) # Event type 1 (EV_KEY) # Event code 1 (KEY_ESC) # Event code 2 (KEY_1) # Event code 3 (KEY_2) # Event code 4 (KEY_3) # Event code 5 (KEY_4) # Event code 6 (KEY_5) # Event code 7 (KEY_6) # Event code 8 (KEY_7) # Event code 9 (KEY_8) # Event code 10 (KEY_9) # Event code 11 (KEY_0) # Event code 12 (KEY_MINUS) # Event code 13 (KEY_EQUAL) # Event code 14 (KEY_BACKSPACE) # Event code 15 (KEY_TAB) # Event code 16 (KEY_Q) # Event code 17 (KEY_W) # Event code 18 (KEY_E) # Event code 19 (KEY_R) # Event code 20 (KEY_T) # Event code 21 (KEY_Y) # Event code 22 (KEY_U) # Event code 23 (KEY_I) # Event code 24 (KEY_O) # Event code 25 (KEY_P) # Event code 26 (KEY_LEFTBRACE) # Event code 27 (KEY_RIGHTBRACE) # Event code 28 (KEY_ENTER) # Event code 29 (KEY_LEFTCTRL) # Event code 30 (KEY_A) # Event code 31 (KEY_S) # Event code 32 (KEY_D) # Event code 33 (KEY_F) # Event code 34 (KEY_G) # Event code 35 (KEY_H) # Event code 36 (KEY_J) # Event code 37 (KEY_K) # Event code 38 (KEY_L) # Event code 39 (KEY_SEMICOLON) # Event code 40 (KEY_APOSTROPHE) # Event code 41 (KEY_GRAVE) # Event code 42 (KEY_LEFTSHIFT) # Event code 43 (KEY_BACKSLASH) # Event code 44 (KEY_Z) # Event code 45 (KEY_X) # Event code 46 (KEY_C) # Event code 47 (KEY_V) # Event code 48 (KEY_B) # Event code 49 (KEY_N) # Event code 50 (KEY_M) # Event code 51 (KEY_COMMA) # Event code 52 (KEY_DOT) # Event code 53 (KEY_SLASH) # Event code 54 (KEY_RIGHTSHIFT) # Event code 55 (KEY_KPASTERISK) # Event code 56 (KEY_LEFTALT) # Event code 57 (KEY_SPACE) # Event code 58 (KEY_CAPSLOCK) # Event code 59 (KEY_F1) # Event code 60 (KEY_F2) # Event code 61 (KEY_F3) # Event code 62 (KEY_F4) # Event code 63 (KEY_F5) # Event code 64 (KEY_F6) # Event code 65 (KEY_F7) # Event code 66 (KEY_F8) # Event code 67 (KEY_F9) # Event code 68 (KEY_F10) # Event code 69 (KEY_NUMLOCK) # Event code 70 (KEY_SCROLLLOCK) # Event code 71 (KEY_KP7) # Event code 72 (KEY_KP8) # Event code 73 (KEY_KP9) # Event code 74 (KEY_KPMINUS) # Event code 75 (KEY_KP4) # Event code 76 (KEY_KP5) # Event code 77 (KEY_KP6) # Event code 78 (KEY_KPPLUS) # Event code 79 (KEY_KP1) # Event code 80 (KEY_KP2) # Event code 81 (KEY_KP3) # Event code 82 (KEY_KP0) # Event code 83 (KEY_KPDOT) # Event code 85 (KEY_ZENKAKUHANKAKU) # Event code 86 (KEY_102ND) # Event code 87 (KEY_F11) # Event code 88 (KEY_F12) # Event code 89 (KEY_RO) # Event code 90 (KEY_KATAKANA) # Event code 91 (KEY_HIRAGANA) # Event code 92 (KEY_HENKAN) # Event code 93 (KEY_KATAKANAHIRAGANA) # Event code 94 (KEY_MUHENKAN) # Event code 95 (KEY_KPJPCOMMA) # Event code 96 (KEY_KPENTER) # Event code 97 (KEY_RIGHTCTRL) # Event code 98 (KEY_KPSLASH) # Event code 99 (KEY_SYSRQ) # Event code 100 (KEY_RIGHTALT) # Event code 102 (KEY_HOME) # Event code 103 (KEY_UP) # Event code 104 (KEY_PAGEUP) # Event code 105 (KEY_LEFT) # Event code 106 (KEY_RIGHT) # Event code 107 (KEY_END) # Event code 108 (KEY_DOWN) # Event code 109 (KEY_PAGEDOWN) # Event code 110 (KEY_INSERT) # Event code 111 (KEY_DELETE) # Event code 113 (KEY_MUTE) # Event code 114 (KEY_VOLUMEDOWN) # Event code 115 (KEY_VOLUMEUP) # Event code 116 (KEY_POWER) # Event code 117 (KEY_KPEQUAL) # Event code 119 (KEY_PAUSE) # Event code 120 (KEY_SCALE) # Event code 121 (KEY_KPCOMMA) # Event code 122 (KEY_HANGEUL) # Event code 123 (KEY_HANJA) # Event code 124 (KEY_YEN) # Event code 125 (KEY_LEFTMETA) # Event code 126 (KEY_RIGHTMETA) # Event code 127 (KEY_COMPOSE) # Event code 128 (KEY_STOP) # Event code 129 (KEY_AGAIN) # Event code 130 (KEY_PROPS) # Event code 131 (KEY_UNDO) # Event code 132 (KEY_FRONT) # Event code 133 (KEY_COPY) # Event code 134 (KEY_OPEN) # Event code 135
[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
# udevadm info /dev/input/event8 P: /devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9/event8 N: input/event8 L: 0 S: input/by-id/usb-Microsoft_Natural®_Ergonomic_Keyboard_4000-event-kbd S: input/by-path/pci-:00:14.0-usb-0:13.1:1.0-event-kbd E: DEVPATH=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9/event8 E: DEVNAME=/dev/input/event8 E: MAJOR=13 E: MINOR=72 E: SUBSYSTEM=input E: USEC_INITIALIZED=4188709 E: KEYBOARD_KEY_c022d=up E: KEYBOARD_KEY_c022e=down E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_VENDOR=Microsoft E: ID_VENDOR_ENC=Microsoft E: ID_VENDOR_ID=045e E: ID_MODEL=Natural®_Ergonomic_Keyboard_4000 E: ID_MODEL_ENC=Natural®\x20Ergonomic\x20Keyboard\x204000 E: ID_MODEL_ID=00db E: ID_REVISION=0173 E: ID_SERIAL=Microsoft_Natural®_Ergonomic_Keyboard_4000 E: ID_TYPE=hid E: ID_BUS=usb E: ID_USB_INTERFACES=:030101:03: E: ID_USB_INTERFACE_NUM=00 E: ID_USB_DRIVER=usbhid E: ID_PATH=pci-:00:14.0-usb-0:13.1:1.0 E: ID_PATH_TAG=pci-_00_14_0-usb-0_13_1_1_0 E: XKBMODEL=pc105 E: XKBLAYOUT=de E: BACKSPACE=guess E: LIBINPUT_DEVICE_GROUP=3/45e/db:usb-:00:14.0-13 E: DEVLINKS=/dev/input/by-id/usb-Microsoft_Natural®_Ergonomic_Keyboard_4000-event-kbd /dev/input/by-path/pci-:00:14.0-usb-0:13.1:1.0-event-kbd E: TAGS=:power-switch: -- 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/1890186 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Status in systemd package in Ubuntu: New Bug description: I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel 5.4.0-42-generic on Dell Latitude E6440. Upon examining the output of journalctl -b, I see this: Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288 Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn acpi driver for receiving events Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument "Invalid argument" means that something goes wrong there, and I don't know what it is. On my laptop, event8 seems to be keyboard-related: $ sudo cat /proc/bus/input/devices | grep -C 5 event8 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-:00:14.0-13.1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9 U: Uniq= H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=107 The issue report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is probably related but marked as a duplicate of a no longer existing issue report (#1750855). The report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415 describes a similar issue for older kernels; the differences pertain to error message, error code, input..., and, opposed to #19 there, I have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine is not a dual-boot machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+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 1891110] Re: Focal ucf need redirect fixes backported to ensure working with config-package-dev
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ucf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891110 Title: Focal ucf need redirect fixes backported to ensure working with config-package-dev Status in ucf package in Ubuntu: Confirmed Bug description: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+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 1891515] Re: ucf overwrites diverted configuration file breaking unattended upgrades - upstream fix available
*** This bug is a duplicate of bug 1891110 *** https://bugs.launchpad.net/bugs/1891110 ** Changed in: dovecot (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of bug 1891110 Focal ucf need redirect fixes backported to ensure working with config-package-dev -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891515 Title: ucf overwrites diverted configuration file breaking unattended upgrades - upstream fix available Status in ucf: Unknown Status in dovecot package in Ubuntu: Invalid Status in ucf package in Ubuntu: New Bug description: An unattended security upgrade (package dovecot-core) failed, interrupting mailbox service. The cause was ucf replacing a custom configuration file which had been diverted (using dpkg-divert) by a custom configuration package. Excerpt from /var/log/apt/term.log: --- Setting up dovecot-core (1:2.2.33.2-1ubuntu4.6) ... Replacing config file /etc/dovecot/dovecot.conf.custom with new version ucfr: Attempt from package dovecot-core to take /etc/dovecot/dovecot.conf.custom away from package custom-mail-server ucfr: Aborting. dpkg: error processing package dovecot-core (--configure): installed dovecot-core package post-installation script subprocess returned error exit status 4 --- The underlying issue has been fixed upstream in ucf version 3.0040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=43 Affected versions: - Ubuntu 18.04.5 LTS - ucf 3.0038 - Ubuntu 20.04.1 LTS - ucf 3.0038+nmu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ucf/+bug/1891515/+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 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
Please ignore #8: at new boot, the device numbers have changed :-(. Sorry, will post anew in short. -- 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/1890186 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Status in systemd package in Ubuntu: New Bug description: I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel 5.4.0-42-generic on Dell Latitude E6440. Upon examining the output of journalctl -b, I see this: Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288 Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn acpi driver for receiving events Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument "Invalid argument" means that something goes wrong there, and I don't know what it is. On my laptop, event8 seems to be keyboard-related: $ sudo cat /proc/bus/input/devices | grep -C 5 event8 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-:00:14.0-13.1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9 U: Uniq= H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=107 The issue report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is probably related but marked as a duplicate of a no longer existing issue report (#1750855). The report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415 describes a similar issue for older kernels; the differences pertain to error message, error code, input..., and, opposed to #19 there, I have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine is not a dual-boot machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+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 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
With the original file /lib/udev/hwdb.d/60-keyboard.hwdb : # udevadm info /dev/input/event8 P: /devices/platform/lis3lv02d/input/input9/event8 N: input/event8 L: 0 S: input/by-path/platform-lis3lv02d-event E: DEVPATH=/devices/platform/lis3lv02d/input/input9/event8 E: DEVNAME=/dev/input/event8 E: MAJOR=13 E: MINOR=72 E: SUBSYSTEM=input E: USEC_INITIALIZED=4296811 E: ID_INPUT=1 E: ID_INPUT_ACCELEROMETER=1 E: ID_PATH=platform-lis3lv02d E: ID_PATH_TAG=platform-lis3lv02d E: IIO_SENSOR_PROXY_TYPE=input-accel E: SYSTEMD_WANTS=iio-sensor-proxy.service E: LIBINPUT_DEVICE_GROUP=19/0/0:lis3lv02d E: DEVLINKS=/dev/input/by-path/platform-lis3lv02d-event E: TAGS=:systemd: # udevadm info /dev/input/event9 P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4f/LNXVIDEO:00/input/input10/event9 N: input/event9 L: 0 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4f/LNXVIDEO:00/input/input10/event9 E: DEVNAME=/dev/input/event9 E: MAJOR=13 E: MINOR=73 E: SUBSYSTEM=input E: USEC_INITIALIZED=4230143 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXVIDEO:00 E: ID_PATH_TAG=acpi-LNXVIDEO_00 E: XKBMODEL=pc105 E: XKBLAYOUT=de E: BACKSPACE=guess E: LIBINPUT_DEVICE_GROUP=19/0/6:LNXVIDEO/video E: TAGS=:power-switch: # evemu-describe /dev/input/event8 # EVEMU 1.3 # Kernel: 5.4.0-42-generic # DMI: dmi:bvnDellInc.:bvrA21:bd02/01/2018:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn02P3T1:rvrA00:cvnDellInc.:ct9:cvr: # Input device name: "ST LIS3LV02DL Accelerometer" # Input device ID: bus 0x19 vendor product version # Supported events: # Event type 0 (EV_SYN) # Event code 0 (SYN_REPORT) # Event code 1 (SYN_CONFIG) # Event code 2 (SYN_MT_REPORT) # Event code 3 (SYN_DROPPED) # Event code 4 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event code 15 (SYN_MAX) # Event type 3 (EV_ABS) # Event code 0 (ABS_X) # Value -172 # Min -2304 # Max 2304 # Fuzz18 # Flat18 # Resolution 0 # Event code 1 (ABS_Y) # Value -10 # Min -2304 # Max 2304 # Fuzz18 # Flat18 # Resolution 0 # Event code 2 (ABS_Z) # Value 1178 # Min -2304 # Max 2304 # Fuzz18 # Flat18 # Resolution 0 # Properties: N: ST LIS3LV02DL Accelerometer I: 0019 P: 00 00 00 00 00 00 00 00 B: 00 0b 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 02 00 00 00 00 00 00 00 00 B: 03 07 00 00 00 00 00 00 00 B: 04 00 00 00 00 00 00 00 00 B: 05 00 00 00 00 00 00 00 00 B: 11 00 00 00 00 00 00 00 00 B: 12 00 00 00 00 00 00 00 00 B: 14 00 00 00 00 00 00 00 00 B: 15 00 00 00 00 00 00 00 00 B: 15 00 00 00 00 00 00 00 00 A: 00 -2304 2304 18 18 0 A: 01 -2304 2304 18 18 0 A: 02 -2304 2304 18 18 0 # evemu-describe /dev/input/event9 # EVEMU 1.3 # Kernel: 5.4.0-42-generic # DMI: dmi:bvnDellInc.:bvrA21:bd02/01/2018:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn02P3T1:rvrA00:cvnDellInc.:ct9:cvr: # Input device name: "Video Bus" # Input device ID: bus 0x19 vendor product 0x06 version # Supported events: # Event type 0 (EV_SYN) # Event code 0 (SYN_REPORT) # Event code 1 (SYN_CONFIG) # Event code 2 (SYN_MT_REPORT) # Event code 3 (SYN_DROPPED) # Event code 4 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event code 15 (SYN_MAX) # Event type 1 (EV_KEY) # Event code 224 (KEY_BRIGHTNESSDOWN) # Event code 225 (KEY_BRIGHTNESSUP) # Event code 227 (KEY_SWITCHVIDEOMODE) # Event code 241 (KEY_VIDEO_NEXT) # Event code 242 (KEY_VIDEO_PREV) # Event code 243 (KEY_BRIGHTNESS_CYCLE) # Event code 244 (KEY_BRIGHTNESS_AUTO) # Event code 245 (KEY_DISPLAY_OFF) # Properties: N: Video Bus I: 0019 0006 P: 00 00 00 00 00 00 00 00 B: 00 0b 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 0b 00 3e 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00
[Touch-packages] [Bug 1891479] Re: pycurl ftbfs in focal (wait-deps)
** Tags added: block-proposed-focal ** Also affects: pycurl (Ubuntu Focal) Importance: Undecided Status: New ** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1891479 Title: pycurl ftbfs in focal (wait-deps) Status in pycurl package in Ubuntu: Confirmed Status in pycurl source package in Focal: New Bug description: seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19799602 Missing build dependencies: python-sphinx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1891479/+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 1891342] Re: network manager does not auto connect to hidden wifi networks
Thank you for the link. Have attached the TRACE logs from NetworkManager. -- 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/1891342 Title: network manager does not auto connect to hidden wifi networks Status in network-manager package in Ubuntu: Incomplete Bug description: Environment: Fresh installation of Lubuntu 20.04 (it also occurs in a fresh installation of Ubuntu 20.04) Steps to reproduce the situation: 1) Lubuntu -> Network Manager -> Edit Connections -> Add SSID of a hidden WiFi network 2) Network Manager does not connect automatically with the hidden Wifi Network However, once the WiFi network SSID is set to broadcast mode, it starts connecting automatically. The workaround suggested in Bug 1542733 works here. https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1542733 However, it was suggested to create a new bug report for later releases. Please provide your assistance. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Aug 12 20:11:18 2020 InstallationDate: Installed on 2020-08-09 (3 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.29.1 dev wlp2s0 proto dhcp metric 600 192.168.29.0/24 dev wlp2s0 proto kernel scope link src 192.168.29.22 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 PCWiFi 9a5f3d88-a43e-4862-9cac-b65102e9e135 /org/freedesktop/NetworkManager/ActiveConnection/1 enp3s0 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+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 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
Hit LP: #1891518 so I can't upload more debdiff... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Incomplete Status in alsa-ucm-conf package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: Incomplete Status in alsa-ucm-conf source package in Groovy: Incomplete Status in pulseaudio source package in Groovy: Incomplete Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+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 1766503] Re: ibus-* randomly use high CPU
I have a Using Linux Mint mate (Linux Mint 19.1 Tessa) Linux 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux We are in Belgium (and ibus-deamon configured for FR-BE keyboard) where we use lot of é, è, à and sometime other likes û. As I'm typing quite quickly and make typing faults, I also use a lot the backspace and ctrl+backspace. As I'm also using the terminals, Shift+Ctrl+v and Shift+Ctrl+v are used a lots (sometime by mistake in regular editor like xed). Note that e is configured for emoticones in the ibus-deamon. When taping text in xed (2.0.2)... and usually with xed, the ibus-deamon became crazy and heating CPU. It is not difficult to me identify it, computer quicly raise from 55°C to 80°C (in ~30 seconds). This happens almost each time with xed, sometine in a minute, sometime after a while. That's completely boring... after several weeks I did need to stop using xed ! As I'm a coder, I also use AtomIDE and I did NEVER have the issue under AtomIDE... but XED + iBus-deamon are still firing my CPU. Kind regards, Dominique I -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1766503 Title: ibus-* randomly use high CPU Status in The Ubuntu Power Consumption Project: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+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 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
PulseAudio debdiff for focal ** Patch added: "pulseaudio_13.99.1-1ubuntu3.6.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1891461/+attachment/5401383/+files/pulseaudio_13.99.1-1ubuntu3.6.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Incomplete Status in alsa-ucm-conf package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: Incomplete Status in alsa-ucm-conf source package in Groovy: Incomplete Status in pulseaudio source package in Groovy: Incomplete Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+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 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
PulseAudio debdiff for groovy ** Description changed: - TBD + [Impact] + Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. + + However, both USB audio don't really work out of the box. Issues and + fixes will be described together below. + + [Fix for alsa-lib] + 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: + https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb + + [Fix for alsa-ucm-conf] + 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. + In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: + https://github.com/alsa-project/alsa-ucm-conf/pull/42 + + [Fix for PulseAudio] + 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: + https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b + + 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: + https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f + + [Test] + Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. + + With the above fix all applied, open Gnome Control Center -> Sound tab. + Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. + Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. + Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. + + On other systems, nothing changed. + + [Regression Potential] + For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. + + For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". + AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. + If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. + + For fix 4), if user depends on the old behavior (i.e. switch to another + card while other profiles are still available), this will bring a + behavioral change. However, all available profiles will still be + available after the fix, so users can still be chose the preferred + profile from the g-c-c dropdown menu. ** Patch added: "pulseaudio_13.99.1-1ubuntu9.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1891461/+attachment/5401382/+files/pulseaudio_13.99.1-1ubuntu9.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Incomplete Status in alsa-ucm-conf package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: Incomplete Status in alsa-ucm-conf source package in Groovy: Incomplete Status in pulseaudio source package in Groovy: Incomplete Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and
[Touch-packages] [Bug 1891515] [NEW] ucf overwrites diverted configuration file breaking unattended upgrades - upstream fix available
Public bug reported: An unattended security upgrade (package dovecot-core) failed, interrupting mailbox service. The cause was ucf replacing a custom configuration file which had been diverted (using dpkg-divert) by a custom configuration package. Excerpt from /var/log/apt/term.log: --- Setting up dovecot-core (1:2.2.33.2-1ubuntu4.6) ... Replacing config file /etc/dovecot/dovecot.conf.custom with new version ucfr: Attempt from package dovecot-core to take /etc/dovecot/dovecot.conf.custom away from package custom-mail-server ucfr: Aborting. dpkg: error processing package dovecot-core (--configure): installed dovecot-core package post-installation script subprocess returned error exit status 4 --- The underlying issue has been fixed upstream in ucf version 3.0040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=43 Affected versions: - Ubuntu 18.04.5 LTS - ucf 3.0038 - Ubuntu 20.04.1 LTS - ucf 3.0038+nmu1 ** Affects: ucf Importance: Unknown Status: Unknown ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Affects: ucf (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #43 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=43 ** Also affects: ucf via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=43 Importance: Unknown Status: Unknown ** Also affects: dovecot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891515 Title: ucf overwrites diverted configuration file breaking unattended upgrades - upstream fix available Status in ucf: Unknown Status in dovecot package in Ubuntu: New Status in ucf package in Ubuntu: New Bug description: An unattended security upgrade (package dovecot-core) failed, interrupting mailbox service. The cause was ucf replacing a custom configuration file which had been diverted (using dpkg-divert) by a custom configuration package. Excerpt from /var/log/apt/term.log: --- Setting up dovecot-core (1:2.2.33.2-1ubuntu4.6) ... Replacing config file /etc/dovecot/dovecot.conf.custom with new version ucfr: Attempt from package dovecot-core to take /etc/dovecot/dovecot.conf.custom away from package custom-mail-server ucfr: Aborting. dpkg: error processing package dovecot-core (--configure): installed dovecot-core package post-installation script subprocess returned error exit status 4 --- The underlying issue has been fixed upstream in ucf version 3.0040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=43 Affected versions: - Ubuntu 18.04.5 LTS - ucf 3.0038 - Ubuntu 20.04.1 LTS - ucf 3.0038+nmu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ucf/+bug/1891515/+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 1886572] Re: Remove uptime from the motd-news user agent
** Description changed: + [Impact] + The uptime value in the user-agent string sent to the motd-news server is unused and not necessary. It should be removed. + + [Test Case] + Inspect the /etc/update-motd.d/50-motd-news script and verify that uptime is no longer used. + + Previous version: + $ grep uptime /etc/update-motd.d/50-motd-news + # Some messages may only be pertinent before or after some amount of uptime + read up idle < /proc/uptime + uptime="uptime/$up/$idle" + USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id" + + Updated version: + $ grep uptime /etc/update-motd.d/50-motd-news + (no output) + + + [Regression Potential] + The server side, if it were checking this value, could be surprised by this change. + + [Other Info] + N/A + + [Original Description] I don't why that was included but it shouldn't be. Please remove it. ** Also affects: base-files (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: base-files (Ubuntu Xenial) Status: New => In Progress ** Changed in: base-files (Ubuntu Bionic) Status: New => In Progress ** Changed in: base-files (Ubuntu Focal) Status: New => In Progress ** Changed in: base-files (Ubuntu Xenial) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: base-files (Ubuntu Bionic) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: base-files (Ubuntu Focal) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- 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/1886572 Title: Remove uptime from the motd-news user agent Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: In Progress Status in base-files source package in Bionic: In Progress Status in base-files source package in Focal: In Progress Bug description: [Impact] The uptime value in the user-agent string sent to the motd-news server is unused and not necessary. It should be removed. [Test Case] Inspect the /etc/update-motd.d/50-motd-news script and verify that uptime is no longer used. Previous version: $ grep uptime /etc/update-motd.d/50-motd-news # Some messages may only be pertinent before or after some amount of uptime read up idle < /proc/uptime uptime="uptime/$up/$idle" USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id" Updated version: $ grep uptime /etc/update-motd.d/50-motd-news (no output) [Regression Potential] The server side, if it were checking this value, could be surprised by this change. [Other Info] N/A [Original Description] I don't why that was included but it shouldn't be. Please remove it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+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 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
I've also commited to the pulseaudio Vcs, the alsa packages don't have a Vcs -- 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/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch ucm-implement-CardIdByName-substitution.patch ucm-allow-to-ignore-errors-for-the-value-substitutio.patch ucm-allow-to-use-the-defined-variables-in-the-substi.patch
[Touch-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
Thanks, I've uploaded the changes to groovy now. It would be nice having some confirmation it works there before SRUing to focal. One point for improvement also, the changelog have no human description of the changes which is suboptimal, especially in case of a SRU -- 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/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch
[Touch-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
** Changed in: alsa-lib (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: pulseaudio (Ubuntu Groovy) Status: New => Fix Committed -- 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/1889217 Title: Make digital mic on the AMD Renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Bug description: [Impact] On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch
[Touch-packages] [Bug 1876506] Re: eoan to focal upgrade hangs when lvm snapshot is present
** Package changed: debconf (Ubuntu) => os-prober (Ubuntu) -- 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/1876506 Title: eoan to focal upgrade hangs when lvm snapshot is present Status in os-prober package in Ubuntu: Confirmed Status in os-prober source package in Focal: Confirmed Bug description: When upgrading from 19.10 (w/ LVM + encypted disks) to 20.04, the installer hangs when trying to probe an LVM snapshot volume created before the upgrade. Steps to reproduce: lvcreate -s -L 20G -n preupgrade /dev/vgubuntu/root do-release-upgrade -d The installer will hang after the following message: /usr/sbin/grub-probe: error: unknown filesystem. Found Ubuntu 19.10 (19.10) on /dev/mapper/vgubuntu-preupgrade done Resolution: Killing the grub-mount process which is probing the LVM snapshot seems to unhang the installer and allow the upgrade to complete without issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1876506/+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 1889068] Re: Improve resolved integration
This bug was fixed in the package isc-dhcp - 4.4.1-2.1ubuntu9 --- isc-dhcp (4.4.1-2.1ubuntu9) groovy; urgency=medium * Revert 4.4.1-2.1ubuntu8, network-manager autopkgtests regress on ppc64el. -- Dimitri John Ledkov Wed, 12 Aug 2020 10:33:55 +0100 ** Changed in: isc-dhcp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1889068 Title: Improve resolved integration Status in ifupdown package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Fix Released Status in resolvconf package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Insure that ifupdown & dhcp DNS information is always added to resolved. Move the resolved hooks from systemd package to isc-dhcp-client and ifupdown themselves. Figure out how to integrate "eth0" resolver => Manager resolver. Blog / document how to control this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1889068/+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 1890609] Re: improved resolved configuration
This bug was fixed in the package systemd - 246-2ubuntu1 --- systemd (246-2ubuntu1) groovy; urgency=medium [ Balint Reczey ] * Merge to Ubuntu from Debian unstable - Dropped changes: * core: set /run size to 10%, like initramfs-tools does. This is now upstream's default, also setting other limits * UBUNTU-resolved-disable-global-LLMNR-and-MulticastDNS.patch * Lock swap blockdevice while calling mkswap * Cherry-pick reversion of detecting WSL by the presence of "microsoft" in osrelease * journald: stream pid change newline fix * network: Change IgnoreCarrierLoss default to value of ConfigureWithoutCarrier. * network: do not re-attach sd-event object * network: attach sd-event in link_load() when creating link dhcp_client or ipv4ll * debian/rules: Configure LLMNR and MulticastDNS to be disabled by default instead of using a carried patch, like before. File: debian/rules https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a186cce127ee1d2b0288e4db1470e45a2b1914d9 * debian/rules: Configure LLMNR and MulticastDNS to be disabled by default instead of using a carried patch, like before. File: debian/rules https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a186cce127ee1d2b0288e4db1470e45a2b1914d9 [ Dimitri John Ledkov ] * dhclient-enter-hooks.d/resolved: drop in favor of exit hooks shipped elsewhere. isc-dhcp / ifupdown now ship the hooks themselves to push DNS data to resolved. Thus enter hook no longer required. (LP: #1890609) Files: - debian/control - debian/rules - debian/systemd.maintscript - debian/extra/dhclient-enter-resolved-hook https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=97b9397e0ac23c4975cbd13ec6ae8d2f9bc48c92 systemd (246-2) unstable; urgency=medium * Upload to unstable systemd (246-1) experimental; urgency=medium * New upstream version 246 * Rebase patches * Update symbols file for libsystemd0 * Bump libapparmor-dev Build-Depends to (>= 2.13) * Disable libfido2 support. This is only used by homed which we don't enable. -- Balint Reczey Thu, 06 Aug 2020 17:13:31 +0200 ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- 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/1890609 Title: improved resolved configuration Status in systemd package in Ubuntu: Fix Released Bug description: improved resolved configuration * isc-dhcp-client pushes DNS data to resolved via a hook it ships * ifupdown pushes DNS data to resolved via a hook it ships * resolvconf skips pulling DNS data that is pushed to resolved * systemd doesn't have enter hook anymore This way with or without resolvconf, resolved has all the information it needs and /etc/resolv.conf can be static, point at resolvconf managed file, or at resolved managed file as desired. isc-dhcp 4.4.1-2.1ubuntu7 ifupdown 0.8.35ubuntu2 resolvconf 1.82ubuntu1 systemd TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890609/+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 1884846] Re: Can't connect to internet if second user session
@seb128, shall I open this bug anywhere else too? Thanks! ** Changed in: network-manager (Ubuntu) Status: Incomplete => New -- 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/1884846 Title: Can't connect to internet if second user session Status in network-manager package in Ubuntu: New Bug description: My kid was using the laptop, connected to internet in his user session. I switched to my user (but his session was still active), and NetworkManager couldn't connect to internet. Error from syslog: Jun 23 19:30:15 tanquita NetworkManager[854]: [1592951415.1979] audit: op="connection-activate" uuid="a52379fa- 0a44-4013-93b6-b04e63515fb9" name="Voyager" pid=34278 uid=1000 result="fail" reason="Private connection already active on the device: uid 1000 has no permission to perform this operation" (uid 1000 is myself) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jun 23 19:40:19 2020 InstallationDate: Installed on 2020-06-20 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.100.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.100.0/24 dev wlp4s0 proto kernel scope link src 192.168.100.103 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1884846/+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 1891474] Re: gdk-pixbuf ftbfs in focal/s390x
that worked on the second retry ** Changed in: gdk-pixbuf (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1891474 Title: gdk-pixbuf ftbfs in focal/s390x Status in gdk-pixbuf package in Ubuntu: Invalid Bug description: seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19794513 Ok: 22 Expected Fail: 0 Fail: 1 Unexpected Pass: 0 Skipped: 0 Timeout: 0 The output from the failed tests: 6/23 gdk-pixbuf:slow / pixbuf-randomly-modified FAIL 0.52 s (killed by signal 5 SIGTRAP) --- command --- 16:22:55 GDK_PIXBUF_MODULE_FILE='/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/gdk-pixbuf/loaders.cache' G_TEST_SRCDIR='/<>/gdk-pixbuf-2.40.0+dfsg/tests' G_TEST_BUILDDIR='/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests' /<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests/pixbuf-randomly-modified -k --tap --- stdout --- # random seed: R02S818441d868b74ad43d50db5aedeb15ea # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? # Modified image is written to pixbuf-randomly-modified-image 1..65 # Start of pixbuf tests # Start of randomly-modified tests ok 1 /pixbuf/randomly-modified/bad-header.ico ok 2 /pixbuf/randomly-modified/bmp-line-overflow.bmp ok 3 /pixbuf/randomly-modified/bug775232.pnm ok 4 /pixbuf/randomly-modified/bug775242.bmp ok 5 /pixbuf/randomly-modified/bug775648.qtif ok 6 /pixbuf/randomly-modified/bug775697.jpg ok 7 /pixbuf/randomly-modified/bug776040.ico ok 8 /pixbuf/randomly-modified/crash.ico ok 9 /pixbuf/randomly-modified/decodecolormap.bmp ok 10 /pixbuf/randomly-modified/invalid.1.xpm ok 11 /pixbuf/randomly-modified/invalid.2.ico ok 12 /pixbuf/randomly-modified/invalid.4.ppm ok 13 /pixbuf/randomly-modified/valid.1.bmp ok 14 /pixbuf/randomly-modified/valid.1.gif Bail out! GLib-FATAL-ERROR: ../../../glib/gmem.c:173: failed to allocate 131072 bytes --- stderr --- (/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests/pixbuf-randomly-modified:10136): GLib-ERROR **: 16:22:56.100: ../../../glib/gmem.c:173: failed to allocate 131072 bytes --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1891474/+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 1891342] Re: network manager does not auto connect to hidden wifi networks
The issue sounds similar to https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/438 upstream, could you provide on gitlab the informations requested? ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #438 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/438 ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1891342 Title: network manager does not auto connect to hidden wifi networks Status in network-manager package in Ubuntu: Incomplete Bug description: Environment: Fresh installation of Lubuntu 20.04 (it also occurs in a fresh installation of Ubuntu 20.04) Steps to reproduce the situation: 1) Lubuntu -> Network Manager -> Edit Connections -> Add SSID of a hidden WiFi network 2) Network Manager does not connect automatically with the hidden Wifi Network However, once the WiFi network SSID is set to broadcast mode, it starts connecting automatically. The workaround suggested in Bug 1542733 works here. https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1542733 However, it was suggested to create a new bug report for later releases. Please provide your assistance. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Aug 12 20:11:18 2020 InstallationDate: Installed on 2020-08-09 (3 days ago) InstallationMedia: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.29.1 dev wlp2s0 proto dhcp metric 600 192.168.29.0/24 dev wlp2s0 proto kernel scope link src 192.168.29.22 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 PCWiFi 9a5f3d88-a43e-4862-9cac-b65102e9e135 /org/freedesktop/NetworkManager/ActiveConnection/1 enp3s0 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891342/+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 1891474] Re: gdk-pixbuf ftbfs in focal/s390x
Could you retry to see if that was a one off? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1891474 Title: gdk-pixbuf ftbfs in focal/s390x Status in gdk-pixbuf package in Ubuntu: Confirmed Bug description: seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19794513 Ok: 22 Expected Fail: 0 Fail: 1 Unexpected Pass: 0 Skipped: 0 Timeout: 0 The output from the failed tests: 6/23 gdk-pixbuf:slow / pixbuf-randomly-modified FAIL 0.52 s (killed by signal 5 SIGTRAP) --- command --- 16:22:55 GDK_PIXBUF_MODULE_FILE='/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/gdk-pixbuf/loaders.cache' G_TEST_SRCDIR='/<>/gdk-pixbuf-2.40.0+dfsg/tests' G_TEST_BUILDDIR='/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests' /<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests/pixbuf-randomly-modified -k --tap --- stdout --- # random seed: R02S818441d868b74ad43d50db5aedeb15ea # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? # Modified image is written to pixbuf-randomly-modified-image 1..65 # Start of pixbuf tests # Start of randomly-modified tests ok 1 /pixbuf/randomly-modified/bad-header.ico ok 2 /pixbuf/randomly-modified/bmp-line-overflow.bmp ok 3 /pixbuf/randomly-modified/bug775232.pnm ok 4 /pixbuf/randomly-modified/bug775242.bmp ok 5 /pixbuf/randomly-modified/bug775648.qtif ok 6 /pixbuf/randomly-modified/bug775697.jpg ok 7 /pixbuf/randomly-modified/bug776040.ico ok 8 /pixbuf/randomly-modified/crash.ico ok 9 /pixbuf/randomly-modified/decodecolormap.bmp ok 10 /pixbuf/randomly-modified/invalid.1.xpm ok 11 /pixbuf/randomly-modified/invalid.2.ico ok 12 /pixbuf/randomly-modified/invalid.4.ppm ok 13 /pixbuf/randomly-modified/valid.1.bmp ok 14 /pixbuf/randomly-modified/valid.1.gif Bail out! GLib-FATAL-ERROR: ../../../glib/gmem.c:173: failed to allocate 131072 bytes --- stderr --- (/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests/pixbuf-randomly-modified:10136): GLib-ERROR **: 16:22:56.100: ../../../glib/gmem.c:173: failed to allocate 131072 bytes --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1891474/+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 1808421] Re: gparted produces unusual results when ZFS partitios exist
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: util-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1808421 Title: gparted produces unusual results when ZFS partitios exist Status in GParted: New Status in gparted package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: Run gparted on a disk that has ZFS partitions. It shows one entire partition. Parted seems to display correctly. gparted image attached. hbarta@saugage:~$ sudo parted /dev/sda GNU Parted 3.2 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) p Model: ATA Samsung SSD 850 (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start EndSizeFile system Name Flags 1 1049kB 538MB 537MB fat32 boot, esp 2 538MB 555MB 16.8MB zfs Microsoft reserved partition msftres 3 555MB 105GB 105GB ntfs Basic data partition msftdata 4 105GB 420GB 315GB zfs rpool (parted) q hbarta@saugage:~$ hbarta@saugage:~$ sudo sgdisk -p /dev/sda Disk /dev/sda: 1953525168 sectors, 931.5 GiB Model: Samsung SSD 850 Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): EBA09D2E-0F70-4D11-8E37-C1C170CFD9DD Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 1953525134 Partitions will be aligned on 2048-sector boundaries Total free space is 1133243757 sectors (540.4 GiB) Number Start (sector)End (sector) Size Code Name 12048 1050623 512.0 MiB EF00 2 1050624 1083391 16.0 MiB0C01 Microsoft reserved ... 3 1083392 205883391 97.7 GiB0700 Basic data partition 4 205883392 820283391 293.0 GiB 8300 rpool hbarta@saugage:~$ hbarta@saugage:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 hbarta@saugage:~$ Reproduce: 1) Configure (perhaps install) Ubuntu on a drive with a ZFS partition. 2) Open gparted. Note: Same issue happens with gparted on the 18.04.1 desktop install USB. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gparted 0.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 13 15:05:13 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US SHELL=/bin/bash SourcePackage: gparted UpgradeStatus: Upgraded to cosmic on 2018-12-13 (0 days ago) mtime.conffile..etc.logrotate.d.apport: 2018-12-12T13:31:49.347693 To manage notifications about this bug go to: https://bugs.launchpad.net/gparted/+bug/1808421/+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 1886886] Re: Plymouth 0.9.5 release
** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1886886 Title: Plymouth 0.9.5 release Status in plymouth package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Confirmed Bug description: Plymouth 0.9.5 release: https://www.freedesktop.org/software/plymouth/releases/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1886886/+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 1870088] Re: xz-utils ftbfs in focal
seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19801445 ** Changed in: xz-utils (Ubuntu Focal) Status: Fix Committed => Confirmed ** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/1870088 Title: xz-utils ftbfs in focal Status in xz-utils package in Ubuntu: Fix Released Status in xz-utils source package in Focal: Confirmed Status in xz-utils package in Debian: New Bug description: seen in the second focal test rebuild https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz dh build --parallel make[2]: Leaving directory '/<>' dh_testroot -O--parallel dh_prep -O--parallel debian/rules override_dh_auto_install make[2]: Entering directory '/<>' dh_auto_install --builddirectory debian/xzdec-build dh_auto_install --builddirectory debian/normal-build dh_auto_install --builddirectory debian/static-build set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \ install -d debian/tmp/lib/$arch; \ mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \ dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \ ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such file or directory make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:4: install] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:4: binary] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1870088/+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 1891332] Re: /usr/bin/unattended-upgrade:apt_pkg.Error:try_to_upgrade:mark_upgrade_adjusted:call_adjusted:clear:/usr/bin/unattended-upgrade@2514:main:run:calculate_upgradable_pkg
*** This bug is a duplicate of bug 1871145 *** https://bugs.launchpad.net/bugs/1871145 ** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 2.3ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/a16ab8014a871a4f125fcf1b5f1412bd338f9b5c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. + + + Traceback (most recent call last): + File "/usr/bin/unattended-upgrade", line 1705, in try_to_upgrade + cache.mark_upgrade_adjusted(pkg, from_user=not pkg.is_auto_installed) + File "/usr/bin/unattended-upgrade", line 440, in mark_upgrade_adjusted + self.call_adjusted(apt.package.Package.mark_upgrade, pkg, **kwargs) + File "/usr/bin/unattended-upgrade", line 399, in call_adjusted + self.clear() + File "/usr/lib/python3/dist-packages/apt/cache.py", line 700, in clear + self._depcache.init() + apt_pkg.Error: E:The package ts3client needs to be reinstalled, but I can't find an archive for it. + + During handling of the above exception, another exception occurred: + + Traceback (most recent call last): + File "/usr/bin/unattended-upgrade", line 2514, in + sys.exit(main(options)) + File "/usr/bin/unattended-upgrade", line 1985, in main + res = run(options, rootdir, mem_log, logfile_dpkg, + File "/usr/bin/unattended-upgrade", line 2157, in run + pkgs_to_upgrade = calculate_upgradable_pkgs(cache, options) + File "/usr/bin/unattended-upgrade", line 1746, in calculate_upgradable_pkgs + try_to_upgrade(pkg, + File "/usr/bin/unattended-upgrade", line 1716, in try_to_upgrade + rewind_cache(cache, pkgs_to_upgrade) + File "/usr/bin/unattended-upgrade", line 1334, in rewind_cache + cache.clear() + File "/usr/lib/python3/dist-packages/apt/cache.py", line 700, in clear + self._depcache.init() + apt_pkg.Error: E:The package ts3client needs to be reinstalled, but I can't find an archive for it. ** This bug has been marked a duplicate of bug 1871145 apt.Cache.clear() -> apt.Cache._depcache.init() raises Error -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1891332 Title: /usr/bin/unattended- upgrade:apt_pkg.Error:try_to_upgrade:mark_upgrade_adjusted:call_adjusted:clear:/usr/bin /unattended- upgrade@2514:main:run:calculate_upgradable_pkgs:try_to_upgrade:rewind_cache:clear Status in unattended-upgrades package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 2.3ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/a16ab8014a871a4f125fcf1b5f1412bd338f9b5c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1705, in try_to_upgrade cache.mark_upgrade_adjusted(pkg, from_user=not pkg.is_auto_installed) File "/usr/bin/unattended-upgrade", line 440, in mark_upgrade_adjusted self.call_adjusted(apt.package.Package.mark_upgrade, pkg, **kwargs) File "/usr/bin/unattended-upgrade", line 399, in call_adjusted self.clear() File "/usr/lib/python3/dist-packages/apt/cache.py", line 700, in clear self._depcache.init() apt_pkg.Error: E:The package ts3client needs to be reinstalled, but I can't find an archive for it. During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2514, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1985, in main res = run(options, rootdir, mem_log, logfile_dpkg, File "/usr/bin/unattended-upgrade", line 2157, in run pkgs_to_upgrade = calculate_upgradable_pkgs(cache, options) File "/usr/bin/unattended-upgrade", line 1746, in calculate_upgradable_pkgs try_to_upgrade(pkg, File "/usr/bin/unattended-upgrade", line 1716, in try_to_upgrade rewind_cache(cache, pkgs_to_upgrade) File "/usr/bin/unattended-upgrade", line 1334, in rewind_cache cache.clear() File "/usr/lib/python3/dist-packages/apt/cache.py", line 700, in clear self._depcache.init() apt_pkg.Error: E:The package ts3client needs to be reinstalled, but I can't find an archive for it. To manage notifications about this bug go to:
[Touch-packages] [Bug 1871145] Re: apt.Cache.clear() -> apt.Cache._depcache.init() raises Error
Unattended-upgrades may handle this exception by exiting with failure and not re-raising it to the top. ** Changed in: unattended-upgrades (Ubuntu) Status: Opinion => Triaged ** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1871145 Title: apt.Cache.clear() -> apt.Cache._depcache.init() raises Error Status in python-apt package in Ubuntu: Opinion Status in unattended-upgrades package in Ubuntu: Triaged Bug description: Unattended-upgrades 2.1 triggers the following crash in python-apt: File "/usr/bin/unattended-upgrade", line 1706, in try_to_upgrade cache.mark_upgrade_adjusted(pkg, from_user=not pkg.is_auto_installed) File "/usr/bin/unattended-upgrade", line 438, in mark_upgrade_adjusted self.call_adjusted(apt.package.Package.mark_upgrade, pkg, **kwargs) File "/usr/bin/unattended-upgrade", line 397, in call_adjusted self.clear() File "/usr/lib/python3/dist-packages/apt/cache.py", line 700, in clear self._depcache.init() apt_pkg.Error: E:The package intellij-idea-ultimate needs to be reinstalled, but I can't find an archive for it. I think .clear() should not raise an error, but if it should u-u can catch that. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 2.1, the problem page at https://errors.ubuntu.com/problem/798f1ab5a4a2784a0fadd6034a875901345682f9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1871145/+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 1891486] [NEW] vim ftbfs in focal (armhf, ppc64el)
Public bug reported: seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19801040 https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19801038 --- Executed: 2257 Tests Skipped:31 Tests FAILED: 1 Tests Failures: From test_debugger.vim: Found errors in Test_Debugger(): function RunTheTest[40]..Test_Debugger[157]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..59 line 1: Expected 'No breakpoints defined' but got 'cmd: echo Foo()' function RunTheTest[40]..Test_Debugger[185]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..71 line 1: Expected '19' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[188]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..72 line 1: Expected 'E161: Breakpoint not found: 2' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..73 line 1: Expected 'Entering Debug mode. Type "cont" to continue.' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..74 line 1: Expected 'function Bazz' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[192]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..75 line 1: Expected 'line 2: let var1 = 3 + a:var' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[199]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..76 line 1: Expected ' 3 func Bazz line 2' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[199]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..77 line 1: Expected ' 4 expr var3' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..78 line 1: Expected 'Breakpoint in "Bazz" line 5' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..79 line 1: Expected 'Oldval = "''another var''"' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..80 line 1: Expected 'Newval = "''value2''"' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..81 line 1: Expected 'function Bazz' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[201]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..82 line 1: Expected 'line 5: catch' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[208]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..83 line 1: Expected 'No breakpoints defined' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..84 line 1: Expected 'Error detected while processing function Bazz:' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..85 line 1: Expected 'line5:' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[211]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..86 line 1: Expected 'E475: Invalid argument: abcd' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[215]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..87 line 1: Expected 'E475: Invalid argument: func' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[216]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..88 line 1: Expected 'E475: Invalid argument: func 2' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[217]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..89 line 1: Expected 'E475: Invalid argument: func a()' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[218]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..90 line 1: Expected 'E475: Invalid argument: abcd' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[219]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..91 line 1: Expected 'E475: Invalid argument: func' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[220]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..92 line 1: Expected 'E475: Invalid argument: func a()' but got '~\[ occurs 74 times]' function RunTheTest[40]..Test_Debugger[221]..RunDbgCmd[8]..WaitForAssert[2]..6_WaitForCommon[11]..93 line 1: Expected 'E161: Breakpoint not found: func a' but got '~\[ occurs 74 times]' function
[Touch-packages] [Bug 1872118] Re: [SRU] DHCP Cluster crashes after a few hours
** Changed in: bind9-libs (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1872118 Title: [SRU] DHCP Cluster crashes after a few hours Status in DHCP: New Status in bind9-libs package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Invalid Status in bind9-libs source package in Focal: In Progress Status in isc-dhcp source package in Focal: Invalid Status in bind9-libs source package in Groovy: Fix Released Status in isc-dhcp source package in Groovy: Invalid Bug description: [Description] isc-dhcp-server uses libisc-export (coming from bind9-libs package) for handling the socket event(s) when configured in peer mode (master/secondary). It's possible that a sequence of messages dispatched by the master that requires acknowledgment from its peers holds a socket in a pending to send state, a timer or a subsequent write request can be scheduled into this socket and the !sock->pending_send assertion will be raised when trying to write again at the time data hasn't been flushed entirely and the pending_send flag hasn't been reset to 0 state. If this race condition happens, the following stacktrace will be hit: (gdb) info threads Id Target Id Frame * 1 Thread 0x7fb4ddecb700 (LWP 3170) __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 2 Thread 0x7fb4dd6ca700 (LWP 3171) __lll_lock_wait (futex=futex@entry=0x7fb4de6d2028, private=0) at lowlevellock.c:52 3 Thread 0x7fb4de6cc700 (LWP 3169) futex_wake (private=, processes_to_wake=1, futex_word=) at ../sysdeps/nptl/futex-internal.h:364 4 Thread 0x7fb4de74f740 (LWP 3148) futex_wait_cancelable (private=, expected=0, futex_word=0x7fb4de6cd0d0) at ../sysdeps/nptl/futex-internal.h:183 (gdb) frame 2 #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 (gdb) bt #1 0x7fb4deaa7859 in __GI_abort () at abort.c:79 #2 0x7fb4dec85985 in isc_assertion_failed (file=file@entry=0x7fb4decd8878 "../../../../lib/isc/unix/socket.c", line=line@entry=3361, type=type@entry=isc_assertiontype_insist, cond=cond@entry=0x7fb4decda033 "!sock->pending_send") at ../../../lib/isc/assertions.c:52 #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 #4 process_fd (writeable=, readable=, fd=11, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4054 #5 process_fds (writefds=, readfds=0x7fb4de6d1090, maxfd=13, manager=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4211 #6 watcher (uap=0x7fb4de6d0010) at ../../../../lib/isc/unix/socket.c:4397 #7 0x7fb4dea68609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb4deba4103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (gdb) frame 3 #3 0x7fb4decc17e1 in dispatch_send (sock=0x7fb4de6d4990) at ../../../../lib/isc/unix/socket.c:4041 4041 in ../../../../lib/isc/unix/socket.c (gdb) p sock->pending_send $2 = 1 [TEST CASE] 1) Install isc-dhcp-server in 2 focal machine(s). 2) Configure peer/cluster mode as follows: Primary configuration: https://pastebin.ubuntu.com/p/XYj648MghK/ Secondary configuration: https://pastebin.ubuntu.com/p/PYkcshZCWK/ 2) Run dhcpd as follows in both machine(s) # dhcpd -f -d -4 -cf /etc/dhcp/dhcpd.conf --no-pid ens4 3) Leave the cluster running for a long (2h) period until the crash/race condition is reproduced. [REGRESSION POTENTIAL] * The fix will prevent the assertion to happen in the dispatch_send path, later versions of isch-dhcp upstream lack this logic and entirely removed the existence of this flag. Therefore, removing the need for this assertion at process_fd shouldn't be problematic. To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1872118/+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 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
** Also affects: alsa-lib (Ubuntu Groovy) Importance: Undecided Status: Incomplete ** Also affects: pulseaudio (Ubuntu Groovy) Importance: Undecided Status: Incomplete ** Also affects: alsa-ucm-conf (Ubuntu Groovy) Importance: Undecided Status: Incomplete ** Also affects: alsa-lib (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Incomplete Status in alsa-ucm-conf package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: Incomplete Status in alsa-ucm-conf source package in Groovy: Incomplete Status in pulseaudio source package in Groovy: Incomplete Bug description: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+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 1856574] Re: removal of various autopilot packages
This bug was fixed in the package autopilot-gtk - 1.6.1 --- autopilot-gtk (1.6.1) groovy; urgency=medium [Jean-Baptiste Lallement] * Updated dependencies to python3 of evdev and gi (LP: #1856574) -- Christian Ehrhardt Thu, 13 Aug 2020 10:00:26 +0200 ** Changed in: autopilot-gtk (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-testtools in Ubuntu. https://bugs.launchpad.net/bugs/1856574 Title: removal of various autopilot packages Status in autopilot-gtk package in Ubuntu: Fix Released Status in autopilot-legacy package in Ubuntu: Fix Released Status in python-fixtures package in Ubuntu: Fix Released Status in python-testtools package in Ubuntu: Fix Released Bug description: python-fixtures and python-testtools are not built anymore in focal, but still referenced by some Ubuntu-only packages. We need to at least remove autopilot-legacy if we don't want to re-introduce those package, and modify autopilot-gtk to build witout the autopilot-legacy b-d. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+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 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
Obviously more information is required :) ** Changed in: alsa-lib (Ubuntu) Status: New => Incomplete ** Changed in: alsa-ucm-conf (Ubuntu) Status: New => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Incomplete Status in alsa-ucm-conf package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+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 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
... because USB audio should work already. If something doesn't work then please describe that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Incomplete Status in alsa-ucm-conf package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+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 1891479] [NEW] pycurl ftbfs in focal (wait-deps)
Public bug reported: seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19799602 Missing build dependencies: python-sphinx ** Affects: pycurl (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ff-incoming ** Changed in: pycurl (Ubuntu) Status: New => Confirmed ** Changed in: pycurl (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1891479 Title: pycurl ftbfs in focal (wait-deps) Status in pycurl package in Ubuntu: Confirmed Bug description: seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19799602 Missing build dependencies: python-sphinx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1891479/+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 1891474] [NEW] gdk-pixbuf ftbfs in focal/s390x
Public bug reported: seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19794513 Ok: 22 Expected Fail: 0 Fail: 1 Unexpected Pass: 0 Skipped: 0 Timeout: 0 The output from the failed tests: 6/23 gdk-pixbuf:slow / pixbuf-randomly-modified FAIL 0.52 s (killed by signal 5 SIGTRAP) --- command --- 16:22:55 GDK_PIXBUF_MODULE_FILE='/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/gdk-pixbuf/loaders.cache' G_TEST_SRCDIR='/<>/gdk-pixbuf-2.40.0+dfsg/tests' G_TEST_BUILDDIR='/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests' /<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests/pixbuf-randomly-modified -k --tap --- stdout --- # random seed: R02S818441d868b74ad43d50db5aedeb15ea # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? # Modified image is written to pixbuf-randomly-modified-image 1..65 # Start of pixbuf tests # Start of randomly-modified tests ok 1 /pixbuf/randomly-modified/bad-header.ico ok 2 /pixbuf/randomly-modified/bmp-line-overflow.bmp ok 3 /pixbuf/randomly-modified/bug775232.pnm ok 4 /pixbuf/randomly-modified/bug775242.bmp ok 5 /pixbuf/randomly-modified/bug775648.qtif ok 6 /pixbuf/randomly-modified/bug775697.jpg ok 7 /pixbuf/randomly-modified/bug776040.ico ok 8 /pixbuf/randomly-modified/crash.ico ok 9 /pixbuf/randomly-modified/decodecolormap.bmp ok 10 /pixbuf/randomly-modified/invalid.1.xpm ok 11 /pixbuf/randomly-modified/invalid.2.ico ok 12 /pixbuf/randomly-modified/invalid.4.ppm ok 13 /pixbuf/randomly-modified/valid.1.bmp ok 14 /pixbuf/randomly-modified/valid.1.gif Bail out! GLib-FATAL-ERROR: ../../../glib/gmem.c:173: failed to allocate 131072 bytes --- stderr --- (/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests/pixbuf-randomly-modified:10136): GLib-ERROR **: 16:22:56.100: ../../../glib/gmem.c:173: failed to allocate 131072 bytes --- ** Affects: gdk-pixbuf (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-ff-incoming ** Changed in: gdk-pixbuf (Ubuntu) Status: New => Confirmed ** Changed in: gdk-pixbuf (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1891474 Title: gdk-pixbuf ftbfs in focal/s390x Status in gdk-pixbuf package in Ubuntu: Confirmed Bug description: seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19794513 Ok: 22 Expected Fail: 0 Fail: 1 Unexpected Pass: 0 Skipped: 0 Timeout: 0 The output from the failed tests: 6/23 gdk-pixbuf:slow / pixbuf-randomly-modified FAIL 0.52 s (killed by signal 5 SIGTRAP) --- command --- 16:22:55 GDK_PIXBUF_MODULE_FILE='/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/gdk-pixbuf/loaders.cache' G_TEST_SRCDIR='/<>/gdk-pixbuf-2.40.0+dfsg/tests' G_TEST_BUILDDIR='/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests' /<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests/pixbuf-randomly-modified -k --tap --- stdout --- # random seed: R02S818441d868b74ad43d50db5aedeb15ea # GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? # Modified image is written to pixbuf-randomly-modified-image 1..65 # Start of pixbuf tests # Start of randomly-modified tests ok 1 /pixbuf/randomly-modified/bad-header.ico ok 2 /pixbuf/randomly-modified/bmp-line-overflow.bmp ok 3 /pixbuf/randomly-modified/bug775232.pnm ok 4 /pixbuf/randomly-modified/bug775242.bmp ok 5 /pixbuf/randomly-modified/bug775648.qtif ok 6 /pixbuf/randomly-modified/bug775697.jpg ok 7 /pixbuf/randomly-modified/bug776040.ico ok 8 /pixbuf/randomly-modified/crash.ico ok 9 /pixbuf/randomly-modified/decodecolormap.bmp ok 10 /pixbuf/randomly-modified/invalid.1.xpm ok 11 /pixbuf/randomly-modified/invalid.2.ico ok 12 /pixbuf/randomly-modified/invalid.4.ppm ok 13 /pixbuf/randomly-modified/valid.1.bmp ok 14 /pixbuf/randomly-modified/valid.1.gif Bail out! GLib-FATAL-ERROR: ../../../glib/gmem.c:173: failed to allocate 131072 bytes --- stderr --- (/<>/gdk-pixbuf-2.40.0+dfsg/obj-s390x-linux-gnu/tests/pixbuf-randomly-modified:10136): GLib-ERROR **: 16:22:56.100: ../../../glib/gmem.c:173: failed to allocate 131072 bytes --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1891474/+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 1891463] [NEW] HP network printer auto-found, two printer instances created, neither work
Public bug reported: Ubuntu 20.04 Desktop auto-finds my wifi network based HP OfficeJet Pro 8720 successfully on boot. It seems to create two instances of printer, neither of which seem to do anything. Log file has "No destination host name supplied by cups-browsed for printer \"HP_OfficeJet_Pro_8720_AE46BB_\", is cups-browsed running?" cups-browsed is running: $ service cups-browsed status ● cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-08-10 17:24:45 BST; 2 days ago Main PID: 905 (cups-browsed) Tasks: 3 (limit: 9356) Memory: 4.8M CGroup: /system.slice/cups-browsed.service └─905 /usr/sbin/cups-browsed Aug 10 17:24:45 shart-Yoga3 systemd[1]: Started Make remote CUPS printers available locally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 13 10:35:15 2020 Lpstat: device for HP_OfficeJet_Pro_8720_AE46BB_: implicitclass://HP_OfficeJet_Pro_8720_AE46BB_/ MachineType: LENOVO 80HE Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_OfficeJet_Pro_8720_AE46BB_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_OfficeJet_Pro_8720_AE46BB_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=2bbae2f7-9256-4aa3-a665-681fc9613e16 ro quiet splash resume=UUID=ebd536cc-b52c-462a-9835-86e7f3faf627 vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/08/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A6CN47WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 3 Pro-1370 dmi.modalias: dmi:bvnLENOVO:bvrA6CN47WW:bd12/08/2014:svnLENOVO:pn80HE:pvrLenovoYOGA3Pro-1370:rvnLENOVO:rnVIUU4:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYOGA3Pro-1370: dmi.product.family: IDEAPAD dmi.product.name: 80HE dmi.product.sku: LENOVO_MT_80HE_BU_idea_FM_Lenovo YOGA 3 Pro-1370 dmi.product.version: Lenovo YOGA 3 Pro-1370 dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1891463 Title: HP network printer auto-found, two printer instances created, neither work Status in cups package in Ubuntu: New Bug description: Ubuntu 20.04 Desktop auto-finds my wifi network based HP OfficeJet Pro 8720 successfully on boot. It seems to create two instances of printer, neither of which seem to do anything. Log file has "No destination host name supplied by cups-browsed for printer \"HP_OfficeJet_Pro_8720_AE46BB_\", is cups-browsed running?" cups-browsed is running: $ service cups-browsed status ● cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-08-10 17:24:45 BST; 2 days ago Main PID: 905 (cups-browsed) Tasks: 3 (limit: 9356) Memory: 4.8M CGroup: /system.slice/cups-browsed.service └─905 /usr/sbin/cups-browsed Aug 10 17:24:45 shart-Yoga3 systemd[1]: Started Make remote CUPS printers available locally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 13 10:35:15 2020 Lpstat: device for HP_OfficeJet_Pro_8720_AE46BB_: implicitclass://HP_OfficeJet_Pro_8720_AE46BB_/ MachineType: LENOVO 80HE Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_OfficeJet_Pro_8720_AE46BB_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_OfficeJet_Pro_8720_AE46BB_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=UUID=2bbae2f7-9256-4aa3-a665-681fc9613e16 ro quiet splash resume=UUID=ebd536cc-b52c-462a-9835-86e7f3faf627 vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/08/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A6CN47WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4
[Touch-packages] [Bug 1891461] [NEW] Add proper USB audio support for Lenovo ThinkStation P620
Public bug reported: TBD ** Affects: alsa-lib (Ubuntu) Importance: Undecided Status: New ** Affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: alsa-lib (Ubuntu) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (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/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+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 1876486] Re: systemd breaks due to old libsecomp libs left on the system
** Summary changed: - Kernel panic booting after 18.04 to 20.04 upgrade + systemd breaks due to old libsecomp libs left on the system -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: systemd breaks due to old libsecomp libs left on the system Status in libseccomp package in Ubuntu: Incomplete Bug description: Upgraded Ubuntu 18.04 to 20.04. Following the upgrade, booting was not possible. The error messages is: /sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: seccomp_api_get [4.608900] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 See also attached photograph of screen during boot. Upgrade followed steps from here: https://help.ubuntu.com/community/FocalUpgrades/Kubuntu With the excpetion that The -d flag was used for the do-release-upgrade: sudo do-release-upgrade -d -m desktop 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Prior to upgrade: Ubuntu 18.04.4 After upgrade (but never booted): Ubuntu (Kubuntu) 20.04 Note that Ubuntu had originally be installed, but kubuntu-desktop was recently installed to change to Kubuntu, but no booting problems were experienced before updating to 20.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Unknown -- Package version may have changed when upgrading to 20.04. 3) What you expected to happen Boot without kernel panic. 4) What happened instead Could not boot. Even selecting safe mode from grub could not boot. Had to restore system from backups. Will not attempt upgrade again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+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 1856574] Re: removal of various autopilot packages
** Changed in: autopilot-gtk (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 python-testtools in Ubuntu. https://bugs.launchpad.net/bugs/1856574 Title: removal of various autopilot packages Status in autopilot-gtk package in Ubuntu: Fix Committed Status in autopilot-legacy package in Ubuntu: Fix Released Status in python-fixtures package in Ubuntu: Fix Released Status in python-testtools package in Ubuntu: Fix Released Bug description: python-fixtures and python-testtools are not built anymore in focal, but still referenced by some Ubuntu-only packages. We need to at least remove autopilot-legacy if we don't want to re-introduce those package, and modify autopilot-gtk to build witout the autopilot-legacy b-d. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+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 1856574] Re: removal of various autopilot packages
Sorry it has completely fallen through the cracks. Here is the fix: https://git.launchpad.net/autopilot- gtk/commit/?id=00d7a3d7111cdca00b949bfa9c315781e6701328 It builds successfully on groovy/amd64 (waiting for armhf) https://launchpad.net/~autopilot/+archive/ubuntu/ap-unstable-rel- testing/+sourcepub/11524790/+listing-archive-extra -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-testtools in Ubuntu. https://bugs.launchpad.net/bugs/1856574 Title: removal of various autopilot packages Status in autopilot-gtk package in Ubuntu: In Progress Status in autopilot-legacy package in Ubuntu: Fix Released Status in python-fixtures package in Ubuntu: Fix Released Status in python-testtools package in Ubuntu: Fix Released Bug description: python-fixtures and python-testtools are not built anymore in focal, but still referenced by some Ubuntu-only packages. We need to at least remove autopilot-legacy if we don't want to re-introduce those package, and modify autopilot-gtk to build witout the autopilot-legacy b-d. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+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 1856574] Re: removal of various autopilot packages
** Changed in: autopilot-gtk (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-testtools in Ubuntu. https://bugs.launchpad.net/bugs/1856574 Title: removal of various autopilot packages Status in autopilot-gtk package in Ubuntu: In Progress Status in autopilot-legacy package in Ubuntu: Fix Released Status in python-fixtures package in Ubuntu: Fix Released Status in python-testtools package in Ubuntu: Fix Released Bug description: python-fixtures and python-testtools are not built anymore in focal, but still referenced by some Ubuntu-only packages. We need to at least remove autopilot-legacy if we don't want to re-introduce those package, and modify autopilot-gtk to build witout the autopilot-legacy b-d. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1856574/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Same issue here with Bose QC35 II and Thinkpad X1 Extreme (2nd gen). Audio profile works just fine, but headset does not play any sound and the microphone does not get any input. It was like this already in April and currently on a fresh install of 20.04. -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1891158] Re: riscv64 build - hang at the end of the build with hanging "dbus-test-runner"
The problem is Ubuntu only, as [1] is good. And the real fix should be in dbus-test-runner, but without repro it will be unclear if anyone gets to that or if we just hope it resolves itslef (again). But due to the above it makes no sense to submit the fix to Debian - as for them it would reduce test coverage. [1]: https://buildd.debian.org/status/fetch.php?pkg=dee=riscv64=1.2.7%2B17.10.20170616-6%2Bb1=1591129930=0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dee in Ubuntu. https://bugs.launchpad.net/bugs/1891158 Title: riscv64 build - hang at the end of the build with hanging "dbus-test- runner" Status in dbus-test-runner package in Ubuntu: New Status in dee package in Ubuntu: Confirmed Bug description: The builds for riscv64 on e.g. https://launchpad.net/ubuntu/+source/dee/1.2.7+17.10.20170616-6build1 hang eventually. All other architectures work fine. Build log tail will be like: ... symlinking changelog.Debian.gz in dee-tools to file in libdee-1.0-4 pkgstripfiles: Running PNG optimization (using 8 cpus) for package dee-tools ... pkgstripfiles: No PNG files. dpkg-deb: building package 'dee-tools' in '../dee-tools_1.2.7+17.10.20170616-6build1_riscv64.deb'. pkgstriptranslations: libdee-1.0-4-dbgsym does not contain translations, skipping pkgstriptranslations: no translation files, not creating tarball pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com pkgstripfiles: processing control file: debian/.debhelper/libdee-1.0-4/dbgsym-root/DEBIAN/control, package libdee-1.0-4-dbgsym, directory debian/.debhelper/libdee-1.0-4/dbgsym-root dpkg-deb: building package 'libdee-1.0-4-dbgsym' in 'debian/.debhelper/scratch-space/build-libdee-1.0-4/libdee-1.0-4-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb'. Renaming libdee-1.0-4-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb to libdee-1.0-4-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.ddeb pkgstriptranslations: dee-tools-dbgsym does not contain translations, skipping pkgstriptranslations: no translation files, not creating tarball pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com pkgstripfiles: processing control file: debian/.debhelper/dee-tools/dbgsym-root/DEBIAN/control, package dee-tools-dbgsym, directory debian/.debhelper/dee-tools/dbgsym-root dpkg-deb: building package 'dee-tools-dbgsym' in 'debian/.debhelper/scratch-space/build-dee-tools/dee-tools-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb'. Renaming dee-tools-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb to dee-tools-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.ddeb dpkg-genbuildinfo --build=any dpkg-genchanges --build=any -mLaunchpad Build Daemon >../dee_1.2.7+17.10.20170616-6build1_riscv64.changes dpkg-genchanges: info: binary-only arch-specific upload (source code and arch-indep packages not included) dpkg-source --after-build . dpkg-buildpackage: info: binary-only upload (no source included) Then it will be stuck until at 24h a timeout will reap the builder. It turned out (thanks cjwatson) that on these systems there is a leftover process Zombie schroot process Looks like there's a dbus-daemon process still running in the background of the build that the build didn't clean up properly buildd481987 0.0 0.0 5244 2780 ?SAug10 0:00 dbus-daemon --config-file /usr/share/dbus-test-runner/session.conf --print-address # ls -l /proc/481987/cwd lrwxrwxrwx 1 buildd buildd 0 Aug 11 10:08 /proc/481987/cwd -> /home/buildd/build-PACKAGEBUILD-19646792/chroot-autobuild/build/dee-1HAMJl/dee-1.2.7+17.10.20170616/tests On #ubuntu-devel we discussed this and agreed that we should not just retry until it slips through by accident, we might never be able to build it again. Instead we should try looking for what actually hangs on riscv64 and why. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-test-runner/+bug/1891158/+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 1891158] Re: riscv64 build - hang at the end of the build with hanging "dbus-test-runner"
https://launchpad.net/ubuntu/+source/dee/1.2.7+17.10.20170616-6ubuntu1 build fine now. It depends on ICU, but otherwise is ready to go now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dee in Ubuntu. https://bugs.launchpad.net/bugs/1891158 Title: riscv64 build - hang at the end of the build with hanging "dbus-test- runner" Status in dbus-test-runner package in Ubuntu: New Status in dee package in Ubuntu: Confirmed Bug description: The builds for riscv64 on e.g. https://launchpad.net/ubuntu/+source/dee/1.2.7+17.10.20170616-6build1 hang eventually. All other architectures work fine. Build log tail will be like: ... symlinking changelog.Debian.gz in dee-tools to file in libdee-1.0-4 pkgstripfiles: Running PNG optimization (using 8 cpus) for package dee-tools ... pkgstripfiles: No PNG files. dpkg-deb: building package 'dee-tools' in '../dee-tools_1.2.7+17.10.20170616-6build1_riscv64.deb'. pkgstriptranslations: libdee-1.0-4-dbgsym does not contain translations, skipping pkgstriptranslations: no translation files, not creating tarball pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com pkgstripfiles: processing control file: debian/.debhelper/libdee-1.0-4/dbgsym-root/DEBIAN/control, package libdee-1.0-4-dbgsym, directory debian/.debhelper/libdee-1.0-4/dbgsym-root dpkg-deb: building package 'libdee-1.0-4-dbgsym' in 'debian/.debhelper/scratch-space/build-libdee-1.0-4/libdee-1.0-4-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb'. Renaming libdee-1.0-4-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb to libdee-1.0-4-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.ddeb pkgstriptranslations: dee-tools-dbgsym does not contain translations, skipping pkgstriptranslations: no translation files, not creating tarball pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com pkgstripfiles: processing control file: debian/.debhelper/dee-tools/dbgsym-root/DEBIAN/control, package dee-tools-dbgsym, directory debian/.debhelper/dee-tools/dbgsym-root dpkg-deb: building package 'dee-tools-dbgsym' in 'debian/.debhelper/scratch-space/build-dee-tools/dee-tools-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb'. Renaming dee-tools-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb to dee-tools-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.ddeb dpkg-genbuildinfo --build=any dpkg-genchanges --build=any -mLaunchpad Build Daemon >../dee_1.2.7+17.10.20170616-6build1_riscv64.changes dpkg-genchanges: info: binary-only arch-specific upload (source code and arch-indep packages not included) dpkg-source --after-build . dpkg-buildpackage: info: binary-only upload (no source included) Then it will be stuck until at 24h a timeout will reap the builder. It turned out (thanks cjwatson) that on these systems there is a leftover process Zombie schroot process Looks like there's a dbus-daemon process still running in the background of the build that the build didn't clean up properly buildd481987 0.0 0.0 5244 2780 ?SAug10 0:00 dbus-daemon --config-file /usr/share/dbus-test-runner/session.conf --print-address # ls -l /proc/481987/cwd lrwxrwxrwx 1 buildd buildd 0 Aug 11 10:08 /proc/481987/cwd -> /home/buildd/build-PACKAGEBUILD-19646792/chroot-autobuild/build/dee-1HAMJl/dee-1.2.7+17.10.20170616/tests On #ubuntu-devel we discussed this and agreed that we should not just retry until it slips through by accident, we might never be able to build it again. Instead we should try looking for what actually hangs on riscv64 and why. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-test-runner/+bug/1891158/+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 1886886] Re: Plymouth 0.9.5 release
FYI - the original bug would be tackled once https://launchpad.net/ubuntu/+source/plymouth/0.9.5-0ubuntu2 migrates -- 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/1886886 Title: Plymouth 0.9.5 release Status in plymouth package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: New Bug description: Plymouth 0.9.5 release: https://www.freedesktop.org/software/plymouth/releases/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1886886/+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 1886886] Re: Plymouth 0.9.5 release
[17:48] rbalint: I was checking the systemd autopkgtests which were flaky retries and which were real issues [17:48] rbalint: and it seems all were flaky (most resolved now and src:audit in the queue to be tested) [17:49] rbalint: but one remained - plymouth - that seemed to be a genuine issue and I found https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1886886/comments/2 [17:49] Launchpad bug 1886886 in plymouth (Ubuntu) "Plymouth 0.9.5 release" [Wishlist,Fix committed] [17:49] I wanted to ask what became of this and if you could update the bug if something was e.g. added to systemd/245.7-1ubuntu1 for it [19:35] cpaelzer, seb128 i plan adding a fix to next systemd upload, will update the bug, too Thanks for the FYI - adding here a systemd task and marking it update- excuse ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags added: update-excuse -- 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/1886886 Title: Plymouth 0.9.5 release Status in plymouth package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: New Bug description: Plymouth 0.9.5 release: https://www.freedesktop.org/software/plymouth/releases/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1886886/+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
