[Touch-packages] [Bug 1925739] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1925739/+attachment/5491681/+files/PulseList.txt ** Tags removed: apport-collected ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+attachment/5491675/+files/AlsaInfo.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+attachment/5491676/+files/CurrentDmesg.txt ** Description changed: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. - --- - ProblemType: Bug - ApportVersion: 2.20.11-0ubuntu50.5 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: bapi 1427 F pulseaudio - CasperMD5CheckResult: skip - CurrentDesktop: ubuntu:GNOME - DistroRelease: Ubuntu 20.10 - InstallationDate: Installed on 2021-04-22 (1 days ago) - InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) - NonfreeKernelModules: nvidia_modeset nvidia - Package: pulseaudio 1:13.99.2-1ubuntu2.3 - PackageArchitecture: amd64 - ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 - Tags: groovy - Uname: Linux 5.8.0-50-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo - _MarkForUpload: True - dmi.bios.date: 09/30/2020 - dmi.bios.release: 1.14 - dmi.bios.vendor: Dell Inc. - dmi.bios.version: 1.14.1 - dmi.board.name: 0VFD52 - dmi.board.vendor: Dell Inc. - dmi.board.version: A00 - dmi.chassis.type: 3 - dmi.chassis.vendor: Dell Inc. - dmi.modalias: dmi:bvnDellInc.:bvr1.14.1:bd09/30/2020:br1.14:svnDellInc.:pnVostro3668:pvr:rvnDellInc.:rn0VFD52:rvrA00:cvnDellInc.:ct3:cvr: - dmi.product.family: Vostro - dmi.product.name: Vostro 3668 - dmi.product.sku: 0760 - dmi.sys.vendor: Dell Inc. ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+attachment/5491677/+files/Dependencies.txt ** Attachment removed: "PaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+attachment/5491678/+files/PaInfo.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+attachment/5491679/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+attachment/5491680/+files/ProcEnviron.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+attachment/5491681/+files/PulseList.txt -- 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/1925739 Title: Strange sound when speaker is muted Status in pulseaudio package in Ubuntu: Incomplete Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+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 1925739] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1925739/+attachment/5491680/+files/ProcEnviron.txt -- 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/1925739 Title: Strange sound when speaker is muted Status in pulseaudio package in Ubuntu: Incomplete Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+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 1925739] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1925739/+attachment/5491679/+files/ProcCpuinfoMinimal.txt -- 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/1925739 Title: Strange sound when speaker is muted Status in pulseaudio package in Ubuntu: Incomplete Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+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 1925739] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1925739/+attachment/5491678/+files/PaInfo.txt -- 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/1925739 Title: Strange sound when speaker is muted Status in pulseaudio package in Ubuntu: Incomplete Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+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 1925739] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1925739/+attachment/5491677/+files/Dependencies.txt -- 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/1925739 Title: Strange sound when speaker is muted Status in pulseaudio package in Ubuntu: Incomplete Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+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 1925739] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1925739/+attachment/5491676/+files/CurrentDmesg.txt -- 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/1925739 Title: Strange sound when speaker is muted Status in pulseaudio package in Ubuntu: Incomplete Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+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 1925739] Re: Strange sound when speaker is muted
apport information ** Tags added: apport-collected groovy ** Description changed: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: bapi 1427 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2021-04-22 (1 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + NonfreeKernelModules: nvidia_modeset nvidia + Package: pulseaudio 1:13.99.2-1ubuntu2.3 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 + Tags: groovy + Uname: Linux 5.8.0-50-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/30/2020 + dmi.bios.release: 1.14 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.14.1 + dmi.board.name: 0VFD52 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 3 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.14.1:bd09/30/2020:br1.14:svnDellInc.:pnVostro3668:pvr:rvnDellInc.:rn0VFD52:rvrA00:cvnDellInc.:ct3:cvr: + dmi.product.family: Vostro + dmi.product.name: Vostro 3668 + dmi.product.sku: 0760 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1925739/+attachment/5491675/+files/AlsaInfo.txt -- 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/1925739 Title: Strange sound when speaker is muted Status in pulseaudio package in Ubuntu: Incomplete Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+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 1916485] Re: test -x fails inside shell scripts in containers
Dan, let me know if you need help driving the Linux kernel SRU forward. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: New Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for
[Touch-packages] [Bug 1925973] Re: Nvidia driver 450.119 crashes lxpanel on Ubuntu 18.04
** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1925973 Title: Nvidia driver 450.119 crashes lxpanel on Ubuntu 18.04 Status in xorg package in Ubuntu: Invalid Bug description: Running Ubuntu 18.04 with the LXDE desktop. After installing the Nvidia driver version 450.119 and rebooting, the LXDE desktop crashes, specifically lxpanel. Reloaded clonezilla clone of / with Nvidia driver 450.102, all is well again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-72.80~18.04.1-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.102.04 Tue Dec 29 06:51:23 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: LXDE Date: Fri Apr 23 15:46:27 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 450.102.04, 5.4.0-67-generic, x86_64: installed nvidia, 450.102.04, 5.4.0-70-generic, x86_64: installed nvidia, 450.102.04, 5.4.0-72-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6253] InstallationDate: Installed on 2018-04-27 (1092 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=UUID=0ca22edb-e6b0-412b-ad6e-00b2126b37c7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: M11AD dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1925973/+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 1925761] Re: libnns-mymachines update breaks local mdns discovery
> there's a really large delta between that and 245.4-ubuntu3.6, and you very probably were running 245.4-ubuntu3.5 before, not 245.4-ubuntu3. Yes I know, but I don't know any easy way to downgrade to 3.5, there is only choice between 3 and 3.6. Full journalctl or only specific service ? -- 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/1925761 Title: libnns-mymachines update breaks local mdns discovery Status in systemd package in Ubuntu: Incomplete Bug description: After the last systemd update 245.4-ubuntu3.6 on 20.04 focal, I discovered I couldn't use .local network names anymore. All returning Name or service unknown. Nothing explicitly showing a problem in avahi-deamon systemd logs, no firewall activated, and no changes done to /etc/nsswitch.conf. After noticing those packages just had been updated, I downgraded systemd to 245.4-ubuntu3 through aptitude and it works again. So I'm pretty sure something's wrong with last package from focal-updates of libnss-mymachines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925761/+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 1925973] [NEW] Nvidia driver 450.119 crashes lxpanel on Ubuntu 18.04
Public bug reported: Running Ubuntu 18.04 with the LXDE desktop. After installing the Nvidia driver version 450.119 and rebooting, the LXDE desktop crashes, specifically lxpanel. Reloaded clonezilla clone of / with Nvidia driver 450.102, all is well again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-72.80~18.04.1-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.102.04 Tue Dec 29 06:51:23 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: LXDE Date: Fri Apr 23 15:46:27 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 450.102.04, 5.4.0-67-generic, x86_64: installed nvidia, 450.102.04, 5.4.0-70-generic, x86_64: installed nvidia, 450.102.04, 5.4.0-72-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6253] InstallationDate: Installed on 2018-04-27 (1092 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=UUID=0ca22edb-e6b0-412b-ad6e-00b2126b37c7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: M11AD dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu ** Description changed: Running Ubuntu 18.04 with the LXDE desktop. - After installing the Nvidia driver version 150.119 and rebooting, the + After installing the Nvidia driver version 450.119 and rebooting, the LXDE desktop crashes, specifically lxpanel. Reloaded clonezilla clone of / with Nvidia driver 150.102, all is well again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-72.80~18.04.1-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.102.04 Tue Dec 29 06:51:23 UTC 2020 - GCC version: gcc version 7.5.0 (Ubuntu 7.5.
[Touch-packages] [Bug 1925761] Re: libnns-mymachines update breaks local mdns discovery
> I downgraded systemd to 245.4-ubuntu3 there's a really large delta between that and 245.4-ubuntu3.6, and you very probably were running 245.4-ubuntu3.5 before, not 245.4-ubuntu3. In any case, we'll need more data to look at your problem, can you attach at least your journalctl output from the time when the problem happened ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925761 Title: libnns-mymachines update breaks local mdns discovery Status in systemd package in Ubuntu: Incomplete Bug description: After the last systemd update 245.4-ubuntu3.6 on 20.04 focal, I discovered I couldn't use .local network names anymore. All returning Name or service unknown. Nothing explicitly showing a problem in avahi-deamon systemd logs, no firewall activated, and no changes done to /etc/nsswitch.conf. After noticing those packages just had been updated, I downgraded systemd to 245.4-ubuntu3 through aptitude and it works again. So I'm pretty sure something's wrong with last package from focal-updates of libnss-mymachines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925761/+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 1925839] Re: Switching between windows by using the "windows" key produce an infinite loop
And here how its look like ** Attachment removed: "Screenshot from 2021-04-23 19-20-10.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1925839/+attachment/5491506/+files/Screenshot%20from%202021-04-23%2019-20-10.png ** Attachment added: "Screenshot from 2021-04-23 20-41-31.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1925839/+attachment/5491553/+files/Screenshot%20from%202021-04-23%2020-41-31.png ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1925839 Title: Switching between windows by using the "windows" key produce an infinite loop Status in xorg package in Ubuntu: New Bug description: Switching between windows using the "windows" key produce an infinite loop. Steps to reproduce: - Open couple applications - Push "Windows" button to "change focus" between windows - Try to select any of opened application by touch-pad or mouse As result each of application becomes unavailable ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 19:23:16 2021 DistUpgraded: 2021-04-23 17:38:56,574 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:39cc] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:39cc] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 002: ID 04f2:b5d9 Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81BQ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=a43f160c-59d4-4e88-bc60-a565d919bf57 ro nouveau.modeset=0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-04-23 (0 days ago) dmi.bios.date: 11/19/2019 dmi.bios.release: 2.51 dmi.bios.vendor: LENOVO dmi.bios.version: 4QCN51WW(V2.15) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320S-15IKB dmi.ec.firmware.release: 2.51 dmi.modalias: dmi:bvnLENOVO:bvr4QCN51WW(V2.15):bd11/19/2019:br2.51:efr2.51:svnLENOVO:pn81BQ:pvrLenovoideapad320S-15IKB:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad320S-15IKB: dmi.product.family: ideapad 320S-15IKB dmi.product.name: 81BQ dmi.product.sku: LENOVO_MT_81BQ_BU_idea_FM_ideapad 320S-15IKB dmi.product.version: Lenovo ideapad 320S-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 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 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/xorg/+bug/1925839/+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 1925833] Re: apt-transport-https reparses URLs, breaking CloudFront signing
Great, thanks for sharing both answers. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1925833 Title: apt-transport-https reparses URLs, breaking CloudFront signing Status in apt package in Ubuntu: Fix Released Bug description: CloudFront URL signing requires that the the whole URL matches the signature, as compared to S3 URLs which prune the querystring before validating the signature. The URL re-parsing which I'm pretty sure was introduced in resolving #1651923 decodes some HTML entities which were encoded before signing. That invalidates the signature and results in permission denied errors. In my case, the equal and semicolon chars from the return-content-disposition header are being decoded, but it applies to any entity which is "optionally" encoded. Personally, I think that the URL returned in a Location: redirect header should be handled as-is, and if some piece of garbage http server is generating redirects which contain spaces or are otherwise invalid, the problem lies with the web server generating invalid redirects and not in apt failing to follow broken URLs. I say that knowing full well that the http spec says those things should be identical, so CloudFront also falls into the general "garbage" category by breaking the spec by requiring a specific format for identical characters. Either way, things are what they are. Rather than unnecessarily fully reencoding the URL, I'd suggest that apt-transport-https (and presumably the http transport as well, but I don't know) should at most just replace the spaces with plusses or %20s to keep the original bug resolved without breaking other stuff. :) PS: I tried to report this against the apt-transport-https package, but the bug tool says that doesn't exist in Ubuntu. That's weird, considering it's definitely a package (https://packages.ubuntu.com/groovy/apt-transport-https), so I assume the apt maintainer will know how to triage. Sorry. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1925833/+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 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi
> Thanks for the details. You did address the part about upstreaming the change to Debian. How important is that notification in practice? If feels like we should have bluez preinstall on the raspi images if that's not the case, and if it's pre-install is that really worth the packaging overhead to have to carry a delta over Debian? Just to give a bit of context here, the bluetooth situation on the pi is somewhat complicated and there's compromises that we make between the desktop and server images: The bluetooth module on the Pi is controlled via a UART. Two UARTs are available on the Pi (there's more on the Pi 4, but it's the same situation for the bits we're talking about here): * the PL011 which is full featured (buffers, flow-control, etc.), and * the mini-UART which is ... not. Furthermore, the mini-UART's baud rate is tied to the GPU's clock, so if that floats then the mini-UART's baud rate floats too On models of Pi with a bluetooth module (everything except the Pi 2, the CM3/3+ and some models of the CM4), the PL011 is used to talk to the bluetooth module and by default the mini-UART is disabled. This is the configuration we use on the desktop images as we make the assumption a serial console is less important on something which almost certainly has a monitor, and this configuration permits the GPU clock to float (important for something relying upon graphical acceleration). On the server images, we assume that the serial console *is* important, and so this is enabled by default. We don't *disable* the bluetooth module, but we don't pre-install the packages for it either. This means that the PL011 is tied to the bluetooth module by default (but unused), and the mini-UART to the serial console. Because the mini-UART is in use, the GPU's clock is locked to the base speed. This is a compromise because all the alternatives are nastier in some way for some of the typical use cases: * If the server image is used without a graphical environment, and without bluetooth, this is fine (this is the default). The GPU's clock doesn't really matter in this scenario and the serial console will still work reliably. * If the server image is used without a graphical environment, but with bluetooth, all the user needs to do is install pi-bluetooth and reboot (personally I don't think the reboot warning is terribly necessary; like knowing to install pi-bluetooth in the first place, it's fairly widespread knowledge and tends to be part of first-time setup steps anyway). This again leaves the GPU's clock locked (but without a graphical environment that doesn't really matter), the serial console still works, and bluetooth works. * If the server image is used with a graphical environment, without bluetooth, the user needs to either disable the serial console (if they don't want it, this is a one-line change in the boot configuration), or alternatively add the line "dtoverlay=disable-bt" to the boot configuration which disables the bluetooth module entirely, allowing the serial console to use the "full" PL011 UART. Either option unlocks the GPU's clock. * If the server image is used with a graphical environment, with bluetooth, that's effectively the same as the desktop setup and we assume that in this scenario the user would disable the serial console (which means the mini-UART is no longer used and the GPU's clock can float again); again, a one-line change in the boot configuration. So the compromise is to ship an image which, with either zero steps or one step can be moved to one of the scenarios above, with hardware working acceptably for that scenario. We could default to, for example, shipping the server image with both serial console *and* bluetooth enabled, but that complicates moving to a GPU clock unlocked scenario as it involves either disabling the serial console (easy) or removing bluetooth (quite a bit harder, especially if the pi-bluetooth package is now depended on by a meta-package, and also still involves disabling the hardware module with the dtoverlay). Anyway, for the above reasons I don't foresee that we're likely to ship bluetooth enabled server images anytime soon. As to how necessary a reboot warning is -- I'd consider it "nice to have but by no means critical" (it's not hardware enablement after all). If we want to keep the delta minimal, I've no objections. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1922792 Title: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi Status in bluez package in Ubuntu: In Progress Status in bluez package in Debian: New Bug description: In the case of upgrading or installing bluez for the first time on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug
[Touch-packages] [Bug 1925833] Re: apt-transport-https reparses URLs, breaking CloudFront signing
This has been fixed in 2.1.15 and newer versions, so starting with hirsute. As the change is too invasive, it has not been backported to older releases. ** Changed in: apt (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1925833 Title: apt-transport-https reparses URLs, breaking CloudFront signing Status in apt package in Ubuntu: Fix Released Bug description: CloudFront URL signing requires that the the whole URL matches the signature, as compared to S3 URLs which prune the querystring before validating the signature. The URL re-parsing which I'm pretty sure was introduced in resolving #1651923 decodes some HTML entities which were encoded before signing. That invalidates the signature and results in permission denied errors. In my case, the equal and semicolon chars from the return-content-disposition header are being decoded, but it applies to any entity which is "optionally" encoded. Personally, I think that the URL returned in a Location: redirect header should be handled as-is, and if some piece of garbage http server is generating redirects which contain spaces or are otherwise invalid, the problem lies with the web server generating invalid redirects and not in apt failing to follow broken URLs. I say that knowing full well that the http spec says those things should be identical, so CloudFront also falls into the general "garbage" category by breaking the spec by requiring a specific format for identical characters. Either way, things are what they are. Rather than unnecessarily fully reencoding the URL, I'd suggest that apt-transport-https (and presumably the http transport as well, but I don't know) should at most just replace the spaces with plusses or %20s to keep the original bug resolved without breaking other stuff. :) PS: I tried to report this against the apt-transport-https package, but the bug tool says that doesn't exist in Ubuntu. That's weird, considering it's definitely a package (https://packages.ubuntu.com/groovy/apt-transport-https), so I assume the apt maintainer will know how to triage. Sorry. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1925833/+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 1925833] Re: apt-transport-https reparses URLs, breaking CloudFront signing
WRT your other comment: apt-transport-https is a binary package, launchpad bugs are against source packages. Also apt-transport-https is an empty transitional package, there is no separate https method anymore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1925833 Title: apt-transport-https reparses URLs, breaking CloudFront signing Status in apt package in Ubuntu: Fix Released Bug description: CloudFront URL signing requires that the the whole URL matches the signature, as compared to S3 URLs which prune the querystring before validating the signature. The URL re-parsing which I'm pretty sure was introduced in resolving #1651923 decodes some HTML entities which were encoded before signing. That invalidates the signature and results in permission denied errors. In my case, the equal and semicolon chars from the return-content-disposition header are being decoded, but it applies to any entity which is "optionally" encoded. Personally, I think that the URL returned in a Location: redirect header should be handled as-is, and if some piece of garbage http server is generating redirects which contain spaces or are otherwise invalid, the problem lies with the web server generating invalid redirects and not in apt failing to follow broken URLs. I say that knowing full well that the http spec says those things should be identical, so CloudFront also falls into the general "garbage" category by breaking the spec by requiring a specific format for identical characters. Either way, things are what they are. Rather than unnecessarily fully reencoding the URL, I'd suggest that apt-transport-https (and presumably the http transport as well, but I don't know) should at most just replace the spaces with plusses or %20s to keep the original bug resolved without breaking other stuff. :) PS: I tried to report this against the apt-transport-https package, but the bug tool says that doesn't exist in Ubuntu. That's weird, considering it's definitely a package (https://packages.ubuntu.com/groovy/apt-transport-https), so I assume the apt maintainer will know how to triage. Sorry. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1925833/+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 1925381] Re: rsync conceals file deletions from reporting when --dry-run --remove-source-files are used together
s/Invalid/Won't Fix/g. -- 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/1925381 Title: rsync conceals file deletions from reporting when --dry-run --remove- source-files are used together Status in rsync package in Ubuntu: Won't Fix Bug description: Rsync has an astonishing and dangerous bug: The dry run feature (-n / --dry-run) inhibits reporting of file deletions when --remove-source-files is used. This is quite serious. People use --dry-run to see if an outcome will work as expected before a live run. When the simulated run shows *less* destruction than the live run, the consequences can be serious because rsync may unexpectedly destroy the only copy(*) of a file. Users rely on --dry-run. Although users probably expect --dry-run to have limitations, we don't expect destructive operations to be under reported. If it were reversed, such that the live run were less destructive than the dry run, this wouldn't be as serious. Reproducer: $ mkdir -p /tmp/src /tmp/dest $ printf '%s\n' 'yada yada' > /tmp/src/foo.txt $ printf '%s\n' 'yada yada' > /tmp/src/bar.txt $ cp /tmp/src/foo.txt /tmp/dest $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt foo.txt $ rsync -na --info=remove1 --remove-source-files --existing src/* dest/ (no output) $ rsync -a --info=remove1 --remove-source-files --existing src/* dest/ sender removed foo.txt $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt (*) note when I say it can destroy the only copy of a file, another circumstance is needed: that is, rsync does not do a checksum by default. It checks for identical files based on superficial parameters like name and date. So it's possible that two files match in the default superficial comparison but differ in the actual content. Losing a unique file in this scenario is perhaps a rare corner case, but this bug should be fixed nonetheless. In the typical case of losing files at the source, there is still a significant inconvenience of trying to identify what files to copy back. Note this bug is similar but differs in a few ways: https://bugzilla.samba.org/show_bug.cgi?id=3844 I've marked this as a security vulnerability because it causes unexpected data loss due to --dry-run creating a false expectation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1925381/+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 1925381] Re: rsync conceals file deletions from reporting when --dry-run --remove-source-files are used together
Hi Bill, Such bugs are worth reporting upstream and once they're fixed there, we can pick it from there and provide it via the packages we ship, as exactly what Paride mentioned. Since you don't want to open an issue upstream, maybe you'd like to use their mailing lists? cf: https://rsync.samba.org/lists.html That said, I am marking this as "Invalid" here because of the above reasons. Thanks! ** Changed in: rsync (Ubuntu) Status: Triaged => Invalid ** Changed in: rsync (Ubuntu) Status: Invalid => Won't Fix -- 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/1925381 Title: rsync conceals file deletions from reporting when --dry-run --remove- source-files are used together Status in rsync package in Ubuntu: Won't Fix Bug description: Rsync has an astonishing and dangerous bug: The dry run feature (-n / --dry-run) inhibits reporting of file deletions when --remove-source-files is used. This is quite serious. People use --dry-run to see if an outcome will work as expected before a live run. When the simulated run shows *less* destruction than the live run, the consequences can be serious because rsync may unexpectedly destroy the only copy(*) of a file. Users rely on --dry-run. Although users probably expect --dry-run to have limitations, we don't expect destructive operations to be under reported. If it were reversed, such that the live run were less destructive than the dry run, this wouldn't be as serious. Reproducer: $ mkdir -p /tmp/src /tmp/dest $ printf '%s\n' 'yada yada' > /tmp/src/foo.txt $ printf '%s\n' 'yada yada' > /tmp/src/bar.txt $ cp /tmp/src/foo.txt /tmp/dest $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt foo.txt $ rsync -na --info=remove1 --remove-source-files --existing src/* dest/ (no output) $ rsync -a --info=remove1 --remove-source-files --existing src/* dest/ sender removed foo.txt $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt (*) note when I say it can destroy the only copy of a file, another circumstance is needed: that is, rsync does not do a checksum by default. It checks for identical files based on superficial parameters like name and date. So it's possible that two files match in the default superficial comparison but differ in the actual content. Losing a unique file in this scenario is perhaps a rare corner case, but this bug should be fixed nonetheless. In the typical case of losing files at the source, there is still a significant inconvenience of trying to identify what files to copy back. Note this bug is similar but differs in a few ways: https://bugzilla.samba.org/show_bug.cgi?id=3844 I've marked this as a security vulnerability because it causes unexpected data loss due to --dry-run creating a false expectation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1925381/+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 1919255] Re: tracker-store crashed with signal 5
FWIW I get this bug in Hirsute every time I boot up my machine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1919255 Title: tracker-store crashed with signal 5 Status in tracker package in Ubuntu: Confirmed Bug description: This just happened... ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Mon Mar 15 17:47:12 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (15 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1919255/+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 1925839] [NEW] Switching between windows by using the "windows" key produce an infinite loop
Public bug reported: Switching between windows using the "windows" key produce an infinite loop. Steps to reproduce: - Open couple applications - Push "Windows" button to "change focus" between windows - Try to select any of opened application by touch-pad or mouse As result each of application becomes unavailable ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 19:23:16 2021 DistUpgraded: 2021-04-23 17:38:56,574 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:39cc] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:39cc] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 002: ID 04f2:b5d9 Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81BQ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=a43f160c-59d4-4e88-bc60-a565d919bf57 ro nouveau.modeset=0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-04-23 (0 days ago) dmi.bios.date: 11/19/2019 dmi.bios.release: 2.51 dmi.bios.vendor: LENOVO dmi.bios.version: 4QCN51WW(V2.15) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320S-15IKB dmi.ec.firmware.release: 2.51 dmi.modalias: dmi:bvnLENOVO:bvr4QCN51WW(V2.15):bd11/19/2019:br2.51:efr2.51:svnLENOVO:pn81BQ:pvrLenovoideapad320S-15IKB:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad320S-15IKB: dmi.product.family: ideapad 320S-15IKB dmi.product.name: 81BQ dmi.product.sku: LENOVO_MT_81BQ_BU_idea_FM_ideapad 320S-15IKB dmi.product.version: Lenovo ideapad 320S-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 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 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/1925839 Title: Switching between windows by using the "windows" key produce an infinite loop Status in xorg package in Ubuntu: New Bug description: Switching between windows using the "windows" key produce an infinite loop. Steps to reproduce: - Open couple applications - Push "Windows" button to "change focus" between windows - Try to select any of opened application by touch-pad or mouse As result each of application becomes unavailable ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 19:23:16 2021 DistUpgraded: 2021-04-23 17:38:56,574 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:39cc] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:39cc] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 002: ID 04f2:b5d9 Chicony Electronics Co., Ltd EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81BQ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=a43f160c-59d4-4e88-bc60-a565d919bf57 ro nouveau.modeset=0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-04-23 (0 days ago) dmi.bios.date: 11/19/2019 dmi.bios.release: 2.51
[Touch-packages] [Bug 1919255] Re: tracker-store crashed with signal 5
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tracker (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1919255 Title: tracker-store crashed with signal 5 Status in tracker package in Ubuntu: Confirmed Bug description: This just happened... ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Mon Mar 15 17:47:12 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (15 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1919255/+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 1925827] Re: [v247] backport routing policy rule fix
The attachment "96.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925827 Title: [v247] backport routing policy rule fix Status in systemd package in Ubuntu: New Bug description: The original issue can be found at https://github.com/systemd/systemd/issues/18107. I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) against v247-stable branch, which got merged and released in v247.4. However due to the freezing state of Debian bullseye, upstream systemd package is frozen at v247.3. Please apply this patchset for Ubuntu if possible. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925827/+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 1925833] [NEW] apt-transport-https reparses URLs, breaking CloudFront signing
Public bug reported: CloudFront URL signing requires that the the whole URL matches the signature, as compared to S3 URLs which prune the querystring before validating the signature. The URL re-parsing which I'm pretty sure was introduced in resolving #1651923 decodes some HTML entities which were encoded before signing. That invalidates the signature and results in permission denied errors. In my case, the equal and semicolon chars from the return-content-disposition header are being decoded, but it applies to any entity which is "optionally" encoded. Personally, I think that the URL returned in a Location: redirect header should be handled as-is, and if some piece of garbage http server is generating redirects which contain spaces or are otherwise invalid, the problem lies with the web server generating invalid redirects and not in apt failing to follow broken URLs. I say that knowing full well that the http spec says those things should be identical, so CloudFront also falls into the general "garbage" category by breaking the spec by requiring a specific format for identical characters. Either way, things are what they are. Rather than unnecessarily fully reencoding the URL, I'd suggest that apt-transport-https (and presumably the http transport as well, but I don't know) should at most just replace the spaces with plusses or %20s to keep the original bug resolved without breaking other stuff. :) PS: I tried to report this against the apt-transport-https package, but the bug tool says that doesn't exist in Ubuntu. That's weird, considering it's definitely a package (https://packages.ubuntu.com/groovy/apt-transport-https), so I assume the apt maintainer will know how to triage. Sorry. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1925833 Title: apt-transport-https reparses URLs, breaking CloudFront signing Status in apt package in Ubuntu: New Bug description: CloudFront URL signing requires that the the whole URL matches the signature, as compared to S3 URLs which prune the querystring before validating the signature. The URL re-parsing which I'm pretty sure was introduced in resolving #1651923 decodes some HTML entities which were encoded before signing. That invalidates the signature and results in permission denied errors. In my case, the equal and semicolon chars from the return-content-disposition header are being decoded, but it applies to any entity which is "optionally" encoded. Personally, I think that the URL returned in a Location: redirect header should be handled as-is, and if some piece of garbage http server is generating redirects which contain spaces or are otherwise invalid, the problem lies with the web server generating invalid redirects and not in apt failing to follow broken URLs. I say that knowing full well that the http spec says those things should be identical, so CloudFront also falls into the general "garbage" category by breaking the spec by requiring a specific format for identical characters. Either way, things are what they are. Rather than unnecessarily fully reencoding the URL, I'd suggest that apt-transport-https (and presumably the http transport as well, but I don't know) should at most just replace the spaces with plusses or %20s to keep the original bug resolved without breaking other stuff. :) PS: I tried to report this against the apt-transport-https package, but the bug tool says that doesn't exist in Ubuntu. That's weird, considering it's definitely a package (https://packages.ubuntu.com/groovy/apt-transport-https), so I assume the apt maintainer will know how to triage. Sorry. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1925833/+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 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.
This fix breaks CloudFront URLs, because the reencoding of URLs results in some HTML entities being replaced by their plain characters. CloudFront signing requires that the the whole URL matches the signature, as compared to S3 URLs which prune the querystring before validating the signature. That explains why this fix worked ok on S3. I'll open a new bug since this is so old that reopening doesn't make sense, but also making a note here for future web search purposes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1651923 Title: apt https method decodes redirect locations and sends them to the destination undecoded. Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Yakkety: Fix Released Bug description: [Impact] Downloads via HTTPS fail if the URL contains a space (before yakkety only if there is no redirect from a previous space-free https URL). This breaks packages like ttf-mscorefonts-installer and various third party hosters. [Test case] Install/Upgrade apt-transport-https, that's where the fix is. Check that /usr/lib/apt/apt-helper download-file http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb test.deb can successfully download the file (or at least start downloading it) and does not fail early with a 505 HTTP version not supported error message. This problem does not occur with that file on xenial, as it first redirects to an https URI without a space which then redirects to an HTTPS uri with a space (http w/o space -> https w/o space -> https w/ space). In xenial, https->https redirects where handled internally by curl. Another test (applicable to xenial) is to install ttf-mscorefonts- installer. [Regression potential] The added code is: Uri.Path = QuoteString(Uri.Path, "+~ "); Some servers might not like + or ~ being quoted. We use the same quoting call for the http method too, though, so it seems highly unlikely to cause an issue. [Original bug report] Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety apt version 1.3.3 (also tried 1.4-beta2 .deb, same results) When trying to install a package hosted on s3 from the kxstudio repo, the download fails with an HTTP error: nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: wine1.6-amd64 The following NEW packages will be installed wine1.6-amd64 wineasio-amd64 0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade. Need to get 30.9 kB/32.6 kB of archives. After this operation, 184 kB of additional disk space will be used. Do you want to continue? [Y/n] y Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 amd64 0.9.0+git20110613-2kxstudio3 505 HTTP Version not supported E: Failed to fetch https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment; filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream 505 HTTP Version not supported E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? Error allegedly not present in Ubuntu 14.04 and 16.04 More details in these forum posts: https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503 https://www.linuxmusicians.com/viewtopic.php?t=16056 https://www.drupal.org/node/2324991 (clues on root cause) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apt 1.3.3 ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6 Uname: Linux 4.8.0-30-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Dec 22 02:31:47 2016 InstallationDate: Installed on 2016-10-20 (62 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1651923/+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 1925824] Re: Display Error (hardware bug: Screen doesnt display on warm boot and turning on after Suspend)
I also change the display scale to 125% in display section in ubuntu setting -- 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/1925824 Title: Display Error (hardware bug: Screen doesnt display on warm boot and turning on after Suspend) Status in xorg package in Ubuntu: New Bug description: I have Avita NS14A2 laptop where i dual boot windows 10 and Ubuntu 20.04. In past few days might be after installing updates I am facing issue where my screen dont display at all when i first boot it and after multiple force shut down and then boot in it work, even on doing Suspend and then opening it, screen didnt not display for about 5-6 minutes, and then shows login screen. On checking logs software i got these line on those time stamp when display doesnt shows this is the line: (Hardware) i915 :00:02.0: [drm] *ERROR* failed to enable link training this line continues for about 30-40 times on average during time when screen doesnt display anything on turing on. So I think there is some issue with it. As I primarily use Ubuntu 20.04 so didnt check it with windows 10 but on doing cold boot it didnt even shows the boot menu where i can choose between Ubuntu 20.04 and Windows 10. But once screen starts displaying i dont see that error in logs software anymore and screen doesnt freezes or hangs. It only happen when i either open after suspend or do cold boot. Please consider this issue on urgent basis, as it takes a lot of time and efforts to make screen display something. :( And please let me know whether I should do fresh installation of ubuntu 20.04 again. Sorry for any grammatical mistakes. :) Thank you, Bipul Harsh bipulharsh...@gmail.com ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 20:36:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation UHD Graphics 620 [8086:5917] InstallationDate: Installed on 2020-11-22 (151 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: AVITA NS14A2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=011d61ba-ef72-40ed-9957-25830622d9c7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2019 dmi.bios.release: 0.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BSR5IPHK-14UF80-AVI-V22 dmi.board.asset.tag: Default string dmi.board.name: 6614UFWC80 dmi.board.vendor: AVITA dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: AVITA dmi.chassis.version: Default string dmi.ec.firmware.release: 0.22 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBSR5IPHK-14UF80-AVI-V22:bd04/19/2019:br0.22:efr0.22:svnAVITA:pnNS14A2:pvrDefaultstring:rvnAVITA:rn6614UFWC80:rvrDefaultstring:cvnAVITA:ct10:cvrDefaultstring: dmi.product.family: CN6614 dmi.product.name: NS14A2 dmi.product.sku: CN6614F56U1IN-MB dmi.product.version: Default string dmi.sys.vendor: AVITA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/xorg/+bug/1925824/+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 1925827] [NEW] [v247] backport routing policy rule fix
Public bug reported: The original issue can be found at https://github.com/systemd/systemd/issues/18107. I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) against v247-stable branch, which got merged and released in v247.4. However due to the freezing state of Debian bullseye, upstream systemd package is frozen at v247.3. Please apply this patchset for Ubuntu if possible. Thanks. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: systemd-networkd ** Patch added: "96.patch" https://bugs.launchpad.net/bugs/1925827/+attachment/5491460/+files/96.patch ** Description changed: The original issue can be found at https://github.com/systemd/systemd/issues/18107. - I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) against v247-stable branch, which get merged and released in v247.4. + I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) against v247-stable branch, which got merged and released in v247.4. However due to the freezing state of Debian bullseye, upstream systemd package is frozen at v247.3. Please apply this patchset for Ubuntu if possible. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925827 Title: [v247] backport routing policy rule fix Status in systemd package in Ubuntu: New Bug description: The original issue can be found at https://github.com/systemd/systemd/issues/18107. I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) against v247-stable branch, which got merged and released in v247.4. However due to the freezing state of Debian bullseye, upstream systemd package is frozen at v247.3. Please apply this patchset for Ubuntu if possible. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925827/+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 1925824] Re: Display Error (hardware bug: Screen doesnt display on warm boot and turning on after Suspend)
One more thing if the logs containing any sensitive information please do let me know so i can remove those file. Thank You -- 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/1925824 Title: Display Error (hardware bug: Screen doesnt display on warm boot and turning on after Suspend) Status in xorg package in Ubuntu: New Bug description: I have Avita NS14A2 laptop where i dual boot windows 10 and Ubuntu 20.04. In past few days might be after installing updates I am facing issue where my screen dont display at all when i first boot it and after multiple force shut down and then boot in it work, even on doing Suspend and then opening it, screen didnt not display for about 5-6 minutes, and then shows login screen. On checking logs software i got these line on those time stamp when display doesnt shows this is the line: (Hardware) i915 :00:02.0: [drm] *ERROR* failed to enable link training this line continues for about 30-40 times on average during time when screen doesnt display anything on turing on. So I think there is some issue with it. As I primarily use Ubuntu 20.04 so didnt check it with windows 10 but on doing cold boot it didnt even shows the boot menu where i can choose between Ubuntu 20.04 and Windows 10. But once screen starts displaying i dont see that error in logs software anymore and screen doesnt freezes or hangs. It only happen when i either open after suspend or do cold boot. Please consider this issue on urgent basis, as it takes a lot of time and efforts to make screen display something. :( And please let me know whether I should do fresh installation of ubuntu 20.04 again. Sorry for any grammatical mistakes. :) Thank you, Bipul Harsh bipulharsh...@gmail.com ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 20:36:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation UHD Graphics 620 [8086:5917] InstallationDate: Installed on 2020-11-22 (151 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: AVITA NS14A2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=011d61ba-ef72-40ed-9957-25830622d9c7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2019 dmi.bios.release: 0.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BSR5IPHK-14UF80-AVI-V22 dmi.board.asset.tag: Default string dmi.board.name: 6614UFWC80 dmi.board.vendor: AVITA dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: AVITA dmi.chassis.version: Default string dmi.ec.firmware.release: 0.22 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBSR5IPHK-14UF80-AVI-V22:bd04/19/2019:br0.22:efr0.22:svnAVITA:pnNS14A2:pvrDefaultstring:rvnAVITA:rn6614UFWC80:rvrDefaultstring:cvnAVITA:ct10:cvrDefaultstring: dmi.product.family: CN6614 dmi.product.name: NS14A2 dmi.product.sku: CN6614F56U1IN-MB dmi.product.version: Default string dmi.sys.vendor: AVITA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/xorg/+bug/1925824/+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 1925824] [NEW] Display Error (hardware bug: Screen doesnt display on warm boot and turning on after Suspend)
Public bug reported: I have Avita NS14A2 laptop where i dual boot windows 10 and Ubuntu 20.04. In past few days might be after installing updates I am facing issue where my screen dont display at all when i first boot it and after multiple force shut down and then boot in it work, even on doing Suspend and then opening it, screen didnt not display for about 5-6 minutes, and then shows login screen. On checking logs software i got these line on those time stamp when display doesnt shows this is the line: (Hardware) i915 :00:02.0: [drm] *ERROR* failed to enable link training this line continues for about 30-40 times on average during time when screen doesnt display anything on turing on. So I think there is some issue with it. As I primarily use Ubuntu 20.04 so didnt check it with windows 10 but on doing cold boot it didnt even shows the boot menu where i can choose between Ubuntu 20.04 and Windows 10. But once screen starts displaying i dont see that error in logs software anymore and screen doesnt freezes or hangs. It only happen when i either open after suspend or do cold boot. Please consider this issue on urgent basis, as it takes a lot of time and efforts to make screen display something. :( And please let me know whether I should do fresh installation of ubuntu 20.04 again. Sorry for any grammatical mistakes. :) Thank you, Bipul Harsh bipulharsh...@gmail.com ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 20:36:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation UHD Graphics 620 [8086:5917] InstallationDate: Installed on 2020-11-22 (151 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: AVITA NS14A2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=011d61ba-ef72-40ed-9957-25830622d9c7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2019 dmi.bios.release: 0.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BSR5IPHK-14UF80-AVI-V22 dmi.board.asset.tag: Default string dmi.board.name: 6614UFWC80 dmi.board.vendor: AVITA dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: AVITA dmi.chassis.version: Default string dmi.ec.firmware.release: 0.22 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBSR5IPHK-14UF80-AVI-V22:bd04/19/2019:br0.22:efr0.22:svnAVITA:pnNS14A2:pvrDefaultstring:rvnAVITA:rn6614UFWC80:rvrDefaultstring:cvnAVITA:ct10:cvrDefaultstring: dmi.product.family: CN6614 dmi.product.name: NS14A2 dmi.product.sku: CN6614F56U1IN-MB dmi.product.version: Default string dmi.sys.vendor: AVITA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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 ubuntu ** Attachment added: "Logs Software Display" https://bugs.launchpad.net/bugs/1925824/+attachment/5491440/+files/bug.png -- 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/1925824 Title: Display Error (hardware bug: Screen doesnt display on warm boot and turning on after Suspend) Status in xorg package in Ubuntu: New Bug description: I have Avita NS14A2 laptop where i dual boot windows 10 and Ubuntu 20.04. In past few days might be after installing updates I am facing issue where my screen dont display at all when i first boot it and after multiple force shut down and then boot in it work, even on doing Suspend and then opening it, screen didnt not display for about 5-6 minutes, and then shows login screen. On checking logs software i got these line on those time stamp when display doesnt shows this is
[Touch-packages] [Bug 1925823] [NEW] gnome-terminal losts or ignore the newline character coming from mouse paste
Public bug reported: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. But in return this bug, the pasted command is showed in reverse coloring, what is very disturbing when a command is not executed, but decorated in a funny way instead. This is new in 21.04, the dropping commands into a gnome-terminal worked fine in 20.10, ... ... and in the last 27 years of my linux usage. ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Also affects: bash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1925823 Title: gnome-terminal losts or ignore the newline character coming from mouse paste Status in bash package in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Bug description: If there is a complete bash command with terminating newline in the cut and paste buffer, and it is pasted into a gnome-terminal, then the command is *not* executed, the newline is ignored by the terminal. But in return this bug, the pasted command is showed in reverse coloring, what is very disturbing when a command is not executed, but decorated in a funny way instead. This is new in 21.04, the dropping commands into a gnome-terminal worked fine in 20.10, ... ... and in the last 27 years of my linux usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1925823/+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 1925815] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1925815 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in gconf package in Ubuntu: New Bug description: Whenever I run apt-get install (for any binary) in command line prompt, - I get the follwing error, please help me - what is the fix? update-gconf-defaults: error: Destination directory does not exist. dpkg: error processing package gconf2 (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: gconf2 E: Sub-process /usr/bin/dpkg returned an error code (1) root@LP-5CD9156H04:/home/tapan# ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-193.224-generic 4.4.236 Uname: Linux 4.4.0-193-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.26 AptOrdering: gconf2: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri Apr 23 19:49:20 2021 DpkgHistoryLog: Start-Date: 2021-04-23 19:49:19 Commandline: apt-get install build-essential libgl1-mesa-dev ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2019-05-09 (715 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1925815/+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 1925815] [NEW] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: Whenever I run apt-get install (for any binary) in command line prompt, - I get the follwing error, please help me - what is the fix? update-gconf-defaults: error: Destination directory does not exist. dpkg: error processing package gconf2 (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: gconf2 E: Sub-process /usr/bin/dpkg returned an error code (1) root@LP-5CD9156H04:/home/tapan# ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-193.224-generic 4.4.236 Uname: Linux 4.4.0-193-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.26 AptOrdering: gconf2: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri Apr 23 19:49:20 2021 DpkgHistoryLog: Start-Date: 2021-04-23 19:49:19 Commandline: apt-get install build-essential libgl1-mesa-dev ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2019-05-09 (715 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1925815 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in gconf package in Ubuntu: New Bug description: Whenever I run apt-get install (for any binary) in command line prompt, - I get the follwing error, please help me - what is the fix? update-gconf-defaults: error: Destination directory does not exist. dpkg: error processing package gconf2 (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: gconf2 E: Sub-process /usr/bin/dpkg returned an error code (1) root@LP-5CD9156H04:/home/tapan# ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-193.224-generic 4.4.236 Uname: Linux 4.4.0-193-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.26 AptOrdering: gconf2: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri Apr 23 19:49:20 2021 DpkgHistoryLog: Start-Date: 2021-04-23 19:49:19 Commandline: apt-get install build-essential libgl1-mesa-dev ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2019-05-09 (715 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1925815/+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 1919177] Re: Azure: issues with accelerated networking on Hirsute
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
Incomplete
Status in linux-azure package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+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 1921452] Please test proposed package
Hello Shengyao, or anyone else affected, Accepted alsa-lib into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.2.2-2.1ubuntu2.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: In Progress Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+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 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
Hello Shengyao, or anyone else affected, Accepted alsa-lib into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.2.3.2-1ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: alsa-lib (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: alsa-lib (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: In Progress Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+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 1925796] [NEW] SRU the current 1.2.4 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some bugfixes https://gitlab.gnome.org/GNOME/gupnp/-/blob/master/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The library is used by rygel for pnp media sharing. Enable the option from the settings and try browsing and playing for another computer using for example rhythmbox. * Regression potential The main fix is around IPv6 local resolution, check that if possible. ** Affects: gupnp (Ubuntu) Importance: Undecided Status: Invalid ** Changed in: gupnp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp in Ubuntu. https://bugs.launchpad.net/bugs/1925796 Title: SRU the current 1.2.4 stable update Status in gupnp package in Ubuntu: Invalid Bug description: * Impact That's the current GNOME stable update, including some bugfixes https://gitlab.gnome.org/GNOME/gupnp/-/blob/master/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The library is used by rygel for pnp media sharing. Enable the option from the settings and try browsing and playing for another computer using for example rhythmbox. * Regression potential The main fix is around IPv6 local resolution, check that if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1925796/+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 1925795] [NEW] SRU the current 0.20.4 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some bugfixes and translation updates https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS There are non trivial changes to the meson build system included in the update but we still build using autotools so that's not impacting us * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Libsecret is providing an API to access gnome-keyring secrets, try a few applications using it and make sure credentials are correctly available. To list a few possible candidate softwares - evince (try to open a a password protected pdf, it should store and remember the password) - evolution - epiphany-browser - vinagre - balsa - deja-dup * Regression potential Nothing specific to try in those changes, just ensure the library still access the passwords as expected ** Affects: libsecret (Ubuntu) Importance: Low Status: Fix Released ** Changed in: libsecret (Ubuntu) Importance: Undecided => Low ** Changed in: libsecret (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1925795 Title: SRU the current 0.20.4 stable update Status in libsecret package in Ubuntu: Fix Released Bug description: * Impact That's the current GNOME stable update, including some bugfixes and translation updates https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS There are non trivial changes to the meson build system included in the update but we still build using autotools so that's not impacting us * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Libsecret is providing an API to access gnome-keyring secrets, try a few applications using it and make sure credentials are correctly available. To list a few possible candidate softwares - evince (try to open a a password protected pdf, it should store and remember the password) - evolution - epiphany-browser - vinagre - balsa - deja-dup * Regression potential Nothing specific to try in those changes, just ensure the library still access the passwords as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1925795/+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 1925797] [NEW] SRU the current 1.2.4 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some bugfixes https://gitlab.gnome.org/GNOME/gupnp/-/blob/master/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The library is used by rygel for pnp media sharing. Enable the option from the settings and try browsing and playing for another computer using for example rhythmbox. * Regression potential The main fix is around IPv6 local resolution, check that if possible. ** Affects: gupnp (Ubuntu) Importance: Undecided Status: Invalid ** Changed in: gupnp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp in Ubuntu. https://bugs.launchpad.net/bugs/1925797 Title: SRU the current 1.2.4 stable update Status in gupnp package in Ubuntu: Invalid Bug description: * Impact That's the current GNOME stable update, including some bugfixes https://gitlab.gnome.org/GNOME/gupnp/-/blob/master/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The library is used by rygel for pnp media sharing. Enable the option from the settings and try browsing and playing for another computer using for example rhythmbox. * Regression potential The main fix is around IPv6 local resolution, check that if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1925797/+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 1925798] [NEW] SRU the current 1.2.4 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some bugfixes https://gitlab.gnome.org/GNOME/gupnp/-/blob/master/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The library is used by rygel for pnp media sharing. Enable the option from the settings and try browsing and playing for another computer using for example rhythmbox. * Regression potential The main fix is around IPv6 local resolution, check that if possible. ** Affects: gupnp (Ubuntu) Importance: Low Status: Fix Released ** Changed in: gupnp (Ubuntu) Importance: Undecided => Low ** Changed in: gupnp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp in Ubuntu. https://bugs.launchpad.net/bugs/1925798 Title: SRU the current 1.2.4 stable update Status in gupnp package in Ubuntu: Fix Released Bug description: * Impact That's the current GNOME stable update, including some bugfixes https://gitlab.gnome.org/GNOME/gupnp/-/blob/master/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The library is used by rygel for pnp media sharing. Enable the option from the settings and try browsing and playing for another computer using for example rhythmbox. * Regression potential The main fix is around IPv6 local resolution, check that if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1925798/+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 1925676] Re: Xorg freeze
Yesterday, I tried to listen to a podcast to see if that bug would affect an audio only program. Here again, the podcast jammed after 10 minutes or so in the same way as Youtube or DailyMotion video. It seems to be related to audio more than video. Robert Boucher -- 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/1925676 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Since a week or two, videos started to freeze on Youtube. The video jam, the audio repeating the last quarter of a second of material, just like an audio CD that stays hooked. At this point, the mouse and the keyboard don't respond in any way and I have to depress the ON/OFF key and hold it a few seconds to do a forced stop. The computer restart normally, and Firefox open with a screen that says:"sorry we cannot restore your previous tabs". This bug happens again and again, each time 15 or 20 minutes after starting a video. I thought maybe it is a problem related to Youtube, but I tried watching a video on another site, DailyMotion, and the same thing happened, again after 15 minutes. I didn't upgrade or add any software recently, nor change any setting. This thing really appeared out of a blue sky. Thanks for your attention, RB ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 22 14:53:35 2021 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: IBM ThinkPad X41 [1014:0582] Subsystem: IBM ThinkPad X41 [1014:0582] InstallationDate: Installed on 2018-08-14 (982 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: IBM 1875M2U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-210-generic root=UUID=596f4e0f-deb0-4de7-973b-8259f928fbe9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2007 dmi.bios.vendor: IBM dmi.bios.version: 70ET69WW (1.29 ) dmi.board.name: 1875M2U dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr70ET69WW(1.29):bd05/29/2007:svnIBM:pn1875M2U:pvrThinkPadT43:rvnIBM:rn1875M2U:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 1875M2U dmi.product.version: ThinkPad T43 dmi.sys.vendor: IBM version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.12 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Apr 22 10:09:47 2021 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1925676/+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 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
Merging gtk+3.0 3.24.28-1 from debian/experimental fixes the problem here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
** Changed in: ubuntu-z-systems Status: Triaged => Fix Committed -- 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/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Status in systemd source package in Hirsute: Invalid Status in udev source package in Hirsute: Invalid Bug description: SRU Justification [Impact] Hot removal of disks under kvm on s390 does not result in the kernel removing the block device, which can lead to hung tasks and other issues. [Test Plan] See steps to reproduce the bug in the original description below. To test, execute these steps and confirm that the block device gets removed as expected. [Where problems could occur] The fix is a revert of the changes which introduced this regression. The original commit was a removal of supposedly unused code, but it seems a mistake was made in the logic around unregistering of disks. Reverting the changes could have potential to introduce bugs related to other virt devices, especially if it interacts badly with subsequent driver changes. However, the patch reverted cleanly, and reverting restores the code to the state which has been working well in previous kernels and seems like the lowest risk option until a proper fix is available upstream. --- Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added&removed => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log pr
[Touch-packages] [Bug 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
@seb128 The auto-correct feature is suppose to be triggered on . It still seems to work with which is not useful in most cases. I am running the hirsute release iso with kvm, chose the French locale and started libreoffice writer. Entering __D does not lead to the expected auto correct. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1925434] Re: New bugfix release 21.0.x
Please, also consider backporting an important fix for Metro Exodus, see this ticket: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1925530 Or wait with the Mesa update until 21.0.4 is released which will happen in 2021-05-05. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1925434 Title: New bugfix release 21.0.x Status in mesa package in Ubuntu: In Progress Status in mesa source package in Focal: In Progress Status in mesa source package in Hirsute: In Progress Bug description: [Impact] This is the last point-release of the 21.0.x-series, we should put it in hirsute so latest bugfixes would get there, and in focal for 20.04.3 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1925434/+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 1925775] Re: SRU the current 3.36.1 stable update
** Description changed: * Impact - That's the current GNOME stable update, including some API documentation fixes + That's the current GNOME stable update, including some API documentation fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Try adding online account in a GNOME session, ensure the service is correctly enabled in application, for example that a google accounts are picked up in gnome-calendar and evolution. * Regression potential The changes are in API documentation so nothing specific to check, if there is an issue it would be from a toolchain regression -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1925775 Title: SRU the current 3.36.1 stable update Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: * Impact That's the current GNOME stable update, including some API documentation fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Try adding online account in a GNOME session, ensure the service is correctly enabled in application, for example that a google accounts are picked up in gnome-calendar and evolution. * Regression potential The changes are in API documentation so nothing specific to check, if there is an issue it would be from a toolchain regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1925775/+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 1925779] [NEW] [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] [Lenovo T14s-AMD] No sound at all when the audio output from HDMI port.
Public bug reported: No sound at all when the audio output from HDMI port. [Steps to reproduce] 1. Install the daily build image on Lenovo T14s-AMD 2. Login the system 3. Connect the HDMI port with a Monitor 4. Select the 'Output Device' is HDMI 5. Try to play sound from the monitor [Actual result] No sound at all when the audio output from HDMI port. The internal speaker works normally. [Test image] http://cdimage.ubuntu.com/ubuntu/daily-live/current/hirsute-desktop-amd64.iso [Test Device] https://certification.canonical.com/hardware/202006-27964 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: u 1424 F pulseaudio /dev/snd/controlC1: u 1424 F pulseaudio /dev/snd/controlC0: u 1424 F pulseaudio /dev/snd/pcmC0D0c: u 1424 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 06:18:01 2021 InstallationDate: Installed on 2021-04-23 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: u 1424 F pulseaudio /dev/snd/controlC1: u 1424 F pulseaudio /dev/snd/controlC0: u 1424 F pulseaudio /dev/snd/pcmC0D0c: u 1424 F...m pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2020 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET55T(1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UHZ5DXUS dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrR1CET55T(1.24):bd09/15/2020:br1.24:efr1.24:svnLENOVO:pn20UHZ5DXUS:pvrThinkPadT14sGen1:rvnLENOVO:rn20UHZ5DXUS:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UHZ5DXUS dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1925779 Title: [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] [Lenovo T14s-AMD] No sound at all when the audio output from HDMI port. Status in alsa-driver package in Ubuntu: New Bug description: No sound at all when the audio output from HDMI port. [Steps to reproduce] 1. Install the daily build image on Lenovo T14s-AMD 2. Login the system 3. Connect the HDMI port with a Monitor 4. Select the 'Output Device' is HDMI 5. Try to play sound from the monitor [Actual result] No sound at all when the audio output from HDMI port. The internal speaker works normally. [Test image] http://cdimage.ubuntu.com/ubuntu/daily-live/current/hirsute-desktop-amd64.iso [Test Device] https://certification.canonical.com/hardware/202006-27964 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: u 1424 F pulseaudio /dev/snd/controlC1: u 1424 F pulseaudio /dev/snd/controlC0: u 1424 F pulseaudio /dev/snd/pcmC0D0c: u 1424 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 06:18:01 2021 InstallationDate: Installed on 2021-04-23 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_DevicesInUse: USE
[Touch-packages] [Bug 1925775] [NEW] SRU the current 3.36.1 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some API documentation fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Try adding online account in a GNOME session, ensure the service is correctly enabled in application, for example that a google accounts are picked up in gnome-calendar and evolution. * Regression potential The changes are in API documentation so nothing specific to check, if there is an issue it would be from a toolchain regression ** Affects: gnome-online-accounts (Ubuntu) Importance: Low Status: Fix Released ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Fix Released ** Changed in: gnome-online-accounts (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1925775 Title: SRU the current 3.36.1 stable update Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: * Impact That's the current GNOME stable update, including some API documentation fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Try adding online account in a GNOME session, ensure the service is correctly enabled in application, for example that a google accounts are picked up in gnome-calendar and evolution. * Regression potential The changes are in API documentation so nothing specific to check, if there is an issue it would be from a toolchain regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1925775/+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 1925705] Re: 100% cpu
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1925705 Title: 100% cpu Status in xorg package in Ubuntu: New Bug description: my spek i5 gen3 ram 8Gb ssd 512 fresh install and my cpu always 100% when open and run apps, like firefox, chrome ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Apr 23 07:15:41 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2021-04-20 (2 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 2349CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=6e403edb-143d-4aa1-8a31-b84abf6175a9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349CTO:pvrThinkPadT430:rvnLENOVO:rn2349CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349CTO dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/xorg/+bug/1925705/+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 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
** Changed in: linux (Ubuntu Hirsute) Status: Triaged => Fix Committed -- 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/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Status in systemd source package in Hirsute: Invalid Status in udev source package in Hirsute: Invalid Bug description: SRU Justification [Impact] Hot removal of disks under kvm on s390 does not result in the kernel removing the block device, which can lead to hung tasks and other issues. [Test Plan] See steps to reproduce the bug in the original description below. To test, execute these steps and confirm that the block device gets removed as expected. [Where problems could occur] The fix is a revert of the changes which introduced this regression. The original commit was a removal of supposedly unused code, but it seems a mistake was made in the logic around unregistering of disks. Reverting the changes could have potential to introduce bugs related to other virt devices, especially if it interacts badly with subsequent driver changes. However, the patch reverted cleanly, and reverting restores the code to the state which has been working well in previous kernels and seems like the lowest risk option until a proper fix is available upstream. --- Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added&removed => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log pr
[Touch-packages] [Bug 1925739] Re: Strange sound when speaker is muted
https://youtu.be/uuMdsLpbW54 here is audio. Reproduce by install ubuntu 20.10(no problem) -> sudo apt update; sudo apt upgrade -y; done. -> Now face this sound while 3.5mm jack plugged https://youtu.be/uuMdsLpbW54. When I am playing songs sound stop. When I stop music this again start. -- 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/1925739 Title: Strange sound when speaker is muted Status in pulseaudio package in Ubuntu: Incomplete Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+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 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
It's not happening on my hirsute installation, picking a random combinaison from the replacing list, __D is correctly replaced by Δ , how do you test exactly? One commention 1/2 but the default syntax seems to be 1//2 which is working -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1925761] [NEW] libnns-mymachines update breaks local mdns discovery
Public bug reported: After the last systemd update 245.4-ubuntu3.6 on 20.04 focal, I discovered I couldn't use .local network names anymore. All returning Name or service unknown. Nothing explicitly showing a problem in avahi-deamon systemd logs, no firewall activated, and no changes done to /etc/nsswitch.conf. After noticing those packages just had been updated, I downgraded systemd to 245.4-ubuntu3 through aptitude and it works again. So I'm pretty sure something's wrong with last package from focal-updates of libnss-mymachines. ** 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/1925761 Title: libnns-mymachines update breaks local mdns discovery Status in systemd package in Ubuntu: New Bug description: After the last systemd update 245.4-ubuntu3.6 on 20.04 focal, I discovered I couldn't use .local network names anymore. All returning Name or service unknown. Nothing explicitly showing a problem in avahi-deamon systemd logs, no firewall activated, and no changes done to /etc/nsswitch.conf. After noticing those packages just had been updated, I downgraded systemd to 245.4-ubuntu3 through aptitude and it works again. So I'm pretty sure something's wrong with last package from focal-updates of libnss-mymachines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925761/+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 1925739] Re: Strange sound when speaker is muted
** Summary changed: - I get sound for no resone + Strange sound when speaker is muted -- 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/1925739 Title: Strange sound when speaker is muted Status in pulseaudio package in Ubuntu: Incomplete Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+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 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
One recent merge mentioning libreoffice is https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3239 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+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 1925742] Re: IMAP broken in Evolution
Thank you for your bug report, from the upstream bug 'The bug in the evolution-data-server is there for a long time. The change on the iCloud server uncovered it, when they added support only for the LIST-STATUS extension' We will include the fix in the next updates though ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => Low ** Changed in: evolution-data-server (Ubuntu) Status: Confirmed => Fix Committed ** Summary changed: - IMAP broken in Evolution + Recent iCloud versions trigger an issue in IMAP x -- 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/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Committed Bug description: There is a recently introduced bug in evolution-data-server which broke access to email in iCloud. The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1925739] Re: I get sound for no resone
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1925739 Title: I get sound for no resone Status in pulseaudio package in Ubuntu: Incomplete Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+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 1925739] Re: I get sound for no resone
Could you also do apport-collect 1925739 -- 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/1925739 Title: I get sound for no resone Status in pulseaudio package in Ubuntu: Incomplete Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1925739/+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 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
Manfred: Thanks! (Offtopic: I googled "apt phased 20%". The "20%" seems to throw Google off completely, it didn't show ANY results related to Linux. Leaving off the 20% yields much better results ;)) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "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: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925745/+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 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
A workaround is to manually force installation of the dependencies with the newer "phased" versions: apt install ubuntu-release-upgrader-core=1:21.04.11 python3-distupgrade=1:21.04.11 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "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: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925745/+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 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
Re: "I could not find any information what "phased 20%" means." https://wiki.ubuntu.com/StableReleaseUpdates#Phasing https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "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: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925745/+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 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "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: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925745/+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 1925745] [NEW] Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
Public bug reported: I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "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: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: 21.04 hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "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: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925745/+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 1925742] Re: IMAP broken in Evolution
Bug is also present in Groovy and Hirsute. -- 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/1925742 Title: IMAP broken in Evolution Status in evolution-data-server package in Ubuntu: Confirmed Bug description: There is a recently introduced bug in evolution-data-server which broke access to email in iCloud. The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1925742] Re: IMAP broken in Evolution
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evolution-data-server (Ubuntu) Status: New => Confirmed -- 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/1925742 Title: IMAP broken in Evolution Status in evolution-data-server package in Ubuntu: Confirmed Bug description: There is a recently introduced bug in evolution-data-server which broke access to email in iCloud. The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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
