[Touch-packages] [Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
** No longer affects: systemd (Ubuntu Jammy) -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1679346] Re: Missing dep8 tests
This bug was fixed in the package net-tools - 1.60+git20181103.0eebece-1ubuntu4 --- net-tools (1.60+git20181103.0eebece-1ubuntu4) jammy; urgency=low * Add new DEP8 tests for hostname and ifconfig (LP: #1679346): - d/t/control: add hostname-set-get and ifconfig-lo-info - d/t/hostname-set-get: new test - d/t/ifconfig-lo-info: new test -- Lena Voytek Fri, 22 Oct 2021 07:49:06 -0700 ** Changed in: net-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1679346 Title: Missing dep8 tests Status in net-tools package in Ubuntu: Fix Released Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As of April 3, 2017, this source package did not contain package tests in the current development release of Ubuntu, named Zesty. This was determined by running `pull-lp-source net-tools zesty` and then checking for the existence of 'debian/tests/' and 'debian/tests/control'. The package was also checked for 1) a test suite declaration in the debian/control file, 2) any 'test', 'tests', 'testsuite', or 'test-suite' directories, 3) go tests (if applicable), and 4) a test suite declared in a setup.py (if applicable). If you feel this report is incorrect (e.g. this is a library or a source only package) or the check above missed some other package level test please reply explaining why and mark this bug as 'invalid'. Test automation is essential to higher levels of quality and confidence in updates to packages. dep8 tests [1] specify how automatic testing can be integrated into packages and then run by package maintainers before new uploads. This defect is to report the absence of these tests and to report the opportunity as a potential item for development by both new and experienced contributors. Thanks! [1] http://packaging.ubuntu.com/html/auto-pkg-test.html affects ubuntu/net-tools status new importance wishlist tag needs-dep8 - --- Joshua Powers Ubuntu Server Canonical Ltd -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJY4siLAAoJEIP8BxPaZgwlKlgP/1tp7NP3mLPZyukvkknbekpa 0Cd02/t3Jy9JNJK/hnH50b0JUQ3HMFAvOIPb6SZgUH7NOlrE2Hgprcyo/OFZ5rRB fX3qc5PRX83VUM2D7IQtaQZqBU+y0vHDZ5DjWWfhke6E9SZsUHybVCAP+yBQXorQ DiEffoTUGkOfi+5S7V57FWw3rBxjeNRBxeoerfq/a0GS4YvTanQgFOMC1weOz/8J I64olcq3EMrUpClxKF2LQ6H0xDdpbF0i3SZfhi5h294p1qF8l4PS0rLT2sqr85Pr 1yz0jORhribXZy3M7thUMz/aLDmimL9+7nPL2lz40JjbNjNTVPZ+s8RguKWYYBx3 DBDJBfdG5JoLhsDDon7PKOILKj40S14KtmdbBY0VGNGuVSz3+m0WiTnTdJQzWWHR FNsfGjD+mdARcXqr11xgp/zY6VEVhG0AFIaZZgs1PbqvqL3FtGPgEGwXetgIU5bS J2suTN+WEEf8nI8kMi6PsUFfGsMogZTRHy04PCfPem0MBB3Olrmulm9bXcfbZ1Le 0eep3OVn06fm43x7YQaI/hzGl959pdppAahlFWTKvF0vfq7mJcSb6n1QpeWhvqeB tBAaV1redyI5ovDGAAVuFzrxJ7rWRKw4PVYln/C2Mayzb1S2dTwpjLtA9kcfQZJQ ZY8eSrPyf6eh2z8LVlR+ =WKVW -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1679346/+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 1950201] Re: Gnugpg does not offer the option to store the private and public keys on two different keycards.
This guide describes how to make a copy of gnupg files in order to create a duplicate card: https://zach.codes/ultimate-yubikey-setup-guide/ It would be nice if such a guide weren't necessary. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1950201 Title: Gnugpg does not offer the option to store the private and public keys on two different keycards. Status in gnupg package in Ubuntu: New Bug description: Gnugpg does not offer the option to store the private and public keys on two different keycards. I have followed the official yubikey guide as follows, but it might apply to similar smart cards and USB tokens: To import the key on your YubiKey: Insert the YubiKey into the USB port if it is not already plugged in. Enter the GPG command: gpg --edit-key 1234ABC (where 1234ABC is the key ID of your key) Enter the command: keytocard When prompted if you really want to move your primary key, enter y (yes). When prompted where to store the key, select 1. This will move the signature subkey to the PGP signature slot of the YubiKey. Enter the command: key 1 Enter the command: keytocard When prompted where to store the key, select 2. This will move the encryption subkey to the YubiKey. Enter the command: key 1 Enter the command: key 2 Enter the command: keytocard When prompted where to store the key, select 3. This will move the authentication subkey to the YubiKey. Enter the command: quit When prompted to save your changes, enter y (yes). You have now saved your keyring to your YubiKey. The issue with that is that it permanently moves the secret keys to the yubikey or similar, and that causes issues later if one wants to create backup keys. If one saves the changes and tries to make a separate identical key card at a later date, one gets the "gpg: KEYTOCARD failed: Unusable secret key." error. I have read that if one presses control and c ( on Linux ) it after the last keytocard and option 3, the secret keys will not be deleted from the computer, only copied. One then can start forward again at this step: gpg --edit-key 1234ABC (where 1234ABC is the key ID of your key). Another possible but tedious workaround is to backup the secret keys and public keys, and import those back into gpg, then move they keys to a physical backup key. ( Note: Key 0 is the primary signature subkey. Key 1is the encryption subkey. key 2 is the authentication subkey .) Ideally, there should be a option in the gpg menu about this, that asks about permanently moving the keys. A nice addition would be: Do you want to make a separate identical key card? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1950201/+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 1950147] Re: [amdgpu] Screen freeze (ring gfx timeout)
*** This bug is a duplicate of bug 1949497 *** https://bugs.launchpad.net/bugs/1949497 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1949497, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - Wayland freeze + [amdgpu] Screen freeze (ring gfx timeout) ** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1949497 [amdgpu] Screen freezes ([drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout) -- 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/1950147 Title: [amdgpu] Screen freeze (ring gfx timeout) Status in linux package in Ubuntu: New Bug description: When playing a game through Wine I occasionally have the screen lock up and become unresponsive to any input, including SysRq commands. However applications are still running in the background because I can e.g. hear spotify playing through my library in the background. I have looked at my journal and this section seems to be relevant because it mentions the Windows app being run using Wine (MTGA.exe) and also my graphics setup. The journal is attached. In particular the line of interest is: Nov 08 21:17:34 michael-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=21072413, emitted seq=21072415 Nov 08 21:17:34 michael-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process MTGA.exe pid 619227 thread MTGA.exe:cs0 pid 619300 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 8 21:45:10 2021 DistUpgraded: 2021-10-19 23:58:20,621 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: xpad, 0.4, 5.13.0-19-generic, x86_64: installed xpad, 0.4, 5.13.0-20-generic, x86_64: installed xpad, 0.4, 5.4.45-050445-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] [174b:e271] InstallationDate: Installed on 2016-07-30 (1926 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=768ef993-9d8f-4c92-9155-97d92a1bdd93 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-19 (19 days ago) XorgLog: Error: path contained symlinks. XorgLogOld: Error: path contained symlinks. dmi.bios.date: 04/09/2013 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.asset.tag: BC5FF4DC2BD7 dmi.board.name: 980DE3/U3S3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd04/09/2013:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rn980DE3/U3S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx
[Touch-packages] [Bug 1950195] Re: Doesn't Unlock After Powering Down Display For Inactivity
Thanks for the bug report. Next time the problem happens please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Tags added: amdgpu ** 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/1950195 Title: Doesn't Unlock After Powering Down Display For Inactivity Status in Ubuntu: Incomplete Bug description: My laptop, HP model 17-y028cy, does not resume after the display has been shut off for inactivity. The computer starts back up and the display does turn on, but nothing is displayed on my screen. It doesn't appear to respond to any key presses so I have to force it to power down and back up by holding the power button until it shuts off. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 8 11:10:58 2021 DistUpgraded: 2021-10-22 09:44:17,286 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon R5 Graphics [103c:8221] InstallationDate: Installed on 2021-08-18 (82 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=19963d75-e403-4c58-aa01-13462ff038ab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-22 (17 days ago) dmi.bios.date: 01/16/2017 dmi.bios.release: 15.37 dmi.bios.vendor: Insyde dmi.bios.version: F.37 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8221 dmi.board.vendor: HP dmi.board.version: 85.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 85.39 dmi.modalias: dmi:bvnInsyde:bvrF.37:bd01/16/2017:br15.37:efr85.39:svnHP:pnHPNotebook:pvrType1ProductConfigId:sku1MF63UAR#ABA:rvnHP:rn8221:rvr85.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: 1MF63UAR#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1950195/+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 1946499] Re: SRU: GDebi - installation of deb-packages with gdebi-gtk not working at all
This bug was fixed in the package gdebi - 0.9.5.7+nmu5ubuntu2 --- gdebi (0.9.5.7+nmu5ubuntu2) impish; urgency=medium * Drop Ubuntu-specific patches - no-longer needed (LP: #1756238, #1946499) -- Dani Llewellyn Thu, 14 Oct 2021 18:30:02 +0100 ** Changed in: gdebi (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: SRU: GDebi - installation of deb-packages with gdebi-gtk not working at all Status in gdebi package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Fix Released Status in gdebi source package in Impish: Fix Released Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1946499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1946499] Update Released
The verification of the Stable Release Update for gdebi has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: SRU: GDebi - installation of deb-packages with gdebi-gtk not working at all Status in gdebi package in Ubuntu: Fix Released Status in vte2.91 package in Ubuntu: Fix Released Status in gdebi source package in Impish: Fix Released Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1946499/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1950201] Re: Gnugpg does not offer the option to store the private and public keys on two different keycards.
** Description changed: - Gnugpg does not offer the option to store the private and public keys - on two different keycards. + Gnugpg does not offer the option to store the private and public keys on + two different keycards. I have followed the official yubikey guide as follows, but it might apply to similar smart cards and USB tokens: To import the key on your YubiKey: - Insert the YubiKey into the USB port if it is not already plugged + Insert the YubiKey into the USB port if it is not already plugged in. - Enter the GPG command: gpg --edit-key 1234ABC (where 1234ABC is the + Enter the GPG command: gpg --edit-key 1234ABC (where 1234ABC is the key ID of your key) - Enter the command: keytocard + Enter the command: keytocard - When prompted if you really want to move your primary key, enter y + When prompted if you really want to move your primary key, enter y (yes). - When prompted where to store the key, select 1. This will move the + When prompted where to store the key, select 1. This will move the signature subkey to the PGP signature slot of the YubiKey. - Enter the command: key 1 - Enter the command: keytocard + Enter the command: key 1 + Enter the command: keytocard - When prompted where to store the key, select 2. This will move the + When prompted where to store the key, select 2. This will move the encryption subkey to the YubiKey. - Enter the command: key 1 + Enter the command: key 1 - Enter the command: key 2 + Enter the command: key 2 - Enter the command: keytocard + Enter the command: keytocard - When prompted where to store the key, select 3. This will move the + When prompted where to store the key, select 3. This will move the authentication subkey to the YubiKey. - - Enter the command: quit - When prompted to save your changes, enter y (yes). You have now saved your keyring to your YubiKey. + Enter the command: quit + When prompted to save your changes, enter y (yes). You have now saved your keyring to your YubiKey. The issue with that is that it permanently moves the secret keys to the yubikey or similar, and that causes issues later if one wants to create backup keys. If one saves the changes and tries to make a separate identical key card at a later date, one gets the "gpg: KEYTOCARD failed: Unusable secret key." error. I have read that if one presses control and c ( on Linux ) it after the last keytocard and option 3, the secret keys will not be deleted from the computer, only copied. One then can start forward again at this step: gpg --edit-key 1234ABC (where 1234ABC is the key ID of your key). Another possible but tedious workaround is to backup the secret keys and public keys, and import those back into gpg, then move they keys to a physical backup key. ( Note: Key 0 is the primary signature subkey. Key 1is the encryption subkey. key 2 is the authentication subkey .) + + + Ideally, there should be a option in the gpg menu about this, that asks about permanently moving the keys. + + A nice addition would be: + + Do you want to make a separate identical key card? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1950201 Title: Gnugpg does not offer the option to store the private and public keys on two different keycards. Status in gnupg package in Ubuntu: New Bug description: Gnugpg does not offer the option to store the private and public keys on two different keycards. I have followed the official yubikey guide as follows, but it might apply to similar smart cards and USB tokens: To import the key on your YubiKey: Insert the YubiKey into the USB port if it is not already plugged in. Enter the GPG command: gpg --edit-key 1234ABC (where 1234ABC is the key ID of your key) Enter the command: keytocard When prompted if you really want to move your primary key, enter y (yes). When prompted where to store the key, select 1. This will move the signature subkey to the PGP signature slot of the YubiKey. Enter the command: key 1 Enter the command: keytocard When prompted where to store the key, select 2. This will move the encryption subkey to the YubiKey. Enter the command: key 1 Enter the command: key 2 Enter the command: keytocard When prompted where to store the key, select 3. This will move the authentication subkey to the YubiKey. Enter the command: quit When prompted to save your changes, enter y (yes). You have now saved your keyring to your YubiKey. The issue with that is that it permanently moves the secret keys to the yubikey or similar, and that causes issues later if one wants to create backup keys. If
[Touch-packages] [Bug 1950201] [NEW] Gnugpg does not offer the option to store the private and public keys on two different keycards.
Public bug reported: Gnugpg does not offer the option to store the private and public keys on two different keycards. I have followed the official yubikey guide as follows, but it might apply to similar smart cards and USB tokens: To import the key on your YubiKey: Insert the YubiKey into the USB port if it is not already plugged in. Enter the GPG command: gpg --edit-key 1234ABC (where 1234ABC is the key ID of your key) Enter the command: keytocard When prompted if you really want to move your primary key, enter y (yes). When prompted where to store the key, select 1. This will move the signature subkey to the PGP signature slot of the YubiKey. Enter the command: key 1 Enter the command: keytocard When prompted where to store the key, select 2. This will move the encryption subkey to the YubiKey. Enter the command: key 1 Enter the command: key 2 Enter the command: keytocard When prompted where to store the key, select 3. This will move the authentication subkey to the YubiKey. Enter the command: quit When prompted to save your changes, enter y (yes). You have now saved your keyring to your YubiKey. The issue with that is that it permanently moves the secret keys to the yubikey or similar, and that causes issues later if one wants to create backup keys. If one saves the changes and tries to make a separate identical key card at a later date, one gets the "gpg: KEYTOCARD failed: Unusable secret key." error. I have read that if one presses control and c ( on Linux ) it after the last keytocard and option 3, the secret keys will not be deleted from the computer, only copied. One then can start forward again at this step: gpg --edit-key 1234ABC (where 1234ABC is the key ID of your key). Another possible but tedious workaround is to backup the secret keys and public keys, and import those back into gpg, then move they keys to a physical backup key. ( Note: Key 0 is the primary signature subkey. Key 1is the encryption subkey. key 2 is the authentication subkey .) ** Affects: gnupg (Ubuntu) Importance: Undecided Status: New ** Tags: gnupg gpg keytocard openpgp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1950201 Title: Gnugpg does not offer the option to store the private and public keys on two different keycards. Status in gnupg package in Ubuntu: New Bug description: Gnugpg does not offer the option to store the private and public keys on two different keycards. I have followed the official yubikey guide as follows, but it might apply to similar smart cards and USB tokens: To import the key on your YubiKey: Insert the YubiKey into the USB port if it is not already plugged in. Enter the GPG command: gpg --edit-key 1234ABC (where 1234ABC is the key ID of your key) Enter the command: keytocard When prompted if you really want to move your primary key, enter y (yes). When prompted where to store the key, select 1. This will move the signature subkey to the PGP signature slot of the YubiKey. Enter the command: key 1 Enter the command: keytocard When prompted where to store the key, select 2. This will move the encryption subkey to the YubiKey. Enter the command: key 1 Enter the command: key 2 Enter the command: keytocard When prompted where to store the key, select 3. This will move the authentication subkey to the YubiKey. Enter the command: quit When prompted to save your changes, enter y (yes). You have now saved your keyring to your YubiKey. The issue with that is that it permanently moves the secret keys to the yubikey or similar, and that causes issues later if one wants to create backup keys. If one saves the changes and tries to make a separate identical key card at a later date, one gets the "gpg: KEYTOCARD failed: Unusable secret key." error. I have read that if one presses control and c ( on Linux ) it after the last keytocard and option 3, the secret keys will not be deleted from the computer, only copied. One then can start forward again at this step: gpg --edit-key 1234ABC (where 1234ABC is the key ID of your key). Another possible but tedious workaround is to backup the secret keys and public keys, and import those back into gpg, then move they keys to a physical backup key. ( Note: Key 0 is the primary signature subkey. Key 1is the encryption subkey. key 2 is the authentication subkey .) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1950201/+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
Re: [Touch-packages] [Bug 1949535] Re: X-forwarding no longer works
I am originating from a Ubuntu 21.10 system to a Debian Bullet system, but now I can't get X-forwarding to work from any site I connect to when originating from Ubuntu 21.10. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Mon, 8 Nov 2021, Paride Legovini wrote: > Date: Mon, 08 Nov 2021 15:43:10 - > From: Paride Legovini <1949...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1949535] Re: X-forwarding no longer works > > Hello Robert and thanks for your bug report. You wrote: > >> I recently upgraded my debian shell server to Bullet > > but I'm not sure I get what you mean. Is it a Debian system or an Ubuntu > system? If it's upgrading a Debian system that broke your setup then > there's nothing I can see that points to a bug in Ubuntu. Moreover: what > is Bullet? Did you mean Bullseye or Bookworm? > > If you think there's actually a bug in Ubuntu here please share more of > your reasoning, possibly providing a reproducer, e.g. by ssh -X to a > container or VM. I'm marking this bug report as Incomplete for the > moment. Feel free to change it back to New after commenting back. > Thanks! > > ** Changed in: openssh (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1949535 > > Title: > X-forwarding no longer works > > Status in openssh package in Ubuntu: > Incomplete > > Bug description: > I operate a Linux based Internet hosting service that includes Linux > shell servers of various flavors. I control these from home using > Ubuntu 21.10 presently. Until recently, X-forwarding has worked from > all but ancient Redhat 6.2 servers. I recently upgraded my debian > shell server to Bullet, and after the upgrade ssh -X debian.eskimo.com > from my workstation nanook.eskimo.com ceased to function. It simply > says "Cannot open DISPLAY". At the time, all the others continued to > work. Today, when I went to do upgrades, now ssh -X is forwarding > across the board to all flavors of Linux. I did an ssh -V, nothing > obvious wrong in the connection. > > debug1: Authentications that can continue: publickey,password > debug1: Next authentication method: publickey > debug1: Offering public key: /home/nanook/.ssh/id_rsa RSA > SHA256:a5bReJXl7L91eGOuCYugHsY2rn2a0WTDXEBTC93YdmA agent > debug1: Server accepts key: /home/nanook/.ssh/id_rsa RSA > SHA256:a5bReJXl7L91eGOuCYugHsY2rn2a0WTDXEBTC93YdmA agent > debug1: Authentication succeeded (publickey). > Authenticated to igloo.eskimo.com ([204.122.16.128]:22). > debug1: channel 0: new [client-session] > debug1: Requesting no-more-sessi...@openssh.com > debug1: Entering interactive session. > debug1: pledge: network > debug1: client_input_global_request: rtype hostkeys...@openssh.com > want_reply 0 > debug1: Remote: /home/nanook/.ssh/authorized_keys:1: key options: > agent-forwarding port-forwarding pty user-rc x11-forwarding > debug1: Remote: /home/nanook/.ssh/authorized_keys:1: key options: > agent-forwarding port-forwarding pty user-rc x11-forwarding > debug1: Sending environment. > debug1: Sending env LANG = en_US.UTF-8 > debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 > debug1: client_input_channel_req: channel 0 rtype e...@openssh.com reply 0 > debug1: channel 0: free: client-session, nchannels 1 > debug1: fd 2 clearing O_NONBLOCK > Connection to igloo.eskimo.com closed. > Transferred: sent 3748, received 3820 bytes, in 6.4 seconds > Bytes per second: sent 589.4, received 600.8 > > I don't see anything obviously wrong here but still it does not work, I get: > xclock > Error: Can't open display: > > ProblemType: Bug > DistroRelease: Ubuntu 21.10 > Package: ssh (not installed) > Uname: Linux 5.13.19 x86_64 > ApportVersion: 2.20.11-0ubuntu71 > Architecture: amd64 > CasperMD5CheckResult: unknown > CurrentDesktop: MATE > Date: Tue Nov 2 17:31:14 2021 > SourcePackage: openssh > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1949535/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1949535 Title: X-forwarding no longer works Status in openssh package in Ubuntu: Incomplete Bug description: I operate a Linux based Internet hosting service that includes Linux shell servers of various flavors. I control these from home using Ubuntu 21.10 presently. Until recently, X-forwarding has worked from all but ancient Redhat 6.2 servers. I
[Touch-packages] [Bug 1896251] Re: rsync --delete-missing-args fails with "error: protocol incompatibility"
Performing the verification for Bionic: First, reproducing the bug with the current version: # apt policy rsync rsync: Installed: 3.1.2-2.1ubuntu1.1 Candidate: 3.1.2-2.1ubuntu1.1 Version table: *** 3.1.2-2.1ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.1.2-2.1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages # mkdir -p a/1 b/1; echo "/1/2/3" > list # rsync --dry-run --stats -Pav --delete-missing-args --files-from=list a b file has vanished: "/root/a/1/2" ABORTING due to invalid path from sender: 1/2/3 rsync error: protocol incompatibility (code 2) at generator.c(1271) [generator=3.1.2] Next, updating the package to the version available in -proposed, clearing the directory, and making sure that the bug is fixed: # apt policy rsync rsync: Installed: 3.1.2-2.1ubuntu1.2 Candidate: 3.1.2-2.1ubuntu1.2 Version table: *** 3.1.2-2.1ubuntu1.2 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.1.2-2.1ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 3.1.2-2.1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages # mkdir -p a/1 b/1; echo "/1/2/3" > list # rsync --dry-run --stats -Pav --delete-missing-args --files-from=list a b file has vanished: "/root/a/1/2" WARNING: parent dir is absent in the file list: 1/2 Number of files: 2 (reg: 1, dir: 1) Number of created files: 0 Number of deleted files: 0 Number of regular files transferred: 0 Total file size: 0 bytes Total transferred file size: 0 bytes Literal data: 0 bytes Matched data: 0 bytes File list size: 0 File list generation time: 0.001 seconds File list transfer time: 0.000 seconds Total bytes sent: 60 Total bytes received: 68 sent 60 bytes received 68 bytes 256.00 bytes/sec total size is 0 speedup is 0.00 (DRY RUN) rsync warning: some files vanished before they could be transferred (code 24) at main.c(1196) [sender=3.1.2] As shown above, there is no longer a crash due to missing parent folders. Therefore, the bug has been fixed for bionic and verification is complete. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-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/1896251 Title: rsync --delete-missing-args fails with "error: protocol incompatibility" Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Xenial: Won't Fix Status in rsync source package in Bionic: Fix Committed Status in rsync source package in Focal: Fix Committed Bug description: [Impact] Rsync crashes when using --delete-missing-args on a file with a missing parent folder. Backporting this fix will allow users to delete missing source args when some files in the list have missing parent folders without interruption. This is fixed by patching in an upstream commit that allows files with missing parent folders to be handled without aborting. [Test Plan] # lxc launch images:ubuntu/focal builder # lxc exec builder bash # apt update # apt dist-upgrade # apt install -y rsync # mkdir -p a/1 b/1; echo "/1/2/3" > list # rsync --dry-run --stats -Pav --delete-missing-args --files-from=list a b * This should crash with exit code 2 after printing the following: building file list ... 0 files... file has vanished: "/root/a/1/2" 2 files to consider ABORTING due to invalid path from sender: 1/2/3 rsync error: protocol incompatibility (code 2) at generator.c(1278) [generator=3.1.3] [Where problems could occur] Since the remove operation will now continue when files in the list have missing parent folders, other errors and warnings with different behaviors could arise instead. A warning that may arise the most often in these situations is the following: warning: some files vanished before they could be transferred (code 24) at main.c(1207) [sender=3.1.3] This appears at the end of the above test case with the new code. The behavior is expected, but it may cause regressions due to changes in the output of certain use cases. [Original Description] Running rsync --delete-missing-args --files-from=... fails with error message like ABORTING due to invalid path from sender: dir1/dir2/dir3 rsync error: protocol incompatibility (code 2) at generator.c(1271) [generator=3.1.2] if the listed directories are trying to delete full subtree of files. According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has been fixed in
[Touch-packages] [Bug 1896251] Re: rsync --delete-missing-args fails with "error: protocol incompatibility"
Performing the verification for Focal: First, reproducing the bug with the current version: # apt policy rsync rsync: Installed: 3.1.3-8 Candidate: 3.1.3-8 Version table: *** 3.1.3-8 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status # mkdir -p a/1 b/1; echo "/1/2/3" > list # rsync --dry-run --stats -Pav --delete-missing-args --files-from=list a b building file list ... 0 files... file has vanished: "/root/a/1/2" 2 files to consider ABORTING due to invalid path from sender: 1/2/3 rsync error: protocol incompatibility (code 2) at generator.c(1278) [generator=3.1.3] Next, updating the package to the version available in -proposed, clearing the directory, and making sure that the bug is fixed: # apt policy rsync rsync: Installed: 3.1.3-8ubuntu0.1 Candidate: 3.1.3-8ubuntu0.1 Version table: *** 3.1.3-8ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.1.3-8 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages # mkdir -p a/1 b/1; echo "/1/2/3" > list # rsync --dry-run --stats -Pav --delete-missing-args --files-from=list a b building file list ... 0 files... file has vanished: "/root/a/1/2" 2 files to consider WARNING: parent dir is absent in the file list: 1/2 Number of files: 2 (reg: 1, dir: 1) Number of created files: 0 Number of deleted files: 0 Number of regular files transferred: 0 Total file size: 0 bytes Total transferred file size: 0 bytes Literal data: 0 bytes Matched data: 0 bytes File list size: 0 File list generation time: 0.001 seconds File list transfer time: 0.000 seconds Total bytes sent: 59 Total bytes received: 68 sent 59 bytes received 68 bytes 254.00 bytes/sec total size is 0 speedup is 0.00 (DRY RUN) rsync warning: some files vanished before they could be transferred (code 24) at main.c(1207) [sender=3.1.3] As shown above, there is no longer a crash due to missing parent folders. Therefore, the bug has been fixed for focal and verification is complete. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1896251 Title: rsync --delete-missing-args fails with "error: protocol incompatibility" Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Xenial: Won't Fix Status in rsync source package in Bionic: Fix Committed Status in rsync source package in Focal: Fix Committed Bug description: [Impact] Rsync crashes when using --delete-missing-args on a file with a missing parent folder. Backporting this fix will allow users to delete missing source args when some files in the list have missing parent folders without interruption. This is fixed by patching in an upstream commit that allows files with missing parent folders to be handled without aborting. [Test Plan] # lxc launch images:ubuntu/focal builder # lxc exec builder bash # apt update # apt dist-upgrade # apt install -y rsync # mkdir -p a/1 b/1; echo "/1/2/3" > list # rsync --dry-run --stats -Pav --delete-missing-args --files-from=list a b * This should crash with exit code 2 after printing the following: building file list ... 0 files... file has vanished: "/root/a/1/2" 2 files to consider ABORTING due to invalid path from sender: 1/2/3 rsync error: protocol incompatibility (code 2) at generator.c(1278) [generator=3.1.3] [Where problems could occur] Since the remove operation will now continue when files in the list have missing parent folders, other errors and warnings with different behaviors could arise instead. A warning that may arise the most often in these situations is the following: warning: some files vanished before they could be transferred (code 24) at main.c(1207) [sender=3.1.3] This appears at the end of the above test case with the new code. The behavior is expected, but it may cause regressions due to changes in the output of certain use cases. [Original Description] Running rsync --delete-missing-args --files-from=... fails with error message like ABORTING due to invalid path from sender: dir1/dir2/dir3 rsync error: protocol incompatibility (code 2) at generator.c(1271) [generator=3.1.2] if the listed directories are trying to delete full subtree of files. According to https://bugzilla.samba.org/show_bug.cgi?id=12569 this has been fixed in version 3.2.2. See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863334 Could you update the rsync package or backport the fix? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64
[Touch-packages] [Bug 1950195] Re: Doesn't Unlock After Powering Down Display For Inactivity
** Package changed: ubuntu => xorg (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/1950195 Title: Doesn't Unlock After Powering Down Display For Inactivity Status in xorg package in Ubuntu: New Bug description: My laptop, HP model 17-y028cy, does not resume after the display has been shut off for inactivity. The computer starts back up and the display does turn on, but nothing is displayed on my screen. It doesn't appear to respond to any key presses so I have to force it to power down and back up by holding the power button until it shuts off. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 8 11:10:58 2021 DistUpgraded: 2021-10-22 09:44:17,286 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon R5 Graphics [103c:8221] InstallationDate: Installed on 2021-08-18 (82 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=19963d75-e403-4c58-aa01-13462ff038ab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-22 (17 days ago) dmi.bios.date: 01/16/2017 dmi.bios.release: 15.37 dmi.bios.vendor: Insyde dmi.bios.version: F.37 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8221 dmi.board.vendor: HP dmi.board.version: 85.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 85.39 dmi.modalias: dmi:bvnInsyde:bvrF.37:bd01/16/2017:br15.37:efr85.39:svnHP:pnHPNotebook:pvrType1ProductConfigId:sku1MF63UAR#ABA:rvnHP:rn8221:rvr85.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: 1MF63UAR#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1950195/+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 1940860] Re: Mellanox NIC interface names change between 5.4 and 5.8
Note that this is for the latest focal debian-installer. Since there is no hwe-netboot image the current focal installer is affected. I think an hwe-netboot image for focal would resolve this issue for the installer. -- 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/1940860 Title: Mellanox NIC interface names change between 5.4 and 5.8 Status in debian-installer: New Status in subiquity: New Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Invalid Bug description: I noticed on a couple of systems that my network interface names change when upgrading from the focal LTS (5.4) kernel to the focal HWE (both 5.8 & 5.11) kernels. Both systems have Mellanox Connect-X 5 NICs. dannf@bizzy:~$ uname -a Linux bizzy 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:10:30 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0 enp1s0f1 enx3e8734bc294f lo dannf@bizzy:~$ uname -a Linux bizzy 5.8.0-63-generic #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:44 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0np0 enp1s0f1np1 enx3e8734bc294f lo dannf@bizzy:~$ uname -a Linux bizzy 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 15:58:08 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0np0 enp1s0f1np1 enx3e8734bc294f lo I bisected this down to a kernel change: # first bad commit: [c6acd629eec754a9679f922d51f90e44c769b80c] net/mlx5e: Add support for devlink-port in non-representors mode The impact is that your network can fail to come up after transitioning from the LTS kernel to the HWE kernel. Now, this isn't a huge problem for MAAS installs because MAAS configures netplan to always use the same names as were used at commissioning. It does impact subiquity based installs however, which do not. To manage notifications about this bug go to: https://bugs.launchpad.net/debian-installer/+bug/1940860/+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 1950195] [NEW] Doesn't Unlock After Powering Down Display For Inactivity
You have been subscribed to a public bug: My laptop, HP model 17-y028cy, does not resume after the display has been shut off for inactivity. The computer starts back up and the display does turn on, but nothing is displayed on my screen. It doesn't appear to respond to any key presses so I have to force it to power down and back up by holding the power button until it shuts off. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 8 11:10:58 2021 DistUpgraded: 2021-10-22 09:44:17,286 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon R5 Graphics [103c:8221] InstallationDate: Installed on 2021-08-18 (82 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=19963d75-e403-4c58-aa01-13462ff038ab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-22 (17 days ago) dmi.bios.date: 01/16/2017 dmi.bios.release: 15.37 dmi.bios.vendor: Insyde dmi.bios.version: F.37 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8221 dmi.board.vendor: HP dmi.board.version: 85.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 85.39 dmi.modalias: dmi:bvnInsyde:bvrF.37:bd01/16/2017:br15.37:efr85.39:svnHP:pnHPNotebook:pvrType1ProductConfigId:sku1MF63UAR#ABA:rvnHP:rn8221:rvr85.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: 1MF63UAR#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu wayland-session -- Doesn't Unlock After Powering Down Display For Inactivity https://bugs.launchpad.net/bugs/1950195 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940860] Re: Mellanox NIC interface names change between 5.4 and 5.8
** Also affects: linux Importance: Undecided Status: New ** Project changed: linux => debian-installer -- 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/1940860 Title: Mellanox NIC interface names change between 5.4 and 5.8 Status in debian-installer: New Status in subiquity: New Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Invalid Bug description: I noticed on a couple of systems that my network interface names change when upgrading from the focal LTS (5.4) kernel to the focal HWE (both 5.8 & 5.11) kernels. Both systems have Mellanox Connect-X 5 NICs. dannf@bizzy:~$ uname -a Linux bizzy 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:10:30 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0 enp1s0f1 enx3e8734bc294f lo dannf@bizzy:~$ uname -a Linux bizzy 5.8.0-63-generic #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:44 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0np0 enp1s0f1np1 enx3e8734bc294f lo dannf@bizzy:~$ uname -a Linux bizzy 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 15:58:08 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux dannf@bizzy:~$ ls /sys/class/net enp1s0f0np0 enp1s0f1np1 enx3e8734bc294f lo I bisected this down to a kernel change: # first bad commit: [c6acd629eec754a9679f922d51f90e44c769b80c] net/mlx5e: Add support for devlink-port in non-representors mode The impact is that your network can fail to come up after transitioning from the LTS kernel to the HWE kernel. Now, this isn't a huge problem for MAAS installs because MAAS configures netplan to always use the same names as were used at commissioning. It does impact subiquity based installs however, which do not. To manage notifications about this bug go to: https://bugs.launchpad.net/debian-installer/+bug/1940860/+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
Re: [Touch-packages] [Bug 1813052] Re: who returns no results
Workaround found! Issue was systemd not providing /var/run/utmp
added a script to /etc/rc.local that does
if [ ! -f /var/run/utmp ]
then
cat /dev/null > /var/run/utmp ; chown root:utmp /var/run/utmp
fi
On Mon, Nov 1, 2021 at 3:16 AM Anthony Godshall
<1813...@bugs.launchpad.net> wrote:
>
> ** Attachment added: "who.strace.txt"
>
> https://bugs.launchpad.net/bugs/1813052/+attachment/5537446/+files/who.strace.txt
>
> ** Attachment added: "dpkg_-l.txt"
>
> https://bugs.launchpad.net/bugs/1813052/+attachment/5537447/+files/dpkg_-l.txt
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1813052
>
> Title:
> who returns no results
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813052/+subscriptions
>
--
Best Regards.
This is unedited.
P-)
--
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/1813052
Title:
who returns no results
Status in systemd package in Ubuntu:
Invalid
Bug description:
Who returns no results on xenial.
Here's an strace. I don't see any obvious difference between it and
an strace on a system that works (an unupdated xenial or a bionic
system).
# strace who
execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
brk(NULL) = 0x9f9000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253eee000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eed000
mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f225391c000
mprotect(0x7f2253adc000, 2097152, PROT_NONE) = 0
mmap(0x7f2253cdc000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7f2253cdc000
mmap(0x7f2253ce2000, 14752, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f2253ce2000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eec000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eeb000
arch_prctl(ARCH_SET_FS, 0x7f2253eec700) = 0
mprotect(0x7f2253cdc000, 16384, PROT_READ) = 0
mprotect(0x60a000, 4096, PROT_READ) = 0
mprotect(0x7f2253f0b000, 4096, PROT_READ) = 0
munmap(0x7f2253eee000, 117369) = 0
brk(NULL) = 0x9f9000
brk(0xa1a000) = 0xa1a000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253644000
close(3)= 0
access("/var/run/utmpx", F_OK) = 0
open("/var/run/utmpx", O_RDONLY|O_CLOEXEC) = 3
lseek(3, 0, SEEK_SET) = 0
alarm(0)= 0
rt_sigaction(SIGALRM, {0x7f2253a5d380, [], SA_RESTORER, 0x7f22539514b0},
{SIG_DFL, [], 0}, 8) = 0
alarm(10) = 0
fcntl(3, F_SETLKW, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
read(3, 0x7f2253ce5120, 384)= -1 EISDIR (Is a directory)
fcntl(3, F_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
alarm(0)= 10
rt_sigaction(SIGALRM, {SIG_DFL, [], SA_RESTORER, 0x7f22539514b0}, NULL, 8) = 0
close(3)= 0
close(1)= 0
close(2)= 0
exit_group(0) = ?
+++ exited with 0 +++
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: coreutils 8.25-2ubuntu3~16.04
ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
Uname: Linux 4.4.0-141-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Jan 23 10:39:00 2019
InstallationDate: Installed on 2016-07-08 (929 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh
[Touch-packages] [Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
About the question about Focal/hirsute/uc20 - we have not observed the issue there. -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd source package in Jammy: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1950181] [NEW] package usbmuxd 1.1.1-2build1 failed to install/upgrade: installed usbmuxd package post-installation script subprocess returned error exit status 1
Public bug reported: no additional details ProblemType: Package DistroRelease: Ubuntu 21.10 Package: usbmuxd 1.1.1-2build1 ProcVersionSignature: Ubuntu 5.11.0-40.44-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Nov 8 16:23:50 2021 ErrorMessage: installed usbmuxd package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: usbmuxd Title: package usbmuxd 1.1.1-2build1 failed to install/upgrade: installed usbmuxd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to impish on 2021-11-08 (0 days ago) ** Affects: usbmuxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish need-duplicate-check uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/1950181 Title: package usbmuxd 1.1.1-2build1 failed to install/upgrade: installed usbmuxd package post-installation script subprocess returned error exit status 1 Status in usbmuxd package in Ubuntu: New Bug description: no additional details ProblemType: Package DistroRelease: Ubuntu 21.10 Package: usbmuxd 1.1.1-2build1 ProcVersionSignature: Ubuntu 5.11.0-40.44-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Nov 8 16:23:50 2021 ErrorMessage: installed usbmuxd package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: usbmuxd Title: package usbmuxd 1.1.1-2build1 failed to install/upgrade: installed usbmuxd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to impish on 2021-11-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1950181/+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 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
That's certainly possible. In the first attempt (that failed according to mvo's tests) I only backported https://github.com/systemd/systemd-stable/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 and https://github.com/systemd/systemd-stable/commit/cc6271f17d3c5c200e8a391f10d0afb71403fc28 (as a dependency) It is quite possible that we need to backport even more commits to fix this without reverting LP: #1934147 -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd source package in Jammy: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1949535] Re: X-forwarding no longer works
Hello Robert and thanks for your bug report. You wrote: > I recently upgraded my debian shell server to Bullet but I'm not sure I get what you mean. Is it a Debian system or an Ubuntu system? If it's upgrading a Debian system that broke your setup then there's nothing I can see that points to a bug in Ubuntu. Moreover: what is Bullet? Did you mean Bullseye or Bookworm? If you think there's actually a bug in Ubuntu here please share more of your reasoning, possibly providing a reproducer, e.g. by ssh -X to a container or VM. I'm marking this bug report as Incomplete for the moment. Feel free to change it back to New after commenting back. Thanks! ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1949535 Title: X-forwarding no longer works Status in openssh package in Ubuntu: Incomplete Bug description: I operate a Linux based Internet hosting service that includes Linux shell servers of various flavors. I control these from home using Ubuntu 21.10 presently. Until recently, X-forwarding has worked from all but ancient Redhat 6.2 servers. I recently upgraded my debian shell server to Bullet, and after the upgrade ssh -X debian.eskimo.com from my workstation nanook.eskimo.com ceased to function. It simply says "Cannot open DISPLAY". At the time, all the others continued to work. Today, when I went to do upgrades, now ssh -X is forwarding across the board to all flavors of Linux. I did an ssh -V, nothing obvious wrong in the connection. debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Offering public key: /home/nanook/.ssh/id_rsa RSA SHA256:a5bReJXl7L91eGOuCYugHsY2rn2a0WTDXEBTC93YdmA agent debug1: Server accepts key: /home/nanook/.ssh/id_rsa RSA SHA256:a5bReJXl7L91eGOuCYugHsY2rn2a0WTDXEBTC93YdmA agent debug1: Authentication succeeded (publickey). Authenticated to igloo.eskimo.com ([204.122.16.128]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: pledge: network debug1: client_input_global_request: rtype hostkeys...@openssh.com want_reply 0 debug1: Remote: /home/nanook/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding debug1: Remote: /home/nanook/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: client_input_channel_req: channel 0 rtype e...@openssh.com reply 0 debug1: channel 0: free: client-session, nchannels 1 debug1: fd 2 clearing O_NONBLOCK Connection to igloo.eskimo.com closed. Transferred: sent 3748, received 3820 bytes, in 6.4 seconds Bytes per second: sent 589.4, received 600.8 I don't see anything obviously wrong here but still it does not work, I get: xclock Error: Can't open display: ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ssh (not installed) Uname: Linux 5.13.19 x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Tue Nov 2 17:31:14 2021 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1949535/+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 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
Thank you for testing the revert! Do we know if the same issue happens in Focal/UC20 as well? Or can we somehow falsify that? The regressing patches had been introduced to Hirsute/Focal/Bionic to fix LP: #1934147 -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd source package in Jammy: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
Fwiw, the patch debian/lp1934147/0001-core-add-a-new-unit-method- catchup.patch is part of a fairly large patchset (https://github.com/systemd/systemd/pull/9200/commits) so maybe something is missing there? -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd source package in Jammy: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
** Merge proposal linked: https://code.launchpad.net/~slyon/ubuntu/+source/systemd/+git/systemd/+merge/411528 -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd source package in Jammy: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1949958] Re: External output Jack produce low volume garbled sound with alc293 on Ubuntu 20.04.3
** Summary changed: - External Jack produce garbled sound with alc293 + External output Jack produce low volume garbled sound with alc293 on Ubuntu 20.04.3 ** Description changed: - External Jack produce garbled sound + External Jack produce low volume garbled sound We tried alc293-dell1 and alc293-dell , but it does not change anything It seems it was working with some older 5.11 kernel + + But We tested a live Ubuntu 20.04.3 with the same fail results. + + It seems the card have recorded some settings ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.12 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip Date: Fri Nov 5 12:06:01 2021 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-13 (387 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: pulseaudio 1:13.99.1-1ubuntu3.12 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: focal Uname: Linux 5.11.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/24/2020 dmi.bios.release: 7.4 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL4x_NL5xLU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd09/24/2020:br7.4:efr7.2:svnNotebook:pnNL4x_NL5xLU:pvrNotApplicable:skuNotApplicable:rvnNotebook:rnNL4x_NL5xLU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NL4x_NL5xLU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1949958 Title: External output Jack produce low volume garbled sound with alc293 on Ubuntu 20.04.3 Status in pulseaudio package in Ubuntu: New Bug description: External Jack produce low volume garbled sound We tried alc293-dell1 and alc293-dell , but it does not change anything It seems it was working with some older 5.11 kernel But We tested a live Ubuntu 20.04.3 with the same fail results. It seems the card have recorded some settings ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.12 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pandora3069 F pulseaudio CasperMD5CheckResult: skip Date: Fri Nov 5 12:06:01 2021 InstallationDate: Installed on
[Touch-packages] [Bug 1950174] [NEW] [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
Public bug reported:
[Description]
This is a request to backport this fix from mesa 21.1 to focal-updates which is
affecting users of WSL:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
This cached stale pointer is causing various chromium applications
(Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is
enabled in WSLg. We’re getting incredibly unlucky because a glx drawable
is being freed and reallocated with exactly the same heap pointers
during a resize, which is causing Mesa to think the new drawable is
already fully initialized when binded to the context, but it is not true
and only because the new drawable is matching the old stale pointer for
the previously freed drawable… and as a result the context remain
invalid and the app is unable to present.
With the push of WDDMv3 drivers which expose vGPU in WSL, the number of
users hitting this issue is increasing.
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: mesa (Ubuntu Focal)
Importance: High
Status: Triaged
** Also affects: mesa (Ubuntu Focal)
Importance: Undecided
Status: New
** Description changed:
[Description]
- This is a request to backport this fix to focal-updates which is affecting
users of WSL:
+ This is a request to backport this fix from mesa 21.1 to focal-updates which
is affecting users of WSL:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
This cached stale pointer is causing various chromium applications
(Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is
enabled in WSLg. We’re getting incredibly unlucky because a glx drawable
is being freed and reallocated with exactly the same heap pointers
during a resize, which is causing Mesa to think the new drawable is
already fully initialized when binded to the context, but it is not true
and only because the new drawable is matching the old stale pointer for
the previously freed drawable… and as a result the context remain
invalid and the app is unable to present.
With the push of WDDMv3 drivers which expose vGPU in WSL, the number of
users hitting this issue is increasing.
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
** Changed in: mesa (Ubuntu Focal)
Status: New => Triaged
** Changed in: mesa (Ubuntu Focal)
Importance: Undecided => High
--
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/1950174
Title:
[SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
Triaged
Bug description:
[Description]
This is a request to backport this fix from mesa 21.1 to focal-updates which
is affecting users of WSL:
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87
This cached stale pointer is causing various chromium applications
(Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU
is enabled in WSLg. We’re getting incredibly unlucky because a glx
drawable is being freed and reallocated with exactly the same heap
pointers during a resize, which is causing Mesa to think the new
drawable is already fully initialized when binded to the context, but
it is not true and only because the new drawable is matching the old
stale pointer for the previously freed drawable… and as a result the
context remain invalid and the app is unable to present.
With the push of WDDMv3 drivers which expose vGPU in WSL, the number
of users hitting this issue is increasing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+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 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
Thank you Michael for verifying this! As per my earlier question during our last-week's sync: do you think it would be possible to have this running for instance as part of the coreXX-edge testing that Sergio is doing? Since we'd like to make sure we don't reintroduce this issue at some point by accident. -- 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/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Status in systemd source package in Jammy: New Bug description: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc- flip-flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 1927337] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (21.04)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1927337 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (21.04) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays slower, e.g. YouTube in a browser. I have never seen anything like that before. I have tried to figure out what the cause might be and I think I have reached the end of where I can get to on my own. I have documented most things at https://ubuntuforums.org/showthread.php?t=2461568 Putting my last step it in a nutshell: I have booted both my computers with a plain Ubuntu 21.04 from a pen drive (it uses kernel version 5.11.0-16-generic) to make sure it's not some different configuration that I have set up over the years on my systems (both Ubuntu 20.04 with kernel 5.8.18). I attached the Rodecaster. It runs fine on my laptop, but not on my desktop (used the output test from). I then detected the card number with aplay -l I killed pulseaudio with pulseaudio -k I then played the same sample (encoded in 48000 Hz in PCM signed 32 bit little endian format) using aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav where x is the appropriate card number and the rest of the arguments meet the Rodecaster's narrow specification. It's playing fine on the laptop, but distorted on the desktop. As far as I understand using aplay this way without a plugin should send the file directly to the device, so I assume there's something on the way from aplay to the Rodecaster that's interfering (kernel or even some piece of hardware) - and that definitely is where my expertise ends (rather a little before :-)). I'll gladly contribute any information that could be useful and I will willingly help to debug this problem if it may be related to the kernel. If there's anything I can do, please let me know. Cheers, Oliver ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Thu May 6 09:33:40 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed Symptom_Card: RODECaster Pro - RODECaster Pro Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927337/+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 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
Just for the record, I also did another run with: https://storage.googleapis.com/snapd-spread- tests/snaps/core18_20211102_amd64.snap and that also fails right away: """ $ git status On branch tests-use-core18-from-gce Your branch is up to date with 'sergiocazzolato/tests-use-core18-from-gce'. $ git diff [empty] $ $GOPATH/bin/spread -repeat 100 google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy ... 2021-11-08 12:13:57 Error executing google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy (nov081101-381415) : - + . /home/gopath/src/github.com/snapcore/snapd/tests/lib/disabled-svcs.sh ++ SVC_MISSING_ERR_MSG='state.json is missing last-active-disabled-services in it:' + echo 'CASE 1' CASE 1 + echo 'Install the snap' Install the snap + snap install --dangerous disabled-svcs-kept_1.0_all.snap disabled-svcs-kept 1.0 installed + echo 'Check that state.json doesn'\''t contain last-active-disabled-services' Check that state.json doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'CASE 2' CASE 2 + echo 'Disable a service in the snap' Disable a service in the snap + snap stop --disable disabled-svcs-kept.svc Stopped. + echo 'Check that it was actually disabled' Check that it was actually disabled + retry -n 10 --wait 1 sh -c 'snap services disabled-svcs-kept | MATCH "disabled-svcs-kept\\.svc\\s+disabled\\s+inactive"' + echo 'Check that state.json still doesn'\''t contain last-active-disabled-services' Check that state.json still doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'Disable the whole snap' Disable the whole snap + snap disable disabled-svcs-kept disabled-svcs-kept disabled + echo 'Check that state.json DOES contain last-active-disabled-services' Check that state.json DOES contain last-active-disabled-services + check_state_json_yes_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' '!=' null 'state.json has invalid last-active-disabled-services in it:' + echo 'Enable the whole snap' Enable the whole snap + snap enable disabled-svcs-kept disabled-svcs-kept enabled + echo 'Check that the service is still disabled' Check that the service is still disabled + MATCH 'disabled-svcs-kept\.svc\s+disabled\s+inactive' + snap services disabled-svcs-kept + echo 'Check that state.json still doesn'\''t contain last-active-disabled-services' Check that state.json still doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'CASE 3' CASE 3 + echo 'Refresh the snap' Refresh the snap + snap install --dangerous disabled-svcs-kept_1.0_all.snap disabled-svcs-kept 1.0 installed + echo 'Check that the service is still disabled' Check that the service is still disabled + MATCH 'disabled-svcs-kept\.svc\s+disabled\s+inactive' + snap services disabled-svcs-kept + echo 'Check that state.json still doesn'\''t contain last-active-disabled-services' Check that state.json still doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'CASE 4' CASE 4 + echo 'Revert the snap' Revert the snap + snap revert disabled-svcs-kept --revision=x1 disabled-svcs-kept reverted to 1.0 + echo 'Check that the service is still disabled' Check that the service is still disabled + MATCH 'disabled-svcs-kept\.svc\s+disabled\s+inactive' + snap services disabled-svcs-kept + echo 'Check that state.json still doesn'\''t contain last-active-disabled-services' Check that state.json still doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'Refresh back to the new revision to unmark it as blacklisted' Refresh back to the new revision to unmark it as blacklisted + snap refresh disabled-svcs-kept --revision=x2
[Touch-packages] [Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
Thanks Lukas for providing this revert of f0831ed2a03fcef582660be1c3b1a9f3e267e656. Using https://people.ubuntu.com/~slyon/uc18/core18_20211105_amd64.snap I can no longer reproduce the isue. To make it easier to reproduce what I did: """ $ git status On branch tests-use-core18-from-gce Your branch is up to date with 'sergiocazzolato/tests-use-core18-from-gce'. ... $ git diff diff --git a/tests/lib/prepare.sh b/tests/lib/prepare.sh index e6b984c4d0..5c58a55b2f 100755 --- a/tests/lib/prepare.sh +++ b/tests/lib/prepare.sh @@ -973,7 +973,7 @@ EOF fi if os.query is-core18; then -curl -s -o core18.snap https://storage.googleapis.com/snapd-spread-tests/snaps/core18_20211102_amd64.snap +curl -s -o core18.snap https://people.ubuntu.com/~slyon/uc18/core18_20211105_amd64.snap EXTRA_FUNDAMENTAL="$EXTRA_FUNDAMENTAL --snap $PWD/core18.snap" fi $ $GOPATH/bin/spread -repeat 100 google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy ... 2021-11-08 11:39:41 Preparing google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy (nov081028-580805)... 2021-11-08 11:39:53 Executing google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy (nov081028-580805) (1/1)... 2021-11-08 11:40:49 Restoring google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy (nov081028-580805)... 2021-11-08 11:41:00 Preparing google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy (nov081028-580805)... ... """ To validate my findings I'm also running the same test against core18 in stable and it fails very quickly: """ $ git status HEAD detached at upstream/master $ git describe 2.53.1-480-g2c39794030 $ $GOPATH/bin/spread -repeat 100 google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy 2021-11-08 11:58:46 Error executing google:ubuntu-core-18-64:tests/main/services-disabled-kept-happy (nov081048-716592) : - + . /home/gopath/src/github.com/snapcore/snapd/tests/lib/disabled-svcs.sh ++ SVC_MISSING_ERR_MSG='state.json is missing last-active-disabled-services in it:' + echo 'CASE 1' CASE 1 + echo 'Install the snap' Install the snap + snap install --dangerous disabled-svcs-kept_1.0_all.snap disabled-svcs-kept 1.0 installed + echo 'Check that state.json doesn'\''t contain last-active-disabled-services' Check that state.json doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'CASE 2' CASE 2 + echo 'Disable a service in the snap' Disable a service in the snap + snap stop --disable disabled-svcs-kept.svc Stopped. + echo 'Check that it was actually disabled' Check that it was actually disabled + retry -n 10 --wait 1 sh -c 'snap services disabled-svcs-kept | MATCH "disabled-svcs-kept\\.svc\\s+disabled\\s+inactive"' + echo 'Check that state.json still doesn'\''t contain last-active-disabled-services' Check that state.json still doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'Disable the whole snap' Disable the whole snap + snap disable disabled-svcs-kept disabled-svcs-kept disabled + echo 'Check that state.json DOES contain last-active-disabled-services' Check that state.json DOES contain last-active-disabled-services + check_state_json_yes_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' '!=' null 'state.json has invalid last-active-disabled-services in it:' + echo 'Enable the whole snap' Enable the whole snap + snap enable disabled-svcs-kept disabled-svcs-kept enabled + echo 'Check that the service is still disabled' Check that the service is still disabled + MATCH 'disabled-svcs-kept\.svc\s+disabled\s+inactive' + snap services disabled-svcs-kept + echo 'Check that state.json still doesn'\''t contain last-active-disabled-services' Check that state.json still doesn't contain last-active-disabled-services + check_state_json_no_disabled_svcs + /home/gopath/src/github.com/snapcore/snapd/tests/lib/tools/snapd-state check-state '.data.snaps."disabled-svcs-kept" | ."last-active-disabled-services"?' = null 'state.json has invalid last-active-disabled-services in it:' + echo 'CASE 3' CASE 3 + echo 'Refresh the snap' Refresh the snap + snap install --dangerous disabled-svcs-kept_1.0_all.snap disabled-svcs-kept 1.0 installed + echo 'Check that the service is still disabled' Check that the service is still disabled + MATCH 'disabled-svcs-kept\.svc\s+disabled\s+inactive' + snap services
[Touch-packages] [Bug 1950147] [NEW] Wayland freeze
Public bug reported: When playing a game through Wine I occasionally have the screen lock up and become unresponsive to any input, including SysRq commands. However applications are still running in the background because I can e.g. hear spotify playing through my library in the background. I have looked at my journal and this section seems to be relevant because it mentions the Windows app being run using Wine (MTGA.exe) and also my graphics setup. The journal is attached. In particular the line of interest is: Nov 08 21:17:34 michael-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=21072413, emitted seq=21072415 Nov 08 21:17:34 michael-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process MTGA.exe pid 619227 thread MTGA.exe:cs0 pid 619300 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 8 21:45:10 2021 DistUpgraded: 2021-10-19 23:58:20,621 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: xpad, 0.4, 5.13.0-19-generic, x86_64: installed xpad, 0.4, 5.13.0-20-generic, x86_64: installed xpad, 0.4, 5.4.45-050445-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] [174b:e271] InstallationDate: Installed on 2016-07-30 (1926 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=768ef993-9d8f-4c92-9155-97d92a1bdd93 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-19 (19 days ago) XorgLog: Error: path contained symlinks. XorgLogOld: Error: path contained symlinks. dmi.bios.date: 04/09/2013 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.asset.tag: BC5FF4DC2BD7 dmi.board.name: 980DE3/U3S3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd04/09/2013:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rn980DE3/U3S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 xserver.bootTime: Wed May 12 17:02:34 2021 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.9 xserver.video_driver: amdgpu ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze impish ubuntu wayland-session ** Attachment added: "Journal" https://bugs.launchpad.net/bugs/1950147/+attachment/5538803/+files/crash_log.txt -- 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/1950147 Title: Wayland freeze Status in xorg package in Ubuntu: New Bug description: When playing a game through Wine I occasionally have the screen lock up and become unresponsive to any input, including SysRq commands. However applications are still running in the
[Touch-packages] [Bug 1950095] Re: [github] 20.04: Apt fails to download URLs with non-encoded querystrings
Marking as fix released. Do not plan to backport this due to significant regression potential ** Changed in: apt (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1950095 Title: [github] 20.04: Apt fails to download URLs with non-encoded querystrings Status in apt package in Ubuntu: Fix Released Bug description: I've just helped a group of Ubuntu 20.04 users with Microsoft Surface devices. They rely upon a github repository releases pocket as the apt archive. Those users recently hit a bug "Ubuntu: Apt update fails with Error 401 Unauthorized" [1] The initial simple Github URL gets a Location: redirect to a complex URL with un-escaped query-string. The resulting complex URL causes apt to fail to fetch the resource. $ sudo apt upgrade -y Err:1 https://pkg.surfacelinux.com/debian release/main amd64 libwacom-surface amd64 1.12-2 401 Unauthorized [IP: 185.199.110.133 443] The URL can be manually corrected. One of the Surface users provided this example: bad: https://objects.githubusercontent.com/github-production-release- asset-2e65be/139604852/86019e52-7bfa-4bc6-8cc1-52147027aee6?X-Amz- Algorithm=AWS4-HMAC-SHA256 Credential=AKIAIWNJYAX4CSVEH53A/20211105/us- east-1/s3/aws4_request=20211105T161053Z Expires=300 Signature=2bc0c28946db539ada250b1030c37249dae909d73a68c90b5e7bfe7fecd5d347 SignedHeaders=host_id=0_id=0_id=139604852 content-disposition=attachment; filename=libwacom- surface_1.12-2_amd64.deb=application/octet- stream good: https://objects.githubusercontent.com/github-production-release- asset-2e65be/139604852/86019e52-7bfa-4bc6-8cc1-52147027aee6?X-Amz- Algorithm=AWS4-HMAC-SHA256 Credential=AKIAIWNJYAX4CSVEH53A%2F20211105%2Fus- east-1%2Fs3%2Faws4_request=20211105T160935Z Expires=300 Signature=44d9307e66dfb5b3672ee0082b8801ad2532ac4b6be61c3442fb265ffce72852 SignedHeaders=host_id=0_id=0_id=139604852 content-disposition=attachment%3B%20filename%3Dlibwacom- surface_1.12-2_amd64.deb=application%2Foctet- stream I found this also affects a github repository I recently added for Zotero on 20.04. The problem is fixed in later versions of apt upstream, in Debian and Ubuntu releases. I cherry-picked the 4 commits [3] and provided a package for Focal in my PPA [2] which multiple users have reported (in [1]) solves the issue. It would be really good to get those patches included in 20.04 as an SRU. As the code is in later versions of apt and is focused on the URL encoding only it has minimal potential for causing regressions. [1] https://github.com/linux-surface/linux-surface/issues/625 [2] https://launchpad.net/~tj/+archive/ubuntu/bugfixes [3] https://salsa.debian.org/apt- team/apt/-/commit/06ec0067057e0578f3bc515f6a97d6a9d70824f6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1950095/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
SRU verification for hirsute: I did a testbuild with repo-stamp enabled against the livecd-rootfs version from proposed (2.719.3). See - https://launchpad.net/~toabctl/+livefs/ubuntu/hirsute/proposed/+build/308173 - https://launchpadlibrarian.net/567803112/buildlog_ubuntu_hirsute_amd64_amd64-tarball_proposed_BUILDING.txt.gz That looks good. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in launchpad-buildd: Invalid Status in iptables package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Status in iptables source package in Bionic: Invalid Status in livecd-rootfs source package in Bionic: Invalid Status in lxd source package in Bionic: Invalid Status in iptables source package in Focal: Invalid Status in livecd-rootfs source package in Focal: Fix Released Status in lxd source package in Focal: Invalid Status in iptables source package in Hirsute: Invalid Status in livecd-rootfs source package in Hirsute: Fix Committed Status in lxd source package in Hirsute: Invalid Bug description: [Impact] The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). [Test Plan] - build a livecd-rootfs image with the changes for every series in a PPA - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature - Check that the build did not fail or hang [Where problems could occur] The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. [Original description] when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
This bug was fixed in the package livecd-rootfs - 2.664.33 --- livecd-rootfs (2.664.33) focal; urgency=medium * Install cloud-initramfs-growroot to actually enable rootfs resize. * Fix a grub error by making sure the unicode.pf2 font is installed in the right path for preinstalled amd64 desktop images. livecd-rootfs (2.664.32) focal; urgency=medium * 099-ubuntu-image-customization.chroot: fix a typo in it. livecd-rootfs (2.664.31) focal; urgency=medium [ Łukasz 'sil2100' Zemczak ] * Add the 099-ubuntu-image-customization.chroot for desktop-preinstalled images similar to what we have in groovy+ (for the pi desktop), but improved for amd64 platforms. We need it to generate a valid grub.cfg on the rootfs (similar to ubuntu-cpc) and then use that instead of a static configuration locked on the boot partition (LP: #1949102). [ Brian Murray ] * Properly check ARCH when setting the intel-iot model. livecd-rootfs (2.664.30) focal; urgency=medium [ Thomas Bechtold ] * magic-proxy: Replace http.client with urllib calls. live-build/auto/build: change iptables calls to query rules and quickly check that connectivity works after transparent proxy has been installed. (LP: #1917920) * magic-proxy: fix TypeError when trying to call get_uri() (LP: #1944906) -- Łukasz 'sil2100' Zemczak Fri, 29 Oct 2021 15:33:34 +0200 ** Changed in: livecd-rootfs (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in launchpad-buildd: Invalid Status in iptables package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Status in iptables source package in Bionic: Invalid Status in livecd-rootfs source package in Bionic: Invalid Status in lxd source package in Bionic: Invalid Status in iptables source package in Focal: Invalid Status in livecd-rootfs source package in Focal: Fix Released Status in lxd source package in Focal: Invalid Status in iptables source package in Hirsute: Invalid Status in livecd-rootfs source package in Hirsute: Fix Committed Status in lxd source package in Hirsute: Invalid Bug description: [Impact] The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). [Test Plan] - build a livecd-rootfs image with the changes for every series in a PPA - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature - Check that the build did not fail or hang [Where problems could occur] The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. [Original description] when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1917920] Update Released
The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in launchpad-buildd: Invalid Status in iptables package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Status in iptables source package in Bionic: Invalid Status in livecd-rootfs source package in Bionic: Invalid Status in lxd source package in Bionic: Invalid Status in iptables source package in Focal: Invalid Status in livecd-rootfs source package in Focal: Fix Committed Status in lxd source package in Focal: Invalid Status in iptables source package in Hirsute: Invalid Status in livecd-rootfs source package in Hirsute: Fix Committed Status in lxd source package in Hirsute: Invalid Bug description: [Impact] The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). [Test Plan] - build a livecd-rootfs image with the changes for every series in a PPA - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature - Check that the build did not fail or hang [Where problems could occur] The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. [Original description] when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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
