[Touch-packages] [Bug 1889479] Re: [groovy] "performance" cpufreq governor has a big impact on CPU consumption
** Description changed: Hello, TL;DR the default cpufreq governor is now "performance" instead of "powersave" since ondemand service is no longer shipped with systemd. + First, thank you for maintaining systemd in Ubuntu! - First, thank you for maintaining systemd in Ubuntu? + I am using Ubuntu Devel on my daily laptop (Dell XPS 13 9730). For a few + weeks now, I noticed the fans of my laptop were more regularly active + and running at a higher speed. I took some time to investigate the + issue, suspecting some apps using more resources or dust causing issues. - I am using Ubuntu Devel on my daily laptop. For a few weeks now, I - noticed the fans of my laptop were more regularly active and running at - a higher speed. I took some time to investigate the issue, suspecting - some apps using more resources or dust causing issues. - - But it started to annoy me and I noticed CPU frequencies were often high: >3.5GHz while not doing intensive use, e.g. having a terminal, note app, chat, a browser with a few active tabs for email, calendar, etc. but no video, etc. I didn't change what I am usually doing with my laptop and I am connected to a remote server via SSH for dev tasks. + But it started to annoy me and I noticed CPU frequencies were often high: >3.5GHz while not doing intensive use, e.g. having a terminal, note app, chat, a browser with a few active tabs for email, calendar, etc. but no video, etc. In total the resources the CPU usage was around 50 to 100 out of 800%. I didn't really change what I am usually doing with my laptop compared to a few months ago -- I even enabled more hardware accelerations working pretty well -- and I am connected to a remote server via SSH for dev tasks. Also, the temperature of the CPU cores were often around 70°C or more according to s-tui and sensors. - == Investigation == My CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz When investigating the issue, I saw the CPU frequencies were often high, I looked at the cpufreq governor and it was set to performance: - $ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor | sort -u - performance + $ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor | sort -u + performance Setting it to "powersave" helped to reduce the CPU freq from ~3.5GHz to - ~2.4GHz when using the laptop with the battery: + ~2.4GHz for the same utilisation with the battery: - # cpupower frequency-set --governor powersave - (...) - # cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor | sort -u - powersave + # cpupower frequency-set --governor powersave + (...) + # cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor | sort -u + powersave Reducing also the temperature by the same occasion. - With TLP, the CPU freq are now around 800MHz when using the battery - while still being quite reactive and increasing when needed. I - understand it's certainly something many people would not like to have - by default. But it is interesting to try for those who want to reduce + After that I tried TLP. I didn't really need it in the past but I wanted + to see the new behaviour. The CPU freq are now around 800MHz when using + the battery doing the same as before while still being quite reactive + and increasing when needed. I understand it's certainly something many + people would not like to have by default. But it is interesting to try + for those who want to reduce Increasing the CPU consumptions has of course an impact on the energy but also the comfort because of the noise of the fans can do when running at high speed and the time you can use your device on battery. - But also and because of the higher temperature, the battery and other - components could have issues and the CPU clock is regularly throttled - while not doing much: + Of course, because of the higher temperature, the battery and other + components are more likely to run into issues and the CPU clock is + regularly throttled while not doing much: - (...) - [39948.392090] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 45107) - [39948.392091] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 45107) - [39948.392127] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 45107) - [39948.392128] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 45107) - [39948.392129] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 45107) - [39948.392130] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 45107) - [39948.392131] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 45107) - [39948.392132] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 45107) - ## there are a lot more - (...) + (...) +
[Touch-packages] [Bug 1889422] Re: Touchpad moves the cursor very slowly on ASUS F82Q
You might want to report the issue upstream at: https://gitlab.freedesktop.org/groups/libinput/-/issues ** Package changed: xorg (Ubuntu) => xserver-xorg-input-libinput (Ubuntu) ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1889422 Title: Touchpad moves the cursor very slowly on ASUS F82Q Status in libinput package in Ubuntu: New Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: Previously, I used ubuntu 18.04 or earlier versions on this old laptop without this problem. When I was installing ubuntu 20.04 from a USB stick, I noticed that the touchpad moved the cursor very slowly -- so slow that I had never seen before. The system is dual boot. In the other OS, the touchpad works fine. To show the problem I have prepared two short videos (see the file cursor-speed.zip). As can be seen in the videos, in both the "mouse speed" and "touchpad speed" are deliberately set to the minimum in "Mouse and Touchpad" settings. And in both I try to stop the video recorder as fast as I can. These two videos compare the speed of mouse with that of touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 18:07:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] InstallationDate: Installed on 2020-04-19 (100 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) MachineType: ASUSTeK Computer Inc. F82Q ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ad3f3a2c-64bc-415b-b70c-4da2b1dbf0af ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F82Q dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd05/19/2009:svnASUSTeKComputerInc.:pnF82Q:pvr1.0:rvnASUSTeKComputerInc.:rnF82Q:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: F82Q dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1889422/+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 1881976] Re: apport-gtk and apport-kde install xiterm+thai as dependency (x-terminal-emulator)
This bug was fixed in the package apport - 2.20.11-0ubuntu43 --- apport (2.20.11-0ubuntu43) groovy; urgency=medium * d/control: Offer real package alternatives along with x-terminal-server for apport-gtk and apport-kde (LP: #1881976). -- Dariusz Gadomski Thu, 23 Jul 2020 08:52:46 +0200 ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1881976 Title: apport-gtk and apport-kde install xiterm+thai as dependency (x -terminal-emulator) Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: In Progress Bug description: [Impact] * When installing apport-gtk (or apport-kde) on a non-GUI installation (cloud image, server image) as a dependency providing x-terminal-emulator xiterm+thai package is pulled in, which is not appropriate for most locales. My understanding is it was selected due to lowest number of unsatisfied dependencies. [Test Case] * lxc launch ubuntu:20.04 test * lxc shell test * apt update * apt install apport-gtk * Examine the packages listed to be installed: xiterm+thai is one of them. [Regression Potential] * In dedicated archive mirrors with limited number of packages changing that may cause errors due to packages missing in the archive. However, that's unlikely. [Other Info] * It is not affecting bionic, since x-terminal-emulator is listed as 'Suggests' not 'Depends' there. * Original bug description: Vanilla install of Ubuntu 20.04 set to an Australian locale includes the "Thai X Terminal" package. This package should not be included. I noticed that it is also reported against Xubuntu and Lubuntu: https://bugs.launchpad.net/lubuntu-next/+bug/1747341 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881976/+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
** Description changed: [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 ucm-implement-CardNumberByName-substitution.patch ucm-fix-the-possible-buffer-overflow-substitution.patch ucm-simplify-get_by_card-in-parser.c.patch ucm-implement-AlwaysTrue-Condition.Type.patch ucm-Allow-empty-strings-in-var-.-substitutions.patch ucm-substitution-remove-duplicate-allow_empty-assign.patch ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch ucm-substitute-the-merged-tree-completely.patch - + add Depends alsa-ucm-conf (>= 1.2.2-1ubuntu0.1.1) in the d/control + add snd_config_is_array@ALSA_0.9 1.2.2-2.1ubuntu1 in the d/libasound2.symbols [Test Case] On the AMD renoir machines: Boot the system with these updated packages (already backported kernel drivers to focal and oem-5.6 kernels), open the gnome-control-center, we could see the digital mic in the input device tab, and only one input
[Touch-packages] [Bug 1888992] Re: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones
I reverted that commit in the kernel of #16. So let me think about how to fix it. thx. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1888992 Title: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones Status in alsa-driver package in Ubuntu: New Bug description: I boot my system without any sound devices plugged into any jacks; checking Gnome settings Sound, Output Device is "Dummy Output" (no other options available in drop-down list). I plug in headphones into the front jack and play some audio, but do not hear any sound from the headphones; checking Gnome settings Sound, the Output Device is still "Dummy Output", with no other options available. This is a regression from previous behaviour, when plugging in headphones into the front jack would automatically enable/switch to the front jack and its associated controller "Family 17h (Models 00h- 0fh) HD Audio Controller" (this is the motherboard's onboard audio hardware). I can currently workaround this each time I plug in the headphones by installing and running pavucontrol, and under Configuration selecting "Analogue Stereo Output (unplugged) (unavailable)" - this option becomes "Analogue Stereo Output" after I select it. This seems to be a regression in pulseaudio after an upgrade from from 1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chinf 1741 F pulseaudio /dev/snd/pcmC1D0p: chinf 1741 F...m pulseaudio /dev/snd/controlC0: chinf 1741 F pulseaudio /dev/snd/timer: chinf 1741 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 12:46:52 2020 InstallationDate: Installed on 2018-10-29 (635 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chinf 1741 F pulseaudio /dev/snd/controlC0: chinf 1741 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1888992/+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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)
Mine today was an ad for micro k8s on macos. Seriously? This has nothing whatsoever to do with my server. I will look into blocking this at the firewall. -- 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/1701068 Title: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu) Status in base-files package in Ubuntu: Opinion Bug description: In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50 -motd-news that reads https://motd.ubuntu.com/ and displays that text with the rest of the MOTD. Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon Valley which has a reference to Ubuntu. Instead, https://motd.ubuntu.com should show relevant items to those that use Ubuntu Server (relevant security issues, etc), instead of items for desktop users. = Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow, Keras & React Native on Ubuntu - https://ubu.one/HBOubu == ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed Jun 28 12:31:24 2017 InstallationDate: Installed on 2017-05-02 (56 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: base-files UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+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 1889297] Re: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb
The failing autopkgtest is in the 'upstream' tests (search for 'TEST RUN: Job-related tests' twice.) It's very probably unrelated: apparently the testsuite.service ended unexpectedly, due to a SIGCHLD because the sleep.service (the child iiuic) got a SIGTERM unexpectedly too, and finished. According to the systemd journal in the artifacts. Just trigerred a re-run since that has no relation with kmod. -- 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/1889297 Title: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb Status in kmod package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in kmod source package in Bionic: Fix Committed Status in systemd source package in Bionic: In Progress Bug description: [Impact] * debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb. * This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. * See the '[Details]' section for the details. :) [Fix] * That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic. Just revert it. * There is no need to "fix" this in Eoan and later (debhelper >= 12.3) * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.) [Test Case] * Try to build debian-installer on Bionic; it FTBFS: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. * Check if libkmod2's shlibs file contains an udeb line: $ dpkg-deb --control libkmod2__.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb # this is good. [Regression Potential] * The fix only changes the libkmod2's shlibs file to include an udeb line (so udebs that depend on that library package should depend on the -udeb package.) Thus the regression potential is limited to the installer, and the udeb packages which depend on libkmod2 (udev-udeb only, probably.) Regressions could be seen as failures to load libkmod2.so and/or not finding its dynamic symbols. * There is a no-change rebuild of systemd involved/required, so some dependency updates may potentially impact systemd. [Details] debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. kmod (24-1ubuntu3.3) bionic; urgency=medium <...> * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) <...> From dh_makeshlibs(1): --add-udeb=udeb Create an additional line for udebs in the shlibs file and use udeb as the package name for udebs to depend on instead of the regular library package. Before: $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb libkmod2-u32-control $ cat libkmod2-u32-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends: Depends: ..., libkmod2-udeb, ... After: $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb libkmod2-u33-control $ cat libkmod2-u33-control/shlibs libkmod 2 libkmod2 $ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends: Depends: ..., libkmod2, ... That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic: Eoan: $ dpkg -s debhelper | grep Version: Version: 12.6.1ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!? make: *** [debian/rules:120: .stamp-binary] Error 255 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Bionic: $ dpkg -s debhelper | grep Version: Version: 11.1.6ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_shlibdeps -- --warnings=7 <...> dpkg-buildpackage:
[Touch-packages] [Bug 1889479] [NEW] [groovy] "performance" cpufreq governor has a big impact on CPU consumption
Public bug reported: Hello, TL;DR the default cpufreq governor is now "performance" instead of "powersave" since ondemand service is no longer shipped with systemd. First, thank you for maintaining systemd in Ubuntu? I am using Ubuntu Devel on my daily laptop. For a few weeks now, I noticed the fans of my laptop were more regularly active and running at a higher speed. I took some time to investigate the issue, suspecting some apps using more resources or dust causing issues. But it started to annoy me and I noticed CPU frequencies were often high: >3.5GHz while not doing intensive use, e.g. having a terminal, note app, chat, a browser with a few active tabs for email, calendar, etc. but no video, etc. I didn't change what I am usually doing with my laptop and I am connected to a remote server via SSH for dev tasks. Also, the temperature of the CPU cores were often around 70°C or more according to s-tui and sensors. == Investigation == My CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz When investigating the issue, I saw the CPU frequencies were often high, I looked at the cpufreq governor and it was set to performance: $ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor | sort -u performance Setting it to "powersave" helped to reduce the CPU freq from ~3.5GHz to ~2.4GHz when using the laptop with the battery: # cpupower frequency-set --governor powersave (...) # cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor | sort -u powersave Reducing also the temperature by the same occasion. With TLP, the CPU freq are now around 800MHz when using the battery while still being quite reactive and increasing when needed. I understand it's certainly something many people would not like to have by default. But it is interesting to try for those who want to reduce Increasing the CPU consumptions has of course an impact on the energy but also the comfort because of the noise of the fans can do when running at high speed and the time you can use your device on battery. But also and because of the higher temperature, the battery and other components could have issues and the CPU clock is regularly throttled while not doing much: (...) [39948.392090] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 45107) [39948.392091] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 45107) [39948.392127] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 45107) [39948.392128] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 45107) [39948.392129] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 45107) [39948.392130] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 45107) [39948.392131] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 45107) [39948.392132] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 45107) ## there are a lot more (...) Regarding the throttle, it was better after having applied: https://github.com/erpalma/throttled But at the end, the temperature was increasing even more: around 80°C when charging the battery and when doing a bit more activities (e.g. webrtc conf call). == Bisect == I tried to understand if it is normal to have "performance" by default. The kernel config didn't change recently (CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y) but then I found this: https://salsa.debian.org/systemd- team/systemd/-/commit/65f46a7d14b335e5743350dbbc5b5ef1e72826f7 It looks like "ondemand" service is no longer shipped with systemd. According to Dan, it is not needed and not used by other distributions. But then I wonder if other distributions are maybe applying other kernel config not to use the full power as quickly as it was in my case. For example, do they also have CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y? On Fedora, for the kernel 5.7, I see ONDEMAND is used by default: https://git.kernel.org/pub/scm/linux/kernel/git/jwboyer/fedora.git/tree/fedora/configs/kernel-5.7.11-x86_64.config?h=f32=b192daedbdefafedac87d825df77ea92d3f4c697#n589 In conclusion, is it a good idea to have "performance" as default cpufreq governor on a desktop? (or others) ** Affects: systemd (Ubuntu) Importance: Undecided Status: 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/1889479 Title: [groovy] "performance" cpufreq governor has a big impact on CPU consumption Status in systemd package in Ubuntu: New Bug description: Hello, TL;DR the default cpufreq governor is now "performance" instead of "powersave" since ondemand service is no longer shipped with systemd. First, thank you for maintaining systemd in Ubuntu? I am using
[Touch-packages] [Bug 1889297] Autopkgtest regression report (kmod/24-1ubuntu3.5)
All autopkgtests for the newly accepted kmod (24-1ubuntu3.5) for bionic have finished running. The following regressions have been reported in tests triggered by the package: systemd/237-3ubuntu10.41 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#kmod [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1889297 Title: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb Status in kmod package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in kmod source package in Bionic: Fix Committed Status in systemd source package in Bionic: In Progress Bug description: [Impact] * debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb. * This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. * See the '[Details]' section for the details. :) [Fix] * That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic. Just revert it. * There is no need to "fix" this in Eoan and later (debhelper >= 12.3) * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.) [Test Case] * Try to build debian-installer on Bionic; it FTBFS: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. * Check if libkmod2's shlibs file contains an udeb line: $ dpkg-deb --control libkmod2__.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb # this is good. [Regression Potential] * The fix only changes the libkmod2's shlibs file to include an udeb line (so udebs that depend on that library package should depend on the -udeb package.) Thus the regression potential is limited to the installer, and the udeb packages which depend on libkmod2 (udev-udeb only, probably.) Regressions could be seen as failures to load libkmod2.so and/or not finding its dynamic symbols. * There is a no-change rebuild of systemd involved/required, so some dependency updates may potentially impact systemd. [Details] debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. kmod (24-1ubuntu3.3) bionic; urgency=medium <...> * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) <...> From dh_makeshlibs(1): --add-udeb=udeb Create an additional line for udebs in the shlibs file and use udeb as the package name for udebs to depend on instead of the regular library package. Before: $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb libkmod2-u32-control $ cat libkmod2-u32-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends: Depends: ..., libkmod2-udeb, ... After: $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb libkmod2-u33-control $ cat libkmod2-u33-control/shlibs libkmod 2 libkmod2 $ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends: Depends: ..., libkmod2, ... That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic: Eoan: $ dpkg -s debhelper | grep Version: Version: 12.6.1ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!? make: *** [debian/rules:120: .stamp-binary] Error 255 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Bionic: $ dpkg -s debhelper | grep Version: Version: 11.1.6ubuntu2 $
[Touch-packages] [Bug 1881972] Re: systemd-networkd crashes with invalid pointer
** Changed in: systemd (Ubuntu Bionic)
Status: Incomplete => In Progress
--
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/1881972
Title:
systemd-networkd crashes with invalid pointer
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
In Progress
Bug description:
[impact]
systemd-networkd double-free causes crash under some circumstances,
such as adding/removing ip rules
[test case]
Use networkd-dispatcher events to add and remove IP rules. The example
scripts below are contrived (and by themselves likely to break access
to a machine) but would be adequate to trigger the bug. Put scripts
like these in place, reboot or run "netplan apply", and then leave the
machine running for a few DHCP renewal cycles.
=== /etc/networkd-dispatcher/configured.d/test.sh ===
#!/bin/bash
/sbin/ip rule add iif lo lookup 99
/sbin/ip rule add to 10.0.0.0/8 iif lo lookup main
=== END ===
=== /etc/networkd-dispatcher/configuring.d/test.sh ===
#!/bin/bash
# Tear down existing ip rules so they aren't duplicated
OLDIFS="${IFS}"
IFS="
"
for rule in `ip rule show|grep "iif lo" | cut -d: -f2-`; do
IFS="${OLDIFS}"
ip rule delete ${rule}
done
IFS="${OLDIFS}"
=== END ===
[regression potential]
this strdup's strings during addition of routing policy rules, so any
regression would likely occur when adding/modifying/removing ip rules,
possibly including networkd segfault or failure to add/remove/modify
ip rules.
[scope]
this is needed for bionic.
this is fixed by upstream commit
eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c which is included starting in
v240, so this is already included in Focal and later.
I did not research what original commit introduced the problem, but
the reporter indicates this did not happen for Xenial so it's unlikely
this is a problem in Xenial or earlier.
[original description]
This is a serious regression with systemd-networkd that I ran in to
while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-
ssd/ubuntu-bionic-18.04-amd64-server-20200131 with
systemd-237-3ubuntu10.33 does NOT have the problem, but the next most
recent AWS AMI ubuntu/images/hvm-ssd/ubuntu-
bionic-18.04-amd64-server-20200311 with systemd-including
237-3ubuntu10.39 does.
Also, a system booted from the (good) 20200131 AMI starts showing the
problem after updating only systemd (to 237-3ubuntu10.41) and its
direct dependencies (e.g. 'apt-get install systemd'). So I'm fairly
confident that a change to the systemd package between
237-3ubuntu10.33 and 237-3ubuntu10.39 introduced the problem and it is
still present.
On the NAT router I use three interfaces and have separate routing
tables for admin and forwarded traffic. Things come up fine initially
but every 30-60 minutes (DHCP lease renewal time?) one or more
interfaces is reconfigured and most of the time systemd-networkd will
crash and need to be restarted. Eventually the system becomes
unreachable when the default crash loop backoff logic prevents the
network service from being restarted at all. The log excerpt attached
illustrates the crash loop.
Also including the netplan and networkd config files below.
# grep . /etc/netplan/*
/etc/netplan/50-cloud-init.yaml:# This file is generated from information
provided by the datasource. Changes
/etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance
reboot. To disable cloud-init's
/etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a
file
/etc/netplan/50-cloud-init.yaml:#
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
/etc/netplan/50-cloud-init.yaml:# network: {config: disabled}
/etc/netplan/50-cloud-init.yaml:network:
/etc/netplan/50-cloud-init.yaml:version: 2
/etc/netplan/50-cloud-init.yaml:ethernets:
/etc/netplan/50-cloud-init.yaml:ens5:
/etc/netplan/50-cloud-init.yaml:dhcp4: true
/etc/netplan/50-cloud-init.yaml:match:
/etc/netplan/50-cloud-init.yaml:macaddress: xx:xx:xx:xx:xx:xx
/etc/netplan/50-cloud-init.yaml:set-name: ens5
/etc/netplan/99_config.yaml:network:
/etc/netplan/99_config.yaml: version: 2
/etc/netplan/99_config.yaml: renderer: networkd
/etc/netplan/99_config.yaml: ethernets:
/etc/netplan/99_config.yaml:ens6:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: yy:yy:yy:yy:yy:yy
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-routes: false
/etc/netplan/99_config.yaml:ens7:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: zz:zz:zz:zz:zz:zz
[Touch-packages] [Bug 1881972] Re: systemd-networkd crashes with invalid pointer
** Description changed:
[impact]
systemd-networkd double-free causes crash under some circumstances, such
as adding/removing ip rules
[test case]
- see original description
+ Use networkd-dispatcher events to add and remove IP rules. The example
+ scripts below are contrived (and by themselves likely to break access to
+ a machine) but would be adequate to trigger the bug. Put scripts like
+ these in place, reboot or run "netplan apply", and then leave the
+ machine running for a few DHCP renewal cycles.
+
+ === /etc/networkd-dispatcher/configured.d/test.sh ===
+ #!/bin/bash
+
+ /sbin/ip rule add iif lo lookup 99
+ /sbin/ip rule add to 10.0.0.0/8 iif lo lookup main
+ === END ===
+ === /etc/networkd-dispatcher/configuring.d/test.sh ===
+ #!/bin/bash
+
+ # Tear down existing ip rules so they aren't duplicated
+ OLDIFS="${IFS}"
+ IFS="
+ "
+ for rule in `ip rule show|grep "iif lo" | cut -d: -f2-`; do
+ IFS="${OLDIFS}"
+ ip rule delete ${rule}
+ done
+ IFS="${OLDIFS}"
+ === END ===
[regression potential]
this strdup's strings during addition of routing policy rules, so any
regression would likely occur when adding/modifying/removing ip rules,
possibly including networkd segfault or failure to add/remove/modify ip
rules.
[scope]
this is needed for bionic.
this is fixed by upstream commit
eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c which is included starting in
v240, so this is already included in Focal and later.
I did not research what original commit introduced the problem, but the
reporter indicates this did not happen for Xenial so it's unlikely this
is a problem in Xenial or earlier.
[original description]
This is a serious regression with systemd-networkd that I ran in to
while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-ssd
/ubuntu-bionic-18.04-amd64-server-20200131 with systemd-237-3ubuntu10.33
does NOT have the problem, but the next most recent AWS AMI
ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20200311 with
systemd-including 237-3ubuntu10.39 does.
Also, a system booted from the (good) 20200131 AMI starts showing the
problem after updating only systemd (to 237-3ubuntu10.41) and its direct
dependencies (e.g. 'apt-get install systemd'). So I'm fairly confident
that a change to the systemd package between 237-3ubuntu10.33 and
237-3ubuntu10.39 introduced the problem and it is still present.
On the NAT router I use three interfaces and have separate routing
tables for admin and forwarded traffic. Things come up fine initially
but every 30-60 minutes (DHCP lease renewal time?) one or more
interfaces is reconfigured and most of the time systemd-networkd will
crash and need to be restarted. Eventually the system becomes
unreachable when the default crash loop backoff logic prevents the
network service from being restarted at all. The log excerpt attached
illustrates the crash loop.
Also including the netplan and networkd config files below.
# grep . /etc/netplan/*
/etc/netplan/50-cloud-init.yaml:# This file is generated from information
provided by the datasource. Changes
/etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance
reboot. To disable cloud-init's
/etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a
file
/etc/netplan/50-cloud-init.yaml:#
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
/etc/netplan/50-cloud-init.yaml:# network: {config: disabled}
/etc/netplan/50-cloud-init.yaml:network:
/etc/netplan/50-cloud-init.yaml:version: 2
/etc/netplan/50-cloud-init.yaml:ethernets:
/etc/netplan/50-cloud-init.yaml:ens5:
/etc/netplan/50-cloud-init.yaml:dhcp4: true
/etc/netplan/50-cloud-init.yaml:match:
/etc/netplan/50-cloud-init.yaml:macaddress: xx:xx:xx:xx:xx:xx
/etc/netplan/50-cloud-init.yaml:set-name: ens5
/etc/netplan/99_config.yaml:network:
/etc/netplan/99_config.yaml: version: 2
/etc/netplan/99_config.yaml: renderer: networkd
/etc/netplan/99_config.yaml: ethernets:
/etc/netplan/99_config.yaml:ens6:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: yy:yy:yy:yy:yy:yy
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-routes: false
/etc/netplan/99_config.yaml:ens7:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: zz:zz:zz:zz:zz:zz
/etc/netplan/99_config.yaml: mtu: 1500
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-mtu: false
/etc/netplan/99_config.yaml:use-routes: false
# grep . /etc/networkd-dispatcher/*/*
/etc/networkd-dispatcher/configured.d/nat:#!/bin/bash
[Touch-packages] [Bug 1832754] Re: "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs.
> So how do you intend to complete this SRU if there is no test case for verifying? intermittent issues frequently are not easily reproducable, and sometimes require specific system configuration that can't be completely identified and duplicated, even by those experiencing the bug. Expecting all SRUs to have a reproducer is a noble goal, but unrealistic. I suppose you could reject this upload and leave the bug in systemd in Bionic? Although it would probably be more useful to have a review of the code change instead of simply rejecting any fix for lack of a clear reproducer. ** Changed in: systemd (Ubuntu Bionic) Status: Incomplete => In Progress -- 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/1832754 Title: "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: [impact] shutdown sometimes fails to unmount some fs, which causes shutdown hang [test case] it's unclear what the specific configuration is to be able to reproduce this, but there are some examples in the upstream bug [regression potential] as this adjusts shutdown umounting, any regression would likely involve either failure to unmount some filesystems on shutdown and/or failure to shutdown the system. [scope] this is needed for b. this is fixed upstream by PR 8429 which is included starting in v239, so this is fixed already in Focal and later. this was caused by upstream commit d5641e0d7e8 which was added in v236, so this bug is not present in x. [original description] I am using Xubuntu 18.04 64 bit and got "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. systemd: 237-3ubuntu10.22 It's this issue: https://github.com/systemd/systemd/issues/8155 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832754/+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 1881972] Re: systemd-networkd crashes with invalid pointer
@r-2ohn-d please do write up a test case for @vorlon, thanks
--
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/1881972
Title:
systemd-networkd crashes with invalid pointer
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Incomplete
Bug description:
[impact]
systemd-networkd double-free causes crash under some circumstances,
such as adding/removing ip rules
[test case]
see original description
[regression potential]
this strdup's strings during addition of routing policy rules, so any
regression would likely occur when adding/modifying/removing ip rules,
possibly including networkd segfault or failure to add/remove/modify
ip rules.
[scope]
this is needed for bionic.
this is fixed by upstream commit
eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c which is included starting in
v240, so this is already included in Focal and later.
I did not research what original commit introduced the problem, but
the reporter indicates this did not happen for Xenial so it's unlikely
this is a problem in Xenial or earlier.
[original description]
This is a serious regression with systemd-networkd that I ran in to
while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-
ssd/ubuntu-bionic-18.04-amd64-server-20200131 with
systemd-237-3ubuntu10.33 does NOT have the problem, but the next most
recent AWS AMI ubuntu/images/hvm-ssd/ubuntu-
bionic-18.04-amd64-server-20200311 with systemd-including
237-3ubuntu10.39 does.
Also, a system booted from the (good) 20200131 AMI starts showing the
problem after updating only systemd (to 237-3ubuntu10.41) and its
direct dependencies (e.g. 'apt-get install systemd'). So I'm fairly
confident that a change to the systemd package between
237-3ubuntu10.33 and 237-3ubuntu10.39 introduced the problem and it is
still present.
On the NAT router I use three interfaces and have separate routing
tables for admin and forwarded traffic. Things come up fine initially
but every 30-60 minutes (DHCP lease renewal time?) one or more
interfaces is reconfigured and most of the time systemd-networkd will
crash and need to be restarted. Eventually the system becomes
unreachable when the default crash loop backoff logic prevents the
network service from being restarted at all. The log excerpt attached
illustrates the crash loop.
Also including the netplan and networkd config files below.
# grep . /etc/netplan/*
/etc/netplan/50-cloud-init.yaml:# This file is generated from information
provided by the datasource. Changes
/etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance
reboot. To disable cloud-init's
/etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a
file
/etc/netplan/50-cloud-init.yaml:#
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
/etc/netplan/50-cloud-init.yaml:# network: {config: disabled}
/etc/netplan/50-cloud-init.yaml:network:
/etc/netplan/50-cloud-init.yaml:version: 2
/etc/netplan/50-cloud-init.yaml:ethernets:
/etc/netplan/50-cloud-init.yaml:ens5:
/etc/netplan/50-cloud-init.yaml:dhcp4: true
/etc/netplan/50-cloud-init.yaml:match:
/etc/netplan/50-cloud-init.yaml:macaddress: xx:xx:xx:xx:xx:xx
/etc/netplan/50-cloud-init.yaml:set-name: ens5
/etc/netplan/99_config.yaml:network:
/etc/netplan/99_config.yaml: version: 2
/etc/netplan/99_config.yaml: renderer: networkd
/etc/netplan/99_config.yaml: ethernets:
/etc/netplan/99_config.yaml:ens6:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: yy:yy:yy:yy:yy:yy
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-routes: false
/etc/netplan/99_config.yaml:ens7:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: zz:zz:zz:zz:zz:zz
/etc/netplan/99_config.yaml: mtu: 1500
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-mtu: false
/etc/netplan/99_config.yaml:use-routes: false
# grep . /etc/networkd-dispatcher/*/*
/etc/networkd-dispatcher/configured.d/nat:#!/bin/bash
/etc/networkd-dispatcher/configured.d/nat:# Do additional configuration for
the inside and outside interfaces
/etc/networkd-dispatcher/configured.d/nat:# route table used for
forwarded/routed/natted traffic
/etc/networkd-dispatcher/configured.d/nat:FWD_TABLE=99
/etc/networkd-dispatcher/configured.d/nat:if [ "${IFACE}" = "ens6" ]; then
/etc/networkd-dispatcher/configured.d/nat: # delete link-local route for
inside in default table
[Touch-packages] [Bug 1888992] Re: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones
Thank you for following up. I have managed to complete a commit bisect of the Ubuntu kernels and can confirm that the first bad commit is 851cc40f47677174527a1decbd1074feacd15a93: ALSA: hda: call runtime_allow() for all hda controllers BugLink: https://bugs.launchpad.net/bugs/1876765 [ Upstream commit 9a6418487b566503c772cb6e7d3d44e652b019b0 ] Regarding #15: I have tested and can confirm that "options snd_hda_intel power_save_controller=0" is also a valid workaround. Regarding #16: I have reverted the workarounds, booted the test kernel and can confirm that this also fixes my detection problem. ** Attachment added: "git bisect output" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1888992/+attachment/5397069/+files/commit_bisect_first_bad.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1888992 Title: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones Status in alsa-driver package in Ubuntu: New Bug description: I boot my system without any sound devices plugged into any jacks; checking Gnome settings Sound, Output Device is "Dummy Output" (no other options available in drop-down list). I plug in headphones into the front jack and play some audio, but do not hear any sound from the headphones; checking Gnome settings Sound, the Output Device is still "Dummy Output", with no other options available. This is a regression from previous behaviour, when plugging in headphones into the front jack would automatically enable/switch to the front jack and its associated controller "Family 17h (Models 00h- 0fh) HD Audio Controller" (this is the motherboard's onboard audio hardware). I can currently workaround this each time I plug in the headphones by installing and running pavucontrol, and under Configuration selecting "Analogue Stereo Output (unplugged) (unavailable)" - this option becomes "Analogue Stereo Output" after I select it. This seems to be a regression in pulseaudio after an upgrade from from 1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chinf 1741 F pulseaudio /dev/snd/pcmC1D0p: chinf 1741 F...m pulseaudio /dev/snd/controlC0: chinf 1741 F pulseaudio /dev/snd/timer: chinf 1741 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 12:46:52 2020 InstallationDate: Installed on 2018-10-29 (635 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chinf 1741 F pulseaudio /dev/snd/controlC0: chinf 1741 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1888992/+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 1881972] Re: systemd-networkd crashes with invalid pointer
The scripts for configured.d and configuring.d to add and remove IP
rules (included above) are likely the culprit. @ddstreet would you like
me to write that up more compactly?
--
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/1881972
Title:
systemd-networkd crashes with invalid pointer
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Incomplete
Bug description:
[impact]
systemd-networkd double-free causes crash under some circumstances,
such as adding/removing ip rules
[test case]
see original description
[regression potential]
this strdup's strings during addition of routing policy rules, so any
regression would likely occur when adding/modifying/removing ip rules,
possibly including networkd segfault or failure to add/remove/modify
ip rules.
[scope]
this is needed for bionic.
this is fixed by upstream commit
eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c which is included starting in
v240, so this is already included in Focal and later.
I did not research what original commit introduced the problem, but
the reporter indicates this did not happen for Xenial so it's unlikely
this is a problem in Xenial or earlier.
[original description]
This is a serious regression with systemd-networkd that I ran in to
while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-
ssd/ubuntu-bionic-18.04-amd64-server-20200131 with
systemd-237-3ubuntu10.33 does NOT have the problem, but the next most
recent AWS AMI ubuntu/images/hvm-ssd/ubuntu-
bionic-18.04-amd64-server-20200311 with systemd-including
237-3ubuntu10.39 does.
Also, a system booted from the (good) 20200131 AMI starts showing the
problem after updating only systemd (to 237-3ubuntu10.41) and its
direct dependencies (e.g. 'apt-get install systemd'). So I'm fairly
confident that a change to the systemd package between
237-3ubuntu10.33 and 237-3ubuntu10.39 introduced the problem and it is
still present.
On the NAT router I use three interfaces and have separate routing
tables for admin and forwarded traffic. Things come up fine initially
but every 30-60 minutes (DHCP lease renewal time?) one or more
interfaces is reconfigured and most of the time systemd-networkd will
crash and need to be restarted. Eventually the system becomes
unreachable when the default crash loop backoff logic prevents the
network service from being restarted at all. The log excerpt attached
illustrates the crash loop.
Also including the netplan and networkd config files below.
# grep . /etc/netplan/*
/etc/netplan/50-cloud-init.yaml:# This file is generated from information
provided by the datasource. Changes
/etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance
reboot. To disable cloud-init's
/etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a
file
/etc/netplan/50-cloud-init.yaml:#
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
/etc/netplan/50-cloud-init.yaml:# network: {config: disabled}
/etc/netplan/50-cloud-init.yaml:network:
/etc/netplan/50-cloud-init.yaml:version: 2
/etc/netplan/50-cloud-init.yaml:ethernets:
/etc/netplan/50-cloud-init.yaml:ens5:
/etc/netplan/50-cloud-init.yaml:dhcp4: true
/etc/netplan/50-cloud-init.yaml:match:
/etc/netplan/50-cloud-init.yaml:macaddress: xx:xx:xx:xx:xx:xx
/etc/netplan/50-cloud-init.yaml:set-name: ens5
/etc/netplan/99_config.yaml:network:
/etc/netplan/99_config.yaml: version: 2
/etc/netplan/99_config.yaml: renderer: networkd
/etc/netplan/99_config.yaml: ethernets:
/etc/netplan/99_config.yaml:ens6:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: yy:yy:yy:yy:yy:yy
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-routes: false
/etc/netplan/99_config.yaml:ens7:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: zz:zz:zz:zz:zz:zz
/etc/netplan/99_config.yaml: mtu: 1500
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-mtu: false
/etc/netplan/99_config.yaml:use-routes: false
# grep . /etc/networkd-dispatcher/*/*
/etc/networkd-dispatcher/configured.d/nat:#!/bin/bash
/etc/networkd-dispatcher/configured.d/nat:# Do additional configuration for
the inside and outside interfaces
/etc/networkd-dispatcher/configured.d/nat:# route table used for
forwarded/routed/natted traffic
/etc/networkd-dispatcher/configured.d/nat:FWD_TABLE=99
/etc/networkd-dispatcher/configured.d/nat:if [ "${IFACE}" = "ens6" ]; then
[Touch-packages] [Bug 1881972] Re: systemd-networkd crashes with invalid pointer
"see original description" is inadequate as a test case. I am reading
the original description and it does not describe a step-by-step
reproducer.
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => Incomplete
--
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/1881972
Title:
systemd-networkd crashes with invalid pointer
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Incomplete
Bug description:
[impact]
systemd-networkd double-free causes crash under some circumstances,
such as adding/removing ip rules
[test case]
see original description
[regression potential]
this strdup's strings during addition of routing policy rules, so any
regression would likely occur when adding/modifying/removing ip rules,
possibly including networkd segfault or failure to add/remove/modify
ip rules.
[scope]
this is needed for bionic.
this is fixed by upstream commit
eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c which is included starting in
v240, so this is already included in Focal and later.
I did not research what original commit introduced the problem, but
the reporter indicates this did not happen for Xenial so it's unlikely
this is a problem in Xenial or earlier.
[original description]
This is a serious regression with systemd-networkd that I ran in to
while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-
ssd/ubuntu-bionic-18.04-amd64-server-20200131 with
systemd-237-3ubuntu10.33 does NOT have the problem, but the next most
recent AWS AMI ubuntu/images/hvm-ssd/ubuntu-
bionic-18.04-amd64-server-20200311 with systemd-including
237-3ubuntu10.39 does.
Also, a system booted from the (good) 20200131 AMI starts showing the
problem after updating only systemd (to 237-3ubuntu10.41) and its
direct dependencies (e.g. 'apt-get install systemd'). So I'm fairly
confident that a change to the systemd package between
237-3ubuntu10.33 and 237-3ubuntu10.39 introduced the problem and it is
still present.
On the NAT router I use three interfaces and have separate routing
tables for admin and forwarded traffic. Things come up fine initially
but every 30-60 minutes (DHCP lease renewal time?) one or more
interfaces is reconfigured and most of the time systemd-networkd will
crash and need to be restarted. Eventually the system becomes
unreachable when the default crash loop backoff logic prevents the
network service from being restarted at all. The log excerpt attached
illustrates the crash loop.
Also including the netplan and networkd config files below.
# grep . /etc/netplan/*
/etc/netplan/50-cloud-init.yaml:# This file is generated from information
provided by the datasource. Changes
/etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance
reboot. To disable cloud-init's
/etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a
file
/etc/netplan/50-cloud-init.yaml:#
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
/etc/netplan/50-cloud-init.yaml:# network: {config: disabled}
/etc/netplan/50-cloud-init.yaml:network:
/etc/netplan/50-cloud-init.yaml:version: 2
/etc/netplan/50-cloud-init.yaml:ethernets:
/etc/netplan/50-cloud-init.yaml:ens5:
/etc/netplan/50-cloud-init.yaml:dhcp4: true
/etc/netplan/50-cloud-init.yaml:match:
/etc/netplan/50-cloud-init.yaml:macaddress: xx:xx:xx:xx:xx:xx
/etc/netplan/50-cloud-init.yaml:set-name: ens5
/etc/netplan/99_config.yaml:network:
/etc/netplan/99_config.yaml: version: 2
/etc/netplan/99_config.yaml: renderer: networkd
/etc/netplan/99_config.yaml: ethernets:
/etc/netplan/99_config.yaml:ens6:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: yy:yy:yy:yy:yy:yy
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-routes: false
/etc/netplan/99_config.yaml:ens7:
/etc/netplan/99_config.yaml: match:
/etc/netplan/99_config.yaml:macaddress: zz:zz:zz:zz:zz:zz
/etc/netplan/99_config.yaml: mtu: 1500
/etc/netplan/99_config.yaml: dhcp4: true
/etc/netplan/99_config.yaml: dhcp4-overrides:
/etc/netplan/99_config.yaml:use-mtu: false
/etc/netplan/99_config.yaml:use-routes: false
# grep . /etc/networkd-dispatcher/*/*
/etc/networkd-dispatcher/configured.d/nat:#!/bin/bash
/etc/networkd-dispatcher/configured.d/nat:# Do additional configuration for
the inside and outside interfaces
/etc/networkd-dispatcher/configured.d/nat:# route table used for
forwarded/routed/natted traffic
/etc/networkd-dispatcher/configured.d/nat:FWD_TABLE=99
[Touch-packages] [Bug 1832754] Re: "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs.
> it's unclear what the specific configuration is to be able to reproduce this, but there are some examples in the upstream bug So how do you intend to complete this SRU if there is no test case for verifying? ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Incomplete -- 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/1832754 Title: "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Incomplete Bug description: [impact] shutdown sometimes fails to unmount some fs, which causes shutdown hang [test case] it's unclear what the specific configuration is to be able to reproduce this, but there are some examples in the upstream bug [regression potential] as this adjusts shutdown umounting, any regression would likely involve either failure to unmount some filesystems on shutdown and/or failure to shutdown the system. [scope] this is needed for b. this is fixed upstream by PR 8429 which is included starting in v239, so this is fixed already in Focal and later. this was caused by upstream commit d5641e0d7e8 which was added in v236, so this bug is not present in x. [original description] I am using Xubuntu 18.04 64 bit and got "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. systemd: 237-3ubuntu10.22 It's this issue: https://github.com/systemd/systemd/issues/8155 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832754/+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 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network
** Description changed: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [test case, pre-focal] - same netplan as above, but remove ethernets: section. Reboot, and the - bridge should have its address and route: + same netplan as above. Reboot, and the bridge should have its address + and route: ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 - link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff - inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 -valid_lft forever preferred_lft forever + link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff + inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 + valid_lft forever preferred_lft forever ubuntu@test-e:~$ ip r - default via 192.168.0.1 dev br0 proto static linkdown - 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown - + default via 192.168.0.1 dev br0 proto static linkdown + 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown add and remove carrier, by adding and removing a slave interface: ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 - link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff - inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 -valid_lft forever preferred_lft forever - inet6 fe80::5411:daff:fe23:bb93/64 scope link -valid_lft forever preferred_lft forever + link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff + inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 + valid_lft forever preferred_lft forever + inet6 fe80::5411:daff:fe23:bb93/64 scope link + valid_lft forever preferred_lft forever ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster - the bridge no longer has its address after losing carrier: ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 - link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff - inet6 fe80::5411:daff:fe23:bb93/64 scope link -valid_lft forever preferred_lft forever - + link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff + inet6 fe80::5411:daff:fe23:bb93/64 scope link + valid_lft forever preferred_lft forever [regression potential] Any regression would likely involve incorrectly configured network after an interface carrier gain/loss. [scope] This is needed for Focal, Eoan, and Bionic. While this only reproduces at boot for Focal, the general loss of configuration on carrier loss even when ConfigureWithoutCarrier=true is reproducable on all releases except Xenial, which does not have the ConfigureWithoutCarrier= parameter. [original description] Freshly installed Ubuntu 20.04 fully patched to days date with static IP address works fine and survives a reboot network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] however when converted to a bridged network for kvm network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] will not survive a reboot and required systemd-network to be restarted or @reboot /usr/sbin/netplan apply added to the crontab after a reboot the network can not b eaccseed and a systemctl status systemd-networkd produces systemd-networkd.service - Network Service
[Touch-packages] [Bug 1881976] Re: apport-gtk and apport-kde install xiterm+thai as dependency (x-terminal-emulator)
[sts-sponsor] Sponsored in active development release (groovy) ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1881976 Title: apport-gtk and apport-kde install xiterm+thai as dependency (x -terminal-emulator) Status in apport package in Ubuntu: Fix Committed Status in apport source package in Focal: In Progress Bug description: [Impact] * When installing apport-gtk (or apport-kde) on a non-GUI installation (cloud image, server image) as a dependency providing x-terminal-emulator xiterm+thai package is pulled in, which is not appropriate for most locales. My understanding is it was selected due to lowest number of unsatisfied dependencies. [Test Case] * lxc launch ubuntu:20.04 test * lxc shell test * apt update * apt install apport-gtk * Examine the packages listed to be installed: xiterm+thai is one of them. [Regression Potential] * In dedicated archive mirrors with limited number of packages changing that may cause errors due to packages missing in the archive. However, that's unlikely. [Other Info] * It is not affecting bionic, since x-terminal-emulator is listed as 'Suggests' not 'Depends' there. * Original bug description: Vanilla install of Ubuntu 20.04 set to an Australian locale includes the "Thai X Terminal" package. This package should not be included. I noticed that it is also reported against Xubuntu and Lubuntu: https://bugs.launchpad.net/lubuntu-next/+bug/1747341 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881976/+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 1889206] Re: Regression in USN-4436-1
** Changed in: librsvg (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1889206 Title: Regression in USN-4436-1 Status in librsvg: Unknown Status in librsvg package in Ubuntu: Invalid Status in librsvg source package in Xenial: Fix Released Status in librsvg source package in Bionic: Fix Released Bug description: The security fix for librsvg introduced a regression in aisleriot. Steps to reproduce: 1- install gnome-cards-data 2- run "sol" to start Aislerot 3- Switch card layout to "Anglo" 4- Notice some cards are missing graphics To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/1889206/+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 1881976] Re: apport-gtk and apport-kde install xiterm+thai as dependency (x-terminal-emulator)
[sts-sponsor] @dgadomski I don't think you can add a runtime dependency from universe to a package found in main apport-gtk | 2.20.11-0ubuntu42 | groovy konsole | 4:20.04.3-0ubuntu1 | groovy/universe This would most likely require an MIR for konsole first. https://wiki.ubuntu.com/MainInclusionProcess Dependencies: All binary dependencies (including Recommends:) must be satisfiable in main (i. e. the preferred alternative must be in main). If not, these dependencies need a separate MIR report (this can be a separate bug or another task on the main MIR bug) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1881976 Title: apport-gtk and apport-kde install xiterm+thai as dependency (x -terminal-emulator) Status in apport package in Ubuntu: In Progress Status in apport source package in Focal: In Progress Bug description: [Impact] * When installing apport-gtk (or apport-kde) on a non-GUI installation (cloud image, server image) as a dependency providing x-terminal-emulator xiterm+thai package is pulled in, which is not appropriate for most locales. My understanding is it was selected due to lowest number of unsatisfied dependencies. [Test Case] * lxc launch ubuntu:20.04 test * lxc shell test * apt update * apt install apport-gtk * Examine the packages listed to be installed: xiterm+thai is one of them. [Regression Potential] * In dedicated archive mirrors with limited number of packages changing that may cause errors due to packages missing in the archive. However, that's unlikely. [Other Info] * It is not affecting bionic, since x-terminal-emulator is listed as 'Suggests' not 'Depends' there. * Original bug description: Vanilla install of Ubuntu 20.04 set to an Australian locale includes the "Thai X Terminal" package. This package should not be included. I noticed that it is also reported against Xubuntu and Lubuntu: https://bugs.launchpad.net/lubuntu-next/+bug/1747341 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881976/+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 1889443] [NEW] "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...`
Public bug reported: The crash file I'm using is as-produced by the system (on groovy), and appears to have an empty value for separator: $ grep separator /var/crash/_usr_bin_neomutt.1000.crash separator: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu42 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:117:1620030:2020-07-29 12:16:57.045274496 -0400:2020-07-29 12:19:15.559243636 -0400:/var/crash/_usr_bin_neomutt.1000.crash 640:1000:117:4399480:2020-07-23 10:30:21.433552906 -0400:2020-07-23 10:30:18.921508067 -0400:/var/crash/_usr_bin_pavucontrol.1000.crash 640:1000:117:29909:2020-07-29 12:19:15.603244279 -0400:2020-07-29 12:19:15.603244279 -0400:/var/crash/_usr_bin_apport-unpack.1000.crash CurrentDesktop: i3 Date: Wed Jul 29 12:22:54 2020 InstallationDate: Installed on 2019-05-07 (448 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to groovy on 2020-06-22 (37 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1889443 Title: "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...` Status in apport package in Ubuntu: New Bug description: The crash file I'm using is as-produced by the system (on groovy), and appears to have an empty value for separator: $ grep separator /var/crash/_usr_bin_neomutt.1000.crash separator: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu42 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:117:1620030:2020-07-29 12:16:57.045274496 -0400:2020-07-29 12:19:15.559243636 -0400:/var/crash/_usr_bin_neomutt.1000.crash 640:1000:117:4399480:2020-07-23 10:30:21.433552906 -0400:2020-07-23 10:30:18.921508067 -0400:/var/crash/_usr_bin_pavucontrol.1000.crash 640:1000:117:29909:2020-07-29 12:19:15.603244279 -0400:2020-07-29 12:19:15.603244279 -0400:/var/crash/_usr_bin_apport-unpack.1000.crash CurrentDesktop: i3 Date: Wed Jul 29 12:22:54 2020 InstallationDate: Installed on 2019-05-07 (448 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to groovy on 2020-06-22 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1889443/+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 1889442] Re: package linux-firmware 1.187.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1889442 Title: package linux-firmware 1.187.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: The machine is a virtual machine in Virtualbox 6.1.12 with a Windows 10 Pro 1903 host. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zenmiser 2402 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jul 29 19:07:25 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-28 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_a7m4fw@/vmlinuz-5.4.0-42-generic root=ZFS=rpool/ROOT/ubuntu_a7m4fw ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 RfKill: SourcePackage: initramfs-tools Title: package linux-firmware 1.187.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1889442/+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 1889442] [NEW] package linux-firmware 1.187.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: The machine is a virtual machine in Virtualbox 6.1.12 with a Windows 10 Pro 1903 host. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zenmiser 2402 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jul 29 19:07:25 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-28 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_a7m4fw@/vmlinuz-5.4.0-42-generic root=ZFS=rpool/ROOT/ubuntu_a7m4fw ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 RfKill: SourcePackage: initramfs-tools Title: package linux-firmware 1.187.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1889442 Title: package linux-firmware 1.187.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: The machine is a virtual machine in Virtualbox 6.1.12 with a Windows 10 Pro 1903 host. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zenmiser 2402 F pulseaudio CasperMD5CheckResult: skip Date: Wed Jul 29 19:07:25 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-28 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_a7m4fw@/vmlinuz-5.4.0-42-generic root=ZFS=rpool/ROOT/ubuntu_a7m4fw ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails:
[Touch-packages] [Bug 1831467] Re: test-umockdev tests flaky on armhf (and sometimes other archs)
https://salsa.debian.org/debian/umockdev/-/commit/87b476aee2 should hopefully help. I uploaded 0.14.2 to Debian unstable now, it should auto-sync into Groovy soon. Thanks Dan for tackling this! ** Changed in: umockdev (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to umockdev in Ubuntu. https://bugs.launchpad.net/bugs/1831467 Title: test-umockdev tests flaky on armhf (and sometimes other archs) Status in umockdev package in Ubuntu: Fix Committed Status in umockdev source package in Xenial: In Progress Status in umockdev source package in Bionic: In Progress Status in umockdev source package in Focal: In Progress Status in umockdev source package in Groovy: Fix Committed Bug description: [impact] these tests fail intermittently, due to various timing issues, as well as an actual code bug in how data fuzz is calculated. it looks like the failures are mostly on armhf, but do happen less often on other archs. [test case] check the previous autopkgtest logs, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/umockdev/20190601_015323_8f795@/log.gz [regression potential] any regression would likely result in incorrectly failing/passing autopkgtests, or in a incorrect pass or incorrect fail of the ScriptRunner to verify the data's level of fuzz. [scope] as the tests are flaky on armhf all the way back to trusty, this is needed for all releases. [other info] Fixed upstream in PR https://github.com/martinpitt/umockdev/pull/103 Most of the changes are test case fixes, but there is one fix to source code to fix the ScriptRunning function that validates the level of fuzz in data, so this is not *only* a testcase fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1831467/+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 1889297] Re: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb
Verification done on bionic-proposed. The shlibs file of libkmod2 contains the udeb line: $ pull-lp-debs libkmod2 bionic $ dpkg-deb --control libkmod2_24-1ubuntu3.5_amd64.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb Then building systemd in a PPA with proposed enabled does result in udev-udeb depending on libkmod2-udeb: Build log: ... Get:51 http://ftpmaster.internal/ubuntu bionic-proposed/main amd64 libkmod2 amd64 24-1ubuntu3.5 [40.2 kB] ... Package: udev-udeb ... Depends: libblkid1-udeb (>= 2.31), libc6-udeb (>= 2.27), libkmod2-udeb, util-linux-udeb ... ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1889297 Title: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb Status in kmod package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in kmod source package in Bionic: Fix Committed Status in systemd source package in Bionic: In Progress Bug description: [Impact] * debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb. * This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. * See the '[Details]' section for the details. :) [Fix] * That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic. Just revert it. * There is no need to "fix" this in Eoan and later (debhelper >= 12.3) * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.) [Test Case] * Try to build debian-installer on Bionic; it FTBFS: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. * Check if libkmod2's shlibs file contains an udeb line: $ dpkg-deb --control libkmod2__.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb # this is good. [Regression Potential] * The fix only changes the libkmod2's shlibs file to include an udeb line (so udebs that depend on that library package should depend on the -udeb package.) Thus the regression potential is limited to the installer, and the udeb packages which depend on libkmod2 (udev-udeb only, probably.) Regressions could be seen as failures to load libkmod2.so and/or not finding its dynamic symbols. * There is a no-change rebuild of systemd involved/required, so some dependency updates may potentially impact systemd. [Details] debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. kmod (24-1ubuntu3.3) bionic; urgency=medium <...> * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) <...> From dh_makeshlibs(1): --add-udeb=udeb Create an additional line for udebs in the shlibs file and use udeb as the package name for udebs to depend on instead of the regular library package. Before: $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb libkmod2-u32-control $ cat libkmod2-u32-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends: Depends: ..., libkmod2-udeb, ... After: $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb libkmod2-u33-control $ cat libkmod2-u33-control/shlibs libkmod 2 libkmod2 $ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends: Depends: ..., libkmod2, ... That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic: Eoan: $ dpkg -s debhelper | grep Version: Version: 12.6.1ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!? make: *** [debian/rules:120:
[Touch-packages] [Bug 1884265] Re: [fips] ntpq segfaults when attempting to use MD5 from FIPS-openssl library.
I have verified it for Bionic using ntp 1:4.2.8p10+dfsg-5ubuntu7.2.
No segfault observed:
sudo ntpq -p
remote refid st t when poll reach delay offset jitter
==
0.ubuntu.pool.n .POOL. 16 p - 64 0 0.000 0.000 0.000
1.ubuntu.pool.n .POOL. 16 p - 64 0 0.000 0.000 0.000
2.ubuntu.pool.n .POOL. 16 p - 64 0 0.000 0.000 0.000
3.ubuntu.pool.n .POOL. 16 p - 64 0 0.000 0.000 0.000
ntp.ubuntu.com .POOL. 16 p - 64 0 0.000 0.000 0.000
+tel50.oa.uj.edu 149.156.70.75 2 u 6 64 1 14.404 0.782 0.386
*SunSITE.icm.edu 210.100.177.101 2 u 5 64 1 12.239 0.138 0.645
(...)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1884265
Title:
[fips] ntpq segfaults when attempting to use MD5 from FIPS-openssl
library.
Status in ntp package in Ubuntu:
New
Status in openssl package in Ubuntu:
Fix Released
Status in ntp source package in Bionic:
Fix Committed
Status in openssl source package in Bionic:
In Progress
Bug description:
[Impact]
In FIPS mode on Bionic MD5 is semi-disabled causing some applications to
segfault.
ntpq uses crypto hashes to authenticate its requests. By default it
uses md5. However, when compiled with openssl it creates a lists of
acceptable hashes from openssl that can be used.
This issue is only applicable in bionic and when using fips-openssl.
[Test Steps]
Test case:
sudo apt install ntp
ntpq -p
Segmentation fault (core dumped)
What happens there is ntpq wants to iterate all available digests
(list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
task.
EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
For FIPS mode it adds:
EVP_add_digest(EVP_md5());
What happens later in ntpq is (list_md_fn function inside ntpq.c):
ctx = EVP_MD_CTX_new();
EVP_DigestInit(ctx, EVP_get_digestbyname(name));
EVP_DigestFinal(ctx, digest, _len);
First digest it gets is MD5, but while running EVP_DigestInit for it, it gets
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
#ifdef OPENSSL_FIPS
if (FIPS_mode()) {
if (!(type->flags & EVP_MD_FLAG_FIPS)
&& !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
return 0;
}
}
#endif
Due to type->flags for MD5 being 0 there's an error set
(EVP_R_DISABLED_FOR_FIPS).
After getting back to ntpq.c:
ctx->engine and ctx->digest are not set (due to the mentioned error), hence
inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
causes a segfault (ctx->digest is NULL).
So either MD5 shouldn't be added in FIPS mode or it should have the
EVP_MD_FLAG_FIPS to be properly initialized.
[Regression Potential]
I don't think this should regress ntpq + openssl from the Ubuntu
archive.
Current archive ntpq + openssl behaviour:
openssl includes all message digests and hands ntpq a sorted digest-list.
ntpq doesn't check return from EVP_Digest(Init|Final) and assumes all is well
and sticks all digests into its list regardless if it is working or not.
i.e.
ntpq> help keytype
function: set key type to use for authenticated requests, one of:
MD4, MD5, RIPEMD160, SHA1, SHAKE128
If somehow openssl library is corrupted and sends back erroneous
results, its possible the authentication will just not ever work.
Newly fixed archive ntpq + oenssl beahviour:
openssl includes all message digests and hands ntpq a sorted digest-list.
ntpq checks each one and includes each working digest. With a non-corrupted
openssl, everything works fine and ntpq includes each into its list. Ends up
with a list identical to the one above.
If somehow opensll library is corrupted and sends back erroneous
results, ntpq will hopefully catch it by checking return code and
include only those algos that appear to be working. Its possible
authentication will work for ntpq.
The difference will be seen in ntpq + fips-openssl. ntpq will check
return, and for fips-not-approved algos, return will indicate an
error. So these algos will be skipped and ntpq will not include into
its digest list. Resulting in a much shorter list of only fips-
approved algos.
i.e.
ntpq> help keytype
function: set key type to use for authenticated requests, one of:
SHA1, SHAKE128
Since md5 is ntpq's default auth algo, this will need to be changed to one of
the above algos in the config files.
But I think it is somewhat understood that MD5 is bad in a FIPS environment.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1884265/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post
[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
This bug was fixed in the package bcache-tools - 1.0.8-4ubuntu1 --- bcache-tools (1.0.8-4ubuntu1) groovy; urgency=medium [ Ryan Harper ] * Revert "Keep symlinks when udev changes /dev/bcacheN" * Add helper script to read bcache devs superblock (LP: #1861941) -- Rafael David Tinoco Thu, 23 Jul 2020 00:14:31 + ** Changed in: bcache-tools (Ubuntu) Status: In Progress => 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Status in bcache-tools source package in Focal: In Progress Status in systemd source package in Focal: In Progress Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1884265] Re: [fips] ntpq segfaults when attempting to use MD5 from FIPS-openssl library.
I have verified it for Bionic using ntp 1:4.2.8p10+dfsg-5ubuntu7.2.
No segfault observed:
sudo ntpq -p
remote refid st t when poll reach delay offset jitter
==
0.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000
1.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000
2.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000
3.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000
ntp.ubuntu.com .POOL. 16 p- 6400.0000.000 0.000
+tel50.oa.uj.edu 149.156.70.752 u6 641 14.4040.782 0.386
*SunSITE.icm.edu 210.100.177.101 2 u5 641 12.2390.138 0.645
+46.175.224.7.ma 178.252.19.225 3 u5 641 35.6070.018 0.661
+news-archive.ic 229.30.220.210 2 u3 6419.9420.135 0.761
-afrodyta.comple 210.100.177.101 2 u1 641 14.6961.299 0.648
ntp11.kashra-se 192.168.100.15 2 u1 641 35.386 -3.146 0.297
-time.taken.pl 80.50.231.2262 u1 6419.1331.390 0.282
-ntp.tktelekom.p 80.50.231.2262 u1 6418.8390.079 0.569
-ntp.wide-net.pl 194.146.251.101 2 u4 641 16.7390.559 0.324
-icemen.pl 17.253.52.2532 u4 641 34.257 -0.985 0.550
96-7.cpe.smnt.p 5.226.98.186 2 u- 641 14.709 -0.850 0.860
-ntp.ifj.edu.pl 213.222.200.99 2 u2 641 30.4639.168 0.457
pugot.canonical 17.253.34.1252 u 13 641 41.787 -3.423 0.000
ntp2.tktelekom. 212.160.106.226 2 u- 6419.2110.220 0.907
alphyn.canonica 132.163.97.1 2 u 12 641 113.404 -3.408 0.000
time.cloudflare 10.71.10.44 3 u- 641 23.523 -1.134 0.748
golem.canonical 140.203.204.77 2 u 11 641 41.912 -2.097 0.00
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1884265
Title:
[fips] ntpq segfaults when attempting to use MD5 from FIPS-openssl
library.
Status in ntp package in Ubuntu:
New
Status in openssl package in Ubuntu:
Fix Released
Status in ntp source package in Bionic:
Fix Committed
Status in openssl source package in Bionic:
In Progress
Bug description:
[Impact]
In FIPS mode on Bionic MD5 is semi-disabled causing some applications to
segfault.
ntpq uses crypto hashes to authenticate its requests. By default it
uses md5. However, when compiled with openssl it creates a lists of
acceptable hashes from openssl that can be used.
This issue is only applicable in bionic and when using fips-openssl.
[Test Steps]
Test case:
sudo apt install ntp
ntpq -p
Segmentation fault (core dumped)
What happens there is ntpq wants to iterate all available digests
(list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
task.
EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
For FIPS mode it adds:
EVP_add_digest(EVP_md5());
What happens later in ntpq is (list_md_fn function inside ntpq.c):
ctx = EVP_MD_CTX_new();
EVP_DigestInit(ctx, EVP_get_digestbyname(name));
EVP_DigestFinal(ctx, digest, _len);
First digest it gets is MD5, but while running EVP_DigestInit for it, it gets
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
#ifdef OPENSSL_FIPS
if (FIPS_mode()) {
if (!(type->flags & EVP_MD_FLAG_FIPS)
&& !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
return 0;
}
}
#endif
Due to type->flags for MD5 being 0 there's an error set
(EVP_R_DISABLED_FOR_FIPS).
After getting back to ntpq.c:
ctx->engine and ctx->digest are not set (due to the mentioned error), hence
inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
causes a segfault (ctx->digest is NULL).
So either MD5 shouldn't be added in FIPS mode or it should have the
EVP_MD_FLAG_FIPS to be properly initialized.
[Regression Potential]
I don't think this should regress ntpq + openssl from the Ubuntu
archive.
Current archive ntpq + openssl behaviour:
openssl includes all message digests and hands ntpq a sorted digest-list.
ntpq doesn't check return from EVP_Digest(Init|Final) and assumes all is well
and sticks all digests into its list regardless if it is working or not.
i.e.
ntpq> help keytype
function: set key type to use for authenticated requests, one of:
MD4, MD5, RIPEMD160, SHA1, SHAKE128
If
[Touch-packages] [Bug 1889297] Re: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb
Hello Mauricio, or anyone else affected, Accepted kmod into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kmod/24-1ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: kmod (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1889297 Title: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb Status in kmod package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in kmod source package in Bionic: Fix Committed Status in systemd source package in Bionic: In Progress Bug description: [Impact] * debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb. * This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. * See the '[Details]' section for the details. :) [Fix] * That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic. Just revert it. * There is no need to "fix" this in Eoan and later (debhelper >= 12.3) * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.) [Test Case] * Try to build debian-installer on Bionic; it FTBFS: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. * Check if libkmod2's shlibs file contains an udeb line: $ dpkg-deb --control libkmod2__.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb # this is good. [Regression Potential] * The fix only changes the libkmod2's shlibs file to include an udeb line (so udebs that depend on that library package should depend on the -udeb package.) Thus the regression potential is limited to the installer, and the udeb packages which depend on libkmod2 (udev-udeb only, probably.) Regressions could be seen as failures to load libkmod2.so and/or not finding its dynamic symbols. * There is a no-change rebuild of systemd involved/required, so some dependency updates may potentially impact systemd. [Details] debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. kmod (24-1ubuntu3.3) bionic; urgency=medium <...> * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) <...> From dh_makeshlibs(1): --add-udeb=udeb Create an additional line for udebs in the shlibs file and use udeb as the package name for udebs to depend on instead of the regular library package. Before: $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb libkmod2-u32-control $ cat libkmod2-u32-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends: Depends: ..., libkmod2-udeb, ... After: $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb libkmod2-u33-control $ cat libkmod2-u33-control/shlibs libkmod 2
[Touch-packages] [Bug 1888685] Re: rsync fails after installing level 3.2.1
No differences between /home/cliff/Bin and /mnt/testrsync (0755) both owned by cliff:cliff. In building my test cast wanted to duplicated the target directories as much as I could. No I use the systemctl start/stop rsync so the answer is the daemon is running under root. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1888685 Title: rsync fails after installing level 3.2.1 Status in rsync package in Ubuntu: Incomplete Bug description: After installation of rsync.3.2.1 my attempt to sync fails with chroot error. The rsyncd.log indicates that rsync can't find the directories I want to sync. 2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 873 2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings failed: No such file or directory (2) Dropping back to Ubuntu 20.04 and rsync works again. The rsync update was install 7/18. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: rsync 3.2.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 10:28:17 2020 InstallationDate: Installed on 2020-07-06 (16 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+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 1889416] Re: pulseaudio.service: Start request repeated too quickly.
Bug fixed if I move pam_systemd.so below pam_fscrypt.so in /etc/pam.d /common-session. Need to fix /usr/share/pam-configs/systemd so that pam_systemd.so always end up after libpam_fscrypt (and potentially everything else...) ** Package changed: pulseaudio (Ubuntu) => systemd (Ubuntu) ** Also affects: fscrypt (Ubuntu) Importance: Undecided Status: 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/1889416 Title: pulseaudio.service: Start request repeated too quickly. Status in fscrypt package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago TriggeredBy: ● pulseaudio.socket Main PID: 5675 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service... Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nafallo5675 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 15:11:28 2020 InstallationDate: Installed on 2018-06-27 (763 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1889416/+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 1889416] Re: pulseaudio.service: Start request repeated too quickly.
Or possibly we need to fix this with fscrypt being before other additional modules. Adding both systemd and fscrypt on the bug :-) -- 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/1889416 Title: pulseaudio.service: Start request repeated too quickly. Status in fscrypt package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago TriggeredBy: ● pulseaudio.socket Main PID: 5675 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service... Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nafallo5675 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 15:11:28 2020 InstallationDate: Installed on 2018-06-27 (763 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1889416/+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 1889425] Re: new version breaks gnome solitaire
*** This bug is a duplicate of bug 1889206 *** https://bugs.launchpad.net/bugs/1889206 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1889206, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Changed in: librsvg (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1889206 Regression in USN-4436-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1889425 Title: new version breaks gnome solitaire Status in librsvg package in Ubuntu: New Bug description: Updated to 2.40.13-3ubuntu0.1 and now gnome solitaire cards don't display properly. Anyway to install the old version 2.40.13-3 until this is fixed? Thanks, George (this is a Mint 19.3 box) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1889425/+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 1615209] Re: ip crashes after a few times adding and removing network namespaces
I also tried to reproduce the mentioned failure in a clean Xenial container with no success. Since this is an old bug and no one replied to it for years I am removing the server-next tag. ** Tags removed: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1615209 Title: ip crashes after a few times adding and removing network namespaces Status in iproute2 package in Ubuntu: Expired Bug description: # which ip /sbin/ip # valgrind ip netns add black2 ==22804== Memcheck, a memory error detector ==22804== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==22804== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==22804== Command: ip netns add black2 ==22804== ==22804== Invalid write of size 1 ==22804==at 0x4031F43: memcpy (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==22804==by 0x8059C83: ??? (in /bin/ip) ==22804==by 0x805AF9A: netns_map_init (in /bin/ip) ==22804==by 0x805B01F: do_netns (in /bin/ip) ==22804==by 0x804DF67: ??? (in /bin/ip) ==22804==by 0x804DA11: main (in /bin/ip) ==22804== Address 0x4227094 is 0 bytes after a block of size 28 alloc'd ==22804==at 0x402D17C: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==22804==by 0x8059C5E: ??? (in /bin/ip) ==22804==by 0x805AF9A: netns_map_init (in /bin/ip) ==22804==by 0x805B01F: do_netns (in /bin/ip) ==22804==by 0x804DF67: ??? (in /bin/ip) ==22804==by 0x804DA11: main (in /bin/ip) ==22804== Cannot create namespace file "/var/run/netns/black2": File exists ==22804== ==22804== HEAP SUMMARY: ==22804== in use at exit: 28 bytes in 1 blocks ==22804== total heap usage: 2 allocs, 1 frees, 32,824 bytes allocated ==22804== ==22804== LEAK SUMMARY: ==22804==definitely lost: 0 bytes in 0 blocks ==22804==indirectly lost: 0 bytes in 0 blocks ==22804== possibly lost: 0 bytes in 0 blocks ==22804==still reachable: 28 bytes in 1 blocks ==22804== suppressed: 0 bytes in 0 blocks ==22804== Rerun with --leak-check=full to see details of leaked memory ==22804== ==22804== For counts of detected and suppressed errors, rerun with: -v ==22804== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1615209/+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 1831467] Re: test-umockdev tests flaky on armhf (and sometimes other archs)
** Description changed: [impact] - these tests fail intermittently, due to read failures when the test - expects to read data, but the umockdev 'replay' script device doesn't - provide the data to read. + these tests fail intermittently, due to various timing issues, as well + as an actual code bug in how data fuzz is calculated. - this appears to just be a timing issue, as the test expects the umockdev device to provide specific data replayed at specific times, and those times are very short (ms). Looking at the autopkgtest results: - http://autopkgtest.ubuntu.com/packages/umockdev - - it looks like the failures are mostly on armhf. + it looks like the failures are mostly on armhf, but do happen less often + on other archs. [test case] check the previous autopkgtest logs, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/umockdev/20190601_015323_8f795@/log.gz [regression potential] - the tests on armhf have been flaky ever since trusty, and people just - retry and/or ignore them; any regression would likely result in (still) - flaky tests and/or false positive or negative test results on armhf. + any regression would likely result in incorrectly failing/passing autopkgtests, or in a incorrect pass or incorrect fail of the ScriptRunner + to verify the data's level of fuzz. [scope] as the tests are flaky on armhf all the way back to trusty, this is needed for all releases. [other info] - the armhf testbeds are unfortunately "different" from all the other archs: - 1) they don't run directly in a virtual instance, they run in an armhf lxd container inside an arm64 virtual instance. - 2) all other archs get are run inside a small instance, with limited memory and 1 cpu, but the armhf tests are run in what appears to be a large instance, and the armhf container inherits the 4 cpus that the arm64 instance has. + Fixed upstream in PR https://github.com/martinpitt/umockdev/pull/103 + + Most of the changes are test case fixes, but there is one fix to source + code to fix the ScriptRunning function that validates the level of fuzz + in data, so this is not *only* a testcase fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to umockdev in Ubuntu. https://bugs.launchpad.net/bugs/1831467 Title: test-umockdev tests flaky on armhf (and sometimes other archs) Status in umockdev package in Ubuntu: In Progress Status in umockdev source package in Xenial: In Progress Status in umockdev source package in Bionic: In Progress Status in umockdev source package in Focal: In Progress Status in umockdev source package in Groovy: In Progress Bug description: [impact] these tests fail intermittently, due to various timing issues, as well as an actual code bug in how data fuzz is calculated. it looks like the failures are mostly on armhf, but do happen less often on other archs. [test case] check the previous autopkgtest logs, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/umockdev/20190601_015323_8f795@/log.gz [regression potential] any regression would likely result in incorrectly failing/passing autopkgtests, or in a incorrect pass or incorrect fail of the ScriptRunner to verify the data's level of fuzz. [scope] as the tests are flaky on armhf all the way back to trusty, this is needed for all releases. [other info] Fixed upstream in PR https://github.com/martinpitt/umockdev/pull/103 Most of the changes are test case fixes, but there is one fix to source code to fix the ScriptRunning function that validates the level of fuzz in data, so this is not *only* a testcase fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1831467/+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 1889425] [NEW] new version breaks gnome solitaire
Public bug reported: Updated to 2.40.13-3ubuntu0.1 and now gnome solitaire cards don't display properly. Anyway to install the old version 2.40.13-3 until this is fixed? Thanks, George (this is a Mint 19.3 box) ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1889425 Title: new version breaks gnome solitaire Status in librsvg package in Ubuntu: New Bug description: Updated to 2.40.13-3ubuntu0.1 and now gnome solitaire cards don't display properly. Anyway to install the old version 2.40.13-3 until this is fixed? Thanks, George (this is a Mint 19.3 box) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1889425/+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 1888685] Re: rsync fails after installing level 3.2.1
Maybe permission differences of the path to /home/cliff/Bin vs /mnt/testrsync Did you start the daemon like I did as root or under a different user? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1888685 Title: rsync fails after installing level 3.2.1 Status in rsync package in Ubuntu: Incomplete Bug description: After installation of rsync.3.2.1 my attempt to sync fails with chroot error. The rsyncd.log indicates that rsync can't find the directories I want to sync. 2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 873 2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings failed: No such file or directory (2) Dropping back to Ubuntu 20.04 and rsync works again. The rsync update was install 7/18. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: rsync 3.2.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 10:28:17 2020 InstallationDate: Installed on 2020-07-06 (16 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+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 1889416] Re: pulseaudio.service: Start request repeated too quickly.
The previous version (1:13.99.1-1ubuntu3.4) has the same problem with trying to create ~/.config/pulse before the home directory is available (in this case decrypted). The theory at the moment is that the new patch in 1:13.99.1-1ubuntu3.5 makes the code break earlier and therefor retry faster. We might want to make sure the service waits for ~/. to be available before trying to create ~/.config/pulse, at least that's my initial thinking. -- 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/1889416 Title: pulseaudio.service: Start request repeated too quickly. Status in pulseaudio package in Ubuntu: New Bug description: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago TriggeredBy: ● pulseaudio.socket Main PID: 5675 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service... Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nafallo5675 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 15:11:28 2020 InstallationDate: Installed on 2018-06-27 (763 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1889416/+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 1889422] [NEW] Touchpad moves the cursor very slowly on ASUS F82Q
Public bug reported: Previously, I used ubuntu 18.04 or earlier versions on this old laptop without this problem. When I was installing ubuntu 20.04 from a USB stick, I noticed that the touchpad moved the cursor very slowly -- so slow that I had never seen before. The system is dual boot. In the other OS, the touchpad works fine. To show the problem I have prepared two short videos (see the file cursor-speed.zip). As can be seen in the videos, in both the "mouse speed" and "touchpad speed" are deliberately set to the minimum in "Mouse and Touchpad" settings. And in both I try to stop the video recorder as fast as I can. These two videos compare the speed of mouse with that of touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 18:07:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] InstallationDate: Installed on 2020-04-19 (100 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) MachineType: ASUSTeK Computer Inc. F82Q ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ad3f3a2c-64bc-415b-b70c-4da2b1dbf0af ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F82Q dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd05/19/2009:svnASUSTeKComputerInc.:pnF82Q:pvr1.0:rvnASUSTeKComputerInc.:rnF82Q:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: F82Q dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "cursor-speed.zip" https://bugs.launchpad.net/bugs/1889422/+attachment/5396981/+files/cursor-speed.zip ** Description changed: Previously, I used ubuntu 18.04 or earlier versions on this old laptop without this problem. When I was installing ubutnu 20.04, I noticed that the touchpad moved the cursor very slowly -- so slow that I had never seen before. - To show the program I have prepared two short videos (see the file + To show the problem I have prepared two short videos (see the file sursor-speed.zip). As can be seen in the videos, in both the "mouse speed" and "touchpad speed" are set to the minimum in "Mouse and Touchpad" settings. And in both I try to stop the video recorder as fast as I can. These two videos compare the speed of mouse with that of touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 18:07:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller
[Touch-packages] [Bug 1889416] Re: pulseaudio.service: Start request repeated too quickly.
For some reason the latest update (1:3.99.1-1ubuntu3.5) break if the user has an encrypted home directory, in my case ext4 encryption. $ journalctl -xe --user-unit pulseaudio ``` -- Reboot -- Jul 29 14:59:18 wendigo systemd[2664]: Starting Sound Service... -- Subject: A start job for unit UNIT has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit UNIT has begun execution. -- -- The job identifier is 25. Jul 29 14:59:18 wendigo pulseaudio[2681]: Failed to create secure directory (/home/nafallo/.config/pulse): No such file or directory Jul 29 14:59:18 wendigo systemd[2664]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An ExecStart= process belonging to unit UNIT has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Jul 29 14:59:18 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit UNIT has entered the 'failed' state with result 'exit-code'. Jul 29 14:59:18 wendigo systemd[2664]: Failed to start Sound Service. -- Subject: A start job for unit UNIT has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit UNIT has finished with a failure. -- -- The job identifier is 25 and the job result is failed. Jul 29 14:59:18 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 1. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Automatic restarting of the unit UNIT has been scheduled, as the result for -- the configured Restart= setting for the unit. Jul 29 14:59:18 wendigo systemd[2664]: Stopped Sound Service. -- Subject: A stop job for unit UNIT has finished -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A stop job for unit UNIT has finished. -- -- The job identifier is 94 and the job result is done. ``` -- 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/1889416 Title: pulseaudio.service: Start request repeated too quickly. Status in pulseaudio package in Ubuntu: New Bug description: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago TriggeredBy: ● pulseaudio.socket Main PID: 5675 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service... Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nafallo5675 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 15:11:28 2020
[Touch-packages] [Bug 1889416] [NEW] pulseaudio.service: Start request repeated too quickly.
Public bug reported: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago TriggeredBy: ● pulseaudio.socket Main PID: 5675 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service... Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nafallo5675 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 15:11:28 2020 InstallationDate: Installed on 2018-06-27 (763 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889416 Title: pulseaudio.service: Start request repeated too quickly. Status in pulseaudio package in Ubuntu: New Bug description: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service
[Touch-packages] [Bug 1888685] Re: rsync fails after installing level 3.2.1
This doesn't seem right to me. Changed the path = Bin and the call to rsync to use the -R option which I think is to use relative path. Still fails on chroot but the rsyncd.log has the following; 2020/07/29 08:52:17 [10277] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/29 08:52:17 [10277] rsync: [Receiver] chroot /Bin failed: No such file or directory (2) The error message is correct there is no /Bin directory but the path statement indicates Bin as a relative path (ensure the test script running from /home/cliff and there is a Bin directory there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1888685 Title: rsync fails after installing level 3.2.1 Status in rsync package in Ubuntu: Incomplete Bug description: After installation of rsync.3.2.1 my attempt to sync fails with chroot error. The rsyncd.log indicates that rsync can't find the directories I want to sync. 2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 873 2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings failed: No such file or directory (2) Dropping back to Ubuntu 20.04 and rsync works again. The rsync update was install 7/18. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: rsync 3.2.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 10:28:17 2020 InstallationDate: Installed on 2020-07-06 (16 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+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 1831467] Re: test-umockdev tests flaky on armhf (and sometimes other archs)
** Also affects: umockdev (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: umockdev (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: umockdev (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: umockdev (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: umockdev (Ubuntu Groovy) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: umockdev (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: umockdev (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: umockdev (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: umockdev (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: umockdev (Ubuntu Focal) Importance: Undecided => Low ** Changed in: umockdev (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: umockdev (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: umockdev (Ubuntu Groovy) Status: New => In Progress ** Changed in: umockdev (Ubuntu Focal) Status: New => In Progress ** Changed in: umockdev (Ubuntu Bionic) Status: New => In Progress ** Changed in: umockdev (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to umockdev in Ubuntu. https://bugs.launchpad.net/bugs/1831467 Title: test-umockdev tests flaky on armhf (and sometimes other archs) Status in umockdev package in Ubuntu: In Progress Status in umockdev source package in Xenial: In Progress Status in umockdev source package in Bionic: In Progress Status in umockdev source package in Focal: In Progress Status in umockdev source package in Groovy: In Progress Bug description: [impact] these tests fail intermittently, due to read failures when the test expects to read data, but the umockdev 'replay' script device doesn't provide the data to read. this appears to just be a timing issue, as the test expects the umockdev device to provide specific data replayed at specific times, and those times are very short (ms). Looking at the autopkgtest results: http://autopkgtest.ubuntu.com/packages/umockdev it looks like the failures are mostly on armhf. [test case] check the previous autopkgtest logs, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/umockdev/20190601_015323_8f795@/log.gz [regression potential] the tests on armhf have been flaky ever since trusty, and people just retry and/or ignore them; any regression would likely result in (still) flaky tests and/or false positive or negative test results on armhf. [scope] as the tests are flaky on armhf all the way back to trusty, this is needed for all releases. [other info] the armhf testbeds are unfortunately "different" from all the other archs: 1) they don't run directly in a virtual instance, they run in an armhf lxd container inside an arm64 virtual instance. 2) all other archs get are run inside a small instance, with limited memory and 1 cpu, but the armhf tests are run in what appears to be a large instance, and the armhf container inherits the 4 cpus that the arm64 instance has. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1831467/+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 1889297] Re: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb
Finally, with the kmod change, plus the systemd rebuild, now d-i builds successfully on all archs in the PPA [1]. [1] https://launchpad.net/~mfo/+archive/ubuntu/lp1889297/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1889297 Title: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb Status in kmod package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in kmod source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Bug description: [Impact] * debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb. * This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. * See the '[Details]' section for the details. :) [Fix] * That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic. Just revert it. * There is no need to "fix" this in Eoan and later (debhelper >= 12.3) * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.) [Test Case] * Try to build debian-installer on Bionic; it FTBFS: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. * Check if libkmod2's shlibs file contains an udeb line: $ dpkg-deb --control libkmod2__.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb # this is good. [Regression Potential] * The fix only changes the libkmod2's shlibs file to include an udeb line (so udebs that depend on that library package should depend on the -udeb package.) Thus the regression potential is limited to the installer, and the udeb packages which depend on libkmod2 (udev-udeb only, probably.) Regressions could be seen as failures to load libkmod2.so and/or not finding its dynamic symbols. * There is a no-change rebuild of systemd involved/required, so some dependency updates may potentially impact systemd. [Details] debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. kmod (24-1ubuntu3.3) bionic; urgency=medium <...> * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) <...> From dh_makeshlibs(1): --add-udeb=udeb Create an additional line for udebs in the shlibs file and use udeb as the package name for udebs to depend on instead of the regular library package. Before: $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb libkmod2-u32-control $ cat libkmod2-u32-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends: Depends: ..., libkmod2-udeb, ... After: $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb libkmod2-u33-control $ cat libkmod2-u33-control/shlibs libkmod 2 libkmod2 $ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends: Depends: ..., libkmod2, ... That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic: Eoan: $ dpkg -s debhelper | grep Version: Version: 12.6.1ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!? make: *** [debian/rules:120: .stamp-binary] Error 255 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Bionic: $ dpkg -s debhelper | grep Version: Version: 11.1.6ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_shlibdeps -- --warnings=7 <...> dpkg-buildpackage: info: binary and diff upload (original source NOT included) There is no need to "fix" this in Eoan and later, as debhelper >= 12.3 has support for udeb auto-detection in dh_makeshlibs(1) -- and the udeb line is added to shlibs
[Touch-packages] [Bug 1831467] Re: test-umockdev tests flaky on armhf (and sometimes other archs)
** Summary changed: - test-umockdev tests flaky on armhf + test-umockdev tests flaky on armhf (and sometimes other archs) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to umockdev in Ubuntu. https://bugs.launchpad.net/bugs/1831467 Title: test-umockdev tests flaky on armhf (and sometimes other archs) Status in umockdev package in Ubuntu: New Status in umockdev source package in Xenial: New Status in umockdev source package in Bionic: New Status in umockdev source package in Focal: New Status in umockdev source package in Groovy: New Bug description: [impact] these tests fail intermittently, due to read failures when the test expects to read data, but the umockdev 'replay' script device doesn't provide the data to read. this appears to just be a timing issue, as the test expects the umockdev device to provide specific data replayed at specific times, and those times are very short (ms). Looking at the autopkgtest results: http://autopkgtest.ubuntu.com/packages/umockdev it looks like the failures are mostly on armhf. [test case] check the previous autopkgtest logs, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/umockdev/20190601_015323_8f795@/log.gz [regression potential] the tests on armhf have been flaky ever since trusty, and people just retry and/or ignore them; any regression would likely result in (still) flaky tests and/or false positive or negative test results on armhf. [scope] as the tests are flaky on armhf all the way back to trusty, this is needed for all releases. [other info] the armhf testbeds are unfortunately "different" from all the other archs: 1) they don't run directly in a virtual instance, they run in an armhf lxd container inside an arm64 virtual instance. 2) all other archs get are run inside a small instance, with limited memory and 1 cpu, but the armhf tests are run in what appears to be a large instance, and the armhf container inherits the 4 cpus that the arm64 instance has. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1831467/+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 1889206] Re: Regression in USN-4436-1
This bug was fixed in the package librsvg - 2.40.20-2ubuntu0.2 --- librsvg (2.40.20-2ubuntu0.2) bionic-security; urgency=medium * SECURITY UPDATE: Regression when parsing Aisleriot cards (LP: #1889206) - debian/patches/CVE-2019-20446-*.patch: removed pending a complete fix. - debian/librsvg2-2.symbols: removed symbol. -- Marc Deslauriers Tue, 28 Jul 2020 18:58:19 -0400 ** Changed in: librsvg (Ubuntu Bionic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1889206 Title: Regression in USN-4436-1 Status in librsvg: Unknown Status in librsvg package in Ubuntu: Confirmed Status in librsvg source package in Xenial: Fix Released Status in librsvg source package in Bionic: Fix Released Bug description: The security fix for librsvg introduced a regression in aisleriot. Steps to reproduce: 1- install gnome-cards-data 2- run "sol" to start Aislerot 3- Switch card layout to "Anglo" 4- Notice some cards are missing graphics To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/1889206/+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 1889206] Re: Regression in USN-4436-1
This bug was fixed in the package librsvg - 2.40.13-3ubuntu0.2 --- librsvg (2.40.13-3ubuntu0.2) xenial-security; urgency=medium * SECURITY UPDATE: Regression when parsing Aisleriot cards (LP: #1889206) - debian/patches/CVE-2019-20446-*.patch: removed pending a complete fix. - debian/librsvg2-2.symbols: removed symbol. -- Marc Deslauriers Tue, 28 Jul 2020 19:40:39 -0400 ** Changed in: librsvg (Ubuntu Xenial) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-20446 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1889206 Title: Regression in USN-4436-1 Status in librsvg: Unknown Status in librsvg package in Ubuntu: Confirmed Status in librsvg source package in Xenial: Fix Released Status in librsvg source package in Bionic: Confirmed Bug description: The security fix for librsvg introduced a regression in aisleriot. Steps to reproduce: 1- install gnome-cards-data 2- run "sol" to start Aislerot 3- Switch card layout to "Anglo" 4- Notice some cards are missing graphics To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/1889206/+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 1872118] Re: DHCP Cluster crashes after a few hours
I don't have specific recommendation on this. The best course of action would be to find a new maintainer that would update the packages to 4.4.2. The upstream (ISC) does very infrequent releases. We had 4.4.2 coming out in Jan 2020. We don't know when the next one (4.4.3) will come out, but we're no longer actively developing it. We're fixing serious bugs reported by customers (and addressing security issues if found), so the future releases are driven by that. My point here is that this isn't that much work to do. Perhaps existing maintainers could be convinced to do the package updates? Also, the alternative - ISC Kea - is much superior in many regards. It's modern, can (but doesn't have to) use MySQL, Postgres and other databases, has much better performance, is extensible with hooks, much cleaner configuration using JSON, ability to alter almost every aspect of its configuration during runtime, the dev version already support multi-threading etc. This is the ultimate solution to that problem: migrate to Kea and stop using isc-dhcp altogether. Finally, ISC provides packages for Kea for many systems, including Ubuntu. We can work with package maintainers if there are specific patches that are needed. We don't and we don't be able to do that for isc-dhcp. -- 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: DHCP Cluster crashes after a few hours Status in isc-dhcp package in Ubuntu: Confirmed Bug description: I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All worked perfectly until recently, when they started stopping with code=killed, status=6/ABRT. This is being fixed by https://bugs.launchpad.net/bugs/1870729 However now one stops after a few hours with the following errors. One can stay on line but not both. Syslog shows Apr 10 17:20:15 dhcp-primary sh[6828]: ../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, back trace Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ?? Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ?? nothing in kern.log apport.log shows ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, signal 6, core limit 0, dump mode 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid with dump mode of 2 ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: /usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf") ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report /var/crash/_usr_sbin_dhcpd.0.crash /var/crash/_usr_sbin_dhcpd.0.crash shows ProblemType: Crash Architecture: amd64 CrashCounter: 1 Date: Fri Apr 10 17:20:15 2020 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/sbin/dhcpd ExecutableTimestamp: 1586210315 ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcMaps: Error: [Errno 13] Permission denied: 'maps' ProcStatus: Name: dhcpd Umask: 0022 State: D (disk sleep) Tgid: 6828 Ngid: 0 Pid: 6828 PPid: 1 TracerPid: 0 Uid: 113 113 113 113 Gid: 118 118 118 118 FDSize:128 Groups: NStgid:6828 NSpid: 6828 NSpgid:6828 NSsid: 6828 VmPeak: 236244 kB VmSize: 170764 kB VmLck:0 kB VmPin:0 kB VmHWM:12064 kB VmRSS:12064 kB RssAnon: 5940 kB RssFile: 6124 kB RssShmem: 0 kB VmData: 30792 kB VmStk: 132 kB VmExe: 592 kB VmLib: 5424 kB VmPTE: 76 kB VmSwap: 0 kB HugetlbPages: 0 kB CoreDumping: 1 THP_enabled: 1 Threads: 4 SigQ: 0/7609 SigPnd: ShdPnd: SigBlk: SigIgn:1000 SigCgt:00018000 CapInh: CapPrm: CapEff: CapBnd:003f CapAmb: NoNewPrivs:0 Seccomp: 0 Speculation_Store_Bypass: thread vulnerable Cpus_allowed: 3 Cpus_allowed_list: 0-1 Mems_allowed:
[Touch-packages] [Bug 1888685] Re: rsync fails after installing level 3.2.1
Stumped to what to do next. Have two test cases, one works, one fails with chroot error. Here is the rsyncd.conf that workds; cat << EOF > /etc/rsyncd.conf log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid lock file = /var/run/rsync.lock [test_dir] path = /mnt/testrsync comment = Test Directory uid = cliff gid = cliff read only = no list = yes hosts allow = 192.168.1.0/24 auth users = cliff secrets file = /etc/rsyncd.scrt strict modes = false EOF cat << EOF > /etc/rsyncd.scrt cliff:ubuntu EOF The one that fails; cat << EOF > /etc/rsyncd.conf log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid lock file = /var/run/rsync.lock [Bin_dir] path = /home/cliff/Bin comment = Common Bin Directory uid = cliff gid = cliff read only = no list = yes hosts allow = 192.168.1.0/24 auth users = cliff secrets file = /etc/rsyncd.scrt strict modes = false EOF cat << EOF > /etc/rsyncd.scrt cliff:ubuntu EOF Tried to change the failure. Change the path = %HOME%/Bin - no change Added use chroot = false - the failure change to "chdir failed" Suggestion on what to try next? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1888685 Title: rsync fails after installing level 3.2.1 Status in rsync package in Ubuntu: Incomplete Bug description: After installation of rsync.3.2.1 my attempt to sync fails with chroot error. The rsyncd.log indicates that rsync can't find the directories I want to sync. 2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 873 2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings failed: No such file or directory (2) Dropping back to Ubuntu 20.04 and rsync works again. The rsync update was install 7/18. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: rsync 3.2.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 10:28:17 2020 InstallationDate: Installed on 2020-07-06 (16 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+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
** Description changed: [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] - we need to backport 3 patches: - 2ae94c141f device-port: queue CARD CHANGE event before update default sink - c8653c13fa alsa: adjust ucm sink/source priority according to ports priority - A patch not merged by upstream: + 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 + ucm-implement-CardNumberByName-substitution.patch + ucm-fix-the-possible-buffer-overflow-substitution.patch + ucm-simplify-get_by_card-in-parser.c.patch + ucm-implement-AlwaysTrue-Condition.Type.patch + ucm-Allow-empty-strings-in-var-.-substitutions.patch + ucm-substitution-remove-duplicate-allow_empty-assign.patch + ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch + ucm-substitute-the-merged-tree-completely.patch + [Test Case] On the AMD renoir machines: Boot the system with these updated packages (already backported kernel drivers to focal and oem-5.6 kernels), open the gnome-control-center, we
[Touch-packages] [Bug 1889217] Re: Make digital mic on the AMD renoir machines work under gnome desktop
** Description changed: [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. + 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] we need to backport 3 patches: 2ae94c141f device-port: queue CARD CHANGE event before update default sink c8653c13fa alsa: adjust ucm sink/source priority according to ports priority A patch not merged by upstream: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Test Case] On the AMD renoir machines: - Boot the system with these updated packages (already backported kernel drivers - to focal and oem-5.6 kernels), open the gnome-control-center, we could see - the digital mic in the input device tab, and only one input device. we could - record sound through this dmic, we could play sound through the speaker, plug - a headset, we could see the output device become headphones and the input - device become headset mic, we could play sound to headphone and record sound - from headset mic, plug a hdmi monitor, there is hdmi audio choice, play sound - to hdmi audio, we could hear the sound from the speaker on the monitor. Suspend - and resume, redo the previous steps, all audio devices still work well. + Boot the system with these updated packages (already backported kernel + drivers to focal and oem-5.6 kernels), open the gnome-control-center, + we could see the digital mic in the input device tab, and only one + input device. we could record sound through this dmic, we could play + sound through the speaker, plug a headset, we could see the output + device become headphones and the input device become headset mic, we + could play sound to headphone and record sound from headset mic, plug + a hdmi monitor, there is hdmi audio choice, play sound to hdmi audio, + we could hear the sound from the speaker on the monitor. Suspend and + resume, redo the previous steps, all audio devices still work well. On other machines: - Boot the system with all updated packages or partial updated packages, check - all input devices and output devices, they worked as the same as before. this - SRU doesn't bring any impact on other machines. + Boot the system with all updated packages or partial updated packages, + check all input devices and output devices, they worked the same as + before. this SRU doesn't bring any impact on other machines. [Regression Risk] Low + For alsa-ucm-conf, this SRU adds two new folders and only minimum + changes on existing folders, and these changes are under control and + are for supporting acp driver. + For alsa-lib, this SRU only adds the patches to support the ucm 3, and + nearly all changes are in the ucm folder. + For pulseaudio, this SRU only integrate 3 patches, and 2 of them are + for auto switching, and they are small patches and already upstreamed. + the left patch are specific to renoir audio, it will not bring impact + to other machines. + + Also, we tested these changes with below machines: + A LENOVO AMD renoir laptop, all audio function works and no regression + found + A DELL laptop with intel dmic, all audio function works and no + regression found + A DELL laptop with intel soundwire audio, all audio function works and + no regression found -- 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: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New 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: New Status in alsa-ucm-conf source package in Groovy: New Status in
[Touch-packages] [Bug 1889217] Re: Make digital mic on the AMD renoir machines work under gnome desktop
** Changed in: pulseaudio (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: alsa-ucm-conf (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: alsa-lib (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: alsa-lib (Ubuntu Groovy) Assignee: (unassigned) => Hui Wang (hui.wang) -- 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: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New 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: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New 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] we need to backport 3 patches: 2ae94c141f device-port: queue CARD CHANGE event before update default sink c8653c13fa alsa: adjust ucm sink/source priority according to ports priority A patch not merged by upstream: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Test Case] On the AMD renoir machines: Boot the system with these updated packages (already backported kernel drivers to focal and oem-5.6 kernels), open the gnome-control-center, we could see the digital mic in the input device tab, and only one input device. we could record sound through this dmic, we could play sound through the speaker, plug a headset, we could see the output device become headphones and the input device become headset mic, we could play sound to headphone and record sound from headset mic, plug a hdmi monitor, there is hdmi audio choice, play sound to hdmi audio, we could hear the sound from the speaker on the monitor. Suspend and resume, redo the previous steps, all audio devices still work well. On other machines: Boot the system with all updated packages or partial updated packages, check all input devices and output devices, they worked the same as before. this SRU doesn't bring any impact on other machines. [Regression Risk] Low For alsa-ucm-conf, this SRU adds two new folders and only minimum changes on existing folders, and these changes are under control and are for supporting acp driver. For alsa-lib, this SRU only adds the patches to support the ucm 3, and nearly all changes are in the ucm folder. For pulseaudio, this SRU only integrate 3 patches, and 2 of them are for auto switching, and they are small patches and already upstreamed. the left patch are specific to renoir audio, it will not bring impact to other machines. Also, we tested these changes with below machines: A LENOVO AMD renoir laptop, all audio function works and no regression found A DELL laptop with intel dmic, all audio function works and no regression found A DELL laptop with intel soundwire audio, all audio function works and no regression found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1889217/+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 1873658] Re: Deb Files are not associated with an application that manages packages
Not fixed in Budgie Ubuntu, where file-roller gets launched instead of software. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Fix Released Status in gdebi package in Ubuntu: Invalid Status in desktop-file-utils source package in Focal: Fix Released Status in gdebi source package in Focal: Invalid Bug description: [Impact] * When a deb is downloaded the default handler is not capable of installing on 20.04. [Test Case] We should perform this test on Ubuntu 20.04 as well as some flavors to ensure we do not regress. * Download any deb in firefox, double click on the downloaded file - On Ubuntu this should open "Ubuntu Software" - On flavors it should open whatever their default app for handling debs is [Regression Potential] * For Ubuntu, very low, rarely would a user expect to open a deb with file-roller * Other flavors of ubuntu are overriding this default and should not be affected. We do need to test this on other flavors to ensure their defaults are still honored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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
** Description changed: - This is for tracking purpose. + [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] + we need to backport 3 patches: + 2ae94c141f device-port: queue CARD CHANGE event before update default sink + c8653c13fa alsa: adjust ucm sink/source priority according to ports priority + A patch not merged by upstream: + https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 + + [Test Case] + On the AMD renoir machines: + Boot the system with these updated packages (already backported kernel drivers + to focal and oem-5.6 kernels), open the gnome-control-center, we could see + the digital mic in the input device tab, and only one input device. we could + record sound through this dmic, we could play sound through the speaker, plug + a headset, we could see the output device become headphones and the input + device become headset mic, we could play sound to headphone and record sound + from headset mic, plug a hdmi monitor, there is hdmi audio choice, play sound + to hdmi audio, we could hear the sound from the speaker on the monitor. Suspend + and resume, redo the previous steps, all audio devices still work well. + + On other machines: + Boot the system with all updated packages or partial updated packages, check + all input devices and output devices, they worked as the same as before. this + SRU doesn't bring any impact on other machines. + + [Regression Risk] + Low -- 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: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New 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: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New 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] we need to backport 3 patches: 2ae94c141f device-port: queue CARD CHANGE event before update default sink c8653c13fa alsa: adjust ucm sink/source priority according to ports priority A patch not merged by upstream: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Test Case] On the AMD renoir machines: Boot the system with these updated packages (already backported kernel drivers to focal and oem-5.6 kernels), open the gnome-control-center, we could see the digital mic in the input device tab, and only one input device. we could record sound through this dmic, we could play sound through the speaker, plug a headset, we could see the output device become headphones and the input device become headset mic, we could play sound to headphone and record sound from headset mic, plug a hdmi monitor, there is hdmi audio choice, play sound to hdmi audio, we could hear the sound from the speaker on the monitor. Suspend and
[Touch-packages] [Bug 1879206] Re: cups hplip not install printer
After sudo apt purge ippusbxd and rebooting, I was able to print and scan with HP Deskjet 3639 -- 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/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
I've removed all apt sources.list and added back from current version of Ubuntu which helped me to package by package upgrade it to current Ubuntu version of the package I had same issues and they were in a system because some packages were from the previous version ( 16 ) which must be upgraded after OS upgrade to 18 so rm -rf /etc/apt/sources.list.d/* apt-get update apt-get upgrade add all repositories back but for current version of Ubuntu and you'll succeed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop mongodb I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1889378] Re: dbus method 'Sleep' not work
Thank you for your bug report, how do you call it exactly? What are you trying to do? The documentation states 'This command should not be called directly by users or clients; it is intended for system suspend/resume tracking.' Is it resulting from a problem you have after suspend or are you trying to manually force a suspend for some reason? Having some details on what you trying to achieve would help understanding the issue... ** 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/1889378 Title: dbus method 'Sleep' not work Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Incomplete Bug description: refer to https://salsa.debian.org/utopia-team/network- manager/-/blob/debian/master/introspection/org.freedesktop.NetworkManager.xml#L157 But the network not be deactivated after the Sleep method be called. steps: 1.$ gdbus call --system --dest org.freedesktop.NetworkManager --object-path /org/freedesktop/NetworkManager --method org.freedesktop.NetworkManager.Sleep true 2.$ journal ctl ; # see the dbus method be called correctly. NetworkManager[843]: [1596010870.8622] manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[843]: [1596010870.8626] device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') NetworkManager[843]: [1596010870.8632] manager: NetworkManager state is now ASLEEP NetworkManager[843]: [1596010870.8635] audit: op="sleep-control" arg="on" pid=2825 uid=0 result="success" 3. $ ping 8.8.8.8 ; # still work unexpectedly Note: this issue can be reproduced on the latest version of network- manager source : https://git.launchpad.net/network- manager/commit/?id=6e17a2e7ad9453c0afe34dab0e6768ad8ee447c2 upstream bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/503 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1889378/+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 1889378] Re: dbus method 'Sleep' not work
** Description changed: + refer to https://salsa.debian.org/utopia-team/network- + manager/-/blob/debian/master/introspection/org.freedesktop.NetworkManager.xml#L157 - refer to https://salsa.debian.org/utopia-team/network-manager/-/blob/debian/master/introspection/org.freedesktop.NetworkManager.xml#L157 + - - - + Control the NetworkManager daemon's sleep state. When asleep, all + interfaces that it manages are deactivated. When awake, devices are + available to be activated. This command should not be called directly by + users or clients; it is intended for system suspend/resume tracking. + --> + + + But the network not be deactivated after the Sleep method be called. + + steps: + 1.$ gdbus call --system --dest org.freedesktop.NetworkManager --object-path /org/freedesktop/NetworkManager --method org.freedesktop.NetworkManager.Sleep true + + 2.$ journal ctl ; # see the dbus method be called correctly. + 七 29 16:21:10 u-XPS-13-9310 sudo[2822]:u : TTY=pts/1 ; PWD=/home/u ; USER=root ; COMMAND=/usr/bin/gdbus call --system --dest org.freedesktop.NetworkManager --object-path /org/freedesktop/NetworkManage + r --method org.freedesktop.NetworkManager.Sleep true + 七 29 16:21:10 u-XPS-13-9310 sudo[2822]: pam_unix(sudo:session): session opened for user root by (uid=0) + 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8622] manager: sleep: sleep requested (sleeping: no enabled: yes) + 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8626] device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') + 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8632] manager: NetworkManager state is now ASLEEP + 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8635] audit: op="sleep-control" arg="on" pid=2825 uid=0 result="success" + + 3. $ ping 8.8.8.8 ; # still work unexpectedly + + Note: this issue can be reproduced on the latest version of network- + manager source : https://git.launchpad.net/network- + manager/commit/?id=6e17a2e7ad9453c0afe34dab0e6768ad8ee447c2 ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Importance: Undecided => High ** Description changed: refer to https://salsa.debian.org/utopia-team/network- manager/-/blob/debian/master/introspection/org.freedesktop.NetworkManager.xml#L157 But the network not be deactivated after the Sleep method be called. steps: - 1.$ gdbus call --system --dest org.freedesktop.NetworkManager --object-path /org/freedesktop/NetworkManager --method org.freedesktop.NetworkManager.Sleep true + 1.$ gdbus call --system --dest org.freedesktop.NetworkManager --object-path /org/freedesktop/NetworkManager --method org.freedesktop.NetworkManager.Sleep true - 2.$ journal ctl ; # see the dbus method be called correctly. - 七 29 16:21:10 u-XPS-13-9310 sudo[2822]:u : TTY=pts/1 ; PWD=/home/u ; USER=root ; COMMAND=/usr/bin/gdbus call --system --dest org.freedesktop.NetworkManager --object-path /org/freedesktop/NetworkManage - r --method org.freedesktop.NetworkManager.Sleep true - 七 29 16:21:10 u-XPS-13-9310 sudo[2822]: pam_unix(sudo:session): session opened for user root by (uid=0) - 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8622] manager: sleep: sleep requested (sleeping: no enabled: yes) - 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8626] device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') - 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8632] manager: NetworkManager state is now ASLEEP - 七 29 16:21:10 u-XPS-13-9310 NetworkManager[843]: [1596010870.8635] audit: op="sleep-control" arg="on" pid=2825 uid=0 result="success" + 2.$ journal ctl ; # see the dbus method be called correctly. + NetworkManager[843]: [1596010870.8622] manager: sleep: sleep requested (sleeping: no enabled: yes) + NetworkManager[843]: [1596010870.8626] device (p2p-dev-wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') + NetworkManager[843]: [1596010870.8632] manager: NetworkManager state is now ASLEEP + NetworkManager[843]: [1596010870.8635] audit: op="sleep-control" arg="on" pid=2825 uid=0 result="success" 3. $ ping 8.8.8.8 ; # still work unexpectedly Note: this issue can be reproduced on the latest version of network- manager source : https://git.launchpad.net/network- manager/commit/?id=6e17a2e7ad9453c0afe34dab0e6768ad8ee447c2 ** Description changed: refer to https://salsa.debian.org/utopia-team/network- manager/-/blob/debian/master/introspection/org.freedesktop.NetworkManager.xml#L157 But the network not be
[Touch-packages] [Bug 1889160] Re: 20.04 no sound from speakers
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1889160 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1889160 Title: 20.04 no sound from speakers Status in alsa-driver package in Ubuntu: Incomplete Bug description: Bluetooth head phones work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1889160/+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 1644995] Re: specific SVG file breaks Ubuntu 16.04 desktop + nautilus
@Jonathan, the issue you are referring to is bug #1889206, the bug here is years old -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1644995 Title: specific SVG file breaks Ubuntu 16.04 desktop + nautilus Status in librsvg: Expired Status in librsvg package in Ubuntu: Triaged Bug description: Saving following file on Desktop (Ubuntu 16.04.1) results in: 1. Wallpaper and all icons on the desktop disappear 2. Nautilus starts for ~1sec then breaks with "Floating point exception" I suspect it's related to librsvg. In syslog I have many records similar to this one: kernel: [ 20.076864] traps: nautilus[2270] trap divide error ip:7f63fbddf716 sp:7f63fad3f5b0 error:0 in librsvg-2.so.2.40.13[7f63fbdc9000+35000] Here is the file (I can't even attach it here with Firefox, because it makes it crash): http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink; xmlns:ev="http://www.w3.org/2001/xml-events;> https://encrypted-tbn2.gstatic.com/images?q=tbn:ANd9GcRiXhgkC523CD5DIdvfwFl3G_S1Hc3oHzh8NUTXPeRSfYv1i8rA; result="pattern" width="4" height="4"/> To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/1644995/+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 1879417] Re: with default font, empty lines have different height to non-empty lines
@Harm, thanks for the upstream bug reference! ** Changed in: gedit (Ubuntu) Status: Confirmed => Triaged ** Package changed: gedit (Ubuntu) => pango1.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1879417 Title: with default font, empty lines have different height to non-empty lines Status in gedit: Unknown Status in Pango: Unknown Status in pango1.0 package in Ubuntu: Triaged Bug description: I suspect this bug is not a gedit bug, but a font bug, however I'm not sure. Steps to reproduce: 1) Ensure font is the default "Use the system fixed width font (Ubuntu Mono 13)" is checked. 2) Create two tabs, in one tab write: 1 2 3 4 In the other tab, write: 4 Switch between the tabs and observer that line 4 is in a different location in each tab. Using a different font "Monospace Regular 12" makes the problem go away, hence I suspect the problem is the font. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1879417/+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 1879417] [NEW] with default font, empty lines have different height to non-empty lines
You have been subscribed to a public bug: I suspect this bug is not a gedit bug, but a font bug, however I'm not sure. Steps to reproduce: 1) Ensure font is the default "Use the system fixed width font (Ubuntu Mono 13)" is checked. 2) Create two tabs, in one tab write: 1 2 3 4 In the other tab, write: 4 Switch between the tabs and observer that line 4 is in a different location in each tab. Using a different font "Monospace Regular 12" makes the problem go away, hence I suspect the problem is the font. ** Affects: gedit Importance: Unknown Status: Unknown ** Affects: pango Importance: Unknown Status: Unknown ** Affects: pango1.0 (Ubuntu) Importance: Low Status: Triaged -- with default font, empty lines have different height to non-empty lines https://bugs.launchpad.net/bugs/1879417 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. -- 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 1889378] [NEW] dbus method 'Sleep' not work
Public bug reported: refer to https://salsa.debian.org/utopia-team/network-manager/-/blob/debian/master/introspection/org.freedesktop.NetworkManager.xml#L157 But the network not be deactivated after the Sleep method be called. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: 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/1889378 Title: dbus method 'Sleep' not work Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Bug description: refer to https://salsa.debian.org/utopia-team/network-manager/-/blob/debian/master/introspection/org.freedesktop.NetworkManager.xml#L157 But the network not be deactivated after the Sleep method be called. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1889378/+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 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
ok, made that change. it stayed on the correct input after a reboot, and after sleep/resume. however, sleep/resume still messes up the device ordering so i still have to change it to the new "correct" dev after resume. still. headway! :) -- 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/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 1873961] Re: tc filter show tcp_flags wrong mask value
The ADT failures related to lubreswan and ubuntu-fan were resolved by re-try. The systemd test fails somewhere in the upstream test but does not give any hints about which part of that section was considered a failure. The amd64 re-try has now succeeded and from the timing it feels like the failure was rather due to some timeout and the test-case is rather to blame. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Fix Committed Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Fix Committed Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to:
[Touch-packages] [Bug 1799580] Re: Settings made by qasmixer are lost on next reboot
I noticed the same bug affecting me on 3 installs: 1. Ubuntu Budgie 20.04 with Ubuntu Studio tools. Desktop, USB audio interface. 2. Ubuntu Budgie 20.04 with Ubuntu Studio tools. Laptop, Internal Audio card. 3. Ubuntu Studio 20.10 daily. Desktop, USB audio interface. I do not think the issue is specifically of QASmixer. I tried to manipulate ALSA volume settings using alsamixer and and alsactl store, both with normal user and using sudo. Volume settings persist in the session, if I close and reopen QASmixer or alsamixer, but all volume settings are reset on reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1799580 Title: Settings made by qasmixer are lost on next reboot Status in alsa-utils package in Ubuntu: Confirmed Bug description: I use qasmixer to set the "Synth" volume to full, on my SoundBlaster Live sound-card. On prior levels of Ubuntu (through 18.04), any settings I make are preserved over reboots. On the latest level of Ubuntu (18.10) the settings are effective only as long as the system is running. The next time I reboot, the settings are gone, and I have to use qasmixer to set them all over again. I expected the settings made by qasmixer to be preserved on the next reboot, as with past levels of Ubuntu. The settings made by qasmixer are not preserved over a reboot on Ubuntu 18.10. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: qasmixer 0.21.0-1.1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic i686 ApportVersion: 2.20.10-0ubuntu13 Architecture: i386 CurrentDesktop: LXQt Date: Tue Oct 23 14:59:06 2018 InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release i386 (20181017.2) SourcePackage: qastools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1799580/+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 1889160] Re: 20.04 no sound from speakers
** Package changed: linux (Ubuntu) => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1889160 Title: 20.04 no sound from speakers Status in alsa-driver package in Ubuntu: Incomplete Bug description: Bluetooth head phones work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1889160/+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 1889160] [NEW] 20.04 no sound from speakers
You have been subscribed to a public bug: Bluetooth head phones work. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: Incomplete -- 20.04 no sound from speakers https://bugs.launchpad.net/bugs/1889160 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- 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
