[Touch-packages] [Bug 1889962] Re: kubuntu 20.04.1 live qa-test, change of display alignment made display unusable
** Summary changed: - kubuntu 20.04.1 live qa-test, screen alignment made display unusable + kubuntu 20.04.1 live qa-test, change of display alignment made display unusable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1889962 Title: kubuntu 20.04.1 live qa-test, change of display alignment made display unusable Status in ubuntu-meta package in Ubuntu: New Bug description: Kubuntu 20.04.1 daily QA-test on dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt) When I adjusted display.settings to have landscape+portrait, the landscape display became unreadable, and I obviously made mistake as portrait was upside-down.. GUI isn't usable as menu is on unusable display this box appears to have IDENTICAL files in /var/crash reported in https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1889960 but are likely unrelated. They were `ubuntu-bug` reported This will be filed against INCORRECT package sorry; I suspect it's radeon related.. Picture of screens https://photos.google.com/share/AF1QipPcjlzMvHtKIQVmi4QLOaY1_yLPbhFXbYFA32iLRCIrT2NTwvY-EpOEh54vwF8g2A?key=M2gtdTN4YjZ2c3RLVWJPMXQ2YXliZ3JMMG1PSW9R Much of the time the image shown on my-left display was changing (lower panel portion especially, also I think where cursor would be on terminal), about 3 changes per second, but at times it became static for awhile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: KDE Date: Sat Aug 1 05:46:46 2020 LiveMediaBuild: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1889962/+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 1889962] Re: kubuntu 20.04.1 live qa-test, screen alignment made display unusable
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1889962 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1889962 Title: kubuntu 20.04.1 live qa-test, screen alignment made display unusable Status in ubuntu-meta package in Ubuntu: New Bug description: Kubuntu 20.04.1 daily QA-test on dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt) When I adjusted display.settings to have landscape+portrait, the landscape display became unreadable, and I obviously made mistake as portrait was upside-down.. GUI isn't usable as menu is on unusable display this box appears to have IDENTICAL files in /var/crash reported in https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1889960 but are likely unrelated. They were `ubuntu-bug` reported This will be filed against INCORRECT package sorry; I suspect it's radeon related.. Picture of screens https://photos.google.com/share/AF1QipPcjlzMvHtKIQVmi4QLOaY1_yLPbhFXbYFA32iLRCIrT2NTwvY-EpOEh54vwF8g2A?key=M2gtdTN4YjZ2c3RLVWJPMXQ2YXliZ3JMMG1PSW9R Much of the time the image shown on my-left display was changing (lower panel portion especially, also I think where cursor would be on terminal), about 3 changes per second, but at times it became static for awhile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: KDE Date: Sat Aug 1 05:46:46 2020 LiveMediaBuild: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1889962/+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 1889962] Re: kubuntu 20.04.1 live qa-test, screen alignment made display unusable
** Description changed: - I'll add details shortly (on more usable box) + Kubuntu 20.04.1 daily QA-test on + dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt) + + When I adjusted display.settings to have landscape+portrait, the + landscape display became unreadable, and I obviously made mistake as + portrait was upside-down.. GUI isn't usable as menu is on unusable + display + + this box appears to have IDENTICAL files in /var/crash reported in + https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1889960 but + are likely unrelated. They were `ubuntu-bug` reported + + This will be filed against INCORRECT package sorry; I suspect it's + radeon related.. + + Picture of screens + https://photos.google.com/share/AF1QipPcjlzMvHtKIQVmi4QLOaY1_yLPbhFXbYFA32iLRCIrT2NTwvY-EpOEh54vwF8g2A?key=M2gtdTN4YjZ2c3RLVWJPMXQ2YXliZ3JMMG1PSW9R + + Much of the time the image shown on my-left display was changing (lower + panel portion especially, also I think where cursor would be on + terminal), about 3 changes per second, but at times it became static for + awhile. + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: KDE Date: Sat Aug 1 05:46:46 2020 LiveMediaBuild: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1889962 Title: kubuntu 20.04.1 live qa-test, screen alignment made display unusable Status in ubuntu-meta package in Ubuntu: New Bug description: Kubuntu 20.04.1 daily QA-test on dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt) When I adjusted display.settings to have landscape+portrait, the landscape display became unreadable, and I obviously made mistake as portrait was upside-down.. GUI isn't usable as menu is on unusable display this box appears to have IDENTICAL files in /var/crash reported in https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1889960 but are likely unrelated. They were `ubuntu-bug` reported This will be filed against INCORRECT package sorry; I suspect it's radeon related.. Picture of screens https://photos.google.com/share/AF1QipPcjlzMvHtKIQVmi4QLOaY1_yLPbhFXbYFA32iLRCIrT2NTwvY-EpOEh54vwF8g2A?key=M2gtdTN4YjZ2c3RLVWJPMXQ2YXliZ3JMMG1PSW9R Much of the time the image shown on my-left display was changing (lower panel portion especially, also I think where cursor would be on terminal), about 3 changes per second, but at times it became static for awhile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: KDE Date: Sat Aug 1 05:46:46 2020 LiveMediaBuild: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1889962/+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 1889962] [NEW] kubuntu 20.04.1 live qa-test, screen alignment made display unusable
Public bug reported: I'll add details shortly (on more usable box) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: KDE Date: Sat Aug 1 05:46:46 2020 LiveMediaBuild: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1889962 Title: kubuntu 20.04.1 live qa-test, screen alignment made display unusable Status in ubuntu-meta package in Ubuntu: New Bug description: I'll add details shortly (on more usable box) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: KDE Date: Sat Aug 1 05:46:46 2020 LiveMediaBuild: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1889962/+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 1886585] Re: Restarting display / screen
** Package changed: ubuntu-release-upgrader (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/1886585 Title: Restarting display / screen Status in xorg package in Ubuntu: New Bug description: The computer stops and restarts the screen and after about 2 secs the display works normally in maybe 30 secs . The proces repeats for several minutes (maybe 24 mins) and then suddenly everything works normally. If I go into some serous work like this report I am able to do that without disturbance. If I go back to no working apps the operation continues with on/off working. My system is the latest 20.04 software upgrade from the Beta-version. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.20 ProcVersionSignature: Ubuntu 5.4.0-41.45-generic 5.4.44 Uname: Linux 5.4.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 6 22:52:53 2020 InstallationDate: Installed on 2019-10-20 (260 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. VarLogDistupgradeAptlog: Log time: 2020-06-25 21:27:41.194955 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1886585/+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 1886585] [NEW] Restarting display / screen
You have been subscribed to a public bug: The computer stops and restarts the screen and after about 2 secs the display works normally in maybe 30 secs . The proces repeats for several minutes (maybe 24 mins) and then suddenly everything works normally. If I go into some serous work like this report I am able to do that without disturbance. If I go back to no working apps the operation continues with on/off working. My system is the latest 20.04 software upgrade from the Beta-version. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.20 ProcVersionSignature: Ubuntu 5.4.0-41.45-generic 5.4.44 Uname: Linux 5.4.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 6 22:52:53 2020 InstallationDate: Installed on 2019-10-20 (260 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. VarLogDistupgradeAptlog: Log time: 2020-06-25 21:27:41.194955 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal package-from-proposed -- Restarting display / screen https://bugs.launchpad.net/bugs/1886585 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 1889941] [NEW] AMD Navi10 GPU powerplay issues when using two DisplayPort connectors
Public bug reported: Connecting two displayport monitors to a 5700XT causes flickering on one of the screens, issue appears to be occurring upstream and is being tracked here: https://gitlab.freedesktop.org/drm/amd/-/issues/929 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 21:45:59 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1682:5701] InstallationDate: Installed on 2020-06-28 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=f17edc40-7eaf-4768-977d-f0e067db9b04 ro amdgpu.noretry=0 processor.max_cstate=5 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1407 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1407:bd04/01/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1889941 Title: AMD Navi10 GPU powerplay issues when using two DisplayPort connectors Status in xorg package in Ubuntu: New Bug description: Connecting two displayport monitors to a 5700XT causes flickering on one of the screens, issue appears to be occurring upstream and is being tracked here: https://gitlab.freedesktop.org/drm/amd/-/issues/929 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 21:45:59 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1682:5701] InstallationDate: Installed on 2020-06-28 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=f17edc40-7eaf-4768-977d-f0e067db9b04 ro amdgpu.noretry=0 processor.max_cstate=5 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1407 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.c
[Touch-packages] [Bug 1877769] Re: [SRU] Rewinding cache triggers obsolete adjustments consuming a lot of CPU
Verified 2.3ubuntu0.1 on Focal: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/u/unattended- upgrades/20200722_172955_59a0f@/log.gz : ... Running ./test_rewind.py with python3 INFO:root:Allowed origins are: o=Ubuntu,a=lucid-security INFO:root:Initial blacklist: ant-doc INFO:root:Initial whitelist (not strict): DEBUG:root:Marking not allowed with -32768 pin DEBUG:root:Applying pinning: PkgFilePin(id=0, priority=-32768) DEBUG:root:Applying pin -32768 to package_file: DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting z-package's dependencies DEBUG:root:sanity check failed for: set() : no package is selected to be upgraded or installed . -- Ran 1 test in 0.063s OK ... ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1877769 Title: [SRU] Rewinding cache triggers obsolete adjustments consuming a lot of CPU Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Focal: Fix Committed Status in unattended-upgrades package in Debian: Fix Released Bug description: [Impact] * Unattended-upgrades consumes excessive amount of CPU when rewinding cache trying to mark packages to upgrade or install even when they are already marked to be upgraded or installed. This can be triggered by packages held back. [Test Case] * Run test_rewind.py: -Fixed output: $ python3 test_rewind.py INFO:root:Allowed origins are: o=Ubuntu,a=lucid-security INFO:root:Initial blacklist: ant-doc INFO:root:Initial whitelist (not strict): DEBUG:root:Marking not allowed with -32768 pin DEBUG:root:Applying pinning: PkgFilePin(id=0, priority=-32768) DEBUG:root:Applying pin -32768 to package_file: DEBUG:root:Applying pinning: PkgPin(pkg='/^ant-doc/', priority=-32768) DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting z-package's dependencies DEBUG:root:sanity check failed for: set() : no package is selected to be upgraded or installed . -- Ran 1 test in 0.022s OK - Not fixed output: $ python3 test_rewind.py INFO:root:Allowed origins are: o=Ubuntu,a=lucid-security INFO:root:Initial blacklist: ant-doc INFO:root:Initial whitelist (not strict): DEBUG:root:Marking not allowed with -32768 pin DEBUG:root:Applying pinning: PkgFilePin(id=0, priority=-32768) DEBUG:root:Applying pin -32768 to package_file: DEBUG:root:Applying pinning: PkgPin(pkg='/^ant-doc/', priority=-32768) DEBUG:root:APT::VersionedKernelPackages is not set DEBUG:root:adjusting candidate version: test-package=2.0 DEBUG:root:adjusting candidate version: test2-package=2.0 DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting z-package's dependencies DEBUG:root:sanity check failed for: set() : no package is selected to be upgraded or installed DEBUG:root:falling back to adjusting test-package's dependencies DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting test3-package's dependencies DEBUG:root:falling back to adjusting test-package's dependencies DEBUG:root:falling back to adjusting test2-package's dependencies DEBUG:root:falling back to adjusting test3-package's dependencies . -- Ran 1 test in 0.024s (Note the extra "DEBUG:root:falling back to adjusting" ... lines) [Regression Potential] * Minimal. The very small change fixes how call_checked() verifies that the package to be upgrades/installed is indeed marked to either being installed or upgraded. In the worst case, if call_checked() erroneously returns success for a package as a result of a regression, unattended-upgrades does not fall back to adjusting packages to make marking successful. Later unattended-upgrades finds out that the package could not be marked and should be treated as kept back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1877769/+subscriptions -- Mailing list: https://launchpad.net/~touch-p
[Touch-packages] [Bug 1883082] Re: Crash when using Package-Whitelist-Strict
Verified 2.3ubuntu0.1 on Focal (checking reproducibility with buggy version first): root@ff-uu-1-verify:~# apt list --upgradable Listing... Done open-vm-tools/focal-updates 2:11.1.0-2~ubuntu20.04.1 amd64 [upgradable from: 2:11.0.5-4] N: There is 1 additional version. Please use the '-a' switch to see it root@ff-uu-1-verify:~# unattended-upgrade root@ff-uu-1-verify:~# echo 'Unattended-Upgrade::Package-Whitelist-Strict "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-whitelist root@ff-uu-1-verify:~# echo 'Unattended-Upgrade::Package-Whitelist {"foo";}' >> /etc/apt/apt.conf.d/51unattended-upgrades-whitelist root@ff-uu-1-verify:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2512, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1983, in main res = run(options, rootdir, mem_log, logfile_dpkg, File "/usr/bin/unattended-upgrade", line 2124, in run cache = UnattendedUpgradesCache(rootdir=rootdir) File "/usr/bin/unattended-upgrade", line 171, in __init__ apt.Cache.__init__(self, rootdir=rootdir) File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__ self.open(progress) File "/usr/bin/unattended-upgrade", line 330, in open self.apply_pinning(self.pinning_from_config()) File "/usr/bin/unattended-upgrade", line 302, in pinning_from_config and policy.get_candidate_ver(pkg) > -1: # type: ignore TypeError: '>' not supported between instances of 'apt_pkg.Version' and 'int' root@ff-uu-1-verify:~# sed -i 's/backports/proposed/' /etc/apt/sources.list root@ff-uu-1-verify:~# apt update Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://security.ubuntu.com/ubuntu focal-security InRelease Get:4 http://archive.ubuntu.com/ubuntu focal-proposed InRelease [265 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages [42.9 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-proposed/main Translation-en [19.5 kB] Get:7 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 c-n-f Metadata [1308 B] Get:8 http://archive.ubuntu.com/ubuntu focal-proposed/restricted amd64 Packages [3684 B] Get:9 http://archive.ubuntu.com/ubuntu focal-proposed/restricted Translation-en [1252 B] Get:10 http://archive.ubuntu.com/ubuntu focal-proposed/restricted amd64 c-n-f Metadata [116 B] Get:11 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 Packages [40.9 kB] Get:12 http://archive.ubuntu.com/ubuntu focal-proposed/universe Translation-en [22.5 kB] Get:13 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 c-n-f Metadata [1688 B] Get:14 http://archive.ubuntu.com/ubuntu focal-proposed/multiverse amd64 Packages [672 B] Get:15 http://archive.ubuntu.com/ubuntu focal-proposed/multiverse Translation-en [3492 B] Get:16 http://archive.ubuntu.com/ubuntu focal-proposed/multiverse amd64 c-n-f Metadata [188 B] Fetched 403 kB in 2s (179 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 17 packages can be upgraded. Run 'apt list --upgradable' to see them. root@ff-uu-1-verify:~# apt install unattended-upgrades Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. Suggested packages: bsd-mailx default-mta | mail-transport-agent needrestart The following packages will be upgraded: unattended-upgrades 1 upgraded, 0 newly installed, 0 to remove and 16 not upgraded. Need to get 48.7 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 unattended-upgrades all 2.3ubuntu0.1 [48.7 kB] Fetched 48.7 kB in 0s (135 kB/s) Preconfiguring packages ... (Reading database ... 31266 files and directories currently installed.) Preparing to unpack .../unattended-upgrades_2.3ubuntu0.1_all.deb ... Unpacking unattended-upgrades (2.3ubuntu0.1) over (2.3) ... Setting up unattended-upgrades (2.3ubuntu0.1) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for systemd (245.4-4ubuntu3.2) ... seroot@ff-uu-1-verify:~# sed -i 's/proposed/backports/' /etc/apt/sources.list root@ff-uu-1-verify:~# apt update Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://security.ubuntu.com/ubuntu focal-security InRelease Get:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 c-n-f Metadata [112 B] Get:6 http://archive.ubuntu.com/ubuntu focal-backports/restricted amd64 c-n-f Metadata [116 B] Get:7 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 Packages [3096 B] Get:8 http://archive.ubuntu.com/ubuntu focal-back
[Touch-packages] [Bug 1832754] Autopkgtest regression report (systemd/237-3ubuntu10.42)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.42) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.0/5.0.0-58.62~18.04.1 (armhf) linux-aws-edge/5.0.0-1019.21~18.04.1 (amd64) linux-hwe-5.4/5.4.0-42.46~18.04.1 (arm64, armhf) lxc/3.0.3-0ubuntu1~18.04.1 (arm64) dovecot/1:2.2.33.2-1ubuntu4.5 (armhf) casync/2+61.20180112-1 (amd64) linux-raspi2-5.3/5.3.0-1030.32~18.04.2 (armhf) umockdev/0.11.1-1 (armhf) netplan.io/0.99-0ubuntu3~18.04.3 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1832754 Title: "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] shutdown sometimes fails to unmount some fs, which causes shutdown hang [test case] it's unclear what the specific configuration is to be able to reproduce this, but there are some examples in the upstream bug [regression potential] as this adjusts shutdown umounting, any regression would likely involve either failure to unmount some filesystems on shutdown and/or failure to shutdown the system. [scope] this is needed for b. this is fixed upstream by PR 8429 which is included starting in v239, so this is fixed already in Focal and later. this was caused by upstream commit d5641e0d7e8 which was added in v236, so this bug is not present in x. [original description] I am using Xubuntu 18.04 64 bit and got "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. systemd: 237-3ubuntu10.22 It's this issue: https://github.com/systemd/systemd/issues/8155 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832754/+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 1876018] Autopkgtest regression report (systemd/237-3ubuntu10.42)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.42) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.0/5.0.0-58.62~18.04.1 (armhf) linux-aws-edge/5.0.0-1019.21~18.04.1 (amd64) linux-hwe-5.4/5.4.0-42.46~18.04.1 (arm64, armhf) lxc/3.0.3-0ubuntu1~18.04.1 (arm64) dovecot/1:2.2.33.2-1ubuntu4.5 (armhf) casync/2+61.20180112-1 (amd64) linux-raspi2-5.3/5.3.0-1030.32~18.04.2 (armhf) umockdev/0.11.1-1 (armhf) netplan.io/0.99-0ubuntu3~18.04.3 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1876018 Title: 40-vm-hotadd.rules attempts to set non-existent sysfs parameters Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [impact] 40-vm-hotadd.rules unconditionally tries onlining memory, which results in logged error messages if the memory is already online [test case] since this rules file restricts operation to only hyper-v or xen guests, boot a hyper-v or xen vm guest, and check for logged error msgs like: Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7: /usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid argument alternately, to test on a vm guest other than hyper-v or xen, comment/remove the 'GOTO="vm_hotadd_end"' line from the rules file and reboot. [regression potential] as this adds a check before attempting to online memory for hyper-v and xen vm guests, any regression would likely involve failure to correctly online all memory on those guest platforms. [scope] this rule has been around for a long time, so is needed for x/b/f/g. [original description] In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu) tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes resulting in warnings such as: Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7: /usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid argument Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics, removed, or something else. This behavior is present on systems upgraded from 18.04 (via d-r-u) as well as new focal systems, upon first reboot of the VM. udev: 245.4-4ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+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 1860926] Autopkgtest regression report (systemd/237-3ubuntu10.42)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.42) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.0/5.0.0-58.62~18.04.1 (armhf) linux-aws-edge/5.0.0-1019.21~18.04.1 (amd64) linux-hwe-5.4/5.4.0-42.46~18.04.1 (arm64, armhf) lxc/3.0.3-0ubuntu1~18.04.1 (arm64) dovecot/1:2.2.33.2-1ubuntu4.5 (armhf) casync/2+61.20180112-1 (amd64) linux-raspi2-5.3/5.3.0-1030.32~18.04.2 (armhf) umockdev/0.11.1-1 (armhf) netplan.io/0.99-0ubuntu3~18.04.3 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1860926 Title: Ubuntu 20.04 Systemd fails to configure bridged network Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Eoan: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: [impact] A bridged interface with static ipv4 address and gateway configuration will fail to properly add the route via the gateway, leaving the system without a globally working network. [test case] On a Focal system, remove all network configuration and create this netplan: network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0: interfaces: [enp4s0] dhcp4: no addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] Replace the interface name 'enp4s0' with the actual interface name on the test system. Reboot the system, and check the route to the gateway, which will be missing: root@lp1860926-f:~# ip r 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 The route is expected to be present, e.g.: ubuntu@lp1860926-e:~$ ip r default via 192.168.0.1 dev br0 proto static 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 [test case, pre-focal] same netplan as above. Reboot, and the bridge should have its address and route: ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever ubuntu@test-e:~$ ip r default via 192.168.0.1 dev br0 proto static linkdown 192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown add and remove carrier, by adding and removing a slave interface: ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet 192.168.0.4/24 brd 192.168.0.255 scope global br0 valid_lft forever preferred_lft forever inet6 fe80::5411:daff:fe23:bb93/64 scope link valid_lft forever preferred_lft forever ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster the bridge no longer has its address after losing carrier: ubuntu@test-e:~$ ip a show br0 3: br0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff inet6 fe80::5411:daff:fe23:bb93/64 scope link valid_lft forever preferred_lft forever [regression potential] Any regression would likely involve incorrectly configured network after an interface carrier gain/loss. [scope] This is needed for Focal, Eoan, and Bionic. While this only reproduces at boot for Focal, the general loss of configuration on carrier loss even when ConfigureWithoutCarrier=true is reproducable on all releases except Xenial, which does not have the ConfigureWithoutCarrier= parameter. [original description] Freshly installed Ubuntu 20.04 fully patched to days date with static IP address works fine and survives a reboot network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false addresses: [192.168.0.4/24] gateway4: 192.168.0.1 nameservers: search: [mydomain] addresses: [192.168.0.1,192.168.0.2,192.168.0.3] however when converted to a bridged network for kvm network: version: 2 renderer: networkd ethernets: enp4s0: dhcp4: false bridges: br0
[Touch-packages] [Bug 1886197] Autopkgtest regression report (systemd/237-3ubuntu10.42)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.42) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.0/5.0.0-58.62~18.04.1 (armhf) linux-aws-edge/5.0.0-1019.21~18.04.1 (amd64) linux-hwe-5.4/5.4.0-42.46~18.04.1 (arm64, armhf) lxc/3.0.3-0ubuntu1~18.04.1 (arm64) dovecot/1:2.2.33.2-1ubuntu4.5 (armhf) casync/2+61.20180112-1 (amd64) linux-raspi2-5.3/5.3.0-1030.32~18.04.2 (armhf) umockdev/0.11.1-1 (armhf) netplan.io/0.99-0ubuntu3~18.04.3 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1886197 Title: FTBFS in b due to libseccomp change Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] systemd FTBFS in b because __NR__sysctl was force-defined by libseccomp in 2.4.1-0ubuntu0.18.04.2, but that force-defining was (correctly) reverted in the latest version 2.4.3-1ubuntu3.18.04.2. On arm64, __NR__sysctl is not defined, so the build now fails, e.g.: https://launchpadlibrarian.net/486997294/buildlog_ubuntu-bionic-arm64.systemd_237-3ubuntu10.42~202007031245~ubuntu18.04.1_BUILDING.txt.gz ../src/test/test-seccomp.c: In function ‘test_protect_sysctl’: ../src/test/test-seccomp.c:251:5: error: "__NR__sysctl" is not defined, evaluates to 0 [-Werror=undef] #if __NR__sysctl > 0 ^~~~ [test case] build systemd on bionic with latest packages (i.e. with latest libseccomp2 package) [regression potential] this adds a defined() check before comparing the __NR__sysctl value, so any regression would be limited to the specific function test_protect_sysctl() which is part of the test framework, thus leading to a failed build or incorrectly passed/failed test. [scope] this is needed only in Bionic. This is fixed upstream by commit 4df8fe8415eaf4abd5b93c3447452547c6ea9e5f which is included in v244 and later, so this is fixed already for Focal and later. Xenial does not include the __NR__sysctl check so does not need this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1886197/+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 1886115] Autopkgtest regression report (systemd/237-3ubuntu10.42)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.42) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.0/5.0.0-58.62~18.04.1 (armhf) linux-aws-edge/5.0.0-1019.21~18.04.1 (amd64) linux-hwe-5.4/5.4.0-42.46~18.04.1 (arm64, armhf) lxc/3.0.3-0ubuntu1~18.04.1 (arm64) dovecot/1:2.2.33.2-1ubuntu4.5 (armhf) casync/2+61.20180112-1 (amd64) linux-raspi2-5.3/5.3.0-1030.32~18.04.2 (armhf) umockdev/0.11.1-1 (armhf) netplan.io/0.99-0ubuntu3~18.04.3 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1886115 Title: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot Status in libseccomp package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Fix Released Status in libseccomp source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Bug description: [impact] systemd sometimes crashes on boot due to free of uninitalized var [test case] a specific system setup is required, see original description [regression potential] any regression would likely involve further crashes on boot. [scope] this is needed in b. this is fixed upstream by commit 58d9d89b4b41189bdcea86c2ad5cf708b7d54aca which is included starting in v240, so this is included already in f and later. this is caused by commit 25cd49647c8 which is included starting in v237, so this bug does not exist in x. [original description] After applying updates to Ubuntu 18.04 my desktop (apple mini with i5-2415M CPU) failed to complete the boot process. A few seconds into the boot, the last message displayed is "/var mounted". The system then appears to hang indefinitely. Luckily, the 'rescue' boot image allows the boot process to proceed sufficiently far to allow a root shell to be spawned. Unfortunately no log files were written during the unsuccessful attempts to boot. Spawning a 2nd root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to observe the message 'systemd freezing execution' after I closed the first root shell and resumed the boot process. Further a core file was created (belonging to /sbin/init) in the root fs --8<-- (gdb) bt #0 0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78 #1 0x563b957223b7 in ?? () #2 #3 __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103 #4 0x563b9577c22e in ?? () #5 0x563b957672d6 in ?? () #6 0x563b9576ba22 in ?? () #7 0x563b9574f51a in ?? () #8 0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so #9 0x7f16803a53ea in sd_event_dispatch () from /lib/systemd/libsystemd-shared-237.so #10 0x7f16803a5579 in sd_event_run () from /lib/systemd/libsystemd-shared-237.so #11 0x563b9572a49d in ?? () #12 0x563b9571560c in ?? () #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, argv=0x7ffe78153758, init=, fini=, rtld_fini=, stack_end=0x7ffe78153748) at ../csu/libc-start.c:310 #14 0x563b957164fa in ?? () (gdb) -->8-- and the kernel message buffer lists --8<-- traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 error:0 in libc-2.27.so[7f17ebed7000+1e7000] -->8-- . To me that looked a bit like Bug 669702 of Gentoo (https://bugs.gentoo.org/669702) and indeed one of the (few) updates applied just prior the reboot was the update of libseccomp. I was able to circumvent the problem by disabling (commenting out) the syscall filtering requested by systemd (on my system, only /etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be modified). --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-30 (460 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Apple Inc. Macmini5,1 NonfreeKernelModules: wl Package: systemd 237-3ubuntu10.41 [modified: lib/systemd/system/systemd-resolved.service] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh inst
[Touch-packages] [Bug 1881972] Autopkgtest regression report (systemd/237-3ubuntu10.42)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.42) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.0/5.0.0-58.62~18.04.1 (armhf) linux-aws-edge/5.0.0-1019.21~18.04.1 (amd64) linux-hwe-5.4/5.4.0-42.46~18.04.1 (arm64, armhf) lxc/3.0.3-0ubuntu1~18.04.1 (arm64) dovecot/1:2.2.33.2-1ubuntu4.5 (armhf) casync/2+61.20180112-1 (amd64) linux-raspi2-5.3/5.3.0-1030.32~18.04.2 (armhf) umockdev/0.11.1-1 (armhf) netplan.io/0.99-0ubuntu3~18.04.3 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1881972 Title: systemd-networkd crashes with invalid pointer Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] systemd-networkd double-free causes crash under some circumstances, such as adding/removing ip rules [test case] Use networkd-dispatcher events to add and remove IP rules. The example scripts below are contrived (and by themselves likely to break access to a machine) but would be adequate to trigger the bug. Put scripts like these in place, reboot or run "netplan apply", and then leave the machine running for a few DHCP renewal cycles. === /etc/networkd-dispatcher/configured.d/test.sh === #!/bin/bash /sbin/ip rule add iif lo lookup 99 /sbin/ip rule add to 10.0.0.0/8 iif lo lookup main === END === === /etc/networkd-dispatcher/configuring.d/test.sh === #!/bin/bash # Tear down existing ip rules so they aren't duplicated OLDIFS="${IFS}" IFS=" " for rule in `ip rule show|grep "iif lo" | cut -d: -f2-`; do IFS="${OLDIFS}" ip rule delete ${rule} done IFS="${OLDIFS}" === END === [regression potential] this strdup's strings during addition of routing policy rules, so any regression would likely occur when adding/modifying/removing ip rules, possibly including networkd segfault or failure to add/remove/modify ip rules. [scope] this is needed for bionic. this is fixed by upstream commit eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c which is included starting in v240, so this is already included in Focal and later. I did not research what original commit introduced the problem, but the reporter indicates this did not happen for Xenial so it's unlikely this is a problem in Xenial or earlier. [original description] This is a serious regression with systemd-networkd that I ran in to while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm- ssd/ubuntu-bionic-18.04-amd64-server-20200131 with systemd-237-3ubuntu10.33 does NOT have the problem, but the next most recent AWS AMI ubuntu/images/hvm-ssd/ubuntu- bionic-18.04-amd64-server-20200311 with systemd-including 237-3ubuntu10.39 does. Also, a system booted from the (good) 20200131 AMI starts showing the problem after updating only systemd (to 237-3ubuntu10.41) and its direct dependencies (e.g. 'apt-get install systemd'). So I'm fairly confident that a change to the systemd package between 237-3ubuntu10.33 and 237-3ubuntu10.39 introduced the problem and it is still present. On the NAT router I use three interfaces and have separate routing tables for admin and forwarded traffic. Things come up fine initially but every 30-60 minutes (DHCP lease renewal time?) one or more interfaces is reconfigured and most of the time systemd-networkd will crash and need to be restarted. Eventually the system becomes unreachable when the default crash loop backoff logic prevents the network service from being restarted at all. The log excerpt attached illustrates the crash loop. Also including the netplan and networkd config files below. # grep . /etc/netplan/* /etc/netplan/50-cloud-init.yaml:# This file is generated from information provided by the datasource. Changes /etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance reboot. To disable cloud-init's /etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a file /etc/netplan/50-cloud-init.yaml:# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: /etc/netplan/50-cloud-init.yaml:# network: {config: disabled} /etc/netplan/50-cloud-init.yaml:network: /etc/netplan/50-cloud-init.yaml:version: 2 /etc/netplan/50-cloud-init.yaml:ethernets: /etc/netplan/50-cloud-init.yaml:ens5: /etc/netplan/50-cloud-init.yaml:dhcp4: true /etc/net
[Touch-packages] [Bug 1870585] Re: Not cleaning /var/tmp by default
** Bug watch added: Debian Bug tracker #966621 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966621 ** Also affects: systemd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966621 Importance: Unknown Status: Unknown -- 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/1870585 Title: Not cleaning /var/tmp by default Status in systemd package in Ubuntu: New Status in systemd package in Debian: Unknown Bug description: 1) 20.04 2) 245.2-1ubuntu2 3) I expect /var/tmp to be cleaned up in some way. 4) It's commented out per https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773313 In sosreport was comparing the difference between /tmp (Ubuntu/Debian) and /var/tmp (RH) and determined that as long as /var/tmp gets cleaned on a regular basis we would prefer /var/tmp. The bug that appears to have prompted the disabling was fixed a long time ago, can we have this 30d delete re-enabled by default? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870585/+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 1722478]
I have the same problem on my Thinkpad x240 with Ubuntu 20.04 Linux E5450 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux This kernel parameter workaround "psmouse.synaptics_intertouch=0" work in the meantime (forever since it's 3 years old bug ??) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling and click-and-drag no longer works after resuming from suspend Status in Linux: Confirmed Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+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 1835660] Re: initramfs unpacking failed
Confirmed on Linux 5.4.0-42-generic with Linux Mint 20 (Ubuntu 20.04) clean install. Changing lz4 to gzip in /etc/initramfs-tools/initramfs.conf removed the error (after doing sudo update-initramfs -u) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Same problem confirmed it's an issue. Using Galaxy Buds+ and Beats X. Please help fix this. We are all working from home and need this feature. -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1812143] Re: gsettings-desktop-schemas 3.31 breaks mutter 3.30
I am getting this error while installing hostapd, lighttpd and isc-dhcp- server on Kali Linux. How can I fix this error and install these packages? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1812143 Title: gsettings-desktop-schemas 3.31 breaks mutter 3.30 Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Won't Fix Status in ukwm package in Ubuntu: Fix Released Bug description: We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to gsettings-desktop-schemas. Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in gdm/gnome-shell being unable to start. Also, ukwm is a fork of mutter so the Kylin devs need to backport the relevant commits from mutter. The problematic gsettings commit was: https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c I think the mutter commits can be found at https://gitlab.gnome.org/GNOME/mutter/merge_requests/133 We could easily add a dummy key with the old name but I'm thinking the way forward is just to package the newer mutter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+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 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Marcelo Pires (marcelo-pires-silva) -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in PulseAudio: Unknown Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,
[Touch-packages] [Bug 1881976] Re: apport-gtk and apport-kde install xiterm+thai as dependency (x-terminal-emulator)
Hello Adam, or anyone else affected, Accepted apport into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu27.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apport (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1881976 Title: apport-gtk and apport-kde install xiterm+thai as dependency (x -terminal-emulator) Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Bug description: [Impact] * When installing apport-gtk (or apport-kde) on a non-GUI installation (cloud image, server image) as a dependency providing x-terminal-emulator xiterm+thai package is pulled in, which is not appropriate for most locales. My understanding is it was selected due to lowest number of unsatisfied dependencies. [Test Case] * lxc launch ubuntu:20.04 test * lxc shell test * apt update * apt install apport-gtk * Examine the packages listed to be installed: xiterm+thai is one of them. [Regression Potential] * In dedicated archive mirrors with limited number of packages changing that may cause errors due to packages missing in the archive. However, that's unlikely. [Other Info] * It is not affecting bionic, since x-terminal-emulator is listed as 'Suggests' not 'Depends' there. * Original bug description: Vanilla install of Ubuntu 20.04 set to an Australian locale includes the "Thai X Terminal" package. This package should not be included. I noticed that it is also reported against Xubuntu and Lubuntu: https://bugs.launchpad.net/lubuntu-next/+bug/1747341 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1881976/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Hello Ryan, or anyone else affected, Accepted bcache-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bcache- tools/1.0.8-3ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: bcache-tools (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Status in bcache-tools source package in Focal: Fix Committed Status in systemd source package in Focal: In Progress Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1888685] Re: rsync fails after installing level 3.2.1
My resync is working fine again. Thanks for your attention to this bug- report. -- 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/1888685 Title: rsync fails after installing level 3.2.1 Status in rsync package in Ubuntu: Triaged Status in rsync package in Debian: Fix Released Bug description: After installation of rsync.3.2.1 my attempt to sync fails with chroot error. The rsyncd.log indicates that rsync can't find the directories I want to sync. 2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 873 2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings failed: No such file or directory (2) Dropping back to Ubuntu 20.04 and rsync works again. The rsync update was install 7/18. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: rsync 3.2.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 10:28:17 2020 InstallationDate: Installed on 2020-07-06 (16 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+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 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
That#s a spin off of the already Fix Released ticket LP 1888654 ** Package changed: linux (Ubuntu) => binutils (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: binutils (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Foundations Team (canonical-foundations) ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Also affects: binutils (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: binutils (Ubuntu Groovy) Importance: Undecided Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Changed in: binutils (Ubuntu Groovy) Status: New => Fix Released ** Changed in: binutils (Ubuntu Groovy) Assignee: Canonical Foundations Team (canonical-foundations) => (unassigned) ** Changed in: binutils (Ubuntu Focal) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1889742 Title: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: New Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Focal: New Status in binutils source package in Groovy: Fix Released Bug description: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889742/+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 1889742] [NEW] [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
You have been subscribed to a public bug: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 ** Affects: binutils (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-187207 severity-medium targetmilestone-inin2004 -- [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) https://bugs.launchpad.net/bugs/1889742 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils 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 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic
Hey Folks, Does the -proposed changes get automatically integrated to -updates after a certain time has passed, or does this require somebody to take action? It would be great to have this update rolled out to 18.04 before OVS 2.14 is released in a week or two. Regards, -Harry -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1883880 Title: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Bionic: Fix Committed Status in binutils package in Debian: Confirmed Bug description: [Impact] * the assembler scales non 8 bit cases which was identified to break e.g. some AVX512 code. It is nasty as it isn't a compile/link/ time error. Instead the instructions might silently be corrupted until running. Things might even work on some but fail on other systems if e.g. the AVX code paths only run on newer chips. * The fix is upstream for a while and not re-changed again. Furthermore it is in several Ubuntu releases without bugs due to that, which should make the backport rather safe. [Test Case] * Simple example to trigger the bug: echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | grep vmovaps The expected output is that the objdump output matches the vmovaps instruction input. When using binutils with the bug, the initial 0x40 will be incorrect. Working: $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | grep vmovaps 0: 62 f1 7c 48 28 04 05 vmovaps 0x40(,%rax,1),%zmm0 Failing: $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | grep vmovaps 0: 62 f1 7c 48 28 04 05 vmovaps 0x1(,%rax,1),%zmm0 [Regression Potential] * Well, this is a double edged sword. On one hand this is fortunately a small change and only affects something formerly clearly broken. So it should be good and only change cases formerly being bad. But OTOH binutils areused in so many cases that I feel unable to say "nothing will happen". The change goes to the gnu assembler, so that is the place to look out for regressions. [Other Info] * needs a sponsor experienced with binutils to check potential pitfalls --- Hi, DPDK has run into some issues in the past https://bugs.dpdk.org/show_bug.cgi?id=97 https://bugs.dpdk.org/show_bug.cgi?id=249 Eventually the issues got resolved in binutils via https://sourceware.org/bugzilla/show_bug.cgi?id=23465 After binutils is fixed people rebuilding DPDK themselve can use http://patches.dpdk.org/patch/71679/ to gain more performance while on Bionics bintuils level. Note: Bionic is on DPDK 17.11.x which will not get further stable release afaik. But quite often people build their own DPDK. In fact this came up as a request from Openvswitch upstream/Intel to allow such builds on Bionic. I'd ping those people about the bug and ask them to participate in the verification if this becomes an SRU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1883880/+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 1888685] Re: rsync fails after installing level 3.2.1
OK, so the directory being in /home is the culprit, I could reproduce the issue and found where the problem is. At some point rsync added ProtectHome=on option to its service file, /lib/systemd/system/rsync.service. This has been reverted in upstream git at [1] as it's too restrictive. The fix landed in rsync v3.2.2 which is already in Debian; Ubuntu will pick it up with the next sync. In the meantime you can workaround the problem by manually disabling ProtectHome. Thanks again for reporting the issue and for providing all the details. [1] https://github.com/WayneD/rsync/commit/ce12142c459788b611da5f5d525e0486822b043a ** Changed in: rsync (Ubuntu) Status: Incomplete => Triaged ** Changed in: rsync (Ubuntu) Milestone: None => ubuntu-20.10 ** Also affects: rsync (Debian) Importance: Undecided Status: New ** Changed in: rsync (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1888685 Title: rsync fails after installing level 3.2.1 Status in rsync package in Ubuntu: Triaged Status in rsync package in Debian: Fix Released Bug description: After installation of rsync.3.2.1 my attempt to sync fails with chroot error. The rsyncd.log indicates that rsync can't find the directories I want to sync. 2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 873 2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings failed: No such file or directory (2) Dropping back to Ubuntu 20.04 and rsync works again. The rsync update was install 7/18. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: rsync 3.2.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 10:28:17 2020 InstallationDate: Installed on 2020-07-06 (16 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+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 1888654] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-07-31 04:33 EDT--- IBM Bugzilla status-> closed, Fix Released with groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1888654 Title: [UBUNTU 20.10] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Groovy: Fix Released Bug description: On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. ---Additional Hardware Info--- n/a ---uname output--- n/a ---Debugger Data--- n/a Machine Type = z13 2964 ---Steps to Reproduce--- n/a Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888654/+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 1888654] Re: [UBUNTU 20.10] Accept vector alignment hints on z13 (binutils)
** Tags removed: targetmilestone-inin2004 ** Tags added: targetmilestone-inin2010 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1888654 Title: [UBUNTU 20.10] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Groovy: Fix Released Bug description: On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. ---Additional Hardware Info--- n/a ---uname output--- n/a ---Debugger Data--- n/a Machine Type = z13 2964 ---Steps to Reproduce--- n/a Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888654/+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 1888654] Re: [UBUNTU 20.10] Accept vector alignment hints on z13 (binutils)
** Also affects: binutils (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: binutils (Ubuntu Groovy) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: Fix Released ** No longer affects: binutils (Ubuntu Focal) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1888654 Title: [UBUNTU 20.10] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Groovy: Fix Released Bug description: On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. ---Additional Hardware Info--- n/a ---uname output--- n/a ---Debugger Data--- n/a Machine Type = z13 2964 ---Steps to Reproduce--- n/a Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888654/+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 1870260] Re: initramfs unpacking failed: Decoding failed", message appears on boot up.
*** This bug is a duplicate of bug 1835660 *** https://bugs.launchpad.net/bugs/1835660 Unfortunately, Ubuntu developers forgot something. I have been building my optimized kernel with lz4 for 5 years ... and here it is necessary to compile or upload lz4 and only then e.g. sudo update-initramfs -u -k 5.7.11-ext73-77.11-kabylake-8th and after restarting the message you will not see https://github.com/lz4/lz4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1870260 Title: initramfs unpacking failed: Decoding failed", message appears on boot up. Status in linux package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: OS : Ubuntu 20.04(20200401) Problem: "initramfs unpacking failed: Decoding failed", message appears on boot up solution: If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to COMPRESS=gzip then the error is fixing . Expected solution: This but in there from a long time I have seen this from Ubuntu 18.04,19.04,19.10 now in 20.04 So please fix it or change it from lz4 to gzip. an early reply is highly appreciated Thank you . --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tamal 1451 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx Package: ubuntu-meta ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=29f895bf-ab7b-4df8-8e9a-c277376a2685 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd11/29/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 5AY34PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870260/+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