[Touch-packages] [Bug 1905623] Re: df: /run/user/1000/doc: Operation not permitted
Daniel, thank you for submitting the patch upstream! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted Status in coreutils package in Ubuntu: Fix Released Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: /run/user/1000/doc is a fuse.portal mount point, but statfs() return EPERM, hence df produces an error message. Maybe statfs() is not implemented, but it would be good to quieten this down (df even does not allow me to ignore it, probably because it looks at statfs to find out fs type, so my fs type ignoring doesn't work). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906243] Re: Audio comes out through system speakers when headset autoconnects
I am facing with similar problem. I have Thinkpad T14 with COWIN bluetooth headphones. When I turn ON the headphones,it automatically connects. However the sound still comes out of internal speaker. When I go to output devices the headphone is not in the list. I have to disconnect and reconnect again to get the audio to the headphones. I tried the suggested solution from #1866194 i.e. deleting ~/.config/pulse and restarting. Also I have pulseaudio v13.99.1. -- 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/1906243 Title: Audio comes out through system speakers when headset autoconnects Status in pulseaudio package in Ubuntu: New Bug description: When I turn on my Bluetooth headset, Ubuntu 20.04 connects to it automatically (Or at least it appears to be connected to it). It says connected and the switch is in the ON position in Bluetooth settings, however the audio still comes out of the speakers, the icon next to the volume bar in the top-right menu shows the speaker icon instead of the headphone icon. I have to disconnect the headset and re-connect it from Bluetooth settings for the audio to go to the headset. It doesn't work only when it connects automatically. Always works when I connect it manually. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sujit 1394 F pulseaudio /dev/snd/controlC0: sujit 1394 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-28 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: pulseaudio 1:13.99.1-1ubuntu3.8 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Tags: focal Uname: Linux 5.4.0-54-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: 07/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0JKRPT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/13/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.sku: 0662 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903814] Re: [binutils] Prevent GOT access rewrite for certain symbols
I can confirm that the patch applies and the build seems to pass OK in a -security enabled PPA (https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4439). But it produces some test failures/regressions, which we need to work on before we can get this moving: https://bileto.ubuntu.com/excuses/4439/bionic.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1903814 Title: [binutils] Prevent GOT access rewrite for certain symbols Status in Ubuntu on IBM z Systems: Triaged Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Bionic: New Status in binutils package in Debian: New Bug description: Please backport the following bugfix into Ubuntu LTS: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e6213e09ed0e Some relevant historic links: Debian bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961736 glibc bugreport: https://sourceware.org/bugzilla/show_bug.cgi?id=18960 In s390 kernel context, this bug manifests itself as random errors and infinite loops, so it's fairly severe. These are the current versions of binutils: Package binutils xenial (16.04LTS) (devel): GNU assembler, linker and binary utilities 2.26.1-1ubuntu1~16.04.8 [security]: amd64 i386 2.26-8ubuntu2 [ports]: arm64 armhf powerpc ppc64el s390x xenial-updates (devel): GNU assembler, linker and binary utilities 2.26.1-1ubuntu1~16.04.8: amd64 arm64 armhf i386 powerpc ppc64el s390x bionic (18.04LTS) (devel): GNU assembler, linker and binary utilities 2.30-21ubuntu1~18.04.4 [security]: amd64 i386 2.30-15ubuntu1 [ports]: arm64 armhf ppc64el s390x bionic-updates (devel): GNU assembler, linker and binary utilities 2.30-21ubuntu1~18.04.4: amd64 arm64 armhf i386 ppc64el s390x focal (20.04LTS) (devel): GNU assembler, linker and binary utilities 2.34-6ubuntu1: amd64 arm64 armhf i386 ppc64el s390x groovy (devel): GNU assembler, linker and binary utilities 2.35.1-1ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The patch applies fine to 2.26 and 2.30 (except for tests, but we don't need them). We don't need it on 2.32+. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel
** Description changed: + [Impact] + APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. + + [Test case] + - Install new kernel + - Reboot into kernel not listed as protected in 01autoremove-kernels + - Run autoremove + + [Where problems could occur] + We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. + + [Original bug report] + This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set in '/etc/apt/apt.conf.d/50unattended-upgrades'. - In shell: $ uname -r 4.4.0-22-generic $ apt-get -s autoremove NOTE: This is only a simulation! apt-get needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic 0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Aug 21 16:11:27 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-28 (114 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified] mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 2016-07-30T12:15:32.706300 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1615381 Title: apt-get autoremove may remove current kernel Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Won't Fix Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Bug description: [Impact] APT will try and fail to remove the currently running kernel, when booted into an older kernel that is not protected. May wreak some havoc if mixed with other operations to the point that apt goes weird and needs manual fixing up. [Test case] - Install new kernel - Reboot into kernel not listed as protected in 01autoremove-kernels - Run autoremove [Where problems could occur] We may more easily run out of space in /boot. hirsute has new autoremoval code that runs completely at runtime; but that seems a bit large to SRU after only a few weeks in hirsute. Hence, we should protect the current kernel _in addition_ to the other kernels, just like unattended-upgrades and update-manager do. This increases the risk of filling up /boot compared to older apt versions, but is at the same level as unattended-upgrades and update-manager. [Original bug report] This may happen, if you boot one of the older kernels, that is not protected by /etc/apt/apt.conf.d/01autoremove-kernels Workaround: run /etc/kernel/postinst.d/apt-auto-removal during each boot (e.g. by using cron). Note: The workaround breaks autoremoving feature of new unneeded kernels in unattended-upgrades i.e. the setting 'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default in 16.04 unless 'Unattended-Upgrade::Remove-Unus
[Touch-packages] [Bug 1825186] Re: gpgv-win32 autopkgtest always fails
Hello Dan, or anyone else affected, Accepted gnupg2 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnupg2/2.2.4-1ubuntu1.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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnupg2 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1825186 Title: gpgv-win32 autopkgtest always fails Status in gnupg package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Opinion Status in gnupg source package in Xenial: Won't Fix Status in gnupg2 source package in Bionic: Fix Committed Status in gnupg2 source package in Cosmic: Won't Fix Status in gnupg2 source package in Disco: Fix Released Bug description: [impact] gpgv-win32 autopkgtest always fails [test case] check http://autopkgtest.ubuntu.com/packages/g/gnupg2 or run autopkgtest manually note the gpgv-win32 test is skipped on ppc64el and s390x for b/c, and has been removed from d/t/control entirely in d [regression potential] little to none; this affects the test case only [other info] as mentioned, in disco, the gpgv-win32 test has been removed from the tests/control completely. not sure if that is a better approach than fixing the test case. For now, I marked this Fix Released for disco since it doesn't fail there (since the testcase was removed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1825186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915250] Re: buildd file owner/group for shared libraries
Fwiw, mysql-8.0 is also affected: $ dpkg -c libmysqlclient21_8.0.23-3_amd64.deb|grep buildd drwxr-xr-x buildd/buildd 0 2021-02-11 10:32 ./ [many more] And some more: $ dpkg -c libqt5xdg3_3.6.0-1ubuntu2_amd64.deb |grep buildd -rw-r--r-- buildd/buildd 268440 2021-02-11 21:58 ./usr/lib/x86_64-linux-gnu/libQt5Xdg.so.3.6.0 But it seems to have stopped around Saturday, not sure if something was done on the buildds maybe? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1915250 Title: buildd file owner/group for shared libraries Status in binutils package in Ubuntu: Confirmed Status in debhelper package in Ubuntu: Confirmed Status in fakeroot package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Confirmed Status in debhelper package in Debian: Unknown Bug description: the current state of -proposed creates deb packages with buildd file owner/group for shared libraries. reported at least for kwayland-integration. $ dpkg -c kwayland-integration_5.20.90-0ubuntu1_amd64.deb|grep \.so -rw-r--r-- doko/doko 18984 2021-01-21 23:44 ./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so -rw-r--r-- doko/doko 85392 2021-01-21 23:44 ./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so -rw-r--r-- doko/doko 35536 2021-01-21 23:44 ./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeKWaylandPlugin.so - in a release pocket, rebuild binutils from proposed. correctly restores the file ownership - in a release pocket, update glibc from proposed. then rebuild binutils from proposed. shows the wrong ownership To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1915250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915707] [NEW] keyboard settings not applied
Public bug reported: Global keyboard settings are set in /etc/defaults/keyboard: XKBMODEL="pc105" XKBLAYOUT="de" XKBVARIANT="" XKBOPTIONS="lv3:ralt_switch,compose:menu,terminate:ctrl_alt_bksp" BACKSPACE="guess" These settings are not active any more after upgrading from focal to groovy. Same applies if upgrading from groovy to hirsute. The file /etc/defaults/keyboard is untouched, but any console uses an US keyboard. Same applies for X11-Sessions: all users have their keyboard defaulted to US layout. Any other layouts configured for any user vanishes. Configurations have to be done again as it they never where set. For all users settings -> Keyboard -> Keyboard Layout is set to use system-wide keyboard settings. This is set to US layout. This seems not changeable at all! If this depends on file /etc/defaults/keyboard. It does not respect this file. There has to be a way to set some other keyboard layout system-wide. Not only for one session or one user! And: this setting shall not be overwritten by upgrading. And it shall not be ignored after upgrading! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: console-setup 1.195ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 15 12:10:46 2021 InstallationDate: Installed on 2014-01-31 (2572 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: Upgraded to groovy on 2018-11-23 (814 days ago) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1915707 Title: keyboard settings not applied Status in console-setup package in Ubuntu: New Bug description: Global keyboard settings are set in /etc/defaults/keyboard: XKBMODEL="pc105" XKBLAYOUT="de" XKBVARIANT="" XKBOPTIONS="lv3:ralt_switch,compose:menu,terminate:ctrl_alt_bksp" BACKSPACE="guess" These settings are not active any more after upgrading from focal to groovy. Same applies if upgrading from groovy to hirsute. The file /etc/defaults/keyboard is untouched, but any console uses an US keyboard. Same applies for X11-Sessions: all users have their keyboard defaulted to US layout. Any other layouts configured for any user vanishes. Configurations have to be done again as it they never where set. For all users settings -> Keyboard -> Keyboard Layout is set to use system-wide keyboard settings. This is set to US layout. This seems not changeable at all! If this depends on file /etc/defaults/keyboard. It does not respect this file. There has to be a way to set some other keyboard layout system-wide. Not only for one session or one user! And: this setting shall not be overwritten by upgrading. And it shall not be ignored after upgrading! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: console-setup 1.195ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 15 12:10:46 2021 InstallationDate: Installed on 2014-01-31 (2572 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: Upgraded to groovy on 2018-11-23 (814 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1915707/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915704] [NEW] Specific pointing device disappear/disconnect when standby
Public bug reported: Ubuntu 20.10 groovy (x86-64) Cinnamon 4.6.7 Kernel 5.8.0-43-generic I installed Ubuntu while using a Microsft mise. This one works great with no problem. The buttons are old and used out, so I changed it with a Trust with RGB. The Trust mouse seems disconnected when going to standby (need keyboard, since mouse seems disconnected to show password prompt). The only way to get the mouse back to work, is to disconnect and reconnect it. What's narrow in this, is that I've tried again with the old pointing device (from Microsoft), and this one still is recognised in standby, and I'm able to click to open the password prompt. I've read this repport: https://bugs.launchpad.net/ubuntu/+bug/1573454 But it seems not totaly the same, since I've the problem with a pointer and not the other one. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/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 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Mon Feb 15 12:07:10 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.8.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GK107 [GeForce GTX 650] [19da:1288] MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=1768f602-2494-474b-970a-2f71d61fca4b ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2020 dmi.bios.release: 14.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1403 dmi.board.asset.tag: Default string dmi.board.name: PRIME B460-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1403:bd07/21/2020:br14.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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 groovy ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915704 Title: Specific pointing device disappear/disconnect when standby Status in xorg package in Ubuntu: New Bug description: Ubuntu 20.10 groovy (x86-64) Cinnamon 4.6.7 Kernel 5.8.0-43-generic I installed Ubuntu while using a Microsft mise. This one works great with no problem. The buttons are old and used out, so I changed it with a Trust with RGB. The Trust mouse seems disconnected when going to standby (need keyboard, since mouse seems disconnected to show password prompt). The only way to get the mouse back to work, is to disconnect and reconnect it. What's narrow in this, is that I've tried again with the old pointing device (from Microsoft), and this one still is recognised in standby, and I'm able to click to open the password prompt. I've read this re
[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
@stgraber Thank you for assisting with aligning udevs's behaviour with LXD. I've added the tests-in-lxd autopkgtests to ensure catching issues in LXD earlier. I'd be happy to add more tests in systemd's autopkgtest to not let udevd regress in LXD. @xnox I don't like to idea of letting services be failed in default installs in LXD because this would result bad user experience. @seb128 could you please patch network-manager 1.28 to behave in LXC like it did in 1.26 to let it migrate and not fail in LXC with systemd 247 until the udevd behaviour is fixed in LXC? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899833] Re: [ZenBook UX434FLC_UX434FL, Realtek ALC294, Speaker, Internal] fails after a while
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1899833 Title: [ZenBook UX434FLC_UX434FL, Realtek ALC294, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: the sound is good for while , then get noisi + lower to nothing, 2 time ago it get solved by turning on secure boot and turning of fast boot ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matinzare 1615 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 23:05:07 2020 InstallationDate: Installed on 2020-08-11 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: اوْکتوْبر 14 19:54:29 matinzare-ZenBook-UX434FLC dbus-daemon[913]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.31' (uid=125 pid=1100 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") اوْکتوْبر 14 19:54:29 matinzare-ZenBook-UX434FLC pulseaudio[1100]: No UCM verb is valid for hw:0 اوْکتوْبر 14 19:54:42 matinzare-ZenBook-UX434FLC systemd[1090]: pulseaudio.service: Succeeded. اوْکتوْبر 14 19:54:52 matinzare-ZenBook-UX434FLC systemd[1090]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX434FLC_UX434FL, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434FLC.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434FLC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434FLC.303:bd12/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434FLC_UX434FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX434FLC_UX434FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-08-11T18:28:56.120214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1899833/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915250] Re: buildd file owner/group for shared libraries
@mvo we know, we are tracing them all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1915250 Title: buildd file owner/group for shared libraries Status in binutils package in Ubuntu: Confirmed Status in debhelper package in Ubuntu: Confirmed Status in fakeroot package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Confirmed Status in debhelper package in Debian: Unknown Bug description: the current state of -proposed creates deb packages with buildd file owner/group for shared libraries. reported at least for kwayland-integration. $ dpkg -c kwayland-integration_5.20.90-0ubuntu1_amd64.deb|grep \.so -rw-r--r-- doko/doko 18984 2021-01-21 23:44 ./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so -rw-r--r-- doko/doko 85392 2021-01-21 23:44 ./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so -rw-r--r-- doko/doko 35536 2021-01-21 23:44 ./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeKWaylandPlugin.so - in a release pocket, rebuild binutils from proposed. correctly restores the file ownership - in a release pocket, update glibc from proposed. then rebuild binutils from proposed. shows the wrong ownership To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1915250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1913187] Re: iproute2 segfaults when filtering sockets
What about the autopkgtest regressions as marked by comment #8?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1913187
Title:
iproute2 segfaults when filtering sockets
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Bionic:
Fix Committed
Bug description:
[Impact]
* The ss tool crashes when a query returns no results (seg fault)
[Test Case]
* $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1
Segmentation fault
* PPA with the fix:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187
[Where problems could occur]
* The ss tool is impacted and it has its code changed for the fix.
* The fix is a clean cherry-pick and straightforward (moving
declaration after a NULL check).
[Other Info]
When in Ubuntu Bionic, if one calls:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58910 127.0.0.1:22
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
it works. Just like when in Groovy:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58908 127.0.0.1:22
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
but.. if there is nothing to show, in Bionic we get a segfault:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
Segmentation fault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903814] Comment bridged from LTC Bugzilla
--- Comment From i...@de.ibm.com 2021-02-15 09:35 EDT--- To me they all look like intermittent problems (timeouts on arm, 404s when installing packages on Intel). Is it possible to simply retrigger those? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1903814 Title: [binutils] Prevent GOT access rewrite for certain symbols Status in Ubuntu on IBM z Systems: Triaged Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Bionic: New Status in binutils package in Debian: New Bug description: Please backport the following bugfix into Ubuntu LTS: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e6213e09ed0e Some relevant historic links: Debian bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961736 glibc bugreport: https://sourceware.org/bugzilla/show_bug.cgi?id=18960 In s390 kernel context, this bug manifests itself as random errors and infinite loops, so it's fairly severe. These are the current versions of binutils: Package binutils xenial (16.04LTS) (devel): GNU assembler, linker and binary utilities 2.26.1-1ubuntu1~16.04.8 [security]: amd64 i386 2.26-8ubuntu2 [ports]: arm64 armhf powerpc ppc64el s390x xenial-updates (devel): GNU assembler, linker and binary utilities 2.26.1-1ubuntu1~16.04.8: amd64 arm64 armhf i386 powerpc ppc64el s390x bionic (18.04LTS) (devel): GNU assembler, linker and binary utilities 2.30-21ubuntu1~18.04.4 [security]: amd64 i386 2.30-15ubuntu1 [ports]: arm64 armhf ppc64el s390x bionic-updates (devel): GNU assembler, linker and binary utilities 2.30-21ubuntu1~18.04.4: amd64 arm64 armhf i386 ppc64el s390x focal (20.04LTS) (devel): GNU assembler, linker and binary utilities 2.34-6ubuntu1: amd64 arm64 armhf i386 ppc64el s390x groovy (devel): GNU assembler, linker and binary utilities 2.35.1-1ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The patch applies fine to 2.26 and 2.30 (except for tests, but we don't need them). We don't need it on 2.32+. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906671] Re: [MIR] usrmerge
letting just the dep update of ubuntu-meta through. ** Tags removed: block-proposed -- 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/1906671 Title: [MIR] usrmerge Status in debootstrap package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in usrmerge package in Ubuntu: Fix Released Bug description: [Availability] In universe. [Rationale] Since Disco, Ubuntu has defaulted to merged usr systems, specifically that /lib is a symlink to /usr/lib. However, we have not yet completed this transition for systems that were installed pre-disco. This package performs such transition using maintainer scripts. It has been tested and improved thoroughly and has managed to work with all sorts of packages that happened to be installed on the system. For systems that were installed post disco, this package is effectively a no-op. Systems that use nfs mounting with split /usr care must be taken to ensure that initrd mounts nfs-backed /usr. The package aborts configuration if such rare configuration is detected to avoid potentially bracking reboot. For all other systems, we always provide a fallback initrd which has been mounting both / and /usr whenever possible. [Security] The package ships two perl scripts, which are executed by root from maintainer scripts. [Quality assurance] There is debconf question one can preseed to prevent the migration, there is README.Debian explaining what it does and how. It is a one- way / one-time migration, removing the package will not undo the migration. [Dependencies] Perl, and many documented conflicts to ensure that usrmerge compatible packages are on disk prior to migration. [Standards compliance] Adheres to Debian Policy. [Maintenance] Maintained in Debian, merged and supported by Foundations, foundations-bugs is subscribed. [Background information] This will complete usrmerge migration, and will allow to switch buildds to build packages with merged-usr by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1906671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915659] Re: MSI computer desktop linux kernel 5.8 bug jammed and freeze all programs
** Package changed: ubuntu-meta (Ubuntu) => linux (Ubuntu) -- 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/1915659 Title: MSI computer desktop linux kernel 5.8 bug jammed and freeze all programs Status in linux package in Ubuntu: Incomplete Bug description: MSI computer desktop linux kernel 5.8 bug jammed and freeze all programs i am removed linux kernel 5.8 my MSI computer desktop because when same is trying install again ubuntu 20.04.2 LTS is jammed and nothing happen my MSI desktop computer only MSI desktop linux kernel 5.4 is working only my MSI computer MSI desktop linux kernel 5.8 dont working only jammed and freeze all programs this my intel graphic card information my MSI computer *-display description: VGA compatible controller product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:32 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915175] Re: wifi network stops working and shows a green wifi icon
** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1915175 Title: wifi network stops working and shows a green wifi icon Status in linux package in Ubuntu: New Bug description: I recently started using ubuntu 20.04, I connected it to my 2.4ghz Wi-Fi, at first the wifi worked fine, but suddenly the wifi stopped connecting, and after a few seconds it said "unable to activate network". I checked the "additional drivers tab" and it showed my wifi adapter, but it said "this device is using an alternate driver". right now I'm using my 5ghz Wi-Fi network, but sometimes it happens that it stops working, usually after suspend. UPDATE #1: Apparently it's working now, I suppose it's from an update. Anyways I guess it's fixed. UPDATE #2: it's broken again UPDATE #3: after checking the error a long time I've realized that this error happens when I leave it suspended it for a long time, it is fixed by doing about 3-4 restarts. I'm going to try to use a code that restarts the network-service after suspend, I'll see if it works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 12:09:28 2021 InstallationDate: Installed on 2021-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IpRoute: default via 192.168.1.254 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.8 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2021-02-08T22:50:26.196692 nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 Betancur 5G cda009c8-c845-4366-8436-8e9c44da2cbf /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915175/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
> @seb128 could you please patch network-manager 1.28 to behave in LXC like it did in 1.26 to let it migrate and not fail in LXC with systemd 247 until the udevd behaviour is fixed in LXC? alright, I can temporarily revert the commit that made it use udev under lxc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915738] [NEW] egrep: U+D56D (항) breaks ^/$ matching
Public bug reported:
In theory the regular expression ^.*$ should match any and every string,
including empty strings, but this specific Korean character U+D56D (항),
which I was unlucky enough to have one of my scripts come across, breaks
the expected behavior in egrep:
$ echo '' | egrep '^.*$'; echo $?
0
$ echo 'foo' | egrep '^.*$'; echo $?
foo
0
$ echo 'bar' | egrep '^.*$'; echo $?
bar
0
$ echo 'の名' | egrep '^.*$'; echo $?
の名
0
$ echo '항' | egrep '^.*$'; echo $?
1
Have I lost my mind...or should I go buy a lottery ticket? Here are some
rambling one-liners to illustrate the behavior further.
# An attempt to match the pattern ^.*$ (beginning of string, anything, end of
string) against this Korean character fails:
$ echo '항' | egrep '^.*$'; echo $?
1
# As you can see here a match works when the $ is dropped from the pattern:
$ echo '항' | egrep '^.*'; echo $?
항
0
# Also using the -P flag from grep instead of -E correctly matches the original
pattern:
$ echo '항' | grep -P '^.*$'; echo $?
항
0
# Sending a different Korean character (U+C720) to the same original pattern
works as expected as well:
$ echo '유' | egrep '^.*$'; echo $?
유
0
# Combining the two leads to the original failure mentioned:
$ echo '항유' | egrep '^.*$'; echo $?
1
# And reversing the order of the combination does not effect the outcome:
$ echo '유항' | egrep '^.*$'; echo $?
1
# But dropping the $ from the pattern gives the expected match:
$ echo '유항' | egrep '^.*'; echo $?
유항
0
# Dropping the ^ from the pattern also gives the expected match:
$ echo '유항' | egrep '.*$'; echo $?
유항
0
# Surrounding U+D56D with U+C720 does not alter the behavior:
$ echo '유항유' | egrep '^.*$'; echo $?
1
# But again dropping U+D56D (항) from the input string returns egrep to the
expected behavior:
$ echo '유유' | egrep '^.*$'; echo $?
유유
0
# And to make it very clear what the input is, here I'm using python to give a
raw dump of the input:
$ echo '유항유' | python -c 'import sys;
print(repr(sys.stdin.read().encode("unicode-escape")))'
b'\\uc720\\ud56d\\uc720\\n'
# My grep/egrep version:
$ grep --version
grep (GNU grep) 3.4
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Mike Haertel and others; see
.
$ egrep --version
grep (GNU grep) 3.4
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Mike Haertel and others; see
.
# My bash version
$ bash --version
GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
===
If somebody could explain this behavior I would appreciate it. If it
could be fixed, even better. In the meantime I think I will prefer 'grep
-P' over 'egrep' when I expect strings to contain Korean text. In this
contrived example the '^' and '$' didn't make a lot of sense, but I
thought it would be best to provide the simplest possible reproduction
case rather than spell out my full use case.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: grep 3.4-1
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Feb 15 17:10:42 2021
InstallationDate: Installed on 2020-01-22 (389 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: grep
UpgradeStatus: Upgraded to focal on 2021-02-01 (13 days ago)
** Affects: grep (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1915738
Title:
egrep: U+D56D (항) breaks ^/$ matching
Status in grep package in Ubuntu:
New
Bug description:
In theory the regular expression ^.*$ should match any and every
string, including empty strings, but this specific Korean character
U+D56D (항), which I was unlucky enough to have one of my scripts come
across, breaks the expected behavior in egrep:
$ echo '' | egrep '^.*$'; echo $?
0
$ echo 'foo' | egrep '^.*$'; echo $?
foo
0
$ echo 'bar' | egrep '^.*$'; echo $?
bar
0
$ echo 'の名' | egrep '^.*$'; echo $?
の名
[Touch-packages] [Bug 1825186] Autopkgtest regression report (gnupg2/2.2.4-1ubuntu1.4)
All autopkgtests for the newly accepted gnupg2 (2.2.4-1ubuntu1.4) for bionic have finished running. The following regressions have been reported in tests triggered by the package: libgnupg-interface-perl/0.52-9 (ppc64el, amd64, armhf, i386, arm64, s390x) paperkey/1.5-3 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#gnupg2 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1825186 Title: gpgv-win32 autopkgtest always fails Status in gnupg package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Opinion Status in gnupg source package in Xenial: Won't Fix Status in gnupg2 source package in Bionic: Fix Committed Status in gnupg2 source package in Cosmic: Won't Fix Status in gnupg2 source package in Disco: Fix Released Bug description: [impact] gpgv-win32 autopkgtest always fails [test case] check http://autopkgtest.ubuntu.com/packages/g/gnupg2 or run autopkgtest manually note the gpgv-win32 test is skipped on ppc64el and s390x for b/c, and has been removed from d/t/control entirely in d [regression potential] little to none; this affects the test case only [other info] as mentioned, in disco, the gpgv-win32 test has been removed from the tests/control completely. not sure if that is a better approach than fixing the test case. For now, I marked this Fix Released for disco since it doesn't fail there (since the testcase was removed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1825186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903605] [NEW] proposed patch: remove dependency on python3-requests
You have been subscribed to a public bug: I'm attaching a patch (based on 15ab343d7c887ca0) which removes apport's dependency on python3-requests. It's similar to a change that was merged into software-properties recently: https://code.launchpad.net/~slingamn/software-properties/+git/software- properties/+merge/389182 Thanks for your time! ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- proposed patch: remove dependency on python3-requests https://bugs.launchpad.net/bugs/1903605 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903605] Re: proposed patch: remove dependency on python3-requests
** Project changed: apport => apport (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1903605 Title: proposed patch: remove dependency on python3-requests Status in apport package in Ubuntu: New Bug description: I'm attaching a patch (based on 15ab343d7c887ca0) which removes apport's dependency on python3-requests. It's similar to a change that was merged into software-properties recently: https://code.launchpad.net/~slingamn/software-properties/+git /software-properties/+merge/389182 Thanks for your time! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1903605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903605] Re: proposed patch: remove dependency on python3-requests
** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu) Importance: Undecided => Medium ** Changed in: apport (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1903605 Title: proposed patch: remove dependency on python3-requests Status in apport package in Ubuntu: In Progress Bug description: I'm attaching a patch (based on 15ab343d7c887ca0) which removes apport's dependency on python3-requests. It's similar to a change that was merged into software-properties recently: https://code.launchpad.net/~slingamn/software-properties/+git /software-properties/+merge/389182 Thanks for your time! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1903605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914839] Re: package upgrade should replace /etc/ssl/certs/ca-certificates.crt atomically
** Changed in: ca-certificates (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1914839 Title: package upgrade should replace /etc/ssl/certs/ca-certificates.crt atomically Status in ca-certificates package in Ubuntu: Confirmed Status in ca-certificates package in Debian: New Bug description: While upgrading the ca-certificates package, a process got the error: SSL_ca_file /etc/ssl/certs/ca-certificates.crt does not exist This file should be replaced atomically, with no time gap where the file does not exist. (I am flagging this as a security vulnerability because, while I did not experience any security issue, I can imagine at least the possibility of this being exploitable in some way in some circumstances.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1914839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903605] Re: proposed patch: remove dependency on python3-requests
I've uploaded this for hirsute, thanks again for looking into this and providing a patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1903605 Title: proposed patch: remove dependency on python3-requests Status in apport package in Ubuntu: In Progress Bug description: I'm attaching a patch (based on 15ab343d7c887ca0) which removes apport's dependency on python3-requests. It's similar to a change that was merged into software-properties recently: https://code.launchpad.net/~slingamn/software-properties/+git /software-properties/+merge/389182 Thanks for your time! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1903605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915746] [NEW] systemd-resolved configuration does not resolve any hostnames
Public bug reported: systemd-resolved will, unter certain circumstances create local only DNS resolution: # host google.com ;; connection timed out; no servers could be reached looking at what is going on behind: # cat /etc/resolv.conf (linked to /run/resolvconf/resolv.conf) nameserver 127.0.0.1 nameserver 127.0.0.53 searchDOMAINS # systemd-resolve --status Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: foreign Current DNS Server: 127.0.0.1 DNS Servers: 127.0.0.1 DNS Domain: DOMAINS Link 2 (eth0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported DNS Domain: DOMAINS Link 3 (virbr0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 4 (vmnet1) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 5 (vmnet2) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 6 (vmnet8) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported This is a useless configuration: dnsmasq asks systemd-resolvd, systemd- resolvd asks dnsmasq. Without ever going to any of the upstream servers. One of them: systemd-resolvd or dnsmasq shall ask upstream servers. But non of them does. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Feb 15 19:16:05 2021 InstallationDate: Installed on 2014-01-31 (2572 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) MachineType: Hewlett-Packard HP Compaq 6200 Pro MT PC ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-36-generic root=UUID=de4af024-5d59-4f85-b5ca-11f17f085706 ro rootflags=subvol=@ consoleblank=0 video=DP-1:e,HDMI-1:e SourcePackage: systemd UpgradeStatus: Upgraded to hirsute on 2018-11-23 (815 days ago) dmi.bios.date: 11/10/2011 dmi.bios.release: 2.15 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.15 dmi.board.name: 1497 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:br2.15:svnHewlett-Packard:pnHPCompaq6200ProMTPC:pvr:rvnHewlett-Packard:rn1497:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 6200 Pro MT PC dmi.product.sku: XL504AV dmi.sys.vendor: Hewlett-Packard mtime.conffile..etc.systemd.resolved.conf: 2021-02-15T19:09:12.129281 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages -- 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/1915746 Title: systemd-resolved configuration does not resolve any hostnames Status in systemd package in Ubuntu: New Bug description: systemd-resolved will, unter certain circumstances create local only DNS resolution: # host google.com ;; connection timed out; no servers could be reached looking at what is going on behind: # cat /etc/resolv.conf (linked to /run/resolvconf/resolv.conf) nameserver 127.0.0.1 nameserver 127.0.0.53 searchDOMAINS # systemd-resolve --status Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: foreign Current DNS Server: 127.0.0.1 DNS Servers: 127.0.0.1 DNS Domain: DOMAINS Link 2 (eth0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported DNS Domain: DOMAINS Link 3 (virbr0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 4 (vmnet1) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 5 (vmnet2) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 6 (vmnet8) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported This is a useless configuration: dnsmasq asks systemd-resolvd, systemd-resolvd asks dnsmasq. Without ever going to any of the upstream servers. One of them: systemd-resolvd or dnsmasq shall ask upstream servers. But non of them does. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: un
[Touch-packages] [Bug 1915307] Re: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main)
Debdiff in comment #5 looks good. There was a missing double space between your email and the date in debian/changelog that was causing a lintian error. I fixed the missing space and uploaded it to hirsute. Thanks! ** Changed in: sudo (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915307 Title: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main) Status in sudo package in Ubuntu: Fix Committed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. -- Justification of patches removed from debian/patches/series -- * typo-in-classic-insults.diff * This exact patch is present in upstream version 1.9.5p2-2 * paths-in-samples.diff * This exact patch is present in upstream version 1.9.5p2-2 * Whitelist-DPKG_COLORS-environment-variable.diff * This exact patch is present in upstream version 1.9.5p2-2 * CVE-2021-23239.patch * This exact patch is NOT present in upstream version 1.9.5p2-2 * The patch is made to address a vulnerability wherein users were able to gain information about what directories existed that they should not have had access to. * Upstream version 1.9.5p2-2 addresses this vulnerability using the function sudo_edit_parent_valid in the file src/sudo_edit.c * Since the vulnerability is addressed in upstream version 1.9.5p2-2 it can safely be dropped * CVE-2021-3156-1.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-2.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-3.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-4.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-5.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * ineffective_no_root_mailer.patch * This exact patch is present in upstream version 1.9.5p2-2 under the name fix-no-root-mailer.diff Changes: * Merge from Debian unstable. (LP: #1915307) Remaining changes: - debian/rules: + use dh-autoreconf - debian/rules: stop shipping init scripts, as they are no longer necessary. - debian/rules: + compile with --without-lecture --with-tty-tickets --enable-admin-flag + install man/man8/sudo_root.8 in both flavours + install apport hooks - debian/sudo-ldap.dirs, debian/sudo.dirs: + add usr/share/apport/package-hooks - debian/sudo.pam: + Use pam_env to read /etc/environment and /etc/default/locale environment files. Reading ~/.pam_environment is not permitted due to security reasons. - debian/sudoers: + also grant admin group sudo access + include /snap/bin in the secure_path sudo (1.9.5p2-2) unstable; urgency=medium * patch from upstream repo to fix NO_ROOT_MAILER sudo (1.9.5p2-1) unstable; urgency=high * new upstream version, addresses CVE-2021-3156 sudo (1.9.5p1-1.1) unstable; urgency=high * Non-maintainer upload. * Heap-based buffer overflow (CVE-2021-3156) - Reset valid_flags to MODE_NONINTERACTIVE for sudoedit - Add sudoedit flag checks in plugin that are consistent with front-end - Fix potential buffer overflow when unescaping backslashes in user_args - Fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL - Don't assume that argv is allocated as a single flat buffer sudo (1.9.5p1-1) unstable; urgency=medium * new upstream version, closes: #980028 sudo (1.9.5-1) unstable; urgency=medium * new upstream version sudo (1.9.4p2-2ubuntu3) hirsute; urgency=medium * SECURITY UPDATE: ineffective NO_ROOT_MAILER hardening option - debian/patches/ineffective_no_root_mailer.patch: fix NO_ROOT_MAILER in plugins/sudoers/logging.c, plugins/sudoers/policy.c. - No CVE number sudo (1.9.4p2-2ubuntu2) hirsute; urgency=medium * SECURITY UPDATE: dir existence issue via sudoedit race - debian/patches/CVE-2021-23239.patch: fix potential directory existing info leak in sudoedit in src/sudo_edit.c. - CVE-2021-23239 * SECURITY UPDATE: heap-based buffer overflow - debian/patches/CVE-2021-3156-1.patch: reset valid_flags to MODE_NONINTERACTIVE for sudoedit in src/parse_args.c. - debian/patches/CVE-2021-3156-2.patch: add sudoedit flag checks in plugin in plugins/sudoers/policy.c. - debian/patches/CVE-2021-3156-3.patch: fix potential buffer overflow when unescaping backslashes in plugins/sudoers/sudoers.c. - debian/patches/C
[Touch-packages] [Bug 1915748] [NEW] dnsmasq wont resolve dns
Public bug reported: dnsmasq ist set up to resolve DNS names with a local, static file given at /etc/dnsmasq-resolv.conf: # cat /etc/dnsmasq-resolv.conf nameserver 10.161.18.34 nameserver 10.177.18.34 nameserver 10.129.90.10 nameserver 10.160.90.10 nameserver 10.161.90.10 search All servers given can be reached: # host google.com 10.161.18.34 Using domain server: Name: 10.161.18.34 Address: 10.161.18.34#53 Aliases: google.com has address 216.58.213.238 google.com has IPv6 address 2a00:1450:4005:80a::200e google.com mail is handled by 10 aspmx.l.google.com. google.com mail is handled by 40 alt3.aspmx.l.google.com. google.com mail is handled by 30 alt2.aspmx.l.google.com. google.com mail is handled by 20 alt1.aspmx.l.google.com. google.com mail is handled by 50 alt4.aspmx.l.google.com. Within /etc/resolv.conf: nameserver 127.0.0.1 search trying to resolve a name using local bound dnsmasq on any of the bound addresses: dnsmasq 24106 dnsmasq6u IPv4 184802 0t0 UDP 172.18.8.1:53 dnsmasq 24106 dnsmasq7u IPv4 184803 0t0 TCP 172.18.8.1:53 (LISTEN) dnsmasq 24106 dnsmasq9u IPv4 184805 0t0 UDP 172.18.2.1:53 dnsmasq 24106 dnsmasq 10u IPv4 184806 0t0 TCP 172.18.2.1:53 (LISTEN) dnsmasq 24106 dnsmasq 12u IPv4 184808 0t0 UDP 172.18.1.1:53 dnsmasq 24106 dnsmasq 13u IPv4 184809 0t0 TCP 172.18.1.1:53 (LISTEN) dnsmasq 24106 dnsmasq 15u IPv4 184811 0t0 UDP 127.0.0.1:53 dnsmasq 24106 dnsmasq 16u IPv4 184812 0t0 TCP 127.0.0.1:53 (LISTEN) # host google.com 127.0.0.1 ;; connection timed out; no servers could be reached # host google.com 172.18.8.1 ;; connection timed out; no servers could be reached # host google.com 172.18.1.1 ;; connection timed out; no servers could be reached # host google.com 172.18.2.1 ;; connection timed out; no servers could be reached Names wont be resolved. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: dnsmasq 2.82-1ubuntu2 [modified: etc/dnsmasq.conf] ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Feb 15 19:31:14 2021 InstallationDate: Installed on 2014-01-31 (2572 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: Upgraded to hirsute on 2018-11-23 (815 days ago) mtime.conffile..etc.default.dnsmasq: 2014-02-19T17:19:28.429595 mtime.conffile..etc.dnsmasq.conf: 2021-02-15T18:38:52.895027 ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1915748 Title: dnsmasq wont resolve dns Status in dnsmasq package in Ubuntu: New Bug description: dnsmasq ist set up to resolve DNS names with a local, static file given at /etc/dnsmasq-resolv.conf: # cat /etc/dnsmasq-resolv.conf nameserver 10.161.18.34 nameserver 10.177.18.34 nameserver 10.129.90.10 nameserver 10.160.90.10 nameserver 10.161.90.10 search All servers given can be reached: # host google.com 10.161.18.34 Using domain server: Name: 10.161.18.34 Address: 10.161.18.34#53 Aliases: google.com has address 216.58.213.238 google.com has IPv6 address 2a00:1450:4005:80a::200e google.com mail is handled by 10 aspmx.l.google.com. google.com mail is handled by 40 alt3.aspmx.l.google.com. google.com mail is handled by 30 alt2.aspmx.l.google.com. google.com mail is handled by 20 alt1.aspmx.l.google.com. google.com mail is handled by 50 alt4.aspmx.l.google.com. Within /etc/resolv.conf: nameserver 127.0.0.1 search trying to resolve a name using local bound dnsmasq on any of the bound addresses: dnsmasq 24106 dnsmasq6u IPv4 184802 0t0 UDP 172.18.8.1:53 dnsmasq 24106 dnsmasq7u IPv4 184803 0t0 TCP 172.18.8.1:53 (LISTEN) dnsmasq 24106 dnsmasq9u IPv4 184805 0t0 UDP 172.18.2.1:53 dnsmasq 24106 dnsmasq 10u IPv4 184806 0t0 TCP 172.18.2.1:53 (LISTEN) dnsmasq 24106 dnsmasq 12u IPv4 184808 0t0 UDP 172.18.1.1:53 dnsmasq 24106 dnsmasq 13u IPv4 184809 0t0 TCP 172.18.1.1:53 (LISTEN) dnsmasq 24106 dnsmasq 15u IPv4 184811 0t0 UDP 127.0.0.1:53 dnsmasq 24106 dnsmasq 16u IPv4 184812 0t0 TCP 127.0.0.1:53 (LISTEN) # host google.com 127.0.0.1 ;; connection timed out; no servers could be reached # host google.com 172.18.8.1 ;; connection timed out; no servers could be reached
[Touch-packages] [Bug 1915749] [NEW] package systemd-timesyncd 245.4-4ubuntu3.4 failed to install/upgrade: »installiertes systemd-timesyncd-Skript des Paketes post-installation«-Unterprozess gab den F
Public bug reported: upgrading from 18.04 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: systemd-timesyncd 245.4-4ubuntu3.4 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 15 19:44:38 2021 ErrorMessage: »installiertes systemd-timesyncd-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: systemd Title: package systemd-timesyncd 245.4-4ubuntu3.4 failed to install/upgrade: »installiertes systemd-timesyncd-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2021-02-15 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1915749 Title: package systemd-timesyncd 245.4-4ubuntu3.4 failed to install/upgrade: »installiertes systemd-timesyncd-Skript des Paketes post- installation«-Unterprozess gab den Fehlerwert 1 zurück Status in systemd package in Ubuntu: New Bug description: upgrading from 18.04 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: systemd-timesyncd 245.4-4ubuntu3.4 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 15 19:44:38 2021 ErrorMessage: »installiertes systemd-timesyncd-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: systemd Title: package systemd-timesyncd 245.4-4ubuntu3.4 failed to install/upgrade: »installiertes systemd-timesyncd-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2021-02-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1915749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800310] Re: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1800310 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: Confirmed Bug description: Attempting to setup up RAID 0, but during first attempt, process halted and Ubuntu 18.10 gave error mentioned in Summary ProblemType: Package DistroRelease: Ubuntu 18.10 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu13 AptOrdering: lvm2:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Oct 27 15:54:25 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1800310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383858] Re: expr-simplify optimization slows click/snap policy compilation
This MR for apparmor_parser: https://gitlab.com/apparmor/apparmor/-/merge_requests/711 helps quite a bit with accelerating the expression optimization, and actually makes it worth enabling them back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1383858 Title: expr-simplify optimization slows click/snap policy compilation Status in AppArmor: Triaged Status in apparmor package in Ubuntu: Fix Released Status in click-apparmor package in Ubuntu: Fix Released Status in apparmor package in Ubuntu RTM: Fix Released Status in click-apparmor package in Ubuntu RTM: Fix Released Bug description: AppArmor has several optimization options that can be used to help speed up policy compiles for certain types of policy. Currently, we are using expr tree simplification option by default, which has dramatic affects on policy compiles for the evince profile. However, with click profiles not using expr tree simplification (ie, adding the '-O no-expr-simplify' option) can improve click policy generation by 44% (375 vs 210 seconds). On Krillin, the difference is even more substantial: 636 vs 233 seconds (63%). Short term for rtm is to to use '-O no-expr-simplify' when compiling policy in /var/lib/apparmor/profiles but leave /etc/apparmor.d alone. We can do the same with click-apparmor. Note: the fix for bug #1385947 must be included with this fix. The long term fix is to adjust expr tree simplification to be more efficient (at least as fast as without) and drop the '-O no-expr- simplify' option. Justification: apparmor policy recompilation is not expected to happen as part of the normal user experience (see bug #1350598 for a lot of detail) and it is expected to only happen on upgrades from 14.10 to 15.04 or to fix very serious apparmor or apparmor policy bugs. None of these bugs are currently scheduled for OTA. However, *if* we ever need to fix one of these, policy will have to be recompiled. Choices: 1. do nothing for RTM since policy recompiles are expected to be rare, but do apply this change to 15.04. Policy is expected to be recompiled on upgrades to 15.04 and upgrades would use the new option 2. apply this change in OTA. This is problematic because this change alone will trigger a policy recompilation that would not otherwise be needed. Optionally, this change could accompany a severe bug fix Risk: The change consists of a small modification to the apparmor upstart job and a change to the arguments click-apparmor gives to apparmor_parser. The risk assessment is considered low because of the size of the change and the simple test case will immediately indicate if either were applied incorrectly. Test case: 1. run aa-status | wc -l and note the result 2. install the new apparmor and click-apparmor packages and verify there are no errors during installation 3. reboot 4. run aa-status | wc -l and compare to '1' 5. run 'sudo start apparmor' and make sure it finishes in a few seconds If they are the same, it indicates the upstart job is properly loading the profiles generated by click apparmor. While these changes may occur separately, landing them at the same time along with a regenerated custom tarball (for preinstalled policy) will reduce policy recompiles. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1383858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915750] [NEW] with wifi on, bluetooth speaker output sound is stuttering / garbled / jittery
You have been subscribed to a public bug: That seems to be the oldest unresolved bug around here (https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/424215) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 Uname: Linux 5.3.18-050318-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 15 19:53:07 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 InstallationDate: Installed on 2019-04-10 (677 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.18-050318-generic root=UUID=8cd56bb5-4fcb-4c5b-a4ba-f5dd560e9f9c ro elevator=noop alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-20 (117 days ago) dmi.bios.date: 03/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 00FK8Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd03/06/2019:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn00FK8Y:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 0885 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 98:2C:BC:39:1F:29 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:538991 acl:390 sco:2748 events:51466 errors:0 TX bytes:24976655 acl:37033 sco:2712 commands:14348 errors:0 modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.bluetooth.main.conf: 2019-05-01T23:43:26.699874 mtime.conffile..etc.default.apport: 2019-04-24T22:54:58.031610 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- with wifi on, bluetooth speaker output sound is stuttering / garbled / jittery https://bugs.launchpad.net/bugs/1915750 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915750] Re: with wifi on, bluetooth speaker output sound is stuttering / garbled / jittery
** Package changed: ubuntu => bluez (Ubuntu) -- 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/1915750 Title: with wifi on, bluetooth speaker output sound is stuttering / garbled / jittery Status in bluez package in Ubuntu: New Bug description: That seems to be the oldest unresolved bug around here (https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/424215) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 Uname: Linux 5.3.18-050318-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 15 19:53:07 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 InstallationDate: Installed on 2019-04-10 (677 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.18-050318-generic root=UUID=8cd56bb5-4fcb-4c5b-a4ba-f5dd560e9f9c ro elevator=noop alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-20 (117 days ago) dmi.bios.date: 03/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 00FK8Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd03/06/2019:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn00FK8Y:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 0885 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:39:1F:29 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:538991 acl:390 sco:2748 events:51466 errors:0 TX bytes:24976655 acl:37033 sco:2712 commands:14348 errors:0 modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.bluetooth.main.conf: 2019-05-01T23:43:26.699874 mtime.conffile..etc.default.apport: 2019-04-24T22:54:58.031610 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1915750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903605] Re: proposed patch: remove dependency on python3-requests
The attachment "norequests.diff" 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1903605 Title: proposed patch: remove dependency on python3-requests Status in apport package in Ubuntu: In Progress Bug description: I'm attaching a patch (based on 15ab343d7c887ca0) which removes apport's dependency on python3-requests. It's similar to a change that was merged into software-properties recently: https://code.launchpad.net/~slingamn/software-properties/+git /software-properties/+merge/389182 Thanks for your time! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1903605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915759] [NEW] error: /etc/logrotate.conf:22 duplicate log entry for /var/log/wtmp
Public bug reported:
The cron.daily job reports an error running logrotate:
/etc/cron.daily/logrotate:
error: /etc/logrotate.conf:22 duplicate log entry for /var/log/wtmp
There is a duplicate entry for "wtmp" in:
/etc/logrotate.conf
/etc/logrotate.d/wtmp
Fix: Comment out the entry in /etc/logrotate.conf
root@sei:/etc# diff -Naur logrotate.conf.dist logrotate.conf
--- logrotate.conf.dist 2017-08-21 19:38:26.0 +0200
+++ logrotate.conf 2021-02-15 21:24:21.650451930 +0100
@@ -19,12 +19,12 @@
include /etc/logrotate.d
# no packages own wtmp, or btmp -- we'll rotate them here
-/var/log/wtmp {
-missingok
-monthly
-create 0664 root utmp
-rotate 1
-}
+#/var/log/wtmp {
+#missingok
+#monthly
+#create 0664 root utmp
+#rotate 1
+#}
/var/log/btmp {
missingok
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: logrotate 3.11.0-0.1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Feb 15 21:30:21 2021
InstallationDate: Installed on 2020-08-03 (196 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64
(20200423)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.logrotate.conf: 2021-02-15T21:24:21.650452
** Affects: logrotate (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1915759
Title:
error: /etc/logrotate.conf:22 duplicate log entry for /var/log/wtmp
Status in logrotate package in Ubuntu:
New
Bug description:
The cron.daily job reports an error running logrotate:
/etc/cron.daily/logrotate:
error: /etc/logrotate.conf:22 duplicate log entry for /var/log/wtmp
There is a duplicate entry for "wtmp" in:
/etc/logrotate.conf
/etc/logrotate.d/wtmp
Fix: Comment out the entry in /etc/logrotate.conf
root@sei:/etc# diff -Naur logrotate.conf.dist logrotate.conf
--- logrotate.conf.dist 2017-08-21 19:38:26.0 +0200
+++ logrotate.conf2021-02-15 21:24:21.650451930 +0100
@@ -19,12 +19,12 @@
include /etc/logrotate.d
# no packages own wtmp, or btmp -- we'll rotate them here
-/var/log/wtmp {
-missingok
-monthly
-create 0664 root utmp
-rotate 1
-}
+#/var/log/wtmp {
+#missingok
+#monthly
+#create 0664 root utmp
+#rotate 1
+#}
/var/log/btmp {
missingok
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: logrotate 3.11.0-0.1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Feb 15 21:30:21 2021
InstallationDate: Installed on 2020-08-03 (196 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64
(20200423)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.logrotate.conf: 2021-02-15T21:24:21.650452
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1915759/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
Installation of version 20.10 crashed on Acer Aspire V Nitro -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libx
[Touch-packages] [Bug 1908502] Re: [MIR] libdeflate
** No longer affects: tiff (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1908502 Title: [MIR] libdeflate Status in libdeflate package in Ubuntu: New Status in libdeflate source package in Hirsute: New Bug description: * Availability In sync with Debian, built on all architectures https://launchpad.net/ubuntu/+source/libdeflate/1.7-1 * Rationale It's a new depends of libtiff * Security There is no known security issues https://security-tracker.debian.org/tracker/source-package/libdeflate https://people.canonical.com/~ubuntu-security/cve/pkg/libdeflate.html https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libdeflate * Quality assurance The desktop team is going to subscribe to the package https://launchpad.net/ubuntu/+source/libdeflate/+bugs https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libdeflate No open reports The package enables upstream tests during the build and ships basic autopkgtests * Dependencies No universe binary dependencies * Standards compliance current 4.5.1 standards-version, debhelper compat 13, dh style simple rules * Maintenance Upstream is active, the package is maintained in Debian and in sync for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdeflate/+bug/1908502/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915759] Re: error: /etc/logrotate.conf:22 duplicate log entry for /var/log/wtmp
Same issue with /var/log/btmp and same fix: Comment out the entry in
/etc/logrotate.conf
root@sei:/etc# !diff
diff -Naur logrotate.conf.dist logrotate.conf
--- logrotate.conf.dist 2017-08-21 19:38:26.0 +0200
+++ logrotate.conf 2021-02-16 02:09:31.665145104 +0100
@@ -19,18 +19,18 @@
include /etc/logrotate.d
# no packages own wtmp, or btmp -- we'll rotate them here
-/var/log/wtmp {
-missingok
-monthly
-create 0664 root utmp
-rotate 1
-}
+#/var/log/wtmp {
+#missingok
+#monthly
+#create 0664 root utmp
+#rotate 1
+#}
-/var/log/btmp {
-missingok
-monthly
-create 0660 root utmp
-rotate 1
-}
+#/var/log/btmp {
+#missingok
+#monthly
+#create 0660 root utmp
+#rotate 1
+#}
# system-specific logs may be configured here
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1915759
Title:
error: /etc/logrotate.conf:22 duplicate log entry for /var/log/wtmp
Status in logrotate package in Ubuntu:
New
Bug description:
The cron.daily job reports an error running logrotate:
/etc/cron.daily/logrotate:
error: /etc/logrotate.conf:22 duplicate log entry for /var/log/wtmp
There is a duplicate entry for "wtmp" in:
/etc/logrotate.conf
/etc/logrotate.d/wtmp
Fix: Comment out the entry in /etc/logrotate.conf
root@sei:/etc# diff -Naur logrotate.conf.dist logrotate.conf
--- logrotate.conf.dist 2017-08-21 19:38:26.0 +0200
+++ logrotate.conf2021-02-15 21:24:21.650451930 +0100
@@ -19,12 +19,12 @@
include /etc/logrotate.d
# no packages own wtmp, or btmp -- we'll rotate them here
-/var/log/wtmp {
-missingok
-monthly
-create 0664 root utmp
-rotate 1
-}
+#/var/log/wtmp {
+#missingok
+#monthly
+#create 0664 root utmp
+#rotate 1
+#}
/var/log/btmp {
missingok
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: logrotate 3.11.0-0.1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Feb 15 21:30:21 2021
InstallationDate: Installed on 2020-08-03 (196 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64
(20200423)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.logrotate.conf: 2021-02-15T21:24:21.650452
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1915759/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915307] Re: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main)
sudo 1.9.5p2-2ubuntu1 sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915307 Title: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main) Status in sudo package in Ubuntu: Fix Committed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. -- Justification of patches removed from debian/patches/series -- * typo-in-classic-insults.diff * This exact patch is present in upstream version 1.9.5p2-2 * paths-in-samples.diff * This exact patch is present in upstream version 1.9.5p2-2 * Whitelist-DPKG_COLORS-environment-variable.diff * This exact patch is present in upstream version 1.9.5p2-2 * CVE-2021-23239.patch * This exact patch is NOT present in upstream version 1.9.5p2-2 * The patch is made to address a vulnerability wherein users were able to gain information about what directories existed that they should not have had access to. * Upstream version 1.9.5p2-2 addresses this vulnerability using the function sudo_edit_parent_valid in the file src/sudo_edit.c * Since the vulnerability is addressed in upstream version 1.9.5p2-2 it can safely be dropped * CVE-2021-3156-1.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-2.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-3.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-4.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-5.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * ineffective_no_root_mailer.patch * This exact patch is present in upstream version 1.9.5p2-2 under the name fix-no-root-mailer.diff Changes: * Merge from Debian unstable. (LP: #1915307) Remaining changes: - debian/rules: + use dh-autoreconf - debian/rules: stop shipping init scripts, as they are no longer necessary. - debian/rules: + compile with --without-lecture --with-tty-tickets --enable-admin-flag + install man/man8/sudo_root.8 in both flavours + install apport hooks - debian/sudo-ldap.dirs, debian/sudo.dirs: + add usr/share/apport/package-hooks - debian/sudo.pam: + Use pam_env to read /etc/environment and /etc/default/locale environment files. Reading ~/.pam_environment is not permitted due to security reasons. - debian/sudoers: + also grant admin group sudo access + include /snap/bin in the secure_path sudo (1.9.5p2-2) unstable; urgency=medium * patch from upstream repo to fix NO_ROOT_MAILER sudo (1.9.5p2-1) unstable; urgency=high * new upstream version, addresses CVE-2021-3156 sudo (1.9.5p1-1.1) unstable; urgency=high * Non-maintainer upload. * Heap-based buffer overflow (CVE-2021-3156) - Reset valid_flags to MODE_NONINTERACTIVE for sudoedit - Add sudoedit flag checks in plugin that are consistent with front-end - Fix potential buffer overflow when unescaping backslashes in user_args - Fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL - Don't assume that argv is allocated as a single flat buffer sudo (1.9.5p1-1) unstable; urgency=medium * new upstream version, closes: #980028 sudo (1.9.5-1) unstable; urgency=medium * new upstream version sudo (1.9.4p2-2ubuntu3) hirsute; urgency=medium * SECURITY UPDATE: ineffective NO_ROOT_MAILER hardening option - debian/patches/ineffective_no_root_mailer.patch: fix NO_ROOT_MAILER in plugins/sudoers/logging.c, plugins/sudoers/policy.c. - No CVE number sudo (1.9.4p2-2ubuntu2) hirsute; urgency=medium * SECURITY UPDATE: dir existence issue via sudoedit race - debian/patches/CVE-2021-23239.patch: fix potential directory existing info leak in sudoedit in src/sudo_edit.c. - CVE-2021-23239 * SECURITY UPDATE: heap-based buffer overflow - debian/patches/CVE-2021-3156-1.patch: reset valid_flags to MODE_NONINTERACTIVE for sudoedit in src/parse_args.c. - debian/patches/CVE-2021-3156-2.patch: add sudoedit flag checks in plugin in plugins/sudoers/policy.c. - debian/patches/CVE-2021-3156-3.patch: fix potential buffer overflow when unescaping backslashes in plugins/sudoers/sudoers.c. - debian/patches/CVE-2021-3156-4.patch: fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL in plugins/sudoers/timestamp.c. - debian/patches/CVE-2021-3156-5.patch: don't as
[Touch-packages] [Bug 1915307] Re: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main)
@iLogin - this is likely caused by https://bugs.launchpad.net/ubuntu/+source/fakeroot/+bug/1915250 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915307 Title: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main) Status in sudo package in Ubuntu: Fix Committed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. -- Justification of patches removed from debian/patches/series -- * typo-in-classic-insults.diff * This exact patch is present in upstream version 1.9.5p2-2 * paths-in-samples.diff * This exact patch is present in upstream version 1.9.5p2-2 * Whitelist-DPKG_COLORS-environment-variable.diff * This exact patch is present in upstream version 1.9.5p2-2 * CVE-2021-23239.patch * This exact patch is NOT present in upstream version 1.9.5p2-2 * The patch is made to address a vulnerability wherein users were able to gain information about what directories existed that they should not have had access to. * Upstream version 1.9.5p2-2 addresses this vulnerability using the function sudo_edit_parent_valid in the file src/sudo_edit.c * Since the vulnerability is addressed in upstream version 1.9.5p2-2 it can safely be dropped * CVE-2021-3156-1.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-2.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-3.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-4.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-5.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * ineffective_no_root_mailer.patch * This exact patch is present in upstream version 1.9.5p2-2 under the name fix-no-root-mailer.diff Changes: * Merge from Debian unstable. (LP: #1915307) Remaining changes: - debian/rules: + use dh-autoreconf - debian/rules: stop shipping init scripts, as they are no longer necessary. - debian/rules: + compile with --without-lecture --with-tty-tickets --enable-admin-flag + install man/man8/sudo_root.8 in both flavours + install apport hooks - debian/sudo-ldap.dirs, debian/sudo.dirs: + add usr/share/apport/package-hooks - debian/sudo.pam: + Use pam_env to read /etc/environment and /etc/default/locale environment files. Reading ~/.pam_environment is not permitted due to security reasons. - debian/sudoers: + also grant admin group sudo access + include /snap/bin in the secure_path sudo (1.9.5p2-2) unstable; urgency=medium * patch from upstream repo to fix NO_ROOT_MAILER sudo (1.9.5p2-1) unstable; urgency=high * new upstream version, addresses CVE-2021-3156 sudo (1.9.5p1-1.1) unstable; urgency=high * Non-maintainer upload. * Heap-based buffer overflow (CVE-2021-3156) - Reset valid_flags to MODE_NONINTERACTIVE for sudoedit - Add sudoedit flag checks in plugin that are consistent with front-end - Fix potential buffer overflow when unescaping backslashes in user_args - Fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL - Don't assume that argv is allocated as a single flat buffer sudo (1.9.5p1-1) unstable; urgency=medium * new upstream version, closes: #980028 sudo (1.9.5-1) unstable; urgency=medium * new upstream version sudo (1.9.4p2-2ubuntu3) hirsute; urgency=medium * SECURITY UPDATE: ineffective NO_ROOT_MAILER hardening option - debian/patches/ineffective_no_root_mailer.patch: fix NO_ROOT_MAILER in plugins/sudoers/logging.c, plugins/sudoers/policy.c. - No CVE number sudo (1.9.4p2-2ubuntu2) hirsute; urgency=medium * SECURITY UPDATE: dir existence issue via sudoedit race - debian/patches/CVE-2021-23239.patch: fix potential directory existing info leak in sudoedit in src/sudo_edit.c. - CVE-2021-23239 * SECURITY UPDATE: heap-based buffer overflow - debian/patches/CVE-2021-3156-1.patch: reset valid_flags to MODE_NONINTERACTIVE for sudoedit in src/parse_args.c. - debian/patches/CVE-2021-3156-2.patch: add sudoedit flag checks in plugin in plugins/sudoers/policy.c. - debian/patches/CVE-2021-3156-3.patch: fix potential buffer overflow when unescaping backslashes in plugins/sudoers/sudoers.c. - debian/patches/CVE-2021-3156-4.patch: fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL in plugins/sudoers/timestamp.c. - debian/patches/CVE-2021-3156-5.patch: don't as
[Touch-packages] [Bug 1915307] Re: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main)
Yep ** Attachment added: "Screenshot_20210216_040220.png" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915307/+attachment/5464005/+files/Screenshot_20210216_040220.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915307 Title: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main) Status in sudo package in Ubuntu: Fix Committed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. -- Justification of patches removed from debian/patches/series -- * typo-in-classic-insults.diff * This exact patch is present in upstream version 1.9.5p2-2 * paths-in-samples.diff * This exact patch is present in upstream version 1.9.5p2-2 * Whitelist-DPKG_COLORS-environment-variable.diff * This exact patch is present in upstream version 1.9.5p2-2 * CVE-2021-23239.patch * This exact patch is NOT present in upstream version 1.9.5p2-2 * The patch is made to address a vulnerability wherein users were able to gain information about what directories existed that they should not have had access to. * Upstream version 1.9.5p2-2 addresses this vulnerability using the function sudo_edit_parent_valid in the file src/sudo_edit.c * Since the vulnerability is addressed in upstream version 1.9.5p2-2 it can safely be dropped * CVE-2021-3156-1.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-2.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-3.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-4.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-5.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * ineffective_no_root_mailer.patch * This exact patch is present in upstream version 1.9.5p2-2 under the name fix-no-root-mailer.diff Changes: * Merge from Debian unstable. (LP: #1915307) Remaining changes: - debian/rules: + use dh-autoreconf - debian/rules: stop shipping init scripts, as they are no longer necessary. - debian/rules: + compile with --without-lecture --with-tty-tickets --enable-admin-flag + install man/man8/sudo_root.8 in both flavours + install apport hooks - debian/sudo-ldap.dirs, debian/sudo.dirs: + add usr/share/apport/package-hooks - debian/sudo.pam: + Use pam_env to read /etc/environment and /etc/default/locale environment files. Reading ~/.pam_environment is not permitted due to security reasons. - debian/sudoers: + also grant admin group sudo access + include /snap/bin in the secure_path sudo (1.9.5p2-2) unstable; urgency=medium * patch from upstream repo to fix NO_ROOT_MAILER sudo (1.9.5p2-1) unstable; urgency=high * new upstream version, addresses CVE-2021-3156 sudo (1.9.5p1-1.1) unstable; urgency=high * Non-maintainer upload. * Heap-based buffer overflow (CVE-2021-3156) - Reset valid_flags to MODE_NONINTERACTIVE for sudoedit - Add sudoedit flag checks in plugin that are consistent with front-end - Fix potential buffer overflow when unescaping backslashes in user_args - Fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL - Don't assume that argv is allocated as a single flat buffer sudo (1.9.5p1-1) unstable; urgency=medium * new upstream version, closes: #980028 sudo (1.9.5-1) unstable; urgency=medium * new upstream version sudo (1.9.4p2-2ubuntu3) hirsute; urgency=medium * SECURITY UPDATE: ineffective NO_ROOT_MAILER hardening option - debian/patches/ineffective_no_root_mailer.patch: fix NO_ROOT_MAILER in plugins/sudoers/logging.c, plugins/sudoers/policy.c. - No CVE number sudo (1.9.4p2-2ubuntu2) hirsute; urgency=medium * SECURITY UPDATE: dir existence issue via sudoedit race - debian/patches/CVE-2021-23239.patch: fix potential directory existing info leak in sudoedit in src/sudo_edit.c. - CVE-2021-23239 * SECURITY UPDATE: heap-based buffer overflow - debian/patches/CVE-2021-3156-1.patch: reset valid_flags to MODE_NONINTERACTIVE for sudoedit in src/parse_args.c. - debian/patches/CVE-2021-3156-2.patch: add sudoedit flag checks in plugin in plugins/sudoers/policy.c. - debian/patches/CVE-2021-3156-3.patch: fix potential buffer overflow when unescaping backslashes in plugins/sudoers/sudoers.c. - debian/patches/CVE-2021-3156-4.patch: fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL in p
[Touch-packages] [Bug 1915307] Re: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main)
Confirmed the regression that iLogin sees. >From within a hirsute daily LXD container with full apt update and apt dist-upgrade done to it, with `sudo apt install -t hirsute-proposed sudo` done to get the sudo AND updated libc it requires): root@hirsute-test:~# ls -al $(which sudo) -rwsr-xr-x 1 2001 2501 190952 Feb 10 11:42 /usr/bin/sudo root@hirsute-test:~# sudo sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set Which means the package does not work as intended, and will break. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915307 Title: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main) Status in sudo package in Ubuntu: Fix Committed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. -- Justification of patches removed from debian/patches/series -- * typo-in-classic-insults.diff * This exact patch is present in upstream version 1.9.5p2-2 * paths-in-samples.diff * This exact patch is present in upstream version 1.9.5p2-2 * Whitelist-DPKG_COLORS-environment-variable.diff * This exact patch is present in upstream version 1.9.5p2-2 * CVE-2021-23239.patch * This exact patch is NOT present in upstream version 1.9.5p2-2 * The patch is made to address a vulnerability wherein users were able to gain information about what directories existed that they should not have had access to. * Upstream version 1.9.5p2-2 addresses this vulnerability using the function sudo_edit_parent_valid in the file src/sudo_edit.c * Since the vulnerability is addressed in upstream version 1.9.5p2-2 it can safely be dropped * CVE-2021-3156-1.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-2.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-3.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-4.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-5.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * ineffective_no_root_mailer.patch * This exact patch is present in upstream version 1.9.5p2-2 under the name fix-no-root-mailer.diff Changes: * Merge from Debian unstable. (LP: #1915307) Remaining changes: - debian/rules: + use dh-autoreconf - debian/rules: stop shipping init scripts, as they are no longer necessary. - debian/rules: + compile with --without-lecture --with-tty-tickets --enable-admin-flag + install man/man8/sudo_root.8 in both flavours + install apport hooks - debian/sudo-ldap.dirs, debian/sudo.dirs: + add usr/share/apport/package-hooks - debian/sudo.pam: + Use pam_env to read /etc/environment and /etc/default/locale environment files. Reading ~/.pam_environment is not permitted due to security reasons. - debian/sudoers: + also grant admin group sudo access + include /snap/bin in the secure_path sudo (1.9.5p2-2) unstable; urgency=medium * patch from upstream repo to fix NO_ROOT_MAILER sudo (1.9.5p2-1) unstable; urgency=high * new upstream version, addresses CVE-2021-3156 sudo (1.9.5p1-1.1) unstable; urgency=high * Non-maintainer upload. * Heap-based buffer overflow (CVE-2021-3156) - Reset valid_flags to MODE_NONINTERACTIVE for sudoedit - Add sudoedit flag checks in plugin that are consistent with front-end - Fix potential buffer overflow when unescaping backslashes in user_args - Fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL - Don't assume that argv is allocated as a single flat buffer sudo (1.9.5p1-1) unstable; urgency=medium * new upstream version, closes: #980028 sudo (1.9.5-1) unstable; urgency=medium * new upstream version sudo (1.9.4p2-2ubuntu3) hirsute; urgency=medium * SECURITY UPDATE: ineffective NO_ROOT_MAILER hardening option - debian/patches/ineffective_no_root_mailer.patch: fix NO_ROOT_MAILER in plugins/sudoers/logging.c, plugins/sudoers/policy.c. - No CVE number sudo (1.9.4p2-2ubuntu2) hirsute; urgency=medium * SECURITY UPDATE: dir existence issue via sudoedit race - debian/patches/CVE-2021-23239.patch: fix potential directory existing info leak in sudoedit in src/sudo_edit.c. - CVE-2021-23239 * SECURITY UPDATE: heap-based buffer overflow - debian/patches/CVE-2021-3156-1.patch: reset valid_flags to MODE_NONINTERACTIVE for sudoedit in src/parse_args.c. - debian/patches/CVE-2021-3156-2.patch: add sudoedit flag chec
[Touch-packages] [Bug 1915307] Re: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main)
The version of sudo in the repos already prior to this (1.9.4p2-2ubuntu3) works as expected, though, with proper permissions being set: root@hirsute-test:~# apt-cache policy sudo sudo: Installed: 1.9.4p2-2ubuntu3 Candidate: 1.9.4p2-2ubuntu3 Version table: 1.9.5p2-2ubuntu1 400 400 http://us.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 Packages *** 1.9.4p2-2ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status root@hirsute-test:~# ls -al $(which sudo) -rwsr-xr-x 1 root root 182760 Jan 30 19:35 /usr/bin/sudo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915307 Title: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main) Status in sudo package in Ubuntu: Fix Committed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. -- Justification of patches removed from debian/patches/series -- * typo-in-classic-insults.diff * This exact patch is present in upstream version 1.9.5p2-2 * paths-in-samples.diff * This exact patch is present in upstream version 1.9.5p2-2 * Whitelist-DPKG_COLORS-environment-variable.diff * This exact patch is present in upstream version 1.9.5p2-2 * CVE-2021-23239.patch * This exact patch is NOT present in upstream version 1.9.5p2-2 * The patch is made to address a vulnerability wherein users were able to gain information about what directories existed that they should not have had access to. * Upstream version 1.9.5p2-2 addresses this vulnerability using the function sudo_edit_parent_valid in the file src/sudo_edit.c * Since the vulnerability is addressed in upstream version 1.9.5p2-2 it can safely be dropped * CVE-2021-3156-1.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-2.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-3.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-4.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-5.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * ineffective_no_root_mailer.patch * This exact patch is present in upstream version 1.9.5p2-2 under the name fix-no-root-mailer.diff Changes: * Merge from Debian unstable. (LP: #1915307) Remaining changes: - debian/rules: + use dh-autoreconf - debian/rules: stop shipping init scripts, as they are no longer necessary. - debian/rules: + compile with --without-lecture --with-tty-tickets --enable-admin-flag + install man/man8/sudo_root.8 in both flavours + install apport hooks - debian/sudo-ldap.dirs, debian/sudo.dirs: + add usr/share/apport/package-hooks - debian/sudo.pam: + Use pam_env to read /etc/environment and /etc/default/locale environment files. Reading ~/.pam_environment is not permitted due to security reasons. - debian/sudoers: + also grant admin group sudo access + include /snap/bin in the secure_path sudo (1.9.5p2-2) unstable; urgency=medium * patch from upstream repo to fix NO_ROOT_MAILER sudo (1.9.5p2-1) unstable; urgency=high * new upstream version, addresses CVE-2021-3156 sudo (1.9.5p1-1.1) unstable; urgency=high * Non-maintainer upload. * Heap-based buffer overflow (CVE-2021-3156) - Reset valid_flags to MODE_NONINTERACTIVE for sudoedit - Add sudoedit flag checks in plugin that are consistent with front-end - Fix potential buffer overflow when unescaping backslashes in user_args - Fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL - Don't assume that argv is allocated as a single flat buffer sudo (1.9.5p1-1) unstable; urgency=medium * new upstream version, closes: #980028 sudo (1.9.5-1) unstable; urgency=medium * new upstream version sudo (1.9.4p2-2ubuntu3) hirsute; urgency=medium * SECURITY UPDATE: ineffective NO_ROOT_MAILER hardening option - debian/patches/ineffective_no_root_mailer.patch: fix NO_ROOT_MAILER in plugins/sudoers/logging.c, plugins/sudoers/policy.c. - No CVE number sudo (1.9.4p2-2ubuntu2) hirsute; urgency=medium * SECURITY UPDATE: dir existence issue via sudoedit race - debian/patches/CVE-2021-23239.patch: fix potential directory existing info leak in sudoedit in src/sudo_edit.c. - CVE-2021-23239 * SECURITY UPDATE: heap-based buffer overflow - debian/patches/CVE-2021-3156-1.patch: reset valid_flags to MODE_NONINTERACTIVE
[Touch-packages] [Bug 1903605] Re: proposed patch: remove dependency on python3-requests
I neglected to add the bug number when uploading the fix. apport (2.20.11-0ubuntu58) hirsute; urgency=medium [ Shivaram Lingamneni ] * Remove dependency on python3-requests thereby reducing memory usage of apport. ** Changed in: apport (Ubuntu) Status: In Progress => Fix Committed ** Changed in: apport (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1903605 Title: proposed patch: remove dependency on python3-requests Status in apport package in Ubuntu: Fix Released Bug description: I'm attaching a patch (based on 15ab343d7c887ca0) which removes apport's dependency on python3-requests. It's similar to a change that was merged into software-properties recently: https://code.launchpad.net/~slingamn/software-properties/+git /software-properties/+merge/389182 Thanks for your time! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1903605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915774] [NEW] Sudo owner changed to user #2001 after update
Public bug reported: This is a configuration bug that affects the hirsute-proposed version of sudo. This bug causes sudo when re-configuring, to assign to an unused user id that is neither the end user nor root. The result is that sudo will refuse to run, returning an error message that is displayed below: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set The reconfiguration is the last process that occurs in a normal update though because sudo will not be usable at this time, the su command with root password must be used instead for accessing root privileges. If you have already upgraded from hirsute-release to hirsute-proposed and you are affected by this bug, please reinstall, and in release do sudo passwd root and then configure the password for the root account and then once update use su for the time being. Once the bug is fixed however please for security reasons delete the root account and use sudo for root privelages. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sudo 1.9.5p2-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu58 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 15 20:57:37 2021 InstallationDate: Installed on 2021-02-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210215) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute package-from-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915774 Title: Sudo owner changed to user #2001 after update Status in sudo package in Ubuntu: New Bug description: This is a configuration bug that affects the hirsute-proposed version of sudo. This bug causes sudo when re-configuring, to assign to an unused user id that is neither the end user nor root. The result is that sudo will refuse to run, returning an error message that is displayed below: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set The reconfiguration is the last process that occurs in a normal update though because sudo will not be usable at this time, the su command with root password must be used instead for accessing root privileges. If you have already upgraded from hirsute-release to hirsute-proposed and you are affected by this bug, please reinstall, and in release do sudo passwd root and then configure the password for the root account and then once update use su for the time being. Once the bug is fixed however please for security reasons delete the root account and use sudo for root privelages. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sudo 1.9.5p2-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu58 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 15 20:57:37 2021 InstallationDate: Installed on 2021-02-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210215) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915777] [NEW] file owner is buildd/buildd (2001/2501) in 1.9.5p2-2ubuntu1
Public bug reported: wget http://ftp.ubuntu.com/ubuntu/pool/main/s/sudo/sudo_1.9.5p2-2ubuntu1_amd64.deb -O - | dpkg-deb -c - All the owners are buildd/buildd instead of root/root, which makes sudo unusable $ sudo sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set ** Affects: sudo (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915777 Title: file owner is buildd/buildd (2001/2501) in 1.9.5p2-2ubuntu1 Status in sudo package in Ubuntu: New Bug description: wget http://ftp.ubuntu.com/ubuntu/pool/main/s/sudo/sudo_1.9.5p2-2ubuntu1_amd64.deb -O - | dpkg-deb -c - All the owners are buildd/buildd instead of root/root, which makes sudo unusable $ sudo sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915777] Re: file owner is buildd/buildd (2001/2501) in 1.9.5p2-2ubuntu1
Many other recently updated hirsute-proposed packages also have this problem, like w3m (0.5.3+git20210102-3), net-tools (1.60+git20181103 .0eebece-1ubuntu1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915777 Title: file owner is buildd/buildd (2001/2501) in 1.9.5p2-2ubuntu1 Status in sudo package in Ubuntu: New Bug description: wget http://ftp.ubuntu.com/ubuntu/pool/main/s/sudo/sudo_1.9.5p2-2ubuntu1_amd64.deb -O - | dpkg-deb -c - All the owners are buildd/buildd instead of root/root, which makes sudo unusable $ sudo sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915779] [NEW] sudo: bad onwership of /usr/bin/sudo and /usr/lib/sudo/sudoers.so (2001:2501)
Public bug reported: After enabling the -proposed ppa in Hirsute (21.04) I'm getting the following error: ubuntu@hirsute:~$ sudo su - sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set ubuntu@hirsute:~$ ls -l /usr/bin/sudo -rwsr-xr-x 1 2001 2501 190952 Feb 10 11:42 /usr/bin/sudo I had a root session open so I could fix it by manually setting user and group ownership back to root. After that I noticed that also /usr/lib/sudo/sudoers.so had the wrong ownership: ubuntu@hirsute:~$ sudo su - sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be owned by uid 0 sudo: fatal error, unable to load plugins I manually fixed also this one and now my system seems to work normally. ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Affects: sudo (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: sudo (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915779 Title: sudo: bad onwership of /usr/bin/sudo and /usr/lib/sudo/sudoers.so (2001:2501) Status in sudo package in Ubuntu: New Status in sudo source package in Hirsute: New Bug description: After enabling the -proposed ppa in Hirsute (21.04) I'm getting the following error: ubuntu@hirsute:~$ sudo su - sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set ubuntu@hirsute:~$ ls -l /usr/bin/sudo -rwsr-xr-x 1 2001 2501 190952 Feb 10 11:42 /usr/bin/sudo I had a root session open so I could fix it by manually setting user and group ownership back to root. After that I noticed that also /usr/lib/sudo/sudoers.so had the wrong ownership: ubuntu@hirsute:~$ sudo su - sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be owned by uid 0 sudo: fatal error, unable to load plugins I manually fixed also this one and now my system seems to work normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915779] Re: sudo: bad onwership of /usr/bin/sudo and /usr/lib/sudo/sudoers.so (2001:2501)
*** This bug is a duplicate of bug 1915250 *** https://bugs.launchpad.net/bugs/1915250 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sudo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915779 Title: sudo: bad onwership of /usr/bin/sudo and /usr/lib/sudo/sudoers.so (2001:2501) Status in sudo package in Ubuntu: Confirmed Status in sudo source package in Hirsute: Confirmed Bug description: After enabling the -proposed ppa in Hirsute (21.04) I'm getting the following error: ubuntu@hirsute:~$ sudo su - sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set ubuntu@hirsute:~$ ls -l /usr/bin/sudo -rwsr-xr-x 1 2001 2501 190952 Feb 10 11:42 /usr/bin/sudo I had a root session open so I could fix it by manually setting user and group ownership back to root. After that I noticed that also /usr/lib/sudo/sudoers.so had the wrong ownership: ubuntu@hirsute:~$ sudo su - sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be owned by uid 0 sudo: fatal error, unable to load plugins I manually fixed also this one and now my system seems to work normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915779] Re: sudo: bad onwership of /usr/bin/sudo and /usr/lib/sudo/sudoers.so (2001:2501)
*** This bug is a duplicate of bug 1915250 *** https://bugs.launchpad.net/bugs/1915250 ** Changed in: sudo (Ubuntu Hirsute) Importance: Undecided => Critical ** Tags added: rls-hh-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915779 Title: sudo: bad onwership of /usr/bin/sudo and /usr/lib/sudo/sudoers.so (2001:2501) Status in sudo package in Ubuntu: Confirmed Status in sudo source package in Hirsute: Confirmed Bug description: After enabling the -proposed ppa in Hirsute (21.04) I'm getting the following error: ubuntu@hirsute:~$ sudo su - sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set ubuntu@hirsute:~$ ls -l /usr/bin/sudo -rwsr-xr-x 1 2001 2501 190952 Feb 10 11:42 /usr/bin/sudo I had a root session open so I could fix it by manually setting user and group ownership back to root. After that I noticed that also /usr/lib/sudo/sudoers.so had the wrong ownership: ubuntu@hirsute:~$ sudo su - sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be owned by uid 0 sudo: fatal error, unable to load plugins I manually fixed also this one and now my system seems to work normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915774] Re: Sudo owner changed to user #2001 after update
*** This bug is a duplicate of bug 1915250 *** https://bugs.launchpad.net/bugs/1915250 ** This bug has been marked a duplicate of bug 1915779 sudo: bad onwership of /usr/bin/sudo and /usr/lib/sudo/sudoers.so (2001:2501) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915774 Title: Sudo owner changed to user #2001 after update Status in sudo package in Ubuntu: New Bug description: This is a configuration bug that affects the hirsute-proposed version of sudo. This bug causes sudo when re-configuring, to assign to an unused user id that is neither the end user nor root. The result is that sudo will refuse to run, returning an error message that is displayed below: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set The reconfiguration is the last process that occurs in a normal update though because sudo will not be usable at this time, the su command with root password must be used instead for accessing root privileges. If you have already upgraded from hirsute-release to hirsute-proposed and you are affected by this bug, please reinstall, and in release do sudo passwd root and then configure the password for the root account and then once update use su for the time being. Once the bug is fixed however please for security reasons delete the root account and use sudo for root privelages. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sudo 1.9.5p2-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu58 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 15 20:57:37 2021 InstallationDate: Installed on 2021-02-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210215) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915779] Re: sudo: bad onwership of /usr/bin/sudo and /usr/lib/sudo/sudoers.so (2001:2501)
*** This bug is a duplicate of bug 1915250 *** https://bugs.launchpad.net/bugs/1915250 ** This bug has been marked a duplicate of bug 1915777 file owner is buildd/buildd (2001/2501) in 1.9.5p2-2ubuntu1 ** This bug is no longer a duplicate of bug 1915777 file owner is buildd/buildd (2001/2501) in 1.9.5p2-2ubuntu1 ** This bug has been marked a duplicate of bug 1915250 buildd file owner/group for shared libraries -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915779 Title: sudo: bad onwership of /usr/bin/sudo and /usr/lib/sudo/sudoers.so (2001:2501) Status in sudo package in Ubuntu: Confirmed Status in sudo source package in Hirsute: Confirmed Bug description: After enabling the -proposed ppa in Hirsute (21.04) I'm getting the following error: ubuntu@hirsute:~$ sudo su - sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set ubuntu@hirsute:~$ ls -l /usr/bin/sudo -rwsr-xr-x 1 2001 2501 190952 Feb 10 11:42 /usr/bin/sudo I had a root session open so I could fix it by manually setting user and group ownership back to root. After that I noticed that also /usr/lib/sudo/sudoers.so had the wrong ownership: ubuntu@hirsute:~$ sudo su - sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy" sudo: /usr/lib/sudo/sudoers.so must be owned by uid 0 sudo: fatal error, unable to load plugins I manually fixed also this one and now my system seems to work normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915777] Re: file owner is buildd/buildd (2001/2501) in 1.9.5p2-2ubuntu1
*** This bug is a duplicate of bug 1915250 *** https://bugs.launchpad.net/bugs/1915250 ** Changed in: sudo (Ubuntu) Importance: Undecided => Critical ** This bug has been marked a duplicate of bug 1915250 buildd file owner/group for shared libraries -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915777 Title: file owner is buildd/buildd (2001/2501) in 1.9.5p2-2ubuntu1 Status in sudo package in Ubuntu: Confirmed Bug description: wget http://ftp.ubuntu.com/ubuntu/pool/main/s/sudo/sudo_1.9.5p2-2ubuntu1_amd64.deb -O - | dpkg-deb -c - All the owners are buildd/buildd instead of root/root, which makes sudo unusable $ sudo sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915777] Re: file owner is buildd/buildd (2001/2501) in 1.9.5p2-2ubuntu1
*** This bug is a duplicate of bug 1915250 *** https://bugs.launchpad.net/bugs/1915250 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sudo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915777 Title: file owner is buildd/buildd (2001/2501) in 1.9.5p2-2ubuntu1 Status in sudo package in Ubuntu: Confirmed Bug description: wget http://ftp.ubuntu.com/ubuntu/pool/main/s/sudo/sudo_1.9.5p2-2ubuntu1_amd64.deb -O - | dpkg-deb -c - All the owners are buildd/buildd instead of root/root, which makes sudo unusable $ sudo sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915307] Re: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main)
** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915307 Title: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main) Status in sudo package in Ubuntu: Fix Committed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. -- Justification of patches removed from debian/patches/series -- * typo-in-classic-insults.diff * This exact patch is present in upstream version 1.9.5p2-2 * paths-in-samples.diff * This exact patch is present in upstream version 1.9.5p2-2 * Whitelist-DPKG_COLORS-environment-variable.diff * This exact patch is present in upstream version 1.9.5p2-2 * CVE-2021-23239.patch * This exact patch is NOT present in upstream version 1.9.5p2-2 * The patch is made to address a vulnerability wherein users were able to gain information about what directories existed that they should not have had access to. * Upstream version 1.9.5p2-2 addresses this vulnerability using the function sudo_edit_parent_valid in the file src/sudo_edit.c * Since the vulnerability is addressed in upstream version 1.9.5p2-2 it can safely be dropped * CVE-2021-3156-1.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-2.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-3.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-4.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * CVE-2021-3156-5.patch * The code from this patch already exitsts in upstream version 1.9.5p2-2 * ineffective_no_root_mailer.patch * This exact patch is present in upstream version 1.9.5p2-2 under the name fix-no-root-mailer.diff Changes: * Merge from Debian unstable. (LP: #1915307) Remaining changes: - debian/rules: + use dh-autoreconf - debian/rules: stop shipping init scripts, as they are no longer necessary. - debian/rules: + compile with --without-lecture --with-tty-tickets --enable-admin-flag + install man/man8/sudo_root.8 in both flavours + install apport hooks - debian/sudo-ldap.dirs, debian/sudo.dirs: + add usr/share/apport/package-hooks - debian/sudo.pam: + Use pam_env to read /etc/environment and /etc/default/locale environment files. Reading ~/.pam_environment is not permitted due to security reasons. - debian/sudoers: + also grant admin group sudo access + include /snap/bin in the secure_path sudo (1.9.5p2-2) unstable; urgency=medium * patch from upstream repo to fix NO_ROOT_MAILER sudo (1.9.5p2-1) unstable; urgency=high * new upstream version, addresses CVE-2021-3156 sudo (1.9.5p1-1.1) unstable; urgency=high * Non-maintainer upload. * Heap-based buffer overflow (CVE-2021-3156) - Reset valid_flags to MODE_NONINTERACTIVE for sudoedit - Add sudoedit flag checks in plugin that are consistent with front-end - Fix potential buffer overflow when unescaping backslashes in user_args - Fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL - Don't assume that argv is allocated as a single flat buffer sudo (1.9.5p1-1) unstable; urgency=medium * new upstream version, closes: #980028 sudo (1.9.5-1) unstable; urgency=medium * new upstream version sudo (1.9.4p2-2ubuntu3) hirsute; urgency=medium * SECURITY UPDATE: ineffective NO_ROOT_MAILER hardening option - debian/patches/ineffective_no_root_mailer.patch: fix NO_ROOT_MAILER in plugins/sudoers/logging.c, plugins/sudoers/policy.c. - No CVE number sudo (1.9.4p2-2ubuntu2) hirsute; urgency=medium * SECURITY UPDATE: dir existence issue via sudoedit race - debian/patches/CVE-2021-23239.patch: fix potential directory existing info leak in sudoedit in src/sudo_edit.c. - CVE-2021-23239 * SECURITY UPDATE: heap-based buffer overflow - debian/patches/CVE-2021-3156-1.patch: reset valid_flags to MODE_NONINTERACTIVE for sudoedit in src/parse_args.c. - debian/patches/CVE-2021-3156-2.patch: add sudoedit flag checks in plugin in plugins/sudoers/policy.c. - debian/patches/CVE-2021-3156-3.patch: fix potential buffer overflow when unescaping backslashes in plugins/sudoers/sudoers.c. - debian/patches/CVE-2021-3156-4.patch: fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL in plugins/sudoers/timestamp.c. - debian/patches/CVE-2021-3156-5.patch: don't assume that argv is allocated as a single flat buffer in src/pa
[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
Just FTR, note that the change in NM upstream was needed so the network- manager snap was able to correctly detect if udevd is running. We currently build the snap from the source package + some patches including this one. But, the long term target is to be able to create the snap by simply staging the network-manager debs. So, please keep this in mind and try to put back this change as soon as is feasible again, so we do not need to remove the change in the deb and then put it back in the snap. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915784] [NEW] Permissions of executables pointing to "buildd"
Public bug reported: I've noticed this issue already with other applications, which have been updated recently, too. This morning I've updated the sudo package and it broke, too. The common issue is that fakeroot gets omitted or faulty in your build environment somehow. After looking into the current sudo package I've noticed that all files are owned by "buildd:buildd", which doesn't exist on my computer and thus the 2001:2501 on my local machine. I'll try to collect some other packages, too, which have the same problem. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sudo 1.9.5p2-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu58 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 16 08:33:27 2021 InstallationDate: Installed on 2020-01-27 (385 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute package-from-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1915784 Title: Permissions of executables pointing to "buildd" Status in sudo package in Ubuntu: New Bug description: I've noticed this issue already with other applications, which have been updated recently, too. This morning I've updated the sudo package and it broke, too. The common issue is that fakeroot gets omitted or faulty in your build environment somehow. After looking into the current sudo package I've noticed that all files are owned by "buildd:buildd", which doesn't exist on my computer and thus the 2001:2501 on my local machine. I'll try to collect some other packages, too, which have the same problem. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: sudo 1.9.5p2-2ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu58 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 16 08:33:27 2021 InstallationDate: Installed on 2020-01-27 (385 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: sudo UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
