[Touch-packages] [Bug 1892559] Re: [MIR] ccid opensc pcsc-lite
The plan seems quite solid, and I do agree that having some more testing would be nice (also using libsofthsm2 can help here I think). I'm not sure if all this can be achieved by the next LTS though, which I think we're targetting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1892559 Title: [MIR] ccid opensc pcsc-lite Status in ccid package in Ubuntu: New Status in opensc package in Ubuntu: Incomplete Status in pam-pkcs11 package in Ubuntu: Invalid Status in pcsc-lite package in Ubuntu: New Status in pcsc-perl package in Ubuntu: Invalid Status in pcsc-tools package in Ubuntu: Invalid Bug description: ==> ccid <== [Availability] ccid is in universe, and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs for ccid are listed in our database. Doesn't appear to bind to a socket. No privileged executables, but does have udev rules. Probably needs a security review. [Quality assurance] No test suite. Does require odd hardware that we'll probably need to buy. I don't see debconf questions. ccid is well maintained in Debian by upstream author. One open wishlist bug in BTS, harmless. One open bug in launchpad, not security, but looks very frustrating for the users. The upstream author was engaged but it never reached resolution. https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465 Has a debian/watch file. Quilt packaging. P: ccid source: no-dep5-copyright P: ccid source: package-uses-experimental-debhelper-compat-version 13 [Dependencies] Minimal dependencies, in main [Standards compliance] Appears to satisfy FHS and Debian policy [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] ccid provides drivers to interact with usb-connected smart card readers. ==> libpam-pkcs11 <== [Availability] Source package pam-pkcs11 is in universe and builds on all architectures. [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] No CVEs in our database. Doesn't appear to bind to sockets. No privileged executables (but is a PAM module). As a PAM module this will require a security review. [Quality assurance] The package does not call pam-auth-update in its postinst #1650366 Does not ask questions during install. One Ubuntu bug claims very poor behaviour if a card isn't plugged in. No Debian bugs. Occasional updates in Debian by long-term maintainer. Does require odd hardware that we'll probably need to buy. Does not appear to run tests during build. Has scary warnings in the build logs. Has a debian/watch file. Ancient standards version; other smaller lintian messages, mostly documentation problems. Quilt packaging. [Dependencies] Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1 All are in main. [Standards compliance] The package does not call pam-auth-update in its postinst #1650366 Otherwise looks to conform to FHS and Debian policies [Maintenance] The desktop team will subscribe to bugs, however it is expected that the security team will assist with security-relevant questions. [Background information] This PAM module can use CRLs and full-chain verification of certificates. It can also do LDAP, AD, and Kerberos username mapping. ==> libpcsc-perl <== [Availability] Source package pcsc-perl is in universe, builds for all architectures, plus i386 [Rationale] The desktop team and security team are interested in bringing smartcard authentication to enterprise desktop environments. [Security] There are no cves for pcsc-perl in our database. No privileged executables. Doesn't appear to bind to sockets. Probably needs a security review. [Quality assurance] Library package not intended to be used directly. No debconf questions. No bugs in Debian. No bugs in Ubuntu. Does require odd hardware that we'll probably need to buy. Tests exist, not run during the build; probably can't run during the build. Includes debian/watch file. A handful of lintian issues Quilt packaging. [Dependencies] libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0. All are in main. [Standards compliance] One oddity, Card.pod is stored in /usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/ Many other perl packages have .pod files in these directory trees so maybe it's fine, but it seems funny all the same. Otherwise appears to satisfy FHS and Debian policy. [Maintenance] The desktop team will subscribe to bugs,
[Touch-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
** Changed in: alsa-ucm-conf (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: alsa-ucm-conf (Ubuntu Impish) Status: New => In Progress -- 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/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: In Progress Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: In Progress Status in alsa-ucm-conf source package in Hirsute: In Progress Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: In Progress Status in alsa-ucm-conf source package in Impish: In Progress Status in linux source package in Impish: Fix Released Status in pulseaudio source package in Impish: Fix Released Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I sent this SRU for the focal kernel. [Impact] Users plug headphone and Mic to the audio jacks, but the system can't detect them, and couldn't output sound through headphone and record sound through Mic. [Fix] Backport a upstream patch, this will set the Mic to auto-detection mode and set the headphone to left location. [Test] Plug a headset to the headset audio jack, both headphone and mic could be detected. And output the sound to headphone, could hear the sound, record the sound through Mic, the sound could be recorded. [Where problems could occur] The patch is specific to Acer Aspire 5 machine, if it could introduce regression, it will make the audio like internal mic and internal spk stop working. But this possibility is very low. Hello, There seems to be
[Touch-packages] [Bug 1946410] Re: freezing
Please run: gsettings set org.gnome.desktop.a11y always-show-universal-access-status true and then use the new menu in the top panel to check you don't have any of those options enabled that would affect keyboard behaviour. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Summary changed: - freezing + when "/" or "?" the system hangs for 5 seconds -- 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/1946410 Title: when "/" or "?" the system hangs for 5 seconds Status in mutter package in Ubuntu: Incomplete Bug description: when "/" or "?" the system hangs for 5 seconds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 7 22:49:32 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] [1002:683f] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] [1682:3248] InstallationDate: Installed on 2021-09-29 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=e4266656-ad3e-418c-ad5b-feb2f61ea165 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0330 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0330:bd05/29/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:skuAll:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1946410/+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 1946367] Re: DisplayPort MST Hub only recognizes one of two displays using Wayland (NVIDIA)
Please report the bug upstream at: https://gitlab.gnome.org/GNOME/mutter/issues and then tell us the new issue ID. ** Package changed: wayland (Ubuntu) => mutter (Ubuntu) ** Tags added: nvidia ** Tags added: multimonitor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1946367 Title: DisplayPort MST Hub only recognizes one of two displays using Wayland (NVIDIA) Status in mutter package in Ubuntu: New Bug description: I have two 4K Monitors connected to a single DisplayPort 1.4 Output via a DisplayPort 1.4 MST Hub working flawlessly under X.org. I have enabled nvidia-drm.modeset=1 in the GRUB CMDLINE Settings and switched to Wayland in the GDM Greeter. But it seems like Wayland is unable to drive multiple displays via a DisplayPort 1.4 MST Hub, because only one of them shows a display output. However they are both correctly recognized under the display settings. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..2a.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 7 15:05:07 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: zfs, 2.0.6, 5.13.0-16-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA102 [GeForce RTX 3080 Ti] [10de:2208] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA102 [GeForce RTX 3080 Ti] [10de:1535] InstallationDate: Installed on 2021-10-07 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_10kpab@/vmlinuz-5.13.0-16-generic root=ZFS=rpool/ROOT/ubuntu_10kpab ro quiet splash nvidia-drm.modeset=1 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.20 dmi.board.name: X570 Phantom Gaming-ITX/TB3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.20:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1946367/+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 1946410] [NEW] freezing
Public bug reported: when "/" or "?" the system hangs for 5 seconds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 7 22:49:32 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] [1002:683f] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] [1682:3248] InstallationDate: Installed on 2021-09-29 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=e4266656-ad3e-418c-ad5b-feb2f61ea165 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0330 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0330:bd05/29/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:skuAll:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal performance 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/1946410 Title: freezing Status in xorg package in Ubuntu: New Bug description: when "/" or "?" the system hangs for 5 seconds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 7 22:49:32 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] [1002:683f] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] [1682:3248] InstallationDate: Installed on 2021-09-29 (8 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=e4266656-ad3e-418c-ad5b-feb2f61ea165 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0330 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0330:bd05/29/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:skuAll:rvnASUSTeKCOMPUTERINC.:rnZ97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2
[Touch-packages] [Bug 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s
Dan, note that although we set the SNAP_REEXEC environment variable in that integration test, that environment variable is actually not obeyed when it comes to the mksquashfs command which is called here: https://github.com/snapcore/snapd/blob/dfba7de59a41bc22786d87f53b20deea14240713/snap/squashfs/squashfs.go#L524 and the function snapdtool.CommandFromSystemSnap does not observe the SNAP_REEXEC environment variable at all, instead just checking if the snapd or core snaps exist at all, and using the mksquashfs from those snaps instead of what's on the host on $PATH (though we do fallback and if there is no mksquashfs found in the core or snapd snaps (somehow???), then we use $PATH). As I mentioned on IRC, we could potentially someday add a workaround where if mksquashfs from the system snap specifically segfaults then we will fall back to using the host's mksquashfs, but we have chosen for now not to work on that patch. Hope this helps explain things. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1943077 Title: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s Status in snapd: Fix Committed Status in openssh package in Ubuntu: New Status in squashfs-tools package in Ubuntu: New Bug description: During current snapd autopkgtest, a failure can be observed: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/amd64/s/snapd/20210907_175258_5451b@/log.gz error: cannot pack "/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox": mksquashfs call failed: - libgcc_s.so.1 must be installed for pthread_cancel to work Parallel mksquashfs: Using 1 processor Creating 4.0 filesystem on /home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox/test-snapd-sandbox_1.0_all.snap, block size 131072. - error: cannot read snap file: "/var/lib/snapd/snaps/.local-install-136125945" is not a snap or snapdir I traced the underlying call to the following: "/snap/snapd/current/lib/x86_64-linux-gnu/ld-2.23.so" "--library-path" "/snap/snapd/current/usr/local/lib:/snap/snapd/current/lib/x86_64-linux-gnu:/snap/snapd/current/usr/lib/x86_64-linux-gnu" "/snap/snapd/current/usr/bin/mksquashfs" asdf asdf.squashfs (the real call has more arguments, this is a simplified version that produces the failure) To observe this, one can create a VM based a cloud image from https://cloud-images.ubuntu.com/impish/current, then run the above command in the resulting environment. Doing so will test against snapd v2.51.4 (12883). Retesting with edge 2.52+git635.gada2d87 (13323) produces an equivalent result. Running a more bland `/snap/snapd/current/usr/bin/mksquashfs asdf asdf.squashfs` without messing with library paths has mksquashfs behaving as expected. Also, getting a v2.51.3 snapd seems to behave itself. Updating from 2.51.3 -> 2.51.4 also works. One can see a passing mksquashfs by taking libgcc_s.so.1 from hirsute and placing it in the library path for the above call. In the working scenario, it appears that libgcc_s is being obtained from outside of /snap (and also libz). In the failing scenario, this external copy of libgcc_s is not being loaded (per gdb info sharedlibrary), but libz still is. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1943077/+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 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.
** Changed in: oem-priority Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Apply upstream patches to fix problems for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Committed Bug description: [Impact] The following 2 modems need the ModemManager v1.16.6 suite to be patched from v1.18.2 to fix some problems(LP#1943774, LP#1943780): * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested upstream patches are for these 2 specific modems and the status information. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading application can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1943077] Re: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s
Snapd team advises that this will be fixed in 2.52.1, and that affected users should pick up that version when available or, in the mean time, pickup a newer snapd. Currently the beta channel has this 2.52.1 version, which does appear to resolve the issue. Based on this advise I'm removing 'rls-ii-incoming' Note that this version being on stable does not necessarily fix autopkgtest, as this deb version of snapd goes out of its way to NOT actually install the snap version of snapd. https://github.com/snapcore/snapd/blob/master/packaging/ubuntu-16.04/tests/integrationtests#L38 ** Tags removed: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1943077 Title: snapd fails to autopkgtest on mksquashfs, which is looking for libgcc_s Status in snapd: Fix Committed Status in openssh package in Ubuntu: New Status in squashfs-tools package in Ubuntu: New Bug description: During current snapd autopkgtest, a failure can be observed: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/amd64/s/snapd/20210907_175258_5451b@/log.gz error: cannot pack "/home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox": mksquashfs call failed: - libgcc_s.so.1 must be installed for pthread_cancel to work Parallel mksquashfs: Using 1 processor Creating 4.0 filesystem on /home/gopath/src/github.com/snapcore/snapd/tests/smoke/sandbox/test-snapd-sandbox/test-snapd-sandbox_1.0_all.snap, block size 131072. - error: cannot read snap file: "/var/lib/snapd/snaps/.local-install-136125945" is not a snap or snapdir I traced the underlying call to the following: "/snap/snapd/current/lib/x86_64-linux-gnu/ld-2.23.so" "--library-path" "/snap/snapd/current/usr/local/lib:/snap/snapd/current/lib/x86_64-linux-gnu:/snap/snapd/current/usr/lib/x86_64-linux-gnu" "/snap/snapd/current/usr/bin/mksquashfs" asdf asdf.squashfs (the real call has more arguments, this is a simplified version that produces the failure) To observe this, one can create a VM based a cloud image from https://cloud-images.ubuntu.com/impish/current, then run the above command in the resulting environment. Doing so will test against snapd v2.51.4 (12883). Retesting with edge 2.52+git635.gada2d87 (13323) produces an equivalent result. Running a more bland `/snap/snapd/current/usr/bin/mksquashfs asdf asdf.squashfs` without messing with library paths has mksquashfs behaving as expected. Also, getting a v2.51.3 snapd seems to behave itself. Updating from 2.51.3 -> 2.51.4 also works. One can see a passing mksquashfs by taking libgcc_s.so.1 from hirsute and placing it in the library path for the above call. In the working scenario, it appears that libgcc_s is being obtained from outside of /snap (and also libz). In the failing scenario, this external copy of libgcc_s is not being loaded (per gdb info sharedlibrary), but libz still is. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1943077/+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 1946343] Re: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
This is the output of my dpkg-query for os-release: $ dpkg-query --search os-release systemd: /usr/share/man/man5/os-release.5.gz diversion by oem-release from: /usr/lib/os-release diversion by oem-release to: /usr/lib/os-release.oem-release base-files: /etc/os-release diversion by oem-release from: /usr/lib/os-release diversion by oem-release to: /usr/lib/os-release.oem-release base-files: /usr/lib/os-release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1946343 Title: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3 Status in base-files package in Ubuntu: Invalid Bug description: Refer: https://answers.launchpad.net/ubuntu/+question/698949 I recently bought a Dell laptop with Ubuntu pre-installed in it. Looks like it came with Ubuntu 20.04.2 and OEM Linux Kernel in it. After my initial login (on October 1, 2021), the 'Software Updater' GUI prompted me for updates, which I went ahead with. However at the end of it, I noticed that I was still at 20.04.2 with Linux Kernel at 5.10.0-1045-oem. lsb_release -a --- No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal uname -a - Linux dev-linux 5.10.0-1045-oem #47-Ubuntu SMP Wed Aug 18 10:41:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Then I manually tried sudo apt update and sudo apt upgrade / dist- upgrade from the terminal, but nothing got upgraded. When I invoked the GUI 'Software Updater' again, it showed me that my system was already up-to-date. However, as 20.04.3 was released end of Aug 2021, I was expecting that I should be at that release after my initial updates. Since that didn't happen, I asked a question regarding this in askubuntu followed by launchpad https://answers.launchpad.net/ubuntu/+question/698949, thinking my update had failed for some unknown reason. However, based on some inputs from other users, we were able to narrow down the problem to /usr/lib/os-release file not having the right contents in it. Every other file including /usr/lib/os-release.oem- release, /etc/issue, /etc/issue.net specifies that I am on 20.04.3. Whereas only /usr/lib/os-release (and its symlink /etc/release) specifies my current release as 20.04.2. Even the lsb_release -a command always displays the output of /usr/lib/os-release file only. $ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /usr/lib/os-release.oem-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /etc/issue Ubuntu 20.04.3 LTS \n \l $ cat /etc/issue.net Ubuntu 20.04.3 LTS If you look at the timestamp of these files, strangely os-release had a newer timestamp of Oct 1 compared to other files. $ ls -l /usr/lib/os-release -rw-r--r-- 1 root root 406 Oct 1 20:31 /usr/lib/os-release $ ls -l /usr/lib/os-release.oem-release -rw-r--r-- 1 root root 382 Aug 4 07:53 /usr/lib/os-release.oem-release $ ls -l /etc/issue -rw-r--r-- 1 root root 26 Aug 4 07:53 /etc/issue $ ls -l /etc/issue.net -rw-r--r-- 1 root root 19 Aug 4 07:53 /etc/issue.net Please note that, other software package updates, and linux kernel updates are happening automatically without any issues so far for me. Few days back even got a new kernel update. $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Workarounds Attempted - 1. Commented out all non-ubuntu external sources from /etc/apt/*.list. Then performed an apt clean + update + upgrade. But still nothing happened and the same issue remained. 2. Tried performing apt-install --reinstall base-files. But still nothing changed: $ sudo apt install --reinstall base-files Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 4 not upgraded. Need to get 60.6 kB of archives. After this operation, 0 B of additional disk
[Touch-packages] [Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer
** Changed in: rsync Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1659950 Title: rsync -u --inplace --partial -a can't resume transfer Status in rsync: New Status in rsync package in Ubuntu: Opinion Bug description: Suppose you have a file in hostA: hostA$ ls -l /tmp/files -rw-rw-r-- 2 root root 563016 Jan 10 15:01 test.txt You download it from the hostB using: hostB$ rsync -u --inplace --partial -a hostA::files/* . If the transfer is aborted, hostB will get only a partial file: hostB$ ls -l /tmp/files -rw-rw-r-- 2 root root 2024 Jan 11 18:00 test.txt BUT the ctime/mtime of hostB/test.txt now is NEWER than hostA/test.txt(and mtime == ctime). So, if you run the same rsync -u command again: hostB$ rsync -u --inplace --partial -a hostA::files/* . Rsync will SKIP THE FILE, because hostB/test.txt is "newer" than hostA/test.txt. So you CAN'T resume using rsync -u command, and you will think there are no differences. To avoid this bug, rsync must create the file with ctime=mtime=0. And if the file already exists before transfer, rsync -u must not change his current ctime/mtime. Ctime/mtime must be updated ONLY after the transfer was successfully completed. Note this is really need because there are scenarios where checksum comparison can't be used, only comparison by time. For example, to avoid deleting changes made in hostB to test.txt. Also I need to use --inplace. To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1659950/+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 1946388] [NEW] Journalctl -f --file some.journal causes coredump
Public bug reported: Focal latest systemd 245. Journalctl -f --file path/to/file.journal. Will allways causes journalctl crash... The same doesnt happen on centos8 systemd 239... I couldnt test on any more systems atm. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1946388 Title: Journalctl -f --file some.journal causes coredump Status in systemd package in Ubuntu: New Bug description: Focal latest systemd 245. Journalctl -f --file path/to/file.journal. Will allways causes journalctl crash... The same doesnt happen on centos8 systemd 239... I couldnt test on any more systems atm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1946388/+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 1946343] Re: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
@Steve, thank you for looking into this. If this is not a base-files issue, where could the problem be? I have not installed any other package myself. This is just the Ubuntu installation that the laptop came with. As an end user I am unable to see whether upgrade to 20.04.3 is successful or not. Clearly lsb_release is not saying so. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1946343 Title: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3 Status in base-files package in Ubuntu: Invalid Bug description: Refer: https://answers.launchpad.net/ubuntu/+question/698949 I recently bought a Dell laptop with Ubuntu pre-installed in it. Looks like it came with Ubuntu 20.04.2 and OEM Linux Kernel in it. After my initial login (on October 1, 2021), the 'Software Updater' GUI prompted me for updates, which I went ahead with. However at the end of it, I noticed that I was still at 20.04.2 with Linux Kernel at 5.10.0-1045-oem. lsb_release -a --- No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal uname -a - Linux dev-linux 5.10.0-1045-oem #47-Ubuntu SMP Wed Aug 18 10:41:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Then I manually tried sudo apt update and sudo apt upgrade / dist- upgrade from the terminal, but nothing got upgraded. When I invoked the GUI 'Software Updater' again, it showed me that my system was already up-to-date. However, as 20.04.3 was released end of Aug 2021, I was expecting that I should be at that release after my initial updates. Since that didn't happen, I asked a question regarding this in askubuntu followed by launchpad https://answers.launchpad.net/ubuntu/+question/698949, thinking my update had failed for some unknown reason. However, based on some inputs from other users, we were able to narrow down the problem to /usr/lib/os-release file not having the right contents in it. Every other file including /usr/lib/os-release.oem- release, /etc/issue, /etc/issue.net specifies that I am on 20.04.3. Whereas only /usr/lib/os-release (and its symlink /etc/release) specifies my current release as 20.04.2. Even the lsb_release -a command always displays the output of /usr/lib/os-release file only. $ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /usr/lib/os-release.oem-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /etc/issue Ubuntu 20.04.3 LTS \n \l $ cat /etc/issue.net Ubuntu 20.04.3 LTS If you look at the timestamp of these files, strangely os-release had a newer timestamp of Oct 1 compared to other files. $ ls -l /usr/lib/os-release -rw-r--r-- 1 root root 406 Oct 1 20:31 /usr/lib/os-release $ ls -l /usr/lib/os-release.oem-release -rw-r--r-- 1 root root 382 Aug 4 07:53 /usr/lib/os-release.oem-release $ ls -l /etc/issue -rw-r--r-- 1 root root 26 Aug 4 07:53 /etc/issue $ ls -l /etc/issue.net -rw-r--r-- 1 root root 19 Aug 4 07:53 /etc/issue.net Please note that, other software package updates, and linux kernel updates are happening automatically without any issues so far for me. Few days back even got a new kernel update. $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Workarounds Attempted - 1. Commented out all non-ubuntu external sources from /etc/apt/*.list. Then performed an apt clean + update + upgrade. But still nothing happened and the same issue remained. 2. Tried performing apt-install --reinstall base-files. But still nothing changed: $ sudo apt install --reinstall base-files Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 4 not upgraded. Need to get 60.6 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu
[Touch-packages] [Bug 1946209] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1946209/+attachment/5531338/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1946209 Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued() Status in evolution-data-server package in Ubuntu: Incomplete Bug description: Crashes when going to system setting / Graphic tablet / manually register a tablet / select Multi-device tablet pen sensor => crash ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: evolution-data-server 3.40.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: KDE Date: Wed Oct 6 10:32:24 2021 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify Signal: 5 SourcePackage: evolution-data-server StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to impish on 2021-10-03 (3 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo uinput separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1946209/+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 1946209] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1946209/+attachment/5531339/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1946209/+attachment/5531020/+files/CoreDump.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1946209 Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued() Status in evolution-data-server package in Ubuntu: Incomplete Bug description: Crashes when going to system setting / Graphic tablet / manually register a tablet / select Multi-device tablet pen sensor => crash ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: evolution-data-server 3.40.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: KDE Date: Wed Oct 6 10:32:24 2021 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify Signal: 5 SourcePackage: evolution-data-server StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to impish on 2021-10-03 (3 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo uinput separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1946209/+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 1946209] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1946209/+attachment/5531337/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1946209 Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued() Status in evolution-data-server package in Ubuntu: Incomplete Bug description: Crashes when going to system setting / Graphic tablet / manually register a tablet / select Multi-device tablet pen sensor => crash ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: evolution-data-server 3.40.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: KDE Date: Wed Oct 6 10:32:24 2021 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify Signal: 5 SourcePackage: evolution-data-server StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to impish on 2021-10-03 (3 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo uinput separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1946209/+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 1946209] evolution-alarm-notify crashed with signal 5 in _XEventsQueued()
StacktraceTop: XPending (dpy=0x560aba38aef0) at ../../src/Pending.c:55 gdk_check_xpending (display=0x560aba3a10e0) at x11/../../../../../gdk/x11/gdkeventsource.c:269 gdk_event_source_check (source=source@entry=0x560aba3e2cb0) at x11/../../../../../gdk/x11/gdkeventsource.c:306 g_main_context_check (context=0x560aba3e2da0, max_priority=2147483647, fds=, n_fds=-728157272) at ../../../glib/gmain.c:3955 g_main_context_iterate.constprop.0 (context=context@entry=0x560aba3e2da0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1946209 Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued() Status in evolution-data-server package in Ubuntu: Incomplete Bug description: Crashes when going to system setting / Graphic tablet / manually register a tablet / select Multi-device tablet pen sensor => crash ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: evolution-data-server 3.40.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: KDE Date: Wed Oct 6 10:32:24 2021 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify Signal: 5 SourcePackage: evolution-data-server StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: evolution-alarm-notify crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to impish on 2021-10-03 (3 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo uinput separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1946209/+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 1946343] Re: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
$ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal You have an OEM-specific package installed that diverts /usr/lib/os- release and replaces the contents. The fact that this file has not changed when base-files changed is not a bug in base-files. ** Changed in: base-files (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1946343 Title: Stale os-release file after possible upgrade from 20.04.2 to 20.04.3 Status in base-files package in Ubuntu: Invalid Bug description: Refer: https://answers.launchpad.net/ubuntu/+question/698949 I recently bought a Dell laptop with Ubuntu pre-installed in it. Looks like it came with Ubuntu 20.04.2 and OEM Linux Kernel in it. After my initial login (on October 1, 2021), the 'Software Updater' GUI prompted me for updates, which I went ahead with. However at the end of it, I noticed that I was still at 20.04.2 with Linux Kernel at 5.10.0-1045-oem. lsb_release -a --- No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal uname -a - Linux dev-linux 5.10.0-1045-oem #47-Ubuntu SMP Wed Aug 18 10:41:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Then I manually tried sudo apt update and sudo apt upgrade / dist- upgrade from the terminal, but nothing got upgraded. When I invoked the GUI 'Software Updater' again, it showed me that my system was already up-to-date. However, as 20.04.3 was released end of Aug 2021, I was expecting that I should be at that release after my initial updates. Since that didn't happen, I asked a question regarding this in askubuntu followed by launchpad https://answers.launchpad.net/ubuntu/+question/698949, thinking my update had failed for some unknown reason. However, based on some inputs from other users, we were able to narrow down the problem to /usr/lib/os-release file not having the right contents in it. Every other file including /usr/lib/os-release.oem- release, /etc/issue, /etc/issue.net specifies that I am on 20.04.3. Whereas only /usr/lib/os-release (and its symlink /etc/release) specifies my current release as 20.04.2. Even the lsb_release -a command always displays the output of /usr/lib/os-release file only. $ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /usr/lib/os-release.oem-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /etc/issue Ubuntu 20.04.3 LTS \n \l $ cat /etc/issue.net Ubuntu 20.04.3 LTS If you look at the timestamp of these files, strangely os-release had a newer timestamp of Oct 1 compared to other files. $ ls -l /usr/lib/os-release -rw-r--r-- 1 root root 406 Oct 1 20:31 /usr/lib/os-release $ ls -l /usr/lib/os-release.oem-release -rw-r--r-- 1 root root 382 Aug 4 07:53 /usr/lib/os-release.oem-release $ ls -l /etc/issue -rw-r--r-- 1 root root 26 Aug 4 07:53 /etc/issue $ ls -l /etc/issue.net -rw-r--r-- 1 root root 19 Aug 4 07:53 /etc/issue.net Please note that, other software package updates, and linux kernel updates are happening automatically without any issues so far for me. Few days back even got a new kernel update. $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Workarounds Attempted - 1. Commented out all non-ubuntu external sources from /etc/apt/*.list. Then performed an apt clean + update + upgrade. But still nothing happened and the same issue remained. 2. Tried performing apt-install --reinstall base-files. But still nothing changed: $ sudo apt install
[Touch-packages] [Bug 1946196] Re: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1946196 Title: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257) Status in software-properties package in Ubuntu: Triaged Bug description: Additional Drivers fails to install nvidia-driver-470: Error while applying changes pk-client-error-quark: Cannot download packages whilst offline (257) But the machine is ONLINE with full Internet access. WORKAROUND: sudo apt install nvidia-driver-470 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1946196/+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 1946367] [NEW] DisplayPort MST Hub only recognizes one of two displays using Wayland (NVIDIA)
Public bug reported: I have two 4K Monitors connected to a single DisplayPort 1.4 Output via a DisplayPort 1.4 MST Hub working flawlessly under X.org. I have enabled nvidia-drm.modeset=1 in the GRUB CMDLINE Settings and switched to Wayland in the GDM Greeter. But it seems like Wayland is unable to drive multiple displays via a DisplayPort 1.4 MST Hub, because only one of them shows a display output. However they are both correctly recognized under the display settings. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..2a.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 7 15:05:07 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: zfs, 2.0.6, 5.13.0-16-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA102 [GeForce RTX 3080 Ti] [10de:2208] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA102 [GeForce RTX 3080 Ti] [10de:1535] InstallationDate: Installed on 2021-10-07 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_10kpab@/vmlinuz-5.13.0-16-generic root=ZFS=rpool/ROOT/ubuntu_10kpab ro quiet splash nvidia-drm.modeset=1 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.20 dmi.board.name: X570 Phantom Gaming-ITX/TB3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.20:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnX570PhantomGaming-ITX/TB3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu wayland-session ** Package changed: xorg (Ubuntu) => wayland (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/1946367 Title: DisplayPort MST Hub only recognizes one of two displays using Wayland (NVIDIA) Status in wayland package in Ubuntu: New Bug description: I have two 4K Monitors connected to a single DisplayPort 1.4 Output via a DisplayPort 1.4 MST Hub working flawlessly under X.org. I have enabled nvidia-drm.modeset=1 in the GRUB CMDLINE Settings and switched to Wayland in the GDM Greeter. But it seems like Wayland is unable to drive multiple displays via a DisplayPort 1.4 MST Hub, because only one of them shows a display output. However they are both correctly recognized under the display settings. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package:
[Touch-packages] [Bug 788167] Re: CUPS cannot print to Kerberos-authenticated SMB print queue
Still not possible to print to via SMB shared printer with kerberos authentication. "No valid Kerberos credential cache found!" Ubuntu 20.04.3 Cups 2.3.1 smbclient 4.11.6-Ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/788167 Title: CUPS cannot print to Kerberos-authenticated SMB print queue Status in cups package in Ubuntu: Confirmed Status in Debian: Fix Released Bug description: Binary package hint: cups That was investigated on maverick (cups 1.4.4) and natty (cups 1.4.6). CUPS in Ubuntu cannot authenticate using Kerberos to an SMB print queue, such as one in an Active Directory. This is because the smb backend is being invoked as user lp, and this user cannot access the Kerberos credential cache of the user who submitted the job. When trying to print, the job is held for authentication, and a dialog prompting for username/password is being shown. On Windows (and possibly other OS), the user would not be prompted if he has a ticket in the Kerberos realm (ie, "logged on to the domain") he is trying to print to. The CUPS smb backend on Ubuntu is the smbspool binary provided by Samba. When run as a user, it will pick the Kerberos credential cache by itself and authenticate seamlessly. Otherwise, it will read the KRB5CCNAME environment variable and try to use that when possible. There is two possible solutions to that: - Invoke the smb backend as root and pass it the KRB5CCNAME environment variable pointing to the user's Kerberos credential cache. CUPS execute the backend as user lp if it is world-executable, which is currently the case on Ubuntu. User lp do not have the permission to read the user's credential cache, hence why the smb backend would need to be executed as root (by removing the world-executable bit). Also, CUPS does not currently set KRB5CCNAME before invoking the smb backend (see http://www.cups.org/str.php?L3847). - Execute smbspool as the user submitting the job. I presume we would have the same problem with other backend that would do Kerberos authentication, although I do not know of a specific one. I have only tested and investigated with the smb backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/788167/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: evince (Ubuntu) Assignee: (unassigned) => Georgia Garcia (georgiag) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Olivier, yes, I shouldn't be assigned. Ian, you're right the profile is
suboptimal (it's also old so likely needs updating).
Do note that this is a separate named profile and evince (and if this is
put in an abstraction, anything that uses the abstraction) only has the
`/{,snap/core/[0-9]*/}usr/bin/snap mrCx -> snap_browser,` rule which
means that it is able to run the 'snap' command (needed since everything
in /snap/bin points to /usr/bin/snap) which at the time I wrote the
profile meant that access to this socket was needed as part of snap run.
IIRC, snapd should be protecting certain actions by uid connecting to it
(eg, you are root or not), but it has been a while since I've looked at
that. Evince is not a snap though so if snapd does any checks on 'is the
client a snap' then those would fail and evince would be able to do
whatever a non-root user could do with the 'snap' command via the
socket.
For snap run, we can see that the snap_browser profile limits what can
be used with 'run' since (at the time I wrote the comment) 'snap run'
required being able to look at the meta/snap.yaml of the specific snap.
This 'works' (worked?) but is brittle since if snap run changed to lift
this requirement (eg, 'snap run' just passed the name of the unresolved
symlink to snapd over the socket and let snapd start the snap, perhaps
via userd, etc) then this falls apart.
The profile was put up as an example as what could be done at the time without
any help from snapd. I never particularly cared for it cause it was brittle and
not designed. I'm not sure how to fix this, but here are some thoughts:
* evince is just executing stuff from /snap/bin (probably via the system's
xdg-open). Assuming xdg-open, the system's xdg-open (or whatever evince is
using to decide and launch the default browser) could itself be fixed in Ubuntu
to launch a different command that behaved better. This wouldn't necessarily
fix other distros (though this is the evince profile in Debian and Ubuntu, so
*technically*, if you got this change (to presumably xdg-open) into them, you
could update the evince profile in them accordingly)
* In lieu of that, if the profile still worked as intended, snapd could be
hardened to look to check more than if the connecting process is root or a
snap; it could also see if it is running under a non-snap profile, then limit
access to the socket API accordingly. This has drawbacks and could break people
who have written custom profiles similar to what I presented.
* I suppose an alternative approach would be to have symlinks in /snap/bin for
things that are registered as browsers (or just the default browser) point to a
designed snap command. Eg:
/snap/bin/firefox -> /usr/bin/snap # keep the
existing one too
/snap/bin/default-browser-is-a-snap -> /usr/bin/snap-browser # name is
illustrative, TBD
Now firefox, chromium, opera, brave, etc snaps registers themselves as
being capable of being a default browser with snapd, then snapd
registers with the system that /snap/bin/default-browser-is-a-snap is
the default browser (so system utilities like xdg-open don't need to
change) and /usr/bin/snap-browser is written to be safe (eg, only able
to 'snap run' the configured default browser, nothing else) and apparmor
profiles are adjusted to have `/{,snap/core/[0-9]*/}usr/bin/snap-browser
Uxr,` (or similar). The /snap/bin/default-browser-is-a-snap path is
illustrative and there isn't really a need for it at all. Could simply
perhaps have snapd register /usr/bin/snap-browser as the default browser
on the system (it now needs to know what snapd configured as the default
browser snap though) and forego the symlink.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1794064
Title:
Clicking a hyperlink in a PDF fails to open it if the default browser
is a snap
Status in apparmor package in Ubuntu:
Confirmed
Status in evince package in Ubuntu:
Triaged
Bug description:
This is related to bug #1792648. After fixing that one (see discussion
at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
clicking a hyperlink in a PDF opens it correctly if the default
browser is a well-known application (such as /usr/bin/firefox), but it
fails to do so if the default browser is a snap (e.g. the chromium
snap).
This is not a recent regression, it's not working on bionic either.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: evince 3.30.0-2
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 24 12:28:06 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-02 (813 days ago)
InstallationMedia: Ubuntu 16.04 LTS
[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: evince (Ubuntu) Assignee: Jamie Strandboge (jdstrand) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1662620] Re: "ip addr add" permits illegal labels
Not sure if it will pass build, review or be acceptable as SRU since it is so low impact. But the fix was so trivial that after all this time I'd feel bad to keep it as-is. So I've prepared an MP to fix it https://code.launchpad.net/~paelzer/ubuntu/+source/iproute2/+git/iproute2/+merge/409821 And a PPA with a test build https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4676/+packages ** Tags added: server-todo ** Changed in: iproute2 (Ubuntu Bionic) Assignee: (unassigned) => Christian Ehrhardt (paelzer) ** Description changed: + [Impact] + + * The filter on label names does not match the intention +by upstream nor the description in the man page + + * Fix by backporting upstream fix that strengthens the check + + [Test Plan] + + Bad case: + root@b:~# ip addr add 1.1.1.1 label test1 dev eth0 + "dev" (eth0) must match "label" (test1). + root@b:~# ip addr add 1.1.1.1 label eth0-test dev eth0 + root@b:~# ip addr show dev eth0 | grep test + inet 1.1.1.1/32 scope global eth0-test + + With the fix it should look like: + root@i:~# ip addr add 1.1.1.1 label test1 dev eth0 + "label" (test1) must match "dev" (eth0) or be prefixed by "dev" with a colon. + root@i:~# ip addr add 1.1.1.1 label eth0-test dev eth0 + "label" (eth0-test) must match "dev" (eth0) or be prefixed by "dev" with a colon. + root@i:~# ip addr show dev eth0 | grep test + + [Where problems could occur] + + * While the fix indeed "corrects" behavior I must say that if someone +relied on the non-intended behavior it would now break e.g. his +scripting or automation. + + [Other Info] + + * It was too easy to fix and too long dormant to ignore it further, +but if the SRU team says this is too much regression risk relative to +the gain we will mark it Won't Fix based on that decision. + + + --- + ip-address(8) manpage states: - label NAME - Each address may be tagged with a label string. In order to preserve compatibility with Linux-2.0 net aliases, this string must coincide with the name of the device or must be prefixed with the device name followed by colon. + label NAME + Each address may be tagged with a label string. In order to preserve compatibility with Linux-2.0 net aliases, this string must coincide with the name of the device or must be prefixed with the device name followed by colon. But you can omit the colon, "ip addr add" is ONLY checking the label is prefixed with the device: # ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). # ip addr add 1.1.1.2 label eth0-test2 dev eth0 # ip addr add 1.1.1.3 label eth0:test3 dev eth0 - Now ifconfig becomes confused about eth0-test2: # ifconfig eth0-test2 eth0-test2: error fetching interface information: Device not found # ifconfig eth0:test3 - eth0:test3 Link encap:Ethernet HWaddr b0:d5:cc:fe:1d:7c - inet addr:1.1.1.3 Bcast:0.0.0.0 Mask:255.255.255.255 - UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 - Interrupt:171 + eth0:test3 Link encap:Ethernet HWaddr b0:d5:cc:fe:1d:7c + inet addr:1.1.1.3 Bcast:0.0.0.0 Mask:255.255.255.255 + UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 + Interrupt:171 And daemons like ntpd also log errors about the interface with the illegal label: ntpd[7570]: eth0-test3: getting interface flags: No such device - ## => many of this error per minute until: + ## => many of this error per minute until: ntpd[7570]: Too many errors. Shutting up. - - So, I think ip addr show disallow adding address with illegal (as stated by his own documentation) labels, it must also check for the colon following the dev name. + So, I think ip addr show disallow adding address with illegal (as stated + by his own documentation) labels, it must also check for the colon + following the dev name. Version: 4.3.0-1ubuntu3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1662620 Title: "ip addr add" permits illegal labels Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Triaged Bug description: [Impact] * The filter on label names does not match the intention by upstream nor the description in the man page * Fix by backporting upstream fix that strengthens the check [Test Plan] Bad case: root@b:~# ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). root@b:~# ip addr add 1.1.1.1 label eth0-test dev eth0 root@b:~# ip addr show dev eth0 | grep test inet 1.1.1.1/32 scope global eth0-test With the fix it should look like: root@i:~# ip addr add 1.1.1.1 label test1 dev eth0 "label" (test1) must match "dev" (eth0) or be prefixed by "dev" with a colon. root@i:~# ip addr add 1.1.1.1 label
[Touch-packages] [Bug 1662620] Re: "ip addr add" permits illegal labels
SRU template added -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1662620 Title: "ip addr add" permits illegal labels Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Triaged Bug description: [Impact] * The filter on label names does not match the intention by upstream nor the description in the man page * Fix by backporting upstream fix that strengthens the check [Test Plan] Bad case: root@b:~# ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). root@b:~# ip addr add 1.1.1.1 label eth0-test dev eth0 root@b:~# ip addr show dev eth0 | grep test inet 1.1.1.1/32 scope global eth0-test With the fix it should look like: root@i:~# ip addr add 1.1.1.1 label test1 dev eth0 "label" (test1) must match "dev" (eth0) or be prefixed by "dev" with a colon. root@i:~# ip addr add 1.1.1.1 label eth0-test dev eth0 "label" (eth0-test) must match "dev" (eth0) or be prefixed by "dev" with a colon. root@i:~# ip addr show dev eth0 | grep test [Where problems could occur] * While the fix indeed "corrects" behavior I must say that if someone relied on the non-intended behavior it would now break e.g. his scripting or automation. [Other Info] * It was too easy to fix and too long dormant to ignore it further, but if the SRU team says this is too much regression risk relative to the gain we will mark it Won't Fix based on that decision. --- ip-address(8) manpage states: label NAME Each address may be tagged with a label string. In order to preserve compatibility with Linux-2.0 net aliases, this string must coincide with the name of the device or must be prefixed with the device name followed by colon. But you can omit the colon, "ip addr add" is ONLY checking the label is prefixed with the device: # ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). # ip addr add 1.1.1.2 label eth0-test2 dev eth0 # ip addr add 1.1.1.3 label eth0:test3 dev eth0 Now ifconfig becomes confused about eth0-test2: # ifconfig eth0-test2 eth0-test2: error fetching interface information: Device not found # ifconfig eth0:test3 eth0:test3 Link encap:Ethernet HWaddr b0:d5:cc:fe:1d:7c inet addr:1.1.1.3 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:171 And daemons like ntpd also log errors about the interface with the illegal label: ntpd[7570]: eth0-test3: getting interface flags: No such device ## => many of this error per minute until: ntpd[7570]: Too many errors. Shutting up. So, I think ip addr show disallow adding address with illegal (as stated by his own documentation) labels, it must also check for the colon following the dev name. Version: 4.3.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1662620/+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 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.
** Changed in: modemmanager (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Apply upstream patches to fix problems for Foxconn and Quectel modems. Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: Fix Committed Bug description: [Impact] The following 2 modems need the ModemManager v1.16.6 suite to be patched from v1.18.2 to fix some problems(LP#1943774, LP#1943780): * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested upstream patches are for these 2 specific modems and the status information. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading application can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1662620] Re: "ip addr add" permits illegal labels
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/iproute2/+git/iproute2/+merge/409821 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1662620 Title: "ip addr add" permits illegal labels Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Triaged Bug description: ip-address(8) manpage states: label NAME Each address may be tagged with a label string. In order to preserve compatibility with Linux-2.0 net aliases, this string must coincide with the name of the device or must be prefixed with the device name followed by colon. But you can omit the colon, "ip addr add" is ONLY checking the label is prefixed with the device: # ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). # ip addr add 1.1.1.2 label eth0-test2 dev eth0 # ip addr add 1.1.1.3 label eth0:test3 dev eth0 Now ifconfig becomes confused about eth0-test2: # ifconfig eth0-test2 eth0-test2: error fetching interface information: Device not found # ifconfig eth0:test3 eth0:test3 Link encap:Ethernet HWaddr b0:d5:cc:fe:1d:7c inet addr:1.1.1.3 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:171 And daemons like ntpd also log errors about the interface with the illegal label: ntpd[7570]: eth0-test3: getting interface flags: No such device ## => many of this error per minute until: ntpd[7570]: Too many errors. Shutting up. So, I think ip addr show disallow adding address with illegal (as stated by his own documentation) labels, it must also check for the colon following the dev name. Version: 4.3.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1662620/+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 1662620] Re: "ip addr add" permits illegal labels
Hi, I come by trying to clear out a few old bugs that might still need to be resolved (or can be closed by now). Even though this one seems to be forgotten by everyone so far it has been fixed. Bionic (affected) root@b:~# ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). root@b:~# ip addr add 1.1.1.1 label eth0-test dev eth0 root@b:~# ip addr show dev eth0 | grep test inet 1.1.1.1/32 scope global eth0-test Impish (fixed) root@i:~# ip addr add 1.1.1.1 label test1 dev eth0 "label" (test1) must match "dev" (eth0) or be prefixed by "dev" with a colon. root@i:~# ip addr add 1.1.1.1 label eth0-test dev eth0 "label" (eth0-test) must match "dev" (eth0) or be prefixed by "dev" with a colon. root@i:~# ip addr show dev eth0 | grep test This was effectively fixed by https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=cad73425d8813 Which is in since v4.18.0 That version is in >=20.04 as well as in 18.04-backports. iproute2 | 3.12.0-2 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el iproute2 | 3.12.0-2ubuntu1.2 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el iproute2 | 4.3.0-1ubuntu3| xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x iproute2 | 4.3.0-1ubuntu3.16.04.5| xenial-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x iproute2 | 4.15.0-2ubuntu1 | bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x iproute2 | 4.15.0-2ubuntu1.1 | bionic-security | source, amd64, arm64, armhf, i386, ppc64el, s390x iproute2 | 4.15.0-2ubuntu1.3 | bionic-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x iproute2 | 4.18.0-1ubuntu2~ubuntu18.04.1 | bionic-backports | source, amd64, arm64, armhf, i386, ppc64el, s390x iproute2 | 5.5.0-1ubuntu1| focal| source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x iproute2 | 5.10.0-4ubuntu1 | hirsute | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x iproute2 | 5.10.0-4ubuntu1 | impish | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x Thereby the active release that still is affected is Bionic (unless you use bionic-backports which already have 4.18). I think to fix this in bionic is only prio-low since it is mostly a cosmetic. Since it is fixed in newer releases there isn't more work to be done to drive this to conclusion for future releases. @Nahuel - I can only beg your pardon that this was dormant for so long :-/ ** Also affects: iproute2 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: iproute2 (Ubuntu Bionic) Status: New => Triaged ** Changed in: iproute2 (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: iproute2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1662620 Title: "ip addr add" permits illegal labels Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Triaged Bug description: ip-address(8) manpage states: label NAME Each address may be tagged with a label string. In order to preserve compatibility with Linux-2.0 net aliases, this string must coincide with the name of the device or must be prefixed with the device name followed by colon. But you can omit the colon, "ip addr add" is ONLY checking the label is prefixed with the device: # ip addr add 1.1.1.1 label test1 dev eth0 "dev" (eth0) must match "label" (test1). # ip addr add 1.1.1.2 label eth0-test2 dev eth0 # ip addr add 1.1.1.3 label eth0:test3 dev eth0 Now ifconfig becomes confused about eth0-test2: # ifconfig eth0-test2 eth0-test2: error fetching interface information: Device not found # ifconfig eth0:test3 eth0:test3 Link encap:Ethernet HWaddr b0:d5:cc:fe:1d:7c inet addr:1.1.1.3 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:171 And daemons like ntpd also log errors about the interface with the illegal label: ntpd[7570]: eth0-test3: getting interface flags: No such device ## => many of this error per minute until: ntpd[7570]: Too many errors. Shutting up. So, I think ip addr show disallow adding address with illegal (as stated by his own documentation) labels, it must also check for the colon following the dev name. Version: 4.3.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1662620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1946341] Re: In Display Setting it is showing UnKnown Device and maximum resolution setting is set to 1024x768 and when i am requesting to update a driver it is saying Drivers ar
Thanks for the bug report. GNOME is using 1024x768 because that's the maximum resolution reported by the kernel. The kernel would report that if it is unable to detect your monitor properly. If you can, please try a different monitor cable and use a digital monitor connection. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - In Display Setting it is showing UnKnown Device and maximum resolution setting is set to 1024x768 and when i am requesting to update a driver it is saying Drivers are already updated + [i915] In Display Setting it is showing UnKnown Device and maximum resolution setting is set to 1024x768 and when i am requesting to update a driver it is saying Drivers are already updated -- 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/1946341 Title: [i915] In Display Setting it is showing UnKnown Device and maximum resolution setting is set to 1024x768 and when i am requesting to update a driver it is saying Drivers are already updated Status in linux package in Ubuntu: New Bug description: In Display Setting it is showing UnKnown Device and maximum resolution setting is set to 1024x768 and when i am requesting to update a driver it is saying Drivers are already updated ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 7 13:55:32 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [103c:339a] InstallationDate: Installed on 2021-10-07 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard HP Compaq Pro 6300 MT ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=46918b1f-e034-4313-8da7-d5df94db823e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.release: 2.90 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.asset.tag: MXL330027R dmi.board.name: 339A dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: MXL330027R dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:skuD8C62UT#ABA:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Pro 6300 MT dmi.product.sku: D8C62UT#ABA dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946341/+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 1946192] Re: "Press Ctrl+C to cancel all filesystem checks in process" on every boot
One more reasoning: fsck is called DESPITE the settings of tune2fs. By default "Maximum mount counts" equals -1 which means that fsck shouldn't run at all. If this parameter is set to some positive value fcsk should run periodically but not on every start. Less experienced users may think that they've got real problems with their disk because of these checks on every boot. -- 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/1946192 Title: "Press Ctrl+C to cancel all filesystem checks in process" on every boot Status in systemd package in Ubuntu: Confirmed Bug description: I installed Kubuntu 20.04 on Latitude 5591 laptop using flash drive. Installation run without any issues but now on every boot I notice a message "Press Ctrl+C to cancel all filesystem checks in process" on the Plymouth screen with Kubuntu logo. It flashes quickly and disappears. I've got fast NVMe drive so I cannot say for sure whether it runs any checks or not. I booted from LiveCD and performed fsck checks of all my partitions: fsck.vfat /dev/nvme0n1p1 (EFI partition) fsck.vfat /dev/nvme0n1p2 (Dell service partition, not mounted) e2fsck -f /dev/nvme0n1p3 (Root partition) e2fsck -f /dev/nvme0n1p5 (Home partition) These checks showed no problems. I changed mount counter to set periodic checks: sudo tune2fs -c 29 /dev/nvme0n1p3 sudo tune2fs -c 30 /dev/nvme0n1p5 But despite these settings this message still appears on every boot. Operating System: Kubuntu 20.04.3 Kernel Version: 5.4.0-88-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz Memory: 15,4 GiB of RAM --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: KDE DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-09 (57 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5591 Package: plymouth 0.9.4git20200323-0ubuntu6.2 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Tags: focal TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/10/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0DVVG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd06/10/2021:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5591 dmi.product.sku: 0819 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1946192/+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 1946343] [NEW] Stale os-release file after possible upgrade from 20.04.2 to 20.04.3
Public bug reported: Refer: https://answers.launchpad.net/ubuntu/+question/698949 I recently bought a Dell laptop with Ubuntu pre-installed in it. Looks like it came with Ubuntu 20.04.2 and OEM Linux Kernel in it. After my initial login (on October 1, 2021), the 'Software Updater' GUI prompted me for updates, which I went ahead with. However at the end of it, I noticed that I was still at 20.04.2 with Linux Kernel at 5.10.0-1045-oem. lsb_release -a --- No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1) Release:20.04 Codename: focal uname -a - Linux dev-linux 5.10.0-1045-oem #47-Ubuntu SMP Wed Aug 18 10:41:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Then I manually tried sudo apt update and sudo apt upgrade / dist- upgrade from the terminal, but nothing got upgraded. When I invoked the GUI 'Software Updater' again, it showed me that my system was already up-to-date. However, as 20.04.3 was released end of Aug 2021, I was expecting that I should be at that release after my initial updates. Since that didn't happen, I asked a question regarding this in askubuntu followed by launchpad https://answers.launchpad.net/ubuntu/+question/698949, thinking my update had failed for some unknown reason. However, based on some inputs from other users, we were able to narrow down the problem to /usr/lib/os-release file not having the right contents in it. Every other file including /usr/lib/os-release.oem- release, /etc/issue, /etc/issue.net specifies that I am on 20.04.3. Whereas only /usr/lib/os-release (and its symlink /etc/release) specifies my current release as 20.04.2. Even the lsb_release -a command always displays the output of /usr/lib/os-release file only. $ cat /usr/lib/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS (fossa-bulbasaur X55.1)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /usr/lib/os-release.oem-release NAME="Ubuntu" VERSION="20.04.3 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.3 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal $ cat /etc/issue Ubuntu 20.04.3 LTS \n \l $ cat /etc/issue.net Ubuntu 20.04.3 LTS If you look at the timestamp of these files, strangely os-release had a newer timestamp of Oct 1 compared to other files. $ ls -l /usr/lib/os-release -rw-r--r-- 1 root root 406 Oct 1 20:31 /usr/lib/os-release $ ls -l /usr/lib/os-release.oem-release -rw-r--r-- 1 root root 382 Aug 4 07:53 /usr/lib/os-release.oem-release $ ls -l /etc/issue -rw-r--r-- 1 root root 26 Aug 4 07:53 /etc/issue $ ls -l /etc/issue.net -rw-r--r-- 1 root root 19 Aug 4 07:53 /etc/issue.net Please note that, other software package updates, and linux kernel updates are happening automatically without any issues so far for me. Few days back even got a new kernel update. $ uname -a Linux vivek-dev-linux 5.10.0-1049-oem #51-Ubuntu SMP Mon Sep 27 11:01:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Workarounds Attempted - 1. Commented out all non-ubuntu external sources from /etc/apt/*.list. Then performed an apt clean + update + upgrade. But still nothing happened and the same issue remained. 2. Tried performing apt-install --reinstall base-files. But still nothing changed: $ sudo apt install --reinstall base-files Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 4 not upgraded. Need to get 60.6 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 base-files amd64 11ubuntu5.4 [60.6 kB] Fetched 60.6 kB in 1s (55.7 kB/s) (Reading database ... 191154 files and directories currently installed.) Preparing to unpack .../base-files_11ubuntu5.4_amd64.deb ... Warning: Stopping motd-news.service, but it can still be activated by: motd-news.timer Unpacking base-files (11ubuntu5.4) over (11ubuntu5.4) ... Setting up base-files (11ubuntu5.4) ... motd-news.service is a disabled or a static unit, not starting it. Processing triggers for cracklib-runtime (2.9.6-3.2) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.4git20200323-0ubuntu6.2) ... update-initramfs: deferring update (trigger activated) Processing triggers for install-info (6.7.0.dfsg.2-5) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for initramfs-tools (0.136ubuntu6.6) ...
[Touch-packages] [Bug 1946341] [NEW] In Display Setting it is showing UnKnown Device and maximum resolution setting is set to 1024x768 and when i am requesting to update a driver it is saying Drivers
Public bug reported: In Display Setting it is showing UnKnown Device and maximum resolution setting is set to 1024x768 and when i am requesting to update a driver it is saying Drivers are already updated ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 7 13:55:32 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [103c:339a] InstallationDate: Installed on 2021-10-07 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard HP Compaq Pro 6300 MT ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=46918b1f-e034-4313-8da7-d5df94db823e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.release: 2.90 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.asset.tag: MXL330027R dmi.board.name: 339A dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: MXL330027R dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:skuD8C62UT#ABA:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Pro 6300 MT dmi.product.sku: D8C62UT#ABA dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- 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/1946341 Title: In Display Setting it is showing UnKnown Device and maximum resolution setting is set to 1024x768 and when i am requesting to update a driver it is saying Drivers are already updated Status in xorg package in Ubuntu: New Bug description: In Display Setting it is showing UnKnown Device and maximum resolution setting is set to 1024x768 and when i am requesting to update a driver it is saying Drivers are already updated ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 7 13:55:32 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [103c:339a] InstallationDate: Installed on 2021-10-07 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard HP Compaq Pro 6300 MT ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=46918b1f-e034-4313-8da7-d5df94db823e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2013 dmi.bios.release: 2.90 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.asset.tag: MXL330027R dmi.board.name: 339A dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: MXL330027R dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:skuD8C62UT#ABA:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family:
[Touch-packages] [Bug 1659950] Re: rsync -u --inplace --partial -a can't resume transfer
Thanks Nahuel! We're doing some retriage and cleanup of old bugs, and I
stumbled on this one :-)
I linked your upstream bug report to this bug, Launchpad will keep its
status in sync. You may have noticed that I didn't set the status of
this bug to Wontfix but to Opinion ("Doesn't fit with the project, but
can be discussed"), I think it fits better.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1659950
Title:
rsync -u --inplace --partial -a can't resume transfer
Status in rsync:
Unknown
Status in rsync package in Ubuntu:
Opinion
Bug description:
Suppose you have a file in hostA:
hostA$ ls -l /tmp/files
-rw-rw-r-- 2 root root 563016 Jan 10 15:01 test.txt
You download it from the hostB using:
hostB$ rsync -u --inplace --partial -a hostA::files/* .
If the transfer is aborted, hostB will get only a partial file:
hostB$ ls -l /tmp/files
-rw-rw-r-- 2 root root 2024 Jan 11 18:00 test.txt
BUT the ctime/mtime of hostB/test.txt now is NEWER than hostA/test.txt(and
mtime == ctime). So, if you run the same rsync -u command again:
hostB$ rsync -u --inplace --partial -a hostA::files/* .
Rsync will SKIP THE FILE, because hostB/test.txt is "newer" than
hostA/test.txt. So you CAN'T resume using rsync -u command, and you
will think there are no differences.
To avoid this bug, rsync must create the file with ctime=mtime=0. And
if the file already exists before transfer, rsync -u must not change
his current ctime/mtime. Ctime/mtime must be updated ONLY after the
transfer was successfully completed.
Note this is really need because there are scenarios where checksum
comparison can't be used, only comparison by time. For example, to
avoid deleting changes made in hostB to test.txt. Also I need to use
--inplace.
To manage notifications about this bug go to:
https://bugs.launchpad.net/rsync/+bug/1659950/+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 1943964] Re: local var="$@" doesn't behave like every other system
I thought I'd illustrate the problem. Given a #!/bin/sh script like this
called tst:
#!/bin/sh
f()
{
local v="$@"
echo "<$V>"
}
f "$@"
On Debian, Fedora, FreeBSD, OpenBSD, macOS, and Solaris, the arguably incorrect
but more useful behaviour is:
> ./tst a b c
> ./tst 1 2 3
<1 2 3>
On Ubuntu, the arguably correct but less useful behaviour is:
> ./tst a b c
> ./tst 1 2 3
./tst: 4: local: 2: bad variable name
On NetBSD, the behaviour is very similar to Ubuntu's, but not identical:
> ./tst a b c
> ./tst 1 2 3
local: 2: bad variable name
<1>
It seems that "bad variable name" is a fatal error on Ubuntu, but not on
NetBSD.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/1943964
Title:
local var="$@" doesn't behave like every other system
Status in dash package in Ubuntu:
New
Bug description:
With Ubuntu (for many years), the following code in /bin/sh (i.e.
dash):
f()
{
local v="$@"
echo "<$v>"
}
f "$@"
behaves differently to /bin/sh on Debian, macOS, FreeBSD, Solaris
(/usr/xpg4/bin/sh).
The behaviour of "$@" is very special. When there are no arguments, it
completely
disappears (i.e. even the surrounding quotes disappear so that there are no
words). When
there are arguments, it replicates those arguments perfectly (i.e. it
effectively produces
multiple quoted arguments if necessary).
The described behaviour applies when "$@" is used for local variable
assignment on Ubuntu,
which sounds consistent with other uses of "$@" and therefore correct, but it
doesn't
match the behaviour on any other system, and is therefore a problem for shell
portability.
On the other systems mentioned above, the behaviour of "$@" when used as the
value of a
variable assignment (local or not) is as though "$*" had been used (i.e. it
produces a
single argument containing all the words).
The difference is clear when the arguments contain multiple words. On Ubuntu,
only
the first word is assigned to v. Any subsequent words are treated as
subsequent variable
names. This goes unnoticed if the subsequent words are valid variable
identifiers.
But if the subsequent words are not valid identifiers, then dash emits a "bad
variable name"
error message.
Note that without the "local" keyword, "$@" does behave like "$*"
(like all the other systems).
You might think that this is correct behaviour, but it is contrary to
non-local variable
assignment, and contrary to all other systems, and is therefore unhelpful.
Please change
it to behave like dash on other systems, e.g. debian.
This behaviour has been witnessed on ubuntu-16.x and ubuntu-20.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1943964/+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 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.
** Changed in: modemmanager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Apply upstream patches to fix problems for Foxconn and Quectel modems. Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Bug description: [Impact] The following 2 modems need the ModemManager v1.16.6 suite to be patched from v1.18.2 to fix some problems(LP#1943774, LP#1943780): * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested upstream patches are for these 2 specific modems and the status information. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading application can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt
** Changed in: umockdev (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
https://bugs.launchpad.net/bugs/1945321
Title:
umockdev 0.16.3-1 breaks autopkgtest of bolt
Status in bolt package in Ubuntu:
In Progress
Status in umockdev package in Ubuntu:
Invalid
Status in umockdev package in Debian:
Fix Released
Bug description:
The test of bolt fails with the new version due to a crash:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz
...
Trace/breakpoint trap (core dumped)
The bolt test really uses umockdev, d/t/control has gir1.2-umockdev-1.0 and
python3-dbusmock and the new version causes this.
Retrying autopkgtest locally with no, all and just umockdev from proposed
and it seems reproducible.
- impish-release - works
- impish-all-proposed - crashes
- impish-release + umockdev+libc6 from proposed - crashes
Repro:
$ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
FYI:
Downgrading to umockdev 0.16.2-1 in the same environment does not
eliminate the issue. So it might happen at the bolt test-build time.
Debian has the same issue in:
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bolt/15587717/log.gz
The new mockdev fails to create /sys/bus which is requested by the test.
From there the error path is what crashes, but the root cause is why we enter
the error-path in the first place.
One should be aware, this fail is "normal" if the environment is not mocked.
Even in the good case the different calls with/without umockdev lead to
exactly the same crash.
# good
$ umockdev-wrapper /usr/libexec/installed-tests/bolt/test-power
# same crash as the new version has with umockdev-wrapper
$ gdb /usr/libexec/installed-tests/bolt/test-power
This is based on ldpreload.
$ cat /usr/bin/umockdev-wrapper
#!/bin/sh
# Wrapper program to preload the libumockdev library, so that test programs
can
# set $UMOCKDEV_DIR for redirecting sysfs and other queries to a test bed.
exec env LD_PRELOAD=libumockdev-preload.so.0:$LD_PRELOAD "$@"
Gut feeling: it seems the mocking no more happens, and due to that
it runs into the non-mocked crash
Debugging with that:
$ pull-lp-source bolt
$ cd bolt-0.9.1/tests
$ gdb /usr/libexec/installed-tests/bolt/test-power
(gdb) set environment LD_PRELOAD libumockdev-preload.so.0
(gdb) b mock_sysfs_init
(gdb) run
With that we can see that while the crash is somewhere inside g_warning the
reason is in the g_mkdir failing with the new umockdev.
Good-case
Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
165 {
(gdb) n
171 ms->bed = umockdev_testbed_new ();
(gdb)
[New Thread 0x76e65640 (LWP 11444)]
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used
after threads are created
# DEBUG: umockdev.vala:104: Created udev test bed /tmp/umockdev.RQBNA1
172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
(gdb)
[New Thread 0x76664640 (LWP 11445)]
175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
(gdb)
180 sys = umockdev_testbed_get_sys_dir (ms->bed);
(gdb)
182 bus = g_build_filename (sys, "bus", NULL);
(gdb) p sys
$1 = 0x555b99a0 "/tmp/umockdev.RQBNA1/sys"
(gdb) n
183 r = g_mkdir (bus, 0744);
(gdb) p bus
$2 = 0x555be330 "/tmp/umockdev.RQBNA1/sys/bus"
(gdb) n
185 if (r < 0)
(gdb) p r
$3 = 0
(gdb) n
188 cls = g_build_filename (sys, "class", NULL);
Bad-Case
Breakpoint 1, mock_sysfs_init (ms=0x555b6400) at ../tests/mock-sysfs.c:165
165 {
(gdb) n
171 ms->bed = umockdev_testbed_new ();
(gdb)
[New Thread 0x76e65640 (LWP 17082)]
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used
after threads are created
# DEBUG: umockdev.vala:110: Created udev test bed /tmp/umockdev.TK2VA1
172 ms->domains = g_hash_table_new_full (g_str_hash, g_str_equal,
(gdb)
[New Thread 0x76664640 (LWP 17083)]
175 ms->devices = g_hash_table_new (g_str_hash, g_str_equal);
(gdb)
180 sys = umockdev_testbed_get_sys_dir (ms->bed);
(gdb)
182 bus = g_build_filename (sys, "bus", NULL);
(gdb) p sys
$1 = 0x555a98b0 "/tmp/umockdev.TK2VA1/sys"
(gdb) n
183 r = g_mkdir (bus, 0744);
(gdb) p bus
$2 = 0x555be560 "/tmp/umockdev.TK2VA1/sys/bus"
(gdb) n
185 if (r < 0)
(gdb) p r
$3 = -1
(gdb) n
186 g_warning ("could not create %s", bus);
(gdb) n
** (/usr/libexec/installed-tests/bolt/test-power:17078): WARNING **:
15:11:06.614: could not create /tmp/umockdev.TK2VA1/sys/bus
Thread 1 "test-power" received signal SIGTRAP, Trace/breakpoint trap.
I'll tag this update-excuse and FYI-subscribe Martin who has
[Touch-packages] [Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
Any updates to this SRU? What's the expected date to include this patch? -- 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/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models Status in OEM Priority Project: New Status in systemd package in Ubuntu: New Bug description: This hwdb update is to avoid unwanted screen rotation when tilting the laptop. This is the update to the previously rolled back SRU LP: #1938259 [Impact] * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerometer. [Test Plan] * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install this package and ensure the kernel is updated to the latest. * Screen should be correct side up in login screen and desktop. * Tilt the laptop and the screen should not be rotated. [Where problems could occur] * This is to add parameters for certain models in hwdb, and does not affect any other part of systemd. * Only models with the same Dell SKU would be affected. [scope] this is needed for all releases this is being added to upstream by https://github.com/systemd/systemd/pull/20314 and https://github.com/systemd/systemd/pull/20661 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+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 1946192] Re: "Press Ctrl+C to cancel all filesystem checks in process" on every boot
The brevity of the message looks like a one-frame flicker, so it looks like a bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1946192 Title: "Press Ctrl+C to cancel all filesystem checks in process" on every boot Status in systemd package in Ubuntu: Confirmed Bug description: I installed Kubuntu 20.04 on Latitude 5591 laptop using flash drive. Installation run without any issues but now on every boot I notice a message "Press Ctrl+C to cancel all filesystem checks in process" on the Plymouth screen with Kubuntu logo. It flashes quickly and disappears. I've got fast NVMe drive so I cannot say for sure whether it runs any checks or not. I booted from LiveCD and performed fsck checks of all my partitions: fsck.vfat /dev/nvme0n1p1 (EFI partition) fsck.vfat /dev/nvme0n1p2 (Dell service partition, not mounted) e2fsck -f /dev/nvme0n1p3 (Root partition) e2fsck -f /dev/nvme0n1p5 (Home partition) These checks showed no problems. I changed mount counter to set periodic checks: sudo tune2fs -c 29 /dev/nvme0n1p3 sudo tune2fs -c 30 /dev/nvme0n1p5 But despite these settings this message still appears on every boot. Operating System: Kubuntu 20.04.3 Kernel Version: 5.4.0-88-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz Memory: 15,4 GiB of RAM --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: KDE DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-09 (57 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5591 Package: plymouth 0.9.4git20200323-0ubuntu6.2 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Tags: focal TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/10/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0DVVG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd06/10/2021:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5591 dmi.product.sku: 0819 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1946192/+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 1946235] Re: pcscd won't install due to bad dependency version
Ok. This was probably a bug in the update-manager that only manifested symptoms in my case in pcscd. I noticed the only place 'hirsute' was mentioned was in /etc/apt/ is one file, /etc/apt/sources.list.d/system.sources there. Once I changed all instances of 'hirsute' to 'impish' in /etc/apt/sources.list.d/system.sources it was possible to get pcscd installed as normal. So I guess this is either solved or should be relabeled as applying to 'update-manager' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1946235 Title: pcscd won't install due to bad dependency version Status in pcsc-lite package in Ubuntu: New Bug description: # apt install pcscd Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pcscd : Depends: libpcsclite1 (= 1.9.1-1) but it is not going to be installed qemu-block-extra : Depends: qemu-system-x86 (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-arm (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-mips (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-ppc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-sparc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-misc (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-s390x (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed or qemu-system-x86-xen (= 1:6.0+dfsg-2expubuntu1) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pcscd (not installed) ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Wed Oct 6 17:15:29 2021 InstallationDate: Installed on 2020-06-16 (477 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-lite UpgradeStatus: Upgraded to impish on 2021-10-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1946235/+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 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
There is also an additional requirement. The package must install successfully and replace an existing file that would have been created manually (we had to ship the file on the image for the customer since we don't have this fix in a package yet) -- 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/1933828 Title: NTP servers from DHCP are not propagated to timesyncd Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Status in network-manager source package in Focal: New Bug description: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base 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/oem-priority/+bug/1933828/+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 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
IMHO having the fix in network-dispatcher makes more sense. -- 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/1933828 Title: NTP servers from DHCP are not propagated to timesyncd Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Status in network-manager source package in Focal: New Bug description: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base 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/oem-priority/+bug/1933828/+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 1946192] Re: "Press Ctrl+C to cancel all filesystem checks in process" on every boot
The message comes from systemd-fsckd. Though I'm not sure why it would be considered a bug that the message shows up briefly on the screen; we always call systemd-fsckd, even if it quickly determines there's no work to do and exits. ** Package changed: plymouth (Ubuntu) => systemd (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/1946192 Title: "Press Ctrl+C to cancel all filesystem checks in process" on every boot Status in systemd package in Ubuntu: Confirmed Bug description: I installed Kubuntu 20.04 on Latitude 5591 laptop using flash drive. Installation run without any issues but now on every boot I notice a message "Press Ctrl+C to cancel all filesystem checks in process" on the Plymouth screen with Kubuntu logo. It flashes quickly and disappears. I've got fast NVMe drive so I cannot say for sure whether it runs any checks or not. I booted from LiveCD and performed fsck checks of all my partitions: fsck.vfat /dev/nvme0n1p1 (EFI partition) fsck.vfat /dev/nvme0n1p2 (Dell service partition, not mounted) e2fsck -f /dev/nvme0n1p3 (Root partition) e2fsck -f /dev/nvme0n1p5 (Home partition) These checks showed no problems. I changed mount counter to set periodic checks: sudo tune2fs -c 29 /dev/nvme0n1p3 sudo tune2fs -c 30 /dev/nvme0n1p5 But despite these settings this message still appears on every boot. Operating System: Kubuntu 20.04.3 Kernel Version: 5.4.0-88-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz Memory: 15,4 GiB of RAM --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: KDE DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-09 (57 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5591 Package: plymouth 0.9.4git20200323-0ubuntu6.2 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Tags: focal TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/10/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0DVVG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd06/10/2021:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5591 dmi.product.sku: 0819 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1946192/+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 1946192] [NEW] "Press Ctrl+C to cancel all filesystem checks in process" on every boot
You have been subscribed to a public bug: I installed Kubuntu 20.04 on Latitude 5591 laptop using flash drive. Installation run without any issues but now on every boot I notice a message "Press Ctrl+C to cancel all filesystem checks in process" on the Plymouth screen with Kubuntu logo. It flashes quickly and disappears. I've got fast NVMe drive so I cannot say for sure whether it runs any checks or not. I booted from LiveCD and performed fsck checks of all my partitions: fsck.vfat /dev/nvme0n1p1 (EFI partition) fsck.vfat /dev/nvme0n1p2 (Dell service partition, not mounted) e2fsck -f /dev/nvme0n1p3 (Root partition) e2fsck -f /dev/nvme0n1p5 (Home partition) These checks showed no problems. I changed mount counter to set periodic checks: sudo tune2fs -c 29 /dev/nvme0n1p3 sudo tune2fs -c 30 /dev/nvme0n1p5 But despite these settings this message still appears on every boot. Operating System: Kubuntu 20.04.3 Kernel Version: 5.4.0-88-generic OS Type: 64-bit Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz Memory: 15,4 GiB of RAM --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: KDE DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-09 (57 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5591 Package: plymouth 0.9.4git20200323-0ubuntu6.2 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Tags: focal TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth Uname: Linux 5.4.0-88-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 06/10/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0DVVG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd06/10/2021:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5591 dmi.product.sku: 0819 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected bot-comment focal -- "Press Ctrl+C to cancel all filesystem checks in process" on every boot https://bugs.launchpad.net/bugs/1946192 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd 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
