[Touch-packages] [Bug 1956915] Re: New bugfix release 21.2.6
Hi Timo, When we can expect that to be part of 'focal-updates' ? -- 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/1956915 Title: New bugfix release 21.2.6 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Status in mesa source package in Impish: Fix Committed Bug description: [Impact] This is the last point-release of the 21.2.x-series, we should put it in impish so latest bugfixes would get there, and in focal for 20.04.4 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam
Getting the same issue using Qualcomm Atheros modem on WPA university WLAN network. Confirmed that same settings and hardware work fine with Ubuntu 21.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network eduroam Status in wpa package in Ubuntu: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wpa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network eduroam Status in wpa package in Ubuntu: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1570900] Re: Unable to change display resolution
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1570900 Title: Unable to change display resolution Status in xorg package in Ubuntu: Expired Bug description: small is small, cant change the resolution ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Apr 15 10:26:37 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 4.3.36, 4.2.0-27-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2016-04-14 (0 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic root=UUID=ab5f4416-0255-4fba-9ec8-b96a805ec790 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Apr 15 10:22:15 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu9.1~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1570900/+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 1960226] Re: Ubuntu Jammy Desktop fails to boot after install
** No longer affects: systemd (Ubuntu) ** No longer affects: ubuntu-meta (Ubuntu) ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Critical -- 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/1960226 Title: Ubuntu Jammy Desktop fails to boot after install Status in gdm3 package in Ubuntu: Fix Committed Bug description: Ubuntu Jammy Desktop fails to boot after install Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07 This also affects Ubuntu Jammy Canary desktop - tested daily ISO 2022-02-07 After installing the OS and selecting reboot the system reboot fails - The vendors logo appears with the Ubuntu logo and fails to boot - I have tried this with 2 barebone machines and 1 in VirtualBox - will attach syslogs and images in a separate comment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960226/+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 1528921] Autopkgtest regression report (rsync/3.1.3-8ubuntu0.2)
All autopkgtests for the newly accepted rsync (3.1.3-8ubuntu0.2) for focal have
finished running.
The following regressions have been reported in tests triggered by the package:
dgit/9.10 (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#rsync
[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 rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync:
Unknown
Status in rsync package in Ubuntu:
Fix Released
Status in rsync source package in Bionic:
Fix Committed
Status in rsync source package in Focal:
Fix Committed
Bug description:
[Impact]
What the user suffering from this bug experiences is that the big
amount of informative messages related to the copy process with the
three spawned processes(sender, receiver and generator) exhaust the
I/O buffer and the sync gets stuck, either because there are too many
files to synchronise and/or because too many detail messages (levels
of verbose mode) have been requested in the output.
The fix, that comes from upstream and is applied there since version
3.2.0., increments the size of the receiver's I/O buffer.
[Test Plan]
This test plan is for Focal, but it's the same for Bionic.
0.Preparing the test environment:
#Preparing the container
lxc launch images:ubuntu/focal rsync-iobuffer-focal
lxc shell rsync-iobuffer-focal
apt update -y
apt upgrade -y
#Installing necessary tools
apt install rsync
#Get test cases from comments #16 and #19 on this LP bug: As test case
#16 covers both aspects (a lot of files and upper verbosity) and test
#19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19
scenario (but, please, feel to reach me it if you consider it
necessary and I'll provide the steps and bad/good scenarios).
cd /tmp/
#16
Paste the contents of https://pastebin.com/raw/ctzJJGwt:
#!/bin/bash
mkdir source_dir
pushd source_dir
dd if=/dev/zero of=source bs=600K count=1
for i in `seq 1 11500`;
do
cp -v source file_$i;
done
rm source
for i in `seq 1 10`;
do
dd if=/dev/zero of=file_large_$i bs=200M count=1
done
popd
echo "Created 11500 files with size 600K and 10 files with size 200M, try the
following command:"
echo "rsync -avvvz --delete source_dir target_dir"
in a new file script_comment16.sh
chmod +x script_comment16.sh
./script_comment16.sh
1. Bad cases (without and with using strace):
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /root/source_dir/
[sender] make_file(source_dir/file_3048,*,2)
[sender] make_file(source_dir/file_11358,*,2)
[sender] make_file(source_dir/file_5914,*,2)
[sender] make_file(source_dir/file_5880,*,2)
[sender] make_file(source_dir/file_9318,*,2)
[sender] make_file(source_dir/file_5539,*,2)
[...]
sending file_sum
false_alarms=0 hash_hits=0 matches=0
sender finished source_dir/file_10807
send_files(903, source_dir/file_10808)
send_files mapped source_dir/file_10808 of size 614400
calling match_sums source_dir/file_10808
source_dir/file_10808
It hangs here, where using strace we can see:
$ strace rsync -avvvz --delete source_dir target_dir
source_dir/file_11280
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 90112) =
90112
select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 1 (in [5], left
{tv_sec=59, tv_usec=96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"...,
1900) = 1900
select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(5, [], [4], [], {tv_sec=60, tv_usec=0}
1. Good cases:
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /tmp/source_dir/
[sender] make_file(source_dir/file_3052,*,2)
[sender] make_file(source_dir/file_1766,*,2)
[sender] make_file(source_dir/file_10466,*,2)
[sender] make_file(source_dir/file_9375,*,2)
[sender] make_file(source_dir/file_7260,*,2)
[sender] make_file(source_dir/file_5554,*,2)
[sender] make_file(source_dir/
[Touch-packages] [Bug 1960226] Re: Ubuntu Jammy Desktop fails to boot after install
** Changed in: gdm3 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1960226 Title: Ubuntu Jammy Desktop fails to boot after install Status in gdm3 package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Incomplete Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Jammy Desktop fails to boot after install Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07 This also affects Ubuntu Jammy Canary desktop - tested daily ISO 2022-02-07 After installing the OS and selecting reboot the system reboot fails - The vendors logo appears with the Ubuntu logo and fails to boot - I have tried this with 2 barebone machines and 1 in VirtualBox - will attach syslogs and images in a separate comment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960226/+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 1960448] Re: Sony WF-XB700 Bluetooth headset not detected
Thanks for the bug report. Please run these commands: lspci -k > lspci.txt lsusb > lsusb.txt journalctl -b0 > journal.txt and attach the resulting text files here. ** Summary changed: - Bluetooth headset not detected by bluetoth + Sony WF-XB700 Bluetooth headset not detected ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: gnome-bluetooth (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: Incomplete Status in gnome-bluetooth package in Ubuntu: Incomplete Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960226] Re: Ubuntu Jammy Desktop fails to boot after install
I was thinking gdm3 needed some investigation but this update was published an hour ago: https://launchpad.net/ubuntu/+source/gdm3/41.3-1ubuntu2 Fingers crossed. ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1960226 Title: Ubuntu Jammy Desktop fails to boot after install Status in gdm3 package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Incomplete Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Jammy Desktop fails to boot after install Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07 This also affects Ubuntu Jammy Canary desktop - tested daily ISO 2022-02-07 After installing the OS and selecting reboot the system reboot fails - The vendors logo appears with the Ubuntu logo and fails to boot - I have tried this with 2 barebone machines and 1 in VirtualBox - will attach syslogs and images in a separate comment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960226/+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 1960410] Re: desktop always flicking after i update processor to i7
Thanks for the bug report. It seems unlikely the flicker is caused by the new CPU. To prove that you could maybe reinstall the old one? I think more likely this is a connection problem with the analog VGA cable. Try unplugging and replugging both ends of the VGA cable. And if you can then please try a different VGA cable. If that doesn't resolve the problem then please attach a photo or video of the problem. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1960410 Title: desktop always flicking after i update processor to i7 Status in Ubuntu: Incomplete Bug description: hello Ihave issue with xorgs after i change my processor from i5 to i7 , my desktop spec is Hp elite 8200 , please help . regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 9 20:33:54 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.13.0-27-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-28-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0122] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1494] InstallationDate: Installed on 2021-08-27 (166 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Compaq 8200 Elite CMT PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=f5f901a5-ac5a-451e-a4a7-7cc65371a63a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 11/10/2011 dmi.bios.release: 2.15 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.15 dmi.board.name: 1494 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:br2.15:svnHewlett-Packard:pnHPCompaq8200EliteCMTPC:pvr:rvnHewlett-Packard:rn1494:rvr:cvnHewlett-Packard:ct6:cvr:skuXL508AV: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 8200 Elite CMT PC dmi.product.sku: XL508AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960410/+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 1960460] Re: Fails to import ZFS rpool during boot
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1960460 ** Tags added: iso-testing -- 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/1960460 Title: Fails to import ZFS rpool during boot Status in systemd package in Ubuntu: New Bug description: Fresh install using 20220202 Daily ISO with ZFS + Encryption selected from the installer The system ends up in busybox after entering the unlock key. Here is a part of the logs captured from the screen, the complete log can be found as an attachement: find: /dev/zvol/: No such file or directory /init: line 971: dirname: not found BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu2) multi-call binary. Usage: basename FILE [SUFFIX] Strip directory path and SUFFIX from FILE Please unlock disk keystore-:_ Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied mount: mounting rpool/ROOT/ubuntu_u169ph on /root// failed: Permission denied Error: 1 Failed to mount rpool/ROOT/ubuntu ui69ph on /root//. Manually mount the filesystem and exit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1960460/+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 1960460] [NEW] Fails to import ZFS rpool during boot
Public bug reported: Fresh install using 20220202 Daily ISO with ZFS + Encryption selected from the installer The system ends up in busybox after entering the unlock key. Here is a part of the logs captured from the screen, the complete log can be found as an attachement: find: /dev/zvol/: No such file or directory /init: line 971: dirname: not found BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu2) multi-call binary. Usage: basename FILE [SUFFIX] Strip directory path and SUFFIX from FILE Please unlock disk keystore-:_ Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied mount: mounting rpool/ROOT/ubuntu_u169ph on /root// failed: Permission denied Error: 1 Failed to mount rpool/ROOT/ubuntu ui69ph on /root//. Manually mount the filesystem and exit. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing jammy zfs ** Attachment added: "Boot Error Log" https://bugs.launchpad.net/bugs/1960460/+attachment/5560098/+files/jammy_boot_log.txt -- 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/1960460 Title: Fails to import ZFS rpool during boot Status in systemd package in Ubuntu: New Bug description: Fresh install using 20220202 Daily ISO with ZFS + Encryption selected from the installer The system ends up in busybox after entering the unlock key. Here is a part of the logs captured from the screen, the complete log can be found as an attachement: find: /dev/zvol/: No such file or directory /init: line 971: dirname: not found BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu2) multi-call binary. Usage: basename FILE [SUFFIX] Strip directory path and SUFFIX from FILE Please unlock disk keystore-:_ Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied mount: mounting rpool/ROOT/ubuntu_u169ph on /root// failed: Permission denied Error: 1 Failed to mount rpool/ROOT/ubuntu ui69ph on /root//. Manually mount the filesystem and exit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1960460/+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 1960458] Re: patch git_socket_dir.patch causing FTBFS in gspell
I fixed gspell and am uploading it now. If you see this issue, you can add NO_AT_BRIDGE=1 to a dh_auto_test override https://salsa.debian.org/gnome-team/gspell/-/commit/9951fca4b ** Changed in: at-spi2-core (Ubuntu) Status: New => Fix Released ** Tags added: ftbfs jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1960458 Title: patch git_socket_dir.patch causing FTBFS in gspell Status in at-spi2-core package in Ubuntu: Fix Released Bug description: With this patch applied gspell is FTBFS with the following errors: Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus: Failed to connect to socket debian/home/.cache/at-spi/bus: No such file or directory I removed the patch and rebuilt this package in a PPA. When built against this PPA, gpsell is able to build again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1960458/+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 1528921] Autopkgtest regression report (rsync/3.1.2-2.1ubuntu1.3)
All autopkgtests for the newly accepted rsync (3.1.2-2.1ubuntu1.3) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
lxc/3.0.3-0ubuntu1~18.04.1 (ppc64el)
s3ql/2.26+dfsg-4 (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#rsync
[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 rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync:
Unknown
Status in rsync package in Ubuntu:
Fix Released
Status in rsync source package in Bionic:
Fix Committed
Status in rsync source package in Focal:
Fix Committed
Bug description:
[Impact]
What the user suffering from this bug experiences is that the big
amount of informative messages related to the copy process with the
three spawned processes(sender, receiver and generator) exhaust the
I/O buffer and the sync gets stuck, either because there are too many
files to synchronise and/or because too many detail messages (levels
of verbose mode) have been requested in the output.
The fix, that comes from upstream and is applied there since version
3.2.0., increments the size of the receiver's I/O buffer.
[Test Plan]
This test plan is for Focal, but it's the same for Bionic.
0.Preparing the test environment:
#Preparing the container
lxc launch images:ubuntu/focal rsync-iobuffer-focal
lxc shell rsync-iobuffer-focal
apt update -y
apt upgrade -y
#Installing necessary tools
apt install rsync
#Get test cases from comments #16 and #19 on this LP bug: As test case
#16 covers both aspects (a lot of files and upper verbosity) and test
#19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19
scenario (but, please, feel to reach me it if you consider it
necessary and I'll provide the steps and bad/good scenarios).
cd /tmp/
#16
Paste the contents of https://pastebin.com/raw/ctzJJGwt:
#!/bin/bash
mkdir source_dir
pushd source_dir
dd if=/dev/zero of=source bs=600K count=1
for i in `seq 1 11500`;
do
cp -v source file_$i;
done
rm source
for i in `seq 1 10`;
do
dd if=/dev/zero of=file_large_$i bs=200M count=1
done
popd
echo "Created 11500 files with size 600K and 10 files with size 200M, try the
following command:"
echo "rsync -avvvz --delete source_dir target_dir"
in a new file script_comment16.sh
chmod +x script_comment16.sh
./script_comment16.sh
1. Bad cases (without and with using strace):
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /root/source_dir/
[sender] make_file(source_dir/file_3048,*,2)
[sender] make_file(source_dir/file_11358,*,2)
[sender] make_file(source_dir/file_5914,*,2)
[sender] make_file(source_dir/file_5880,*,2)
[sender] make_file(source_dir/file_9318,*,2)
[sender] make_file(source_dir/file_5539,*,2)
[...]
sending file_sum
false_alarms=0 hash_hits=0 matches=0
sender finished source_dir/file_10807
send_files(903, source_dir/file_10808)
send_files mapped source_dir/file_10808 of size 614400
calling match_sums source_dir/file_10808
source_dir/file_10808
It hangs here, where using strace we can see:
$ strace rsync -avvvz --delete source_dir target_dir
source_dir/file_11280
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 90112) =
90112
select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 1 (in [5], left
{tv_sec=59, tv_usec=96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"...,
1900) = 1900
select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(5, [], [4], [], {tv_sec=60, tv_usec=0}
1. Good cases:
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /tmp/source_dir/
[sender] make_file(source_dir/file_3052,*,2)
[sender] make_file(source_dir/file_1766,*,2)
[sender] make_file(source_dir/file_10466,*,2)
[sender] make_file(source_dir/file_9375,*,2)
[sender] make_file(source_dir/file_7260,*,2)
[sender] make_file(source_dir
[Touch-packages] [Bug 1960458] [NEW] patch git_socket_dir.patch causing FTBFS in gspell
Public bug reported: With this patch applied gspell is FTBFS with the following errors: Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus: Failed to connect to socket debian/home/.cache/at-spi/bus: No such file or directory I removed the patch and rebuilt this package in a PPA. When built against this PPA, gpsell is able to build again. ** Affects: at-spi2-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1960458 Title: patch git_socket_dir.patch causing FTBFS in gspell Status in at-spi2-core package in Ubuntu: New Bug description: With this patch applied gspell is FTBFS with the following errors: Bail out! dbind-FATAL-WARNING: Couldn't connect to accessibility bus: Failed to connect to socket debian/home/.cache/at-spi/bus: No such file or directory I removed the patch and rebuilt this package in a PPA. When built against this PPA, gpsell is able to build again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1960458/+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 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders
** Changed in: binutils Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders Status in binutils: Fix Released Status in launchpad-buildd: New Status in binutils package in Ubuntu: Fix Released Status in xen package in Ubuntu: Invalid Status in binutils source package in Jammy: Fix Released Status in xen source package in Jammy: Invalid Status in binutils package in Debian: Fix Released Bug description: FTBFS in Jammy on LP infra: https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz Related PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages Summary: - Build reliably fails on LP - Build in local sbuild works reliably on my Laptop - Build in local VM (sizing like LP builders) works (other crashes but works) - Build on AMD server (chip more similar to LP) works reliably Failing step: On Launchpad build infrastructure it breaks on ld: $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0 --heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /<>/xen/.xen.efi.0x82d04000.0 && : Segmentation fault (core dumped --- Steps to recreate (result depends on platform) # you can grab the package from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4760/+packages sudo vim /etc/apt/sources.list sudo apt update sudo apt dist-upgrade -y sudo apt build-dep xen sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts apport-retrace sudo mkdir /mnt/build sudo chmod go+w /mnt/build cd /mnt/build # copy in things from host scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 ubuntu@:/mnt/build dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0 cd xen_4.16.0 dpkg-buildpackage -i -us -uc -b --- In a jammy VM 4cpu/8G I get some avx2 crashes but the build works: Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000] Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 0x7fa98d63c2d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x7fa98d6021e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x7fa98d602509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x7fa98d6033bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x562bdaaae3bf in ?? () #6 0x7fa98d2e8fd0 in __libc_start_call_main (main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58 #7 0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, argc=8, argv=0x7ffc797f2968, init=, fini=, rtld_fini=, stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409 #8 0x562bdaaad515 in ?? () ^^ that is a different crash than on th LP builders ! And despite those crashes the build does appear to work oO?! The same crashes I see on my local sbuild runs, the full set of one build is Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in libc.so.6[7f566e74+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in libc.so.6[7fbba2571000+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in libc.so.6[7fe368044000+194000] Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 ip 7f241f455f3d sp 7ffd05c2e7c8 error 4 in libc.so.6[7f241f2e2000+194000] Jan 19 07:44:57 Keschdeichel kernel
[Touch-packages] [Bug 1958389]
Fixed mainline and 2.38 branch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders Status in binutils: Fix Released Status in launchpad-buildd: New Status in binutils package in Ubuntu: Fix Released Status in xen package in Ubuntu: Invalid Status in binutils source package in Jammy: Fix Released Status in xen source package in Jammy: Invalid Status in binutils package in Debian: Fix Released Bug description: FTBFS in Jammy on LP infra: https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz Related PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages Summary: - Build reliably fails on LP - Build in local sbuild works reliably on my Laptop - Build in local VM (sizing like LP builders) works (other crashes but works) - Build on AMD server (chip more similar to LP) works reliably Failing step: On Launchpad build infrastructure it breaks on ld: $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0 --heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 --minor-image-version=16 --major-os-version=2 --minor-os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp --build-id=sha1 -T efi.lds -N prelink.o /<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o /<>/xen/.xen.efi.0x82d04000.0 && : Segmentation fault (core dumped --- Steps to recreate (result depends on platform) # you can grab the package from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4760/+packages sudo vim /etc/apt/sources.list sudo apt update sudo apt dist-upgrade -y sudo apt build-dep xen sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts apport-retrace sudo mkdir /mnt/build sudo chmod go+w /mnt/build cd /mnt/build # copy in things from host scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 ubuntu@:/mnt/build dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0 cd xen_4.16.0 dpkg-buildpackage -i -us -uc -b --- In a jammy VM 4cpu/8G I get some avx2 crashes but the build works: Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000] Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. (gdb) bt #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #1 0x7fa98d63c2d0 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #2 0x7fa98d6021e8 in ?? () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #3 0x7fa98d602509 in coff_write_alien_symbol () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #4 0x7fa98d6033bd in _bfd_coff_final_link () from /lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so #5 0x562bdaaae3bf in ?? () #6 0x7fa98d2e8fd0 in __libc_start_call_main (main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58 #7 0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, argc=8, argv=0x7ffc797f2968, init=, fini=, rtld_fini=, stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409 #8 0x562bdaaad515 in ?? () ^^ that is a different crash than on th LP builders ! And despite those crashes the build does appear to work oO?! The same crashes I see on my local sbuild runs, the full set of one build is Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in libc.so.6[7f566e74+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in libc.so.6[7fbba2571000+194000] Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in libc.so.6[7fe368044000+194000] Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 ip 7f241f455f3d sp 7ffd05c2e7c8 error 4 in libc.so.6[7f241f2e2000+194000] Jan 19 07:44:57 Keschdeichel kernel: x86_64-linux-gn[4171794]: segfault
[Touch-packages] [Bug 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)
(We technically had the same issue with the previous upload as 4.0.6 was higher than what hirsute shipped at the time, though in that case the EOL for hirsute was just a month or so away making the case for skipping that SRU even stronger :)) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1959993 Title: SRU of LXC 4.0.12 to focal (upstream bugfix release) Status in lxc package in Ubuntu: In Progress Bug description: LXC released 4.0.12 as a bugfix release and is now in jammy. We'd like to line things up in focal. [Impact] The proposed SRU will bump from 4.0.6 all the way to 4.0.12, lining it up with what's currently in jammy. We've been skipping a few of the bugfix releases in focal so far, mostly catching up when we're starting to see problems with the older version. In this case, we've seen a number of issues when running with the HWE kernels as well as autopkgtest issues on foreign architectures (arm64 and s390x), all those will go away with this bump as we've confirmed everything is clean in jammy. Changelog: * Cherry-pick upstream bugfixes (stable-4.0): - 0002-lxc-checkconfig-Fix-bashism.patch - 0003-doc-Fix-reverse-allowlist-denylist.patch * New upstream bugfix release (4.0.12): (https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288) - Fixed CRIU restoration of containers with pre-created veth interfaces - Fixed issue with kernels lacking SMT support - Extended cgroup2 config options in lxc.mount.auto (cgroup2) - lxc-download now relies on HTTPS for validation (avoids GPG issues) * New upstream bugfix release (4.0.11): (https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427) - Core scheduling support (lxc.sched.core) - riscv64 support in lxc.arch - Significantly improved bash completion profile - Greater use of the new VFS mount API (when supported by the kernel) - Fix containers with empty network namespaces - Handle kernels that lack TIOCGPTPEER - Improve CPU bitmask/id handling (handle skipped CPU numbers) - Reworked the tests to run offline * New upstream bugfix release (4.0.10): (https://discuss.linuxcontainers.org/t/lxc-4-0-10-has-been-released/11618) - Fix issues with less common architectures - Support for additional idmap mounts - nft support in lxc-net - Cleaner mount entries for sys:mixed - Switched GPG server to keyserver.ubuntu.com * New upstream bugfix release (4.0.9): (https://discuss.linuxcontainers.org/t/lxc-4-0-9-has-been-released/10999) - Fix incorrect personality setting when running 32bit containers on 64bit * New upstream bugfix release (4.0.8): - Fix CGroup attach against older running containers * New upstream bugfix release (4.0.7): - Testing improvements including fixes from oss-fuzz - Rework of the attach codepath - Cgroup handling rework * Bump to debhelper 12 (allows focal SRUs) * Bump standards to 4.6.0.1 * Add lintian overrides for incorrect bashism detection * Remove bash completion install logic (now done upstream) Just like Ubuntu itself, upstream releases long term support releases, e.g. 4.0, and then periodic point releases including all the accumulated bugfixes. Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support. This should qualify under the minor/micro upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release. [Test Plan] lxc has autopkgtests which will assert that the binaries built in -proposed are functional. [Where problems could occur] This is catching up a fair bit on recent kernel API changes, including cgroup1/cgroup2 support, handling of nftables, riscv64 and core scheduling which were all needed to properly handle the most recent HWE kernels especially as we're getting ready for Ubuntu 22.04's 5.15 to get pushed to focal. We've had all that code running on well over a million of LXD snap users for a few months now without seeing any issues (or more precisely, those issues we found have been all been resolved as of 4.0.12). However what LXD exercises isn't 100% of LXC and it's certainly possible that we missed a corner case in one of those changes. The good news is that this would most likely be triggered by a HWE kernel, so a viable workaround in many cases would be to temporarily go back to the original kernel (5.4) while the issue is sorted out in a follow up SRU. It's also worth noting that LXD CI runs daily tests against over a dozen different kernels coming from various distros which help
[Touch-packages] [Bug 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)
In general, it's indeed a problem for such cases, though there are a few mitigating factors here: - This would only be a problem for those who upgrade from focal to impish. My understanding is that there is no direct upgrade path to achieve this, you'd need to go throughgroovy and hirsute, both of which are EOL, so I wouldn't really expect many/any user to do this. - The LXC team is responsible for self-assigning CVEs and preparing LXC security updates (~ubuntu-lxc-security). In such cases we usually prefer releasing a new upstream bugfix release (LXC 4.0.x is an LTS with a 5 years security commitment upstream) and then upload that to the -security pockets where applicable. So in that case, we'd bump jammy to match focal, saving us some effort on validating the security update by making things be identical on all releases shipping 4.0.x (jammy will be on 5.0.x). That's generally how we've handled those micro release updates and so far haven't run into any problems but I'm also not necessarily against uploading the exact same source package as focal to impish, the preparation time would be pretty minimal, it's mostly on the review and testing side of things that things can increase significantly especially as we usually struggle to find users on non-LTS to perform more than a simple install/upgrade test. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1959993 Title: SRU of LXC 4.0.12 to focal (upstream bugfix release) Status in lxc package in Ubuntu: In Progress Bug description: LXC released 4.0.12 as a bugfix release and is now in jammy. We'd like to line things up in focal. [Impact] The proposed SRU will bump from 4.0.6 all the way to 4.0.12, lining it up with what's currently in jammy. We've been skipping a few of the bugfix releases in focal so far, mostly catching up when we're starting to see problems with the older version. In this case, we've seen a number of issues when running with the HWE kernels as well as autopkgtest issues on foreign architectures (arm64 and s390x), all those will go away with this bump as we've confirmed everything is clean in jammy. Changelog: * Cherry-pick upstream bugfixes (stable-4.0): - 0002-lxc-checkconfig-Fix-bashism.patch - 0003-doc-Fix-reverse-allowlist-denylist.patch * New upstream bugfix release (4.0.12): (https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288) - Fixed CRIU restoration of containers with pre-created veth interfaces - Fixed issue with kernels lacking SMT support - Extended cgroup2 config options in lxc.mount.auto (cgroup2) - lxc-download now relies on HTTPS for validation (avoids GPG issues) * New upstream bugfix release (4.0.11): (https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427) - Core scheduling support (lxc.sched.core) - riscv64 support in lxc.arch - Significantly improved bash completion profile - Greater use of the new VFS mount API (when supported by the kernel) - Fix containers with empty network namespaces - Handle kernels that lack TIOCGPTPEER - Improve CPU bitmask/id handling (handle skipped CPU numbers) - Reworked the tests to run offline * New upstream bugfix release (4.0.10): (https://discuss.linuxcontainers.org/t/lxc-4-0-10-has-been-released/11618) - Fix issues with less common architectures - Support for additional idmap mounts - nft support in lxc-net - Cleaner mount entries for sys:mixed - Switched GPG server to keyserver.ubuntu.com * New upstream bugfix release (4.0.9): (https://discuss.linuxcontainers.org/t/lxc-4-0-9-has-been-released/10999) - Fix incorrect personality setting when running 32bit containers on 64bit * New upstream bugfix release (4.0.8): - Fix CGroup attach against older running containers * New upstream bugfix release (4.0.7): - Testing improvements including fixes from oss-fuzz - Rework of the attach codepath - Cgroup handling rework * Bump to debhelper 12 (allows focal SRUs) * Bump standards to 4.6.0.1 * Add lintian overrides for incorrect bashism detection * Remove bash completion install logic (now done upstream) Just like Ubuntu itself, upstream releases long term support releases, e.g. 4.0, and then periodic point releases including all the accumulated bugfixes. Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support. This should qualify under the minor/micro upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release. [Test Plan] lxc has autopkgtests which will assert that th
[Touch-packages] [Bug 1878945] Re: crash slapd after update
Sorry about the delay in replying to this bug. >From the bug description, it seems to me that this issue happened while using Ubuntu Xenial (16.04); is that correct? I know it has been a while, but can you still reproduce the issue? If yes, are you able to describe the steps necessary to trigger this failure? Ubuntu Xenial has reached the end of standard support, but I would like to determine whether this is still affecting you and if you are able to reproduce this using a newer version of Ubuntu (Bionic or Focal). I'm marking this bug as Incomplete for now; please move it back to New once you have replied to this comment and provided more details. Thanks. ** Changed in: openldap (Ubuntu) Status: Triaged => Incomplete -- 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/1878945 Title: crash slapd after update Status in openldap package in Ubuntu: Incomplete Bug description: hi, after update slapd to version 2.4.42+dfsg-2ubuntu3.8 I get not working ldap auth service; perform: slaptest -f /etc/ldap/slapd.conf -F /etc/ldap/slapd.d/ and get: 5ebeb45f hdb_db_open: database "dc=myBase": db_open(/var/lib/ldap/id2entry.bdb) failed: No such file or directory (2). 5ebeb45f backend_startup_one (type=hdb, suffix="dc=myBase"): bi_db_open failed! (2) slap_startup failed (test would succeed using the -u switch) journalctl -xe -- Unit slapd.service has finished starting up. -- -- The start-up result is done. May 15 18:25:33 srv sshd[3917]: Connection closed by IP port PORT1 [preauth] May 15 18:26:32 srv sshd[3919]: Connection closed by IP port PORT2 [preauth] May 15 18:27:21 srv systemd[1]: Starting Daily apt download activities... -- Subject: Unit apt-daily.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apt-daily.service has begun starting up. May 15 18:27:23 srv systemd[1]: Started Daily apt download activities. -- Subject: Unit apt-daily.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apt-daily.service has finished starting up. -- -- The start-up result is done. May 15 18:27:32 srv sshd[3987]: Connection closed by IP port PORT3 [preauth] May 15 18:28:04 srv systemd[1]: Stopping LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)... -- Subject: Unit slapd.service has begun shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit slapd.service has begun shutting down. May 15 18:28:04 srv slapd[4020]: * Stopping OpenLDAP slapd May 15 18:28:14 srv slapd[4020]:...fail! May 15 18:28:14 svr systemd[1]: slapd.service: Control process exited, code=exited status=1 May 15 18:28:14 srv systemd[1]: Stopped LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol). -- Subject: Unit slapd.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit slapd.service has finished shutting down. May 15 18:28:14 srv systemd[1]: slapd.service: Unit entered failed state. May 15 18:28:14 srv systemd[1]: slapd.service: Failed with result 'exit-code'. May 15 18:28:14 srv systemd[1]: Starting LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)... -- Subject: Unit slapd.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit slapd.service has begun starting up. May 15 18:28:15 srv slapd[4029]: * Starting OpenLDAP slapd May 15 18:28:15 srv slapd[4029]:...done. May 15 18:28:15 srv systemd[1]: Started LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol). -- Subject: Unit slapd.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit slapd.service has finished starting up. -- -- The start-up result is done. OS: Ubuntu 16.04.6 LTS help, please! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1878945/+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 1528921] Please test proposed package
Hello David, or anyone else affected,
Accepted rsync into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/rsync/3.1.2-2.1ubuntu1.3 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 rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync:
Unknown
Status in rsync package in Ubuntu:
Fix Released
Status in rsync source package in Bionic:
Fix Committed
Status in rsync source package in Focal:
Fix Committed
Bug description:
[Impact]
What the user suffering from this bug experiences is that the big
amount of informative messages related to the copy process with the
three spawned processes(sender, receiver and generator) exhaust the
I/O buffer and the sync gets stuck, either because there are too many
files to synchronise and/or because too many detail messages (levels
of verbose mode) have been requested in the output.
The fix, that comes from upstream and is applied there since version
3.2.0., increments the size of the receiver's I/O buffer.
[Test Plan]
This test plan is for Focal, but it's the same for Bionic.
0.Preparing the test environment:
#Preparing the container
lxc launch images:ubuntu/focal rsync-iobuffer-focal
lxc shell rsync-iobuffer-focal
apt update -y
apt upgrade -y
#Installing necessary tools
apt install rsync
#Get test cases from comments #16 and #19 on this LP bug: As test case
#16 covers both aspects (a lot of files and upper verbosity) and test
#19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19
scenario (but, please, feel to reach me it if you consider it
necessary and I'll provide the steps and bad/good scenarios).
cd /tmp/
#16
Paste the contents of https://pastebin.com/raw/ctzJJGwt:
#!/bin/bash
mkdir source_dir
pushd source_dir
dd if=/dev/zero of=source bs=600K count=1
for i in `seq 1 11500`;
do
cp -v source file_$i;
done
rm source
for i in `seq 1 10`;
do
dd if=/dev/zero of=file_large_$i bs=200M count=1
done
popd
echo "Created 11500 files with size 600K and 10 files with size 200M, try the
following command:"
echo "rsync -avvvz --delete source_dir target_dir"
in a new file script_comment16.sh
chmod +x script_comment16.sh
./script_comment16.sh
1. Bad cases (without and with using strace):
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /root/source_dir/
[sender] make_file(source_dir/file_3048,*,2)
[sender] make_file(source_dir/file_11358,*,2)
[sender] make_file(source_dir/file_5914,*,2)
[sender] make_file(source_dir/file_5880,*,2)
[sender] make_file(source_dir/file_9318,*,2)
[sender] make_file(source_dir/file_5539,*,2)
[...]
sending file_sum
false_alarms=0 hash_hits=0 matches=0
sender finished source_dir/file_10807
send_files(903, source_dir/file_10808)
send_files mapped source_dir/file_10808 of size 614400
calling match_sums source_dir/file_10808
source_dir/file_10808
It hangs here, where using strace we can see:
$ strace rsync -avvvz --delete source_dir target_dir
source_dir/file_11280
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 90112) =
90112
select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 1 (in [5], left
{tv_sec=59, tv_usec=96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"...,
1900) = 1900
select(5, [], [4], [], {tv_s
[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
Hello David, or anyone else affected,
Accepted rsync into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/rsync/3.1.3-8ubuntu0.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
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: rsync (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-focal
** Changed in: rsync (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync:
Unknown
Status in rsync package in Ubuntu:
Fix Released
Status in rsync source package in Bionic:
Fix Committed
Status in rsync source package in Focal:
Fix Committed
Bug description:
[Impact]
What the user suffering from this bug experiences is that the big
amount of informative messages related to the copy process with the
three spawned processes(sender, receiver and generator) exhaust the
I/O buffer and the sync gets stuck, either because there are too many
files to synchronise and/or because too many detail messages (levels
of verbose mode) have been requested in the output.
The fix, that comes from upstream and is applied there since version
3.2.0., increments the size of the receiver's I/O buffer.
[Test Plan]
This test plan is for Focal, but it's the same for Bionic.
0.Preparing the test environment:
#Preparing the container
lxc launch images:ubuntu/focal rsync-iobuffer-focal
lxc shell rsync-iobuffer-focal
apt update -y
apt upgrade -y
#Installing necessary tools
apt install rsync
#Get test cases from comments #16 and #19 on this LP bug: As test case
#16 covers both aspects (a lot of files and upper verbosity) and test
#19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19
scenario (but, please, feel to reach me it if you consider it
necessary and I'll provide the steps and bad/good scenarios).
cd /tmp/
#16
Paste the contents of https://pastebin.com/raw/ctzJJGwt:
#!/bin/bash
mkdir source_dir
pushd source_dir
dd if=/dev/zero of=source bs=600K count=1
for i in `seq 1 11500`;
do
cp -v source file_$i;
done
rm source
for i in `seq 1 10`;
do
dd if=/dev/zero of=file_large_$i bs=200M count=1
done
popd
echo "Created 11500 files with size 600K and 10 files with size 200M, try the
following command:"
echo "rsync -avvvz --delete source_dir target_dir"
in a new file script_comment16.sh
chmod +x script_comment16.sh
./script_comment16.sh
1. Bad cases (without and with using strace):
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /root/source_dir/
[sender] make_file(source_dir/file_3048,*,2)
[sender] make_file(source_dir/file_11358,*,2)
[sender] make_file(source_dir/file_5914,*,2)
[sender] make_file(source_dir/file_5880,*,2)
[sender] make_file(source_dir/file_9318,*,2)
[sender] make_file(source_dir/file_5539,*,2)
[...]
sending file_sum
false_alarms=0 hash_hits=0 matches=0
sender finished source_dir/file_10807
send_files(903, source_dir/file_10808)
send_files mapped source_dir/file_10808 of size 614400
calling match_sums source_dir/file_10808
source_dir/file_10808
It hangs here, where using strace we can see:
$ strace rsync -avvvz --delete source_dir target_dir
source_dir/file_11280
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
[Touch-packages] [Bug 1956915] Re: New bugfix release 21.2.6
this bug is "fix committed" for both focal and impish, meaning the update is in the respective -proposed pocket. see comment #5 -- 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/1956915 Title: New bugfix release 21.2.6 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Status in mesa source package in Impish: Fix Committed Bug description: [Impact] This is the last point-release of the 21.2.x-series, we should put it in impish so latest bugfixes would get there, and in focal for 20.04.4 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
** Merge proposal linked:
https://code.launchpad.net/~mirespace/ubuntu/+source/rsync/+git/rsync/+merge/415253
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync:
Unknown
Status in rsync package in Ubuntu:
Fix Released
Status in rsync source package in Bionic:
In Progress
Status in rsync source package in Focal:
In Progress
Bug description:
[Impact]
What the user suffering from this bug experiences is that the big
amount of informative messages related to the copy process with the
three spawned processes(sender, receiver and generator) exhaust the
I/O buffer and the sync gets stuck, either because there are too many
files to synchronise and/or because too many detail messages (levels
of verbose mode) have been requested in the output.
The fix, that comes from upstream and is applied there since version
3.2.0., increments the size of the receiver's I/O buffer.
[Test Plan]
This test plan is for Focal, but it's the same for Bionic.
0.Preparing the test environment:
#Preparing the container
lxc launch images:ubuntu/focal rsync-iobuffer-focal
lxc shell rsync-iobuffer-focal
apt update -y
apt upgrade -y
#Installing necessary tools
apt install rsync
#Get test cases from comments #16 and #19 on this LP bug: As test case
#16 covers both aspects (a lot of files and upper verbosity) and test
#19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19
scenario (but, please, feel to reach me it if you consider it
necessary and I'll provide the steps and bad/good scenarios).
cd /tmp/
#16
Paste the contents of https://pastebin.com/raw/ctzJJGwt:
#!/bin/bash
mkdir source_dir
pushd source_dir
dd if=/dev/zero of=source bs=600K count=1
for i in `seq 1 11500`;
do
cp -v source file_$i;
done
rm source
for i in `seq 1 10`;
do
dd if=/dev/zero of=file_large_$i bs=200M count=1
done
popd
echo "Created 11500 files with size 600K and 10 files with size 200M, try the
following command:"
echo "rsync -avvvz --delete source_dir target_dir"
in a new file script_comment16.sh
chmod +x script_comment16.sh
./script_comment16.sh
1. Bad cases (without and with using strace):
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /root/source_dir/
[sender] make_file(source_dir/file_3048,*,2)
[sender] make_file(source_dir/file_11358,*,2)
[sender] make_file(source_dir/file_5914,*,2)
[sender] make_file(source_dir/file_5880,*,2)
[sender] make_file(source_dir/file_9318,*,2)
[sender] make_file(source_dir/file_5539,*,2)
[...]
sending file_sum
false_alarms=0 hash_hits=0 matches=0
sender finished source_dir/file_10807
send_files(903, source_dir/file_10808)
send_files mapped source_dir/file_10808 of size 614400
calling match_sums source_dir/file_10808
source_dir/file_10808
It hangs here, where using strace we can see:
$ strace rsync -avvvz --delete source_dir target_dir
source_dir/file_11280
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 90112) =
90112
select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 1 (in [5], left
{tv_sec=59, tv_usec=96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"...,
1900) = 1900
select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(5, [], [4], [], {tv_sec=60, tv_usec=0}
1. Good cases:
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /tmp/source_dir/
[sender] make_file(source_dir/file_3052,*,2)
[sender] make_file(source_dir/file_1766,*,2)
[sender] make_file(source_dir/file_10466,*,2)
[sender] make_file(source_dir/file_9375,*,2)
[sender] make_file(source_dir/file_7260,*,2)
[sender] make_file(source_dir/file_5554,*,2)
[sender] make_file(source_dir/file_5523,*,2)
[sender] make_file(source_dir/file_1685,*,2)
[sender] make_file(source_dir/file_7217,*,2)
[sender] make_file(source_dir/file_10411,*,2)
[...]
generate_files finished
sent 9,555,678 bytes received 3,599,560 bytes 124,694.20 bytes/sec
total size is 9,162,752,000 speedup is 696.51
[Where problems could occur]
Perhaps the buffer size may not be sufficient for an operation
involving a very huge amount of data,
[Touch-packages] [Bug 1960372] Re: DPMS ignores attempts to DISABLE IT
** Package changed: libxcb (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1960372 Title: DPMS ignores attempts to DISABLE IT Status in Ubuntu: New Bug description: I'm on a fresh installation of Debian, linux image 5.10, with a radeon RX580 gpu. My computer is not honoring the setting to "never" turn the monitor off, in power settings. DPMS is still killing the monitor after 10 minutes. It appears bugged. I have to manually turn DPMS with a cron job every 5 minutes to make sure it "stays off". I don't want DPMS. I want my monitor to always stay on ALWAYS FOREVER AND EVER NO MATTER WHAT HAPPENS. Why is DPMS fighting me??? How do I completely disable and REMOVE this bugged program "dpms" from my system, safely??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960372/+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 1960428] [NEW] Network Manager greyed out after resume
Public bug reported: Fresh install; NM is greyed out upon resume from suspend. Everything works, but NM is not accessible. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.3 Uname: Linux 5.15.15-76051515-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Feb 9 10:16:17 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2022-02-02 (7 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 10.35.239.254 dev enx8cae4ceace1f proto dhcp metric 100 10.35.239.0/24 dev enx8cae4ceace1f proto kernel scope link src 10.35.239.45 metric 100 169.254.0.0/16 dev enx8cae4ceace1f scope link metric 1000 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1960428 Title: Network Manager greyed out after resume Status in network-manager package in Ubuntu: New Bug description: Fresh install; NM is greyed out upon resume from suspend. Everything works, but NM is not accessible. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.3 Uname: Linux 5.15.15-76051515-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Feb 9 10:16:17 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2022-02-02 (7 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 10.35.239.254 dev enx8cae4ceace1f proto dhcp metric 100 10.35.239.0/24 dev enx8cae4ceace1f proto kernel scope link src 10.35.239.45 metric 100 169.254.0.0/16 dev enx8cae4ceace1f scope link metric 1000 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1960428/+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 1960425] [NEW] package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Not sure - submitting crash record ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 9 11:10:21 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-11-30 (70 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1960425 Title: package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Not sure - submitting crash record ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 9 11:10:21 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-11-30 (70 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1960425/+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 1956915] Re: New bugfix release 21.2.6
Yes, but this bug is about focal (+ impish), and I'm missing 21.2.x (or 21.3.x) on focal updates. -- 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/1956915 Title: New bugfix release 21.2.6 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Status in mesa source package in Impish: Fix Committed Bug description: [Impact] This is the last point-release of the 21.2.x-series, we should put it in impish so latest bugfixes would get there, and in focal for 20.04.4 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
Upstream 3.2.0 includes the identified upstream fix and Jammy has
3.2.3-8ubuntu2 so this is Fix Released for the development release.
Impish is also > 3.2.0 so only Focal and older are affected.
** Changed in: rsync (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync:
Unknown
Status in rsync package in Ubuntu:
Fix Released
Status in rsync source package in Bionic:
In Progress
Status in rsync source package in Focal:
In Progress
Bug description:
[Impact]
What the user suffering from this bug experiences is that the big
amount of informative messages related to the copy process with the
three spawned processes(sender, receiver and generator) exhaust the
I/O buffer and the sync gets stuck, either because there are too many
files to synchronise and/or because too many detail messages (levels
of verbose mode) have been requested in the output.
The fix, that comes from upstream and is applied there since version
3.2.0., increments the size of the receiver's I/O buffer.
[Test Plan]
This test plan is for Focal, but it's the same for Bionic.
0.Preparing the test environment:
#Preparing the container
lxc launch images:ubuntu/focal rsync-iobuffer-focal
lxc shell rsync-iobuffer-focal
apt update -y
apt upgrade -y
#Installing necessary tools
apt install rsync
#Get test cases from comments #16 and #19 on this LP bug: As test case
#16 covers both aspects (a lot of files and upper verbosity) and test
#19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19
scenario (but, please, feel to reach me it if you consider it
necessary and I'll provide the steps and bad/good scenarios).
cd /tmp/
#16
Paste the contents of https://pastebin.com/raw/ctzJJGwt:
#!/bin/bash
mkdir source_dir
pushd source_dir
dd if=/dev/zero of=source bs=600K count=1
for i in `seq 1 11500`;
do
cp -v source file_$i;
done
rm source
for i in `seq 1 10`;
do
dd if=/dev/zero of=file_large_$i bs=200M count=1
done
popd
echo "Created 11500 files with size 600K and 10 files with size 200M, try the
following command:"
echo "rsync -avvvz --delete source_dir target_dir"
in a new file script_comment16.sh
chmod +x script_comment16.sh
./script_comment16.sh
1. Bad cases (without and with using strace):
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /root/source_dir/
[sender] make_file(source_dir/file_3048,*,2)
[sender] make_file(source_dir/file_11358,*,2)
[sender] make_file(source_dir/file_5914,*,2)
[sender] make_file(source_dir/file_5880,*,2)
[sender] make_file(source_dir/file_9318,*,2)
[sender] make_file(source_dir/file_5539,*,2)
[...]
sending file_sum
false_alarms=0 hash_hits=0 matches=0
sender finished source_dir/file_10807
send_files(903, source_dir/file_10808)
send_files mapped source_dir/file_10808 of size 614400
calling match_sums source_dir/file_10808
source_dir/file_10808
It hangs here, where using strace we can see:
$ strace rsync -avvvz --delete source_dir target_dir
source_dir/file_11280
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144)
= 262144
read(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 90112) =
90112
select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 1 (in [5], left
{tv_sec=59, tv_usec=96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"...,
1900) = 1900
select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
select(5, [], [4], [], {tv_sec=60, tv_usec=0}
1. Good cases:
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /tmp/source_dir/
[sender] make_file(source_dir/file_3052,*,2)
[sender] make_file(source_dir/file_1766,*,2)
[sender] make_file(source_dir/file_10466,*,2)
[sender] make_file(source_dir/file_9375,*,2)
[sender] make_file(source_dir/file_7260,*,2)
[sender] make_file(source_dir/file_5554,*,2)
[sender] make_file(source_dir/file_5523,*,2)
[sender] make_file(source_dir/file_1685,*,2)
[sender] make_file(source_dir/file_7217,*,2)
[sender] make_file(source_dir/file_10411,*,2)
[...]
generate_files finished
sent 9,555,678 bytes received 3,599,560 bytes 124,694.20 bytes/sec
total size is 9,162,752,000 sp
[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform
Is there a risk here that on other desktop environments on Ubuntu, there will be a duplicate event that will not be debounced, and therefore regress users? I'm not sure if this is what you're already stating in "Where problems could occur". If this is a risk, then could you include it in your Test Plan please? If not, then maybe I misunderstand why and I would appreciate clarification. -- 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/1955997 Title: The airplane hotkey has no function on a HP platform Status in OEM Priority Project: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Impish: In Progress Status in systemd source package in Jammy: Fix Released Bug description: [Impact] The airplane hokey doesn't work on HP new generation machines. [Test Plan] Press airplane hokey. Before the patch, nothing happens. After the patch, the rfkill works as expected. [Where problems could occur] In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will not work but HP confirmed the new HP generation won't contain the HPQ6001 and also each DM still need to deal with multi-rfkill events because upstream changes[2]. --- In the last year, HP mentions HP machines need to use hp-wireless (HPQ6001) as the rfkill source[1]. However, HP confirms the HPQ6001 has been retired in the platforms since 2022. In the platforms after 2022, there are two sources of rkfill events (intel-hid, atkbd) and HP only guarantee the intel-hid works. Therefore, the upstream already accept the patch[2] to unmask intel-hid and mention this big change in the NEWS. This change makes the pre-2022 HP platforms meet the regression since they have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing function key. Thus, there is a patch[3] to make sure the GNOME could deal with this case smoothly. However, the systemd change will still cause other DEs meet the regression (xfce, KDE, lxde, etc..). Backport systemd change to make HP 2022 platforms work is not the best choice on stable version (focal in this case). We still need a solution to make airplane key works on 2022 HP platforms (intel-hid and atkbd only). The potential solution from my mind that is to maintain a whitelist to unmask intel-hid in ubuntu-patch in focal, something like: ``` evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:* KEYBOARD_KEY_8=wlan # Use hp-wireless instead ``` after "KEYBOARD_KEY_8=unkown". [1] https://bugs.launchpad.net/bugs/1883846 [2] https://github.com/systemd/systemd/pull/20219 [3] https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955997/+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 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)
Thank you for the detailed SRU information! You anticipated most of the obvious questions and saved us a bunch of round trips. > Should someone do an upgrade to impish, we've confirmed that the upgrade is resolvable and that they'll just be left with a more recent version of LXC than that in the impish archive, until jammy releases and they upgrade to it. Wouldn't that leave them missing security updates that might be subsequently uploaded to Impish? I was under the impression that leaving the archive in this situation is always a hard no. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1959993 Title: SRU of LXC 4.0.12 to focal (upstream bugfix release) Status in lxc package in Ubuntu: In Progress Bug description: LXC released 4.0.12 as a bugfix release and is now in jammy. We'd like to line things up in focal. [Impact] The proposed SRU will bump from 4.0.6 all the way to 4.0.12, lining it up with what's currently in jammy. We've been skipping a few of the bugfix releases in focal so far, mostly catching up when we're starting to see problems with the older version. In this case, we've seen a number of issues when running with the HWE kernels as well as autopkgtest issues on foreign architectures (arm64 and s390x), all those will go away with this bump as we've confirmed everything is clean in jammy. Changelog: * Cherry-pick upstream bugfixes (stable-4.0): - 0002-lxc-checkconfig-Fix-bashism.patch - 0003-doc-Fix-reverse-allowlist-denylist.patch * New upstream bugfix release (4.0.12): (https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288) - Fixed CRIU restoration of containers with pre-created veth interfaces - Fixed issue with kernels lacking SMT support - Extended cgroup2 config options in lxc.mount.auto (cgroup2) - lxc-download now relies on HTTPS for validation (avoids GPG issues) * New upstream bugfix release (4.0.11): (https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427) - Core scheduling support (lxc.sched.core) - riscv64 support in lxc.arch - Significantly improved bash completion profile - Greater use of the new VFS mount API (when supported by the kernel) - Fix containers with empty network namespaces - Handle kernels that lack TIOCGPTPEER - Improve CPU bitmask/id handling (handle skipped CPU numbers) - Reworked the tests to run offline * New upstream bugfix release (4.0.10): (https://discuss.linuxcontainers.org/t/lxc-4-0-10-has-been-released/11618) - Fix issues with less common architectures - Support for additional idmap mounts - nft support in lxc-net - Cleaner mount entries for sys:mixed - Switched GPG server to keyserver.ubuntu.com * New upstream bugfix release (4.0.9): (https://discuss.linuxcontainers.org/t/lxc-4-0-9-has-been-released/10999) - Fix incorrect personality setting when running 32bit containers on 64bit * New upstream bugfix release (4.0.8): - Fix CGroup attach against older running containers * New upstream bugfix release (4.0.7): - Testing improvements including fixes from oss-fuzz - Rework of the attach codepath - Cgroup handling rework * Bump to debhelper 12 (allows focal SRUs) * Bump standards to 4.6.0.1 * Add lintian overrides for incorrect bashism detection * Remove bash completion install logic (now done upstream) Just like Ubuntu itself, upstream releases long term support releases, e.g. 4.0, and then periodic point releases including all the accumulated bugfixes. Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support. This should qualify under the minor/micro upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release. [Test Plan] lxc has autopkgtests which will assert that the binaries built in -proposed are functional. [Where problems could occur] This is catching up a fair bit on recent kernel API changes, including cgroup1/cgroup2 support, handling of nftables, riscv64 and core scheduling which were all needed to properly handle the most recent HWE kernels especially as we're getting ready for Ubuntu 22.04's 5.15 to get pushed to focal. We've had all that code running on well over a million of LXD snap users for a few months now without seeing any issues (or more precisely, those issues we found have been all been resolved as of 4.0.12). However what LXD exercises isn't 100% of LXC and it's certainly possible that we missed a corner case in one of those changes. The good news is that this would most likely be trigge
[Touch-packages] [Bug 1960410] [NEW] desktop always flicking after i update processor to i7
Public bug reported: hello Ihave issue with xorgs after i change my processor from i5 to i7 , my desktop spec is Hp elite 8200 , please help . regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 9 20:33:54 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.13.0-27-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-28-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0122] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1494] InstallationDate: Installed on 2021-08-27 (166 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Compaq 8200 Elite CMT PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=f5f901a5-ac5a-451e-a4a7-7cc65371a63a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 11/10/2011 dmi.bios.release: 2.15 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.15 dmi.board.name: 1494 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:br2.15:svnHewlett-Packard:pnHPCompaq8200EliteCMTPC:pvr:rvnHewlett-Packard:rn1494:rvr:cvnHewlett-Packard:ct6:cvr:skuXL508AV: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 8200 Elite CMT PC dmi.product.sku: XL508AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1960410 Title: desktop always flicking after i update processor to i7 Status in xorg package in Ubuntu: New Bug description: hello Ihave issue with xorgs after i change my processor from i5 to i7 , my desktop spec is Hp elite 8200 , please help . regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 9 20:33:54 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.13.0-27-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-28-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0122] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1494] InstallationDate: Installed on 2021-08-27 (166 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP Compaq 8200 Elite CMT PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=f5f901a5-ac5a-451e-a4a7-7cc65371a63a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 11/10/2011 dmi.bios.release: 2.15 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.15 dmi.board.name: 1494 dmi.board.vendor: Hewlett-Packard dmi.chas
[Touch-packages] [Bug 1960404] Re: merge python-debian 0.1.43 from Debian sid
** Tags added: fr-2035 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-debian in Ubuntu. https://bugs.launchpad.net/bugs/1960404 Title: merge python-debian 0.1.43 from Debian sid Status in python-debian package in Ubuntu: New Bug description: Please merge the latest Debian version of this package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1960404/+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 1960404] Re: merge python-debian 0.1.43 from Debian sid
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-debian in Ubuntu. https://bugs.launchpad.net/bugs/1960404 Title: merge python-debian 0.1.43 from Debian sid Status in python-debian package in Ubuntu: New Bug description: Please merge the latest Debian version of this package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1960404/+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 1960404] Re: merge python-debian 0.1.43 from Debian sid
Attached is a patch against the latest Debian version. The delta has also been pushed here : https://salsa.debian.org/schopin/python- debian/-/commits/external-zstd and will be posted in a MR if athos doesn't pick it up in his own at https://salsa.debian.org/python-debian-team/python- debian/-/merge_requests/65 The new version has been uploaded to a PPA, just pop the extraneous changelog entry: https://launchpad.net/~schopin/+archive/ubuntu/test- ppa/+sourcepub/13253281/+listing-archive-extra ** Patch added: "debian.debdiff" https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1960404/+attachment/5559939/+files/debian.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-debian in Ubuntu. https://bugs.launchpad.net/bugs/1960404 Title: merge python-debian 0.1.43 from Debian sid Status in python-debian package in Ubuntu: New Bug description: Please merge the latest Debian version of this package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1960404/+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 1456789] Re: restarting services hangs on systemd-tty-ask-password-agent
Just faced this bug on 20.04.3 with service apache2 restart. As noted earlier 'systemctl daemon-reload' did fix it, but this workaround is rather not an obvious solution. -- 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/1456789 Title: restarting services hangs on systemd-tty-ask-password-agent Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Fix Released Bug description: I have a script run as root from cron that tweaks smb.conf and restarts smbd and winbind. Problem is, starting today after working perfectly up till yesterday, this script now hangs on Ubuntu 15.04. When run from cron, the process tree looks like this: service smbd restart \_ systemctl restart smbd.service \_ /bin/systemd-tty-ask-password-agent --watch \_ /usr/bin/pkttyagent --notify-fd 5 --fallback Run from a shell via sudo, same thing except the process tree (obviously) includes the sudo command. It times out after 5 minutes, causing the script to fail. If I manually kill the processes, it fails faster. The simplest possible scripts that reproduce this, run as root or through cron or via sudo, are: #!/bin/sh service smbd restart #!/bin/sh systemctl restart smbd.service Using 'service', this works perfectly on Ubuntu 14.04 and 14.10, and until this morning worked perfectly on 15.04 as well. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 15.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd 219-7ubuntu5 samba 2:4.1.13+dfsg-4ubuntu3 3) What you expected to happen Services to restart 4) What happened instead Services didn't restart, 'systemctl' hung To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456789/+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 1960404] [NEW] merge python-debian 0.1.43 from Debian sid
Public bug reported: Please merge the latest Debian version of this package. ** Affects: python-debian (Ubuntu) Importance: Wishlist Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-debian in Ubuntu. https://bugs.launchpad.net/bugs/1960404 Title: merge python-debian 0.1.43 from Debian sid Status in python-debian package in Ubuntu: New Bug description: Please merge the latest Debian version of this package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1960404/+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 1960226] Re: Ubuntu Jammy Desktop fails to boot after install
2022-02-09 Fails Ran 2 tests - http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/244128/testcases/1300/results -- 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/1960226 Title: Ubuntu Jammy Desktop fails to boot after install Status in systemd package in Ubuntu: Incomplete Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Jammy Desktop fails to boot after install Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07 This also affects Ubuntu Jammy Canary desktop - tested daily ISO 2022-02-07 After installing the OS and selecting reboot the system reboot fails - The vendors logo appears with the Ubuntu logo and fails to boot - I have tried this with 2 barebone machines and 1 in VirtualBox - will attach syslogs and images in a separate comment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1960226/+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 1960226] Re: Ubuntu Jammy Desktop fails to boot after install
Seems the problem is not ubiquity. Downgrading to 22.04.4 before installing made no improvement. ** No longer affects: ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1960226 Title: Ubuntu Jammy Desktop fails to boot after install Status in systemd package in Ubuntu: Incomplete Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Jammy Desktop fails to boot after install Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07 This also affects Ubuntu Jammy Canary desktop - tested daily ISO 2022-02-07 After installing the OS and selecting reboot the system reboot fails - The vendors logo appears with the Ubuntu logo and fails to boot - I have tried this with 2 barebone machines and 1 in VirtualBox - will attach syslogs and images in a separate comment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1960226/+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 1960226] Re: Ubuntu Jammy Desktop fails to boot after install
** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1960226 Title: Ubuntu Jammy Desktop fails to boot after install Status in systemd package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Jammy Desktop fails to boot after install Testing Ubuntu Jammy Desktop daily ISO - 2022-02-07 This also affects Ubuntu Jammy Canary desktop - tested daily ISO 2022-02-07 After installing the OS and selecting reboot the system reboot fails - The vendors logo appears with the Ubuntu logo and fails to boot - I have tried this with 2 barebone machines and 1 in VirtualBox - will attach syslogs and images in a separate comment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1960226/+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 1956915] Re: New bugfix release 21.2.6
the jammy queue has had 21.3.x for weeks now -- 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/1956915 Title: New bugfix release 21.2.6 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Status in mesa source package in Impish: Fix Committed Bug description: [Impact] This is the last point-release of the 21.2.x-series, we should put it in impish so latest bugfixes would get there, and in focal for 20.04.4 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+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
