[Touch-packages] [Bug 1917298] Re: dbus-daemon not started after reboot
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1917298 Title: dbus-daemon not started after reboot Status in dbus package in Ubuntu: Expired Status in systemd package in Ubuntu: Expired Status in dbus source package in Focal: Expired Status in systemd source package in Focal: Expired Bug description: In the past weeks we experienced few systems coming up without started dbus-daemon after reboots due to updates. The first occurrence happens on January 21th 2021, since this time we were experiencing 0 up to 2 machines with this issue on each reboot cycle affecting all (approx 20) Ubuntu 20.4 (Focal Fossa) LTS machines. On January 21th the machines were rebooted due to a kernel update. On January 19th there were updates for systemd (systemd:amd64 from 245.4-4ubuntu3.3 undated to 245.4-4ubuntu3.4) installed. The Symptoms seem to be: ``` root@es1:~# systemctl status dbus ● dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enabled) Active: inactive (dead) TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) ``` There is no `dbus-daemon` process running any more after reboot. The messages in /var/log/syslog: ``` Feb 24 09:21:52 runner1 kernel: [ 11.005391] systemd[1]: sockets.target: Found ordering cycle on dbus.socket/start [...] Feb 24 09:21:52 runner1 kernel: [ 11.012386] systemd[1]: sockets.target: Job dbus.socket/start deleted to break ordering cycle starting with sockets.target/start ``` Jounalctl output ends with the dbus-Shutdown before reboot, and it is not updated any more. When rebooting the affected machine again, this does'nt occur again, and the dbus-daemon is started and working again. We experienced this on 4 rather different machines on 6 reboot cycles across all Ubuntu 20.4 (Focal Fossa) LTS machines till now. We are not experiencing this on other LTS releases than 20.4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1917298/+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 1917298] Re: dbus-daemon not started after reboot
[Expired for dbus (Ubuntu Focal) because there has been no activity for 60 days.] ** Changed in: dbus (Ubuntu Focal) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1917298 Title: dbus-daemon not started after reboot Status in dbus package in Ubuntu: Expired Status in systemd package in Ubuntu: Expired Status in dbus source package in Focal: Expired Status in systemd source package in Focal: Expired Bug description: In the past weeks we experienced few systems coming up without started dbus-daemon after reboots due to updates. The first occurrence happens on January 21th 2021, since this time we were experiencing 0 up to 2 machines with this issue on each reboot cycle affecting all (approx 20) Ubuntu 20.4 (Focal Fossa) LTS machines. On January 21th the machines were rebooted due to a kernel update. On January 19th there were updates for systemd (systemd:amd64 from 245.4-4ubuntu3.3 undated to 245.4-4ubuntu3.4) installed. The Symptoms seem to be: ``` root@es1:~# systemctl status dbus ● dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enabled) Active: inactive (dead) TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) ``` There is no `dbus-daemon` process running any more after reboot. The messages in /var/log/syslog: ``` Feb 24 09:21:52 runner1 kernel: [ 11.005391] systemd[1]: sockets.target: Found ordering cycle on dbus.socket/start [...] Feb 24 09:21:52 runner1 kernel: [ 11.012386] systemd[1]: sockets.target: Job dbus.socket/start deleted to break ordering cycle starting with sockets.target/start ``` Jounalctl output ends with the dbus-Shutdown before reboot, and it is not updated any more. When rebooting the affected machine again, this does'nt occur again, and the dbus-daemon is started and working again. We experienced this on 4 rather different machines on 6 reboot cycles across all Ubuntu 20.4 (Focal Fossa) LTS machines till now. We are not experiencing this on other LTS releases than 20.4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1917298/+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 1917298] Re: dbus-daemon not started after reboot
[Expired for dbus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: dbus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1917298 Title: dbus-daemon not started after reboot Status in dbus package in Ubuntu: Expired Status in systemd package in Ubuntu: Expired Status in dbus source package in Focal: Expired Status in systemd source package in Focal: Expired Bug description: In the past weeks we experienced few systems coming up without started dbus-daemon after reboots due to updates. The first occurrence happens on January 21th 2021, since this time we were experiencing 0 up to 2 machines with this issue on each reboot cycle affecting all (approx 20) Ubuntu 20.4 (Focal Fossa) LTS machines. On January 21th the machines were rebooted due to a kernel update. On January 19th there were updates for systemd (systemd:amd64 from 245.4-4ubuntu3.3 undated to 245.4-4ubuntu3.4) installed. The Symptoms seem to be: ``` root@es1:~# systemctl status dbus ● dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enabled) Active: inactive (dead) TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) ``` There is no `dbus-daemon` process running any more after reboot. The messages in /var/log/syslog: ``` Feb 24 09:21:52 runner1 kernel: [ 11.005391] systemd[1]: sockets.target: Found ordering cycle on dbus.socket/start [...] Feb 24 09:21:52 runner1 kernel: [ 11.012386] systemd[1]: sockets.target: Job dbus.socket/start deleted to break ordering cycle starting with sockets.target/start ``` Jounalctl output ends with the dbus-Shutdown before reboot, and it is not updated any more. When rebooting the affected machine again, this does'nt occur again, and the dbus-daemon is started and working again. We experienced this on 4 rather different machines on 6 reboot cycles across all Ubuntu 20.4 (Focal Fossa) LTS machines till now. We are not experiencing this on other LTS releases than 20.4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1917298/+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 1917298] Re: dbus-daemon not started after reboot
[Expired for systemd (Ubuntu Focal) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu Focal) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1917298 Title: dbus-daemon not started after reboot Status in dbus package in Ubuntu: Expired Status in systemd package in Ubuntu: Expired Status in dbus source package in Focal: Expired Status in systemd source package in Focal: Expired Bug description: In the past weeks we experienced few systems coming up without started dbus-daemon after reboots due to updates. The first occurrence happens on January 21th 2021, since this time we were experiencing 0 up to 2 machines with this issue on each reboot cycle affecting all (approx 20) Ubuntu 20.4 (Focal Fossa) LTS machines. On January 21th the machines were rebooted due to a kernel update. On January 19th there were updates for systemd (systemd:amd64 from 245.4-4ubuntu3.3 undated to 245.4-4ubuntu3.4) installed. The Symptoms seem to be: ``` root@es1:~# systemctl status dbus ● dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enabled) Active: inactive (dead) TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) ``` There is no `dbus-daemon` process running any more after reboot. The messages in /var/log/syslog: ``` Feb 24 09:21:52 runner1 kernel: [ 11.005391] systemd[1]: sockets.target: Found ordering cycle on dbus.socket/start [...] Feb 24 09:21:52 runner1 kernel: [ 11.012386] systemd[1]: sockets.target: Job dbus.socket/start deleted to break ordering cycle starting with sockets.target/start ``` Jounalctl output ends with the dbus-Shutdown before reboot, and it is not updated any more. When rebooting the affected machine again, this does'nt occur again, and the dbus-daemon is started and working again. We experienced this on 4 rather different machines on 6 reboot cycles across all Ubuntu 20.4 (Focal Fossa) LTS machines till now. We are not experiencing this on other LTS releases than 20.4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1917298/+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 1926050] Re: [radeon] Web benchmark freezing and crashing the system
Thanks for that. Your system log shows it was Xorg crashing in the radeon driver: mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: radeon: The kernel rejected CS, see dmesg for more information (-16). mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) Backtrace: mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 0: /usr/bin/Xwayland (OsLookupColor+0x13c) [0x563171f8122c] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fd7d0f9547f] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (__nss_database_lookup+0x44c4) [0x7fd7d0ef52e4] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 3: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x74483) [0x7fd7cf85bde3] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x7a00b) [0x7fd7cf866c8b] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x128cc) [0x7fd7cf7982fc] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x13efe) [0x7fd7cf79b1fe] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 7: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x19952) [0x7fd7cf7a6592] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 8: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (nouveau_drm_screen_create+0x214793) [0x7fd7cfd68943] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 9: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (nouveau_drm_screen_create+0x21489a) [0x7fd7cfd68c5a] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 10: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x5e6cd) [0x7fd7cf8301dd] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 11: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (__driDriverGetExtensions_zink+0x3b139) [0x7fd7cf1266c9] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 12: /usr/bin/Xwayland (glamor_get_modifiers+0x76d) [0x563171e27e3d] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 13: /usr/bin/Xwayland (XkbDDXTerminateServer+0x102) [0x563171f325c2] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 14: /usr/bin/Xwayland (XkbDDXTerminateServer+0x12cb) [0x563171f3496b] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 15: /usr/bin/Xwayland (XkbDDXTerminateServer+0x683) [0x563171f33013] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 16: /usr/bin/Xwayland (XkbDDXTerminateServer+0xc16) [0x563171f33b46] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 17: /usr/bin/Xwayland (XkbDDXTerminateServer+0x1f90) [0x563171f362b0] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 18: /usr/bin/Xwayland (SendErrorToClient+0x354) [0x563171f4a5c4] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 19: /usr/bin/Xwayland (InitFonts+0x3b4) [0x563171f4e654] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 20: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fd7d0daf0b3] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 21: /usr/bin/Xwayland (_start+0x2e) [0x563171e1c5be] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) Bus error at address 0x7fd7d07c4000 mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: Fatal server error: mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) Caught signal 7 (Bus error). Server aborting ** Summary changed: - [radeon] Web benchmark freezing and crashing the system + [radeon] Web benchmark freezing and crashing the system (Xorg crashes in Mesa's r600_dri.so) ** Package changed: linux-hwe-5.8 (Ubuntu) => mesa (Ubuntu) ** Also affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1926050 Title: [radeon] Web benchmark freezing and crashing the system (Xorg crashes in Mesa's r600_dri.so) Status in mesa package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: Expected behavior: perform the "Basemark Web 3.0" benchmark (Firefox 87 and 88), at most a loss of performance. Real behavior: the benchmark completely crashes the system in one of the initial stages (4). The screen presents graphical distortion (it never happens), intense crashes and sometimes it is solved with the automatic suspension of the computer (which remains on at times). But it doesn't usually come back from the crash.
[Touch-packages] [Bug 1926050] Re: [radeon] Web benchmark freezing and crashing the system (Xorg crashes in Mesa's r600_dri.so)
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: apport-cli YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: mesa (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1926050 Title: [radeon] Web benchmark freezing and crashing the system (Xorg crashes in Mesa's r600_dri.so) Status in mesa package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: Expected behavior: perform the "Basemark Web 3.0" benchmark (Firefox 87 and 88), at most a loss of performance. Real behavior: the benchmark completely crashes the system in one of the initial stages (4). The screen presents graphical distortion (it never happens), intense crashes and sometimes it is solved with the automatic suspension of the computer (which remains on at times). But it doesn't usually come back from the crash. The problem happens with the onboard ATI RADEON 3000 (RS780 driver) and it happens in both xorg and wayland. Ubuntu and kernel duly updated to the present date. Crash moment: WebGL 1.0.2 Test (test 4/20); "Loading scene_uv2.DAE" Benchmark website: https://web.basemark.com/ Motherboard: GA78LMT Ubuntu 20.04.2 LTS Kernel 5.8.0-50-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: poe1860 F pulseaudio /dev/snd/pcmC2D0p: poe1860 F...m pulseaudio /dev/snd/controlC0: poe1860 F pulseaudio /dev/snd/controlC1: poe1860 F pulseaudio BootLog: Error: [Errno 13] Permissão recusada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2021-03-25 15:17:02,784 DEBUG /openCache(), new cache size 67025 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2021-03-04 (51 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 Package: xorg-server (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash radeon.audio=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal wayland-session wayland-session ubuntu Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-03-25 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Touch-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
** No longer affects: sddm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa package in Fedora: Confirmed Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+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 1927993] Re: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction
*** This bug is a duplicate of bug 1922353 *** https://bugs.launchpad.net/bugs/1922353 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1922353, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) ** This bug has been marked a duplicate of bug 1922353 Overview sometimes fails to appear or disappear in 21.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1927993 Title: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction Status in gnome-shell package in Ubuntu: New Bug description: This also effects the Ubuntu Dock. Ubuntu 21.04 installed on a Micosoft Surface Go. When invoking the Activities Overview, the overview ceases to be responsive to mouse clicks or to touchscreen interaction. The only interaction to which it responds is the keyboard. Likewise, the Ubuntu Dock also ceases to respond to mouse gestures, clicks or to touchscreen interaction. Meanwhile, apps continue to respond to both Mouse and Touchscreen gestures. I haven't yet found a workaround. That said, I experimented yesterday with limiting myself to touchscreen interaction and the bug, for the period of time that used the system, didn't appear. It's possible that there's some kind of conflict between the mouse, touchscreen and Wayland usage? When used under a Xorg session, this Bug doesn't appear to affect the system. Notes: I chose Wayland as the affected passage but apparently Wayland "does not exist in Ubuntu". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927993/+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 1926050] [NEW] [radeon] Web benchmark freezing and crashing the system (Xorg crashes in Mesa's r600_dri.so)
*** This bug is a security vulnerability *** You have been subscribed to a public security bug: Expected behavior: perform the "Basemark Web 3.0" benchmark (Firefox 87 and 88), at most a loss of performance. Real behavior: the benchmark completely crashes the system in one of the initial stages (4). The screen presents graphical distortion (it never happens), intense crashes and sometimes it is solved with the automatic suspension of the computer (which remains on at times). But it doesn't usually come back from the crash. The problem happens with the onboard ATI RADEON 3000 (RS780 driver) and it happens in both xorg and wayland. Ubuntu and kernel duly updated to the present date. Crash moment: WebGL 1.0.2 Test (test 4/20); "Loading scene_uv2.DAE" Benchmark website: https://web.basemark.com/ Motherboard: GA78LMT Ubuntu 20.04.2 LTS Kernel 5.8.0-50-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: poe1860 F pulseaudio /dev/snd/pcmC2D0p: poe1860 F...m pulseaudio /dev/snd/controlC0: poe1860 F pulseaudio /dev/snd/controlC1: poe1860 F pulseaudio BootLog: Error: [Errno 13] Permissão recusada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2021-03-25 15:17:02,784 DEBUG /openCache(), new cache size 67025 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2021-03-04 (51 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 Package: xorg-server (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash radeon.audio=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal wayland-session wayland-session ubuntu Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-03-25 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd apport-collected ati basemark benchmark crash focal freeze graphics instability performance radeon rs780 ubuntu wayland-session -- [radeon] Web benchmark freezing and crashing the system (Xorg crashes in Mesa's r600_dri.so) https://bugs.launchpad.net/bugs/1926050 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa 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 1926437] Autopkgtest regression report (python-apt/1.6.5ubuntu0.6)
All autopkgtests for the newly accepted python-apt (1.6.5ubuntu0.6) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
botch/unknown (arm64)
update-manager/unknown (arm64)
apt/1.6.13 (amd64)
ubiquity/unknown (arm64)
isenkram/unknown (arm64)
python-apt/unknown (arm64)
chromium-browser/unknown (arm64)
livecd-rootfs/unknown (arm64)
aptdaemon/1.1.1+bzr982-0ubuntu19.5 (i386)
breezy-debian/unknown (arm64)
bzr-builddeb/unknown (arm64)
apport/2.20.9-0ubuntu7.23 (amd64)
software-properties/0.96.24.32.14 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#python-apt
[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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Fix Released
Status in python-apt package in Ubuntu:
New
Status in apt source package in Xenial:
Fix Released
Status in python-apt source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
Fix Committed
Status in python-apt source package in Focal:
Fix Committed
Status in python-apt source package in Groovy:
Fix Committed
Status in python-apt source package in Hirsute:
Fix Committed
Status in python-apt source package in Impish:
New
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the compressor,
and then ExtractTar fails (same for other compressors).
On hirsute, the python-apt upload also includes some new
annotations for build-dependencies, as it's a straight upload of the 2.2
stable series.
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
For hirsute, the build dependency changes will verify themselves
during the build ;)
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd
and then linking it into the configuration. The former is adding new
code, triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing
else has as stringent requirements as the test suite, so I don't
believe that is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might
open you up to security vulnerabilities in the zstd code if you pass
APT zstd compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
** Description changed: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). - There are already two customer cases from the US Army complaining about - this behavior - (https://canonical.lightning.force.com/lightning/r/Case/5004K03vkq4QAA/view - and - https://canonical.lightning.force.com/lightning/r/Case/5004K03tkbmQAA/view). + There are already two customer cases from Canonical clients complaining + about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Confirmed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to:
[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
The verification passed for focal. * On Pi 400 ** ubuntu@ubuntu:~$ apt-cache policy bluez pi-bluetooth linux-firmware-raspi2 bluez: Installed: 5.53-0ubuntu3 Candidate: 5.53-0ubuntu3.1 Version table: 5.53-0ubuntu3.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 Packages *** 5.53-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages 100 /var/lib/dpkg/status pi-bluetooth: Installed: 0.1.10ubuntu6 Candidate: 0.1.15ubuntu0~20.04.1 Version table: 0.1.15ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages *** 0.1.10ubuntu6 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages 100 /var/lib/dpkg/status linux-firmware-raspi2: Installed: 3-0ubuntu2~20.04.1 Candidate: 4-0ubuntu0~20.04.1 Version table: 4-0ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages *** 3-0ubuntu2~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse arm64 Packages 100 /var/lib/dpkg/status 1.20200212-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages ubuntu@ubuntu:~$ bluetoothctl devices No default controller available ubuntu@ubuntu:~$ apt-cache policy bluez pi-bluetooth linux-firmware-raspi2 bluez: Installed: 5.53-0ubuntu3.1 Candidate: 5.53-0ubuntu3.1 Version table: *** 5.53-0ubuntu3.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 Packages 100 /var/lib/dpkg/status 5.53-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages pi-bluetooth: Installed: 0.1.15ubuntu0~20.04.1 Candidate: 0.1.15ubuntu0~20.04.1 Version table: *** 0.1.15ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages 100 /var/lib/dpkg/status 0.1.10ubuntu6 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages linux-firmware-raspi2: Installed: 4-0ubuntu0~20.04.1 Candidate: 4-0ubuntu0~20.04.1 Version table: *** 4-0ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages 100 /var/lib/dpkg/status 3-0ubuntu2~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse arm64 Packages 1.20200212-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages ubuntu@ubuntu:~$ bluetoothctl Agent registered [CHG] Controller DC:A6:32:F6:84:4E Pairable: yes [bluetooth]# scan on Discovery started [CHG] Controller DC:A6:32:F6:84:4E Discovering: yes [NEW] Device 28:11:A5:D5:AC:98 28-11-A5-D5-AC-98 [NEW] Device 68:27:37:05:F4:ED [TV] Samsung 6 Series (55) [NEW] Device 5B:1B:6F:46:F3:00 5B-1B-6F-46-F3-00 [NEW] Device 28:11:A5:D5:CB:47 LE-reserved_M [NEW] Device 42:25:C8:1B:5F:D2 42-25-C8-1B-5F-D2 [NEW] Device 64:FF:0A:21:B1:70 64-FF-0A-21-B1-70 [CHG] Device 28:11:A5:D5:AC:98 RSSI: -62 [CHG] Device 28:11:A5:D5:AC:98 TxPower: 8 [CHG] Device 28:11:A5:D5:AC:98 Name: LE-Lemonade [CHG] Device 28:11:A5:D5:AC:98 Alias: LE-Lemonade [NEW] Device 4B:04:19:F1:60:90 4B-04-19-F1-60-90 [bluetooth]# ** On CM4 ** apt-cache policy bluez pi-bluetooth linux-firmware-raspi2 bluez: Installed: 5.53-0ubuntu3 Candidate: 5.53-0ubuntu3.1 Version table: 5.53-0ubuntu3.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 Packages *** 5.53-0ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages 100 /var/lib/dpkg/status pi-bluetooth: Installed: 0.1.10ubuntu6 Candidate: 0.1.15ubuntu0~20.04.1 Version table: 0.1.15ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages *** 0.1.10ubuntu6 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages 100 /var/lib/dpkg/status linux-firmware-raspi2: Installed: 3-0ubuntu2~20.04.1 Candidate: 4-0ubuntu0~20.04.1 Version table: 4-0ubuntu0~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/multiverse arm64 Packages *** 3-0ubuntu2~20.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse arm64 Packages 100 /var/lib/dpkg/status 1.20200212-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/multiverse arm64 Packages ubuntu@ubuntu:~$ bluetoothctl devices No default controller available ubuntu@ubuntu:~$ apt-cache policy bluez linux-firmware-raspi2 pi-bluetooth bluez: Installed: 5.53-0ubuntu3.1 Candidate: 5.53-0ubuntu3.1 Version table: *** 5.53-0ubuntu3.1 500 500 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 Packages 100 /var/lib/dpkg/status 5.53-0ubuntu3 500 500
[Touch-packages] [Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pam (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Confirmed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
** Also affects: sddm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in sddm package in Ubuntu: New Status in mesa package in Fedora: Confirmed Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+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 1926437] Autopkgtest regression report (python-apt/2.1.3ubuntu1.4)
All autopkgtests for the newly accepted python-apt (2.1.3ubuntu1.4) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
apt-clone/0.4.1ubuntu5 (armhf, ppc64el, amd64, s390x, arm64)
apt/2.1.10ubuntu0.3 (s390x)
salt/3001+dfsg1-2 (s390x)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/groovy/update_excuses.html#python-apt
[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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Fix Released
Status in python-apt package in Ubuntu:
New
Status in apt source package in Xenial:
Fix Released
Status in python-apt source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
Fix Committed
Status in python-apt source package in Focal:
Fix Committed
Status in python-apt source package in Groovy:
Fix Committed
Status in python-apt source package in Hirsute:
Fix Committed
Status in python-apt source package in Impish:
New
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the compressor,
and then ExtractTar fails (same for other compressors).
On hirsute, the python-apt upload also includes some new
annotations for build-dependencies, as it's a straight upload of the 2.2
stable series.
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
For hirsute, the build dependency changes will verify themselves
during the build ;)
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd
and then linking it into the configuration. The former is adding new
code, triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing
else has as stringent requirements as the test suite, so I don't
believe that is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might
open you up to security vulnerabilities in the zstd code if you pass
APT zstd compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+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 1927078] Re: Don't allow useradd to use fully numeric names
The Ubuntu Security team is +1 on disallowing purely numeric usernames, as they are too easily confused with UIDs. I think our preference would be to disallow leading numeric digits entirely so that for example, 0x0 and 0o0 would be blocked as well, to try to prevent both user and programmatic confusion. Probably adduser should also be made consistent with whatever change is made to useradd. The package provided adduser.conf files do have a NAME_REGEX option (in addition to the --force-badname option) but AFAICT is commented out by default (the commented out regex is "^[a-z][-a-z0-9_]*\$" but I'm not sure that's appropriate in a UTF-8 world.) It would be good to have testcase and documentation for this captured somewhere. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names Status in shadow package in Ubuntu: New Status in shadow source package in Focal: New Status in shadow source package in Groovy: New Status in shadow source package in Hirsute: New Status in shadow source package in Impish: New Bug description: [Description] Fully numeric names support in Ubuntu is inconsistent in Focal onwards because systemd does not like them[1] but are still allowed by default by useradd, leaving the session behavior in hands of the running applications. Two examples: 1. After creating a user named "0", the user can log in via ssh or console but loginctl won't create a session for it: root@focal:/home/ubuntu# useradd -m 0 root@focal:/home/ubuntu# id 0 uid=1005(0) gid=1005(0) groups=1005(0) .. 0@192.168.122.6's password: Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64) Last login: Thu Apr 8 16:17:06 2021 from 192.168.122.1 $ loginctl No sessions. $ w 16:20:09 up 4 min, 1 user, load average: 0.03, 0.14, 0.08 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT 0pts/0192.168.122.116:170.00s 0.00s 0.00s w And pam-systemd shows the following message: Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for user 0 by (uid=0) Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd initializing Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get user record: Invalid argument 2. With that same username, every successful authentication in gdm will loop back to gdm again instead of starting gnome, making the user unable to login. Making useradd fail (unless --badnames is set) when a fully numeric name is used will make the default OS behavior consistent. [Other info] - Upstream does not support fully numeric usernames - useradd has a --badnames parameter that would still allow the use of these type of names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1923479] Re: out of buffer access and Integer overflow in Exiv2
This bug was fixed in the package exiv2 - 0.27.2-8ubuntu2.2 --- exiv2 (0.27.2-8ubuntu2.2) focal-security; urgency=medium * SECURITY UPDATE: Heap buffer overflow - debian/patches/CVE-2021-3482-*.patch: fix buffer overflow in src/jp2image.cpp and adds tests test/data/poc_1522.jp2, tests/bugfixes/github/test_issue_1522.py. - debian/source/include-binaries: add poc_1522.jp2 entry. - CVE-2021-3482 * SECURITY UPDATE: An out of buffer access - debian/patches/CVE-2021-29457.patch: fix in src/jp2image.cpp (LP: #1923479) - CVE-2021-29457 * SECURITY UPDATE: Integer overflow - debian/patches/CVE-2021-29458.patch: fix in src/crwimage_int.cpp (LP: #1923479) - CVE-2021-29458 * SECURITY UPDATE: Out-of-bounds - debian/patches/CVE-2021-29470-*.patch: Add more bound checks in Jp2Image::encodeJp2Header and add some tests from/for github. - CVE-2021-29470 -- Leonidas Da Silva Barbosa Tue, 13 Apr 2021 09:49:39 -0300 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: Fix Released Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+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 1923479] Re: out of buffer access and Integer overflow in Exiv2
This bug was fixed in the package exiv2 - 0.27.3-3ubuntu1.1 --- exiv2 (0.27.3-3ubuntu1.1) hirsute-security; urgency=medium * SECURITY UPDATE: Heap buffer overflow - debian/patches/CVE-2021-3482-*.patch: fix buffer overflow in src/jp2image.cpp and adds tests test/data/poc_1522.jp2, tests/bugfixes/github/test_issue_1522.py. - debian/source/include-binaries: add poc_1522.jp2 entry. - CVE-2021-3482 * SECURITY UPDATE: An out of buffer access - debian/patches/CVE-2021-29457.patch: fix in src/jp2image.cpp (LP: #1923479) - CVE-2021-29457 * SECURITY UPDATE: Integer overflow - debian/patches/CVE-2021-29458.patch: fix in src/crwimage_int.cpp (LP: #1923479) - CVE-2021-29458 * SECURITY UPDATE: Out-of-bounds - debian/patches/CVE-2021-29470-*.patch: Add more bound checks in Jp2Image::encodeJp2Header and add some tests from/for github. - CVE-2021-29470 -- Leonidas Da Silva Barbosa Mon, 12 Apr 2021 14:47:29 -0300 ** Changed in: exiv2 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: Fix Released Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+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 1923479] Re: out of buffer access and Integer overflow in Exiv2
This bug was fixed in the package exiv2 - 0.27.3-3ubuntu0.2 --- exiv2 (0.27.3-3ubuntu0.2) groovy-security; urgency=medium * SECURITY UPDATE: Heap buffer overflow - debian/patches/CVE-2021-3482-*.patch: fix buffer overflow in src/jp2image.cpp and adds tests test/data/poc_1522.jp2, tests/bugfixes/github/test_issue_1522.py. - debian/source/include-binaries: add poc_1522.jp2 entry. - CVE-2021-3482 * SECURITY UPDATE: An out of buffer access - debian/patches/CVE-2021-29457.patch: fix in src/jp2image.cpp (LP: #1923479) - CVE-2021-29457 * SECURITY UPDATE: Integer overflow - debian/patches/CVE-2021-29458.patch: fix in src/crwimage_int.cpp (LP: #1923479) - CVE-2021-29458 * SECURITY UPDATE: Out-of-bounds - debian/patches/CVE-2021-29470-*.patch: Add more bound checks in Jp2Image::encodeJp2Header and add some tests from/for github. - CVE-2021-29470 -- Leonidas Da Silva Barbosa Mon, 12 Apr 2021 15:25:12 -0300 ** Changed in: exiv2 (Ubuntu) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-29470 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3482 ** Changed in: exiv2 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: Fix Released Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+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 1927078] Re: Don't allow useradd to use fully numeric names
** Tags added: fr-1357 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names Status in shadow package in Ubuntu: New Status in shadow source package in Focal: New Status in shadow source package in Groovy: New Status in shadow source package in Hirsute: New Status in shadow source package in Impish: New Bug description: [Description] Fully numeric names support in Ubuntu is inconsistent in Focal onwards because systemd does not like them[1] but are still allowed by default by useradd, leaving the session behavior in hands of the running applications. Two examples: 1. After creating a user named "0", the user can log in via ssh or console but loginctl won't create a session for it: root@focal:/home/ubuntu# useradd -m 0 root@focal:/home/ubuntu# id 0 uid=1005(0) gid=1005(0) groups=1005(0) .. 0@192.168.122.6's password: Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64) Last login: Thu Apr 8 16:17:06 2021 from 192.168.122.1 $ loginctl No sessions. $ w 16:20:09 up 4 min, 1 user, load average: 0.03, 0.14, 0.08 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT 0pts/0192.168.122.116:170.00s 0.00s 0.00s w And pam-systemd shows the following message: Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for user 0 by (uid=0) Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd initializing Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get user record: Invalid argument 2. With that same username, every successful authentication in gdm will loop back to gdm again instead of starting gnome, making the user unable to login. Making useradd fail (unless --badnames is set) when a fully numeric name is used will make the default OS behavior consistent. [Other info] - Upstream does not support fully numeric usernames - useradd has a --badnames parameter that would still allow the use of these type of names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1926437] Autopkgtest regression report (python-apt/2.0.0ubuntu0.20.04.5)
All autopkgtests for the newly accepted python-apt (2.0.0ubuntu0.20.04.5) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
unattended-upgrades/2.3ubuntu0.1 (armhf)
apt-clone/0.4.1ubuntu3 (ppc64el, amd64, arm64, s390x, 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/focal/update_excuses.html#python-apt
[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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Fix Released
Status in python-apt package in Ubuntu:
New
Status in apt source package in Xenial:
Fix Released
Status in python-apt source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
Fix Committed
Status in python-apt source package in Focal:
Fix Committed
Status in python-apt source package in Groovy:
Fix Committed
Status in python-apt source package in Hirsute:
Fix Committed
Status in python-apt source package in Impish:
New
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the compressor,
and then ExtractTar fails (same for other compressors).
On hirsute, the python-apt upload also includes some new
annotations for build-dependencies, as it's a straight upload of the 2.2
stable series.
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
For hirsute, the build dependency changes will verify themselves
during the build ;)
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd
and then linking it into the configuration. The former is adding new
code, triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing
else has as stringent requirements as the test suite, so I don't
believe that is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might
open you up to security vulnerabilities in the zstd code if you pass
APT zstd compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+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 1928001] [NEW] [SRU] New stable release 2.68.1
Public bug reported: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: glib2.0 (Ubuntu Hirsute) Importance: Undecided Assignee: Iain Lane (laney) Status: In Progress ** Also affects: glib2.0 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released ** Changed in: glib2.0 (Ubuntu Hirsute) Status: New => In Progress ** Changed in: glib2.0 (Ubuntu Hirsute) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1928001 Title: [SRU] New stable release 2.68.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Hirsute: In Progress Bug description: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+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 1921475] Re: [2.9.2] Commissioning does not collect correct storage information
systemd doesn't report any 'E:ID_ATA_ROTATION_RATE_RPM' value for the SCSI drive, because it's a SCSI drive, not an ATA drive. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1921475 Title: [2.9.2] Commissioning does not collect correct storage information Status in lxd: Fix Released Status in MAAS: Invalid Status in systemd package in Ubuntu: Invalid Bug description: MAAS version 2.9.2 When commissioning servers with different storage types (SSDs in a virtual disk behind RAID controller, NVMes and HDDs), but everything shows up tagged as SSD. The commissioning step 50-maas-01-commissioning is generating _incorrect_ storage info such as a random serial and it’s missing the rpm for the virtual disk (behind RAID controller) and the HDDs. The commissioning step maas-lshw generates the correct info, but is not used. I have added screenshot of storage after commission and outputs from both 50-maas-01-commissioning and maas-lshw here: https://discourse.maas.io/t/how-to-work-with-storage- tags/4344/3?u=szeestraten See https://discourse.maas.io/t/how-to-work-with-storage-tags/4344 for conversation To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1921475/+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 1927993] Re: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction
** Package changed: ubuntu => wayland (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1927993 Title: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction Status in wayland package in Ubuntu: New Bug description: This also effects the Ubuntu Dock. Ubuntu 21.04 installed on a Micosoft Surface Go. When invoking the Activities Overview, the overview ceases to be responsive to mouse clicks or to touchscreen interaction. The only interaction to which it responds is the keyboard. Likewise, the Ubuntu Dock also ceases to respond to mouse gestures, clicks or to touchscreen interaction. Meanwhile, apps continue to respond to both Mouse and Touchscreen gestures. I haven't yet found a workaround. That said, I experimented yesterday with limiting myself to touchscreen interaction and the bug, for the period of time that used the system, didn't appear. It's possible that there's some kind of conflict between the mouse, touchscreen and Wayland usage? When used under a Xorg session, this Bug doesn't appear to affect the system. Notes: I chose Wayland as the affected passage but apparently Wayland "does not exist in Ubuntu". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1927993/+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 1927993] [NEW] Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction
You have been subscribed to a public bug: This also effects the Ubuntu Dock. Ubuntu 21.04 installed on a Micosoft Surface Go. When invoking the Activities Overview, the overview ceases to be responsive to mouse clicks or to touchscreen interaction. The only interaction to which it responds is the keyboard. Likewise, the Ubuntu Dock also ceases to respond to mouse gestures, clicks or to touchscreen interaction. Meanwhile, apps continue to respond to both Mouse and Touchscreen gestures. I haven't yet found a workaround. That said, I experimented yesterday with limiting myself to touchscreen interaction and the bug, for the period of time that used the system, didn't appear. It's possible that there's some kind of conflict between the mouse, touchscreen and Wayland usage? When used under a Xorg session, this Bug doesn't appear to affect the system. Notes: I chose Wayland as the affected passage but apparently Wayland "does not exist in Ubuntu". ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction https://bugs.launchpad.net/bugs/1927993 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland 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 1927978] Re: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to db5.3 in Ubuntu. https://bugs.launchpad.net/bugs/1927978 Title: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable Status in db5.3 package in Ubuntu: New Bug description: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1927978/+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 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
ubuntu@lp1927161-h:~$ pull-lp-source openssl hirsute ... ubuntu@lp1927161-h:~$ cd openssl-1.1.1j/ ubuntu@lp1927161-h:~/openssl-1.1.1j$ dpkg-parsechangelog | grep Version Version: 1.1.1j-1ubuntu3.1 ubuntu@lp1927161-h:~/openssl-1.1.1j$ quilt pop -a ubuntu@lp1927161-h:~/openssl-1.1.1j$ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1j-1ubuntu3.1 dpkg-buildpackage: info: source distribution hirsute dpkg-buildpackage: info: source changed by Matthew Ruffell ... dpkg-buildpackage: info: binary and diff upload (original source NOT included) ubuntu@lp1927161-g:~$ pull-lp-source openssl groovy ... ubuntu@lp1927161-g:~$ cd openssl-1.1.1f/ ubuntu@lp1927161-g:~/openssl-1.1.1f$ dpkg-parsechangelog | grep Version Version: 1.1.1f-1ubuntu4.4 ubuntu@lp1927161-g:~/openssl-1.1.1f$ quilt pop -a ... ubuntu@lp1927161-g:~/openssl-1.1.1f$ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.4 dpkg-buildpackage: info: source distribution groovy dpkg-buildpackage: info: source changed by Matthew Ruffell ... dpkg-buildpackage: info: binary and diff upload (original source NOT included) ** Tags removed: verification-needed verification-needed-groovy verification-needed-hirsute ** Tags added: verification-done verification-done-groovy verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: In Progress Status in openssl source package in Groovy: Fix Committed Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: In Progress Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 Test builds are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1927161-test [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1926437] Autopkgtest regression report (python-apt/2.2.0~ubuntu0.21.04.1)
All autopkgtests for the newly accepted python-apt (2.2.0~ubuntu0.21.04.1) for
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:
apport/2.20.11-0ubuntu65 (amd64)
sshuttle/1.0.4-1ubuntu4 (ppc64el)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#python-apt
[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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Fix Released
Status in python-apt package in Ubuntu:
New
Status in apt source package in Xenial:
Fix Released
Status in python-apt source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
Fix Committed
Status in python-apt source package in Focal:
Fix Committed
Status in python-apt source package in Groovy:
Fix Committed
Status in python-apt source package in Hirsute:
Fix Committed
Status in python-apt source package in Impish:
New
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the compressor,
and then ExtractTar fails (same for other compressors).
On hirsute, the python-apt upload also includes some new
annotations for build-dependencies, as it's a straight upload of the 2.2
stable series.
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
For hirsute, the build dependency changes will verify themselves
during the build ;)
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd
and then linking it into the configuration. The former is adding new
code, triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing
else has as stringent requirements as the test suite, so I don't
believe that is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might
open you up to security vulnerabilities in the zstd code if you pass
APT zstd compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+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 1926265] Re: slapd enter in infinite loop on sched_yield syscall
Hi, yes it can occur on any machine (slave or master) with the same
configuration / OS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
New
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1923880] Re: Add support for Intel Jasper Lake, Alder Lake
This bug was fixed in the package libdrm - 2.4.105-3 --- libdrm (2.4.105-3) experimental; urgency=medium * Revert a commit causing additional dependencies to be added to *.pc.in. Also drop libpciaccess-dev from libdrm-dev Depends. -- Timo Aaltonen Sat, 08 May 2021 22:52:07 +0300 ** Changed in: libdrm (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1923880 Title: Add support for Intel Jasper Lake, Alder Lake Status in libdrm package in Ubuntu: Fix Released Status in libdrm source package in Focal: In Progress Status in libdrm source package in Hirsute: In Progress Bug description: [Impact] There is a new minor release available, which adds support for i915 Jasper Lake (JSL) and Alder Lake S (ADL-S), among other things. With this added, JSL can boot hirsute with the native driver. [Test case] Boot on JSL/ADL hardware, check that the native drm/dri driver is used (mesa support is already included). [What could go wrong] The worst case would be that the native driver would not be used anymore with this version, but there's no chance for that. -- git shortlog since 2.4.104: 6b4e956d299c6ff Bump version to 2.4.105 1d13cc1032bf66f amdgpu: add function of INFO ioctl for querying video caps 50c98335c7b4013 amdgpu: sync up amdgpu_drm.h with latest from kernel b362850689d1b00 xf86drmMode: set FB_MODIFIERS flag when modifiers are supplied a5a400c9581c3b9 tests/amdgpu: fix bo eviction test issue af871ec1a6f017b drm/tests/amdgpu: fix Metadata test failed issue 6d821612d9a4bc4 xf86drmMode: introduce drmModeGetPropertyType f5abbc303361980 test/amdgpu: remove static varible in Syncobj test cd3681976c3bbef intel: Keep libdrm working without pread/pwrite ioctls 52f05d3d896480e meson: use library() instead of shared_library(). 7d6a1759900ffde xf86drm: fix null pointer deref in drmGetBufInfo 2e67fef5f6c5870 intel: Add support for JSL a9bb32cfe1ee87f xf86drm: cap number of reported devices by drmGetDevice(2) 06844b6eaefb03c Revert "xf86drm: cap number of reported devices by drmGetDevice(2)" 632f59fcbfc790a xf86drm: warn about GEM handle reference counting 523b3658aa8efa7 xf86drmMode: add drmIsKMS 1225171bd55f65d amdgpu_drm: sync up with the latest amdgpu_drm.h based on drm-next (https://cgit.freedesktop.org/drm/drm) 3b6cfb20fb3b7dd intel: add INTEL_ADLS_IDS to the pciids list 9086ff9dafa87f9 intel: sync i915_pciids.h with kernel 869ef0e4b22b8ba amdgpu: update marketing names a43cac24db2876b Avoid some compiler errors for tests/util/pattern.c62b9a3eee9bdaaf 8cb12a2528d795c xf86drm: cap number of reported devices by drmGetDevice(2) 19f0a9cb878da5b tests/amdgpu/vcn: clean abundant codes 2315bcddd643b4b tests/amdgpu: add vcn test support for dimgrey_cavefish 10377d661a31c7a tests/amdgpu: add vcn test support for navy_flounder 5f85a6d98baba1d tests/util: Add mxsfb-drm driver 62b9a3eee9bdaaf meson: Also search for rst2man.py 10dd3eb6d5ab6c1 Use dep_rt in amdgpu/meson.build diffstat: amdgpu/amdgpu-symbols.txt|1 amdgpu/amdgpu.h | 17 +++ amdgpu/amdgpu_gpu_info.c | 15 ++ amdgpu/meson.build |4 - core-symbols.txt |1 data/amdgpu.ids |6 ++ etnaviv/meson.build |2 exynos/meson.build |2 freedreno/meson.build|2 include/drm/amdgpu_drm.h | 51 +++--- intel/i915_pciids.h | 177 +++-- intel/intel_bufmgr_gem.c | 96 - intel/intel_chipset.c|2 intel/meson.build|2 libkms/meson.build |2 meson.build |6 +- nouveau/meson.build |2 omap/meson.build |2 radeon/meson.build |2 tegra/meson.build|2 tests/amdgpu/amdgpu_test.c |6 -- tests/amdgpu/basic_tests.c | 13 +++-- tests/amdgpu/bo_tests.c |4 - tests/amdgpu/syncobj_tests.c |2 tests/amdgpu/vcn_tests.c |6 +- tests/util/kms.c |1 tests/util/pattern.c |5 -- xf86drm.c| 11 xf86drm.h| 18 +++ xf86drmMode.c| 14 +- xf86drmMode.h| 12 + 31 files changed, 365 insertions(+), 121 deletions(-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1923880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
** No longer affects: libreoffice (Ubuntu) ** Also affects: gtk+3.0 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu Hirsute) Status: New => In Progress ** Changed in: gtk+3.0 (Ubuntu Hirsute) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Hirsute: In Progress Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926843] Re: online accounts integration with fb isn't working
But can you confirm: sudo add-apt-repository ppa:folke-schwinning/personal sudo apt-get update sudo apt-get install desktop-facebook sudo apt install npm nodejs-legacy git https://snapcraft.io/install/facebook-webapp/ubuntu Its this safe as worksaground or may is get safety issue? I want replacement for linux, because windows 10 android works with facebook but did no know how becauce is hard to get to works with wine HQ or other software? Because i did not know if APT get or other repo is protected other than wrong repo to old config, because some software may be maded only because developer get money for works with other company that get money on password leaks or other. Not sure if some of apps if safe because it can come software bugs to safety also. Or is snap\apt-get safe with install apps? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: * Impact The online accounts setting are proposing a facebook item which isn't working * Test case Go to settings -> online account, browse the accounts option proposed, facebook shouldn't be in the list since it doesn't work. * Regression potential The change is to disable the facebook provider using the upstream provided build option. Check that facebook isn't listed anymore but that the other providers still are. Since it's a build option change it could fail to build so check for that as well on launchpad. Since the facebook service currently doesn't consider gnome-online- accounts as a valid client there should be no user with that provider configured. Even if there were since the service isn't working they would see a functional regression. --- Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1927978] [NEW] Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable
Public bug reported: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. ** Affects: db5.3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to db5.3 in Ubuntu. https://bugs.launchpad.net/bugs/1927978 Title: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable Status in db5.3 package in Ubuntu: New Bug description: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1927978/+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 1927978] Re: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable
Attaching patch against Debian unstable. Test builds available from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/db/+packages ** Patch added: "1-1927978.debdiff" https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1927978/+attachment/5496169/+files/1-1927978.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to db5.3 in Ubuntu. https://bugs.launchpad.net/bugs/1927978 Title: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable Status in db5.3 package in Ubuntu: New Bug description: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1927978/+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 58002] Re: Some programs create root-owned files in user $HOME when run under sudo
I know it's been a long time since the original bug was reported and the last message was posted. However, I am unable to reproduce this bug on Ubuntu 20.04.2. Perhaps that's because I already have everything mentioned here as my own user. If I rename ~/.vimrc and ~/.viminfo and then run `sudo vi /etc/apt/source.list`, then a default .vimrc and .viminfo are not created in my user directory. I can also see that there is still nothing in /etc/skel related to vim. It has been 8 years and things do change. I've only been using vim for a couple of years, so it's quite possible that the ~/.vimrc isn't created upon first running `vi` or `vim` anymore. What should we do with this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/58002 Title: Some programs create root-owned files in user $HOME when run under sudo Status in vim package in Ubuntu: Triaged Bug description: The first time I noticed this I thought I'd done something wrong. But 5 installations later, my .viminfo is always owned by root, causing certain things to malfunction or not function at all. For example I can't copy and paste text (vim-style) from one file to another, and despite my .vimrc magic my cursor is always on line 1, column 1 when I open a file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/58002/+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 1926265] Re: slapd enter in infinite loop on sched_yield syscall
Hi, I went a bit down the rabbit hole Sergio mentioned and found the
same old reports and nothing really useful. I'd also be curios to see if
the problem still occurs with the newer releases.
Did you see this happen on more that one machine/deployment?
The backtrace didn't suggest my anything, but maybe Sergio will have
better use for it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
New
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1926843] Re: online accounts integration with fb isn't working
** Description changed: + * Impact + + The online accounts setting are proposing a facebook item which isn't + working + + * Test case + + Go to settings -> online account, browse the accounts option proposed, + facebook shouldn't be in the list since it doesn't work. + + * Regression potential + + The change is to disable the facebook provider using the upstream + provided build option. Check that facebook isn't listed anymore but that + the other providers still are. Since it's a build option change it could + fail to build so check for that as well on launchpad. + + Since the facebook service currently doesn't consider gnome-online- + accounts as a valid client there should be no user with that provider + configured. Even if there were since the service isn't working they + would see a functional regression. + + --- + Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: * Impact The online accounts setting are proposing a facebook item which isn't working * Test case Go to settings -> online account, browse the accounts option proposed, facebook shouldn't be in the list since it doesn't work. * Regression potential The change is to disable the facebook provider using the upstream provided build option. Check that facebook isn't listed anymore but that the other providers still are. Since it's a build option change it could fail to build so check for that as well on launchpad. Since the facebook service currently doesn't consider gnome-online- accounts as a valid client there should be no user with that provider configured. Even if there were since the service isn't working they would see a functional regression. --- Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+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 1926843] Re: online accounts integration with fb isn't working
> its because facebook did not want to use it on linux or safety issue? no, it's the code in gnome-online-accounts which isn't properly maintained upstream at the moment, they would need to do changes to the code and follow the registration process for the service Ideally that would be fixed and enabled, but until that happens it's less misleading to not propose the option than to have one that isn't working -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted iptables-netflow into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iptables- netflow/2.4-2ubuntu0.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into
[Touch-packages] [Bug 1876035] Re: Automatically retry downloads on failures
This bug was fixed in the package apt - 2.3.3 --- apt (2.3.3) experimental; urgency=medium [ David Kalnischkies ] * Allow superfluous commas in build-dependency lines * Mark only provides from protected versioned kernel packages * Count uninstallable packages in "not upgraded" (Closes: #981535) * Reexplore providers of marked packages if some didn't satisfy before * Call MarkAndSweep only manually in apt-get for autoremove * Store versioned kernel package detectors in d-pointer [ Brian Murray ] * Fix a typo in json-hooks-protocol.md [ Julian Andres Klode ] * Temporarily Revert "2.3-only: Warn that the 0.1 protocol is deprecated" -- Julian Andres Klode Thu, 29 Apr 2021 10:43:19 +0200 ** Changed in: apt (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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1876035 Title: Automatically retry downloads on failures Status in apt package in Ubuntu: Fix Released Bug description: Hi, We operate archive.ubuntu.com as well as mirrors of it in various places. We're getting reports of various CI/CD jobs failing. Sometimes due to routing issues, issues with overloaded servers/VMs hosting archive, etc. Any chance we can make '-o Acquire::Retries=3' the default for 'apt- get update/install/dist-upgrade'? Preferably with a randomised skew between retries. Also, any chance of having apt-get retry with different IPs/hosts returned from the DNS lookup? (e.g. for archive.ubuntu.com - 91.189.88.142, 91.189.88.152, ...). Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876035/+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 1926265] Re: slapd enter in infinite loop on sched_yield syscall
** Attachment removed: "slapd backtrace during sched_yield loop"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+attachment/5495540/+files/2021070_backtrace_front02_..txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
New
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt
Hello Julian, or anyone else affected,
Accepted python-apt into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-
apt/2.0.0ubuntu0.20.04.5 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: python-apt (Ubuntu Focal)
Status: New => Fix Committed
** Tags added: verification-needed-focal
** Changed in: python-apt (Ubuntu Bionic)
Status: New => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Fix Released
Status in python-apt package in Ubuntu:
New
Status in apt source package in Xenial:
Fix Released
Status in python-apt source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
Fix Committed
Status in python-apt source package in Focal:
Fix Committed
Status in python-apt source package in Groovy:
Fix Committed
Status in python-apt source package in Hirsute:
Fix Committed
Status in python-apt source package in Impish:
New
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the compressor,
and then ExtractTar fails (same for other compressors).
On hirsute, the python-apt upload also includes some new
annotations for build-dependencies, as it's a straight upload of the 2.2
stable series.
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
For hirsute, the build dependency changes will verify themselves
during the build ;)
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd
and then linking it into the configuration. The former is adding new
code, triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing
else has as stringent requirements as the test suite, so I don't
believe that is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might
open you up to security vulnerabilities in the zstd code if you pass
APT zstd compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+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 1926437] Please test proposed package
Hello Julian, or anyone else affected,
Accepted python-apt into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-
apt/1.6.5ubuntu0.6 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.
--
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/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Fix Released
Status in python-apt package in Ubuntu:
New
Status in apt source package in Xenial:
Fix Released
Status in python-apt source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
Fix Committed
Status in python-apt source package in Focal:
Fix Committed
Status in python-apt source package in Groovy:
Fix Committed
Status in python-apt source package in Hirsute:
Fix Committed
Status in python-apt source package in Impish:
New
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the compressor,
and then ExtractTar fails (same for other compressors).
On hirsute, the python-apt upload also includes some new
annotations for build-dependencies, as it's a straight upload of the 2.2
stable series.
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
For hirsute, the build dependency changes will verify themselves
during the build ;)
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd
and then linking it into the configuration. The former is adding new
code, triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing
else has as stringent requirements as the test suite, so I don't
believe that is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might
open you up to security vulnerabilities in the zstd code if you pass
APT zstd compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+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 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt
Hello Julian, or anyone else affected,
Accepted python-apt into groovy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-
apt/2.1.3ubuntu1.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: python-apt (Ubuntu Groovy)
Status: New => Fix Committed
** Tags added: verification-needed-groovy
--
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/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Fix Released
Status in python-apt package in Ubuntu:
New
Status in apt source package in Xenial:
Fix Released
Status in python-apt source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
New
Status in python-apt source package in Focal:
New
Status in python-apt source package in Groovy:
Fix Committed
Status in python-apt source package in Hirsute:
Fix Committed
Status in python-apt source package in Impish:
New
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the compressor,
and then ExtractTar fails (same for other compressors).
On hirsute, the python-apt upload also includes some new
annotations for build-dependencies, as it's a straight upload of the 2.2
stable series.
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
For hirsute, the build dependency changes will verify themselves
during the build ;)
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd
and then linking it into the configuration. The former is adding new
code, triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing
else has as stringent requirements as the test suite, so I don't
believe that is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might
open you up to security vulnerabilities in the zstd code if you pass
APT zstd compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+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 1926254] Autopkgtest regression report (openssl/1.1.1f-1ubuntu4.4)
All autopkgtests for the newly accepted openssl (1.1.1f-1ubuntu4.4) for groovy have finished running. The following regressions have been reported in tests triggered by the package: libcrypt-ssleay-perl/0.73.06-1build3 (arm64) resource-agents/1:4.6.1-1ubuntu2 (s390x) puma/3.12.4-1ubuntu2 (arm64) uftp/4.10.2-1 (amd64) python3.8/3.8.6-1ubuntu0.2 (arm64) ecflow/5.5.1-1 (s390x) python3.9/3.9.0-5 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#openssl [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 openssl in Ubuntu. https://bugs.launchpad.net/bugs/1926254 Title: x509 Certificate verification fails when basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Committed Status in openssl source package in Groovy: Fix Committed Status in openssl source package in Hirsute: Fix Released Bug description: [Impact] In openssl 1.1.1f, the below commit was merged: commit ba4356ae4002a04e28642da60c551877eea804f7 Author: Bernd Edlinger Date: Sat Jan 4 15:54:53 2020 +0100 Subject: Fix error handling in x509v3_cache_extensions and related functions Link: https://github.com/openssl/openssl/commit/ba4356ae4002a04e28642da60c551877eea804f7 This introduced a regression which caused certificate validation to fail when certificates violate RFC 5280 [1], namely, when a certificate has "basicConstraints=CA:FALSE,pathlen:0". This combination is commonly seen by self-signed leaf certificates with an intermediate CA before the root CA. Because of this, openssl 1.1.1f rejects these certificates and they cannot be used in the system certificate store, and ssl connections fail when you try to use them to connect to a ssl endpoint. The error you see when you try verify is: $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem user1_cert.pem error 20 at 0 depth lookup: unable to get local issuer certificate error user1_cert.pem: verification failed The exact same certificates work fine on Xenial, Bionic and Hirsute. [1] https://tools.ietf.org/html/rfc5280.html [Testcase] We will create our own root CA, intermediate CA and leaf server certificate. Create necessary directories: $ mkdir reproducer $ cd reproducer $ mkdir CA Write openssl configuration files to disk for each CA and cert: $ cat << EOF >> rootCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Root-CA [ usr_cert ] basicConstraints= critical,CA:TRUE keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> subCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Sub-CA [ usr_cert ] basicConstraints= critical,CA:TRUE,pathlen:0 keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> user.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test User [ usr_cert ] basicConstraints= critical,CA:FALSE,pathlen:0 keyUsage= critical,digitalSignature,keyAgreement extendedKeyUsage= clientAuth,serverAuth subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF Then generate the necessary RSA keys and form certificates: $ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes -x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ openssl genpkey -algorithm RSA-PSS -out subCA_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config subCA.cnf -new -out subCA_req.pem -key subCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ openssl x509 -req -sha256 -in subCA_req.pem -CA CA/rootCA_cert.pem -CAkey rootCA_key.pem -out CA/subCA_cert.pem -CAserial rootCA_serial.txt -CAcreateserial -extfile subCA.cnf -extensions usr_cert -days 4380 -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $
[Touch-packages] [Bug 1927161] Autopkgtest regression report (openssl/1.1.1f-1ubuntu4.4)
All autopkgtests for the newly accepted openssl (1.1.1f-1ubuntu4.4) for groovy have finished running. The following regressions have been reported in tests triggered by the package: libcrypt-ssleay-perl/0.73.06-1build3 (arm64) resource-agents/1:4.6.1-1ubuntu2 (s390x) puma/3.12.4-1ubuntu2 (arm64) uftp/4.10.2-1 (amd64) python3.8/3.8.6-1ubuntu0.2 (arm64) ecflow/5.5.1-1 (s390x) python3.9/3.9.0-5 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#openssl [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 openssl in Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: In Progress Status in openssl source package in Groovy: Fix Committed Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: In Progress Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 Test builds are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1927161-test [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1927940] [NEW] [LINCPLUS P1, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all
Public bug reported: It's a notebook with internal audio and HDMI. The sound card cant be used at all. Pulse audio only shows "Dummy Output". Adding "options snd-hda-intel model=generic" to "/etc/modprobe.d/alsa- base.conf" shows at least the HDMI out. But internal analogue output still won't appear. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mia1766 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 10 11:55:50 2021 InstallationDate: Installed on 2021-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Eingebautes Tongerät - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mia1766 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [LINCPLUS P1, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: HW-13.3-BI-X133GRX210-040-A dmi.board.asset.tag: OEM default string inject dmi.board.name: LINCPLUS dmi.board.vendor: LINCPLUS dmi.board.version: 1.0 dmi.chassis.asset.tag: OEM default string inject dmi.chassis.type: 10 dmi.chassis.vendor: OEM default string inject dmi.chassis.version: OEM default string inject dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrHW-13.3-BI-X133GRX210-040-A:bd01/06/2021:br5.13:svnLINCPLUS:pnLINCPLUSP1:pvrOEMdefaultstringinject:rvnLINCPLUS:rnLINCPLUS:rvr1.0:cvnOEMdefaultstringinject:ct10:cvrOEMdefaultstringinject: dmi.product.family: TVE1315E dmi.product.name: LINCPLUS P1 dmi.product.sku: 1315E20201113001 dmi.product.version: OEM default string inject dmi.sys.vendor: LINCPLUS modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-05-10T11:51:26.728974 ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1927940 Title: [LINCPLUS P1, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: It's a notebook with internal audio and HDMI. The sound card cant be used at all. Pulse audio only shows "Dummy Output". Adding "options snd-hda-intel model=generic" to "/etc/modprobe.d/alsa- base.conf" shows at least the HDMI out. But internal analogue output still won't appear. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mia1766 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 10 11:55:50 2021 InstallationDate: Installed on 2021-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Eingebautes Tongerät - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mia1766 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [LINCPLUS P1, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: HW-13.3-BI-X133GRX210-040-A dmi.board.asset.tag: OEM default string inject dmi.board.name: LINCPLUS dmi.board.vendor: LINCPLUS dmi.board.version: 1.0 dmi.chassis.asset.tag: OEM default string inject dmi.chassis.type: 10 dmi.chassis.vendor: OEM default string inject dmi.chassis.version: OEM default string inject dmi.modalias:
[Touch-packages] [Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
** Changed in: openldap (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
New
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1926265] Re: slapd enter in infinite loop on sched_yield syscall
issue occured today to.
This time, I join a *full* backtrace .
** Attachment added: "2021010_backtrace_front01_FULL.txt"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+attachment/5496108/+files/2021010_backtrace_front01_FULL.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
Incomplete
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1927936] [NEW] My display is flashes
Public bug reported: All my desktop windows are flashes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 10 12:24:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad X240 [17aa:2214] InstallationDate: Installed on 2021-04-10 (29 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20AL00C6MS ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2018 dmi.bios.release: 2.44 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AL00C6MS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:br2.44:efr1.17:svnLENOVO:pn20AL00C6MS:pvrThinkPadX240:rvnLENOVO:rn20AL00C6MS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20AL00C6MS dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages 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/1927936 Title: My display is flashes Status in xorg package in Ubuntu: New Bug description: All my desktop windows are flashes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 10 12:24:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad X240 [17aa:2214] InstallationDate: Installed on 2021-04-10 (29 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20AL00C6MS ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2018 dmi.bios.release: 2.44 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AL00C6MS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:br2.44:efr1.17:svnLENOVO:pn20AL00C6MS:pvrThinkPadX240:rvnLENOVO:rn20AL00C6MS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20AL00C6MS dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx:
[Touch-packages] [Bug 1927936] Re: My display is flashes
*** This bug is a duplicate of bug 1924624 *** https://bugs.launchpad.net/bugs/1924624 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1924624, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1924624 After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge) graphics a lot of glitches render screen unusable -- 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/1927936 Title: My display is flashes Status in xorg package in Ubuntu: New Bug description: All my desktop windows are flashes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 10 12:24:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad X240 [17aa:2214] InstallationDate: Installed on 2021-04-10 (29 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20AL00C6MS ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2018 dmi.bios.release: 2.44 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AL00C6MS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:br2.44:efr1.17:svnLENOVO:pn20AL00C6MS:pvrThinkPadX240:rvnLENOVO:rn20AL00C6MS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20AL00C6MS dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1927936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, ppc64el, armhf, arm64) -> is a false negative. virtualbox-hwe is only supported on amd64 i thought. https://autopkgtest.ubuntu.com/packages/v/virtualbox https://autopkgtest.ubuntu.com/packages/v/virtualbox-hwe Suggests that to be the case. -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt
Hello Julian, or anyone else affected,
Accepted python-apt into hirsute-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/python-
apt/2.2.0~ubuntu0.21.04.1 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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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: python-apt (Ubuntu Hirsute)
Status: New => Fix Committed
** Tags removed: verification-done
** Tags added: verification-needed verification-needed-hirsute
--
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/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Fix Released
Status in python-apt package in Ubuntu:
New
Status in apt source package in Xenial:
Fix Released
Status in python-apt source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
New
Status in python-apt source package in Focal:
New
Status in python-apt source package in Groovy:
New
Status in python-apt source package in Hirsute:
Fix Committed
Status in python-apt source package in Impish:
New
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the compressor,
and then ExtractTar fails (same for other compressors).
On hirsute, the python-apt upload also includes some new
annotations for build-dependencies, as it's a straight upload of the 2.2
stable series.
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
For hirsute, the build dependency changes will verify themselves
during the build ;)
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd
and then linking it into the configuration. The former is adding new
code, triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing
else has as stringent requirements as the test suite, so I don't
believe that is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might
open you up to security vulnerabilities in the zstd code if you pass
APT zstd compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+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 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt
Weirdly there was no acceptance comment regarding python-apt for xenial,
but I confirm that the package has been accepted into xenial-proposed 10
days ago. Let's adjust the status.
Julian, what about the failing autopkgtests for python-apt? Did you have
a moment to take a look at those?
** Changed in: python-apt (Ubuntu Xenial)
Status: New => Fix Committed
--
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/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Fix Released
Status in python-apt package in Ubuntu:
New
Status in apt source package in Xenial:
Fix Released
Status in python-apt source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
New
Status in python-apt source package in Focal:
New
Status in python-apt source package in Groovy:
New
Status in python-apt source package in Hirsute:
Fix Committed
Status in python-apt source package in Impish:
New
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the compressor,
and then ExtractTar fails (same for other compressors).
On hirsute, the python-apt upload also includes some new
annotations for build-dependencies, as it's a straight upload of the 2.2
stable series.
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
For hirsute, the build dependency changes will verify themselves
during the build ;)
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd
and then linking it into the configuration. The former is adding new
code, triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing
else has as stringent requirements as the test suite, so I don't
believe that is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might
open you up to security vulnerabilities in the zstd code if you pass
APT zstd compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+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 1926254] Autopkgtest regression report (openssl/1.1.1f-1ubuntu2.4)
All autopkgtests for the newly accepted openssl (1.1.1f-1ubuntu2.4) for focal have finished running. The following regressions have been reported in tests triggered by the package: casync/2+20190213-1 (s390x) uftp/4.10.1-1 (amd64) galera-3/unknown (amd64) puma/3.12.4-1ubuntu2 (s390x, arm64) m2crypto/0.31.0-9ubuntu1 (amd64) apache2/2.4.41-4ubuntu3.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#openssl [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 openssl in Ubuntu. https://bugs.launchpad.net/bugs/1926254 Title: x509 Certificate verification fails when basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Committed Status in openssl source package in Groovy: Fix Committed Status in openssl source package in Hirsute: Fix Released Bug description: [Impact] In openssl 1.1.1f, the below commit was merged: commit ba4356ae4002a04e28642da60c551877eea804f7 Author: Bernd Edlinger Date: Sat Jan 4 15:54:53 2020 +0100 Subject: Fix error handling in x509v3_cache_extensions and related functions Link: https://github.com/openssl/openssl/commit/ba4356ae4002a04e28642da60c551877eea804f7 This introduced a regression which caused certificate validation to fail when certificates violate RFC 5280 [1], namely, when a certificate has "basicConstraints=CA:FALSE,pathlen:0". This combination is commonly seen by self-signed leaf certificates with an intermediate CA before the root CA. Because of this, openssl 1.1.1f rejects these certificates and they cannot be used in the system certificate store, and ssl connections fail when you try to use them to connect to a ssl endpoint. The error you see when you try verify is: $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem user1_cert.pem error 20 at 0 depth lookup: unable to get local issuer certificate error user1_cert.pem: verification failed The exact same certificates work fine on Xenial, Bionic and Hirsute. [1] https://tools.ietf.org/html/rfc5280.html [Testcase] We will create our own root CA, intermediate CA and leaf server certificate. Create necessary directories: $ mkdir reproducer $ cd reproducer $ mkdir CA Write openssl configuration files to disk for each CA and cert: $ cat << EOF >> rootCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Root-CA [ usr_cert ] basicConstraints= critical,CA:TRUE keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> subCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Sub-CA [ usr_cert ] basicConstraints= critical,CA:TRUE,pathlen:0 keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> user.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test User [ usr_cert ] basicConstraints= critical,CA:FALSE,pathlen:0 keyUsage= critical,digitalSignature,keyAgreement extendedKeyUsage= clientAuth,serverAuth subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF Then generate the necessary RSA keys and form certificates: $ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes -x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ openssl genpkey -algorithm RSA-PSS -out subCA_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config subCA.cnf -new -out subCA_req.pem -key subCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ openssl x509 -req -sha256 -in subCA_req.pem -CA CA/rootCA_cert.pem -CAkey rootCA_key.pem -out CA/subCA_cert.pem -CAserial rootCA_serial.txt -CAcreateserial -extfile subCA.cnf -extensions usr_cert -days 4380 -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ c_rehash CA $ openssl genpkey -algorithm RSA-PSS
[Touch-packages] [Bug 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
This bug was fixed in the package gtk+3.0 - 3.24.25-1ubuntu6 --- gtk+3.0 (3.24.25-1ubuntu6) impish; urgency=medium * debian/patches/git_imcontext.patch: - cherry pick imcontext fixes until 3.24.29 (LP: #1925379) -- Rico Tzschichholz Sat, 01 May 2021 10:01:31 +0200 ** Changed in: gtk+3.0 (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 gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927919] Re: Screen flicker, sections going dark, icons and filenames vanishing, flickering or looking jumbled up
*** This bug is a duplicate of bug 1924624 *** https://bugs.launchpad.net/bugs/1924624 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1924624, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1924624 After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge) graphics a lot of glitches render screen unusable -- 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/1927919 Title: Screen flicker, sections going dark, icons and filenames vanishing, flickering or looking jumbled up Status in xorg package in Ubuntu: New Bug description: Started about 2 weeks ago, tried reinstalling Ubuntu20lts as fix yet issue persists. I can't use terminal because whatever I type, after the third letter things vanish, or become jumbled and impossible to recognise. Attempted updating intel drivers but wasn't successful, I'm not the best at this sort of thing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 10 09:22:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20B7S0XX0L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=ba39f6c6-e11e-4a3c-abb7-d8d45b02a4a6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2014 dmi.bios.release: 2.22 dmi.bios.vendor: LENOVO dmi.bios.version: GJET72WW (2.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B7S0XX0L dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET72WW(2.22):bd02/21/2014:br2.22:efr1.9:svnLENOVO:pn20B7S0XX0L:pvrThinkPadT440:rvnLENOVO:rn20B7S0XX0L:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440 dmi.product.name: 20B7S0XX0L dmi.product.sku: LENOVO_MT_20B7_BU_Think_FM_ThinkPad T440 dmi.product.version: ThinkPad T440 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1927919/+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 1927919] [NEW] Screen flicker, sections going dark, icons and filenames vanishing, flickering or looking jumbled up
Public bug reported: Started about 2 weeks ago, tried reinstalling Ubuntu20lts as fix yet issue persists. I can't use terminal because whatever I type, after the third letter things vanish, or become jumbled and impossible to recognise. Attempted updating intel drivers but wasn't successful, I'm not the best at this sort of thing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 10 09:22:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20B7S0XX0L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=ba39f6c6-e11e-4a3c-abb7-d8d45b02a4a6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2014 dmi.bios.release: 2.22 dmi.bios.vendor: LENOVO dmi.bios.version: GJET72WW (2.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B7S0XX0L dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET72WW(2.22):bd02/21/2014:br2.22:efr1.9:svnLENOVO:pn20B7S0XX0L:pvrThinkPadT440:rvnLENOVO:rn20B7S0XX0L:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440 dmi.product.name: 20B7S0XX0L dmi.product.sku: LENOVO_MT_20B7_BU_Think_FM_ThinkPad T440 dmi.product.version: ThinkPad T440 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1927919 Title: Screen flicker, sections going dark, icons and filenames vanishing, flickering or looking jumbled up Status in xorg package in Ubuntu: New Bug description: Started about 2 weeks ago, tried reinstalling Ubuntu20lts as fix yet issue persists. I can't use terminal because whatever I type, after the third letter things vanish, or become jumbled and impossible to recognise. Attempted updating intel drivers but wasn't successful, I'm not the best at this sort of thing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 10 09:22:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20B7S0XX0L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=ba39f6c6-e11e-4a3c-abb7-d8d45b02a4a6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2014 dmi.bios.release: 2.22 dmi.bios.vendor: LENOVO dmi.bios.version: GJET72WW (2.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B7S0XX0L dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10
[Touch-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)
Yeah I thought so. The problem was obvious a while back but has been gone for a couple of months or so. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released ** Changed in: mesa (Ubuntu) Status: Incomplete => Fix Released ** Changed in: mutter (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions) Status in gnome-shell package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+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 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)
Just upgrade, I just tried Ubuntu again and I didn't get the problem this time. Looks like it's fixed in Ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions) Status in gnome-shell package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+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
