[Bug 1927158] Re: Problem with python-trio with s3ql
** Bug watch added: Debian Bug tracker #982381 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982381 ** Also affects: s3ql (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982381 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927158 Title: Problem with python-trio with s3ql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1927158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922340] Re: GNOME lock screen wallpaper turns black on main display
Hi, this bug does still affect Ubuntu 21.10: ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 26 08:46:23 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-09-26 (121 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922340 Title: GNOME lock screen wallpaper turns black on main display To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938773] Re: [MIR] oem-sutton.simon-carlisle-meta
oem-sutton.simon-carlisle-meta 20.04~ubuntu1 has been put into https://launchpad.net/ubuntu/focal/+queue. ** Description changed: [Background] Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details. [Impact] - 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive. - 2. The background and impact of the situation for this change, and it's impact. + 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive. + 2. The background and impact of the situation for this change, and it's impact. [Testing] - 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware - 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the hardware - 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly. + 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware + 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the hardware + 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly. [Regression Potential] Most potential regressions will live in the package set that will be installed via dependency of this package, which live in OEM archive (outside of Ubuntu) and control by OEM team. OEM team and other corresponding team need take responsibility of those dependency installed. [When switching kernel flavour] Check that the new kernel flavour works on the target platform. [Availability] This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet. The source code of the oem-sutton.simon-carlisle-meta for focal: - git clone -b simon.carlisle-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta + git clone -b simon.carlisle-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-sutton-projects-meta [Rationale] We want to improve the hardware support for some Lenovo platforms. [Security] No CVE/known security issue. [Quality assurance] I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Lenovo platforms. oem-sutton.simon-carlisle-meta will be upgraded to 20.04ubuntu1 or the later version from OEM archive. [Dependencies] It only depends on ubuntu-oem-keyring. [Standards compliance] This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM. [Maintenance] Canonical OEM Enablement Team will take care of the maintenance. [Background information] Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details. Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to verify this MIR against the reference package in the archive. https://ubuntu.com/certified/202107-29263 - https://ubuntu.com/certified/202107-29264 ** Changed in: ubuntu Status: Confirmed => In Progress ** Tags removed: oem-needs-upload ** Tags added: oem-done-upload -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938773 Title: [MIR] oem-sutton.simon-carlisle-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1938773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959071] [NEW] nvidia-dkms-450 450.119.03-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-450 450.119.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-27-generic Date: Tue Jan 25 20:31:51 2022 DuplicateSignature: dkms:nvidia-dkms-450:450.119.03-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/450.119.03/build/nvidia-drm/nvidia-drm-crtc.c:234:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2020-12-04 (417 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 450.119.03-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-dkms-450 450.119.03-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959071 Title: nvidia-dkms-450 450.119.03-0ubuntu0.20.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1959071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959070] [NEW] NO standby or shutdown possible (5.13.0.27)
Public bug reported: I am using Xubuntu (actual LTS-version) with AMD-Ryzen with Kernel: 5.13.0.27 there is no regular powerdwn or Standby possible: The system does not switch off with: "tl@tl-as:~$ shutdown now -h" too; If I boot with the last version in the boot options (5.11.0.46) I can use Standby, Powerdown again normally Additional infos: Description:Ubuntu 20.04.3 LTS Release:20.04 -Systemstarts- Wed Jan 26 07:44: 5.13.0-27-generi Wed Jan 26 08:01: 5.11.0-46-generi Wed Jan 26 06:55: 5.13.0-27-generi Wed Jan 26 04:39: 5.13.0-27-generi Tue Jan 25 20:33: 5.13.0-27-generi Tue Jan 25 12:40: 5.13.0-27-generi Tue Jan 25 06:53: 5.13.0-27-generi Tue Jan 25 06:51: 5.13.0-27-generi Tue Jan 25 06:46: 5.13.0-27-generi Tue Jan 25 04:31: 5.13.0-27-generi Mon Jan 24 22:15: 5.13.0-27-generi Mon Jan 24 11:42: 5.13.0-27-generi Mon Jan 24 08:38: 5.13.0-27-generi Sun Jan 23 06:27: 5.11.0-46-generi Wed Jan 19 09:16: 5.11.0-46-generi Tue Jan 18 19:19: 5.11.0-46-generi ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959070 Title: NO standby or shutdown possible (5.13.0.27) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959064] Re: [SRU][F] Add mt8183 SCP firmware
https://lists.ubuntu.com/archives/kernel-team/2022-January/127425.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959064 Title: [SRU][F] Add mt8183 SCP firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1959064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959068] [NEW] old highscores are disregarded in ranking
Public bug reported: I have a highscore file that reaches several years back. When I choose a setup I haven't played recently, I notice that the old scores are shown but lower scores are sroted before them, so while they are displayed in the highscore list, they are treated as if the score was lower than displayed (possibly 0). I also have the impression that not all scores are displayed in the highscore list (because when playing I usually name the entry by the score number, e.g. when I managed to rank third, I would mostly call the entry "ke3" while when I reach a highscore I will enter KE in upper case and no number, and it is very unlikely I played one setup only a few times, so if a highscore table shows only some entries and even more so if they have numbers, it is likely that others are missing. The old highscore was shown as the current highscore during playing that game, and when playing again it was replaced by the lower new one. Package version: 2.5+dfsg1-1build1 Ubuntu version: 20.04.3 LTS I attach a sample screenshot of wrong sorting and my .bl2/hscore.dat file (after playing once more). ** Affects: blockout2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot showing a lower new score above a higher old one" https://bugs.launchpad.net/bugs/1959068/+attachment/5557481/+files/Screenshot%20from%202022-01-26%2007-44-06.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959068 Title: old highscores are disregarded in ranking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blockout2/+bug/1959068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959068] Re: old highscores are disregarded in ranking
** Attachment added: "sample .bl2/hscore.dat file with old and new entries" https://bugs.launchpad.net/ubuntu/+source/blockout2/+bug/1959068/+attachment/5557482/+files/hscore.dat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959068 Title: old highscores are disregarded in ranking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blockout2/+bug/1959068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937223] Re: [MIR] oem-somerville-kakuna-meta
There were no outputs by `ubuntu-drivers list-oem` before using focal-proposed. After using focal-proposed, `ubuntu-drivers list-oem` shows oem-somerville-kakuna-meta. When I executed `sudo ubuntu-drivers install`, it will install oem-somerville-kakuna-meta 20.04~ubuntu1 from focal-proposed/main, and then upgrade to oem-somerville-kakuna-meta 20.04ubuntu8 from "http://dell.archive.canonical.com focal/somerville-kakuna". After I reboot the system, the system boots by linux-image-5.10.0-1057-oem that meets our expectation. ** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937223 Title: [MIR] oem-somerville-kakuna-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920196] Re: [MIR] oem-somerville-pidgeot-meta
There were no outputs by `ubuntu-drivers list-oem` before using focal-proposed. After using focal-proposed, `ubuntu-drivers list-oem` shows oem-somerville-pidgeot-meta. When I executed `sudo ubuntu-drivers install`, it will install oem-somerville-pidgeot-meta 20.04~ubuntu1 from focal-proposed/main, and then upgrade to oem-somerville-pidgeot-meta 20.04ubuntu4 from "http://dell.archive.canonical.com focal/somerville-pidgeot". After I reboot the system, the system boots by linux-image-5.13.0-1029-oem that meets our expectation. ** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920196 Title: [MIR] oem-somerville-pidgeot-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
As a workaround I updated to Thunderbird Beta (v. 97.0b3) and it does not cause the alt-tab problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920195] Re: [MIR] oem-somerville-pidgeot-14-meta
There were no outputs by `ubuntu-drivers list-oem` before using focal-proposed. After using focal-proposed, `ubuntu-drivers list-oem` shows oem-somerville-pidgeot-14-meta. When I executed `sudo ubuntu-drivers install`, it will install oem-somerville-pidgeot-14-meta 20.04~ubuntu1 from focal-proposed/main, and then upgrade to oem-somerville-pidgeot-14-meta 20.04ubuntu3 from "http://dell.archive.canonical.com focal/somerville-pidgeot-14". After I reboot the system, the system boots by linux-image-5.13.0-1029-oem that meets our expectation. ** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920195 Title: [MIR] oem-somerville-pidgeot-14-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
Not fixed. Jammy w/ mutter 41.3. Alt-tab works on boot. Send e-mail with Thunderbird, alt-tab fails to work. ** Changed in: mutter (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959064] [NEW] [SRU][F] Add mt8183 SCP firmware
Public bug reported: [Impact] No driver is loaded for scp firmware on the mt8183 platform, and fw is missing too. [Fix] Add mt8183 SCP firmware [Test] Verified on the mt8183 platform, it can be loaded and powered up. [Where problems could occur] This firmware is specific for mt8183, it should be low risk. The firmware is already in impish and jammy, only SRU fw for focal. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Assignee: Hsuan-Yu Lin (shanelin) Status: In Progress ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => Hsuan-Yu Lin (shanelin) ** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959064 Title: [SRU][F] Add mt8183 SCP firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1959064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952365] Re: After suspend system GUI don't load
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952365 Title: After suspend system GUI don't load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1952365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959061] [NEW] The display output on type-c hub doesn't work on ADL platform
Public bug reported: [Impact] The display output(DP/HDMI) on the USB type-c hub doesn't work. No display output device could be found after the monitor is plugged into the hub. [Fix] Intel provide a new patch to fix this issue on ADL platforms. [Test] Verified on ADL platform with different type-c hubs, the display output works. [Where problems could occur] ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1946314 somerville ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: oem-priority originate-from-1946314 somerville ** Description changed: [Impact] + The display output(DP/HDMI) on the USB type-c hub doesn't work. No display output device could be found after the monitor is plugged into the hub. [Fix] + Intel provide a new patch to fix this issue on ADL platforms. [Test] + Verified on ADL platform with different type-c hubs, the display output works. [Where problems could occur] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959061 Title: The display output on type-c hub doesn't work on ADL platform To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1959061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959058] [NEW] Files missing in Ubuntu Ports repo
Public bug reported: After adding the Ubuntu Ports repo, apt update fails with the following error E: Failed to fetch http://ports.ubuntu.com/ubuntu- ports/dists/xenial/main/dep11/Components-amd64.yml 404 Not Found E: Failed to fetch http://ports.ubuntu.com/ubuntu- ports/dists/bionic/main/binary-amd64/Packages 404 Not Found E: Failed to fetch http://ports.ubuntu.com/ubuntu- ports/dists/focal/main/binary-amd64/Packages 404 Not Found E: Some index files failed to download. They have been ignored, or old ones used instead. These files are also not accessible from the web browser. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959058 Title: Files missing in Ubuntu Ports repo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1959058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958724] Re: System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic
Here is the danger of this bug on a laptop (as I've experienced): The system, from all appearances looks powered down (with the exception of the power indicator which remains lit on my laptop). Unfortunately, the power indicator is not in a conspicuous place which means that in order to *verify* the system is off, I have to lean over and look at the side of the laptop. When a user gets into the habit of a system just working, checking the power indicator slips the mind. Hence, a powered on laptop may be placed inside a tightly insulated laptop bag. When this happened to me, I didn't discover it for about 2 hours. When I went to take the laptop out of the bag, the fan was now running trying to keep the internals cool, but the bag was insulated (padded). This resulted in the system being so hot that I could not even touch the keyboard in places without getting mildly burned. I have no idea what will happen to a discharging lithium battery that is being heated rather than cooled in that situation, but I imagine there may be a component of definite risk to a system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958724 Title: System Shutdown and resume hangs since Kernel linux- image-5.13.0-23-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1017603] Re: perl needs to be multiarch
Here is a similar problem on 20.04 (Focal): https://forum.winehq.org/viewtopic.php?f=8=36119=135865#p135852 The following packages have unmet dependencies: perl-base : Conflicts: perl-base:i386 but 5.30.0-9ubuntu0.2 is to be installed perl-base:i386 : Conflicts: perl-base but 5.30.0-9ubuntu0.2 is installed snmp : Conflicts: snmp:i386 but 5.8+dfsg-2ubuntu2.3 is to be installed snmp:i386 : Conflicts: snmp but 5.8+dfsg-2ubuntu2.3 is installed perl : Conflicts: perl:i386 but 5.30.0-9ubuntu0.2 is to be installed perl:i386 : Conflicts: perl but 5.30.0-9ubuntu0.2 is installed vkd3d-compiler : Conflicts: vkd3d-compiler:i386 but 1.2~focal-1 is to be installed vkd3d-compiler:i386 : Conflicts: vkd3d-compiler but 1.2~focal-1 is to be installed Unable to resolve dependencies! Giving up... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1017603 Title: perl needs to be multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1017603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957765] Re: Jammy: Update to 5.1.21 needed for PHP 8.1 compatibility
Uploaded to -proposed php-apcu | 5.1.20+4.0.11-0+deb11u1ubuntu3 | jammy/universe php-apcu | 5.1.21+4.0.11-7ubuntu1 | jammy-proposed/universe ** Changed in: php-apcu (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957765 Title: Jammy: Update to 5.1.21 needed for PHP 8.1 compatibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-apcu/+bug/1957765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959019] Re: package gfortran 4:9.3.0-1ubuntu2 failed to install/upgrade: installed gfortran package post-installation script subprocess returned error exit status 2
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959019 Title: package gfortran 4:9.3.0-1ubuntu2 failed to install/upgrade: installed gfortran package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1959019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894795] Re: [MIR] oem-somerville-charmander-meta
There were no outputs by `ubuntu-drivers list-oem` before using focal-proposed. After using focal-proposed, `ubuntu-drivers list-oem` shows oem-somerville-charmander-meta. When I executed `sudo ubuntu-drivers install`, it will install oem-somerville-charmander-meta 20.04~ubuntu1 from focal-proposed/main, and then upgrade to oem-somerville-charmander-meta 20.04ubuntu10 from "http://dell.archive.canonical.com focal/somerville-charmander". After I reboot the system, the system boots by linux-image-5.13.0-1029-oem that meets our expectation. ** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894795 Title: [MIR] oem-somerville-charmander-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1894795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958951] Re: not updating
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958951 Title: not updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1958951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944113]
*** Bug 146942 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396367] Re: Kdeconnectd uses 100%
Operating System: Kubuntu 21.10 DE: KDE 5.86.0 / Plasma 5.22.5 see also bug/1922465 When a second user attempts to log out it appears to log out, but afterwards gradually the fans rise to full speed. If the first user (never logged out just locked) logs back in and runs sudo htop you can see 60ish pids running in the name of the second user, 6ish of those are using 100% of all cores. The pids that are hogging are xdg-desktop-portal-kde and at least one kdeconnectd, usually multiple threads of kdeconnectd. Each of the threads that those pids are in are end with a drconqi pid that, if you kill it, the entire thread closes and that core frees up. If all of the hogging threads are killed in that way that still leaves 50ish pids running in the name of the second user, but they use 0% CPU. I have been killing all of second users threads without noticing any repercussions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396367 Title: Kdeconnectd uses 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1396367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900197] Re: netcat fails with an error with -v
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: netcat-openbsd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900197 Title: netcat fails with an error with -v To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1900197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922465] Re: [Wayland] xdg-desktop-portal-kde hogs CPU after logout and login
When a second user attempts to log out it appears to log out, but afterwards gradually the fans rise to full speed. If the first user (never logged out just locked) logs back in and runs sudo htop you can see 60ish pids running in the name of the second user, 6ish of those are using 100% of all cores. The pids that are hogging are xdg-desktop-portal-kde and at least one kdeconnectd, usually multiple threads of kdeconnectd. Each of the threads that those pids are in are end with a drconqi pid that, if you kill it, the entire thread closes and that core frees up. If all of the hogging threads are killed in that way that still leaves 50ish pids running in the name of the second user, but they use 0% CPU. I have been killing all of second users threads without noticing any repercussions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922465 Title: [Wayland] xdg-desktop-portal-kde hogs CPU after logout and login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-kde/+bug/1922465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1374892] Re: Please backport php5-apcu version 4.0.6 to Ubuntu 14.04 LTS
** Changed in: php-apcu (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1374892 Title: Please backport php5-apcu version 4.0.6 to Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-apcu/+bug/1374892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959054] Re: debhelper restarts services marked --no-restart-on-upgrade
** Changed in: debhelper (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959054 Title: debhelper restarts services marked --no-restart-on-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1959054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session
FWIW I could reproduce the issue, as described in comment #16, on Debian testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599282] Re: Package recommends non-existent php-apcu-bc
Not sure of the situation in xenial but php-apcu-bc was available in focal and bionic, I believe. In jammy it's deprecated and no longer a Recommends for php-apcu. Eventually it'll be removed from the archive. ** Changed in: php-apcu (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599282 Title: Package recommends non-existent php-apcu-bc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-apcu/+bug/1599282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647725] Re: Please add php-apcu-bc to PHP 7.1
** Changed in: php-apcu (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647725 Title: Please add php-apcu-bc to PHP 7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-apcu/+bug/1647725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789454] Re: gsmartcontrol immediately crashes while running smartctl
Thanks for working on this, has this been fixed in releases later than Ubuntu 20.04? ** Changed in: gsmartcontrol (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789454 Title: gsmartcontrol immediately crashes while running smartctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsmartcontrol/+bug/1789454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924298] Re: accept returns duplicate endpoints under load
Not sure if this is useful, but running the test with WSL and Ubuntu 20.04.3 LTS 2 "console windows" running the wrk at the same time. This is how the server failed Listening on port pthread_create: Cannot allocate memory I realize this is WSL and not native Windows. We have spent about 90 minutes working on porting from the server.c to run on Windows natively and haven't succeeded yet. We are not c/c++ developers, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924298 Title: accept returns duplicate endpoints under load To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1924298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958872] Re: [needs-packaging] Sync uxplay 1.46-1 (universe) from Debian experimental (main)
*** This is an automated message *** This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs- packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist. ** Changed in: ubuntu Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958872 Title: [needs-packaging] Sync uxplay 1.46-1 (universe) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1958872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958690] Re: initramfs-tools/0.136ubuntu6.6 ADT test failure with linux/5.4.0-97.110 (No space left on device)
*** This bug is a duplicate of bug 1958904 *** https://bugs.launchpad.net/bugs/1958904 ** This bug has been marked a duplicate of bug 1958904 autopkgtest is failing on jammy with "no space left on device" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958690 Title: initramfs-tools/0.136ubuntu6.6 ADT test failure with linux/5.4.0-97.110 (No space left on device) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958904] Re: autopkgtest is failing on jammy with "no space left on device"
It looks like this also needs fixing in Focal see bug 1958690, which I've marked as a duplicate of this. ** Also affects: initramfs-tools (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Focal) Status: New => Triaged ** Changed in: initramfs-tools (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958904 Title: autopkgtest is failing on jammy with "no space left on device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959054] Re: debhelper restarts services marked --no-restart-on-upgrade
** Description changed: Debian bug #994204 (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that results in the postinst being generated in such a fashion that services marked - --no-restart-on-upgrade (now deprecated in favour of --no-stop-on- - upgrade) restart anyway. + --no-stop-on-upgrade (or its deprecated alias --no-restart-on-upgrade), + restart anyway. + + Please note: this is nothing to do with the --no-restart-after-upgrade + flag (which is, somewhat confusingly IMO, unrelated). I've confirmed that the flaw appears to be present in the jammy version of debhelper (though not impish) and that packages generated with it appear to contain the flawed postinst (I first encountered this whilst working on the open-iscsi merge), though I haven't yet managed to test that the flaw exhibits itself on upgrade (though I'd say from the presence of the flaw in the postinst, that it's a reasonable inference that it will). In dbus (the merge of which I'm currently working on), Debian has worked around this but given I've now run into two affected packages (open- iscsi and dbus), only one of which has a work-around, I'd much rather we got debhelper fixed up and rebuilt affected packages? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959054 Title: debhelper restarts services marked --no-restart-on-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1959054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943280] Re: OpenLDAP's ufw profile is redundant and can be removed
As it turns out, the situation is a bit more complex. Although ufw does provide the ufw-directoryserver profile, for some reason we don't install ufw profiles on Ubuntu: https://git.launchpad.net/ufw/tree/debian/rules?h=ubuntu/master#n90 I'm not sure why that is the case, and git-blame isn't very helpful to clarify the question. I will try to ask around and see if I can understand the rationale behind this decision. ** Changed in: openldap (Ubuntu) Importance: Medium => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943280 Title: OpenLDAP's ufw profile is redundant and can be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1943280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959054] [NEW] debhelper restarts services marked --no-restart-on-upgrade
Public bug reported: Debian bug #994204 (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that results in the postinst being generated in such a fashion that services marked --no-restart-on-upgrade (now deprecated in favour of --no-stop-on- upgrade) restart anyway. I've confirmed that the flaw appears to be present in the jammy version of debhelper (though not impish) and that packages generated with it appear to contain the flawed postinst (I first encountered this whilst working on the open-iscsi merge), though I haven't yet managed to test that the flaw exhibits itself on upgrade (though I'd say from the presence of the flaw in the postinst, that it's a reasonable inference that it will). In dbus (the merge of which I'm currently working on), Debian has worked around this but given I've now run into two affected packages (open- iscsi and dbus), only one of which has a work-around, I'd much rather we got debhelper fixed up and rebuilt affected packages? ** Affects: debhelper (Ubuntu) Importance: Undecided Status: New ** Affects: debhelper (Debian) Importance: Unknown Status: Unknown ** Tags: rls-jj-incoming ** Bug watch added: Debian Bug tracker #994204 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994204 ** Also affects: debhelper (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994204 Importance: Unknown Status: Unknown ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959054 Title: debhelper restarts services marked --no-restart-on-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1959054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957261] Re: PHP modules don't load
*** This bug is a duplicate of bug 1957765 *** https://bugs.launchpad.net/bugs/1957765 Ubuntu 22.04 will be using PHP 8.1, which is currently staging in jammy- proposed. ** This bug has been marked a duplicate of bug 1957765 Jammy: Update to 5.1.21 needed for PHP 8.1 compatibility -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957261 Title: PHP modules don't load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-apcu/+bug/1957261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957765] Re: Jammy: Update to 5.1.21 needed for PHP 8.1 compatibility
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: php-apcu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957765 Title: Jammy: Update to 5.1.21 needed for PHP 8.1 compatibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-apcu/+bug/1957765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958872] Re: [needs-packaging] Sync uxplay 1.46-1 (universe) from Debian experimental (main)
I synced this, but because it's a NEW package, it needs to be manually accepted by the Ubuntu Archive team. This may take a few days. https://launchpad.net/ubuntu/jammy/+queue ** Changed in: ubuntu Importance: Wishlist => Undecided ** Changed in: ubuntu Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958872 Title: [needs-packaging] Sync uxplay 1.46-1 (universe) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1958872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955556] Re: Javascript libraries with vulnerabilities
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/196 Title: Javascript libraries with vulnerabilities To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958393] Re: crmsh orderedset.py does not support python 3.10
** Merge proposal linked: https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/crmsh/+git/crmsh/+merge/414581 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958393 Title: crmsh orderedset.py does not support python 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1958393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938964] Re: icmp_redirect from selftests fails on F/kvm (unary operator expected)
Verified "unary operator expected" error is not showing on any kvm selftests results for the kernels in -proposed. Thank you! ** Tags removed: verification-needed-focal verification-needed-hirsute verification-needed-impish ** Tags added: verification-done-focal verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938964 Title: icmp_redirect from selftests fails on F/kvm (unary operator expected) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1938964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959047] [NEW] systemd ignores RootDirectory option in .service units
Public bug reported: The version of systemd (249.5-2ubuntu4) currently packaged for the Ubuntu development version (22.04 Jammy Jellyfish) totally ignores the RootDirectory= option in systemd service files. With RootDirectory, systemd should start the service after calling chroot() on the supplied directory. To test/reproduce, create a test service file with the following contents: # /etc/systemd/system/lsb-release.service [Unit] Description=LSB Release Information [Service] Type=simple RootDirectory=/var/chroot/trusty ExecStartPre=/bin/pwd ExecStart=/usr/bin/lsb_release -a You should have a chroot environment in the specified RootDirectory, even though you can still deduce if systemd attempted to chroot or not from the resulting error message. In my example, I installed an end-of-life Ubuntu 14.04 Trusty Tahr in the chroot environment. On systems NOT affected by the problem, I get the following result when I start this test service. This is what I'd expect. Jan 25 20:40:40 dolly systemd[1]: Starting LSB Release Information... Jan 25 20:40:40 dolly pwd[361]: / Jan 25 20:40:40 dolly systemd[1]: Started LSB Release Information. Jan 25 20:40:40 dolly lsb_release[362]: No LSB modules are available. Jan 25 20:40:40 dolly lsb_release[362]: Distributor ID:Ubuntu Jan 25 20:40:40 dolly lsb_release[362]: Description:Ubuntu 14.04 LTS Jan 25 20:40:40 dolly lsb_release[362]: Release:14.04 Jan 25 20:40:40 dolly lsb_release[362]: Codename:trusty Jan 25 20:40:40 dolly systemd[1]: lsb-release.service: Succeeded. On the problematic system, however, I get the following result. Jan 25 21:21:08 savelog systemd[1]: Starting LSB Release Information... Jan 25 21:21:08 savelog systemd[1]: Started LSB Release Information. Jan 25 21:21:08 savelog pwd[81114]: / Jan 25 21:21:08 savelog lsb_release[81115]: No LSB modules are available. Jan 25 21:21:08 savelog lsb_release[81115]: Distributor ID:Ubuntu Jan 25 21:21:08 savelog lsb_release[81115]: Description:Ubuntu Jammy Jellyfish (development branch) Jan 25 21:21:08 savelog lsb_release[81115]: Release:22.04 Jan 25 21:21:08 savelog lsb_release[81115]: Codename:jammy Jan 25 21:21:08 savelog systemd[1]: lsb-release.service: Deactivated successfully. It totally run the service on the host's root filesystem, it didn't care even the slightest that a RootDirectory is specified. Tested on the following releases / systemd versions: Ubuntu 18.04.6 Bionic Beaver – ISSUE NOT PRESENT systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid Ubuntu 20.04.3 Focal Fossa – ISSUE NOT PRESENT systemd 245 (245.4-4ubuntu3.15) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid Ubuntu 21.10 Impish Indri – ISSUE NOT PRESENT systemd 248 (248.3-1ubuntu8.2) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified Ubuntu 22.04 Jammy Jellyfish (development branch) – ISSUE PRESENT systemd 249 (249.5-2ubuntu4) +PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified Note that the problem is produced under an LXC container; since systemd detects virtualization, it might change how it behaves. It's either a bug or an intentional change I don't understand yet (i.e. the RootDirectory option has deprecated and is about to be replaced with something else, or there are additional conditions to be met before RootDirectory is considered), but I think in the latter case I should at least get a warning that there is a change in configuration. I imagine suddenly everyone's existing service units utilizing RootDirectory silently stop working without any information regarding why. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959047 Title: systemd ignores RootDirectory option in .service units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956213] Re: Lan6_Conf section is unknown to freeipmi
I reported upstream but after a diff from patch used in ubuntu 18.04 upstream have additional changes so before enable by default upstream more testing is needed, also a stable proposed update for ubuntu 20.04 is excluded for the users that are using/will use latest version with lan6_conf section enabled, after testing it (not simple check that is present like the output in previous msg) please report if is working or there is bugs here: https://github.com/chu11/freeipmi-mirror/issues/53 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956213 Title: Lan6_Conf section is unknown to freeipmi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1956213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956213] Re: Lan6_Conf section is unknown to freeipmi
I reported upstream but after a diff from patch used in ubuntu 18.04 upstream have additional changes so before enable by default upstream more testing is needed, also a stable proposed update for ubuntu 20.04 is excluded for the users that are using/will use latest version with lan6_conf section enabled, after testing it (not simple check that is present like the output in previous msg) please report if is working or there is bugs here: https://github.com/chu11/freeipmi-mirror/issues/53 ** Bug watch added: github.com/chu11/freeipmi-mirror/issues #53 https://github.com/chu11/freeipmi-mirror/issues/53 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956213 Title: Lan6_Conf section is unknown to freeipmi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1956213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959046] [NEW] system crashes a lot and faces problems of unetermined kind
Public bug reported: system crashes at frequent intervals and faces problems of undetermined kind. alongside, the Firefox also crashes a lot and exits abruptly. forced to do a clean install, because system becomes unusable after a few days. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity 21.10.10 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 26 02:00:34 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubiquity-21.10.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959046 Title: system crashes a lot and faces problems of unetermined kind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1959046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820586] Re: Should document keys are not trusted by default
This bug was fixed in the package debian-archive-keyring - 2021.1.1ubuntu2 --- debian-archive-keyring (2021.1.1ubuntu2) jammy; urgency=medium * Document the fact that the keys are disabled in APT for Ubuntu (LP: #1820586) -- Simon Chopin Tue, 25 Jan 2022 18:51:18 +0100 ** Changed in: debian-archive-keyring (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820586 Title: Should document keys are not trusted by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-archive-keyring/+bug/1820586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work
** Changed in: initramfs-tools (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958594 Title: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
Thanks, booting into a different kernel version worked. I installed 5.11.0-46 like you said, but then when I went into advanced options in my boot menu there were three versions listed, so maybe I didn't have to do that. I also didn't bother changing my grub default. I'll just choose my kernel manually every time I restart, and when it's time to go back to normal I just have to stop doing that. Thank you for the advice! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959023] Re: upgrade 16 to 18 fails
** Tags added: xenial2bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959023 Title: upgrade 16 to 18 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1959023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work
Accidentally changed the status... sorry about that. Can anyone please remove the "Fix Released" status? Not sure how to do that... ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958594 Title: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953673] Re: Please update gce-compute-image-packages to 20211028.00
As Hirsute has been EOL'd, marking this bug with the same. ** Changed in: gce-compute-image-packages (Ubuntu Hirsute) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953673 Title: Please update gce-compute-image-packages to 20211028.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1953673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955137] Re: [SRU] 2.54
Hi, these test failures are not issues in snapd, those are related to the tests, I'll work on adapting those tests to make then work for SRU validation. When we run tests for sru validation, reexec is disabled and the snapd deb package is not generated as usual, this is making some tests fail in this case. Thanks for the review. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-hirsute verification-needed-impish ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955137 Title: [SRU] 2.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1955137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
There may be better ways to downgrade the kernel(?), but what I've done is re-install the previous 5.11 kernel: sudo apt install linux-image-5.11.0-46-generic linux- headers-5.11.0-46-generic linux-modules-extra-5.11.0-46-generic Then edit /etc/default/grub to change the GRUB_DEFAULT line to select this kernel by default: GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 5.11.0-46-generic" and then run `sudo update-grub` and reboot. Now `uname -r` shows 5.11.0-46-generic. This will lock you on that kernel forever (no security patches!). You should watch these launchpad bugs for changes to know when to undo it. Undo the change by returning /etc/default/grub to having `GRUB_DEFAULT=0` and re-running `sudo update-grub`. Once everything is back to normal you can then `apt purge` the packages above installed with `apt install`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948714] Re: After reboot, the password set at install time doesn't work.
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948714 Title: After reboot, the password set at install time doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1948714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958312] Re: Livepatch not working on Ubuntu 22.04 LTS
Do you have the canonical-livepatch snap installed? ** Changed in: software-properties (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958312 Title: Livepatch not working on Ubuntu 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1958312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work
** Changed in: initramfs-tools (Ubuntu) Milestone: None => ubuntu-22.02 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958594 Title: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958594 Title: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958007] Re: Regression in 5.13.0-23: laptop cannot suspend or turn off
Interesting, I have the "same" problem on Jammy Jellyfish (22.04). https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041 My suspend is also not working, freezes at the same state. Mainline kernel works. Also a Lenovo Device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958007 Title: Regression in 5.13.0-23: laptop cannot suspend or turn off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953599] Please test proposed package
Hello James, or anyone else affected, Accepted ceph into wallaby-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:wallaby-proposed sudo apt-get update 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, and change the tag from verification-wallaby-needed to verification-wallaby-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-wallaby-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953599 Title: [SRU] ceph 16.2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1953599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958774] Re: Blackscreen after suspending and closing LID
maybe this website will help you to debug your problem: https://01.org/blogs/rzhang/2015/best-practice-debug-linux- suspend/hibernate-issues -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958774 Title: Blackscreen after suspending and closing LID To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958968] Re: failed to resume PC
Maybe this website will help you to debug your issue https://01.org/blogs/rzhang/2015/best-practice-debug-linux- suspend/hibernate-issues -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958968 Title: failed to resume PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend
** Description changed: Hi, - I want to report, that your delivered kernel has problem with STR on my Laptop. - When I run `echo mem | sudo tee /sys/power/state` the systems trys to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". + I want to report, that Ubuntu's shipped kernel has a problem with STR on my Laptop. + When I run `echo mem | sudo tee /sys/power/state` the systems try to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". So the final step is missing and the machine can only be forced to poweroff and on again. I already tested with the mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ And there standby works flawless. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: thomas 1409 F pipewire-media- - thomas 1410 F pulseaudio - /dev/snd/seq:thomas 1408 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC0: thomas 1409 F pipewire-media- + thomas 1410 F pulseaudio + /dev/snd/seq:thomas 1408 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jan 25 20:06:44 2022 InstallationDate: Installed on 2022-01-21 (4 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) MachineType: LENOVO 20ELS03U00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug no_console_suspend ignore_loglevel RelatedPackageVersions: - linux-restricted-modules-5.15.0-17-generic N/A - linux-backports-modules-5.15.0-17-generic N/A - linux-firmware 1.204 + linux-restricted-modules-5.15.0-17-generic N/A + linux-backports-modules-5.15.0-17-generic N/A + linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20ELS03U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20ELS03U00 dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959041 Title: STR (suspend-to-RAM) freezes at suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953673] Re: Please update gce-compute-image-packages to 20211028.00
This bug was fixed in the package gce-compute-image-packages - 20211028.00-0ubuntu1~21.10.0 --- gce-compute-image-packages (20211028.00-0ubuntu1~21.10.0) impish; urgency=medium * No-change rebuild for Impish. (LP: #1953673) -- Utkarsh Gupta Wed, 08 Dec 2021 23:42:49 +0530 ** Changed in: gce-compute-image-packages (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953673 Title: Please update gce-compute-image-packages to 20211028.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1953673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959041] [NEW] STR (suspend-to-RAM) freezes at suspend
Public bug reported: Hi, I want to report, that your delivered kernel has problem with STR on my Laptop. When I run `echo mem | sudo tee /sys/power/state` the systems trys to go in standby mode. Everything shuts down, but the power led flashes fast (how it does every time between going into standby and before the standby is reached). It never reaches the state that the led starts slowly "breathing in and out". I already tested with the mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/ And there standby works flawless. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 1409 F pipewire-media- thomas 1410 F pulseaudio /dev/snd/seq:thomas 1408 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue Jan 25 20:06:44 2022 InstallationDate: Installed on 2022-01-21 (4 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220121) MachineType: LENOVO 20ELS03U00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug no_console_suspend ignore_loglevel RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20ELS03U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20ELS03U00 dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959041 Title: STR (suspend-to-RAM) freezes at suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
I'm thinking of trying to roll back my software so that I can continue using my computer until this is fixed. Can anyone recommend which package I should try rolling back, or how I should go about this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953673] Re: Please update gce-compute-image-packages to 20211028.00
This bug was fixed in the package gce-compute-image-packages - 20211028.00-0ubuntu1~18.04.0 --- gce-compute-image-packages (20211028.00-0ubuntu1~18.04.0) bionic; urgency=medium * No-change rebuild for Bionic. (LP: #1953673) -- Utkarsh Gupta Wed, 08 Dec 2021 23:39:33 +0530 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953673 Title: Please update gce-compute-image-packages to 20211028.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1953673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953673] Re: Please update gce-compute-image-packages to 20211028.00
This bug was fixed in the package gce-compute-image-packages - 20211028.00-0ubuntu1~20.04.0 --- gce-compute-image-packages (20211028.00-0ubuntu1~20.04.0) focal; urgency=medium * No-change rebuild for Focal. (LP: #1953673) -- Utkarsh Gupta Wed, 08 Dec 2021 23:32:46 +0530 ** Changed in: gce-compute-image-packages (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: gce-compute-image-packages (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953673 Title: Please update gce-compute-image-packages to 20211028.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1953673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953673] Update Released
The verification of the Stable Release Update for gce-compute-image- packages has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953673 Title: Please update gce-compute-image-packages to 20211028.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1953673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959038] Re: VirtualBox fails to boot FreeBSD 13.0 install ISO in EFI mode
** Changed in: virtualbox (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959038 Title: VirtualBox fails to boot FreeBSD 13.0 install ISO in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1959038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957123] Re: livecd-rootfs incorrectly installs core snap as implicit dep of other base snaps
The daily images for focal use livecd-rootfs from -proposed by default when building, and they have built successfully. Today's Ubuntu focal daily-live image no longer has the core snap included. All flavors have successful builds within the past 2 days. Verified. ** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957123 Title: livecd-rootfs incorrectly installs core snap as implicit dep of other base snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1957123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953673] Re: Please update gce-compute-image-packages to 20211028.00
## Conclusion Due to the completion of Google's testing and my own verification, I am marking verification-complete for all releases. ## Notes Testing of the new Google guest agents was primarily performed by Google themselves. They have given the +1. In addition, these images have gone through testing from the Canonical Public Cloud team. From my own testing images were produced with the guest agents directly from proposed and uploaded to GCE. These are the same images that Google used in their own testing. I verified: 1) The versions of packages 3) that my account and other project accounts were created 4) correct SSH keys were imported 5) the new packages provided parity with the existing agents. Verified with the following package versions: Bionic: google-compute-engine 20211028.00-0ubuntu1~18.04.0 Focal: google-compute-engine 20211028.00-0ubuntu1~20.04.0 Hirsute: google-compute-engine 20211028.00-0ubuntu1~21.04.0 Impish: google-compute-engine 20211028.00-0ubuntu1~21.10.0 ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-hirsute verification-needed-impish ** Tags added: verification-done-bionic verification-done-focal verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953673 Title: Please update gce-compute-image-packages to 20211028.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1953673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959038] Re: VirtualBox fails to boot FreeBSD 13.0 install ISO in EFI mode
VirtualBox bug ticket: https://www.virtualbox.org/ticket/19910 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959038 Title: VirtualBox fails to boot FreeBSD 13.0 install ISO in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1959038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959038] [NEW] VirtualBox fails to boot FreeBSD 13.0 install ISO in EFI mode
Public bug reported: VirtualBox 6.1.26, provided with up-to-date Ubuntu 20.04, fails to boot FreeBSD 13.0 install ISO in EFI mode. However, it worked with 6.1.10 some time ago (Ubuntu 20.04 version), i.e. it was possible to boot the ISO in EFI mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virtualbox 6.1.26-dfsg-3~ubuntu1.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-lowlatency 5.13.19 Uname: Linux 5.13.0-27-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 25 19:39:28 2022 InstallationDate: Installed on 2020-07-16 (558 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) VirtualBox.DpkgList: ii linux-headers-5.13.0-27-lowlatency5.13.0-27.29~20.04.1 amd64Linux kernel headers for version 5.13.0 on 64 bit x86 SMP ii linux-headers-lowlatency-hwe-20.045.13.0.27.29~20.04.13 amd64lowlatency Linux kernel headers ii virtualbox 6.1.26-dfsg-3~ubuntu1.20.04.2 amd64x86 virtualization solution - base binaries ii virtualbox-dkms 6.1.26-dfsg-3~ubuntu1.20.04.2 amd64x86 virtualization solution - kernel module sources for dkms ii virtualbox-qt 6.1.26-dfsg-3~ubuntu1.20.04.2 amd64x86 virtualization solution - Qt based user interface ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Affects: virtualbox (Debian) Importance: Unknown Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Bug watch added: Virtualbox Trac #19910 http://www.virtualbox.org/ticket/19910 ** Also affects: virtualbox (Debian) via http://www.virtualbox.org/ticket/19910 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959038 Title: VirtualBox fails to boot FreeBSD 13.0 install ISO in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1959038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958412] Re: [amdgpu] Flickering/noise on screen started in kernel 5.13
In my case the problem is severe. I can see login screen, but when I log in I see a white noise screen. It renders my computer unusable. That is unless I use older kernel. There is how to do it: When your computer boots press escape (UEFI boot) or shift (BIOS boot). You may have to try several times to press it in right time. A menu should appear. Choose option 'Advanced options for Ubuntu'. Then choose 'Ubuntu, with Linux 5.11.0-46-generic'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958412 Title: [amdgpu] Flickering/noise on screen started in kernel 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958959] Re: pahole v1.22-2 segfaults when building a Linux kernel
Hello Alexandre, please try again with dwarves 1.22-2build1 and libbpf 0.5.0-1 If this doesn't fix the issue, I'll just upload without that patch and use the embedded libbpf version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958959 Title: pahole v1.22-2 segfaults when building a Linux kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwarves/+bug/1958959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959002] Re: Blacklist and remove lintian-brush from the archive
$ reverse-depends src:lintian-brush Reverse-Recommends * silver-platter(for lintian-brush) Reverse-Depends * routine-update(for lintian-brush) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x vorlon@homer:~/devel/canonical/sync-blacklist$ reverse-depends src:lintian-brush -a source Reverse-Testsuite-Triggers * silver-platter(for lintian-brush) Reverse-Build-Depends * silver-platter(for lintian-brush) $ What do you want done with the affected reverse-dependencies? ** Changed in: lintian-brush (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959002 Title: Blacklist and remove lintian-brush from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lintian-brush/+bug/1959002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken
Hello Sebastian, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/70~ubuntu3.21.10.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- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947445 Title: Click actions "previews" and "minimize-or-previews" are broken To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1947445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874578] Re: Dock has very long load time when show-mounts is enabled
Hello Xanthopoulos, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/70~ubuntu3.21.10.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- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874578 Title: Dock has very long load time when show-mounts is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1874578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949352] Re: Removable drives are not auto-mounted after screen lock/unlock
Hello István, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/70~ubuntu3.21.10.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- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949352 Title: Removable drives are not auto-mounted after screen lock/unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1949352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949572] Re: Shell freeze after right click on the app in the dock
Hello giorgi, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/70~ubuntu3.21.10.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- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949572 Title: Shell freeze after right click on the app in the dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1949572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951599] Re: gnome-shell logs errors when ejecting SD card
Hello Bin, or anyone else affected, Accepted gnome-shell-extension-ubuntu-dock into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/70~ubuntu3.21.10.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- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: gnome-shell-extension-ubuntu-dock (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951599 Title: gnome-shell logs errors when ejecting SD card To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1951599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959033] [NEW] Bionic update: upstream stable patchset 2022-01-25
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-01-25 Ported from the following upstream stable releases: v4.14.260, v4.19.223 from git://git.kernel.org/ IB/qib: Use struct_size() helper IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields net: usb: lan78xx: add Allied Telesis AT29M2-AF can: kvaser_usb: get CAN clock frequency from device HID: holtek: fix mouse probing spi: change clk_disable_unprepare to clk_unprepare IB/qib: Fix memory leak in qib_user_sdma_queue_pkts() netfilter: fix regression in looped (broad|multi)cast's MAC handling qlcnic: potential dereference null pointer of rx_queue->page_ring net: accept UFOv6 packages in virtio_net_hdr_to_skb net: skip virtio_net_hdr_set_proto if protocol already set bonding: fix ad_actor_system option setting to default fjes: Check for error irq drivers: net: smc911x: Check for error irq sfc: falcon: Check null pointer of rx_queue->page_ring hwmon: (lm90) Fix usage of CONFIG2 register in detect function ALSA: jack: Check the return value of kstrdup() ALSA: drivers: opl3: Fix incorrect use of vp->state Input: atmel_mxt_ts - fix double free in mxt_read_info_block x86/pkey: Fix undefined behaviour with PKRU_WD_BIT pinctrl: stm32: consider the GPIO offset to expose all the GPIO lines ARM: 9169/1: entry: fix Thumb2 bug in iWMMXt exception handling f2fs: fix to do sanity check on last xattr entry in __f2fs_setxattr() usb: gadget: u_ether: fix race in setting MAC address in setup phase KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state hwmon: (lm90) Do not report 'busy' status bit as alarm ax25: NPD bug when detaching AX25 device hamradio: defer ax25 kfree after unregister_netdev hamradio: improve the incomplete fix to avoid NPD phonet/pep: refuse to enable an unbound pipe parisc: Correct completer in lws start UBUNTU: upstream stable to v4.14.260, v4.19.223 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2022-01-25 + from git://git.kernel.org/ -upstream stable patchset 2022-01-25 -from git://git.kernel.org/ + IB/qib: Use struct_size() helper + IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields + net: usb: lan78xx: add Allied Telesis AT29M2-AF + can: kvaser_usb: get CAN clock frequency from device + HID: holtek: fix mouse probing + spi: change clk_disable_unprepare to clk_unprepare + IB/qib: Fix memory leak in qib_user_sdma_queue_pkts() + netfilter: fix regression in looped (broad|multi)cast's MAC handling + qlcnic: potential dereference null pointer of rx_queue->page_ring + net: accept UFOv6 packages in virtio_net_hdr_to_skb + net: skip virtio_net_hdr_set_proto if protocol already set + bonding: fix ad_actor_system option setting to default + fjes: Check for error irq + drivers: net: smc911x: Check for error irq + sfc: falcon: Check null pointer of rx_queue->page_ring + hwmon: (lm90) Fix usage of CONFIG2 register in detect function + ALSA: jack: Check the return value of kstrdup() + ALSA: drivers: opl3: Fix incorrect use of vp->state + Input: atmel_mxt_ts - fix double free in mxt_read_info_block + x86/pkey: Fix undefined
[Bug 1959034] [NEW] nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: Won't load newest kernel, have to boot via advancedthen this error is received. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-27-generic Date: Mon Jan 24 09:47:23 2022 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-02-14 (345 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959034 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1959034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959030] Re: [SOF - sof-bytcht rt5651, playback] No sound at all
When booting into 5.11.0-46-generic #51~20.04.1-Ubuntu SMP Fri Jan 7 06:51:40 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Sound still working ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959030 Title: [SOF - sof-bytcht rt5651, playback] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1959030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955137] Re: [SRU] 2.54
I've set the tags back to verification-needed to prevent the accidental release of this while we wait for some details about the testing results. ** Tags removed: verification-done verification-done-bionic verification-done-focal verification-done-hirsute verification-done-impish ** Tags added: verification-needed verification-needed-bionic verification-needed-focal verification-needed-hirsute verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955137 Title: [SRU] 2.54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1955137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959030] [NEW] [SOF - sof-bytcht rt5651, playback] No sound at all
Public bug reported: After last update sound stopped to work ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ttrolka1260 F pulseaudio /dev/snd/pcmC1D0p: ttrolka1260 F...m pulseaudio /dev/snd/controlC0: ttrolka1260 F pulseaudio /dev/snd/timer: ttrolka1260 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 25 20:29:29 2022 InstallationDate: Installed on 2021-09-04 (143 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:rt5651 failed Symptom_Card: Built-in Audio - sof-bytcht rt5651 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ttrolka1260 F pulseaudio /dev/snd/pcmC1D0p: ttrolka1260 F...m pulseaudio /dev/snd/controlC0: ttrolka1260 F pulseaudio /dev/snd/timer: ttrolka1260 f pulseaudio Symptom_Type: No sound at all Title: [SOF - sof-bytcht rt5651, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Digma12x.WJ3142.NFNKRCN01 dmi.board.asset.tag: Default string dmi.board.name: CITI E401 ET4007EW dmi.board.vendor: Digma dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrDigma12x.WJ3142.NFNKRCN01:bd07/03/2018:br5.11:svnDigma:pnCITIE401ET4007EW:pvrDefaultstring:rvnDigma:rnCITIE401ET4007EW:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:sku1806078: dmi.product.family: CHT dmi.product.name: CITI E401 ET4007EW dmi.product.sku: 1806078 dmi.product.version: Default string dmi.sys.vendor: Digma ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal kernel-sound ** Tags removed: wayland-session ** Tags added: kernel-sound -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959030 Title: [SOF - sof-bytcht rt5651, playback] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1959030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958120] Re: Kubuntu Jammy ISO doesn't start welcome screen
** Changed in: ubiquity (Ubuntu Jammy) Status: New => In Progress ** Changed in: ubiquity (Ubuntu Jammy) Importance: Undecided => High ** Changed in: ubiquity (Ubuntu Jammy) Milestone: None => ubuntu-22.02 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958120 Title: Kubuntu Jammy ISO doesn't start welcome screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1958120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959021] Re: botan ecdsa test failures on ppc64el with openssl 3
** Tags added: transition-openssl3-jj -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959021 Title: botan ecdsa test failures on ppc64el with openssl 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/botan/+bug/1959021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958724] Re: System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic
I can confirm that it works until 5.13.22 and from 5.13.23 onward shutting down does not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958724 Title: System Shutdown and resume hangs since Kernel linux- image-5.13.0-23-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959027] Re: Various UI and theming issues in Firefox snap when running in Plasma Wayland session
** Attachment added: "Second screenshot: GTK File dialog with distorted fonts" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1959027/+attachment/5557396/+files/Screenshot_20220125_165558.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959027 Title: Various UI and theming issues in Firefox snap when running in Plasma Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1959027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959027] [NEW] Various UI and theming issues in Firefox snap when running in Plasma Wayland session
Public bug reported: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Wrong theme, UI font too big" https://bugs.launchpad.net/bugs/1959027/+attachment/5557383/+files/Screenshot_20220125_165617.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959027 Title: Various UI and theming issues in Firefox snap when running in Plasma Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1959027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950633] Re: [SRU] Update wifi firmware for future zero 2 boards
** Description changed: + [Impact] + + Future Pi Zero 2 boards will have a slightly different wifi chip on + board which requires a variant of the current firmware. This is being + added to the rename of linux-firmware-raspi2 (to linux-firmware-raspi) + for jammy, but requires adding to the existing linux-firmware-raspi2 + package for focal and impish, otherwise users on newer variants of the + Pi Zero 2 will find themselves without any wifi connectivity (or, in + fact, any connectivity given there is no ethernet on these boards). + + [Test Plan] + + Boards with the new wifi chip are not yet available, so the following + test plan is the best we can do: + + * Flash a fresh SD card with the appropriate server image + * Boot the card on the Pi under test with *no* ethernet attached (if the board supports it) + * Edit /etc/netplan/50-cloud-init.yaml to include an appropriate wifi configuration for your local AP + * sudo netplan apply + * ip addr # verify wlan0 is up and has a valid address + * sudo add-apt-repository ppa:waveform/firmware + * sudo apt install linux-firmware-raspi2 + * sudo reboot + * ip addr # verify wlan0 is up and has a valid address + + This should be performed on all supported boards with wifi (3B, 3A+, + 3B+, 4B, 400) on both supported architectures (armhf, and arm64). + + [Regression Potential] + + As we're updating the wifi firmware, the obvious possible regression is + failure of the wifi interface (hence the testing of all supported boards + in the plan). + + [Original Description] + In the upstream wifi firmware package (version 1:20210315-3+rpt3 of the firmware-nonfree package), the following is noted in the changelog: "Future Zero 2 W boards will have an alternative version of 43436 that should have different firmware, named brcmfmac43436s-sdio". We need to incorporate these blobs to support future variants of this board. ** Changed in: linux-firmware-raspi2 (Ubuntu Jammy) Milestone: None => ubuntu-22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950633 Title: [SRU] Update wifi firmware for future zero 2 boards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1950633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959023] [NEW] upgrade 16 to 18 fails
Public bug reported: The upgrade fails. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.32 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 CrashDB: ubuntu Date: Tue Jan 25 17:34:09 2022 InstallationDate: Installed on 2011-10-16 (3753 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2022-01-25 (0 days ago) VarLogDistupgradeAptlog: Log time: 2022-01-25 17:33:00.950015 Log time: 2022-01-25 17:33:08.545097 Log time: 2022-01-25 17:34:09.400948 Log time: 2022-01-25 17:34:13.452484 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959023 Title: upgrade 16 to 18 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1959023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950633] Re: Update wifi firmware for future zero 2 boards
** Changed in: linux-firmware-raspi2 (Ubuntu Focal) Milestone: None => ubuntu-20.04.4 ** Changed in: linux-firmware-raspi2 (Ubuntu Focal) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: linux-firmware-raspi2 (Ubuntu Impish) Assignee: (unassigned) => Dave Jones (waveform) ** Summary changed: - Update wifi firmware for future zero 2 boards + [SRU] Update wifi firmware for future zero 2 boards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950633 Title: [SRU] Update wifi firmware for future zero 2 boards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1950633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958563] Re: [SRU] Wrong permissions on vcio
** Description changed: [Impact] The incorrect permissions on these devices mean the regular console user cannot access various videocore services. An example of a side-effect of this is that camera usage (via the new libcamera mechanism) requires root access. Likewise, usage of the GPU (under the KMS system) for H.264 decoding (via v4l2m2m) likewise requires root access. [Test Plan] * Flash the appropriate version to a fresh SD card and boot it + * sudo apt install libraspberrypi0 # because it's not seeded on focal (this can be skipped on impish) + * sudo reboot * ls -l /dev/vc* /dev/dma_heap/ * Note that /dev/vcio, /dev/vcsm-cma, /dev/vchiq, /dev/dma_heap/* have incorrect permissions (specifically, their ownership is not root:video and/or their mode is not 0664) * sudo reboot * sudo add-apt-repository ppa:waveform/userland * sudo apt install libraspberrypi0 * sudo reboot * ls -l /dev/vc* /dev/dma_heap/ * Note that /dev/vcio, /dev/vcsm-cma, /dev/vchiq, /dev/dma_heap/* now have correct permissions (root:video ownership, and mode 0664) [Regression Potential] Only the permission changes are being backported, not a fully updated userland. Nonetheless, existing functionality from userland should be re-tested, in particular the legacy camera stack, with the following procedure: * Attach a raspberry pi camera module to the board * Add "start_x=1" and "gpu_mem=128" to /boot/firmware/config.txt * sudo reboot * raspistill -o test.jpg * Confirm that test.jpg contains a valid picture The "tvservice" binary *may* be tested too, but is known to be inoperable under the arm64 architecture (see LP: #1944541). It is also worth noting that the test plan above only looks at the permissions as libcamera is not *currently* expected to operate on Focal. Tests should be carried out on all supported boards (Zero 2, 2B, 3B, 3A+, 3B+, 4B) under both armhf and arm64 architectures (within the caveats noted above about the arm64 architecture). [Original Description] The /dev/vcio can have the wrong permissions due to a change in the kernel. As reported in https://github.com/raspberrypi/linux/pull/4624 (which I missed entirely, sorry pelwell!) we'll need a change in the udev rules to ensure the correct permissions are set. ** Description changed: [Impact] The incorrect permissions on these devices mean the regular console user cannot access various videocore services. An example of a side-effect of this is that camera usage (via the new libcamera mechanism) requires root access. Likewise, usage of the GPU (under the KMS system) for H.264 decoding (via v4l2m2m) likewise requires root access. [Test Plan] * Flash the appropriate version to a fresh SD card and boot it - * sudo apt install libraspberrypi0 # because it's not seeded on focal (this can be skipped on impish) + * sudo apt install libraspberrypi-bin # because it's not seeded on focal (this can be skipped on impish) * sudo reboot * ls -l /dev/vc* /dev/dma_heap/ * Note that /dev/vcio, /dev/vcsm-cma, /dev/vchiq, /dev/dma_heap/* have incorrect permissions (specifically, their ownership is not root:video and/or their mode is not 0664) * sudo reboot * sudo add-apt-repository ppa:waveform/userland - * sudo apt install libraspberrypi0 + * sudo apt install libraspberrypi-bin * sudo reboot * ls -l /dev/vc* /dev/dma_heap/ * Note that /dev/vcio, /dev/vcsm-cma, /dev/vchiq, /dev/dma_heap/* now have correct permissions (root:video ownership, and mode 0664) [Regression Potential] Only the permission changes are being backported, not a fully updated userland. Nonetheless, existing functionality from userland should be re-tested, in particular the legacy camera stack, with the following procedure: * Attach a raspberry pi camera module to the board * Add "start_x=1" and "gpu_mem=128" to /boot/firmware/config.txt * sudo reboot * raspistill -o test.jpg * Confirm that test.jpg contains a valid picture The "tvservice" binary *may* be tested too, but is known to be inoperable under the arm64 architecture (see LP: #1944541). It is also worth noting that the test plan above only looks at the permissions as libcamera is not *currently* expected to operate on Focal. Tests should be carried out on all supported boards (Zero 2, 2B, 3B, 3A+, 3B+, 4B) under both armhf and arm64 architectures (within the caveats noted above about the arm64 architecture). [Original Description] The /dev/vcio can have the wrong permissions due to a change in the kernel. As reported in https://github.com/raspberrypi/linux/pull/4624 (which I missed entirely, sorry pelwell!) we'll need a change in the udev rules to ensure the correct permissions are set. ** Changed in: raspberrypi-userland (Ubuntu Focal) Milestone: None => ubuntu-20.04.4 -- You received this bug notification because you are a member of
