[Bug 1949002] Re: can only mount btrfs filesystems with standard crc32c checksum, fails with xxhash, sha256
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: btrfs-progs (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/1949002 Title: can only mount btrfs filesystems with standard crc32c checksum, fails with xxhash, sha256 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs-progs/+bug/1949002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953685] Re: [Regression] Firefox 95 is laggy on GMA X4500 (EGL related?)
Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1745098 Likely caused by this change: https://bugzilla.mozilla.org/show_bug.cgi?id=1737068 ** Bug watch added: Mozilla Bugzilla #1745098 https://bugzilla.mozilla.org/show_bug.cgi?id=1745098 ** Bug watch added: Mozilla Bugzilla #1737068 https://bugzilla.mozilla.org/show_bug.cgi?id=1737068 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953685 Title: [Regression] Firefox 95 is laggy on GMA X4500 (EGL related?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1953685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953729] Re: Fixed user mapping broken in Samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.26
** Package changed: ubuntu => samba (Ubuntu) ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953729 Title: Fixed user mapping broken in Samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1953729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block
Actually there may be an even better solution: Before=shutdown.target which lintian has been nagging us about: https://lintian.debian.org/tags/systemd-service-file-shutdown-problems "There is race condition between stopping units and systemd getting a request to exit the main loop, so it may proceed with shutdown before all pending stop jobs have been processed." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840122 Title: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1840122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953736] [NEW] Request to upgrade vagrant-sshfs package version
Public bug reported: Recently, I learned that the package `vagrant-sshfs` 1.3.5-1 provided by Ubuntu is having a bug. It cannot handle CentOS gusts because CentOS have changed their repository names. I see a fix has been released in the upstream project: https://github.com/dustymabe/vagrant- sshfs/releases/tag/v1.3.6 I would like to request Ubuntu package maintainers to upgrade the package to 1.3.6. Steps to reproduce the error: Install Vagrant. Create a CentOS 8 guest with SSHFS mount. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: vagrant-sshfs 1.3.5-1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Dec 9 16:03:21 2021 InstallationDate: Installed on 2021-11-13 (25 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: vagrant-sshfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vagrant-sshfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953736 Title: Request to upgrade vagrant-sshfs package version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vagrant-sshfs/+bug/1953736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953733] [NEW] package matlab-support 0.0.21.1 failed to install/upgrade: 已安装 matlab-support 软件包 post-installation 脚本 子进程返回错误状态 1
Public bug reported: I can not install it. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: matlab-support 0.0.21.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 9 18:22:31 2021 ErrorMessage: 已安装 matlab-support 软件包 post-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2021-12-07 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all 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: matlab-support Title: package matlab-support 0.0.21.1 failed to install/upgrade: 已安装 matlab-support 软件包 post-installation 脚本 子进程返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: matlab-support (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953733 Title: package matlab-support 0.0.21.1 failed to install/upgrade: 已安装 matlab- support 软件包 post-installation 脚本 子进程返回错误状态 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matlab-support/+bug/1953733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949063] Re: Add F81966 watchdog support
** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949063 Title: Add F81966 watchdog support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block
@brian-murray prepared a test Jammy arm64 ISO with finalrd from the PPA above (serial: 20211208.1). I chose arm64 as it's the architecture most heavily affected by this issue (at least in our test environment). I performed several ISO test runs on the image and the success rate went from <50% to a solid 100%. I think it's enough to say that the fix works. I'll prepare an upload for Jammy, then we'll have to SRU the fix. ** Changed in: finalrd (Ubuntu) Status: New => Triaged ** Changed in: finalrd (Ubuntu) Assignee: (unassigned) => Paride Legovini (paride) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840122 Title: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1840122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946213] Re: strongswan: Fail to build against OpenSSL 3.0
** Changed in: strongswan 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/1946213 Title: strongswan: Fail to build against OpenSSL 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1946213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume
This bug was fixed in the package pulseaudio - 1:15.0+dfsg1-1ubuntu2.2 --- pulseaudio (1:15.0+dfsg1-1ubuntu2.2) impish; urgency=medium * d/p/0001-card-restore-setting-preferred-ports-in-entry_from_c.patch - cherry pick an upstream commit to fix the issue of hdmi can't be restored after s3 resume (LP: #1951667) -- Hui Wang Sat, 20 Nov 2021 12:15:12 +0800 ** Changed in: pulseaudio (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/1951667 Title: [SRU] pulseaudio: restore hdmi audio be active output after resume To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953731] [NEW] Jammy update: v5.15.7 upstream stable release
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: v5.15.7 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953731 Title: Jammy update: v5.15.7 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block
** Changed in: finalrd (Ubuntu Eoan) Status: New => Won't Fix ** Also affects: casper (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: finalrd (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: casper (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: finalrd (Ubuntu Impish) 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/1840122 Title: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1840122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952421] Re: Issue on sshd finds correct private key for a certificate when using ssh-agent
Hello, All the 2 (for Focal) and 5 (for Hirsute) tests were re-triggered and are passing now, so there's no real regression. We'll proceed with the verification from our end shortly. TIA! \o/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952421 Title: Issue on sshd finds correct private key for a certificate when using ssh-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1952421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953609] Re: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB
Hi Lukasz, > Ok, accepting this into -proposed, but I'm just actually wondering: > do we know why the armhf images require more space nowadays? I asked the same question whilst sponsoring the upload to Jammy. See: https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd- rootfs-1/+merge/412258/comments/1089194 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953609 Title: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1953609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789544] Re: smbd.service failed
Hi, did you comment to the wrong bug? This one was not about printers, as I understand it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789544 Title: smbd.service failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1789544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934735] Re: package gitolite3 3.6.11-2 failed to install/upgrade: installed gitolite3 package post-installation script subprocess returned error exit status 1
It looks like the root cause of this issue is that the post-install script uses the mktemp command when the current user is root and the default Ubuntu configuration sets $TMPDIR to /tmp/user/uid# so the temporary file that gets created is in /tmp/user/0. Later, the script switches to the gitolite3 user and tries to read the file that was created with mktemp (as the gitolite3 user, but that read fails because the gitolite3 user doesn't have permission to navigate the parent directories of the file. Changing permissions on the parent directories is a security problem, so the best solution is probably to set the $TMPDIR environment variable to some world-readable directory, such as /tmp, at the start of the post-install script. So, a one-line addition to the debian/postinst script probably fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934735 Title: package gitolite3 3.6.11-2 failed to install/upgrade: installed gitolite3 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitolite3/+bug/1934735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953173] Re: [MIR] python-asgiref
Review for Package: python-asgiref [Summary] I can confirm all the checks done when filing this. It seems to be a useful well maintainer library with not many known issues. MIR team ACK Sadly it isn't ready for promotion yet, as due to the nature of the code between servers and web-apps it does need a security review, so I'll assign ubuntu-security List of specific binary packages to be promoted to main: python3-asgiref Specific binary packages built, but NOT to be promoted to main: None Notes: - No TODOs identified at the moment [Duplication] OK: There is no other package in main providing the same functionality. [Dependencies] OK: - no other Dependencies to MIR due to this - no -dev/-debug/-doc packages that need exclusion [Embedded sources and static linking] OK: - no embedded source present - no static linking - does not have odd Built-Using entries - not a go package, no extra constraints to consider in that regard [Security] OK: - history of CVEs does not look concerning - does not run a daemon as root - does not use webkit1,2 - does not use lib*v8 directly - does not open a port/socket - does not process arbitrary web content - does not use centralized online accounts - does not integrate arbitrary javascript into the desktop - does not deal with system authentication (eg, pam), etc) - does not deal with security attestation (secure boot, tpm, signatures) Problems: - does not parse data formats - does process arbitrary web content - it is meant for "web apps <-> server" which by its nature is rather exposed [Common blockers] OK: - does not FTBFS currently - does have a test suite that runs at build time - test suite fails will fail the build upon error. - does have a non-trivial test suite that runs as autopkgtest - no new python2 dependency - Python package, but using dh_python [Packaging red flags] OK: - Ubuntu does not carry a delta - symbols tracking not applicable for this kind of code. - d/watch is present and looks ok (if needed, e.g. non-native) - Upstream update history is good - Debian/Ubuntu update history is good - the current release is packaged - promoting this does not seem to cause issues for MOTUs that so far maintained the package - no massive Lintian warnings - d/rules is rather clean - It is not on the lto-disabled list [Upstream red flags] OK: - no Errors/warnings during the build - no incautious use of malloc/sprintf - no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside tests) - no use of user nobody - no use of setuid - no important open bugs (crashers, etc) in Debian or Ubuntu - no dependency on webkit, qtwebkit, seed or libgoa-* - not part of the UI for extra checks - no translation present, but none needed for this case ** Changed in: python-asgiref (Ubuntu) Assignee: Christian Ehrhardt (paelzer) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953173 Title: [MIR] python-asgiref To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-asgiref/+bug/1953173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953712] Re: 5.15.2 rebuild against libopenssl3 requires patches and dependency fixes
$ remove-package -m "Agreed not to rebuild this for now against OpenSSL3, needs more changes (LP: #1953712)" -s jammy-proposed -e 5.15.2+dfsg-14ubuntu2 qtbase-opensource-src Removing packages from jammy-proposed: qtbase-opensource-src 5.15.2+dfsg-14ubuntu2 in jammy libqt5concurrent5 5.15.2+dfsg-14ubuntu2 in jammy amd64 libqt5concurrent5 5.15.2+dfsg-14ubuntu2 in jammy arm64 libqt5concurrent5 5.15.2+dfsg-14ubuntu2 in jammy armhf libqt5concurrent5 5.15.2+dfsg-14ubuntu2 in jammy i386 libqt5concurrent5 5.15.2+dfsg-14ubuntu2 in jammy ppc64el libqt5concurrent5 5.15.2+dfsg-14ubuntu2 in jammy s390x libqt5core5a 5.15.2+dfsg-14ubuntu2 in jammy amd64 libqt5core5a 5.15.2+dfsg-14ubuntu2 in jammy arm64 libqt5core5a 5.15.2+dfsg-14ubuntu2 in jammy armhf libqt5core5a 5.15.2+dfsg-14ubuntu2 in jammy i386 libqt5core5a 5.15.2+dfsg-14ubuntu2 in jammy ppc64el libqt5core5a 5.15.2+dfsg-14ubuntu2 in jammy s390x libqt5dbus5 5.15.2+dfsg-14ubuntu2 in jammy amd64 libqt5dbus5 5.15.2+dfsg-14ubuntu2 in jammy arm64 libqt5dbus5 5.15.2+dfsg-14ubuntu2 in jammy armhf libqt5dbus5 5.15.2+dfsg-14ubuntu2 in jammy i386 libqt5dbus5 5.15.2+dfsg-14ubuntu2 in jammy ppc64el libqt5dbus5 5.15.2+dfsg-14ubuntu2 in jammy s390x libqt5gui5 5.15.2+dfsg-14ubuntu2 in jammy amd64 libqt5gui5 5.15.2+dfsg-14ubuntu2 in jammy arm64 libqt5gui5 5.15.2+dfsg-14ubuntu2 in jammy armhf libqt5gui5 5.15.2+dfsg-14ubuntu2 in jammy i386 libqt5gui5 5.15.2+dfsg-14ubuntu2 in jammy ppc64el libqt5gui5 5.15.2+dfsg-14ubuntu2 in jammy s390x libqt5network5 5.15.2+dfsg-14ubuntu2 in jammy amd64 libqt5network5 5.15.2+dfsg-14ubuntu2 in jammy arm64 libqt5network5 5.15.2+dfsg-14ubuntu2 in jammy armhf libqt5network5 5.15.2+dfsg-14ubuntu2 in jammy i386 libqt5network5 5.15.2+dfsg-14ubuntu2 in jammy ppc64el libqt5network5 5.15.2+dfsg-14ubuntu2 in jammy s390x libqt5opengl5 5.15.2+dfsg-14ubuntu2 in jammy amd64 libqt5opengl5 5.15.2+dfsg-14ubuntu2 in jammy arm64 libqt5opengl5 5.15.2+dfsg-14ubuntu2 in jammy armhf libqt5opengl5 5.15.2+dfsg-14ubuntu2 in jammy i386 libqt5opengl5 5.15.2+dfsg-14ubuntu2 in jammy ppc64el libqt5opengl5 5.15.2+dfsg-14ubuntu2 in jammy s390x libqt5opengl5-dev 5.15.2+dfsg-14ubuntu2 in jammy amd64 libqt5opengl5-dev 5.15.2+dfsg-14ubuntu2 in jammy arm64 libqt5opengl5-dev 5.15.2+dfsg-14ubuntu2 in jammy armhf libqt5opengl5-dev 5.15.2+dfsg-14ubuntu2 in jammy i386 libqt5opengl5-dev 5.15.2+dfsg-14ubuntu2 in jammy ppc64el libqt5opengl5-dev 5.15.2+dfsg-14ubuntu2 in jammy s390x libqt5printsupport5 5.15.2+dfsg-14ubuntu2 in jammy amd64 libqt5printsupport5 5.15.2+dfsg-14ubuntu2 in jammy arm64 libqt5printsupport5 5.15.2+dfsg-14ubuntu2 in jammy armhf libqt5printsupport5 5.15.2+dfsg-14ubuntu2 in jammy i386 libqt5printsupport5 5.15.2+dfsg-14ubuntu2 in jammy ppc64el libqt5printsupport5 5.15.2+dfsg-14ubuntu2 in jammy s390x libqt5sql5 5.15.2+dfsg-14ubuntu2 in jammy amd64 libqt5sql5 5.15.2+dfsg-14ubuntu2 in jammy arm64 libqt5sql5 5.15.2+dfsg-14ubuntu2 in jammy armhf libqt5sql5 5.15.2+dfsg-14ubuntu2 in jammy i386 libqt5sql5 5.15.2+dfsg-14ubuntu2 in jammy ppc64el libqt5sql5 5.15.2+dfsg-14ubuntu2 in jammy s390x libqt5sql5-ibase 5.15.2+dfsg-14ubuntu2 in jammy amd64 libqt5sql5-ibase 5.15.2+dfsg-14ubuntu2 in jammy arm64 libqt5sql5-ibase 5.15.2+dfsg-14ubuntu2 in jammy armhf libqt5sql5-ibase 5.15.2+dfsg-14ubuntu2 in jammy i386 libqt5sql5-ibase 5.15.2+dfsg-14ubuntu2 in jammy ppc64el libqt5sql5-ibase 5.15.2+dfsg-14ubuntu2 in jammy s390x libqt5sql5-mysql 5.15.2+dfsg-14ubuntu2 in jammy amd64 libqt5sql5-mysql 5.15.2+dfsg-14ubuntu2 in jammy arm64 libqt5sql5-mysql 5.15.2+dfsg-14ubuntu2 in jammy armhf libqt5sql5-mysql 5.15.2+dfsg-14ubuntu2 in jammy i386 libqt5sql5-mysql 5.15.2+dfsg-14ubuntu2 in jammy ppc64el libqt5sql5-mysql 5.15.2+dfsg-14ubuntu2 in jammy s390x libqt5sql5-odbc 5.15.2+dfsg-14ubuntu2 in jammy amd64 libqt5sql5-odbc 5.15.2+dfsg-14ubuntu2 in jammy arm64 libqt5sql5-odbc 5.15.2+dfsg-14ubuntu2 in jammy armhf
[Bug 1923104] Re: Include Infiniband Peer Memory interface
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923104 Title: Include Infiniband Peer Memory interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947206] Re: Updates to ib_peer_memory requested by Nvidia
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947206 Title: Updates to ib_peer_memory requested by Nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953609] Re: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB
Ok, accepting this into -proposed, but I'm just actually wondering: do we know why the armhf images require more space nowadays? ** Changed in: livecd-rootfs (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/1953609 Title: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1953609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953609] Re: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB
Hello Philip, or anyone else affected, Accepted livecd-rootfs into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd- rootfs/2.742.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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: livecd-rootfs (Ubuntu Impish) Status: New => 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/1953609 Title: [SRU] Bump disk image size for amhf cloud images from 2.2GB to 3.5GB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1953609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953729] [NEW] Fixed user mapping broken in Samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.26
Public bug reported: Samba upgrade from 2:4.7.6+dfsg~ubuntu-0ubuntu2 to 2:4.7.6+dfsg~ubuntu-0ubuntu2.26 breaks fixed user mapping Environment: Operating System: Ubuntu 18.04.6 LTS Kernel: Linux 5.4.0-1058-oracle (Oracle OCI kernel) apt list -a samba samba/bionic-updates,bionic-security,now 2:4.7.6+dfsg~ubuntu-0ubuntu2.26 amd64 [installed] samba/bionic 2:4.7.6+dfsg~ubuntu-0ubuntu2 amd64 /etc/samba/smb.conf (relevant parts): [global] workgroup = DOMAIN security = ADS realm = DOMAIN.TLD idmap config * : backend = tdb idmap config * : range = 3000-9 idmap config DOMAIN : backend = rid idmap config DOMAIN : range = 10-19 username map = /etc/samba/user.map winbind refresh tickets = Yes vfs objects = acl_xattr map acl inherit = Yes dedicated keytab file = /etc/krb5.keytab kerberos method = secrets and keytab /etc/samba/user.map: !root = DOMAIN\Administrator Expected behaviour (running without problems in 2:4.7.6+dfsg~ubuntu-0ubuntu2) User DOMAIN\Administrator has access as root to all Samba shares. Behaviour after (unattended) upgrade to 2:4.7.6+dfsg~ubuntu-0ubuntu2.26: Changes: /var/log/unattended-upgrades/unattended-upgrades.log 2021-12-08 06:59:55,179 INFO Packages that will be upgraded: busybox-initramfs busybox-static libnss-winbind libwbclient0 python-samba samba samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules winbind Problem: User DOMAIN\Administrator (mapped as user root on samba server) has no more access to any Samba shares. Detailed problem description: Attempt to access Samba shares from Windows (Server 2016, current patch level). Errors differ if Client for NFS is installed in Windows or not. When Client for NFS ist installed, Windows tries to connect with NFS first, so remove it for testing or results will be false (ERROR_INVALID_TOKEN). Trying to acces Samba with SMB results in immediate error: [Window Title] Network Error [Main Instruction] Windows cannot access \\sambaserver [Content] Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose. [^] Hide details [Diagnose] [Cancel] [Expanded Information] Error code: 0x80070035 The network path was not found. I could not find any corresponding log file entry on Samba server in any log. IMPORTANT: Attempt to connect as regular AD domain user from SAME server (Map network drive using different credentials) works without any problem. After rolling back all packages to 2:4.7.6+dfsg~ubuntu-0ubuntu2 everything works without problems again: apt install libnss-winbind=2:4.7.6+dfsg~ubuntu-0ubuntu2 libsmbclient=2:4.7.6+dfsg~ubuntu-0ubuntu2 libwbclient0=2:4.7.6+dfsg~ubuntu-0ubuntu2 python- samba=2:4.7.6+dfsg~ubuntu-0ubuntu2 samba=2:4.7.6+dfsg~ubuntu-0ubuntu2 samba-common=2:4.7.6+dfsg~ubuntu-0ubuntu2 samba-common- bin=2:4.7.6+dfsg~ubuntu-0ubuntu2 samba-dsdb- modules=2:4.7.6+dfsg~ubuntu-0ubuntu2 samba- libs=2:4.7.6+dfsg~ubuntu-0ubuntu2 samba-vfs- modules=2:4.7.6+dfsg~ubuntu-0ubuntu2 smbclient=2:4.7.6+dfsg~ubuntu-0ubuntu2 winbind=2:4.7.6+dfsg~ubuntu-0ubuntu2 # I hope that prevents from further unattended upgrade till the bug is fixed: apt-mark hold libnss-winbind libsmbclient libwbclient0 python-samba samba samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules smbclient winbind ** Affects: 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/1953729 Title: Fixed user mapping broken in Samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1953729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953523] Re: KDE problem mounting Sandisk USB
Thanks for providing the additional logs. As Sergio said, SMART is often unreliable on USB drives. What can happen, in very general terms, is that a proper SATA ssd is attached to a SATA-to-USB adapter. The adapter is not fully transparent to the SMART data, or it provides incomplete data, which may be enough for the vendor's "health monitor app", but isn't fully standards compliant, and so it can appear as failing. I did a quick Google search for "sandisk usb Perc_Avail_Resrvd_Space" apparently that's a common issue for Sandisk USB drives. You may need to disable SMART monitoring for yours. If in doubt, do an extra backup :-) I doubt there's a bug in Ubuntu here, but if you believe otherwise please comment back with your rationale and we'll look at this again. I'm leaving this report marked Incomplete for the moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953523 Title: KDE problem mounting Sandisk USB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1953523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
Any update on this bug and the status of focal? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882420] Re: Please make qemu-bridge-helper suid as suggested in the qemu docs
What can be a solution for that? Without making it root suid (which is a good thing) applications like gnome-boxes fail in an ungraceful way that is very hard to understand. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882420 Title: Please make qemu-bridge-helper suid as suggested in the qemu docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1882420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932445] Update Released
The verification of the Stable Release Update for oem-sutton.newell- cable-meta 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/1932445 Title: [MIR] oem-sutton.newell-cable-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1932445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
The speed is limited on every boot now...I also notice my bios time
being reset to 2013...when unplugged from the wall (I'm going to open it
up, the cmos battery may have died.)
rt@sys76:~$ sudo grep . /sys/class/powercap/intel-rapl/intel-rapl\:0/*
[sudo] password for rt:
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_max_power_uw:4700
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_name:long_term
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_power_limit_uw:4700
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_0_time_window_us:27983872
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_max_power_uw:0
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_name:short_term
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_power_limit_uw:5875
/sys/class/powercap/intel-rapl/intel-rapl:0/constraint_1_time_window_us:2440
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/device: Is a directory
/sys/class/powercap/intel-rapl/intel-rapl:0/enabled:0
/sys/class/powercap/intel-rapl/intel-rapl:0/energy_uj:5242172615
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:0: Is a directory
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:1: Is a directory
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:2: Is a directory
/sys/class/powercap/intel-rapl/intel-rapl:0/max_energy_range_uj:262143328850
/sys/class/powercap/intel-rapl/intel-rapl:0/name:package-0
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/power: Is a directory
grep: /sys/class/powercap/intel-rapl/intel-rapl:0/subsystem: Is a directory
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$
rt@sys76:~$ sudo rdmsr -c -p0 0x64F
rdmsr: CPU 0 cannot read MSR 0x064f
rt@sys76:~$ sudo strace rdmsr 0x64F
execve("/usr/sbin/rdmsr", ["rdmsr", "0x64F"], 0x7ffe9486b188 /* 16 vars */) = 0
brk(NULL) = 0x5633b869a000
arch_prctl(0x3001 /* ARCH_??? */, 0x7ffe398f8370) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=79034, ...}) = 0
mmap(NULL, 79034, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fc1f8b19000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360q\2\0\0\0\0\0"...,
832) = 832
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
fstat(3, {st_mode=S_IFREG|0755, st_size=2029224, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fc1f8b17000
pread64(3, "\6\0\0\0\4\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0@\0\0\0\0\0\0\0"...,
784, 64) = 784
pread64(3, "\4\0\0\0\20\0\0\0\5\0\0\0GNU\0\2\0\0\300\4\0\0\0\3\0\0\0\0\0\0\0",
32, 848) = 32
pread64(3,
"\4\0\0\0\24\0\0\0\3\0\0\0GNU\0\t\233\222%\274\260\320\31\331\326\10\204\276X>\263"...,
68, 880) = 68
mmap(NULL, 2036952, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fc1f8925000
mprotect(0x7fc1f894a000, 1847296, PROT_NONE) = 0
mmap(0x7fc1f894a000, 1540096, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x25000) = 0x7fc1f894a000
mmap(0x7fc1f8ac2000, 303104, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x19d000) = 0x7fc1f8ac2000
mmap(0x7fc1f8b0d000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7fc1f8b0d000
mmap(0x7fc1f8b13000, 13528, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fc1f8b13000
close(3)= 0
arch_prctl(ARCH_SET_FS, 0x7fc1f8b18580) = 0
mprotect(0x7fc1f8b0d000, 12288, PROT_READ) = 0
mprotect(0x5633b7d85000, 4096, PROT_READ) = 0
mprotect(0x7fc1f8b5a000, 4096, PROT_READ) = 0
munmap(0x7fc1f8b19000, 79034) = 0
openat(AT_FDCWD, "/dev/cpu/0/msr", O_RDONLY) = 3
pread64(3, 0x7ffe398f8288, 8, 1615) = -1 EIO (Input/output error)
write(2, "rdmsr: CPU 0 cannot read MSR 0x0"..., 40rdmsr: CPU 0 cannot read MSR
0x064f
) = 40
exit_group(4) = ?
+++ exited with 4 +++
rt@sys76:~$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at minimum value..again Ubuntu 20.04.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1945221/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949179] Re: Backport OpenJDK 17.0.1 to 21.10, 21.04, 20.04 LTS and 18.04 LTS
This bug was fixed in the package openjdk-17 - 17.0.1+12-1~18.04 --- openjdk-17 (17.0.1+12-1~18.04) bionic-security; urgency=medium * SRU: LP: #1949179: Backport the OpenJDK 17.0.1 security release. openjdk-17 (17.0.1+12-1) unstable; urgency=medium * OpenJDK 17.0.1+12 (release). * Remove patches applied upstream. -- Matthias Klose Fri, 29 Oct 2021 11:50:31 +0200 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949179 Title: Backport OpenJDK 17.0.1 to 21.10, 21.04, 20.04 LTS and 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-17/+bug/1949179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949179] Re: Backport OpenJDK 17.0.1 to 21.10, 21.04, 20.04 LTS and 18.04 LTS
This bug was fixed in the package openjdk-17 - 17.0.1+12-1~20.04 --- openjdk-17 (17.0.1+12-1~20.04) focal-security; urgency=medium * SRU: LP: #1949179: Backport the OpenJDK 17.0.1 security release. openjdk-17 (17.0.1+12-1) unstable; urgency=medium * OpenJDK 17.0.1+12 (release). * Remove patches applied upstream. -- Matthias Klose Fri, 29 Oct 2021 11:50:31 +0200 ** Changed in: openjdk-17 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: openjdk-17 (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/1949179 Title: Backport OpenJDK 17.0.1 to 21.10, 21.04, 20.04 LTS and 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-17/+bug/1949179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915910] Re: evince does not print (apparmor, pxgsettings)
The apparmor config works. Thanks Karsten. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924730] Re: [MIR] oem-sutton.newell-carnell-meta
This bug was fixed in the package oem-sutton.newell-carnell-meta - 20.04~ubuntu1 --- oem-sutton.newell-carnell-meta (20.04~ubuntu1) focal; urgency=medium * Meta package for Lenovo ThinkCentre M90a Gen 2. (LP: #1924730) -- Bin Li Wed, 17 Nov 2021 16:17:51 +0800 ** Changed in: oem-sutton.newell-carnell-meta (Ubuntu Focal) 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/1924730 Title: [MIR] oem-sutton.newell-carnell-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924730] Update Released
The verification of the Stable Release Update for oem-sutton.newell- carnell-meta 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/1924730 Title: [MIR] oem-sutton.newell-carnell-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924734] Update Released
The verification of the Stable Release Update for oem-sutton.newell- carrie-meta 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/1924734 Title: [MIR] oem-sutton.newell-carrie-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924734] Re: [MIR] oem-sutton.newell-carrie-meta
This bug was fixed in the package oem-sutton.newell-carrie-meta - 20.04~ubuntu1 --- oem-sutton.newell-carrie-meta (20.04~ubuntu1) focal; urgency=medium * Meta package for Lenovo ThinkCentre M70q Gen 2, M90q Gen 2. (LP: #1924734) -- Bin Li Wed, 17 Nov 2021 17:09:22 +0800 ** Changed in: oem-sutton.newell-carrie-meta (Ubuntu Focal) 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/1924734 Title: [MIR] oem-sutton.newell-carrie-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932439] Update Released
The verification of the Stable Release Update for oem-sutton.newell- aadi-meta 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/1932439 Title: [MIR] oem-sutton.newell-aadi-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1932439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932439] Re: [MIR] oem-sutton.newell-aadi-meta
This bug was fixed in the package oem-sutton.newell-aadi-meta - 20.04~ubuntu1 --- oem-sutton.newell-aadi-meta (20.04~ubuntu1) focal; urgency=medium * Meta package for Lenovo ThinkPad L15 Gen 1. (LP: #1932439) -- Bin Li Wed, 17 Nov 2021 14:20:52 +0800 ** Changed in: oem-sutton.newell-aadi-meta (Ubuntu Focal) 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/1932439 Title: [MIR] oem-sutton.newell-aadi-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1932439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932445] Re: [MIR] oem-sutton.newell-cable-meta
This bug was fixed in the package oem-sutton.newell-cable-meta - 20.04~ubuntu1 --- oem-sutton.newell-cable-meta (20.04~ubuntu1) focal; urgency=medium * Meta package for Lenovo ThinkCentre M75s Gen 2. (LP: #1932445) -- Bin Li Wed, 17 Nov 2021 15:01:42 +0800 ** Changed in: oem-sutton.newell-cable-meta (Ubuntu Focal) 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/1932445 Title: [MIR] oem-sutton.newell-cable-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1932445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934831] Update Released
The verification of the Stable Release Update for oem-sutton.newell- aaden-meta 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/1934831 Title: [MIR] oem-sutton.newell-aaden-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934831] Re: [MIR] oem-sutton.newell-aaden-meta
This bug was fixed in the package oem-sutton.newell-aaden-meta - 20.04~ubuntu1 --- oem-sutton.newell-aaden-meta (20.04~ubuntu1) focal; urgency=medium * Meta package for Lenovo ThinkPad L15 Gen 2a. (LP: #1934831) -- Bin Li Wed, 17 Nov 2021 14:20:52 +0800 ** Changed in: oem-sutton.newell-aaden-meta (Ubuntu Focal) 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/1934831 Title: [MIR] oem-sutton.newell-aaden-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951238] Update Released
The verification of the Stable Release Update for oem-sutton.simon- carrie-meta 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/1951238 Title: [MIR] oem-sutton.simon-carrie-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1951238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951238] Re: [MIR] oem-sutton.simon-carrie-meta
This bug was fixed in the package oem-sutton.simon-carrie-meta - 20.04~ubuntu2 --- oem-sutton.simon-carrie-meta (20.04~ubuntu2) focal; urgency=medium * Meta package for Lenovo ThinkStation P350 Tiny. (LP: #1951238) -- Bin Li Wed, 17 Nov 2021 17:14:40 +0800 ** Changed in: oem-sutton.simon-carrie-meta (Ubuntu Focal) 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/1951238 Title: [MIR] oem-sutton.simon-carrie-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1951238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949179] Update Released
The verification of the Stable Release Update for openjdk-17 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/1949179 Title: Backport OpenJDK 17.0.1 to 21.10, 21.04, 20.04 LTS and 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-17/+bug/1949179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949179] Re: Backport OpenJDK 17.0.1 to 21.10, 21.04, 20.04 LTS and 18.04 LTS
This bug was fixed in the package openjdk-17 - 17.0.1+12-1~21.04 --- openjdk-17 (17.0.1+12-1~21.04) hirsute-security; urgency=medium * SRU: LP: #1949179: Backport the OpenJDK 17.0.1 security release. openjdk-17 (17.0.1+12-1) unstable; urgency=medium * OpenJDK 17.0.1+12 (release). * Remove patches applied upstream. -- Matthias Klose Fri, 29 Oct 2021 11:50:31 +0200 ** Changed in: openjdk-17 (Ubuntu Hirsute) 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/1949179 Title: Backport OpenJDK 17.0.1 to 21.10, 21.04, 20.04 LTS and 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-17/+bug/1949179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949179] Re: Backport OpenJDK 17.0.1 to 21.10, 21.04, 20.04 LTS and 18.04 LTS
This bug was fixed in the package openjdk-17 - 17.0.1+12-1~21.10 --- openjdk-17 (17.0.1+12-1~21.10) impish-security; urgency=medium * SRU: LP: #1949179: Backport the OpenJDK 17.0.1 security release. openjdk-17 (17.0.1+12-1) unstable; urgency=medium * OpenJDK 17.0.1+12 (release). * Remove patches applied upstream. -- Matthias Klose Fri, 29 Oct 2021 11:50:31 +0200 ** Changed in: openjdk-17 (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/1949179 Title: Backport OpenJDK 17.0.1 to 21.10, 21.04, 20.04 LTS and 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-17/+bug/1949179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951667] Update Released
The verification of the Stable Release Update for pulseaudio 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/1951667 Title: [SRU] pulseaudio: restore hdmi audio be active output after resume To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945296] Re: To support goodix fp device [27C6:639C]
This bug was fixed in the package libfprint - 1:1.90.2+tod1-0ubuntu1~20.04.5 --- libfprint (1:1.90.2+tod1-0ubuntu1~20.04.5) focal; urgency=medium * debian/patches: Add support for goodix and new elan and synaptics devices. Elan and synaptics drivers only need to list new product IDs to work with new devices, and including other changes that new devices may require. While adding the new goodix moc driver, that is already part of many stable releases now, coming with full unit test and latest supported devices. (LP: #1945296, #1945298) * debian/patches: Fix template struct in goodix drivers (LP: #1945296) -- Marco Trevisan (Treviño) Wed, 27 Oct 2021 00:07:47 +0200 ** Changed in: libfprint (Ubuntu Focal) 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/1945296 Title: To support goodix fp device [27C6:639C] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945296] Update Released
The verification of the Stable Release Update for libfprint 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/1945296 Title: To support goodix fp device [27C6:639C] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945296] Re: To support goodix fp device [27C6:639C]
This bug was fixed in the package libfprint - 1:1.90.7+git20210222+tod1-0ubuntu4~21.10.1 --- libfprint (1:1.90.7+git20210222+tod1-0ubuntu4~21.10.1) impish; urgency=medium * debian/patches: Add support for new elan, goodix and synaptics drivers. Most of the drivers only need to list new product IDs to work with new devices, and including other changes that new devices may require. (LP: #1945296, #1945298) * debian/patches: Fix template struct in goodix drivers (LP: #1945296) -- Marco Trevisan (Treviño) Tue, 26 Oct 2021 21:40:36 +0200 ** Changed in: libfprint (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/1945296 Title: To support goodix fp device [27C6:639C] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945296] Re: To support goodix fp device [27C6:639C]
Thank you! This is really good testing, I appreciate you trying this out on so many different fingerprint devices. The ageing of SRUs is important because it exposes the update to additional testing by the community, but in certain cases - and for packages that are not as widely tested (or not part of a critical bugfix), ageing is not as useful as it normally would. So after discussing the testing performed for this SRU and discussing the importance of landing this sooner than later (from the HWE POV), I will accept the updates earlier as an exception. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945296 Title: To support goodix fp device [27C6:639C] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945298] Re: To support goodix fp device [27C6:63BC]
This bug was fixed in the package libfprint - 1:1.90.2+tod1-0ubuntu1~20.04.5 --- libfprint (1:1.90.2+tod1-0ubuntu1~20.04.5) focal; urgency=medium * debian/patches: Add support for goodix and new elan and synaptics devices. Elan and synaptics drivers only need to list new product IDs to work with new devices, and including other changes that new devices may require. While adding the new goodix moc driver, that is already part of many stable releases now, coming with full unit test and latest supported devices. (LP: #1945296, #1945298) * debian/patches: Fix template struct in goodix drivers (LP: #1945296) -- Marco Trevisan (Treviño) Wed, 27 Oct 2021 00:07:47 +0200 ** Changed in: libfprint (Ubuntu Focal) 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/1945298 Title: To support goodix fp device [27C6:63BC] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945298] Update Released
The verification of the Stable Release Update for libfprint 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/1945298 Title: To support goodix fp device [27C6:63BC] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945298] Re: To support goodix fp device [27C6:63BC]
This bug was fixed in the package libfprint - 1:1.90.7+git20210222+tod1-0ubuntu4~21.10.1 --- libfprint (1:1.90.7+git20210222+tod1-0ubuntu4~21.10.1) impish; urgency=medium * debian/patches: Add support for new elan, goodix and synaptics drivers. Most of the drivers only need to list new product IDs to work with new devices, and including other changes that new devices may require. (LP: #1945296, #1945298) * debian/patches: Fix template struct in goodix drivers (LP: #1945296) -- Marco Trevisan (Treviño) Tue, 26 Oct 2021 21:40:36 +0200 ** Changed in: libfprint (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/1945298 Title: To support goodix fp device [27C6:63BC] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1118551] Re: I-NEX n'appariat pas sous voyager 12.10
** Changed in: i-nex Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1118551 Title: I-NEX n'appariat pas sous voyager 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/i-nex/+bug/1118551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1270373] Re: Nemo allows only one file rename (in list view) per login session
** Changed in: linuxmint Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1270373 Title: Nemo allows only one file rename (in list view) per login session To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1270373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952924] Re: [MIR] pipewire-media-session
Ack on the testplan. The remaining part is some comments on the recommended TODO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952924 Title: [MIR] pipewire-media-session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1952924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953722] [NEW] package linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным
Public bug reported: -( ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-5.8.0-59-generic:amd64: Remove linux-hwe-5.8-headers-5.8.0-59:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 9 10:42:13 2021 ErrorMessage: проблемы зависимостей — оставляем не настроенным InstallationDate: Installed on 2020-07-09 (517 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: Error: command ['readlink', '-f', "ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. , Error: [Errno 2] Нет такого файла или каталога: 'Error: command [\'readlink\', \'-f\', "ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n', unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953722 Title: package linux-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1953722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953721] [NEW] package linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным
Public bug reported: _( ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: linux-headers-5.8.0-59-generic:amd64: Remove linux-hwe-5.8-headers-5.8.0-59:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 9 10:42:13 2021 ErrorMessage: проблемы зависимостей — оставляем не настроенным InstallationDate: Installed on 2020-07-09 (517 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: Error: command ['readlink', '-f', "ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. , Error: [Errno 2] Нет такого файла или каталога: 'Error: command [\'readlink\', \'-f\', "ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\\n/usr/bin/python3"] failed with exit code 1: ERROR: ld.so: object \'libesets_pac.so\' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.\n', unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953721 Title: package linux-image-generic-hwe-20.04 5.11.0.41.45~20.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1953721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949579] Re: [MIR] postgresql-14
Thanks to RAOF the postgresql-server-dev-1 -> llvm issue is resolved. python-sqlalchemy-utils was a test on an old version 0.36.8-2ubuntu2 failing when openssl3 migrated. There now is a merge of the new version 0.37.8-1ubuntu1 with new tests. Migration reference runs with that new version worked fine, I'm retesting postgresql with that new version locally and on LP. The new version passes fine with the right triggers to the new postgresql and should unblock on the next migration run. The x86 run is the only one missing and in the autopkgtest queue which is rather slow atm - estimating 10h. pgsql-ogr-fdw also had a test fail, but someone already submitted a migration-reference run and that failed as well independent to PG-14 - so that should be fine as well. ... waiting for tests and proposed migration to run showing me new blockers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949579 Title: [MIR] postgresql-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-14/+bug/1949579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)
Thanks for the explanation, I can understand the difficulty and hope misbehaving external extensions don't affect the image of GNOME too much. I will reactivate the dock and repeat the steps in comments #1 and #3 at the next crash, although I'm unsure how that will bring new information as I would imagine we'll get the same information as when it happened before? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953720] [NEW] OSError: [Errno 30] Read-only file system: '/var/crash/...
Public bug reported: Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: Traceback (most recent call last): Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 408, in Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: main() Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 152, in main Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: if not dispatch(client, servers, config): Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 239, in check Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: send_digest(digested, mock_runner, servers) Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 262, in send_digest Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: _send_digest(runner, servers[0], digested) Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/bin/pyzor", line 253, in _send_digest Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: runner.run(server, (digested, server)) Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/lib/python3/dist-packages/pyzor/client.py", line 258, in run Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: response = self.routine(*args, **kwargs) Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/lib/python3/dist-packages/pyzor/client.py", line 120, in _mock_check Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: msg = (b"Code: %s\nDiag: OK\nPV: %s\nThread: 1024\nCount: 0\n" Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: TypeError: %b requires a bytes-like object, or an object that implements __bytes__, not 'int' Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: Error in sys.excepthook: Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: Traceback (most recent call last): Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 153, in apport_excepthook Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: with os.fdopen(os.open(pr_filename, Dec 6 12:02:32 mail-cbf-int pyzor[2966924]: OSError: [Errno 30] Read-only file system: '/var/crash/_usr_bin_pyzor.122.crash' 1) due to an encoding error, pyzor is throwing an exception. 2) /usr/lib/python3/dist-packages/apport_python_hook.py is the exception handler invoked (belonging to the python3-apport package) 3) This exception handler tries to write to /var/crash/_usr_bin_pyzor.122.crash, which fails I checked the permissions: # ls -l /var/crash total 0 # ls -ld /var/crash drwxrwxrwt 2 root root 4096 Dec 8 16:45 /var/crash # ls -ld /var/ drwxr-xr-x 18 root root 4096 Jun 23 2020 /var/ # ls -ld / drwxr-xr-x 24 root root 4096 Nov 30 06:19 / /var/crash is sticky, so why can't it write? # cat /proc/mounts |fgrep crash # ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3-apport 2.20.11-0ubuntu27.21 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 9 09:39:40 2021 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to focal on 2021-04-07 (245 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953720 Title: OSError: [Errno 30] Read-only file system: '/var/crash/... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1953720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925017] Re: [MIR] oem-stella.cmit-deoxys-meta
Attach oem-stella.cmit-deoxys-meta_20.04~ubuntu1.debdiff by oem-scripts 1.25. ** Changed in: oem-priority Status: In Progress => Fix Committed ** Changed in: ubuntu Status: New => Confirmed ** Patch removed: "oem-stella.cmit-deoxys-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/bugs/1925017/+attachment/5546374/+files/oem-stella.cmit-deoxys-meta_20.04~ubuntu1.debdiff ** Patch added: "oem-stella.cmit-deoxys-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/bugs/1925017/+attachment/5546431/+files/oem-stella.cmit-deoxys-meta_20.04~ubuntu1.debdiff ** Tags added: oem-needs-upload ubuntu-certified -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925017 Title: [MIR] oem-stella.cmit-deoxys-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1925017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le
Manually verified on Focal 5.4.0-92-generic with node dryden (as the test will be interrupted with reuseport_bpf_cpu bug 1927076) ubuntu@dryden:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./reuseport_bpf_numa ubuntu@dryden:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ echo $? 0 ** Tags removed: verification-needed-focal ** Tags added: 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/1867570 Title: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1867570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952934] Re: Intel HDA Sound Card not detected on Ubuntu 20.04
Thnaks hui , dmesg attached , I thought apport-collect would attach it actually ** Changed in: alsa-driver (Ubuntu) Assignee: I-Cat (i-cat) => (unassigned) ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+attachment/5546430/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952934 Title: Intel HDA Sound Card not detected on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934697] Re: Default keyring password keeps resetting if set to empty
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: seahorse (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/1934697 Title: Default keyring password keeps resetting if set to empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1934697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953431] Re: [SRU] fix unsafe access in unregister_conn()
The attachment "0001-msgr-async-fix-unsafe-access-in- unregister_conn.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953431 Title: [SRU] fix unsafe access in unregister_conn() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934697] Re: Default keyring password keeps resetting if set to empty
I maybe experience the same issue: seahorse keeps (randomly after session start) asking me a password to unlock keyring. The point is that I set a void keyring pwd avery time and it's resetted every time. I have full-disk-encryption too... but I kept a gdm login pwd after boot. Ubuntu 22.04 dev, up to date. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934697 Title: Default keyring password keeps resetting if set to empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1934697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951680] Re: DDNet client server browser doesn't show most servers
** Changed in: ddnet (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/1951680 Title: DDNet client server browser doesn't show most servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddnet/+bug/1951680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948904] Re: Installed systemd package post-installation script subprocess returned error exit status 127
I am also affected by this error. I did this update yesterday. I can no longer use any package installation system. But I did something for this situation. I created symlink of 'lib/systemd/libsystem-shared-248.so' as 'libsystem-shared-247.so' so this error is fixed. ( sudo ln -s /lib/systemd/libsystem-shared-248.so /lib/systemd/libsystemd-shared-247.so sudo ln -s /lib/systemd/libsystem-shared-248.so /usr/lib/systemd/libsystemd-shared-247.so ) But now when I run 'sudo dpkg --configure systemd' the error changed to: Ayarlanıyor: systemd (248.3-1ubuntu8) ... systemd-machine-id-setup: symbol lookup error: systemd-machine-id-setup: undefined symbol: log_assert_failed_unreachable_realm, version SD_SHARED dpkg: systemd paketi işlenirken sorun yaşandı (--configure): systemd paketi post-installation betiği kuruldu alt süreci 127 hatalı çıkış kodu ile sona erdi İşleme sırasında hatalarla karşılaşıldı: systemd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948904 Title: Installed systemd package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1948904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835630] Re: Relax dependency on specific version of libnvidia-compute-NNN
bloodyiron: do you know how -dkms packages work? they compile from source, every time... that's what ufos suggests, and if you look at install-nvtop posted early, it'll just build a package (whenever needed, and install that, and mark it hold). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835630 Title: Relax dependency on specific version of libnvidia-compute-NNN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvtop/+bug/1835630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953431] Re: [SRU] fix unsafe access in unregister_conn()
** Description changed: [Impact] without holding sufficient locks, accept_conn and shutdown_connections in AsyncMessenger could cause OSD processes crash [Test plan] + run ceph_test_async_networkstack repeatedly, this will trigger many async messenger events and make sure + 1. OSD process not crash + 2. no deadlock [Where problems could occur] hold sufficient locks and decrement l_msgr_active_connections can avoid OSD processes to crash due to race condition The only problem I can imagine is deadlock if one process is holding lock A and wait for lock B, the there is another process holding lock B and wait for lock A - [Other info] from upstream: octopus backport tracker https://tracker.ceph.com/issues/50482 octopus backport PR https://github.com/ceph/ceph/pull/43325 ** Patch added: "0001-msgr-async-fix-unsafe-access-in-unregister_conn.patch" https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953431/+attachment/5546429/+files/0001-msgr-async-fix-unsafe-access-in-unregister_conn.patch ** Tags added: sts sts-sru-needed verification-needed-focal ** Also affects: ceph (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ceph (Ubuntu Focal) Status: New => In Progress ** Changed in: ceph (Ubuntu Focal) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953431 Title: [SRU] fix unsafe access in unregister_conn() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1953431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)
Regarding your other question; sandboxing would of course be best but that's something that would need to be designed from the ground up. And then new APIs specifically for sandboxed extensions would be needed. And then we would still find either most extensions want to do things not possible in the sandbox, or most extensions never get ported to the sandbox model. So sandboxing is unlikely to ever happen. More likely that extensions would just be forbidden, but more likely than that is maintaining the status quo - extensions are allowed to do anything and break anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932525] Re: This bug is back on my pc - bug #1722481 Systemd Sync twice at shutdown
I am seeing something similar on 20.04. If my network fails and I have any network filesystems mounted (including nfs3 or nfs4 via autofs or iSCSI via fstab) when I issue a shutdown or reboot command, then I am likely to have a 10+ minute delay after the console displays that it has reached target shutdown. The console will then cycle through displaying information about each filesystem, such as the fact that the system is trying to unmount it, the unmount failed, and it is now forcibly killing processes. While I have not looked at the source, the timing of the console messages would imply that the process to unmount filesystems and kill processes is single-threaded, as there is a significant delay as it goes through this process with each filesystem. After it has cycled through all filesystems, it then slowly cycles through each filesystem again. Unfortunately, the logging system has already shut down by the time any of this happens, so I have no logs in journald or syslog to submit in relationship to this issue. Can the process be fixed to only cycle through each filesystem once, and also to attempt to do multiple filesystems simultaneously so that, at worst, I only have to wait through one timeout cycle? I could possibly see a reason that you might need to wait the timeout multiple times in the event of nested remote filesystems (e.g. if every level of /dont/try/this/at/home was a different filesystem on non-local disk), but that is not the configuration that I have. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932525 Title: This bug is back on my pc - bug #1722481 Systemd Sync twice at shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1932525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)
Bug 1951786 would not explain these crashes, it's just something I saw in your log. To track down the crashes further you would need to repeat the steps in comments #1 and #3. But at least it sounds like we can assign it to ubuntu-dock now. Probably. ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606245] Re: gwenview crashes when loading multiple files
Upstream bug closed "RESOLVED WORKSFORME" on 2017-10-15 Bug report did not expire due to bug watch ** Changed in: gwenview (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606245 Title: gwenview crashes when loading multiple files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwenview/+bug/1606245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932525] Re: This bug is back on my pc - bug #1722481 Systemd Sync twice at shutdown
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (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/1932525 Title: This bug is back on my pc - bug #1722481 Systemd Sync twice at shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1932525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952924] Re: [MIR] pipewire-media-session
Thanks for the review, I created a TestPlan category under UbuntuDesktop and wrote one for this package now as https://wiki.ubuntu.com/DesktopTeam/TestPlans/PipewireMediaSession . I will try to discuss the Debian team if they would welcome having that somehow part of the source package. I've upstreamed the build warning on https://gitlab.freedesktop.org/pipewire/media-session/-/issues/4 ** Bug watch added: gitlab.freedesktop.org/pipewire/media-session/-/issues #4 https://gitlab.freedesktop.org/pipewire/media-session/-/issues/4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952924 Title: [MIR] pipewire-media-session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1952924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952924] Re: [MIR] pipewire-media-session
** Changed in: pipewire-media-session (Ubuntu) Status: Incomplete => New ** Changed in: pipewire-media-session (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) ** Description changed: [Availability] The package pipewire-media-session is already in Ubuntu universe. The package pipewire-media-session build for the architectures it is designed to work on. It currently builds and works for architectures: amd64 arm64 armhf ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/pipewire-media-session [Rationale] - The package pipewire-media-session is required in Ubuntu main for video recording and sharing in GNOME to work correctly. - The feature was included in pipewire itself until impish and split out as a separate component in 0.3.39 - Wireplumber (MIR bug https://launchpad.net/bugs/1949776) is an alternative but it's newer and more complex and we decided to stick to the simple option until we switch to pipewire also as the default sound service. [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package installs an user services, but they are safe because it's an user job so under limited priviledge and using systemd securoty features like RestrictNamespaces=yes - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu - - Ubuntu https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug has no reports - - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=pipewire-media-session has no reports + - Ubuntu https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug has no reports + - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=pipewire-media-session has no reports - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package does not run a test at build time because upstream doesn't provide any. They define it as a example session manager and focus on wireplumber. The situation is suboptiomal but the code is already in main as part of pipewire in impish so that's not a regression. We will transition in the futur to wireplumber which has tests but just don't have resources to implement tests for upstream this cycle. - The package does not run an autopkgtest for similar reasons. Also it's a session manager for the pipewire and is dealing with external devices and audio and video content which wouldn't be easy to set up as autopkgtests. - Since there are no tests we will manually test that it's working. We plan to use limited features since pulseaudio is staying our default sound service and we limit the pipewire usage to what is needed for gnome-remote-desktop, which means testing that screen recording and sharing is working under GNOME, under xorg and wayland sessions. + + The testplan is documented on + https://wiki.ubuntu.com/DesktopTeam/TestPlans/PipewireMediaSession [Quality assurance - packaging] - debian/watch is present and works - One lintian warning about the missing manpage # lintian --pedantic W: pipewire-media-session: no-manual-page usr/bin/pipewire-media-session - Lintian overrides are not present - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not use debconf - Packaging and build is easy, link to d/rules https://salsa.debian.org/utopia-team/pipewire-media- session/-/blob/debian/master/debian/rules [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - Owning Team will be desktop-packages - Team is not yet, but will subscribe to the package before promotion - This does not use static builds [Background information] The Package description explains the package well Upstream Name is pipewire-media-session Link to upstream project https://gitlab.freedesktop.org/pipewire/media-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952924 Title: [MIR] pipewire-media-session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1952924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953628] Re: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10
Hi, so to be sure to get it right. This is: slow: BareMetal -> Ubuntu ??.?? -> Virtualbox -> Ubuntu 22.04 fast: BareMetal -> Ubuntu ??.?? -> Virtualbox -> Ubuntu before 22.04 That matches the screenshots, but not the description you gave. So there must be something wrong here - I fail to see in your screenshots where qemu comes into play. Please clarify, until then my answer is based on assumptions. --- Compiz is the compositor and will try to use GPU acceleration features. My gut feeling tells me that either: - the new 22.04 guests wants to use features not present in the virt environment - some part of your stack now fails to present accelerated virtual HW You could experiment with different GPUs configured for the guests and/or different UI acceleration options in the guest. --- Until we know more, incomplete ** Changed in: qemu (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/1953628 Title: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1953628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
