[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
I tried to reproduce this in an up-to-date bionic VM as follows: # inside the bionic VM sudo snap install lxd sudo lxd init # accept defauls sudo lxc launch ubuntu-daily:hirsute hirsute sudo lxc exec hirsute /bin/bash # then inside the hirsute container install livecd-rootfs apt update apt install livecd-rootfs # http works as expected with no changes wget -q www.google.com -O/dev/null && echo Working || echo Failed Working # works as expected with no iptables rule # add iptables rule manually iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon \ -j REDIRECT --to 8080 # now we expect it to fail as there is no magic-proxy running yet wget -q www.google.com -O/dev/null && echo Working || echo Failed Failed # start the magic-proxy manually /usr/share/livecd-rootfs/magic-proxy \ --address="127.0.0.1" \ --port=8080\ --run-as=daemon\ --cutoff-time=0\ --log-file=livecd.magic-proxy.log \ --pid-file=magic-proxy.pid \ --background \ --setsid # wget works as expected via the proxy wget -q www.google.com -O/dev/null && echo Working || echo Failed Working # kill the proxy killall magic-proxy # fails again wget -q www.google.com -O/dev/null && echo Working || echo Failed Failed # remove iptables rule iptables -t nat -D OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon \ -j REDIRECT --to 8080 # works as normal wget -q www.google.com -O/dev/null && echo Working || echo Failed Working -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in Launchpad itself: New Status in iptables package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in lxd package in Ubuntu: New Bug description: when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1917920/+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 1918227] Re: No display after sleep
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1918227 Title: No display after sleep Status in xorg-server package in Ubuntu: New Bug description: Approximately two weeks ago after leaving the computer alone the display turned off like normal but did not come back.The system is working in the background but the display wont show. I've gotten it to work sometimes by pulling out the display port cable out and putting it back in but that hasn't been working lately. Any help would be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 22:44:08 2021 DistUpgraded: 2020-05-07 22:40:27,977 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1043:0577] InstallationDate: Installed on 2019-10-30 (495 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=cdbb24bd-9536-4aa2-b059-e849c202173a ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-08 (305 days ago) dmi.bios.date: 07/01/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2407 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2407:bd07/01/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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/xorg-server/+bug/1918227/+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 1918227] [NEW] No display after sleep
Public bug reported: Approximately two weeks ago after leaving the computer alone the display turned off like normal but did not come back.The system is working in the background but the display wont show. I've gotten it to work sometimes by pulling out the display port cable out and putting it back in but that hasn't been working lately. Any help would be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 22:44:08 2021 DistUpgraded: 2020-05-07 22:40:27,977 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1043:0577] InstallationDate: Installed on 2019-10-30 (495 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=cdbb24bd-9536-4aa2-b059-e849c202173a ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-08 (305 days ago) dmi.bios.date: 07/01/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2407 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2407:bd07/01/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1918227 Title: No display after sleep Status in xorg-server package in Ubuntu: New Bug description: Approximately two weeks ago after leaving the computer alone the display turned off like normal but did not come back.The system is working in the background but the display wont show. I've gotten it to work sometimes by pulling out the display port cable out and putting it back in but that hasn't been working lately. Any help would be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 22:44:08 2021 DistUpgraded: 2020-05-07 22:40:27,977 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1043:0577] InstallationDate: Installed on 2019-10-30 (495 days ago) InstallationMedia: Ub
[Touch-packages] [Bug 1918122] Re: Background picture not changed correctly
Thanks for the bug report. Please try uninstalling/disabling all extensions you might have added via the 'Extensions' app. Then reboot and tell us if the problem still happens. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: amdgpu ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1918122 Title: Background picture not changed correctly Status in mutter package in Ubuntu: Incomplete Bug description: I have changed my background picture to a external picture everything is good but when I changed my screen to the bottom one(super+pate down) my prevision background coming back ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:13:07 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1002:67ef] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1458:22de] InstallationDate: Installed on 2021-03-01 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2e09764a-1fb8-4580-868d-0660951ab9a2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2010 dmi.bios.release: 22.9 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2209 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2209:bd03/11/2010:br22.9:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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/mutter/+bug/1918122/+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 1651500] Re: [ASUS X441SA] No sound at all
** Summary changed: - [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all + [ASUS X441SA] No sound at all ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: focal ** Summary changed: - [ASUS X441SA] No sound at all + [ASUS X441SA] [8086:2284] No sound at all ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1651500 Title: [ASUS X441SA] [8086:2284] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: 1. Release of ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 2. version of the package AlsaMixer v1.1.0 3. I expect to hear sound from speaker 4. I can not any sound from speaker ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio CurrentDesktop: Unity Date: Tue Dec 20 22:51:08 2016 InstallationDate: Installed on 2016-12-15 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X441SA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X441SA 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.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X441SA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1651500/+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 1875259] Re: [8086:27d8] No sound when upgrading to Kubuntu-20.04
** Summary changed: - no sound when upgrading to Kubuntu-20.04 + [8086:27d8] No sound when upgrading to Kubuntu-20.04 ** Package changed: ubiquity (Ubuntu) => pulseaudio (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1875259 Title: [8086:27d8] No sound when upgrading to Kubuntu-20.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Since I upgraded to Kubuntu-20.04, there is no sound. Everything worked fine with Kubuntu-19.10. pacmd list-cards 1 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "0" alsa.card_name = "HDA Intel" alsa.long_card_name = "HDA Intel at 0xefebc000 irq 26" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "27d8" device.product.name = "NM10/ICH7 Family High Definition Audio Controller" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: input:analog-stereo: Analog Stereo Input (priority 60, available: no) output:analog-stereo: Analog Stereo Output (priority 6000, available: no) output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060, available: no) output:iec958-stereo: Digital Stereo (IEC958) Output (priority 5500, available: unknown) output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) Output + Analog Stereo Input (priority 5560, available: no) off: Off (priority 0, available: unknown) active profile: sinks: alsa_output.pci-_00_1b.0.iec958-stereo/#0: Built-in Audio Digital Stereo (IEC958) sources: alsa_output.pci-_00_1b.0.iec958-stereo.monitor/#0: Monitor of Built-in Audio Digital Stereo (IEC958) ports: analog-input-internal-mic-always: Internal Microphone (priority 8900, latency offset 0 usec, available: no) properties: device.icon_name = "audio-input-microphone" analog-input-mic: Microphone (priority 8700, latency offset 0 usec, available: no) properties: device.icon_name = "audio-input-microphone" analog-output-speaker-always: Speakers (priority 1, latency offset 0 usec, available: no) properties: device.icon_name = "audio-speakers" analog-output-headphones: Headphones (priority 9900, latency offset 0 usec, available: no) properties: device.icon_name = "audio-headphones" iec958-stereo-output: Digital Output (S/PDIF) (priority 0, latency offset 0 usec, available: unknown) properties: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Apr 26 14:06:13 2020 InstallCmdLine: file=/cdrom/preseed/kubuntu.seed maybe-ubiquity initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2019-04-11 (381 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubiquity Symptom: installer UpgradeStatus: Upgraded to focal on 2020-04-24 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875259/+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 1916877] Re: [Sony VGN-TZ150N] Bluetooth sound card not detected
*** This bug is a duplicate of bug 1875259 *** https://bugs.launchpad.net/bugs/1875259 ** Summary changed: - Bluetooth sound card not detected + [Sony VGN-TZ150N] Bluetooth sound card not detected ** This bug has been marked a duplicate of bug 1875259 [8086:27d8] No sound when upgrading to Kubuntu-20.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1916877 Title: [Sony VGN-TZ150N] Bluetooth sound card not detected Status in pulseaudio package in Ubuntu: Incomplete Bug description: "Dummy output" is on audio volume setting and there is no sound ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Feb 25 06:06:58 2021 InstallationDate: Installed on 2021-02-24 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2007 dmi.bios.release: 5.2 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0052N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 5.2 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0052N7:bd07/11/2007:br5.2:efr5.2:svnSonyCorporation:pnVGN-TZ150N:pvrJ002NHLG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-TZ150N dmi.product.sku: N/A dmi.product.version: J002NHLG dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1916877/+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 1875259] [NEW] [8086:27d8] No sound when upgrading to Kubuntu-20.04
You have been subscribed to a public bug: Since I upgraded to Kubuntu-20.04, there is no sound. Everything worked fine with Kubuntu-19.10. pacmd list-cards 1 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "0" alsa.card_name = "HDA Intel" alsa.long_card_name = "HDA Intel at 0xefebc000 irq 26" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "27d8" device.product.name = "NM10/ICH7 Family High Definition Audio Controller" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: input:analog-stereo: Analog Stereo Input (priority 60, available: no) output:analog-stereo: Analog Stereo Output (priority 6000, available: no) output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060, available: no) output:iec958-stereo: Digital Stereo (IEC958) Output (priority 5500, available: unknown) output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) Output + Analog Stereo Input (priority 5560, available: no) off: Off (priority 0, available: unknown) active profile: sinks: alsa_output.pci-_00_1b.0.iec958-stereo/#0: Built-in Audio Digital Stereo (IEC958) sources: alsa_output.pci-_00_1b.0.iec958-stereo.monitor/#0: Monitor of Built-in Audio Digital Stereo (IEC958) ports: analog-input-internal-mic-always: Internal Microphone (priority 8900, latency offset 0 usec, available: no) properties: device.icon_name = "audio-input-microphone" analog-input-mic: Microphone (priority 8700, latency offset 0 usec, available: no) properties: device.icon_name = "audio-input-microphone" analog-output-speaker-always: Speakers (priority 1, latency offset 0 usec, available: no) properties: device.icon_name = "audio-speakers" analog-output-headphones: Headphones (priority 9900, latency offset 0 usec, available: no) properties: device.icon_name = "audio-headphones" iec958-stereo-output: Digital Output (S/PDIF) (priority 0, latency offset 0 usec, available: unknown) properties: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Apr 26 14:06:13 2020 InstallCmdLine: file=/cdrom/preseed/kubuntu.seed maybe-ubiquity initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2019-04-11 (381 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubiquity Symptom: installer UpgradeStatus: Upgraded to focal on 2020-04-24 (2 days ago) ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ubiquity-19.10.21 -- [8086:27d8] No sound when upgrading to Kubuntu-20.04 https://bugs.launchpad.net/bugs/1875259 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio 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 1918190] Re: Enabling/Disabling VPN crashes window manager
*** This bug is a duplicate of bug 1918033 *** https://bugs.launchpad.net/bugs/1918033 ** Tags added: fixed-in-40 fixed-upstream ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Committed ** This bug has been marked a duplicate of bug 1918033 gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor)) -- 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/1918190 Title: Enabling/Disabling VPN crashes window manager Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Invalid Bug description: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F= '{print $2}' wayland $ apt-cache policy network-manager network-manager: Installed: 1.30.0-1ubuntu1 Candidate: 1.30.0-1ubuntu1 Version table: *** 1.30.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-shell gnome-shell: Installed: 3.38.3-3ubuntu1 Candidate: 3.38.3-3ubuntu1 Version table: *** 3.38.3-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status $ dpkg-query -W|grep mutter gir1.2-mutter-7:amd64 3.38.3-3ubuntu1 libmutter-7-0:amd64 3.38.3-3ubuntu1 mutter3.38.3-3ubuntu1 mutter-common 3.38.3-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:12:44 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918190/+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 1918190] Re: Enabling/Disabling VPN crashes window manager
Should be fixed by https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1651 ** Changed in: network-manager (Ubuntu) Status: New => Invalid ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid ** Changed in: mutter (Ubuntu) Status: New => Triaged -- 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/1918190 Title: Enabling/Disabling VPN crashes window manager Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Bug description: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F= '{print $2}' wayland $ apt-cache policy network-manager network-manager: Installed: 1.30.0-1ubuntu1 Candidate: 1.30.0-1ubuntu1 Version table: *** 1.30.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-shell gnome-shell: Installed: 3.38.3-3ubuntu1 Candidate: 3.38.3-3ubuntu1 Version table: *** 3.38.3-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status $ dpkg-query -W|grep mutter gir1.2-mutter-7:amd64 3.38.3-3ubuntu1 libmutter-7-0:amd64 3.38.3-3ubuntu1 mutter3.38.3-3ubuntu1 mutter-common 3.38.3-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:12:44 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918190/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Upstream are not totally sure that fix also addresses this crash so reopened for now. ** Changed in: mesa (Ubuntu) Status: Fix Committed => Confirmed ** Changed in: mesa (Ubuntu) Importance: Undecided => High ** No longer affects: linux (Ubuntu) ** No longer affects: xorg-server (Ubuntu) ** Tags removed: fixed-in-22 fixed-upstream ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #2859 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 ** Changed in: mesa Remote watch: gitlab.freedesktop.org/mesa/mesa/-/issues #4275 => gitlab.freedesktop.org/mesa/mesa/-/issues #2859 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+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 1911187] Autopkgtest regression report (systemd/246.6-1ubuntu1.2)
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.2) for groovy have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.48.3+20.10 (amd64) nut/2.7.4-12ubuntu1 (ppc64el) 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/groovy/update_excuses.html#systemd [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/1911187 Title: scheduled reboot reboots immediately if dbus or logind is not available Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Bug description: [IMPACT] When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately. From the sources it seems that this is intended : https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318 However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately. There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and a PR ( https://github.com/systemd/systemd/pull/18010 ). Upstream community is not willing to accept the patch but debian is. I open this bug to to pull the patch into Ubuntu once it lands in debian. [TEST PLAN] The simpler reproducer is to disable dbus to imitate the real world case. # systemctl stop dbus.service # systemctl stop dbus.socket # shutdown +1140 -r "REBOOT!" Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms) Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out Connection to groovy closed by remote host. Connection to groovy closed. [WHERE PROBLEM COULD OCCUR] This patch changes the behaviour of scheduled reboot in case logind or dbus has failed. Originally, if logind is not available (call to logind bus fails https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319) it proceeds with immediate shutdown. This patch changes this behaviour and instead of shutting down it does nothing. The actual regression potential is a user asking for a reboot and not getting it, so the largest regression potential is any existing users (human or programmatic) that are requesting a scheduled shutdown but not checking the return value for error. Any other regression would likely result in the system incorrectly not rebooted, or incorrectly scheduled for reboot. [OTHER] This is now fixed in H, currently affects B,G,F. Debian bug reports : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042 Upstream issue : https://github.com/systemd/systemd/issues/17575 PR : https://github.com/systemd/systemd/pull/18010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+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 1880258] Autopkgtest regression report (systemd/246.6-1ubuntu1.2)
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.2) for groovy have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.48.3+20.10 (amd64) nut/2.7.4-12ubuntu1 (ppc64el) 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/groovy/update_excuses.html#systemd [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/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in network-manager source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in network-manager source package in Focal: Confirmed Status in systemd source package in Focal: Fix Committed Status in network-manager source package in Groovy: New Status in systemd source package in Groovy: Fix Committed Status in network-manager source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Committed Bug description: [impact] systemd-resolved emits a disturbingly large amount of NXDOMAIN log messages that do not actually indicate any real problem [test case] see original description, or look at any log from any recent Ubuntu system, or search google for endless complaints about NXDOMAIN messages logged by Ubuntu [regression potential] any regression would likely be isolated to systemd-resolved handling of a NXDOMAIN response from its upstream nameserver, including possibly failing to resolve a hostname or delays in resolving hostnames [scope] this is needed for all releases; the patch is not upstream, but carried by Ubuntu [original description] I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+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 1913763] Autopkgtest regression report (systemd/246.6-1ubuntu1.2)
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.2) for groovy have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.48.3+20.10 (amd64) nut/2.7.4-12ubuntu1 (ppc64el) 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/groovy/update_excuses.html#systemd [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/1913763 Title: hyperv: unable to distinguish PTP devices Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Bug description: [impact] the /dev/ptp0 device for a hyperv instance may not be the correct, hyperv-provided, ptp device. [test case] on some hyperv instance types, particularly those that might contain passthrough network card(s) that also provide ptp, the first ptp device may not be the correct one to use for ptp, e.g. there may be multiple ones: $ ls /dev/ptp* /dev/ptp0 /dev/ptp1 $ cat /sys/class/ptp/ptp0/clock_name hyperv $ cat /sys/class/ptp/ptp1/clock_name mlx5_p2p the order can change across boots, so a consistent way of addressing the hyperv-provided one is needed [regression potential] any regression would involve failure to properly create the ptp symlink, or other failure while udev is processing newly detected ptp device(s) [scope] this is needed in all releases this was fixed upstream with the commit 32e868f058da8b90add00b2958c516241c532b70 which is not yet included in any release [original description] Hyperv provides a PTP device. On system with multiple PTP devices, services like Chrony don't have a way to know which one is which. We would like to have a udev rule to create a symlink to the hyperv clock. This way, services could be configured to always use this clock no matter if it is ptp0, ptp1, etc.. For example: ``` SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv" ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1906331] Re: systemd-resolve crashes fairly often (and reports various assertions)
> Do you plan releasing this version on PPA that was for the hirsute release - are you able to test that (development) release to ensure the problem is fixed? it's the same patches as for focal, so it may not be fixed there. Alternately if you have a test environment (NOT some system that you care about, as it may break) can you test the latest upstream systemd code from this ppa: https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/systemd -- 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/1906331 Title: systemd-resolve crashes fairly often (and reports various assertions) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Status in systemd source package in Hirsute: Fix Released Bug description: [impact] systemd-resolved crashes [test case] see original description; I can't reproduce so I'm relying on the reporter(s) to test/verify. [regression potential] any regression would likely occur while processing sd_event objects, which are used throughout systemd code; this could result in crashes in almost any part of systemd code. However a more likely regression would be leaks of sd_event objects due to failure to release the final ref for an object. [scope] This is needed for f/g/h This might be fixed by upstream commit f814c871e65df8552a055dd887bc94b074037833; if so, that commit isn't included in any systemd release yet, and so is needed in h and earlier. [other info] I believe this is caused by a freed sd_event object that is then processed and calls the on_query_timeout callback with invalid state, leading to failed assertion, which causes resolved to crash; that's what analysis of the crash dump appears to indicate. This may be fixed by the upstream commit referenced in [scope], which takes additional refs during function calls. However I haven't reproduced this myself, so I'm only guessing as to the cause and solution at this point. I'm unsure why this would not occur in bionic, but per comment 5 it seems it doesn't happen in that release. [original description] (Tested on regularly updated Ubuntu 20.04, currently i use systemd 245.4-4ubuntu3.2) I observe fairly lot of segfaults of systemd-resolve. Frequency vary but … see below. I have no clue what is the reason. Specific feature of my machine is that apart from normal cable connection (to OpenWRT router) I use OpenVPN for business network (and this submits specific nameserver for myorg.local domain). ~ $ LC_ALL=C dmesg -T --level=info | grep systemd-resolve [Sun Nov 29 11:47:37 2020] systemd-resolve[1629307]: segfault at 190eed7bdc6 ip 7fd98f771dc9 sp 7ffc2352a100 error 4 in libsystemd-shared-245.so[7fd98f74c000+16e000] [Sun Nov 29 11:57:27 2020] systemd-resolve[1629787]: segfault at 1f ip 55ab7b0cb686 sp 7fff78ce4bd0 error 4 in systemd-resolved[55ab7b0a4000+3e000] [Sun Nov 29 12:07:37 2020] systemd-resolve[1630481]: segfault at 191 ip 55ca69fed91c sp 7ffc4d757dc0 error 6 in systemd-resolved[55ca69fc2000+3e000] [Sun Nov 29 13:12:26 2020] systemd-resolve[1638829]: segfault at 19224162371 ip 7fc1bc9b9dc9 sp 7ffc21378170 error 4 in libsystemd-shared-245.so[7fc1bc994000+16e000] [Sun Nov 29 13:32:57 2020] systemd-resolve[1639886]: segfault at 1926d8126d3 ip 7f7ed17e9dc9 sp 7ffda2cea0b0 error 4 in libsystemd-shared-245.so[7f7ed17c4000+16e000] [Sun Nov 29 13:42:37 2020] systemd-resolve[1640246]: segfault at 61 ip 558d992e2686 sp 7fff08906af0 error 4 in systemd-resolved[558d992bb000+3e000] [Sun Nov 29 15:42:26 2020] systemd-resolve[1645397]: segfault at 1943c92afc7 ip 7fd4c1721dc9 sp 7fff25259ce0 error 4 in libsystemd-shared-245.so[7fd4c16fc000+16e000] [Sun Nov 29 16:02:36 2020] systemd-resolve[1646052]: segfault at 1947ecb3726 ip 7f1008549dc9 sp 7fff44a6db70 error 4 in libsystemd-shared-245.so[7f1008524000+16e000] [Sun Nov 29 17:42:35 2020] systemd-resolve[1649403]: segfault at 71 ip 55a37fe5a686 sp 7ffd9a160440 error 4 in systemd-resolved[55a37fe33000+3e000] [Sun Nov 29 17:52:35 2020] systemd-resolve[1649759]: segfault at 558d292947d0 ip 558d292947d0 sp 7ffec7ab3bf8 error 15 [Sun Nov 29 19:17:55 2020] systemd-resolve[1652349]: segfault at 558995b77cf0 ip 558995b77cf0 sp 7ffe545ae4a8 error 15 [Sun Nov 29 19:32:35 2020] systemd-resolve[1652640]: segfault at 19773c20194 ip 7f66bb529dc9 sp 7fffd7066fc0 error 4 in libsystemd-shared-245.so[7f66bb504000+16e000] [Sun Nov 29 20:03:54 2020] systemd-resolve[1653715]: segfault at 197e3aee918 ip 7fdc40b51dc9 sp 7ffde484fbf0 error 4 in libsystemd-shared-245.so[7fdc40b2c000+16e000] [Sun Nov 29 20:22:24 2020] systemd-resolve[
[Touch-packages] [Bug 1913189] Autopkgtest regression report (systemd/245.4-4ubuntu3.5)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: prometheus-apache-exporter/0.7.0+ds-1 (arm64) udisks2/2.8.4-1ubuntu1 (amd64, ppc64el) munin/2.0.56-1ubuntu1 (arm64) docker.io/19.03.8-0ubuntu1.20.04.2 (s390x) 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/focal/update_excuses.html#systemd [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/1913189 Title: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1 Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Bug description: [impact] test-fs-util fails when running under 5.8 kernel [test case] see autopkgtest runs, e.g. amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz [regression potential] any regression would likely result in incorrectly passed or failed build-time or autopkgtest-time test run [scope] this is needed in f and b this was fixed upstream with commit 5b5ce6298e which was first included in v247, and has already been backported to g in bug 1891527. while it's unlikely that the 5.8 kernel will ever officially be available directly in b, this test case is also run at build time, so if the lp build farm is ever updated to the 5.8 kernel this test case would begin failing during build, so the patch should be backported there as well. this isn't needed in x as the test-fs-util test isn't present there. [original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20210121_021134_f3c65@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20210121_090718_fa164@/log.gz The failing test case is: TEST-24-UNIT-TESTS: === Failed test log === --- test-fs-util begin --- /* test_chase_symlinks */ /* test_unlink_noerrno */ /* test_readlink_and_make_absolute */ /* test_var_tmp */ /* test_dot_or_dot_dot */ /* test_access_fd */ /* test_touch_file */ Assertion 'mknod(a, 0775 | S_IFBLK, makedev(0, 0)) >= 0' failed at src/test/test-fs-util.c:637, funct ion test_touch_file(). Aborting. --- test-fs-util end --- make: Leaving directory '/tmp/autopkgtest.KFUfZH/build.scn/src/test/TEST-24-UNIT-TESTS' make: *** [Makefile:4: run] Error 1 This issue has been solved in Groovy on bug 1891527, likely the fix needs to be backported to systemd in Focal for the testcase to pass with the 5.8 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1913189/+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 1878969] Autopkgtest regression report (systemd/245.4-4ubuntu3.5)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: prometheus-apache-exporter/0.7.0+ds-1 (arm64) udisks2/2.8.4-1ubuntu1 (amd64, ppc64el) munin/2.0.56-1ubuntu1 (arm64) docker.io/19.03.8-0ubuntu1.20.04.2 (s390x) 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/focal/update_excuses.html#systemd [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/1878969 Title: time-epoch never changes in SRUs Status in ubuntu-core-initramfs: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Bug description: [Impact] * Systems without hwclock come up with a fixed time epoch which is not updated in SRUs * Ideally booting with a newer built of systemd should move time epoch to be at least when systemd was last built. For example to the value of SOURCE_DATE_EPOCH. [Test Case] * Boot without network NTP or hwclock * Observe that the epoch is the same as the time when NEWS entry in the systemd source code was last touched. * Boot newer update of systemd, observe that the time epoch is at least 2020 [Regression Potential] * Bad epoch, may result in unable to perform TLS connections, validated GPG signatures, and snapd assertions. Changing epoch to be more recent is desired. Some machines may rely on the fact that "bionic" without hwclock always comes up in year 2018. But in practice that is incorrect thing to do. [Other Info] * By default option('time-epoch', type : 'integer', value : '-1', description : 'time epoch for time clients') in systemd is set to the modification time of the NEW entry time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int() If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value to be compliant with the https://reproducible- builds.org/docs/timestamps/ specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+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 1913423] Autopkgtest regression report (systemd/245.4-4ubuntu3.5)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: prometheus-apache-exporter/0.7.0+ds-1 (arm64) udisks2/2.8.4-1ubuntu1 (amd64, ppc64el) munin/2.0.56-1ubuntu1 (arm64) docker.io/19.03.8-0ubuntu1.20.04.2 (s390x) 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/focal/update_excuses.html#systemd [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/1913423 Title: getgrouplist is not thread safe with libnss_systemd Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Bug description: [impact] programs calling getgrouplist() may crash as it is not thread-safe [test case] see upstream bug description for sample c program to reproduce: https://github.com/systemd/systemd/issues/17007#issue-698123284 [regression potential] any regression would likely occur when creating a hashmap in systemd, or when any multi-threaded programs concurrently create (and use) the hashmap [scope] this is needed for f and b this is fixed upstream by commit ae0b700a856c0ae460d271bb50dccfaae84dbcab, already included in g/h (per comment 1). [original description] This upstream issue (https://github.com/systemd/systemd/issues/17007) is affecting the latest version of systemd in Ubuntu Focal. It has been fixed upstream with https://github.com/systemd/systemd/pull/17033. Can we have this patched for Focal please as it causes Mesos to randomly segfault on start. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913423/+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 1880258] Autopkgtest regression report (systemd/245.4-4ubuntu3.5)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: prometheus-apache-exporter/0.7.0+ds-1 (arm64) udisks2/2.8.4-1ubuntu1 (amd64, ppc64el) munin/2.0.56-1ubuntu1 (arm64) docker.io/19.03.8-0ubuntu1.20.04.2 (s390x) 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/focal/update_excuses.html#systemd [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/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in network-manager source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in network-manager source package in Focal: Confirmed Status in systemd source package in Focal: Fix Committed Status in network-manager source package in Groovy: New Status in systemd source package in Groovy: Fix Committed Status in network-manager source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Committed Bug description: [impact] systemd-resolved emits a disturbingly large amount of NXDOMAIN log messages that do not actually indicate any real problem [test case] see original description, or look at any log from any recent Ubuntu system, or search google for endless complaints about NXDOMAIN messages logged by Ubuntu [regression potential] any regression would likely be isolated to systemd-resolved handling of a NXDOMAIN response from its upstream nameserver, including possibly failing to resolve a hostname or delays in resolving hostnames [scope] this is needed for all releases; the patch is not upstream, but carried by Ubuntu [original description] I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+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 1902236] Autopkgtest regression report (systemd/245.4-4ubuntu3.5)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: prometheus-apache-exporter/0.7.0+ds-1 (arm64) udisks2/2.8.4-1ubuntu1 (amd64, ppc64el) munin/2.0.56-1ubuntu1 (arm64) docker.io/19.03.8-0ubuntu1.20.04.2 (s390x) 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/focal/update_excuses.html#systemd [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/1902236 Title: Duplicated root and nobody returned by getent on Focal Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [impact] getent password or getent group returns duplicate, false/synthesized, entries for root and nobody [test case] root@lp1902236-f:~# getent passwd | grep root root:x:0:0:root:/root:/bin/bash root:x:0:0:root:/root:/bin/sh root@lp1902236-f:~# getent group | grep root root:x:0: root:x:0: root@lp1902236-f:~# getent passwd | grep nobody nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin nobody:x:65534:65534:nobody:/:/usr/sbin/nologin root@lp1902236-f:~# getent group | grep nogroup nogroup:x:65534: nogroup:x:65534: [regression potential] any regression would likely result in incorrect results to calls to getent or other programs using libnss-systemd [scope] this is needed only for f this was fixed upstream by commit 9494da41c271bb9519d3484b6016526a72cc6be5 which was included first in v246, so this is fixed in g and later already. b and earlier doesn't show the duplication. [original description] * Summary systemd's NSS integration causes getent passwd/group to return duplicated entries for root/root and nobody/nogroup. The root account also gets a different shell (/bin/sh instead of /bin/bash). * Steps to reproduce: 1) create a container $ lxc launch images:ubuntu/focal test-nobody 2) check the root and nobody accounts $ lxc exec test-nobody -- getent passwd | grep -E '^(root|nobody):' 3) check the root and nogroup groups $ lxc exec test-nobody -- getent group | grep -E '^(root|nogroup):' 2 and 3 should report a single entry for each account/group but they return dups like this: root:x:0:0:root:/root:/bin/bash nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin root:x:0:0:root:/root:/bin/sh nobody:x:65534:65534:nobody:/:/usr/sbin/nologin * Description The problem seems to come from the NSS integration: $ lxc exec test-nobody -- grep -wF systemd /etc/nsswitch.conf passwd: files systemd group: files systemd as the /etc/passwd and /etc/group file contain no dups: $ lxc exec test-nobody -- grep ^nobody: /etc/passwd nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin $ lxc exec test-nobody -- grep ^nogroup: /etc/group nogroup:x:65534: Removing systemd from /etc/nsswitch.conf indeed removes the dup. An alternative way of seeing what systemd adds on top of the flat files: $ lxc exec test-nobody -- bash -c 'diff -u /etc/passwd <(getent passwd)' --- /etc/passwd 2020-10-30 13:07:52.219261001 + +++ /dev/fd/632020-10-30 13:29:38.396928732 + @@ -24,3 +24,5 @@ _apt:x:105:65534::/nonexistent:/usr/sbin/nologin ubuntu:x:1000:1000::/home/ubuntu:/bin/bash systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin +root:x:0:0:root:/root:/bin/sh +nobody:x:65534:65534:nobody:/:/usr/sbin/nologin $ lxc exec test-nobody -- bash -c 'diff -u /etc/group <(getent group)' --- /etc/group2020-10-30 13:07:52.211261089 + +++ /dev/fd/632020-10-30 13:29:45.892846747 + @@ -50,3 +50,5 @@ ubuntu:x:1000: ssh:x:111: systemd-coredump:x:999: +root:x:0: +nogroup:x:65534: * Additional information This bug seems to occur on Focal alone as Bionic and Groovy are not affected. $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 $ apt-cache policy base-passwd systemd base-passwd: Installed: 3.5.47 Candidate: 3.5.47 Version table: *** 3.5.47 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status systemd: Installed: 245.4-4ubuntu3.2 Candidate: 245.4-4ubuntu3.2 Version table: *** 245.4-4ubuntu3.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 245.4-4ubuntu3 500 500 http://archive.ubunt
[Touch-packages] [Bug 1911187] Autopkgtest regression report (systemd/245.4-4ubuntu3.5)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: prometheus-apache-exporter/0.7.0+ds-1 (arm64) udisks2/2.8.4-1ubuntu1 (amd64, ppc64el) munin/2.0.56-1ubuntu1 (arm64) docker.io/19.03.8-0ubuntu1.20.04.2 (s390x) 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/focal/update_excuses.html#systemd [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/1911187 Title: scheduled reboot reboots immediately if dbus or logind is not available Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Bug description: [IMPACT] When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately. From the sources it seems that this is intended : https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318 However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately. There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and a PR ( https://github.com/systemd/systemd/pull/18010 ). Upstream community is not willing to accept the patch but debian is. I open this bug to to pull the patch into Ubuntu once it lands in debian. [TEST PLAN] The simpler reproducer is to disable dbus to imitate the real world case. # systemctl stop dbus.service # systemctl stop dbus.socket # shutdown +1140 -r "REBOOT!" Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms) Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out Connection to groovy closed by remote host. Connection to groovy closed. [WHERE PROBLEM COULD OCCUR] This patch changes the behaviour of scheduled reboot in case logind or dbus has failed. Originally, if logind is not available (call to logind bus fails https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319) it proceeds with immediate shutdown. This patch changes this behaviour and instead of shutting down it does nothing. The actual regression potential is a user asking for a reboot and not getting it, so the largest regression potential is any existing users (human or programmatic) that are requesting a scheduled shutdown but not checking the return value for error. Any other regression would likely result in the system incorrectly not rebooted, or incorrectly scheduled for reboot. [OTHER] This is now fixed in H, currently affects B,G,F. Debian bug reports : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042 Upstream issue : https://github.com/systemd/systemd/issues/17575 PR : https://github.com/systemd/systemd/pull/18010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+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 1913763] Autopkgtest regression report (systemd/245.4-4ubuntu3.5)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: prometheus-apache-exporter/0.7.0+ds-1 (arm64) udisks2/2.8.4-1ubuntu1 (amd64, ppc64el) munin/2.0.56-1ubuntu1 (arm64) docker.io/19.03.8-0ubuntu1.20.04.2 (s390x) 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/focal/update_excuses.html#systemd [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/1913763 Title: hyperv: unable to distinguish PTP devices Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Bug description: [impact] the /dev/ptp0 device for a hyperv instance may not be the correct, hyperv-provided, ptp device. [test case] on some hyperv instance types, particularly those that might contain passthrough network card(s) that also provide ptp, the first ptp device may not be the correct one to use for ptp, e.g. there may be multiple ones: $ ls /dev/ptp* /dev/ptp0 /dev/ptp1 $ cat /sys/class/ptp/ptp0/clock_name hyperv $ cat /sys/class/ptp/ptp1/clock_name mlx5_p2p the order can change across boots, so a consistent way of addressing the hyperv-provided one is needed [regression potential] any regression would involve failure to properly create the ptp symlink, or other failure while udev is processing newly detected ptp device(s) [scope] this is needed in all releases this was fixed upstream with the commit 32e868f058da8b90add00b2958c516241c532b70 which is not yet included in any release [original description] Hyperv provides a PTP device. On system with multiple PTP devices, services like Chrony don't have a way to know which one is which. We would like to have a udev rule to create a symlink to the hyperv clock. This way, services could be configured to always use this clock no matter if it is ptp0, ptp1, etc.. For example: ``` SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv" ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally
This bug was fixed in the package systemd - 247.3-1ubuntu4 --- systemd (247.3-1ubuntu4) hirsute; urgency=medium [ Dimitri John Ledkov ] * d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch: Patch updated to reduce log level to debug https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=299002546ec2d62e7f0dd7d614ba958fc9df83c2 [ Dan Streetman ] * d/p/lp1906331-sd-event-ref-event-loop-while-in-sd_event_prepare-ot.patch: Take event reference while processing (LP: #1906331) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1bc38abcd3b62d317fcb62b72e26d9cb2e35ccf9 * d/p/lp1917458-udev-rules-add-rule-to-create-dev-ptp_hyperv.patch: Create symlink for hyperv-provided ptp device (LP: #1917458) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f1ee790ad66395457ca64cb5f8a01fdd8aabe47 [ Balint Reczey ] * Pick proposed patch for not returning early in udevadm (LP: #1914062) File: debian/patches/lp1914062-udevadm-don-t-return-early.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d8c80751a97b0c6c4df972f6f8325293aa1607c4 * debian/tests/control: Mark systemd-fsckd flaky again. As promised in LP: 1915126, until further investigation. File: debian/tests/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=68fbaab272af81aab29497f7c6a3e4e6e9aa091b -- Balint Reczey Thu, 04 Mar 2021 12:19:05 +0100 ** Changed in: systemd (Ubuntu) Status: Invalid => 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/1915126 Title: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally Status in Auto Package Testing: Incomplete Status in systemd package in Ubuntu: Fix Released Bug description: Hi, I've asked yesterday on IRC but so far got no answer. I think it is right to file a bug about the current state of systemd autopkgtest to unite the efforts in regard to it. I was looking at the systemd tests for a no-change rebuild that really had no reason to now make it fail. While checking I found that as of this month (first bad test on 1st of February) most of the systemd test runs on amd64 will not pass/fail but instead in most cases time out. I've seen various people retry the case as it shows the typical symptoms of a "not the fault of the package, let us retry this" case. But it seems that won't help as the test history is rather clear. * Watch this in monospace to make more sense of it * $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64" Check last 50 test results for src:systemd on releases 'hirsute' on architectures 'amd64' Of the 50 last tests, we had these subtest failing per release/arch: hirsute amd64 tests-in-lxd (F 2% f 0% S 0% B 12% => P 52%/) .BTTTBTT.BTBTTTBBTTT..F.. hostnamed (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. build-login(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. unit-config(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. networkd-testpy(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-locale (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-and-services (F 4% f 0% S 0% B 12% => P 50%/) .BTTTBTT.BTBTTTBBTTT...F.F... timedated (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. boot-smoke (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. logind (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. storage(F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. upstream (F 12% f 0% S 0% B 12% => P 42%/) .BTTTBTT.BTBTTTBBTTTF.F.F..FF..F. udev (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. systemd-fsckd (F 8% f 0% S 0% B 12% => P 46%/) FBTTTBTTFBTBTTTBBTTT.F..F root-unittests (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT. localed-x11-keymap (F 0% f 0% S 0% B 12% => P 54%/) .BTTTBTT.BTBTTTBBTTT..
[Touch-packages] [Bug 1685754] Re: 'systemd --user' unduly forces umask=0022
** No longer affects: dbus (Ubuntu) ** No longer affects: dbus (Ubuntu Bionic) ** No longer affects: gnome-terminal (Ubuntu) ** No longer affects: gnome-terminal (Ubuntu Bionic) ** Project changed: nautilus => ubuntu-translations ** No longer affects: ubuntu-translations ** Project changed: gedit => ubuntu-translations ** No longer affects: ubuntu-translations ** Project changed: gnome-session => ubuntu-translations ** No longer affects: ubuntu-translations ** Bug watch removed: freedesktop.org Bugzilla #18446 https://bugs.freedesktop.org/show_bug.cgi?id=18446 ** Bug watch removed: bugzilla.gnome.org/ #784113 https://bugzilla.gnome.org/show_bug.cgi?id=784113 ** Bug watch removed: GNOME Bug Tracker #780622 https://gitlab.gnome.org/780622 ** Project changed: gnome-terminal => ubuntu-translations ** No longer affects: ubuntu-translations -- 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/1685754 Title: 'systemd --user' unduly forces umask=0022 Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] pam_umask, from /etc/passwd, is not honored in systemd --user instances [test case] on a desktop system, edit /etc/passwd to change the test user entry (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th field). For example change: ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash to: ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash You may need to reboot for your X session to pick up the change. Then, from the graphical desktop, open a terminal and run: $ gnome-terminal -e sh in the opened terminal, run: $ umask the number shown should be 0007, as set in the passwd file [regression potential] any regression would likely result in an incorrect umask for the user whose passwd entry is modified. [scope] this is needed only for b this is fixed in systemd upstream by commit 5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in v246, so this is fixed in g and later. This commit was also picked up by Debian and included in the v245 release for focal, so this is fixed in focal already. [original description] In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1685754/+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 1913763] Re: hyperv: unable to distinguish PTP devices
This bug was fixed in the package systemd - 247.3-1ubuntu4 --- systemd (247.3-1ubuntu4) hirsute; urgency=medium [ Dimitri John Ledkov ] * d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch: Patch updated to reduce log level to debug https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=299002546ec2d62e7f0dd7d614ba958fc9df83c2 [ Dan Streetman ] * d/p/lp1906331-sd-event-ref-event-loop-while-in-sd_event_prepare-ot.patch: Take event reference while processing (LP: #1906331) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1bc38abcd3b62d317fcb62b72e26d9cb2e35ccf9 * d/p/lp1917458-udev-rules-add-rule-to-create-dev-ptp_hyperv.patch: Create symlink for hyperv-provided ptp device (LP: #1917458) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f1ee790ad66395457ca64cb5f8a01fdd8aabe47 [ Balint Reczey ] * Pick proposed patch for not returning early in udevadm (LP: #1914062) File: debian/patches/lp1914062-udevadm-don-t-return-early.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d8c80751a97b0c6c4df972f6f8325293aa1607c4 * debian/tests/control: Mark systemd-fsckd flaky again. As promised in LP: 1915126, until further investigation. File: debian/tests/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=68fbaab272af81aab29497f7c6a3e4e6e9aa091b -- Balint Reczey Thu, 04 Mar 2021 12:19:05 +0100 ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Groovy) Importance: Undecided => Medium -- 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/1913763 Title: hyperv: unable to distinguish PTP devices Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Bug description: [impact] the /dev/ptp0 device for a hyperv instance may not be the correct, hyperv-provided, ptp device. [test case] on some hyperv instance types, particularly those that might contain passthrough network card(s) that also provide ptp, the first ptp device may not be the correct one to use for ptp, e.g. there may be multiple ones: $ ls /dev/ptp* /dev/ptp0 /dev/ptp1 $ cat /sys/class/ptp/ptp0/clock_name hyperv $ cat /sys/class/ptp/ptp1/clock_name mlx5_p2p the order can change across boots, so a consistent way of addressing the hyperv-provided one is needed [regression potential] any regression would involve failure to properly create the ptp symlink, or other failure while udev is processing newly detected ptp device(s) [scope] this is needed in all releases this was fixed upstream with the commit 32e868f058da8b90add00b2958c516241c532b70 which is not yet included in any release [original description] Hyperv provides a PTP device. On system with multiple PTP devices, services like Chrony don't have a way to know which one is which. We would like to have a udev rule to create a symlink to the hyperv clock. This way, services could be configured to always use this clock no matter if it is ptp0, ptp1, etc.. For example: ``` SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv" ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
** No longer affects: lxd (Ubuntu) -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1914062/+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 1895665] Re: PulseAudio automatically switches away from HDMI after display sleep
*** This bug is a duplicate of bug 1888598 *** https://bugs.launchpad.net/bugs/1888598 if I add blacklist= to load-module module-switch-on-connect, switching to HDMI is no longer inhibited, and the HDMI output is listed first in pavucontrol, but the output still disappears for good when the monitor goes to sleep. -- 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/1895665 Title: PulseAudio automatically switches away from HDMI after display sleep Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have an Nvidia based video card that has an HDMI output + a DisplayPort output. DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output is listed as "Digital Stereo (HDMI 2)". I prefer to use "Digital Stereo (HDMI 2)". But after each display sleep (screen lock for example) audio is switched to built in audio ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 15 14:56:58 2020 InstallationDate: Installed on 2020-06-20 (86 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0CNDTP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1918190] Re: Enabling/Disabling VPN crashes window manager
@3v1n0 (Marco Trevisan) has pointed out https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1651 as a possible fix ** Description changed: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F= '{print $2}' wayland $ apt-cache policy network-manager network-manager: Installed: 1.30.0-1ubuntu1 Candidate: 1.30.0-1ubuntu1 Version table: *** 1.30.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-shell gnome-shell: - Installed: 3.38.3-3ubuntu1 - Candidate: 3.38.3-3ubuntu1 - Version table: - *** 3.38.3-3ubuntu1 500 - 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 3.38.3-3ubuntu1 + Candidate: 3.38.3-3ubuntu1 + Version table: + *** 3.38.3-3ubuntu1 500 + 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages + 100 /var/lib/dpkg/status + + $ dpkg-query -W|grep mutter + gir1.2-mutter-7:amd64 3.38.3-3ubuntu1 + libmutter-7-0:amd64 3.38.3-3ubuntu1 + mutter3.38.3-3ubuntu1 + mutter-common 3.38.3-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:12:44 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled ** Also affects: mutter (Ubuntu) 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/1918190 Title: Enabling/Disabling VPN crashes window manager Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F= '{print $2}' wayland $ apt-cache policy network-manager network-manager: Installed: 1.30.0-1ubuntu1 Candidate: 1.30.0-1ubuntu1 Version table: *** 1.30.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-shell gnome-shell: Installed: 3.38.3-3ubuntu1 Candidate: 3.38.3-3ubuntu1 Version table: *** 3.38.3-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status $ dpkg-query -W|grep mutter gir1.2-mutter-7:amd64 3.38.3-3ubuntu1 libmutter-7-0:amd64 3.38.3-3ubuntu1 mutter3.38.3-3ubuntu1 mutter-common 3.38.3-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:12:44 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1
[Touch-packages] [Bug 1818027] Re: cinnamon-sessio: segfault at ip sp error 6 in libpcre.so.3.13.3[+70000]
Just confirming that this is still an issue in Ubuntu 20.10 groovy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcre3 in Ubuntu. https://bugs.launchpad.net/bugs/1818027 Title: cinnamon-sessio: segfault at ip sp error 6 in libpcre.so.3.13.3[+7] Status in pcre3 package in Ubuntu: Confirmed Bug description: When trying to start cinnamon-session, gnome-session or mate-session got the following error in dmesg and system comes back to login screen. Feb 25 12:21:57 vdc008es kernel: [ 4152.156085] mate-session[9280]: segfault at 7ffec6653f50 ip 7fcc7192f544 sp 7ffec6653f40 error 6 in libpcre.so.3.13.3[7fcc7191c000+52000] Feb 25 12:28:32 vdc008es kernel: [ 4547.063501] mate-session[11708]: segfault at 7ffdb99adfd0 ip 7f3be4ce7544 sp 7ffdb99adfc0 error 6 in libpcre.so.3.13.3[7f3be4cd4000+52000] Feb 25 12:32:59 vdc008es kernel: [ 4814.736465] gnome-session-b[14886]: segfault at 7fff0955dfc0 ip 7f0c2edb1544 sp 7fff0955dfb0 error 6 in libpcre.so.3.13.3[7f0c2ed9e000+52000] Feb 25 12:34:09 vdc008es kernel: [ 4884.530854] gnome-session-b[15428]: segfault at 7ffdda078f00 ip 7ff8ebe52544 sp 7ffdda078ef0 error 6 in libpcre.so.3.13.3[7ff8ebe3f000+52000] Feb 25 12:46:24 vdc008es kernel: [ 5619.711529] cinnamon-sessio[16509]: segfault at 7ffd76354f50 ip 7f95fd51a5b4 sp 7ffd76354f40 error 6 in libpcre.so.3.13.3[7f95fd507000+52000] Feb 25 12:47:19 vdc008es kernel: [ 5674.763774] cinnamon-sessio[16710]: segfault at 7ffc71db3f00 ip 7f2b564625b4 sp 7ffc71db3ef0 error 6 in libpcre.so.3.13.3[7f2b5644f000+52000] Feb 27 08:53:45 vdc008es kernel: [ 797.603382] cinnamon-sessio[8717]: segfault at 7fffdce58f10 ip 7ff112ea8a6a sp 7fffdce58f00 error 6 in libpcre.so.3.13.3[7ff112e9+7] Feb 27 08:54:51 vdc008es kernel: [ 863.390698] cinnamon-sessio[8916]: segfault at 7fff6482ded0 ip 7fdd97659a6a sp 7fff6482dec0 error 6 in libpcre.so.3.13.3[7fdd97641000+7] Feb 27 09:12:57 vdc008es kernel: [ 1949.158835] cinnamon-sessio[10260]: segfault at 7fff709d4f10 ip 7f358d697a6a sp 7fff709d4f00 error 6 in libpcre.so.3.13.3[7f358d67f000+7] Feb 28 08:28:39 vdc008es kernel: [ 200.816875] cinnamon-sessio[4996]: segfault at 7fff3d476e90 ip 7f053ae23a6a sp 7fff3d476e80 error 6 in libpcre.so.3.13.3[7f053ae0b000+7] Do not know if it is a configuration issue or something else. Tried removing any configuration file related to X in user home with no luck at all: rm -fRv .aptitude .aws .cache .config createLinks.sh .dbeaver-drivers .dbus .dmrc .emma .esd_auth .gconf .gimp-2.8 .gnome .gnome2 .gnome2_private .gnupg .gstreamer-0.10.history .ICEauthority .icons .install4j .java .jedit .jmc .jprofiler10 .kde .lesshst .local .mozilla .mplayer .mysql .nbi .p2 .pki.recently-used .rnd rpmbuild .rpmdb .sdbg .selected_editor .sonar .sonarlint .subversion.backup_20181228-1207 .sudo_as_admin_successful .swt .themes .thumbnails .thunderbird .tooling .tora.tse .unison .vim .viminfo VirtualBox\ VMs/ .visualvm .vscode .vscode-insiders .wget- hsts .Xauthority .xscreensaver .xsession-errors .xsession-errors.old client64/ .gstreamer-0.10/ .pki/ .recently-used Trying too with night build of cinnamon. Still the same. $ apt-cache policy cinnamon cinnamon: Installed: 3.8.8-20180729040943-bionic Candidate: 3.8.8-20180729040943-bionic Version table: *** 3.8.8-20180729040943-bionic 100 99 http://ppa.launchpad.net/gwendal-lebihan-dev/cinnamon-nightly/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 $ apt-cache policy libpcre3 libpcre3: Installed: 2:8.39-9 Candidate: 2:8.39-9 Version table: *** 2:8.39-9 600 Thanks in advance for your help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libpcre3 2:8.39-9 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 28 08:30:13 2019 Dependencies: gcc-8-base 8.2.0-1ubuntu2~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.2.0-1ubuntu2~18.04 InstallationDate: Installed on 2017-05-22 (647 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: pcre3 UpgradeStatus: Upgraded to bionic on 2018-12-27 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1818027/+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 1542471] Re: Playing mp3 files causes: Problem occurred without error being set. This is a bug in Rhythmbox or GStreamer.
** Changed in: rhythmbox (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1542471 Title: Playing mp3 files causes: Problem occurred without error being set. This is a bug in Rhythmbox or GStreamer. Status in gstreamer1.0 package in Ubuntu: Confirmed Status in rhythmbox package in Ubuntu: Incomplete Bug description: I get the following error in the console when trying to play a mp3 file using Rhythmbox: (21:23:27) [0x832a60] [rb_shell_player_error] rb-shell-player.c:2443: playback error while playing: Problem occurred without error being set. This is a bug in Rhythmbox or GStreamer. I don't get the same error while trying to play the same file using 'Video's. I installed the required codec using the 'Video's application as it told me to install a codec. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.7.1-1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia zfs zunicode zcommon znvpair zavl ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 5 21:24:05 2016 ExecutablePath: /usr/bin/rhythmbox SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1542471/+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 1895665] Re: PulseAudio automatically switches away from HDMI after display sleep
*** This bug is a duplicate of bug 1888598 *** https://bugs.launchpad.net/bugs/1888598 Here is what happens as seen by pulseaudio - during the monitor sleep/wake cycle leading to disappearance of the HDMI output: D: [pulseaudio] alsa-util.c: ELD info empty (for device=3) D: [pulseaudio] module-alsa-card.c: Jack 'HDMI/DP,pcm=3 Jack' is now unplugged D: [pulseaudio] device-port.c: Setting port hdmi-output-0 to status no D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-switch-on-port-available.c: Trying to switch away from port hdmi-output-0, found no better option I: [pulseaudio] core.c: default_sink: alsa_output.pci-_65_00.1.hdmi-stereo -> alsa_output.pci-_00_1f.3.iec958-stereo D: [pulseaudio] card.c: Setting card alsa_card.pci-_65_00.1 profile output:hdmi-stereo to availability status no D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-switch-on-port-available.c: Active profile output:hdmi-stereo on card alsa_card.pci-_65_00.1 became unavailable, switching to another profile D: [pulseaudio] sink.c: alsa_output.pci-_65_00.1.hdmi-stereo: state: SUSPENDED -> UNLINKED D: [pulseaudio] source.c: alsa_output.pci-_65_00.1.hdmi-stereo.monitor: state: SUSPENDED -> UNLINKED D: [alsa-sink-HDMI 0] alsa-sink.c: Thread shutting down I: [pulseaudio] sink.c: Freeing sink 1 "alsa_output.pci-_65_00.1.hdmi-stereo" I: [pulseaudio] source.c: Freeing source 2 "alsa_output.pci-_65_00.1.hdmi-stereo.monitor" D: [pulseaudio] card.c: alsa_card.pci-_65_00.1: active_profile: output:hdmi-stereo -> off D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] alsa-util.c: ELD info empty (for device=3) D: [pulseaudio] module-alsa-card.c: Jack 'HDMI/DP,pcm=3 Jack' is now unplugged D: [pulseaudio] alsa-util.c: ELD info empty (for device=3) Although slightly redundant, it looks all right. Part of the problem seems to come from blacklisting HDMI monitors by default (not switching to them when they are plugged in). But that's the second part of the problem. I: [pulseaudio] module-switch-on-connect.c: Refusing to switch to blacklisted sink alsa_output.pci-_65_00.1.hdmi-stereo The first and major issue is the absence of any event detection when the DP monitor wakes up. "pulseaudio -k" restarts the daemon, and probing at startup seems to find it again. -- 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/1895665 Title: PulseAudio automatically switches away from HDMI after display sleep Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have an Nvidia based video card that has an HDMI output + a DisplayPort output. DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output is listed as "Digital Stereo (HDMI 2)". I prefer to use "Digital Stereo (HDMI 2)". But after each display sleep (screen lock for example) audio is switched to built in audio ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 15 14:56:58 2020 InstallationDate: Installed on 2020-06-20 (86 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0CNDTP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1918190] Re: Enabling/Disabling VPN crashes window manager
As a workaround for anyone, you can use nmcli to bring up a VPN connection. Run `nmcli c` to get a list of connections, once you have the name you can enable it with `nmcli c up $name` or disable it with `nmcli c down $name`. -- 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/1918190 Title: Enabling/Disabling VPN crashes window manager Status in gnome-shell package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F= '{print $2}' wayland $ apt-cache policy network-manager network-manager: Installed: 1.30.0-1ubuntu1 Candidate: 1.30.0-1ubuntu1 Version table: *** 1.30.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy gnome-shell gnome-shell: Installed: 3.38.3-3ubuntu1 Candidate: 3.38.3-3ubuntu1 Version table: *** 3.38.3-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:12:44 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918190/+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 1880258] Autopkgtest regression report (systemd/237-3ubuntu10.45)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic have finished running. The following regressions have been reported in tests triggered by the package: corosync/2.4.3-0ubuntu1.1 (armhf) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el, arm64, i386, armhf, s390x) linux-hwe-5.0/5.0.0-65.71 (i386) linux-hwe-5.4/5.4.0-67.75~18.04.1 (i386) gvfs/1.36.1-0ubuntu1.3.3 (amd64) 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#systemd [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/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in network-manager source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in network-manager source package in Focal: Confirmed Status in systemd source package in Focal: Fix Committed Status in network-manager source package in Groovy: New Status in systemd source package in Groovy: Fix Committed Status in network-manager source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Committed Bug description: [impact] systemd-resolved emits a disturbingly large amount of NXDOMAIN log messages that do not actually indicate any real problem [test case] see original description, or look at any log from any recent Ubuntu system, or search google for endless complaints about NXDOMAIN messages logged by Ubuntu [regression potential] any regression would likely be isolated to systemd-resolved handling of a NXDOMAIN response from its upstream nameserver, including possibly failing to resolve a hostname or delays in resolving hostnames [scope] this is needed for all releases; the patch is not upstream, but carried by Ubuntu [original description] I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+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 1685754] Autopkgtest regression report (systemd/237-3ubuntu10.45)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic have finished running. The following regressions have been reported in tests triggered by the package: corosync/2.4.3-0ubuntu1.1 (armhf) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el, arm64, i386, armhf, s390x) linux-hwe-5.0/5.0.0-65.71 (i386) linux-hwe-5.4/5.4.0-67.75~18.04.1 (i386) gvfs/1.36.1-0ubuntu1.3.3 (amd64) 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#systemd [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/1685754 Title: 'systemd --user' unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: Invalid Status in GNOME Terminal: Confirmed Status in Nautilus: Invalid Status in systemd: Unknown Status in dbus package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Bionic: Invalid Status in gnome-terminal source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Bug description: [impact] pam_umask, from /etc/passwd, is not honored in systemd --user instances [test case] on a desktop system, edit /etc/passwd to change the test user entry (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th field). For example change: ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash to: ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash You may need to reboot for your X session to pick up the change. Then, from the graphical desktop, open a terminal and run: $ gnome-terminal -e sh in the opened terminal, run: $ umask the number shown should be 0007, as set in the passwd file [regression potential] any regression would likely result in an incorrect umask for the user whose passwd entry is modified. [scope] this is needed only for b this is fixed in systemd upstream by commit 5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in v246, so this is fixed in g and later. This commit was also picked up by Debian and included in the v245 release for focal, so this is fixed in focal already. [original description] In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+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 1878969] Autopkgtest regression report (systemd/237-3ubuntu10.45)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic have finished running. The following regressions have been reported in tests triggered by the package: corosync/2.4.3-0ubuntu1.1 (armhf) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el, arm64, i386, armhf, s390x) linux-hwe-5.0/5.0.0-65.71 (i386) linux-hwe-5.4/5.4.0-67.75~18.04.1 (i386) gvfs/1.36.1-0ubuntu1.3.3 (amd64) 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#systemd [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/1878969 Title: time-epoch never changes in SRUs Status in ubuntu-core-initramfs: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Bug description: [Impact] * Systems without hwclock come up with a fixed time epoch which is not updated in SRUs * Ideally booting with a newer built of systemd should move time epoch to be at least when systemd was last built. For example to the value of SOURCE_DATE_EPOCH. [Test Case] * Boot without network NTP or hwclock * Observe that the epoch is the same as the time when NEWS entry in the systemd source code was last touched. * Boot newer update of systemd, observe that the time epoch is at least 2020 [Regression Potential] * Bad epoch, may result in unable to perform TLS connections, validated GPG signatures, and snapd assertions. Changing epoch to be more recent is desired. Some machines may rely on the fact that "bionic" without hwclock always comes up in year 2018. But in practice that is incorrect thing to do. [Other Info] * By default option('time-epoch', type : 'integer', value : '-1', description : 'time epoch for time clients') in systemd is set to the modification time of the NEW entry time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int() If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value to be compliant with the https://reproducible- builds.org/docs/timestamps/ specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+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 1883447] Autopkgtest regression report (systemd/237-3ubuntu10.45)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic have finished running. The following regressions have been reported in tests triggered by the package: corosync/2.4.3-0ubuntu1.1 (armhf) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el, arm64, i386, armhf, s390x) linux-hwe-5.0/5.0.0-65.71 (i386) linux-hwe-5.4/5.4.0-67.75~18.04.1 (i386) gvfs/1.36.1-0ubuntu1.3.3 (amd64) 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#systemd [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/1883447 Title: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [impact] nspawn fails on armhf [test case] setup a bionic armhf system, and get a focal img/filesystem to use with systemd-nspawn, e.g. $ wget https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-armhf-root.tar.xz $ mkdir f $ cd f $ tar xvf ../focal-server-cloudimg-armhf-root.tar.xz install systemd-container, and start nspawn; then test anything that uses the time, e.g. just run python: $ systemd-nspawn Spawning container f on /root/f. Press ^] three times within 1s to kill container. root@f:~# python3 Fatal Python error: pyinit_main: can't initialize time Python runtime state: core initialized PermissionError: [Errno 1] Operation not permitted Current thread 0xf7bbd310 (most recent call first): [regression potential] any regression would likely break nspawn creation or operation of containers, particularly on armhf, but possibly on other archs [scope] this is needed only in bionic. this is fixed upstream by commit 6ca677106992321326427c89a40e1c9673a499b2 which was included first in v244, so this is fixed already in focal and later. [original description] Recent Linux kernels introduced a number of new syscalls ending in _time64 to fix Y2038 problem; it appears recent glibc, including the version in focal, test for the existence of these. systemd-nspawn in bionic (237-3ubuntu10.38) doesn't know about these so blocks them by default. It seems however glibc isn't expecting an EPERM, causing numerous programs to fail. In particular, running do-release-upgrade to focal in an nspawn container hosted on bionic will break as soon as the new libc has been unpacked. Solution (tested here) is to cherrypick upstream commit https://github.com/systemd/systemd/commit/6ca677106992321326427c89a40e1c9673a499b2 A newer libseccomp is also needed but this is already being worked on, see bug #1876055. It's a pretty trivial fix one the new libseccomp lands, and there is precedent for SRU-ing for a similar issue in bug #1840640. https://patchwork.kernel.org/patch/10756415/ is apparently the upstream kernel patch, which should give a clearer idea of which architectures are likely to be affected - I noticed it on armhf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1883447/+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 1890448] Autopkgtest regression report (systemd/237-3ubuntu10.45)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic have finished running. The following regressions have been reported in tests triggered by the package: corosync/2.4.3-0ubuntu1.1 (armhf) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el, arm64, i386, armhf, s390x) linux-hwe-5.0/5.0.0-65.71 (i386) linux-hwe-5.4/5.4.0-67.75~18.04.1 (i386) gvfs/1.36.1-0ubuntu1.3.3 (amd64) 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#systemd [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/1890448 Title: hwdb: Add EliteBook to use micmute hotkey Status in HWE Next: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [Impact] Micmute hotkey on many HP EliteBooks don't work. [Fix] Commit b6eb208b29ae ("hwdb: Add EliteBook to use micmute hotkey"), to map AT keyboard's scancode to micmute hotkey. [Test] With the one-liner fix, micmute hotkey works on all the EliteBooks I tested. [Regression Potential] The hwdb originally only matches a few EliteBook, and fix changes that to match all EliteBook models. So if there's an EliteBook that uses the scancode for other purpose, there will be a regression. However, the risk is rather slim because HP is confident that all EliteBooks use the same scancode for mic mute hotkey. [scope] this is needed for f and earlier. this is fixed upstream by commit b6eb208b29ae which is included starting in v246, so g and later are already fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1890448/+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 1902553] Autopkgtest regression report (systemd/237-3ubuntu10.45)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic have finished running. The following regressions have been reported in tests triggered by the package: corosync/2.4.3-0ubuntu1.1 (armhf) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el, arm64, i386, armhf, s390x) linux-hwe-5.0/5.0.0-65.71 (i386) linux-hwe-5.4/5.4.0-67.75~18.04.1 (i386) gvfs/1.36.1-0ubuntu1.3.3 (amd64) 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#systemd [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/1902553 Title: TEST-03 sometimes fails during autopkgtests Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Won't Fix Status in systemd source package in Bionic: Fix Committed Bug description: [impact] during autopkgtest runs, sometimes TEST-03 fails when running under qemu. [test case] check autopkgtest results, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/s/systemd/20201009_025713_c1956@/log.gz [regression potential] any regression would likely result in a failure to detect some other regression that is otherwise tested by this test case. [scope] this is needed only for bionic. upstream, this is fixed by disabling TEST-03 (and TEST-16) running under qemu, as their timing is very tight, in commit 3edc0c590d3a9212267d0a7cf56e95efa7f61039, which is included first in v239, so this is fixed already in focal and later. technically, this also is needed for xenial, however since that release is reaching ESM status early next year, and this is only an autopkgtest fix, i have no plans to update xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902553/+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 1911187] Autopkgtest regression report (systemd/237-3ubuntu10.45)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic have finished running. The following regressions have been reported in tests triggered by the package: corosync/2.4.3-0ubuntu1.1 (armhf) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el, arm64, i386, armhf, s390x) linux-hwe-5.0/5.0.0-65.71 (i386) linux-hwe-5.4/5.4.0-67.75~18.04.1 (i386) gvfs/1.36.1-0ubuntu1.3.3 (amd64) 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#systemd [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/1911187 Title: scheduled reboot reboots immediately if dbus or logind is not available Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Bug description: [IMPACT] When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately. From the sources it seems that this is intended : https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318 However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately. There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and a PR ( https://github.com/systemd/systemd/pull/18010 ). Upstream community is not willing to accept the patch but debian is. I open this bug to to pull the patch into Ubuntu once it lands in debian. [TEST PLAN] The simpler reproducer is to disable dbus to imitate the real world case. # systemctl stop dbus.service # systemctl stop dbus.socket # shutdown +1140 -r "REBOOT!" Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms) Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out Connection to groovy closed by remote host. Connection to groovy closed. [WHERE PROBLEM COULD OCCUR] This patch changes the behaviour of scheduled reboot in case logind or dbus has failed. Originally, if logind is not available (call to logind bus fails https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319) it proceeds with immediate shutdown. This patch changes this behaviour and instead of shutting down it does nothing. The actual regression potential is a user asking for a reboot and not getting it, so the largest regression potential is any existing users (human or programmatic) that are requesting a scheduled shutdown but not checking the return value for error. Any other regression would likely result in the system incorrectly not rebooted, or incorrectly scheduled for reboot. [OTHER] This is now fixed in H, currently affects B,G,F. Debian bug reports : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042 Upstream issue : https://github.com/systemd/systemd/issues/17575 PR : https://github.com/systemd/systemd/pull/18010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+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 1913189] Autopkgtest regression report (systemd/237-3ubuntu10.45)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic have finished running. The following regressions have been reported in tests triggered by the package: corosync/2.4.3-0ubuntu1.1 (armhf) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el, arm64, i386, armhf, s390x) linux-hwe-5.0/5.0.0-65.71 (i386) linux-hwe-5.4/5.4.0-67.75~18.04.1 (i386) gvfs/1.36.1-0ubuntu1.3.3 (amd64) 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#systemd [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/1913189 Title: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1 Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Bug description: [impact] test-fs-util fails when running under 5.8 kernel [test case] see autopkgtest runs, e.g. amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz [regression potential] any regression would likely result in incorrectly passed or failed build-time or autopkgtest-time test run [scope] this is needed in f and b this was fixed upstream with commit 5b5ce6298e which was first included in v247, and has already been backported to g in bug 1891527. while it's unlikely that the 5.8 kernel will ever officially be available directly in b, this test case is also run at build time, so if the lp build farm is ever updated to the 5.8 kernel this test case would begin failing during build, so the patch should be backported there as well. this isn't needed in x as the test-fs-util test isn't present there. [original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20210121_021134_f3c65@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20210121_090718_fa164@/log.gz The failing test case is: TEST-24-UNIT-TESTS: === Failed test log === --- test-fs-util begin --- /* test_chase_symlinks */ /* test_unlink_noerrno */ /* test_readlink_and_make_absolute */ /* test_var_tmp */ /* test_dot_or_dot_dot */ /* test_access_fd */ /* test_touch_file */ Assertion 'mknod(a, 0775 | S_IFBLK, makedev(0, 0)) >= 0' failed at src/test/test-fs-util.c:637, funct ion test_touch_file(). Aborting. --- test-fs-util end --- make: Leaving directory '/tmp/autopkgtest.KFUfZH/build.scn/src/test/TEST-24-UNIT-TESTS' make: *** [Makefile:4: run] Error 1 This issue has been solved in Groovy on bug 1891527, likely the fix needs to be backported to systemd in Focal for the testcase to pass with the 5.8 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1913189/+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 1913423] Autopkgtest regression report (systemd/237-3ubuntu10.45)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic have finished running. The following regressions have been reported in tests triggered by the package: corosync/2.4.3-0ubuntu1.1 (armhf) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el, arm64, i386, armhf, s390x) linux-hwe-5.0/5.0.0-65.71 (i386) linux-hwe-5.4/5.4.0-67.75~18.04.1 (i386) gvfs/1.36.1-0ubuntu1.3.3 (amd64) 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#systemd [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/1913423 Title: getgrouplist is not thread safe with libnss_systemd Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Bug description: [impact] programs calling getgrouplist() may crash as it is not thread-safe [test case] see upstream bug description for sample c program to reproduce: https://github.com/systemd/systemd/issues/17007#issue-698123284 [regression potential] any regression would likely occur when creating a hashmap in systemd, or when any multi-threaded programs concurrently create (and use) the hashmap [scope] this is needed for f and b this is fixed upstream by commit ae0b700a856c0ae460d271bb50dccfaae84dbcab, already included in g/h (per comment 1). [original description] This upstream issue (https://github.com/systemd/systemd/issues/17007) is affecting the latest version of systemd in Ubuntu Focal. It has been fixed upstream with https://github.com/systemd/systemd/pull/17033. Can we have this patched for Focal please as it causes Mesos to randomly segfault on start. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913423/+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 1913763] Autopkgtest regression report (systemd/237-3ubuntu10.45)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.45) for bionic have finished running. The following regressions have been reported in tests triggered by the package: corosync/2.4.3-0ubuntu1.1 (armhf) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) openssh/1:7.6p1-4ubuntu0.3 (amd64, ppc64el, arm64, i386, armhf, s390x) linux-hwe-5.0/5.0.0-65.71 (i386) linux-hwe-5.4/5.4.0-67.75~18.04.1 (i386) gvfs/1.36.1-0ubuntu1.3.3 (amd64) 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#systemd [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/1913763 Title: hyperv: unable to distinguish PTP devices Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Bug description: [impact] the /dev/ptp0 device for a hyperv instance may not be the correct, hyperv-provided, ptp device. [test case] on some hyperv instance types, particularly those that might contain passthrough network card(s) that also provide ptp, the first ptp device may not be the correct one to use for ptp, e.g. there may be multiple ones: $ ls /dev/ptp* /dev/ptp0 /dev/ptp1 $ cat /sys/class/ptp/ptp0/clock_name hyperv $ cat /sys/class/ptp/ptp1/clock_name mlx5_p2p the order can change across boots, so a consistent way of addressing the hyperv-provided one is needed [regression potential] any regression would involve failure to properly create the ptp symlink, or other failure while udev is processing newly detected ptp device(s) [scope] this is needed in all releases this was fixed upstream with the commit 32e868f058da8b90add00b2958c516241c532b70 which is not yet included in any release [original description] Hyperv provides a PTP device. On system with multiple PTP devices, services like Chrony don't have a way to know which one is which. We would like to have a udev rule to create a symlink to the hyperv clock. This way, services could be configured to always use this clock no matter if it is ptp0, ptp1, etc.. For example: ``` SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv" ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1918190] Re: Enabling/Disabling VPN crashes window manager
This looks to be around the time of the issue where I disabled a VPN connection (from syslog): Mar 8 14:11:54 splat gnome-shell[677801]: ** Mar 8 14:11:54 splat gnome-shell[677801]: Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor)) Mar 8 14:11:54 splat gnome-shell[677801]: Bail out! Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor)) Mar 8 14:11:54 splat gnome-shell[677801]: GNOME Shell crashed with signal 6 Mar 8 14:11:54 splat gnome-shell[677801]: == Stack trace for context 0x556edc56f150 == Mar 8 14:11:54 splat gnome-shell[677801]: #0 556edea1ffc0 i resource:///org/gnome/shell/ui/popupMenu.js:390 (1162dc8fad80 @ 138) Mar 8 14:11:54 splat gnome-shell[677801]: #1 556edea1ff18 i resource:///org/gnome/shell/ui/status/network.js:1429 (2ab06bf803d0 @ 171) Mar 8 14:11:54 splat gnome-shell[677801]: #2 556edea1fe80 i resource:///org/gnome/shell/ui/status/network.js:171 (2ab06bf82560 @ 111) Mar 8 14:11:54 splat gnome-shell[677801]: #3 7ffef0da2770 b self-hosted:850 (b5d5c736d80 @ 454) Mar 8 14:11:54 splat gnome-shell[677801]: #4 556edea1fde0 i resource:///org/gnome/shell/ui/popupMenu.js:411 (1162dc8face0 @ 56) Mar 8 14:11:54 splat gnome-shell[677801]: #5 556edea1fd48 i resource:///org/gnome/shell/ui/popupMenu.js:398 (1162dc8fad30 @ 41) Mar 8 14:11:54 splat gnome-shell[677801]: #6 556edea1fca8 i resource:///org/gnome/shell/ui/popupMenu.js:138 (1162dc8fb4c0 @ 88) Mar 8 14:11:54 splat systemd[1]: Starting Network Manager Script Dispatcher Service... Mar 8 14:11:54 splat dbus-daemon[1286]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' ** Attachment added: "journal" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1918190/+attachment/5474636/+files/journal ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Description changed: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F= '{print $2}' wayland $ apt-cache policy network-manager network-manager: - Installed: 1.30.0-1ubuntu1 - Candidate: 1.30.0-1ubuntu1 + Installed: 1.30.0-1ubuntu1 + Candidate: 1.30.0-1ubuntu1 + Version table: + *** 1.30.0-1ubuntu1 500 + 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages + 100 /var/lib/dpkg/status + + $ apt-cache policy gnome-shell + gnome-shell: + Installed: 3.38.3-3ubuntu1 + Candidate: 3.38.3-3ubuntu1 Version table: - *** 1.30.0-1ubuntu1 500 + *** 3.38.3-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:12:44 2021 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) RebootRequiredPkgs: - libssl1.1 - libssl1.1 + libssl1.1 + libssl1.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.30.0 connected started full enabled enabled disabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.30.0 connected started full enabled enabled disabled enabled enabled -- 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/1918190 Title: Enabling/Disabling VPN crashes window manager Status in gnome-shell package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Descr
[Touch-packages] [Bug 1918190] [NEW] Enabling/Disabling VPN crashes window manager
Public bug reported: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F= '{print $2}' wayland $ apt-cache policy network-manager network-manager: Installed: 1.30.0-1ubuntu1 Candidate: 1.30.0-1ubuntu1 Version table: *** 1.30.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:12:44 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1918190 Title: Enabling/Disabling VPN crashes window manager Status in network-manager package in Ubuntu: New Bug description: When I click on a VPN connection in the Gnome top bar to enable or disable the connection the entire desktop session crashes and dumps me at the session login screen. $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ loginctl show-session $(awk '/tty/ {print $1}' <(loginctl)) -p Type | awk -F= '{print $2}' wayland $ apt-cache policy network-manager network-manager: Installed: 1.30.0-1ubuntu1 Candidate: 1.30.0-1ubuntu1 Version table: *** 1.30.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:12:44 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-21 (1416 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) RebootRequiredPkgs: libssl1.1 libssl1.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1918190/+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 1895665] Re: PulseAudio automatically switches away from HDMI after display sleep
*** This bug is a duplicate of bug 1888598 *** https://bugs.launchpad.net/bugs/1888598 Hi! Affected by this bug, but not exactly bug #1888598. Config: Asus Extreme Omega integrated HDA Intel PCH as Card 1 + ASUS Nvidia 3090 as Card 2. Card 0 is an USB webcam and only an audio input. Problem occurs as described: the audio output changes when the monitor connected to a DisplayPort output goes to sleep (after locking). No need for the computer to go through a sleep/wake cycle. Normal operation is restored by 'pulseaudio -k', then choosing the correct output using e.g. pavucontrol. Commands 'pactl list' and 'pacmd list-cards' give different results: pacmd list-cards: before: HDMI output is available ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: yes) properties: device.icon_name = "video-display" device.product.name = "Acer T272HUL after: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" pactl list: before: Ports : hdmi-output-0: HDMI / DisplayPort (priority: 5900, latency offset: 0 usec, available) Propriétés : device.icon_name = "video-display" device.product.name = "Acer T272HUL " Partie du(des) profil(s) : output:hdmi-stereo after: Ports : hdmi-output-0: HDMI / DisplayPort (priority: 5900, latency offset: 0 usec, not available) Propriétés : device.icon_name = "video-display" Partie du(des) profil(s) : output:hdmi-stereo -- 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/1895665 Title: PulseAudio automatically switches away from HDMI after display sleep Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have an Nvidia based video card that has an HDMI output + a DisplayPort output. DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output is listed as "Digital Stereo (HDMI 2)". I prefer to use "Digital Stereo (HDMI 2)". But after each display sleep (screen lock for example) audio is switched to built in audio ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 15 14:56:58 2020 InstallationDate: Installed on 2020-06-20 (86 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0CNDTP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1918186] [NEW] tracker-store crashed with signal 5 in g_printerr()
Public bug reported: Just happened, didn't really do anything. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Mar 8 14:50:14 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (8 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store RebootRequiredPkgs: evolution-data-server Signal: 5 SourcePackage: tracker StacktraceTop: g_printerr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libsqlite3.so.0 () () () Title: tracker-store crashed with signal 5 in g_printerr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash hirsute need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1918186 Title: tracker-store crashed with signal 5 in g_printerr() Status in tracker package in Ubuntu: New Bug description: Just happened, didn't really do anything. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Mar 8 14:50:14 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (8 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store RebootRequiredPkgs: evolution-data-server Signal: 5 SourcePackage: tracker StacktraceTop: g_printerr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libsqlite3.so.0 () () () Title: tracker-store crashed with signal 5 in g_printerr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1918186/+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 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly
Thank you for taking the time to file a bug report. >From what you described it seems that Network Manager is the one responsible for adding the unexpected routing rule, so this might not affect OpenVPN itself. I quickly tried to reproduce your setup but did not notice the bug there. Could you please share your config files to see if I missed something? Since there is not enough information in your report to begin triage or to differentiate between a local configuration problem and a bug in Ubuntu, I am marking this bug as "Incomplete". We would be grateful if you would: provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu) Status: New => Incomplete ** Changed in: openvpn (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/1917887 Title: Network Manager OpenVPN nested connections fail to setup routes correctly Status in network-manager package in Ubuntu: Incomplete Status in openvpn package in Ubuntu: Incomplete Bug description: Setup: Host lan: 192.168.0.238/24 Host Default gw: 192.168.0.1 ip route: default via 192.168.0.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 Primary OpenVPN (check "Use this connection only for resources on its network"): server ip: public a.b.c.d OpenVPN Tunnel: 192.168.1.0/24 routes pushed: 192.168.100.0/24 First VPN works OK: default via 192.168.0.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 Secondary OpenVPN (check "Use this connection only for resources on its network"): server ip: private 192.168.100.10 OpenVPN Tunnel: 192.168.20.0/24 routes pushed: 192.168.200.0/24 Second VPN Connect OK, routing table is wrong: default via 192.168.0.1 dev eno1 proto dhcp metric 100 192.168.200.0/24 via 192.168.20.1 dev tun1 192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is wrong, the openVPN#2 Gateway is not on the local lan Correct routing table using "sudo /usr/sbin/openvpn /path/to/config.openvpn" (same a Network Manager) default via 192.168.0.1 dev eno1 proto dhcp metric 100 192.168.200.0/24 via 192.168.20.1 dev tun1 192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 It seems that Network Manager add a wrong additional route not added by the openvpn bin: 192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openvpn 2.4.7-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 12:44:39 2021 InstallationDate: Installed on 2021-02-19 (13 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1917887/+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/ListH
[Touch-packages] [Bug 1906331] Re: systemd-resolve crashes fairly often (and reports various assertions)
Do you plan releasing this version on PPA (for 20.04, which I use)? I'd be glad to test… -- 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/1906331 Title: systemd-resolve crashes fairly often (and reports various assertions) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Status in systemd source package in Hirsute: Fix Released Bug description: [impact] systemd-resolved crashes [test case] see original description; I can't reproduce so I'm relying on the reporter(s) to test/verify. [regression potential] any regression would likely occur while processing sd_event objects, which are used throughout systemd code; this could result in crashes in almost any part of systemd code. However a more likely regression would be leaks of sd_event objects due to failure to release the final ref for an object. [scope] This is needed for f/g/h This might be fixed by upstream commit f814c871e65df8552a055dd887bc94b074037833; if so, that commit isn't included in any systemd release yet, and so is needed in h and earlier. [other info] I believe this is caused by a freed sd_event object that is then processed and calls the on_query_timeout callback with invalid state, leading to failed assertion, which causes resolved to crash; that's what analysis of the crash dump appears to indicate. This may be fixed by the upstream commit referenced in [scope], which takes additional refs during function calls. However I haven't reproduced this myself, so I'm only guessing as to the cause and solution at this point. I'm unsure why this would not occur in bionic, but per comment 5 it seems it doesn't happen in that release. [original description] (Tested on regularly updated Ubuntu 20.04, currently i use systemd 245.4-4ubuntu3.2) I observe fairly lot of segfaults of systemd-resolve. Frequency vary but … see below. I have no clue what is the reason. Specific feature of my machine is that apart from normal cable connection (to OpenWRT router) I use OpenVPN for business network (and this submits specific nameserver for myorg.local domain). ~ $ LC_ALL=C dmesg -T --level=info | grep systemd-resolve [Sun Nov 29 11:47:37 2020] systemd-resolve[1629307]: segfault at 190eed7bdc6 ip 7fd98f771dc9 sp 7ffc2352a100 error 4 in libsystemd-shared-245.so[7fd98f74c000+16e000] [Sun Nov 29 11:57:27 2020] systemd-resolve[1629787]: segfault at 1f ip 55ab7b0cb686 sp 7fff78ce4bd0 error 4 in systemd-resolved[55ab7b0a4000+3e000] [Sun Nov 29 12:07:37 2020] systemd-resolve[1630481]: segfault at 191 ip 55ca69fed91c sp 7ffc4d757dc0 error 6 in systemd-resolved[55ca69fc2000+3e000] [Sun Nov 29 13:12:26 2020] systemd-resolve[1638829]: segfault at 19224162371 ip 7fc1bc9b9dc9 sp 7ffc21378170 error 4 in libsystemd-shared-245.so[7fc1bc994000+16e000] [Sun Nov 29 13:32:57 2020] systemd-resolve[1639886]: segfault at 1926d8126d3 ip 7f7ed17e9dc9 sp 7ffda2cea0b0 error 4 in libsystemd-shared-245.so[7f7ed17c4000+16e000] [Sun Nov 29 13:42:37 2020] systemd-resolve[1640246]: segfault at 61 ip 558d992e2686 sp 7fff08906af0 error 4 in systemd-resolved[558d992bb000+3e000] [Sun Nov 29 15:42:26 2020] systemd-resolve[1645397]: segfault at 1943c92afc7 ip 7fd4c1721dc9 sp 7fff25259ce0 error 4 in libsystemd-shared-245.so[7fd4c16fc000+16e000] [Sun Nov 29 16:02:36 2020] systemd-resolve[1646052]: segfault at 1947ecb3726 ip 7f1008549dc9 sp 7fff44a6db70 error 4 in libsystemd-shared-245.so[7f1008524000+16e000] [Sun Nov 29 17:42:35 2020] systemd-resolve[1649403]: segfault at 71 ip 55a37fe5a686 sp 7ffd9a160440 error 4 in systemd-resolved[55a37fe33000+3e000] [Sun Nov 29 17:52:35 2020] systemd-resolve[1649759]: segfault at 558d292947d0 ip 558d292947d0 sp 7ffec7ab3bf8 error 15 [Sun Nov 29 19:17:55 2020] systemd-resolve[1652349]: segfault at 558995b77cf0 ip 558995b77cf0 sp 7ffe545ae4a8 error 15 [Sun Nov 29 19:32:35 2020] systemd-resolve[1652640]: segfault at 19773c20194 ip 7f66bb529dc9 sp 7fffd7066fc0 error 4 in libsystemd-shared-245.so[7f66bb504000+16e000] [Sun Nov 29 20:03:54 2020] systemd-resolve[1653715]: segfault at 197e3aee918 ip 7fdc40b51dc9 sp 7ffde484fbf0 error 4 in libsystemd-shared-245.so[7fdc40b2c000+16e000] [Sun Nov 29 20:22:24 2020] systemd-resolve[1654540]: segfault at 19820a05297 ip 7f6a92839dc9 sp 7ffe4ba00440 error 4 in libsystemd-shared-245.so[7f6a92814000+16e000] [Sun Nov 29 21:13:10 2020] systemd-resolve[1660272]: segfault at 555f9a5915e0 ip 555f9a5915e0 sp 7fff053e5e68 error 15 [Sun Nov 29 21:32:34 2020] systemd-resolve[1661026]: segfault at 1991af73f2e ip 7ff194021dc9 sp
[Touch-packages] [Bug 1917424] Re: LVM2 hook not executable; causes update-initramfs to miss adding lvm2 binaries
*** This bug is a duplicate of bug 1915579 *** https://bugs.launchpad.net/bugs/1915579 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1917424 Title: LVM2 hook not executable; causes update-initramfs to miss adding lvm2 binaries Status in lvm2 package in Ubuntu: Confirmed Bug description: I did an upgrade from Groovy to Hirsute today, but the upgrade did not go well. I run an encrypted LVM for my root Ubuntu partition. My grub did not get updated properly at upgrade time, but via a USB startup disk for Hirsute I was able to repair this myself. However, I spent hours trying to get grub to detect my LVs. Ultimately, I found the problem: /usr/share/initramfs-tools/hooks/lvm2 in the lvm2_2.03.11-2ubuntu2_amd64.deb package lacks an executable flag. Running update-initramfs verbosely highlighted that the hook was not getting fired for this reason. Upon adding the executable flag to the file, I was able to use a chroot to re-build the initramfs and get my system to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917424/+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 1906331] Re: systemd-resolve crashes fairly often (and reports various assertions)
This bug was fixed in the package systemd - 247.3-1ubuntu4 --- systemd (247.3-1ubuntu4) hirsute; urgency=medium [ Dimitri John Ledkov ] * d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch: Patch updated to reduce log level to debug https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=299002546ec2d62e7f0dd7d614ba958fc9df83c2 [ Dan Streetman ] * d/p/lp1906331-sd-event-ref-event-loop-while-in-sd_event_prepare-ot.patch: Take event reference while processing (LP: #1906331) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1bc38abcd3b62d317fcb62b72e26d9cb2e35ccf9 * d/p/lp1917458-udev-rules-add-rule-to-create-dev-ptp_hyperv.patch: Create symlink for hyperv-provided ptp device (LP: #1917458) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f1ee790ad66395457ca64cb5f8a01fdd8aabe47 [ Balint Reczey ] * Pick proposed patch for not returning early in udevadm (LP: #1914062) File: debian/patches/lp1914062-udevadm-don-t-return-early.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d8c80751a97b0c6c4df972f6f8325293aa1607c4 * debian/tests/control: Mark systemd-fsckd flaky again. As promised in LP: 1915126, until further investigation. File: debian/tests/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=68fbaab272af81aab29497f7c6a3e4e6e9aa091b -- Balint Reczey Thu, 04 Mar 2021 12:19:05 +0100 ** Changed in: systemd (Ubuntu Hirsute) 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/1906331 Title: systemd-resolve crashes fairly often (and reports various assertions) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Status in systemd source package in Hirsute: Fix Released Bug description: [impact] systemd-resolved crashes [test case] see original description; I can't reproduce so I'm relying on the reporter(s) to test/verify. [regression potential] any regression would likely occur while processing sd_event objects, which are used throughout systemd code; this could result in crashes in almost any part of systemd code. However a more likely regression would be leaks of sd_event objects due to failure to release the final ref for an object. [scope] This is needed for f/g/h This might be fixed by upstream commit f814c871e65df8552a055dd887bc94b074037833; if so, that commit isn't included in any systemd release yet, and so is needed in h and earlier. [other info] I believe this is caused by a freed sd_event object that is then processed and calls the on_query_timeout callback with invalid state, leading to failed assertion, which causes resolved to crash; that's what analysis of the crash dump appears to indicate. This may be fixed by the upstream commit referenced in [scope], which takes additional refs during function calls. However I haven't reproduced this myself, so I'm only guessing as to the cause and solution at this point. I'm unsure why this would not occur in bionic, but per comment 5 it seems it doesn't happen in that release. [original description] (Tested on regularly updated Ubuntu 20.04, currently i use systemd 245.4-4ubuntu3.2) I observe fairly lot of segfaults of systemd-resolve. Frequency vary but … see below. I have no clue what is the reason. Specific feature of my machine is that apart from normal cable connection (to OpenWRT router) I use OpenVPN for business network (and this submits specific nameserver for myorg.local domain). ~ $ LC_ALL=C dmesg -T --level=info | grep systemd-resolve [Sun Nov 29 11:47:37 2020] systemd-resolve[1629307]: segfault at 190eed7bdc6 ip 7fd98f771dc9 sp 7ffc2352a100 error 4 in libsystemd-shared-245.so[7fd98f74c000+16e000] [Sun Nov 29 11:57:27 2020] systemd-resolve[1629787]: segfault at 1f ip 55ab7b0cb686 sp 7fff78ce4bd0 error 4 in systemd-resolved[55ab7b0a4000+3e000] [Sun Nov 29 12:07:37 2020] systemd-resolve[1630481]: segfault at 191 ip 55ca69fed91c sp 7ffc4d757dc0 error 6 in systemd-resolved[55ca69fc2000+3e000] [Sun Nov 29 13:12:26 2020] systemd-resolve[1638829]: segfault at 19224162371 ip 7fc1bc9b9dc9 sp 7ffc21378170 error 4 in libsystemd-shared-245.so[7fc1bc994000+16e000] [Sun Nov 29 13:32:57 2020] systemd-resolve[1639886]: segfault at 1926d8126d3 ip 7f7ed17e9dc9 sp 7ffda2cea0b0 error 4 in libsystemd-shared-245.so[7f7ed17c4000+16e000] [Sun Nov 29 13:42:37 2020] systemd-resolve[1640246]: segfault at 61 ip 558d992e2686 sp 7fff08906af0 error 4 in systemd-resolved[558d992bb
[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
This bug was fixed in the package systemd - 247.3-1ubuntu4 --- systemd (247.3-1ubuntu4) hirsute; urgency=medium [ Dimitri John Ledkov ] * d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch: Patch updated to reduce log level to debug https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=299002546ec2d62e7f0dd7d614ba958fc9df83c2 [ Dan Streetman ] * d/p/lp1906331-sd-event-ref-event-loop-while-in-sd_event_prepare-ot.patch: Take event reference while processing (LP: #1906331) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1bc38abcd3b62d317fcb62b72e26d9cb2e35ccf9 * d/p/lp1917458-udev-rules-add-rule-to-create-dev-ptp_hyperv.patch: Create symlink for hyperv-provided ptp device (LP: #1917458) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f1ee790ad66395457ca64cb5f8a01fdd8aabe47 [ Balint Reczey ] * Pick proposed patch for not returning early in udevadm (LP: #1914062) File: debian/patches/lp1914062-udevadm-don-t-return-early.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d8c80751a97b0c6c4df972f6f8325293aa1607c4 * debian/tests/control: Mark systemd-fsckd flaky again. As promised in LP: 1915126, until further investigation. File: debian/tests/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=68fbaab272af81aab29497f7c6a3e4e6e9aa091b -- Balint Reczey Thu, 04 Mar 2021 12:19:05 +0100 ** Changed in: systemd (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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1917458] Re: ptp0 device under hyperv may not be correct
*** This bug is a duplicate of bug 1913763 *** https://bugs.launchpad.net/bugs/1913763 This bug was fixed in the package systemd - 247.3-1ubuntu4 --- systemd (247.3-1ubuntu4) hirsute; urgency=medium [ Dimitri John Ledkov ] * d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch: Patch updated to reduce log level to debug https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=299002546ec2d62e7f0dd7d614ba958fc9df83c2 [ Dan Streetman ] * d/p/lp1906331-sd-event-ref-event-loop-while-in-sd_event_prepare-ot.patch: Take event reference while processing (LP: #1906331) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1bc38abcd3b62d317fcb62b72e26d9cb2e35ccf9 * d/p/lp1917458-udev-rules-add-rule-to-create-dev-ptp_hyperv.patch: Create symlink for hyperv-provided ptp device (LP: #1917458) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f1ee790ad66395457ca64cb5f8a01fdd8aabe47 [ Balint Reczey ] * Pick proposed patch for not returning early in udevadm (LP: #1914062) File: debian/patches/lp1914062-udevadm-don-t-return-early.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d8c80751a97b0c6c4df972f6f8325293aa1607c4 * debian/tests/control: Mark systemd-fsckd flaky again. As promised in LP: 1915126, until further investigation. File: debian/tests/control https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=68fbaab272af81aab29497f7c6a3e4e6e9aa091b -- Balint Reczey Thu, 04 Mar 2021 12:19:05 +0100 ** Changed in: systemd (Ubuntu Hirsute) 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/1917458 Title: ptp0 device under hyperv may not be correct Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Status in systemd source package in Hirsute: Fix Released Bug description: [impact] the /dev/ptp0 device for a hyperv instance may not be the correct, hyperv-provided, ptp device. [test case] on some hyperv instance types, particularly those that might contain passthrough network card(s) that also provide ptp, the first ptp device may not be the correct one to use for ptp, e.g. there may be multiple ones: $ ls /dev/ptp* /dev/ptp0 /dev/ptp1 $ cat /sys/class/ptp/ptp0/clock_name hyperv $ cat /sys/class/ptp/ptp1/clock_name mlx5_p2p the order can change across boots, so a consistent way of addressing the hyperv-provided one is needed [regression potential] any regression would involve failure to properly create the ptp symlink, or other failure while udev is processing newly detected ptp device(s) [scope] this is needed in all releases this was fixed upstream with the commit 32e868f058da8b90add00b2958c516241c532b70 which is not yet included in any release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1917458/+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
Re: [Touch-packages] [Bug 1916877] Re: Bluetooth sound card not detected
Thanks for reply. I remove pipewire by using `Muon package manager` and then restart computer. Still no sound and dummy output. Daniel van Vugt <1916...@bugs.launchpad.net>, 8 Mar 2021 Pzt, 03:35 tarihinde şunu yazdı: > This sounds like bug 1897965, which might now be affecting 20.04.2. > Please try the suggestions in bug 1897965. > > ** Changed in: alsa-driver (Ubuntu) >Status: New => Incomplete > > ** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1916877 > > Title: > Bluetooth sound card not detected > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > "Dummy output" is on audio volume setting and there is no sound > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-44-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.16 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/seq', '/dev/snd/timer'] > failed with exit code 1: > CasperMD5CheckResult: skip > CurrentDesktop: KDE > Date: Thu Feb 25 06:06:58 2021 > InstallationDate: Installed on 2021-02-24 (0 days ago) > InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 > (20210209.1) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Title: Bluetooth sound card not detected > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/11/2007 > dmi.bios.release: 5.2 > dmi.bios.vendor: Phoenix Technologies LTD > dmi.bios.version: R0052N7 > dmi.board.asset.tag: N/A > dmi.board.name: VAIO > dmi.board.vendor: Sony Corporation > dmi.board.version: N/A > dmi.chassis.type: 10 > dmi.chassis.vendor: Sony Corporation > dmi.chassis.version: N/A > dmi.ec.firmware.release: 5.2 > dmi.modalias: > dmi:bvnPhoenixTechnologiesLTD:bvrR0052N7:bd07/11/2007:br5.2:efr5.2:svnSonyCorporation:pnVGN-TZ150N:pvrJ002NHLG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: > dmi.product.family: N/A > dmi.product.name: VGN-TZ150N > dmi.product.sku: N/A > dmi.product.version: J002NHLG > dmi.sys.vendor: Sony Corporation > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1916877/+subscriptions > -- 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/1916877 Title: Bluetooth sound card not detected Status in pulseaudio package in Ubuntu: Incomplete Bug description: "Dummy output" is on audio volume setting and there is no sound ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Feb 25 06:06:58 2021 InstallationDate: Installed on 2021-02-24 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2007 dmi.bios.release: 5.2 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0052N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 5.2 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0052N7:bd07/11/2007:br5.2:efr5.2:svnSonyCorporation:pnVGN-TZ150N:pvrJ002NHLG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-TZ150N dmi.product.sku: N/A dmi.product.version: J002NHLG dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1916877/+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 1915547] Re: Users are prompted by ucf on upgrade from Trusty to Xenial
Thanks for the review Robie, I have tested the package on the proposed pocket by using this script: #!/bin/sh set -x series=trusty name=$series-upgrade multipass delete $name multipass purge multipass launch $series --name $name multipass exec $name -- sudo sh -c "cat
[Touch-packages] [Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
** Also affects: wireshark (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916705 Title: glib2.0 >=2.67.3 breaks include from an extern C context Status in glib2.0 package in Ubuntu: Fix Released Status in open-vm-tools package in Ubuntu: New Status in qemu package in Ubuntu: Fix Released Status in ukui-control-center package in Ubuntu: Triaged Status in wireshark package in Ubuntu: New Bug description: qemu now breaks in Hirsute (it didn't 23h ago) Broken: https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz Good before: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages Error: ../../disas/arm-a64.cc In file included from /usr/include/glib-2.0/glib/gmacros.h:241, from /usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9, from /usr/include/glib-2.0/glib/gtypes.h:32, from /usr/include/glib-2.0/glib/galloca.h:32, from /usr/include/glib-2.0/glib.h:30, from /<>/qemu-5.2+dfsg/include/glib-compat.h:32, from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126, from ../../disas/arm-a64.cc:21: /usr/include/c++/10/type_traits:56:3: error: template with C linkage 56 | template | ^~~~ ../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here 20 | extern "C" { | ^~ Also in disas/nanomips.cpp, ... And indeed disas/arm-a64.cc has: 20 extern "C" { 21 #include "qemu/osdep.h" 22 #include "disas/dis-asm.h" 23 } Through the chain of headers as reported above this gets to the templates in /usr/include/c++/10/type_traits which fails due to that. So C++ constructs within a C scope which is this bug. Upstream qemu has not recently changed yet for this. The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc: Include osdep.h first" by Peter Maydell. But what was different before to break it now? To find that I was comparing Hirsute vs Hirsute-proposed ... It is indeed failing in -proposed but working in hirsute-release. 10.2.1-20ubuntu1 : bad repro in broken build: $ cd /root/qemu-5.2+dfsg/b/qemu $ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 -I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr -I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall -Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef -Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 -ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem /root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote /root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote /root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote /root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d -o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp With that I have a test env... Doko asked me to test https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1 It must be something else. The difference were ~340 packages I was upgrading them to spot what broke it. I eventually found glib 2.66 -> 2.67 to break it. libglib2.0-0/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1] libglib2.0-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1] libglib2.0-data/hirsute-proposed 2.67.4-1 all [upgradable from: 2.66.4-1] libglib2.0-dev-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1] libglib2.0-dev/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1] Old: /* * We can only use __typeof__ on GCC >= 4.8, and not when compiling
[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
Hi Dimitri, These are the dkms packages which had the build failure fixed after the -hwe switch in Focal from 5.4 to 5.8: bcmwl=6.30.223.271+bdcom-0ubuntu7~20.04.1 nvidia-graphics-drivers-340=340.108-0ubuntu5.20.04.1 virtualbox-hwe=6.1.16-dfsg-6ubuntu1.20.04.1 And this is the list of all the other dkms packages which had to be updated to fix build failures in Focal with the 5.8 kernel: acpi-call=1.1.0-5ubuntu0.1 backport-iwlwifi-dkms=8324-0ubuntu3~20.04.2 dahdi-linux=1:2.11.1~dfsg-1ubuntu6.1 dm-writeboost=2.2.9-1ubuntu1.1 evdi=1.7.0+dfsg-1ubuntu1~20.04.2 gost-crypto=0.3.2-2ubuntu0.1 iptables-netflow=2.4-2ubuntu0.2 lime-forensics=1.9-1ubuntu0.1 lttng-modules=2.12.2-1ubuntu1~20.04.1 openafs=1.8.4~pre1-1ubuntu2.1 oss4=4.2-build2010-5ubuntu6~20.04.1 r8168=8.048.00-1ubuntu0.20.04.1 rtl8812au=4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.1 sysdig=0.26.4-1ubuntu0.2 v4l2loopback=0.12.3-1ubuntu0.3 virtualbox=6.1.16-dfsg-6~ubuntu1.20.04.1 zfs-linux=0.8.3-1ubuntu12.6 None of these updates has been released to -security, so if we want to make sure that users running the hwe-5.8 kernel from -security will not get broken dkms packages we need to release them all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in apt package in Ubuntu: Invalid Status in dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
The issue with the dkms package has been fixed via bug 1915051. ** Changed in: dkms (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in apt package in Ubuntu: Invalid Status in dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+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 1902236] Re: Duplicated root and nobody returned by getent on Focal
Verification procedure on Focal: $ lxc launch focal lp1902236-f Creating lp1902236-f Starting lp1902236-f $ lxc exec lp1902236-f bash root@lp1902236-f:~# getent passwd | grep root root:x:0:0:root:/root:/bin/bash root:x:0:0:root:/root:/bin/sh root@lp1902236-f:~# getent passwd | grep nobody nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin nobody:x:65534:65534:nobody:/:/usr/sbin/nologin # Enable proposed root@lp1902236-f:~# vim /etc/apt/sources.list root@lp1902236-f:~# apt update && apt-get dist-upgrade Calculating upgrade... Done The following packages will be upgraded: libnss-systemd (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) libpam-systemd (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) libsystemd0 (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) libudev1 (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) systemd (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) systemd-sysv (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) systemd-timesyncd (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) udev (245.4-4ubuntu3.4 => 245.4-4ubuntu3.5) 8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 5845 kB of archives. After this operation, 15.4 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libnss-systemd amd64 245.4-4ubuntu3.5 [95.8 kB] Get:2 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 udev amd64 245.4-4ubuntu3.5 [1366 kB] Get:3 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libudev1 amd64 245.4-4ubuntu3.5 [81.2 kB] Get:4 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 systemd-sysv amd64 245.4-4ubuntu3.5 [10.3 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 systemd-timesyncd amd64 245.4-4ubuntu3.5 [28.1 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libpam-systemd amd64 245.4-4ubuntu3.5 [186 kB] Get:7 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 systemd amd64 245.4-4ubuntu3.5 [3805 kB] Get:8 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libsystemd0 amd64 245.4-4ubuntu3.5 [274 kB] Fetched 5845 kB in 2s (2391 kB/s) ... Setting up libnss-systemd:amd64 (245.4-4ubuntu3.5) ... Setting up libpam-systemd:amd64 (245.4-4ubuntu3.5) ... Processing triggers for libc-bin (2.31-0ubuntu9.2) ... Processing triggers for dbus (1.12.16-2ubuntu2.1) ... root@lp1902236-f:~# getent passwd | grep root root:x:0:0:root:/root:/bin/bash root@lp1902236-f:~# getent passwd | grep nobody nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1902236 Title: Duplicated root and nobody returned by getent on Focal Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [impact] getent password or getent group returns duplicate, false/synthesized, entries for root and nobody [test case] root@lp1902236-f:~# getent passwd | grep root root:x:0:0:root:/root:/bin/bash root:x:0:0:root:/root:/bin/sh root@lp1902236-f:~# getent group | grep root root:x:0: root:x:0: root@lp1902236-f:~# getent passwd | grep nobody nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin nobody:x:65534:65534:nobody:/:/usr/sbin/nologin root@lp1902236-f:~# getent group | grep nogroup nogroup:x:65534: nogroup:x:65534: [regression potential] any regression would likely result in incorrect results to calls to getent or other programs using libnss-systemd [scope] this is needed only for f this was fixed upstream by commit 9494da41c271bb9519d3484b6016526a72cc6be5 which was included first in v246, so this is fixed in g and later already. b and earlier doesn't show the duplication. [original description] * Summary systemd's NSS integration causes getent passwd/group to return duplicated entries for root/root and nobody/nogroup. The root account also gets a different shell (/bin/sh instead of /bin/bash). * Steps to reproduce: 1) create a container $ lxc launch images:ubuntu/focal test-nobody 2) check the root and nobody accounts $ lxc exec test-nobody -- getent passwd | grep -E '^(root|nobody):' 3) check the root and nogroup groups $ lxc exec test-nobody -- getent group | grep -E '^(root|nogroup):' 2 and 3 should report a single entry for each account/group but they return dups like this: root:x:0:0:root:/root:/bin/bash nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin root:x:0:0:root:/root:/bin/sh nobody:x:65534:65534:nobody:/:/usr/sbin/nologin * Description The problem seems to come from the NSS integration: $ lxc exec test-nobody -- grep -wF systemd /etc/nsswitch.conf
[Touch-packages] [Bug 1779767] Re: Default cron PATH does not include /snap/bin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cron (Ubuntu Groovy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin Status in anacron package in Ubuntu: Confirmed Status in cron package in Ubuntu: Confirmed Status in anacron source package in Bionic: Confirmed Status in cron source package in Bionic: Confirmed Status in anacron source package in Focal: Confirmed Status in cron source package in Focal: Confirmed Status in anacron source package in Groovy: Confirmed Status in cron source package in Groovy: Confirmed Status in anacron source package in Hirsute: Confirmed Status in cron source package in Hirsute: Confirmed Bug description: I recently changed from a .deb install of LXD to a snap, and was surprised that one of my crontab scripts stopped working. I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas my default shell also includes "/snap/bin". It seems to me that for the best user experience with snaps, "/snap/bin" should be part of the default $PATH in cron. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 14:30:06 2018 InstallationDate: Installed on 2017-12-20 (194 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+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 1779767] Re: Default cron PATH does not include /snap/bin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: anacron (Ubuntu Groovy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin Status in anacron package in Ubuntu: Confirmed Status in cron package in Ubuntu: Confirmed Status in anacron source package in Bionic: Confirmed Status in cron source package in Bionic: Confirmed Status in anacron source package in Focal: Confirmed Status in cron source package in Focal: Confirmed Status in anacron source package in Groovy: Confirmed Status in cron source package in Groovy: Confirmed Status in anacron source package in Hirsute: Confirmed Status in cron source package in Hirsute: Confirmed Bug description: I recently changed from a .deb install of LXD to a snap, and was surprised that one of my crontab scripts stopped working. I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas my default shell also includes "/snap/bin". It seems to me that for the best user experience with snaps, "/snap/bin" should be part of the default $PATH in cron. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 14:30:06 2018 InstallationDate: Installed on 2017-12-20 (194 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+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 1779767] Re: Default cron PATH does not include /snap/bin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cron (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin Status in anacron package in Ubuntu: Confirmed Status in cron package in Ubuntu: Confirmed Status in anacron source package in Bionic: Confirmed Status in cron source package in Bionic: Confirmed Status in anacron source package in Focal: Confirmed Status in cron source package in Focal: Confirmed Status in anacron source package in Groovy: Confirmed Status in cron source package in Groovy: Confirmed Status in anacron source package in Hirsute: Confirmed Status in cron source package in Hirsute: Confirmed Bug description: I recently changed from a .deb install of LXD to a snap, and was surprised that one of my crontab scripts stopped working. I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas my default shell also includes "/snap/bin". It seems to me that for the best user experience with snaps, "/snap/bin" should be part of the default $PATH in cron. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 14:30:06 2018 InstallationDate: Installed on 2017-12-20 (194 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+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 1779767] Re: Default cron PATH does not include /snap/bin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: anacron (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin Status in anacron package in Ubuntu: Confirmed Status in cron package in Ubuntu: Confirmed Status in anacron source package in Bionic: Confirmed Status in cron source package in Bionic: Confirmed Status in anacron source package in Focal: Confirmed Status in cron source package in Focal: Confirmed Status in anacron source package in Groovy: Confirmed Status in cron source package in Groovy: Confirmed Status in anacron source package in Hirsute: Confirmed Status in cron source package in Hirsute: Confirmed Bug description: I recently changed from a .deb install of LXD to a snap, and was surprised that one of my crontab scripts stopped working. I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas my default shell also includes "/snap/bin". It seems to me that for the best user experience with snaps, "/snap/bin" should be part of the default $PATH in cron. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 14:30:06 2018 InstallationDate: Installed on 2017-12-20 (194 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+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 1779767] Re: Default cron PATH does not include /snap/bin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cron (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin Status in anacron package in Ubuntu: Confirmed Status in cron package in Ubuntu: Confirmed Status in anacron source package in Bionic: Confirmed Status in cron source package in Bionic: Confirmed Status in anacron source package in Focal: Confirmed Status in cron source package in Focal: Confirmed Status in anacron source package in Groovy: Confirmed Status in cron source package in Groovy: Confirmed Status in anacron source package in Hirsute: Confirmed Status in cron source package in Hirsute: Confirmed Bug description: I recently changed from a .deb install of LXD to a snap, and was surprised that one of my crontab scripts stopped working. I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas my default shell also includes "/snap/bin". It seems to me that for the best user experience with snaps, "/snap/bin" should be part of the default $PATH in cron. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 14:30:06 2018 InstallationDate: Installed on 2017-12-20 (194 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+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 1779767] Re: Default cron PATH does not include /snap/bin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: anacron (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin Status in anacron package in Ubuntu: Confirmed Status in cron package in Ubuntu: Confirmed Status in anacron source package in Bionic: Confirmed Status in cron source package in Bionic: Confirmed Status in anacron source package in Focal: Confirmed Status in cron source package in Focal: Confirmed Status in anacron source package in Groovy: Confirmed Status in cron source package in Groovy: Confirmed Status in anacron source package in Hirsute: Confirmed Status in cron source package in Hirsute: Confirmed Bug description: I recently changed from a .deb install of LXD to a snap, and was surprised that one of my crontab scripts stopped working. I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas my default shell also includes "/snap/bin". It seems to me that for the best user experience with snaps, "/snap/bin" should be part of the default $PATH in cron. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 14:30:06 2018 InstallationDate: Installed on 2017-12-20 (194 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+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 1779767] Re: Default cron PATH does not include /snap/bin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: anacron (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin Status in anacron package in Ubuntu: Confirmed Status in cron package in Ubuntu: Confirmed Status in anacron source package in Bionic: Confirmed Status in cron source package in Bionic: Confirmed Status in anacron source package in Focal: Confirmed Status in cron source package in Focal: Confirmed Status in anacron source package in Groovy: Confirmed Status in cron source package in Groovy: Confirmed Status in anacron source package in Hirsute: Confirmed Status in cron source package in Hirsute: Confirmed Bug description: I recently changed from a .deb install of LXD to a snap, and was surprised that one of my crontab scripts stopped working. I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas my default shell also includes "/snap/bin". It seems to me that for the best user experience with snaps, "/snap/bin" should be part of the default $PATH in cron. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 14:30:06 2018 InstallationDate: Installed on 2017-12-20 (194 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+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 1918122] Re: Background picture not changed correctly
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1918122 Title: Background picture not changed correctly Status in xorg package in Ubuntu: New Bug description: I have changed my background picture to a external picture everything is good but when I changed my screen to the bottom one(super+pate down) my prevision background coming back ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:13:07 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1002:67ef] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1458:22de] InstallationDate: Installed on 2021-03-01 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2e09764a-1fb8-4580-868d-0660951ab9a2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2010 dmi.bios.release: 22.9 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2209 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2209:bd03/11/2010:br22.9:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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/xorg/+bug/1918122/+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 1918122] [NEW] Background picture not changed correctly
You have been subscribed to a public bug: I have changed my background picture to a external picture everything is good but when I changed my screen to the bottom one(super+pate down) my prevision background coming back ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 8 14:13:07 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1002:67ef] (rev cf) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1458:22de] InstallationDate: Installed on 2021-03-01 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2e09764a-1fb8-4580-868d-0660951ab9a2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2010 dmi.bios.release: 22.9 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2209 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2209:bd03/11/2010:br22.9:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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 -- Background picture not changed correctly https://bugs.launchpad.net/bugs/1918122 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1906331] Re: systemd-resolve crashes fairly often (and reports various assertions)
systemd-resolved still crashing more-or-less every 10 minutes. Some update arrived (I installed it 15 minutes ago) - 245.4-4ubuntu3.5~202103051349~ubuntu20.04.1 - it also crashed few mins since the installation. I tried various approaches to kernel.core_pattern, but nothing is gathered. As I understand, the way it aborts itself doesn't lead to core creation. There are few failing assertions leading to the failure (stats for the version mentioned in #12) a) Assertion 'DNS_TRANSACTION_IS_LIVE(q->state)' failed at src/resolve /resolved-dns-query.c:520, function dns_query_complete(). Aborting Most frequent one, 753 times this week b) Assertion '*_head == _item' failed at src/resolve/resolved-dns- query.c:372, function dns_query_free(). Aborting. 49 times this week c) Assertion 'p->n_ref > 0' failed at src/libsystemd/sd-event/sd- event.c:1912, function sd_event_source_unref(). Aborting. 9 times this week d) Assertion 'q->auxiliary_for->n_auxiliary_queries > 0' failed at src/resolve/resolved-dns-query.c:370, function dns_query_free(). Aborting 6 times this week e) Assertion 'p->n_ref > 0' failed at src/resolve/resolved-dns- question.c:33, function dns_question_unref(). Aborting. 2 times this week -- 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/1906331 Title: systemd-resolve crashes fairly often (and reports various assertions) Status in systemd package in Ubuntu: In Progress Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: In Progress Status in systemd source package in Hirsute: In Progress Bug description: [impact] systemd-resolved crashes [test case] see original description; I can't reproduce so I'm relying on the reporter(s) to test/verify. [regression potential] any regression would likely occur while processing sd_event objects, which are used throughout systemd code; this could result in crashes in almost any part of systemd code. However a more likely regression would be leaks of sd_event objects due to failure to release the final ref for an object. [scope] This is needed for f/g/h This might be fixed by upstream commit f814c871e65df8552a055dd887bc94b074037833; if so, that commit isn't included in any systemd release yet, and so is needed in h and earlier. [other info] I believe this is caused by a freed sd_event object that is then processed and calls the on_query_timeout callback with invalid state, leading to failed assertion, which causes resolved to crash; that's what analysis of the crash dump appears to indicate. This may be fixed by the upstream commit referenced in [scope], which takes additional refs during function calls. However I haven't reproduced this myself, so I'm only guessing as to the cause and solution at this point. I'm unsure why this would not occur in bionic, but per comment 5 it seems it doesn't happen in that release. [original description] (Tested on regularly updated Ubuntu 20.04, currently i use systemd 245.4-4ubuntu3.2) I observe fairly lot of segfaults of systemd-resolve. Frequency vary but … see below. I have no clue what is the reason. Specific feature of my machine is that apart from normal cable connection (to OpenWRT router) I use OpenVPN for business network (and this submits specific nameserver for myorg.local domain). ~ $ LC_ALL=C dmesg -T --level=info | grep systemd-resolve [Sun Nov 29 11:47:37 2020] systemd-resolve[1629307]: segfault at 190eed7bdc6 ip 7fd98f771dc9 sp 7ffc2352a100 error 4 in libsystemd-shared-245.so[7fd98f74c000+16e000] [Sun Nov 29 11:57:27 2020] systemd-resolve[1629787]: segfault at 1f ip 55ab7b0cb686 sp 7fff78ce4bd0 error 4 in systemd-resolved[55ab7b0a4000+3e000] [Sun Nov 29 12:07:37 2020] systemd-resolve[1630481]: segfault at 191 ip 55ca69fed91c sp 7ffc4d757dc0 error 6 in systemd-resolved[55ca69fc2000+3e000] [Sun Nov 29 13:12:26 2020] systemd-resolve[1638829]: segfault at 19224162371 ip 7fc1bc9b9dc9 sp 7ffc21378170 error 4 in libsystemd-shared-245.so[7fc1bc994000+16e000] [Sun Nov 29 13:32:57 2020] systemd-resolve[1639886]: segfault at 1926d8126d3 ip 7f7ed17e9dc9 sp 7ffda2cea0b0 error 4 in libsystemd-shared-245.so[7f7ed17c4000+16e000] [Sun Nov 29 13:42:37 2020] systemd-resolve[1640246]: segfault at 61 ip 558d992e2686 sp 7fff08906af0 error 4 in systemd-resolved[558d992bb000+3e000] [Sun Nov 29 15:42:26 2020] systemd-resolve[1645397]: segfault at 1943c92afc7 ip 7fd4c1721dc9 sp 7fff25259ce0 error 4 in libsystemd-shared-245.so[7fd4c16fc000+16e000] [Sun Nov 29 16:02:36 2020] systemd-resolve[1646052]: segfault at 1947ecb3726 ip 7f1008549dc9 sp 7fff44a6db70 error 4 in libsystemd-shared-245.so[7f1008524000+16e000] [Sun Nov 29 17:42:35 2020] s
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: New Status in docker.io source package in Xenial: New Status in glibc source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in docker.io source package in Bionic: New Status in glibc source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: New Status in docker.io source package in Focal: New Status in glibc source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: New Status in docker.io source package in Groovy: New Status in glibc source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: New Status in docker.io source package in Hirsute: New Status in glibc source package in Hirsute: Opinion Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: New Bug description: glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The simple Dockerfile to reproduce the error - "docker build -t foo ." FROM amd64/ubuntu:hirsute MAINTAINER Florian Lohoff USER root RUN apt-get update \ && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \ && curl https://syncthing.net/release-key.txt | apt-key add - Breaking it down it this seems to be an issue that there is new functionality in apt/apt-key e.g. security hardening that docker prohibits in its containers. Running this manually works only in an --privileged container. So adding keys in unpriviledged container or possibly kubernetes will not work anymore. Flo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+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 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
Forwarded to upstream open-vm-tools as https://github.com/vmware/open-vm-tools/issues/500 Uploaded a fix for Ubuntu in https://launchpad.net/ubuntu/+source/open-vm-tools/2:11.2.5-2ubuntu1 ** Bug watch added: github.com/vmware/open-vm-tools/issues #500 https://github.com/vmware/open-vm-tools/issues/500 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916705 Title: glib2.0 >=2.67.3 breaks include from an extern C context Status in glib2.0 package in Ubuntu: Fix Released Status in open-vm-tools package in Ubuntu: New Status in qemu package in Ubuntu: Fix Released Status in ukui-control-center package in Ubuntu: Triaged Bug description: qemu now breaks in Hirsute (it didn't 23h ago) Broken: https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz Good before: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages Error: ../../disas/arm-a64.cc In file included from /usr/include/glib-2.0/glib/gmacros.h:241, from /usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9, from /usr/include/glib-2.0/glib/gtypes.h:32, from /usr/include/glib-2.0/glib/galloca.h:32, from /usr/include/glib-2.0/glib.h:30, from /<>/qemu-5.2+dfsg/include/glib-compat.h:32, from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126, from ../../disas/arm-a64.cc:21: /usr/include/c++/10/type_traits:56:3: error: template with C linkage 56 | template | ^~~~ ../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here 20 | extern "C" { | ^~ Also in disas/nanomips.cpp, ... And indeed disas/arm-a64.cc has: 20 extern "C" { 21 #include "qemu/osdep.h" 22 #include "disas/dis-asm.h" 23 } Through the chain of headers as reported above this gets to the templates in /usr/include/c++/10/type_traits which fails due to that. So C++ constructs within a C scope which is this bug. Upstream qemu has not recently changed yet for this. The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc: Include osdep.h first" by Peter Maydell. But what was different before to break it now? To find that I was comparing Hirsute vs Hirsute-proposed ... It is indeed failing in -proposed but working in hirsute-release. 10.2.1-20ubuntu1 : bad repro in broken build: $ cd /root/qemu-5.2+dfsg/b/qemu $ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 -I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr -I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall -Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef -Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 -ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem /root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote /root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote /root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote /root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d -o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp With that I have a test env... Doko asked me to test https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1 It must be something else. The difference were ~340 packages I was upgrading them to spot what broke it. I eventually found glib 2.66 -> 2.67 to break it. libglib2.0-0/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1] libglib2.0-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1] libglib2.0-data/hirsute-proposed 2.67.4-1 all [upgradable from: 2.66.4-1] libglib2.0-dev-bin/hirsute-proposed 2.67.4-1 amd64 [up
[Touch-packages] [Bug 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers
LGTM! -- 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/1883447 Title: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [impact] nspawn fails on armhf [test case] setup a bionic armhf system, and get a focal img/filesystem to use with systemd-nspawn, e.g. $ wget https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-armhf-root.tar.xz $ mkdir f $ cd f $ tar xvf ../focal-server-cloudimg-armhf-root.tar.xz install systemd-container, and start nspawn; then test anything that uses the time, e.g. just run python: $ systemd-nspawn Spawning container f on /root/f. Press ^] three times within 1s to kill container. root@f:~# python3 Fatal Python error: pyinit_main: can't initialize time Python runtime state: core initialized PermissionError: [Errno 1] Operation not permitted Current thread 0xf7bbd310 (most recent call first): [regression potential] any regression would likely break nspawn creation or operation of containers, particularly on armhf, but possibly on other archs [scope] this is needed only in bionic. this is fixed upstream by commit 6ca677106992321326427c89a40e1c9673a499b2 which was included first in v244, so this is fixed already in focal and later. [original description] Recent Linux kernels introduced a number of new syscalls ending in _time64 to fix Y2038 problem; it appears recent glibc, including the version in focal, test for the existence of these. systemd-nspawn in bionic (237-3ubuntu10.38) doesn't know about these so blocks them by default. It seems however glibc isn't expecting an EPERM, causing numerous programs to fail. In particular, running do-release-upgrade to focal in an nspawn container hosted on bionic will break as soon as the new libc has been unpacked. Solution (tested here) is to cherrypick upstream commit https://github.com/systemd/systemd/commit/6ca677106992321326427c89a40e1c9673a499b2 A newer libseccomp is also needed but this is already being worked on, see bug #1876055. It's a pretty trivial fix one the new libseccomp lands, and there is precedent for SRU-ing for a similar issue in bug #1840640. https://patchwork.kernel.org/patch/10756415/ is apparently the upstream kernel patch, which should give a clearer idea of which architectures are likely to be affected - I noticed it on armhf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1883447/+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 1918112] Re: Deal with rred shortcomings around empty patch files
We're actually not backporting this to stable releases just future stable one :) ** Changed in: apt (Ubuntu Groovy) Status: New => Won't Fix ** Changed in: apt (Ubuntu Focal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1918112 Title: Deal with rred shortcomings around empty patch files Status in apt package in Ubuntu: New Status in apt source package in Focal: Won't Fix Status in apt source package in Groovy: Won't Fix Status in apt source package in Hirsute: New Bug description: [Impact] Merge request https://salsa.debian.org/apt-team/apt/-/merge_requests/159 has a bunch of fixes for empty pdiff files, cleaning up pdiff files, as well as correcting some bugs with index files in the mirror method. While we don't use pdiffs ourselves, third party repositories might, and people might want to use rred on Ubuntu to create merged pdiff files, and hence benefit from those patches, so we want to backport it to 2.0, such that it is not more buggy than Debian's 1.8 and forces you to run Debian if you want to do those things. [Test plan] Each commit comes with a change to the test suite that tests it, and the test suite is fairly exhaustive too. [Where problems could occur] Changes are limited to adding headers to Index file downloads (so that mirror works correctly), and pdiff-specific code, so problems could occur with mirror method or pdiff. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918112/+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 1918112] [NEW] Deal with rred shortcomings around empty patch files
Public bug reported: [Impact] Merge request https://salsa.debian.org/apt-team/apt/-/merge_requests/159 has a bunch of fixes for empty pdiff files, cleaning up pdiff files, as well as correcting some bugs with index files in the mirror method. While we don't use pdiffs ourselves, third party repositories might, and people might want to use rred on Ubuntu to create merged pdiff files, and hence benefit from those patches, so we want to backport it to 2.0, such that it is not more buggy than Debian's 1.8 and forces you to run Debian if you want to do those things. [Test plan] Each commit comes with a change to the test suite that tests it, and the test suite is fairly exhaustive too. [Where problems could occur] Changes are limited to adding headers to Index file downloads (so that mirror works correctly), and pdiff-specific code, so problems could occur with mirror method or pdiff. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Affects: apt (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: apt (Ubuntu Groovy) Importance: Undecided Status: Won't Fix ** Affects: apt (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1918112 Title: Deal with rred shortcomings around empty patch files Status in apt package in Ubuntu: New Status in apt source package in Focal: Won't Fix Status in apt source package in Groovy: Won't Fix Status in apt source package in Hirsute: New Bug description: [Impact] Merge request https://salsa.debian.org/apt-team/apt/-/merge_requests/159 has a bunch of fixes for empty pdiff files, cleaning up pdiff files, as well as correcting some bugs with index files in the mirror method. While we don't use pdiffs ourselves, third party repositories might, and people might want to use rred on Ubuntu to create merged pdiff files, and hence benefit from those patches, so we want to backport it to 2.0, such that it is not more buggy than Debian's 1.8 and forces you to run Debian if you want to do those things. [Test plan] Each commit comes with a change to the test suite that tests it, and the test suite is fairly exhaustive too. [Where problems could occur] Changes are limited to adding headers to Index file downloads (so that mirror works correctly), and pdiff-specific code, so problems could occur with mirror method or pdiff. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1918112/+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 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"
Indeed, I'm running the daily build and toggling the percentage setting on and off has the expected result. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1766108 Title: Battery indicator crashes when unchecking "Show Percentage in Menu Bar" Status in Ubuntu MATE: New Status in ayatana-indicator-power package in Ubuntu: Confirmed Status in indicator-power package in Ubuntu: Confirmed Status in mate-indicator-applet package in Ubuntu: Confirmed Status in mate-panel package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Click on the battery indicator. 2. Click "Show Percentage on Menu Bar" to enable it. 3. Do it again to disable it. 4. Battery indicator disappears Output from dmesg: [ 613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000] [ 749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000] [ 775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000] [ 816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000] [ 841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+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 1685754] Re: 'systemd --user' unduly forces umask=0022
Hello Etienne, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 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: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: 'systemd --user' unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: Invalid Status in GNOME Terminal: Confirmed Status in Nautilus: Invalid Status in systemd: Unknown Status in dbus package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Bionic: Invalid Status in gnome-terminal source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Bug description: [impact] pam_umask, from /etc/passwd, is not honored in systemd --user instances [test case] on a desktop system, edit /etc/passwd to change the test user entry (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th field). For example change: ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash to: ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash You may need to reboot for your X session to pick up the change. Then, from the graphical desktop, open a terminal and run: $ gnome-terminal -e sh in the opened terminal, run: $ umask the number shown should be 0007, as set in the passwd file [regression potential] any regression would likely result in an incorrect umask for the user whose passwd entry is modified. [scope] this is needed only for b this is fixed in systemd upstream by commit 5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in v246, so this is fixed in g and later. This commit was also picked up by Debian and included in the v245 release for focal, so this is fixed in focal already. [original description] In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : ht
[Touch-packages] [Bug 1878969] Re: time-epoch never changes in SRUs
Hello Dimitri, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 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: systemd (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-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/1878969 Title: time-epoch never changes in SRUs Status in ubuntu-core-initramfs: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Bug description: [Impact] * Systems without hwclock come up with a fixed time epoch which is not updated in SRUs * Ideally booting with a newer built of systemd should move time epoch to be at least when systemd was last built. For example to the value of SOURCE_DATE_EPOCH. [Test Case] * Boot without network NTP or hwclock * Observe that the epoch is the same as the time when NEWS entry in the systemd source code was last touched. * Boot newer update of systemd, observe that the time epoch is at least 2020 [Regression Potential] * Bad epoch, may result in unable to perform TLS connections, validated GPG signatures, and snapd assertions. Changing epoch to be more recent is desired. Some machines may rely on the fact that "bionic" without hwclock always comes up in year 2018. But in practice that is incorrect thing to do. [Other Info] * By default option('time-epoch', type : 'integer', value : '-1', description : 'time epoch for time clients') in systemd is set to the modification time of the NEW entry time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int() If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value to be compliant with the https://reproducible- builds.org/docs/timestamps/ specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+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 1890448] Re: hwdb: Add EliteBook to use micmute hotkey
Hello Kai-Heng, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1890448 Title: hwdb: Add EliteBook to use micmute hotkey Status in HWE Next: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [Impact] Micmute hotkey on many HP EliteBooks don't work. [Fix] Commit b6eb208b29ae ("hwdb: Add EliteBook to use micmute hotkey"), to map AT keyboard's scancode to micmute hotkey. [Test] With the one-liner fix, micmute hotkey works on all the EliteBooks I tested. [Regression Potential] The hwdb originally only matches a few EliteBook, and fix changes that to match all EliteBook models. So if there's an EliteBook that uses the scancode for other purpose, there will be a regression. However, the risk is rather slim because HP is confident that all EliteBooks use the same scancode for mic mute hotkey. [scope] this is needed for f and earlier. this is fixed upstream by commit b6eb208b29ae which is included starting in v246, so g and later are already fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1890448/+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 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
Hello MarcH, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-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/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in network-manager source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in network-manager source package in Focal: Confirmed Status in systemd source package in Focal: Fix Committed Status in network-manager source package in Groovy: New Status in systemd source package in Groovy: Fix Committed Status in network-manager source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Committed Bug description: [impact] systemd-resolved emits a disturbingly large amount of NXDOMAIN log messages that do not actually indicate any real problem [test case] see original description, or look at any log from any recent Ubuntu system, or search google for endless complaints about NXDOMAIN messages logged by Ubuntu [regression potential] any regression would likely be isolated to systemd-resolved handling of a NXDOMAIN response from its upstream nameserver, including possibly failing to resolve a hostname or delays in resolving hostnames [scope] this is needed for all releases; the patch is not upstream, but carried by Ubuntu [original description] I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+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 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers
Hello Steve, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 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: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1883447 Title: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [impact] nspawn fails on armhf [test case] setup a bionic armhf system, and get a focal img/filesystem to use with systemd-nspawn, e.g. $ wget https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-armhf-root.tar.xz $ mkdir f $ cd f $ tar xvf ../focal-server-cloudimg-armhf-root.tar.xz install systemd-container, and start nspawn; then test anything that uses the time, e.g. just run python: $ systemd-nspawn Spawning container f on /root/f. Press ^] three times within 1s to kill container. root@f:~# python3 Fatal Python error: pyinit_main: can't initialize time Python runtime state: core initialized PermissionError: [Errno 1] Operation not permitted Current thread 0xf7bbd310 (most recent call first): [regression potential] any regression would likely break nspawn creation or operation of containers, particularly on armhf, but possibly on other archs [scope] this is needed only in bionic. this is fixed upstream by commit 6ca677106992321326427c89a40e1c9673a499b2 which was included first in v244, so this is fixed already in focal and later. [original description] Recent Linux kernels introduced a number of new syscalls ending in _time64 to fix Y2038 problem; it appears recent glibc, including the version in focal, test for the existence of these. systemd-nspawn in bionic (237-3ubuntu10.38) doesn't know about these so blocks them by default. It seems however glibc isn't expecting an EPERM, causing numerous programs to fail. In particular, running do-release-upgrade to focal in an nspawn container hosted on bionic will break as soon as the new libc has been unpacked. Solution (tested here) is to cherrypick upstream commit https://github.com/systemd/systemd/commit/6ca677106992321326427c89a40e1c9673a499b2 A newer libseccomp is also needed but this is already being worked on, see bug #1876055. It's a pretty trivial fix one the new libseccomp lands, and there is precedent for SRU-ing for a similar issue in bug #1840640. https://patchwork.kernel.org/patch/10756415/ is apparently the upstream kernel patch, which should give a clearer idea of which architectures are likely to be affected - I noticed it on armhf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1883447/+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 1902553] Re: TEST-03 sometimes fails during autopkgtests
Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 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: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1902553 Title: TEST-03 sometimes fails during autopkgtests Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Won't Fix Status in systemd source package in Bionic: Fix Committed Bug description: [impact] during autopkgtest runs, sometimes TEST-03 fails when running under qemu. [test case] check autopkgtest results, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/s/systemd/20201009_025713_c1956@/log.gz [regression potential] any regression would likely result in a failure to detect some other regression that is otherwise tested by this test case. [scope] this is needed only for bionic. upstream, this is fixed by disabling TEST-03 (and TEST-16) running under qemu, as their timing is very tight, in commit 3edc0c590d3a9212267d0a7cf56e95efa7f61039, which is included first in v239, so this is fixed already in focal and later. technically, this also is needed for xenial, however since that release is reaching ESM status early next year, and this is only an autopkgtest fix, i have no plans to update xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902553/+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 1911187] Re: scheduled reboot reboots immediately if dbus or logind is not available
Hello Ioanna, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-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/1911187 Title: scheduled reboot reboots immediately if dbus or logind is not available Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Bug description: [IMPACT] When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately. From the sources it seems that this is intended : https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318 However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately. There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and a PR ( https://github.com/systemd/systemd/pull/18010 ). Upstream community is not willing to accept the patch but debian is. I open this bug to to pull the patch into Ubuntu once it lands in debian. [TEST PLAN] The simpler reproducer is to disable dbus to imitate the real world case. # systemctl stop dbus.service # systemctl stop dbus.socket # shutdown +1140 -r "REBOOT!" Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms) Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out Connection to groovy closed by remote host. Connection to groovy closed. [WHERE PROBLEM COULD OCCUR] This patch changes the behaviour of scheduled reboot in case logind or dbus has failed. Originally, if logind is not available (call to logind bus fails https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319) it proceeds with immediate shutdown. This patch changes this behaviour and instead of shutting down it does nothing. The actual regression potential is a user asking for a reboot and not getting it, so the largest regression potential is any existing users (human or programmatic) that are requesting a scheduled shutdown but not checking the return value for error. Any other regression would likely result in the system incorrectly not rebooted, or incorrectly scheduled for reboot. [OTHER] This is now fixed in H, currently affects B,G,F. Debian bug reports : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042 Upstream issue : https://github.com/systemd/systemd/issues/17575 PR : https://github.com/systemd/systemd/pull/18010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+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 1913763] Re: hyperv: unable to distinguish PTP devices
Hello Gauthier, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 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: systemd (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-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/1913763 Title: hyperv: unable to distinguish PTP devices Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Bug description: [impact] the /dev/ptp0 device for a hyperv instance may not be the correct, hyperv-provided, ptp device. [test case] on some hyperv instance types, particularly those that might contain passthrough network card(s) that also provide ptp, the first ptp device may not be the correct one to use for ptp, e.g. there may be multiple ones: $ ls /dev/ptp* /dev/ptp0 /dev/ptp1 $ cat /sys/class/ptp/ptp0/clock_name hyperv $ cat /sys/class/ptp/ptp1/clock_name mlx5_p2p the order can change across boots, so a consistent way of addressing the hyperv-provided one is needed [regression potential] any regression would involve failure to properly create the ptp symlink, or other failure while udev is processing newly detected ptp device(s) [scope] this is needed in all releases this was fixed upstream with the commit 32e868f058da8b90add00b2958c516241c532b70 which is not yet included in any release [original description] Hyperv provides a PTP device. On system with multiple PTP devices, services like Chrony don't have a way to know which one is which. We would like to have a udev rule to create a symlink to the hyperv clock. This way, services could be configured to always use this clock no matter if it is ptp0, ptp1, etc.. For example: ``` SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv" ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1913423] Re: getgrouplist is not thread safe with libnss_systemd
Hello Daniel, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-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/1913423 Title: getgrouplist is not thread safe with libnss_systemd Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Bug description: [impact] programs calling getgrouplist() may crash as it is not thread-safe [test case] see upstream bug description for sample c program to reproduce: https://github.com/systemd/systemd/issues/17007#issue-698123284 [regression potential] any regression would likely occur when creating a hashmap in systemd, or when any multi-threaded programs concurrently create (and use) the hashmap [scope] this is needed for f and b this is fixed upstream by commit ae0b700a856c0ae460d271bb50dccfaae84dbcab, already included in g/h (per comment 1). [original description] This upstream issue (https://github.com/systemd/systemd/issues/17007) is affecting the latest version of systemd in Ubuntu Focal. It has been fixed upstream with https://github.com/systemd/systemd/pull/17033. Can we have this patched for Focal please as it causes Mesos to randomly segfault on start. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913423/+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 1913189] Re: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1
Hello Kleber, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 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: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-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/1913189 Title: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1 Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Bug description: [impact] test-fs-util fails when running under 5.8 kernel [test case] see autopkgtest runs, e.g. amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz [regression potential] any regression would likely result in incorrectly passed or failed build-time or autopkgtest-time test run [scope] this is needed in f and b this was fixed upstream with commit 5b5ce6298e which was first included in v247, and has already been backported to g in bug 1891527. while it's unlikely that the 5.8 kernel will ever officially be available directly in b, this test case is also run at build time, so if the lp build farm is ever updated to the 5.8 kernel this test case would begin failing during build, so the patch should be backported there as well. this isn't needed in x as the test-fs-util test isn't present there. [original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20210121_021134_f3c65@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20210121_090718_fa164@/log.gz The failing test case is: TEST-24-UNIT-TESTS: === Failed test log === --- test-fs-util begin --- /* test_chase_symlinks */ /* test_unlink_noerrno */ /* test_readlink_and_make_absolute */ /* test_var_tmp */ /* test_dot_or_dot_dot */ /* test_access_fd */ /* test_touch_file */ Assertion 'mknod(a, 0775 | S_IFBLK, makedev(0, 0)) >= 0' failed at src/test/test-fs-util.c:637, funct ion test_touch_file(). Aborting. --- test-fs-util end --- make: Leaving directory '/tmp/autopkgtest.KFUfZH/build.scn/src/test/TEST-24-UNIT-TESTS' make: *** [Makefile:4: run] Error 1 This issue has been solved in Groovy on bug 1891527, likely the fix needs to be backported to systemd in Focal for the testcase to pass with the 5.8 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1913189/+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 1916229] Re: udev reports error due to NIS usage
@ddstreet Well, after thinking about it, I'm actually not sure if this is an issue after all. Or if this should/must be handled by the system administrator itself, when using NIS. -- 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/1916229 Title: udev reports error due to NIS usage Status in systemd: Fix Released Status in systemd package in Ubuntu: Incomplete Bug description: I see the following error message when trying to updating udev to 245.4-4ubuntu3.4. > systemd-udevd[25721]: do_ypcall: clnt_call: RPC: Unable to send; errno = Operation not permitted As it turns out we trigger a security feature of systemd, which appears because we use NIS: https://github.com/systemd/systemd/commit/695fe4078f0df6564a1be1c4a6a9e8a640d23b67 The solution is fairly simple: $ sudo mkdir /etc/systemd/system/systemd-udevd.service.d/ $ printf "[Service]\nIPAddressDeny=\n" | sudo tee /etc/systemd/system/systemd-udevd.service.d/override.conf And here the full error message occurring during the update: Setting up udev (245.4-4ubuntu3.4) ... Job for systemd-udevd.service failed because a timeout was exceeded. See "systemctl status systemd-udevd.service" and "journalctl -xe" for details. invoke-rc.d: initscript udev, action "restart" failed. ● systemd-udevd.service - udev Kernel Device Manager Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; vendor preset: enabled) Active: activating (start) since Fri 2021-02-19 10:44:33 CET; 7ms ago TriggeredBy: ● systemd-udevd-control.socket ● systemd-udevd-kernel.socket Docs: man:systemd-udevd.service(8) man:udev(7) Main PID: 2196 ((md-udevd)) Tasks: 1 Memory: 640.0K CGroup: /system.slice/systemd-udevd.service └─2196 (md-udevd) Feb 19 10:44:33 hasfpnccd systemd[1]: Starting udev Kernel Device Manager... dpkg: error processing package udev (--configure): installed udev package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of snapd: snapd depends on udev; however: Package udev is not configured yet. dpkg: error processing package snapd (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of ubuntu-drivers-common: ubuntu-drivers-common depends on udev (>= 204-0ubuntu4~); however: Package udev is not configured yet. dpkg: error processing package ubuntu-drivers-common (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of xserver-xorg-core: xserver-xorg-core depends on udev (>= 149); however: Package udev is not configured yet. dpkg: error processing package xserver-xorg-core (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. N o apport report written because MaxReports is reached already Errors were encountered while processing: udev snapd ubuntu-drivers-common xserver-xorg-core E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1916229/+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 1878969] Re: time-epoch never changes in SRUs
Hello Dimitri, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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: systemd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1878969 Title: time-epoch never changes in SRUs Status in ubuntu-core-initramfs: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Bug description: [Impact] * Systems without hwclock come up with a fixed time epoch which is not updated in SRUs * Ideally booting with a newer built of systemd should move time epoch to be at least when systemd was last built. For example to the value of SOURCE_DATE_EPOCH. [Test Case] * Boot without network NTP or hwclock * Observe that the epoch is the same as the time when NEWS entry in the systemd source code was last touched. * Boot newer update of systemd, observe that the time epoch is at least 2020 [Regression Potential] * Bad epoch, may result in unable to perform TLS connections, validated GPG signatures, and snapd assertions. Changing epoch to be more recent is desired. Some machines may rely on the fact that "bionic" without hwclock always comes up in year 2018. But in practice that is incorrect thing to do. [Other Info] * By default option('time-epoch', type : 'integer', value : '-1', description : 'time epoch for time clients') in systemd is set to the modification time of the NEW entry time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int() If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value to be compliant with the https://reproducible- builds.org/docs/timestamps/ specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+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 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
Hello MarcH, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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: systemd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- 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/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in network-manager source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in network-manager source package in Focal: Confirmed Status in systemd source package in Focal: Fix Committed Status in network-manager source package in Groovy: New Status in systemd source package in Groovy: Fix Committed Status in network-manager source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Committed Bug description: [impact] systemd-resolved emits a disturbingly large amount of NXDOMAIN log messages that do not actually indicate any real problem [test case] see original description, or look at any log from any recent Ubuntu system, or search google for endless complaints about NXDOMAIN messages logged by Ubuntu [regression potential] any regression would likely be isolated to systemd-resolved handling of a NXDOMAIN response from its upstream nameserver, including possibly failing to resolve a hostname or delays in resolving hostnames [scope] this is needed for all releases; the patch is not upstream, but carried by Ubuntu [original description] I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+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 1902236] Re: Duplicated root and nobody returned by getent on Focal
Hello Simon, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1902236 Title: Duplicated root and nobody returned by getent on Focal Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [impact] getent password or getent group returns duplicate, false/synthesized, entries for root and nobody [test case] root@lp1902236-f:~# getent passwd | grep root root:x:0:0:root:/root:/bin/bash root:x:0:0:root:/root:/bin/sh root@lp1902236-f:~# getent group | grep root root:x:0: root:x:0: root@lp1902236-f:~# getent passwd | grep nobody nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin nobody:x:65534:65534:nobody:/:/usr/sbin/nologin root@lp1902236-f:~# getent group | grep nogroup nogroup:x:65534: nogroup:x:65534: [regression potential] any regression would likely result in incorrect results to calls to getent or other programs using libnss-systemd [scope] this is needed only for f this was fixed upstream by commit 9494da41c271bb9519d3484b6016526a72cc6be5 which was included first in v246, so this is fixed in g and later already. b and earlier doesn't show the duplication. [original description] * Summary systemd's NSS integration causes getent passwd/group to return duplicated entries for root/root and nobody/nogroup. The root account also gets a different shell (/bin/sh instead of /bin/bash). * Steps to reproduce: 1) create a container $ lxc launch images:ubuntu/focal test-nobody 2) check the root and nobody accounts $ lxc exec test-nobody -- getent passwd | grep -E '^(root|nobody):' 3) check the root and nogroup groups $ lxc exec test-nobody -- getent group | grep -E '^(root|nogroup):' 2 and 3 should report a single entry for each account/group but they return dups like this: root:x:0:0:root:/root:/bin/bash nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin root:x:0:0:root:/root:/bin/sh nobody:x:65534:65534:nobody:/:/usr/sbin/nologin * Description The problem seems to come from the NSS integration: $ lxc exec test-nobody -- grep -wF systemd /etc/nsswitch.conf passwd: files systemd group: files systemd as the /etc/passwd and /etc/group file contain no dups: $ lxc exec test-nobody -- grep ^nobody: /etc/passwd nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin $ lxc exec test-nobody -- grep ^nogroup: /etc/group nogroup:x:65534: Removing systemd from /etc/nsswitch.conf indeed removes the dup. An alternative way of seeing what systemd adds on top of the flat files: $ lxc exec test-nobody -- bash -c 'diff -u /etc/passwd <(getent passwd)' --- /etc/passwd 2020-10-30 13:07:52.219261001 + +++ /dev/fd/632020-10-30 13:29:38.396928732 + @@ -24,3 +24,5 @@ _apt:x:105:65534::/nonexistent:/usr/sbin/nologin ubuntu:x:1000:1000::/home/ubuntu:/bin/bash systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin +root:x:0:0:root:/root:/bin/sh +nobody:x:65534:65534:nobody:/:/usr/sbin/nologin $ lxc exec test-nobody -- bash -c 'diff -u /etc/group <(getent group)' --- /etc/group2020-10-30 13:07:52.211261089 + +++ /dev/fd/632020-10-30 13:29:45.892846747 + @@ -50,3 +50,5 @@ ubuntu:x:1000: ssh:x:111: systemd-coredump:x:999: +root:x:0: +nogroup:x:65534: * Additional information Thi
[Touch-packages] [Bug 1911187] Re: scheduled reboot reboots immediately if dbus or logind is not available
Hello Ioanna, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- 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/1911187 Title: scheduled reboot reboots immediately if dbus or logind is not available Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Bug description: [IMPACT] When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately. From the sources it seems that this is intended : https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318 However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately. There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and a PR ( https://github.com/systemd/systemd/pull/18010 ). Upstream community is not willing to accept the patch but debian is. I open this bug to to pull the patch into Ubuntu once it lands in debian. [TEST PLAN] The simpler reproducer is to disable dbus to imitate the real world case. # systemctl stop dbus.service # systemctl stop dbus.socket # shutdown +1140 -r "REBOOT!" Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms) Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out Connection to groovy closed by remote host. Connection to groovy closed. [WHERE PROBLEM COULD OCCUR] This patch changes the behaviour of scheduled reboot in case logind or dbus has failed. Originally, if logind is not available (call to logind bus fails https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319) it proceeds with immediate shutdown. This patch changes this behaviour and instead of shutting down it does nothing. The actual regression potential is a user asking for a reboot and not getting it, so the largest regression potential is any existing users (human or programmatic) that are requesting a scheduled shutdown but not checking the return value for error. Any other regression would likely result in the system incorrectly not rebooted, or incorrectly scheduled for reboot. [OTHER] This is now fixed in H, currently affects B,G,F. Debian bug reports : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042 Upstream issue : https://github.com/systemd/systemd/issues/17575 PR : https://github.com/systemd/systemd/pull/18010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+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 1913189] Re: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1
Hello Kleber, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1913189 Title: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1 Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Bug description: [impact] test-fs-util fails when running under 5.8 kernel [test case] see autopkgtest runs, e.g. amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz [regression potential] any regression would likely result in incorrectly passed or failed build-time or autopkgtest-time test run [scope] this is needed in f and b this was fixed upstream with commit 5b5ce6298e which was first included in v247, and has already been backported to g in bug 1891527. while it's unlikely that the 5.8 kernel will ever officially be available directly in b, this test case is also run at build time, so if the lp build farm is ever updated to the 5.8 kernel this test case would begin failing during build, so the patch should be backported there as well. this isn't needed in x as the test-fs-util test isn't present there. [original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20210121_021134_f3c65@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20210121_090718_fa164@/log.gz The failing test case is: TEST-24-UNIT-TESTS: === Failed test log === --- test-fs-util begin --- /* test_chase_symlinks */ /* test_unlink_noerrno */ /* test_readlink_and_make_absolute */ /* test_var_tmp */ /* test_dot_or_dot_dot */ /* test_access_fd */ /* test_touch_file */ Assertion 'mknod(a, 0775 | S_IFBLK, makedev(0, 0)) >= 0' failed at src/test/test-fs-util.c:637, funct ion test_touch_file(). Aborting. --- test-fs-util end --- make: Leaving directory '/tmp/autopkgtest.KFUfZH/build.scn/src/test/TEST-24-UNIT-TESTS' make: *** [Makefile:4: run] Error 1 This issue has been solved in Groovy on bug 1891527, likely the fix needs to be backported to systemd in Focal for the testcase to pass with the 5.8 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1913189/+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 1913423] Re: getgrouplist is not thread safe with libnss_systemd
Hello Daniel, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1913423 Title: getgrouplist is not thread safe with libnss_systemd Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Bug description: [impact] programs calling getgrouplist() may crash as it is not thread-safe [test case] see upstream bug description for sample c program to reproduce: https://github.com/systemd/systemd/issues/17007#issue-698123284 [regression potential] any regression would likely occur when creating a hashmap in systemd, or when any multi-threaded programs concurrently create (and use) the hashmap [scope] this is needed for f and b this is fixed upstream by commit ae0b700a856c0ae460d271bb50dccfaae84dbcab, already included in g/h (per comment 1). [original description] This upstream issue (https://github.com/systemd/systemd/issues/17007) is affecting the latest version of systemd in Ubuntu Focal. It has been fixed upstream with https://github.com/systemd/systemd/pull/17033. Can we have this patched for Focal please as it causes Mesos to randomly segfault on start. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913423/+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 1913763] Re: hyperv: unable to distinguish PTP devices
Hello Gauthier, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.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- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. 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: systemd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- 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/1913763 Title: hyperv: unable to distinguish PTP devices Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Bug description: [impact] the /dev/ptp0 device for a hyperv instance may not be the correct, hyperv-provided, ptp device. [test case] on some hyperv instance types, particularly those that might contain passthrough network card(s) that also provide ptp, the first ptp device may not be the correct one to use for ptp, e.g. there may be multiple ones: $ ls /dev/ptp* /dev/ptp0 /dev/ptp1 $ cat /sys/class/ptp/ptp0/clock_name hyperv $ cat /sys/class/ptp/ptp1/clock_name mlx5_p2p the order can change across boots, so a consistent way of addressing the hyperv-provided one is needed [regression potential] any regression would involve failure to properly create the ptp symlink, or other failure while udev is processing newly detected ptp device(s) [scope] this is needed in all releases this was fixed upstream with the commit 32e868f058da8b90add00b2958c516241c532b70 which is not yet included in any release [original description] Hyperv provides a PTP device. On system with multiple PTP devices, services like Chrony don't have a way to know which one is which. We would like to have a udev rule to create a symlink to the hyperv clock. This way, services could be configured to always use this clock no matter if it is ptp0, ptp1, etc.. For example: ``` SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv" ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+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 1911187] Re: scheduled reboot reboots immediately if dbus or logind is not available
Hello Ioanna, or anyone else affected, Accepted systemd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.2 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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: systemd (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- 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/1911187 Title: scheduled reboot reboots immediately if dbus or logind is not available Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Bug description: [IMPACT] When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately. From the sources it seems that this is intended : https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318 However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately. There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and a PR ( https://github.com/systemd/systemd/pull/18010 ). Upstream community is not willing to accept the patch but debian is. I open this bug to to pull the patch into Ubuntu once it lands in debian. [TEST PLAN] The simpler reproducer is to disable dbus to imitate the real world case. # systemctl stop dbus.service # systemctl stop dbus.socket # shutdown +1140 -r "REBOOT!" Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms) Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out Connection to groovy closed by remote host. Connection to groovy closed. [WHERE PROBLEM COULD OCCUR] This patch changes the behaviour of scheduled reboot in case logind or dbus has failed. Originally, if logind is not available (call to logind bus fails https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319) it proceeds with immediate shutdown. This patch changes this behaviour and instead of shutting down it does nothing. The actual regression potential is a user asking for a reboot and not getting it, so the largest regression potential is any existing users (human or programmatic) that are requesting a scheduled shutdown but not checking the return value for error. Any other regression would likely result in the system incorrectly not rebooted, or incorrectly scheduled for reboot. [OTHER] This is now fixed in H, currently affects B,G,F. Debian bug reports : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042 Upstream issue : https://github.com/systemd/systemd/issues/17575 PR : https://github.com/systemd/systemd/pull/18010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+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 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
Hello MarcH, or anyone else affected, Accepted systemd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.2 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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: systemd (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- 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/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in network-manager source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in network-manager source package in Focal: Confirmed Status in systemd source package in Focal: Fix Committed Status in network-manager source package in Groovy: New Status in systemd source package in Groovy: Fix Committed Status in network-manager source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Committed Bug description: [impact] systemd-resolved emits a disturbingly large amount of NXDOMAIN log messages that do not actually indicate any real problem [test case] see original description, or look at any log from any recent Ubuntu system, or search google for endless complaints about NXDOMAIN messages logged by Ubuntu [regression potential] any regression would likely be isolated to systemd-resolved handling of a NXDOMAIN response from its upstream nameserver, including possibly failing to resolve a hostname or delays in resolving hostnames [scope] this is needed for all releases; the patch is not upstream, but carried by Ubuntu [original description] I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+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 1913763] Re: hyperv: unable to distinguish PTP devices
Hello Gauthier, or anyone else affected, Accepted systemd into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.2 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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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. ** Description changed: - [SRU TEMPLATE] + [impact] - please see template in bug 1917458 for sru template + the /dev/ptp0 device for a hyperv instance may not be the correct, + hyperv-provided, ptp device. + + [test case] + + on some hyperv instance types, particularly those that might contain + passthrough network card(s) that also provide ptp, the first ptp device + may not be the correct one to use for ptp, e.g. there may be multiple + ones: + + $ ls /dev/ptp* + /dev/ptp0 /dev/ptp1 + $ cat /sys/class/ptp/ptp0/clock_name + hyperv + $ cat /sys/class/ptp/ptp1/clock_name + mlx5_p2p + + the order can change across boots, so a consistent way of addressing the + hyperv-provided one is needed + + [regression potential] + + any regression would involve failure to properly create the ptp symlink, + or other failure while udev is processing newly detected ptp device(s) + + [scope] + + this is needed in all releases + + this was fixed upstream with the commit + 32e868f058da8b90add00b2958c516241c532b70 which is not yet included in + any release [original description] Hyperv provides a PTP device. On system with multiple PTP devices, services like Chrony don't have a way to know which one is which. We would like to have a udev rule to create a symlink to the hyperv clock. This way, services could be configured to always use this clock no matter if it is ptp0, ptp1, etc.. For example: ``` SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv" ``` ** Changed in: systemd (Ubuntu Groovy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- 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/1913763 Title: hyperv: unable to distinguish PTP devices Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Groovy: Fix Committed Bug description: [impact] the /dev/ptp0 device for a hyperv instance may not be the correct, hyperv-provided, ptp device. [test case] on some hyperv instance types, particularly those that might contain passthrough network card(s) that also provide ptp, the first ptp device may not be the correct one to use for ptp, e.g. there may be multiple ones: $ ls /dev/ptp* /dev/ptp0 /dev/ptp1 $ cat /sys/class/ptp/ptp0/clock_name hyperv $ cat /sys/class/ptp/ptp1/clock_name mlx5_p2p the order can change across boots, so a consistent way of addressing the hyperv-provided one is needed [regression potential] any regression would involve failure to properly create the ptp symlink, or other failure while udev is processing newly detected ptp device(s) [scope] this is needed in all releases this was fixed upstream with the commit 32e868f058da8b90add00b2958c516241c532b70 which is not yet included in any release [original description] Hyperv provides a PTP device. On system with multiple PTP devices, services like Chrony don't have a way to know which one is which. We would like to have a udev rule to create a symlink to the hyperv clock. This way, services could be configured to always use this clock no matter if it is ptp0, ptp1, etc.. For example: ``` SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv" ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https:
[Touch-packages] [Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd
Hiya, This was fixed in Debian via 5.1.6-4, which is merged in Hirsute release (5.1.6-4ubuntu1). Therefore, I am marking this as "Fix Released" for Hirsute. Should you have any questions or problems wrt this, let me know! Thanks. ** Changed in: autofs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1891548 Title: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd Status in autofs package in Ubuntu: Fix Released Status in openldap package in Ubuntu: New Status in autofs package in Debian: Fix Released Bug description: Ubuntu Release: # lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 Version of packages in use: # dpkg -l autofs autofs-ldap slapd | grep '^ii' ii autofs 5.1.6-2ubuntu0.1 amd64kernel-based automounter for Linux ii autofs-ldap5.1.6-2ubuntu0.1 amd64LDAP map support for autofs ii slapd 2.4.49+dfsg-2ubuntu1.3 amd64OpenLDAP server (slapd) Expected: No errors from slaptest Actual Output: 5f359370 /etc/ldap/schema/autofs.schema: line 14 attributetype: AttributeType inappropriate matching rule: "caseExactMatch" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1891548/+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 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
> Also open-vm-tools is also FTBFS by this, so I need to add a task and work on that as well. You want this kind of thing minimally to get over the FTBFS: --- open-vm-tools-11.2.5.orig/open-vm-tools/configure.ac +++ open-vm-tools-11.2.5/open-vm-tools/configure.ac @@ -503,6 +503,9 @@ AC_CHECK_PROG([have_genmarshal], [yes], [no]) +AC_DEFINE(GLIB_VERSION_MIN_REQUIRED, GLIB_VERSION_2_34, [Ignore post 2.34 deprecations]) +AC_DEFINE(GLIB_VERSION_MAX_ALLOWED, GLIB_VERSION_2_34, [Prevent post 2.34 APIs]) + if test "$have_genmarshal" != "yes"; then AC_MSG_ERROR([glib-genmarshal is required; make sure it is available in your path.]) fi But I would recommend also at least asking upstream to do the full fix and move glib's headers out of 'extern "C"' too as outlined in comment #2 here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1916705 Title: glib2.0 >=2.67.3 breaks include from an extern C context Status in glib2.0 package in Ubuntu: Fix Released Status in open-vm-tools package in Ubuntu: New Status in qemu package in Ubuntu: Fix Released Status in ukui-control-center package in Ubuntu: Triaged Bug description: qemu now breaks in Hirsute (it didn't 23h ago) Broken: https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz Good before: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages Error: ../../disas/arm-a64.cc In file included from /usr/include/glib-2.0/glib/gmacros.h:241, from /usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9, from /usr/include/glib-2.0/glib/gtypes.h:32, from /usr/include/glib-2.0/glib/galloca.h:32, from /usr/include/glib-2.0/glib.h:30, from /<>/qemu-5.2+dfsg/include/glib-compat.h:32, from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126, from ../../disas/arm-a64.cc:21: /usr/include/c++/10/type_traits:56:3: error: template with C linkage 56 | template | ^~~~ ../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here 20 | extern "C" { | ^~ Also in disas/nanomips.cpp, ... And indeed disas/arm-a64.cc has: 20 extern "C" { 21 #include "qemu/osdep.h" 22 #include "disas/dis-asm.h" 23 } Through the chain of headers as reported above this gets to the templates in /usr/include/c++/10/type_traits which fails due to that. So C++ constructs within a C scope which is this bug. Upstream qemu has not recently changed yet for this. The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc: Include osdep.h first" by Peter Maydell. But what was different before to break it now? To find that I was comparing Hirsute vs Hirsute-proposed ... It is indeed failing in -proposed but working in hirsute-release. 10.2.1-20ubuntu1 : bad repro in broken build: $ cd /root/qemu-5.2+dfsg/b/qemu $ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader -I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 -I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr -I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall -Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef -Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 -ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body -Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs -Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem /root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote /root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote /root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote /root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d -o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp With that I have a test env... Doko asked me to test https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb That f
[Touch-packages] [Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
This bug was fixed in the package qemu - 1:5.2+dfsg-6ubuntu2 --- qemu (1:5.2+dfsg-6ubuntu2) hirsute; urgency=medium * d/p/u/lp-1916705-disas-Fix-build-with-glib2.0-2.67.3.patch: Fix FTFBS due to glib2.0 >=2.67.3 (LP: #1916705) qemu (1:5.2+dfsg-6ubuntu1) hirsute; urgency=medium * Merge with Debian unstable, includes fixes for - build operates differently if source is a git repo (LP: #1887535) Remaining changes: - qemu-kvm to systemd unit - d/qemu-kvm-init: script for QEMU KVM preparation modules, ksm, hugepages and architecture specifics - d/qemu-system-common.qemu-kvm.service: systemd unit to call qemu-kvm-init - d/qemu-system-common.install: install helper script - d/qemu-system-common.qemu-kvm.default: defaults for /etc/default/qemu-kvm - d/rules: call dh_installinit and dh_installsystemd for qemu-kvm - Distribution specific machine type (LP: 1304107 1621042) - d/p/ubuntu/define-ubuntu-machine-types.patch: distro machine types - d/qemu-system-x86.NEWS Info on fixed machine type definitions for host-phys-bits=true (LP: 1776189) - add an info about -hpb machine type in debian/qemu-system-x86.NEWS - provide pseries-bionic-2.11-sxxm type as convenience with all meltdown/spectre workarounds enabled by default. (LP: 1761372). - ubuntu-q35 alias added to auto-select the most recent q35 ubuntu type - Enable nesting by default - d/p/ubuntu/enable-svm-by-default.patch: Enable nested svm by default in qemu64 on amd [ No more strictly needed, but required for backward compatibility ] - improved dependencies - Make qemu-system-common depend on qemu-block-extra - Make qemu-utils depend on qemu-block-extra - let qemu-utils recommend sharutils - tolerate ipxe size change on migrations to >=18.04 (LP: 1713490) - d/p/ubuntu/pre-bionic-256k-ipxe-efi-roms.patch: old machine types reference 256k path - d/control-in: depend on ipxe-qemu-256k-compat-efi-roms to be able to handle incoming migrations from former releases. - d/control-in: Disable capstone disassembler library support (universe) - d/qemu-system-x86.README.Debian: add info about updated nesting changes - d/control*, d/rules: disable xen by default, but provide universe package qemu-system-x86-xen as alternative [includes compat links changes of 5.0-5ubuntu4] - allow qemu to load old modules post upgrade (LP 1847361) - Drop d/qemu-block-extra.*.in, d/qemu-system-gui.*.in - d/rules: Drop generating package version into maintainer scripts - d/qemu-system-gui.prerm: add no-op prerm to overcome upgrade issues on the bad old prerm (LP 1906245 1905377) - d/p/ubuntu/lp-1907789-build-no-pie-is-no-functional-liker-flag.patch: fix ld usage of -no-pie (LP 1907789) * Added changes - d/p/u/lp-1916230-hw-s390x-fix-build-for-virtio-9p-ccw.patch: fix virtio-9p-ccw being missing (LP: #1916230) qemu (1:5.2+dfsg-6) unstable; urgency=medium * deprecate qemu-debootstrap. It is not needed anymore with binfmt F flag, since everything now works without --foreign debootstrap argument and copying the right qemu binary into the chroot. Closes: #901197 * fix the brown-paper bag bug: wrong argument order in the linux-user-binfmt patch (really closes: #970460) qemu (1:5.2+dfsg-5) unstable; urgency=medium * d/rules: ensure b/ subdir exists before building palcode and qboot * d/changelog: #959530 is not fixed by 5.2+dfsg-4 * 3 virtiofsd patches Closes: #980814, CVE-2020-35517 virtiofsd: potential privileged host device access from guest - virtiofsd-extract-lo_do_open-from-lo_open.patch - virtiofsd-optionally-return-inode-pointer-from-lo_do_lookup.patch - virtiofsd-prevent-opening-of-special-files-CVE-2020-35517.patch qemu (1:5.2+dfsg-4) unstable; urgency=medium [ Michael Tokarev ] * require libfdt >= 1.5.0-2 due to #931046 * qemu-user: attempt to preserve argv[0] when run under binfmt (Closes: #970460) This changes the enterpreter name for all linux-user registered binfmts, so it potentially can break stuff. The actual binary being registered now is /usr/libexec/qemu-binfmt/foo-binfmt-P, which is a symlink to actual /usr/lib/qemu-foo[-static]. * ignore .git-submodule-status when building source * some security fixes from upstream: o arm_gic-fix-interrupt-ID-in-GICD_SGIR-CVE-2021-20221.patch Closes: CVE-2021-20221 GIC (armv7): out-of-bound heap buffer access via an interrupt ID field o 9pfs-Fully-restart-unreclaim-loop-CVE-2021-20181.patch Closes: CVE-2021-20181 * non-security fixes from upstream: pc-bios-descriptors-fix-paths-in-json-files.patch - fixes wrong paths in edk2-firmware-related json files introduced in 5.2 [ Christian Ehrhardt ] * d/control-in: avoid version mismatch of install
[Touch-packages] [Bug 1916877] Re: Bluetooth sound card not detected
This sounds like bug 1897965, which might now be affecting 20.04.2. Please try the suggestions in bug 1897965. ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete ** Package changed: alsa-driver (Ubuntu) => pulseaudio (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/1916877 Title: Bluetooth sound card not detected Status in pulseaudio package in Ubuntu: Incomplete Bug description: "Dummy output" is on audio volume setting and there is no sound ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Feb 25 06:06:58 2021 InstallationDate: Installed on 2021-02-24 (0 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2007 dmi.bios.release: 5.2 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R0052N7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 5.2 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR0052N7:bd07/11/2007:br5.2:efr5.2:svnSonyCorporation:pnVGN-TZ150N:pvrJ002NHLG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-TZ150N dmi.product.sku: N/A dmi.product.version: J002NHLG dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1916877/+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 1917624] Re: no sound at all
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1917624 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. ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Tags added: focal ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1917624 Title: no sound at all Status in linux package in Ubuntu: Incomplete Bug description: 1. Description: Ubuntu 20.04.2 LTS Release: 20.04 2. alsa-base 1.0.25+dfsg-0ubuntu5 3. I hope can hear sound from my laptop speaker 4. I can not hear any sound from my speaker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917624/+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