[Bug 2065932] [NEW] Only adds the weak key for PPAs dual-signed with both weak and strong keys
Public bug reported: After running ‘add-apt-repository ppa:git-core/ppa’ on Ubuntu 24.04, ‘apt update’ gives this warning: W: https://ppa.launchpadcontent.net/git- core/ppa/ubuntu/dists/noble/InRelease: Signature by key E1DD270288B4E6030699E45FA1715D88E1DF1F24 uses weak algorithm (rsa1024) But this PPA is dual-signed by two keys, only one of which is weak. add-apt-repository has chosen to install the rsa1024 key in sources.list.d. It should choose the rsa4096 key instead. $ curl 'https://ppa.launchpadcontent.net/git-core/ppa/ubuntu/dists/noble/InRelease' | gpg … gpg: Signature made Thu 16 May 2024 05:22:18 AM PDT gpg:using RSA key F911AB184317630C59970973E363C90F8F1B6217 gpg: Good signature from "Launchpad PPA for Ubuntu Git Maintainers" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: F911 AB18 4317 630C 5997 0973 E363 C90F 8F1B 6217 gpg: Signature made Thu 16 May 2024 05:22:18 AM PDT gpg:using RSA key E1DD270288B4E6030699E45FA1715D88E1DF1F24 gpg: Good signature from "Launchpad PPA for Ubuntu Git Maintainers" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E1DD 2702 88B4 E603 0699 E45F A171 5D88 E1DF 1F24 $ gpg --list-keys F911AB184317630C59970973E363C90F8F1B6217 E1DD270288B4E6030699E45FA1715D88E1DF1F24 pub rsa1024 2009-01-22 [SC] E1DD270288B4E6030699E45FA1715D88E1DF1F24 uid [ unknown] Launchpad PPA for Ubuntu Git Maintainers pub rsa4096 2024-04-24 [SC] F911AB184317630C59970973E363C90F8F1B6217 uid [ unknown] Launchpad PPA for Ubuntu Git Maintainers Context: https://discourse.ubuntu.com/t/new-requirements-for-apt- repository-signing-in-24-04/42854 ** Affects: software-properties (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/2065932 Title: Only adds the weak key for PPAs dual-signed with both weak and strong keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2065932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056706] Re: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0"
This bug is still present in the 24.04 Beta with 6.8.0-22 kernel. VM is unusable on Xen/XCP-NG. Will the fix be in the final relase on the 25th? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056706 Title: System unstable, kernel ring buffer flooded with "BUG: Bad page state in process swapper/0" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059723] Re: Please delete libmagic1 1:5.45-2 from the archive (in favor of libmagic1t64 1:5.45-3)
Seems resolved. ** Changed in: file (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/2059723 Title: Please delete libmagic1 1:5.45-2 from the archive (in favor of libmagic1t64 1:5.45-3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/2059723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059723] Re: Please delete libmagic1 1:5.45-2 from the archive (in favor of libmagic1t64 1:5.45-3)
Same problem is back now that 1:5.45-3build1 is uploaded and 1:5.45-2 still isn’t deleted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059723 Title: Please delete libmagic1 1:5.45-2 from the archive (in favor of libmagic1t64 1:5.45-3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/2059723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059723] Re: Please delete libmagic1 1:5.45-2 from the archive (in favor of libmagic1t64 1:5.45-3)
It seems like 1:5.45-3 was deleted instead of 1:5.45-2? That resolves the immediate issue, I guess, but it’s probably not the intended resolution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059723 Title: Please delete libmagic1 1:5.45-2 from the archive (in favor of libmagic1t64 1:5.45-3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/2059723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059723] [NEW] Please delete libmagic1 1:5.45-2 from the archive (in favor of libmagic1t64 1:5.45-3)
Public bug reported: As part of the 64-bit time_t transition, libmagic1 was renamed to libmagic1t64 in https://bugs.debian.org/1063113. However, libmagic1 1:5.45-2 is still in the archive, despite being non-installable: # apt-get install libmagic1 Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libmagic1 : Depends: libmagic-mgc (= 1:5.45-2) but 1:5.45-3 is to be installed E: Unable to correct problems, you have held broken packages. Please delete libmagic1 from the archive, so that libmagic1t64 1:5.45-3 can take over this role (it’s already marked Provides: libmagic1 (= 1:5.45-3)). ** Affects: file (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/2059723 Title: Please delete libmagic1 1:5.45-2 from the archive (in favor of libmagic1t64 1:5.45-3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/2059723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964763] Re: QtChooser doesn't support qt6
There also needs to be a default.conf, to avoid having to set QT_SELECT -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964763 Title: QtChooser doesn't support qt6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1964763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971034] Re: Several security issues in libpod 3.4.x
Which "latest binaries from github" ? Upstream only releases source code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971034 Title: Several security issues in libpod 3.4.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/1971034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting
Sorry for the late response. From what I can see we don't really implement any dependency chain when configuring NFS/Kerberos on Ubuntu. We haven't seen this issue in earlier releases of Ubuntu (20.04 and earlier) though. But seems like the process worked differently at that point since /etc/nfs.conf didn't exist. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971935 Title: Invalid pipefs-directory prevents rpc-gssd.service from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1971935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972108] Re: Git packages should have better title for description
Debian policy is very clear that the the description title is not expected to include the package name: https://www.debian.org/doc/debian-policy/ch-binary.html#the-single-line- synopsis “Do not include the package name in the synopsis line.” See https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/655998 for the longstanding update-manager issue about how these are displayed. ** Changed in: git (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972108 Title: Git packages should have better title for description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1972108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting
I can add more information on Monday when I'm working again. I suspect we found this issue because it was manually developed/tested to ensure that everything works. That is without going through the normal provisioning chain. As part of our provisioning chain one step is usually to restart the system (at least when the system is initially provisioned). From that perspective it would not be an issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971935 Title: Invalid pipefs-directory prevents rpc-gssd.service from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1971935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting
We're using Puppet to configure our systems and one of the steps is to ensure gss-rpcd.service is up and running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971935 Title: Invalid pipefs-directory prevents rpc-gssd.service from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1971935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting
Hello, You're correct. The use-case is to mount Kerberos secured NFS mount points. All other configuration is working as expected since after a reboot (as mentioned earlier) the system in question is able to successfully mount with krb5. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971935 Title: Invalid pipefs-directory prevents rpc-gssd.service from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1971935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting
After restarting the system /run/rpc_pipefs exists because /run/systemd/generator/run-rpc_pipefs.mount is created and rpc-gssd works correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971935 Title: Invalid pipefs-directory prevents rpc-gssd.service from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1971935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971935] Re: Invalid pipefs-directory prevents rpc-gssd.service from starting
** Description changed: Ubuntu 22.04 Server + Package version: 1:2.6.1-1ubuntu1 Package nfs-common/nfs-utils provides /etc/nfs.conf and /lib/systemd/system/rpc-gssd.service. /etc/nfs.conf (and seems to be copied from /usr/share/nfs-common/conffiles/nfs.conf) has the configuration: ... [general] pipefs-directory=/run/rpc_pipefs ... When attempting to start rpc-gssd it gives the following error: ... ERROR: opendir(/run/rpc_pipefs) failed: No such file or directory ... There is a systemd unit called var-lib-nfs-rpc_pipefs.mount which mounts this directory as /var/lib/nfs/rpc_pipefs. However this does not match with the configuration in nfs.conf It's worth mentioning that sometimes it seems a systemd unit is generated (run-rpc_pipefs.mount) which ensures /run/rpc_pipefs is created and everything works as expected. Seems to be random. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971935 Title: Invalid pipefs-directory prevents rpc-gssd.service from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1971935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971935] [NEW] Invalid pipefs-directory prevents rpc-gssd.service from starting
Public bug reported: Ubuntu 22.04 Server Package nfs-common/nfs-utils provides /etc/nfs.conf and /lib/systemd/system/rpc-gssd.service. /etc/nfs.conf (and seems to be copied from /usr/share/nfs-common/conffiles/nfs.conf) has the configuration: ... [general] pipefs-directory=/run/rpc_pipefs ... When attempting to start rpc-gssd it gives the following error: ... ERROR: opendir(/run/rpc_pipefs) failed: No such file or directory ... There is a systemd unit called var-lib-nfs-rpc_pipefs.mount which mounts this directory as /var/lib/nfs/rpc_pipefs. However this does not match with the configuration in nfs.conf It's worth mentioning that sometimes it seems a systemd unit is generated (run-rpc_pipefs.mount) which ensures /run/rpc_pipefs is created and everything works as expected. Seems to be random. ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Description changed: - Package nfs-common/nfs-utils provides /etc/nfs.conf and /lib/systemd/system/rpc-gssd.service. + Ubuntu 22.04 Server + + Package nfs-common/nfs-utils provides /etc/nfs.conf and /lib/systemd/system/rpc-gssd.service. /etc/nfs.conf (and seems to be copied from /usr/share/nfs-common/conffiles/nfs.conf) has the configuration: ... [general] pipefs-directory=/run/rpc_pipefs ... - When attempting to start rpc-gssd it gives the following error: ... ERROR: opendir(/run/rpc_pipefs) failed: No such file or directory ... There is a systemd unit called var-lib-nfs-rpc_pipefs.mount which mounts this directory as /var/lib/nfs/rpc_pipefs. However this does not match with the configuration in nfs.conf It's worth mentioning that sometimes it seems a systemd unit is generated (run-rpc_pipefs.mount) which ensures /run/rpc_pipefs is created and everything works as expected. Seems to be random. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971935 Title: Invalid pipefs-directory prevents rpc-gssd.service from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1971935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969939] Re: puppet 5 package incompatible with ruby 3 / ubuntu 22.04
** Bug watch added: Debian Bug tracker #1009643 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009643 ** Also affects: puppet (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009643 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969939 Title: puppet 5 package incompatible with ruby 3 / ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1969939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968203] Re: Setting a symbolic link via puppet doesn't work on Ubuntu22
*** This bug is a duplicate of bug 1969939 *** https://bugs.launchpad.net/bugs/1969939 ** Also affects: puppet (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009643 Importance: Unknown Status: Unknown ** This bug has been marked a duplicate of bug 1969939 puppet 5 package incompatible with ruby 3 / ubuntu 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968203 Title: Setting a symbolic link via puppet doesn't work on Ubuntu22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1968203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968405] Re: yaru-theme-gnome-shell fails to install ["/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new": No such file or directory]
Can confirm that this indeed worked :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968405 Title: yaru-theme-gnome-shell fails to install ["/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg- new": No such file or directory] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1968405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968405] Re: File missing in package?
Just to confirm a few things; Downloaded the .deb source file and checked. It contains the .svg-file in two locations: root@instant:/usr/src/yaru-theme-22.04.3.1# find ./ -iname "calendar-today-light.svg*" ./gnome-shell/src/calendar-today-light.svg ./gnome-shell/upstream/theme/calendar-today-light.svg After doing a local rebuild, strangely enough, the file is listed when doing a file listing of the .deb: root@instant:/usr/src# dpkg --contents yaru-theme-gnome-shell_22.04.3.1_all.deb |grep Yaru/gnome-shell/calendar-today-light.svg -rw-r--r-- root/root 197 2022-03-28 23:58 ./usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg The installation however still gives the same error as reported: root@instant:/usr/src# dpkg -i yaru-theme-gnome-shell_22.04.3.1_all.deb (Reading database ... 378365 files and directories currently installed.) Preparing to unpack yaru-theme-gnome-shell_22.04.3.1_all.deb ... Unpacking yaru-theme-gnome-shell (22.04.3.1) over (20.04.11.1) ... dpkg: error processing archive yaru-theme-gnome-shell_22.04.3.1_all.deb (--install): unable to open '/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new': No such file or directory Errors were encountered while processing: yaru-theme-gnome-shell_22.04.3.1_all.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968405 Title: File missing in package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1968405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962791] Re: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip
Fixed in 3.10.2-7 in jammy-proposed. ** Changed in: python3.10 (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962791 Title: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964288] Re: Upgrade podman packages to v3.23 or above
This was the bug report, of the original issue: https://github.com/containers/podman/issues/10914 ``` $ podman --remote build -t example/dev testbuild STEP 1: FROM docker.io/ubuntu Trying to pull docker.io/library/ubuntu:latest... Getting image source signatures Copying blob sha256:7c3b88808835aa80f1ef7f03083c5ae781d0f44e644537cd72de4ce6c5e62e00 Copying config sha256:2b4cba85892afc2ad8ce258a8e3d9daa4a1626ba380677cee93ef2338da442ab Writing manifest to image destination Storing signatures STEP 2: RUN true STEP 3: COMMIT example/dev --> 17e670d137c Successfully tagged localhost/example/dev:latest 17e670d137ccab35aaacfbc49fa45aa94c6bcc25e56f630298c2ae84e4156e2d $ podman --remote run -it --rm example/dev bash Trying to pull localhost/example/dev:latest... Error: Error initializing source docker://localhost/example/dev:latest: error pinging docker registry localhost: Get "https://localhost/v2/": dial tcp 127.0.0.1:443: connect: connection refused ``` podman/impish,now 3.2.1+ds1-2ubuntu3 amd64 [installed] ** Bug watch added: github.com/containers/podman/issues #10914 https://github.com/containers/podman/issues/10914 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964288 Title: Upgrade podman packages to v3.23 or above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/1964288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960608] Re: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10
This new sysconfig-debian-schemes.diff has broken virtual environments (venv and virtualenv). Please take a look at the fix in https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960608 Title: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/automake-1.16/+bug/1960608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953301] Re: Segfault on AArch64 caused by OpenSSL affecting numerous packages
*** This bug is a duplicate of bug 1951279 *** https://bugs.launchpad.net/bugs/1951279 ** This bug has been marked a duplicate of bug 1951279 OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953301 Title: Segfault on AArch64 caused by OpenSSL affecting numerous packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1953301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962791] Re: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip
sysconfig-debian-schemes.patch uses an incorrect test for a virtual environment: if 'real_prefix' in sys.__dict__ or 'VIRTUAL_ENV' in os.environ: Both sys.real_prefix and VIRTUAL_ENV are only set by virtualenv, not venv, and then only when the virtualenv is activated by VENV_ROOT/bin/activate, not when VENV_ROOT/bin/python is launched directly by its path. This patch corrects the test to if sys.base_prefix != sys.prefix: which works on Python ≥ 3.3. (Also submitted to https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1006707.) ** Patch added: "python3.10_3.10.2-5_venv.debdiff" https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791/+attachment/5566147/+files/python3.10_3.10.2-5_venv.debdiff ** Tags added: patch patch-forwarded-debian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962791 Title: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962791] Re: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip
** Tags added: jammy testcase -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962791 Title: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962791] Re: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip
** Bug watch added: Debian Bug tracker #1006707 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006707 ** Also affects: python3.10 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006707 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962791 Title: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962791] Re: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip
Trying virtualenv instead of venv, it installs pip to the right path, but if you use it to install other packages before activating the virtualenv, their binaries end up in the wrong path. Ubuntu 21.10: # apt update; apt install python3-virtualenv # virtualenv /tmp/my-virtualenv # /tmp/my-virtualenv/bin/pip install black # . /tmp/my-virtualenv/bin/activate # type black black is /tmp/my-virtualenv/bin/black # black --version black, 22.1.0 (compiled: yes) Ubuntu 22.04: # apt update; apt install python3-virtualenv # virtualenv /tmp/my-virtualenv # /tmp/my-virtualenv/bin/pip install black # . /tmp/my-virtualenv/bin/activate # type black bash: type: black: not found # black --version bash: black: command not found # ls /tmp/my-virtualenv/local/bin black black-primer blackd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962791 Title: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962791] [NEW] python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip
Public bug reported: python3 -m venv worked correctly in Ubuntu 21.10: # apt update; apt install python3.10-venv # python3.10 -m venv /tmp/my-venv # . /tmp/my-venv/bin/activate # type pip pip is /tmp/my-venv/bin/pip # pip --version pip 20.3.4 from /tmp/my-venv/lib/python3.10/site-packages/pip (python 3.10) But in Ubuntu 22.04, it installs pip to the wrong path: # apt update; apt install python3.10-venv # python3.10 -m venv /tmp/my-venv # . /tmp/my-venv/bin/activate # type pip bash: type: pip: not found # pip --version bash: pip: command not found # echo $PATH /tmp/my-venv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin # ls /tmp/my-venv/bin Activate.ps1 activate.csh python python3.10 activate activate.fish python3 # ls /tmp/my-venv/local/bin pip pip3 pip3.10 ** Affects: python3.10 (Ubuntu) Importance: Undecided Status: New ** Tags: regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962791 Title: python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 47958] Re: ssh-agent clobbers LD_LIBRARY_PATH and other environment variables
** Changed in: openssh (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/47958 Title: ssh-agent clobbers LD_LIBRARY_PATH and other environment variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/47958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
Any news on this one? I can boot the Ubuntu Jammy desktop using acpi=force and install the desktop. However, on subsequent boots it hangs with the same error in spite of the changed grub config. Also, shutdown does not work at all. Ubuntu just hangs silently. This is on VMware Fusion (latest tech preview) on a Mac Mini 2020 M1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951279] Re: OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds
Here’s a debdiff with the two-line upstream fix. ** Patch added: "openssl_1.1.1f-1ubuntu2.10_lp1951279.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1951279/+attachment/5559328/+files/openssl_1.1.1f-1ubuntu2.10_lp1951279.debdiff ** Tags added: focal patch patch-accepted-upstream regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951279 Title: OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1951279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951279] Re: OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds
David Hess’s analysis is correct. This is a bug in the ARM64 assembly for Poly1305, introduced in https://github.com/openssl/openssl/commit/2cf7fd698ec1375421f91338ff8a44e7da5238b6 (OpenSSL_1_1_1b~37) and fixed upstream in https://github.com/openssl/openssl/commit/5795acffd8706e1cb584284ee5bb3a30986d0e75 (OpenSSL_1_1_1i~21). This fix needs to be backported to focal. ** Changed in: openssl (Ubuntu) Status: Incomplete => Confirmed ** Bug watch added: github.com/openssl/openssl/issues #13256 https://github.com/openssl/openssl/issues/13256 ** Also affects: openssl via https://github.com/openssl/openssl/issues/13256 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #989604 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989604 ** Also affects: openssl (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989604 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951279 Title: OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1951279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956831] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Thank you Brian for getting back. The problem was indeed that /boot was full - after cleaning it up manually the upgrade went through. Since I know that /boot is a problem with updates, I did clean it before doing the upgrade, but apparently not enough. The installation was done long ago (7 years according to the status dump) and I think it was from a bootable USB stick with online download of packages. I've never made a reinstall for these years - just upgraded multiple times. To me, this problem is solved and it the ticket can be closed. When I looked it up I found multiple similar bug reports, but for older versions. So I did send in the auto-report to inform that it occurs in this version too and hope it could help with clues on what causes the crash to the upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956831 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1956831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956831] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Happened during do-release-upgrade. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18 Uname: Linux 4.15.0-166-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jan 8 18:54:36 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-10-04 (2288 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-01-08 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956831 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1956831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990982] Re: [Multiarch] libfreetype6-dev:i386 dependencies issue
6 years later, I'm encountering the same issue in Ubuntu 18.04. sudo apt install libfreetype6-dev:i386 [...] The following packages have unmet dependencies: libfreetype6-dev:i386 : Depends: libc6-dev:i386 but it is not going to be installed or libc-dev:i386 Depends: zlib1g-dev:i386 but it is not going to be installed or libz-dev:i386 Depends: libpng-dev:i386 but it is not going to be installed E: Unable to correct problems, you have held broken packages. And then, for the linux-libc-dev:i386 dependency: sudo apt install linux-libc-dev:i386 [...] The following packages will be REMOVED: build-essential g++ g++-7 gcc-7-multilib gcc-multilib libc6-dev libc6-dev-i386 libc6-dev-x32 libfreetype6-dev libpng-dev libstdc++-7-dev linux-libc-dev zlib1g-dev The following NEW packages will be installed: linux-libc-dev:i386 I echo kenorb's sentiment: is there a workaround to install the 32-bit FreeType libraries? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990982 Title: [Multiarch] libfreetype6-dev:i386 dependencies issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/990982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940723] Re: shim-signed fails to install if grub disk config is incorrect
We "solved" it by reinstalling grub. I.e. export DEBIAN_FRONTEND=noninteractive apt-get purge grub\* -y --allow-remove-essential apt-get install grub-efi -y apt-get autoremove -y update-grub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940723 Title: shim-signed fails to install if grub disk config is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940723] Re: shim-signed fails to install if grub disk config is incorrect
More context: cat /boot/grub/device.map cat: /boot/grub/device.map: No such file or directory sudo debconf-show grub-pc | grep grub-pc/install_devices grub-pc/install_devices_failed: false grub-pc/install_devices_failed_upgrade: true * grub-pc/install_devices_empty: false grub-pc/install_devices_disks_changed: * grub-pc/install_devices: /dev/disk/by-id/scsi-14d534654202020206b732779d9c8429f997bc9f57f0b9212 ls -l /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 Aug 18 11:36 ata-Virtual_CD -> ../../sr0 lrwxrwxrwx 1 root root 9 Aug 18 11:36 scsi-3600224800de237bbe8e76773044489a1 -> ../../sdc lrwxrwxrwx 1 root root 9 Aug 18 11:36 scsi-360022480400bb6ba207caad0981cbca9 -> ../../sdb lrwxrwxrwx 1 root root 10 Aug 18 11:36 scsi-360022480400bb6ba207caad0981cbca9-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Aug 18 11:36 scsi-3600224806b732779d9c8c9f57f0b9212 -> ../../sda lrwxrwxrwx 1 root root 10 Aug 18 11:36 scsi-3600224806b732779d9c8c9f57f0b9212-part1 -> ../../sda1 lrwxrwxrwx 1 root root 11 Aug 18 11:36 scsi-3600224806b732779d9c8c9f57f0b9212-part14 -> ../../sda14 lrwxrwxrwx 1 root root 11 Aug 18 11:36 scsi-3600224806b732779d9c8c9f57f0b9212-part15 -> ../../sda15 lrwxrwxrwx 1 root root 9 Aug 18 11:36 wwn-0x600224800de237bbe8e76773044489a1 -> ../../sdc lrwxrwxrwx 1 root root 9 Aug 18 11:36 wwn-0x60022480400bb6ba207caad0981cbca9 -> ../../sdb lrwxrwxrwx 1 root root 10 Aug 18 11:36 wwn-0x60022480400bb6ba207caad0981cbca9-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Aug 18 11:36 wwn-0x600224806b732779d9c8c9f57f0b9212 -> ../../sda lrwxrwxrwx 1 root root 10 Aug 18 11:36 wwn-0x600224806b732779d9c8c9f57f0b9212-part1 -> ../../sda1 lrwxrwxrwx 1 root root 11 Aug 18 11:36 wwn-0x600224806b732779d9c8c9f57f0b9212-part14 -> ../../sda14 lrwxrwxrwx 1 root root 11 Aug 18 11:36 wwn-0x600224806b732779d9c8c9f57f0b9212-part15 -> ../../sda15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940723 Title: shim-signed fails to install if grub disk config is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940723] Re: shim-signed fails to install if grub disk config is incorrect
No -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940723 Title: shim-signed fails to install if grub disk config is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940723] Re: shim-signed fails to install if grub disk config is incorrect
We are using the "rest" api. Storage profiles look something like:
{
"imageReference": {
"publisher": "canonical",
"offer": "0001-com-ubuntu-server-focal",
"sku": "20_04-lts",
"version": "latest"
},
"osDisk": {
"name": "yadayada-os",
"managedDisk": {
"storageAccountType": "Standard_LRS"
},
"caching": "ReadWrite",
"createOption": "fromImage",
},
"dataDisks": [
{
"name": "yadayada-data1",
"diskSizeGB": 8,
"lun": 0,
"managedDisk": {
"storageAccountType": "StandardSSD_LRS"
},
"caching": "ReadOnly",
"createOption": "empty"
}
]
}
Data disk storageAccountType can also be "Premium_LRS", Disk size varies
up between 4, 8, 128, 256, 512 and 1024.
We are configuring the data disk like this:
mkfs.xfs -f /dev/sdc
mkdir -p /var/lib/rabbitmq
uuid=$(blkid -s UUID -o value /dev/sdc)
echo "UUID=$uuid /var/lib/rabbitmq xfs defaults,noatime 0 0" >> /etc/fstab
mount -a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940723
Title:
shim-signed fails to install if grub disk config is incorrect
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940723/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940723] Re: shim-signed fails to install if grub disk config is incorrect
Great! Standard_B1ms Standard_B1s Standard_D16as_v4 Standard_D2as_v4 Standard_D8as_v4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940723 Title: shim-signed fails to install if grub disk config is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940723] Re: shim-signed fails to install if grub disk config is incorrect
We are only seeing it on Azure, but other cloud providers Ubuntu images don't come with shim-signed so that's why I though we could remove it. lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 55.5M 1 loop /snap/core18/2074 loop2 7:20 32.3M 1 loop /snap/snapd/12398 sda 8:00 4G 0 disk /var/lib/rabbitmq sdb 8:16 030G 0 disk ├─sdb18:17 0 29.9G 0 part / ├─sdb14 8:30 0 4M 0 part └─sdb15 8:31 0 106M 0 part /boot/efi sdc 8:32 0 4G 0 disk └─sdc18:33 0 4G 0 part /mnt sr0 11:01 638K 0 rom zram0 252:00 229.2M 0 disk [SWAP] /etc/fstab # CLOUD_IMG: This file was created/modified by the Cloud Image build process UUID=7339cdbb-1045-46fc-99df-ed81a4d0b313 /ext4 defaults,discard0 1 UUID=BD61-C33D /boot/efi vfatumask=0077 0 1 /dev/disk/cloud/azure_resource-part1/mntauto defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig 0 2 UUID=face62a9-e9d1-40a2-b94b-d18497d7423d /var/lib/rabbitmq xfs defaults,noatime 0 0 /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=hidden GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940723 Title: shim-signed fails to install if grub disk config is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940723] Re: shim-signed fails to install if grub disk config is incorrect
Ok, seemed like some Microsoft thing I don't need. But ok, to bad I have to do that on ~500 vms. How come this is only an issue on Azure Ubuntu vms? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940723 Title: shim-signed fails to install if grub disk config is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940723] Re: shim-signed fails to install if grub disk config is incorrect
Is it safe to remove shim-signed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940723 Title: shim-signed fails to install if grub disk config is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940981] Re: Value in glitchpeg.desktop, "Comment", divided into two lines
The issue are also reported in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990007#5 /Jackson ** Bug watch added: Debian Bug tracker #990007 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990007 ** Description changed: The value of the key "Comment" in /usr/share/applications/screensavers/glitchpeg.desktop is divided into - to lines, like this: + two lines, like this: Comment=Loads an image, corrupts it, and then displays the corrupted version, several times a second. After a while, finds a new image to corrupt. Written by Jamie Zawinski; 2018. It should be one single line, without a line break after "version,", or there will be an error report when installing the desktop file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940981 Title: Value in glitchpeg.desktop, "Comment", divided into two lines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1940981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940981] [NEW] Value in glitchpeg.desktop, "Comment", divided into two lines
Public bug reported: The value of the key "Comment" in /usr/share/applications/screensavers/glitchpeg.desktop is divided into to lines, like this: Comment=Loads an image, corrupts it, and then displays the corrupted version, several times a second. After a while, finds a new image to corrupt. Written by Jamie Zawinski; 2018. It should be one single line, without a line break after "version,", or there will be an error report when installing the desktop file. ** Affects: xscreensaver (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/1940981 Title: Value in glitchpeg.desktop, "Comment", divided into two lines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1940981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940588] Re: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 32
*** This bug is a duplicate of bug 1940723 *** https://bugs.launchpad.net/bugs/1940723 @parviafore We are using latest ubuntu 20.04 (Ubuntu 20.04.3 LTS (GNU/Linux 5.8.0-1039-azure x86_64)) URN: "Canonical:0001-com-ubuntu-server-focal:20_04-lts:20.04.202107200" cat /etc/cloud/build.info build_name: server serial: 20210720 Grub config is system default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940588 Title: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1940588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940769] [NEW] zfs initramfs and encrypted volume compatibility
Public bug reported: I wanted to combine zfs encryption with dropbear and remote unlock. 1. I installed dropbear-initramfs and set that up. That works no problem. 2. I boot up the machine, connect via ssh no problem. 3. I am able to do zfs load-key rpool no problem. 4. Then... I need to kill the plymouth ask-for-password 3 times in a row so it runs out of retries - and then it boots just fine. I'm a little bit worried about the reliability of that last step. It works, but I'm, abusing retries in a way I'm fairly sure they weren't intended to be used.. I'd love a zfs-unlock script or something like that that combines the zfs load-key with a signal to the decrypt_fs function that it can unblock and keep going. But maybe at least in that function stick in some logic for "if the pool has been decrypted in the background, stop retrying"? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfs-initramfs 0.8.3-1ubuntu12.12 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Aug 22 13:50:39 2021 InstallationDate: Installed on 2019-08-15 (738 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: zfs-linux UpgradeStatus: Upgraded to focal on 2020-04-22 (486 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962 ** Affects: zfs-linux (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/1940769 Title: zfs initramfs and encrypted volume compatibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1940769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940588] Re: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 32
We are seeing this error on unattended-upgrades on all Azure ubuntu 20.04 VMs. Preconfiguring packages ... (Reading database ... 58945 files and directories currently installed.) Preparing to unpack .../shim_15.4-0ubuntu9_amd64.deb ... Unpacking shim (15.4-0ubuntu9) over (15+1533136590.3beb971-0ubuntu1) ... Preparing to unpack .../shim-signed_1.40.7+15.4-0ubuntu9_amd64.deb ... Unpacking shim-signed (1.40.7+15.4-0ubuntu9) over (1.40.3+15+1533136590.3beb971-0ubuntu1) ... Setting up shim (15.4-0ubuntu9) ... Setting up shim-signed (1.40.7+15.4-0ubuntu9) ... mount: /var/lib/grub/esp: special device /dev/disk/by-id/scsi-14d534654202020206b732779d9c8429f997bc9f57f0b9212-part15 does not exist. dpkg: error processing package shim-signed (--configure): installed shim-signed package post-installation script subprocess returned error exit status 32 Errors were encountered while processing: shim-signed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940588 Title: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1940588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
This is the only way i managed to speed up my "Trackpoint" on HP ZBOOK 15u G6 to a acceptable level. user1@lab1-w:~$ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ALP0017:00 044E:121C Mouseid=11 [slave pointer (2)] ⎜ ↳ ALP0017:00 044E:121C Touchpad id=12 [slave pointer (2)] ⎜ ↳ PS/2 Generic Mouseid=15 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS GlidePoint id=16 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ HP HD Camera: HP HD Cameraid=10 [slave keyboard (3)] ↳ ALP0017:00 044E:121C UNKNOWN id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ HP Wireless hotkeys id=17 [slave keyboard (3)] ↳ HP WMI hotkeysid=18 [slave keyboard (3)] user1@lab1-w:~$ xinput --list-props 15 Device 'PS/2 Generic Mouse': Device Enabled (180): 1 Coordinate Transformation Matrix (182): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 0.20 libinput Natural Scrolling Enabled (317): 1 libinput Natural Scrolling Enabled Default (318): 0 libinput Scroll Methods Available (319):0, 0, 1 libinput Scroll Method Enabled (320): 0, 0, 1 libinput Scroll Method Enabled Default (321): 0, 0, 1 libinput Button Scrolling Button (322): 2 libinput Button Scrolling Button Default (323): 2 libinput Middle Emulation Enabled (346):0 libinput Middle Emulation Enabled Default (347):0 libinput Accel Speed (324): 1.00 libinput Accel Speed Default (325): 0.00 libinput Accel Profiles Available (326):1, 1 libinput Accel Profile Enabled (327): 1, 0 libinput Accel Profile Enabled Default (328): 1, 0 libinput Left Handed Enabled (329): 0 libinput Left Handed Enabled Default (330): 0 libinput Send Events Modes Available (302): 1, 0 libinput Send Events Mode Enabled (303):0, 0 libinput Send Events Mode Enabled Default (304):0, 0 Device Node (305): "/dev/input/event8" Device Product ID (306):2, 1 libinput Drag Lock Buttons (331): libinput Horizontal Scroll Enabled (332): 1 user1@lab1-w:~$ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ALP0017:00 044E:121C Mouseid=11 [slave pointer (2)] ⎜ ↳ ALP0017:00 044E:121C Touchpad id=12 [slave pointer (2)] ⎜ ↳ PS/2 Generic Mouseid=15 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS GlidePoint id=16 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ HP HD Camera: HP HD Cameraid=10 [slave keyboard (3)] ↳ ALP0017:00 044E:121C UNKNOWN id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ HP Wireless hotkeys id=17 [slave keyboard (3)] ↳ HP WMI hotkeysid=18 [slave keyboard (3)] user1@lab1-w:~$ xinput --list-props 15 Device 'PS/2 Generic Mouse': Device Enabled (180): 1 Coordinate Transformation Matrix (182): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 0.20 libinput Natural Scrolling Enabled (317): 1 libinput Natural Scrolling Enabled Default (318): 0 libinput Scroll Methods Available (319):0, 0, 1 libinput Scroll Method Enabled (320): 0, 0, 1 libinput Scroll Method Enabled Default (321): 0, 0, 1 libinput Button Scrolling Button (322): 2 libinput
[Bug 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
20.04 still has this problem. I'm on a HP Zbook 15u G6. It seems that xinput only can handle values of max 1, which in my case is all to slow. user1@lab1-w:~$ xinput --list-props 11 Device 'ALP0017:00 044E:121C Mouse': Device Enabled (180): 1 Coordinate Transformation Matrix (182): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Natural Scrolling Enabled (317): 1 libinput Natural Scrolling Enabled Default (318): 0 libinput Scroll Methods Available (319):0, 0, 1 libinput Scroll Method Enabled (320): 0, 0, 1 libinput Scroll Method Enabled Default (321): 0, 0, 1 libinput Button Scrolling Button (322): 3 libinput Button Scrolling Button Default (323): 3 libinput Accel Speed (324): 1.00 libinput Accel Speed Default (325): 0.00 libinput Accel Profiles Available (326):1, 1 libinput Accel Profile Enabled (327): 1, 0 libinput Accel Profile Enabled Default (328): 1, 0 libinput Left Handed Enabled (329): 0 libinput Left Handed Enabled Default (330): 0 libinput Send Events Modes Available (302): 1, 0 libinput Send Events Mode Enabled (303):0, 0 libinput Send Events Mode Enabled Default (304):0, 0 Device Node (305): "/dev/input/event7" Device Product ID (306):1102, 4636 libinput Drag Lock Buttons (331): libinput Horizontal Scroll Enabled (332): 1 user1@lab1-w:~$ xinput --set-prop 11 324 1.1 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 131 (XInputExtension) Minor opcode of failed request: 57 () Value in failed request: 0x144 Serial number of failed request: 20 Current serial number in output stream: 21 user1@lab1-w:~$ xinput --set-prop 11 324 2 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 131 (XInputExtension) Minor opcode of failed request: 57 () Value in failed request: 0x144 Serial number of failed request: 20 Current serial number in output stream: 21 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682193 Title: Mouse acceleration significantly reduced after upgrade to 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924937] [NEW] Can't update to 20.04 lts
Public bug reported: Crashes when trying to update to 20.04 lts ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Apr 18 23:43:04 2021 InstallationDate: Installed on 2017-12-11 (1224 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-04-18 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade 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/1924937 Title: Can't update to 20.04 lts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881747] Re: cephadm does not work with zfs root
** Also affects: zfs-linux (Arch Linux) 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/1881747 Title: cephadm does not work with zfs root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916950] Re: [amdgpu] Screen fails to wake up after sleep using 5.4.0-66, but 5.4.0-65 works
Everything was working fine for me up until I created this bug. I checked dpkg logs + my reboot times and it's when I booted from 5.4.0-65 to 5.4.0-66 that this broke. So this adds up nicely -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916950 Title: [amdgpu] Screen fails to wake up after sleep using 5.4.0-66, but 5.4.0-65 works To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1916950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916950] Re: [amdgpu] Screen fails to wake up after sleep
Based on the latest comment in https://gitlab.freedesktop.org/drm/amd/-/issues/1427 it looks like this got reverted in 5.4.88, which is presumably why this works for me in HWE? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916950 Title: [amdgpu] Screen fails to wake up after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1916950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916950] Re: [amdgpu] Screen fails to wake up after sleep
Switching to linux-image-generic-hwe-20.04 seems to have solved the problem - but I don't think it immediately showed up. Will report back if I run into the issue again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916950 Title: [amdgpu] Screen fails to wake up after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1916950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916950] [NEW] Screen fails to wake up after sleep
Public bug reported: It looks an awful lot like this issue : https://gitlab.freedesktop.org/drm/amd/-/issues/1427. I'm hitting these: [11596.268677] [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* dce112_get_pix_clk_dividers: Invalid parameters!! [11596.269781] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state failed with -22 Switching to tty2 wakes it up and allows me to switch back and recover my xorg session. Should this be filed against the kernel, xorg, or amd drivers? I'm not sure.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu Feb 25 21:07:28 2021 DistUpgraded: 2020-04-22 17:41:41,681 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-64-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed zfs, 0.8.3, 5.4.0-65-generic, x86_64: installed zfs, 0.8.3, 5.4.0-66-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701] InstallationDate: Installed on 2019-08-15 (560 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-66-generic root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash amd_iommu=on iommu=pt video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset usbhid.quirks=0x1b1c:0x1b44:0x2408 usbcore.quirks=1b1c:1b44:gn crashkernel=384M vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-22 (309 days ago) dmi.bios.date: 02/17/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33c dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33c:bd02/17/2021:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal kubuntu ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916950 Title: Screen fails to wake up after sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1916950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1913639] Re: linux-crashdump is not capable of mounting zfs root pools
Hi Sorry about the lack of reply on this, I had some hardware issues with this setup and I've been waiting for the time to have a proper go at fixing it. Unfortunately I failed at that yesterday. This machine no longer boots, so it's hard for me to get the output.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913639 Title: linux-crashdump is not capable of mounting zfs root pools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913639] Re: linux-crashdump is not capable of mounting zfs root pools
I did a dmesg picture attachment in the previous update. Do you need more of that output? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913639 Title: linux-crashdump is not capable of mounting zfs root pools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913639] Re: linux-crashdump is not capable of mounting zfs root pools
So I got the ps2 adapter and... it looks like this has nothing to do with ZFS. I have 4 SATA drives in this machine. sda - ST2000DM001-1ER1 - zpool storage sdb - ST2000DM008-2FR1 - zpool storage sdc - Samsung SSD 860 - my main drive. zpool rpool and bpool. sdd - Samsung SSD 850 - windows - used with vfio + qemu. (This is also where my kernel commandline arguments are coming from, isolating one gpu and a usb controller. The iommu groups are clean and only contains the gpu+usb controller, nothing else). When in the crashkernel, I can see: sda and sdb. Which now translates into the Samsung ssd 850 and one of the storage pool drives. So half of my storage pool and the windows drive. The 2 other sata drives are not there. And I see a lot of errors for ata5.00: failed to IDENTIFY (I/O error, err_mask=0x100) The motherboard is a MSI X99A SLI PLUS. I'm.. happy with closing this issue at this point. If there's anything quick I can do to help debug this absolutely. But I feel like this moved from a category of "zfs initrd script needs patching" into "weird motherboard bug" - in a motherboard I'm planning to replace anyway. ** Attachment added: "picture of whats going on" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+attachment/5461871/+files/full-log.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913639 Title: linux-crashdump is not capable of mounting zfs root pools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913639] Re: linux-crashdump is not capable of mounting zfs root pools
A : I can confirm that debug was there, and the output on the console is different. However, plugging in the keyboard again didn't work, regardless of usb port on the machine, and I can't get a response on ssh either (or pinging the machine for that matter). Any ideas? I've attached a photo of what happens... which is surprisingly different? No errors, just dumps me on the initramfs prompt. Ref getting usb working there is no output on the console whatsoever if I replug the keyboard. B : I've attached these. C : I realize I had from previous debugging already ran with crashkernel=2096M-:2096M, so I don't think it's a memory issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913639 Title: linux-crashdump is not capable of mounting zfs root pools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913639] Re: linux-crashdump is not capable of mounting zfs root pools
I also just spend 5$ to order a usb to ps2 adapter, that should make it a bit easier to figure out what's going on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913639 Title: linux-crashdump is not capable of mounting zfs root pools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913639] Re: linux-crashdump is not capable of mounting zfs root pools
** Attachment added: "initramfs.debug" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+attachment/5460762/+files/initramfs.debug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913639 Title: linux-crashdump is not capable of mounting zfs root pools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913639] Re: linux-crashdump is not capable of mounting zfs root pools
** Attachment added: "20210206_125923.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+attachment/5460761/+files/20210206_125923.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913639 Title: linux-crashdump is not capable of mounting zfs root pools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913639] Re: linux-crashdump is not capable of mounting zfs root pools
** Attachment added: "regular_initrd.out" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+attachment/5460764/+files/regular_initrd.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913639 Title: linux-crashdump is not capable of mounting zfs root pools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913639] Re: linux-crashdump is not capable of mounting zfs root pools
** Attachment added: "kdump_initrd.out" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+attachment/5460763/+files/kdump_initrd.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913639 Title: linux-crashdump is not capable of mounting zfs root pools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913639] Re: linux-crashdump is not capable of mounting zfs root pools
That made my kdump initrd grow from 46mb to 86mb. However, it still fails. An additional complication here is that kdump does something with my usb keyboard so I can't actually write anything when I get to the initramfs prompt... So it's a bit hard to debug what's going on. my zpool/rpool setup looks like this: ``` pool: bpool state: ONLINE scan: scrub repaired 0B in 0 days 00:00:04 with 0 errors on Sun Jan 10 00:24:05 2021 config: NAMESTATE READ WRITE CKSUM bpool ONLINE 0 0 0 sdc1 ONLINE 0 0 0 errors: No known data errors pool: rpool state: ONLINE scan: scrub repaired 0B in 0 days 00:18:34 with 0 errors on Sun Jan 10 00:42:35 2021 config: NAMESTATE READ WRITE CKSUM rpool ONLINE 0 0 0 sdc2 ONLINE 0 0 0 ``` sdc is just a standard sata drive, so it should just work out of the box with any fairly recent kernel, I haven't needed any non standard changes for that drive in many many kernels. Can I easily modify the initrd that's built into this initrd and add some debug info to stdout somehow? ** Attachment added: ""screenshot"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+attachment/5458267/+files/20210130_122038.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913639 Title: linux-crashdump is not capable of mounting zfs root pools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913639] [NEW] linux-crashdump is not capable of mounting zfs root pools
Public bug reported: I could not get any crash logs after using this package. I tried using it and triggering a crash from a terminal. The alternate kernel boots successfully, but the initrd for linux-crashdump is not capable of loading my rpool. running: linux-crashdump:amd64 5.4.0.64.67 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-crashdump:amd64 (not installed) ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 28 20:15:19 2021 InstallationDate: Installed on 2019-08-15 (532 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: MSI MS-7885 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-65-generic root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash intel_iommu=on iommu=pt vfio-pci.ids=10de:1b81,10de:10f0,1b21:1242 video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset crashkernel=2096M-:2096M vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-65-generic N/A linux-backports-modules-5.4.0-65-generic N/A linux-firmware1.187.8 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-22 (281 days ago) dmi.bios.date: 06/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E0 dmi.board.asset.tag: Default string dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E0:bd06/15/2018:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7885 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913639 Title: linux-crashdump is not capable of mounting zfs root pools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1913639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897848] Re: package xtables-addons-dkms 3.8-2 failed to install/upgrade: installed xtables-addons-dkms package post-installation script subprocess returned error exit status 7
*** This bug is a duplicate of bug 1907109 *** https://bugs.launchpad.net/bugs/1907109 ** This bug has been marked a duplicate of bug 1907109 xtables-addons 3.0-0.1ubuntu4/3.8-2ubuntu0.1 fails to build with linux 5.4.0-57.63 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897848 Title: package xtables-addons-dkms 3.8-2 failed to install/upgrade: installed xtables-addons-dkms package post-installation script subprocess returned error exit status 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1897848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912468] Re: OpenAFS emergency release 1.8.7
The patches are in 1.8.6-5, currently in hirsuite-proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912468 Title: OpenAFS emergency release 1.8.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1912468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897848] Re: package xtables-addons-dkms 3.8-2 failed to install/upgrade: installed xtables-addons-dkms package post-installation script subprocess returned error exit status 7
With kernel 5.10 the netfilter API was slightly modified. This change was backported to the stable kernels (including 5.4) thereby breaking xtables-addons-dkms. The API change is really very simple; the enclosed patch contains the change that were made to upstream xtables-addons from version 3.8 to 3.12 ** Patch added: "Update to kernel API 5.10" https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1897848/+attachment/5452382/+files/0002-kernel-5.10-support.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897848 Title: package xtables-addons-dkms 3.8-2 failed to install/upgrade: installed xtables-addons-dkms package post-installation script subprocess returned error exit status 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1897848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897848] Re: package xtables-addons-dkms 3.8-2 failed to install/upgrade: installed xtables-addons-dkms package post-installation script subprocess returned error exit status 7
A netfilter modification from 5.10 was backported to all stable kernels including 5.4 xtables-addons must be updated to 3.12 (or later) to match this change! @MikeR: Kernel 5.8 is obsolete - that is the reason the modification did not make it into that kernel... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897848 Title: package xtables-addons-dkms 3.8-2 failed to install/upgrade: installed xtables-addons-dkms package post-installation script subprocess returned error exit status 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1897848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838771] Re: http:Fix Host header in proxied https connections
** Bug watch added: Debian Bug tracker #977930 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977930 ** Also affects: apt (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977930 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838771 Title: http:Fix Host header in proxied https connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1838771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901406] Re: Lenovo T490 extremely show with Ubuntu 20.20 running kernel 5.8
I have the same problem but on a Lenovo ThinkPad P43s (Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901406 Title: Lenovo T490 extremely show with Ubuntu 20.20 running kernel 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902243] Re: init-system-helpers pre-depends bionic
(Closing since the PPA is not part of Ubuntu.) To use the PPA on bionic, you need to have the bionic-backports repository enabled (it should be enabled by default, see https://help.ubuntu.com/community/UbuntuBackports#Enabling_Backports) and run `apt install init-system-helpers/bionic-backports`. I’ll add a note about this to the PPA description. ** Changed in: openafs (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902243 Title: init-system-helpers pre-depends bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1902243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902169] [NEW] Sync openafs 1.8.6-4 (universe) from Debian unstable (main)
Public bug reported: Please sync openafs 1.8.6-4 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Import upstream 5.8 FTBFS fixes * Import upstream 5.8 FTBFS fixes These patches were added to Debian in 1.8.6-3. Changelog entries since current hirsute version 1.8.6-1ubuntu1: openafs (1.8.6-4) unstable; urgency=medium * Bump Standards-Version to 4.5.0 (no changes needed) * Pull in upstream patches for linux kernel 5.9 support -- Benjamin Kaduk Sun, 25 Oct 2020 11:28:45 -0700 openafs (1.8.6-3) unstable; urgency=medium * Pull in upstream patches for linux kernel 5.8 support (Closes: #970258) -- Benjamin Kaduk Sat, 19 Sep 2020 15:39:18 -0700 openafs (1.8.6-2) unstable; urgency=medium * Pull in upstream patches for -fcommon support (Closes: #966881) -- Benjamin Kaduk Sun, 30 Aug 2020 19:39:18 -0700 ** Affects: openafs (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/1902169 Title: Sync openafs 1.8.6-4 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1902169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897747] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: do-rleasae-upgrade from 18.04 to 20.04 today. upgrade from 16.04 to 18.04 performed last Sunday on 5 machines. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 29 11:56:41 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2013-11-28 (2496 days ago) InstallationMedia: Ubuntu-Server 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.2) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-09-29 (0 days ago) ** 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/1897747 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1897747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892340] Re: Setting Java Flight Recorder option forces English locale
Can confirm and reproduce using the method described by mr. Kaufmann on Ubuntu, Debian and Centos, so this should probably be pushed upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892340 Title: Setting Java Flight Recorder option forces English locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1892340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1893693] Re: Unable to scroll gnome app list
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893693 Title: Unable to scroll gnome app list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894346] [NEW] Livepatch should not be reported as available in a Docker container
Public bug reported: A Docker container, like an LXD container (bug 1759257), cannot load kernel modules, so it should not report Canonical Livepatch as being available in the motd. $ docker run --rm -it ubuntu:18.04 root@12d1934cc2df:/# apt-get update root@12d1934cc2df:/# apt-get install lsb-release ubuntu-advantage-tools root@12d1934cc2df:/# /etc/cron.daily/ubuntu-advantage-tools root@12d1934cc2df:/# /etc/update-motd.d/80-livepatch * Canonical Livepatch is available for installation. - Reduce system reboots and improve kernel security. Activate at: https://ubuntu.com/livepatch root@12d1934cc2df:/# exit $ docker run --rm -it ubuntu:20.04 root@b9959e2f6ae9:/# apt-get update root@b9959e2f6ae9:/# apt-get install ca-certificates ubuntu-advantage-tools root@b9959e2f6ae9:/# ubuntu-advantage status SERVICE AVAILABLE DESCRIPTION cc-ealno Common Criteria EAL2 Provisioning Packages esm-apps yesUA Apps: Extended Security Maintenance esm-infra yesUA Infra: Extended Security Maintenance fips no NIST-certified FIPS modules fips-updates no Uncertified security updates to FIPS modules livepatch yesCanonical Livepatch service This machine is not attached to a UA subscription. See https://ubuntu.com/advantage ** Affects: ubuntu-advantage-tools (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/1894346 Title: Livepatch should not be reported as available in a Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1894346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893693] [NEW] Unable to scroll gnome app list
Public bug reported: I'm unable to scroll from page 1 to 2 in all apps under the gnome app list. Changing the dock from left side to bottom or right side solves the issue. Ubuntu 20.04 fresh install. See here for same issue: https://askubuntu.com/questions/1241165/should-i-report-show- applications-not-scrolling-as-a-bug ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 22:37:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-22 (39 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893693 Title: Unable to scroll gnome app list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885065] [NEW] i fucking dont know its your shit
Public bug reported: i dont fucking nknow ** Affects: software-properties (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/1885065 Title: i fucking dont know its your shit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1885065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883450] Re: Default HEAD should point at refs/heads/main
This change will need to happen upstream first. Upstream is making progress on it: https://lore.kernel.org/git/pull.656.git.1591823971.gitgitgad...@gmail.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883450 Title: Default HEAD should point at refs/heads/main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1883450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
I assume Rafael added block-proposed mistakenly; there is no staged upload involved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878721 Title: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1878721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
** Tags removed: block-proposed-eoan block-proposed-focal block- proposed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878721 Title: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1878721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
Verified that 1.5.22-2ubuntu0.1 works on focal with the config file in all four locations. ** 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/1878721 Title: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1878721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882407] Re: package openafs-client 1.8.4~pre1-1ubuntu2 failed to install/upgrade: installed openafs-client package post-installation script subprocess returned error exit status 1
Although the openafs-client package happens to include a command named ‘sys’, it’s almost certainly not the one you’re looking for. openafs- client is for connecting to the AFS network filesystem (https://en.wikipedia.org/wiki/Andrew_File_System). What are you trying to do? As for the errors with –f and ––purge, you want -f and --purge instead (with the normal hyphen that you can type on your keyboard, not a Unicode dash character). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882407 Title: package openafs-client 1.8.4~pre1-1ubuntu2 failed to install/upgrade: installed openafs-client package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1882407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
** Description changed: [Impact] memcached 1.5.22 in focal has a bug where it looks for its SASL configuration at /etc/sasl2/memcached.conf/memcached.conf instead of /etc/sasl2/memcached.conf. This causes a memcached setup with authentication that was working in bionic to fail in focal. The bug was introduced upstream in 1.5.7~3: https://github.com/memcached/memcached/commit/39151c870c5e598f039714bdb790bd46f614856e https://github.com/memcached/memcached/pull/366 and fixed upstream in 1.6.0~15: https://github.com/memcached/memcached/commit/6207330c2705fdb5f02de13b99a0d994f7c4f14a [Test Case] apt-get install memcached libmemcached-tools libsasl2-modules sasl2-bin mkdir /etc/sasl2 echo 'mech_list: plain' > /etc/sasl2/memcached.conf echo 'sasldb_path: /etc/sasl2/memcached-sasldb2' >> /etc/sasl2/memcached.conf echo bar | saslpasswd2 -p -f /etc/sasl2/memcached-sasldb2 -a memcached foo chown memcache: /etc/sasl2/memcached-sasldb2 + echo '-S' >> /etc/memcached.conf systemctl restart memcached memcping --servers=127.0.0.1 --binary --username=foo --password=bar Succeeds in bionic (with no output); fails in focal with “Failed to ping 127.0.0.1:11211 UNKNOWN READ FAILURE” or “Failed to ping 127.0.0.1:11211 WRITE FAILURE”; should succeed with the patch. If you want to test alternate locations for the SASL config file, here are all four locations that will now work by default: • /etc/sasl/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should succeed with the patch • /etc/sasl/memcached.conf: succeeds in bionic; fails in focal; should succeed with the patch • /etc/sasl2/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should work with the patch • /etc/sasl2/memcached.conf: succeeds in bionic; fails in focal; should succeed with the patch [Regression Potential] Low risk. The upstream patch is targeted and applies cleanly to 1.5.22. It looks for the SASL configuration at both the incorrect and correct paths, so even in the (unlikely) event that someone worked around this bug by manually creating a configuration file at the incorrect path /etc/sasl2/memcached.conf/memcached.conf, that will continue to be respected. If there were to be a regression, it would likely manifest as an authentication failure, which clients may display as a read or write failure, like the failure mode of the regression being fixed here. ** Description changed: [Impact] memcached 1.5.22 in focal has a bug where it looks for its SASL configuration at /etc/sasl2/memcached.conf/memcached.conf instead of /etc/sasl2/memcached.conf. This causes a memcached setup with authentication that was working in bionic to fail in focal. The bug was introduced upstream in 1.5.7~3: https://github.com/memcached/memcached/commit/39151c870c5e598f039714bdb790bd46f614856e https://github.com/memcached/memcached/pull/366 and fixed upstream in 1.6.0~15: https://github.com/memcached/memcached/commit/6207330c2705fdb5f02de13b99a0d994f7c4f14a [Test Case] apt-get install memcached libmemcached-tools libsasl2-modules sasl2-bin mkdir /etc/sasl2 echo 'mech_list: plain' > /etc/sasl2/memcached.conf echo 'sasldb_path: /etc/sasl2/memcached-sasldb2' >> /etc/sasl2/memcached.conf echo bar | saslpasswd2 -p -f /etc/sasl2/memcached-sasldb2 -a memcached foo chown memcache: /etc/sasl2/memcached-sasldb2 echo '-S' >> /etc/memcached.conf systemctl restart memcached memcping --servers=127.0.0.1 --binary --username=foo --password=bar Succeeds in bionic (with no output); fails in focal with “Failed to ping 127.0.0.1:11211 UNKNOWN READ FAILURE” or “Failed to ping 127.0.0.1:11211 WRITE FAILURE”; should succeed with the patch. If you want to test alternate locations for the SASL config file, here are all four locations that will now work by default: • /etc/sasl/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should succeed with the patch • /etc/sasl/memcached.conf: succeeds in bionic; fails in focal; should succeed with the patch - • /etc/sasl2/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should work with the patch + • /etc/sasl2/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should succeed with the patch • /etc/sasl2/memcached.conf: succeeds in bionic; fails in focal; should succeed with the patch [Regression Potential] Low risk. The upstream patch is targeted and applies cleanly to 1.5.22. It looks for the SASL configuration at both the incorrect and correct paths, so even in the (unlikely) event that someone worked around this bug by manually creating a configuration file at the incorrect path /etc/sasl2/memcached.conf/memcached.conf, that will continue to be respected. If there were to be a regression, it would
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
** Description changed: [Impact] memcached 1.5.22 in focal has a bug where it looks for its SASL configuration at /etc/sasl2/memcached.conf/memcached.conf instead of /etc/sasl2/memcached.conf. This causes a memcached setup with authentication that was working in bionic to fail in focal. The bug was introduced upstream in 1.5.7~3: https://github.com/memcached/memcached/commit/39151c870c5e598f039714bdb790bd46f614856e https://github.com/memcached/memcached/pull/366 and fixed upstream in 1.6.0~15: https://github.com/memcached/memcached/commit/6207330c2705fdb5f02de13b99a0d994f7c4f14a [Test Case] apt-get install memcached libmemcached-tools libsasl2-modules sasl2-bin mkdir /etc/sasl2 echo 'mech_list: plain' > /etc/sasl2/memcached.conf echo 'sasldb_path: /etc/sasl2/memcached-sasldb2' >> /etc/sasl2/memcached.conf echo bar | saslpasswd2 -p -f /etc/sasl2/memcached-sasldb2 -a memcached foo chown memcache: /etc/sasl2/memcached-sasldb2 - echo '-S' >> /etc/memcached.conf systemctl restart memcached memcping --servers=127.0.0.1 --binary --username=foo --password=bar - Works in bionic; fails in focal with “Failed to ping 127.0.0.1:11211 - WRITE FAILURE”. + Succeeds in bionic (with no output); fails in focal with “Failed to ping + 127.0.0.1:11211 UNKNOWN READ FAILURE” or “Failed to ping 127.0.0.1:11211 + WRITE FAILURE”; should succeed with the patch. + + If you want to test alternate locations for the SASL config file, here + are all four locations that will now work by default: + + • /etc/sasl/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should succeed with the patch + • /etc/sasl/memcached.conf: succeeds in bionic; fails in focal; should succeed with the patch + • /etc/sasl2/memcached.conf/memcached.conf: fails in bionic; accidentally succeeds in focal; should work with the patch + • /etc/sasl2/memcached.conf: succeeds in bionic; fails in focal; should succeed with the patch [Regression Potential] Low risk. The upstream patch is targeted and applies cleanly to 1.5.22. - It looks for the SASL configuration at both locations, so if someone - worked around this bug by creating + It looks for the SASL configuration at both the incorrect and correct + paths, so even in the (unlikely) event that someone worked around this + bug by manually creating a configuration file at the incorrect path /etc/sasl2/memcached.conf/memcached.conf, that will continue to be respected. + + If there were to be a regression, it would likely manifest as an + authentication failure, which clients may display as a read or write + failure, like the failure mode of the regression being fixed here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878721 Title: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1878721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
** Description changed: [Impact] memcached 1.5.22 in focal has a bug where it looks for its SASL configuration at /etc/sasl2/memcached.conf/memcached.conf instead of /etc/sasl2/memcached.conf. This causes a memcached setup with authentication that was working in bionic to fail in focal. The bug was introduced upstream in 1.5.7~3: https://github.com/memcached/memcached/commit/39151c870c5e598f039714bdb790bd46f614856e https://github.com/memcached/memcached/pull/366 and fixed upstream in 1.6.0~15: https://github.com/memcached/memcached/commit/6207330c2705fdb5f02de13b99a0d994f7c4f14a [Test Case] apt-get install memcached libmemcached-tools libsasl2-modules sasl2-bin mkdir /etc/sasl2 echo 'mech_list: plain' > /etc/sasl2/memcached.conf echo 'sasldb_path: /etc/sasl2/memcached-sasldb2' >> /etc/sasl2/memcached.conf echo bar | saslpasswd2 -p -f /etc/sasl2/memcached-sasldb2 -a memcached foo chown memcache: /etc/sasl2/memcached-sasldb2 + echo '-S' >> /etc/memcached.conf systemctl restart memcached memcping --servers=127.0.0.1 --binary --username=foo --password=bar Works in bionic; fails in focal with “Failed to ping 127.0.0.1:11211 WRITE FAILURE”. [Regression Potential] Low risk. The upstream patch is targeted and applies cleanly to 1.5.22. It looks for the SASL configuration at both locations, so if someone worked around this bug by creating /etc/sasl2/memcached.conf/memcached.conf, that will continue to be respected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878721 Title: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1878721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
Rafael: I said that bionic is *not* affected, both because bionic has 1.5.6 while the bug was introduced in 1.5.7, and because the test case passes on bionic. What makes you think otherwise? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878721 Title: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1878721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878721] Re: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
Here’s a debdiff with the upstream patch. I built this in https://launchpad.net/~andersk/+archive/ubuntu/ppa and verified it against the test case. ** Patch added: "memcached_1.5.22-2_lp1878721.debdiff" https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1878721/+attachment/5371790/+files/memcached_1.5.22-2_lp1878721.debdiff ** 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/1878721 Title: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1878721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878721] [NEW] memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression)
Public bug reported: [Impact] memcached 1.5.22 in focal has a bug where it looks for its SASL configuration at /etc/sasl2/memcached.conf/memcached.conf instead of /etc/sasl2/memcached.conf. This causes a memcached setup with authentication that was working in bionic to fail in focal. The bug was introduced upstream in 1.5.7~3: https://github.com/memcached/memcached/commit/39151c870c5e598f039714bdb790bd46f614856e https://github.com/memcached/memcached/pull/366 and fixed upstream in 1.6.0~15: https://github.com/memcached/memcached/commit/6207330c2705fdb5f02de13b99a0d994f7c4f14a [Test Case] apt-get install memcached libmemcached-tools libsasl2-modules sasl2-bin mkdir /etc/sasl2 echo 'mech_list: plain' > /etc/sasl2/memcached.conf echo 'sasldb_path: /etc/sasl2/memcached-sasldb2' >> /etc/sasl2/memcached.conf echo bar | saslpasswd2 -p -f /etc/sasl2/memcached-sasldb2 -a memcached foo chown memcache: /etc/sasl2/memcached-sasldb2 systemctl restart memcached memcping --servers=127.0.0.1 --binary --username=foo --password=bar Works in bionic; fails in focal with “Failed to ping 127.0.0.1:11211 WRITE FAILURE”. [Regression Potential] Low risk. The upstream patch is targeted and applies cleanly to 1.5.22. It looks for the SASL configuration at both locations, so if someone worked around this bug by creating /etc/sasl2/memcached.conf/memcached.conf, that will continue to be respected. ** Affects: memcached (Ubuntu) Importance: Undecided Status: New ** Tags: focal patch-accepted-upstream regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878721 Title: memcached looks for SASL configuration at wrong path /etc/sasl2/memcached.conf/memcached.conf (18.04→20.04 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memcached/+bug/1878721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866900] Re: Javascript clipboard does not work
I am now on a fresh install of 20.04 and can confirm that this works. I have a theory: Did github change their copy content from "git clone http" to "http...", I might have been thrown of from the different practices. I am sorry, closing the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866900 Title: Javascript clipboard does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1866900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866900] Re: Javascript clipboard does not work
You're not wrong, I can't say the bug is in Firefox. All I know is I have a problem and that is when i push the copy button on github, gitlab or whatever site that has autocopy to the clipboard, It's not going to my clipboard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866900 Title: Javascript clipboard does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1866900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866900] Re: Javascript clipboard does not work
shift - ins -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866900 Title: Javascript clipboard does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1866900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866900] Re: Javascript clipboard does not work
Can you confirm that you can paste with "shift + i" or "mouse3" ? Ctrl - v seems to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866900 Title: Javascript clipboard does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1866900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866900] Re: Javascript clipboard does not work
I'm, sorry I assumed it was a snap, its the deb:
i.e. https://github.com/micheleg/gnome-shell-extension-cpu-freq
Push Clone or download, and then the clipboard button, now try and paste
it in a terminal (or somewhere else.
Package: firefox
Version: 74.0+build3-0ubuntu1
Priority: optional
Section: web
Origin: Ubuntu
Maintainer: Ubuntu Mozilla Team
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 201 MB
Provides: gnome-www-browser, iceweasel, www-browser
Depends: lsb-release, libatk1.0-0 (>= 1.12.4), libc6 (>= 2.30),
libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.10.0), libdbus-1-3 (>= 1.9.14),
libdbus-glib-1-2 (>= 0.78), libfontconfig1 (>= 2.12.6), libfreetype6 (>=
2.10.1), libgcc-s1 (>= 3.3), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>=
2.31.8), libgtk-3-0 (>= 3.4), libharfbuzz0b (>= 0.6.0), libpango-1.0-0 (>=
1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libpangoft2-1.0-0 (>= 1.14.0),
libstdc++6 (>= 9), libx11-6, libx11-xcb1 (>= 2:1.6.9), libxcb-shm0, libxcb1,
libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1),
libxext6, libxfixes3, libxi6, libxrender1, libxt6
Recommends: xul-ext-ubufox, libcanberra0, libdbusmenu-glib4, libdbusmenu-gtk3-4
Suggests: fonts-lyx
Replaces: kubuntu-firefox-installer
Task: ubuntu-desktop-minimal, ubuntu-desktop, kubuntu-desktop, kubuntu-full,
xubuntu-desktop, lubuntu-desktop, ubuntustudio-desktop, ubuntukylin-desktop,
ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop
Xul-Appid: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
Supported: 9m
Download-Size: 51,6 MB
APT-Manual-Installed: no
APT-Sources: http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
Description: Safe and easy web browser from Mozilla
Firefox delivers safe, easy web browsing. A familiar user interface,
enhanced security features including protection from online identity theft,
and integrated search let you get the most out of the web.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866900
Title:
Javascript clipboard does not work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1866900/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866974] [NEW] The Diffie-Hellman prime sent by the server is not acceptable
Public bug reported: I can no longer connect to my ISP mail server. Works in previous version 19.10 "The reported error was “Failed to get capabilities: Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough).”." I've tried finding a workaround but so far no luck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evolution 3.35.92-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 11:07:01 2020 InstallationDate: Installed on 2020-03-03 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (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/1866974 Title: The Diffie-Hellman prime sent by the server is not acceptable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866900] [NEW] Javascript clipboard does not work
Public bug reported: Pressing the "copy to clipboard" buttons on websites does not work. (e. g. Gitlab / Github) Manual ctrl-c is necessary. (Wrorks in several other browsers on same system) Snap / connection ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anders 2056 F pulseaudio /dev/snd/controlC0: anders 2056 F pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 19:45:10 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-03-03 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=74.0/20200304223017 (Out of date) Profile0 - LastVersion=74.0/20200309095159 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2013 dmi.bios.vendor: LENOVO dmi.bios.version: I1KT24AUS dmi.board.vendor: LENOVO dmi.board.version: 3193 STD dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrI1KT24AUS:bd07/24/2013:svnLENOVO:pn10120:pvrIdeaCentreK450:rvnLENOVO:rn:rvr3193STD:cvnLENOVO:ct3:cvr: dmi.product.family: IdeaCentre dmi.product.name: 10120 dmi.product.sku: LENOVO_MT_1012 dmi.product.version: IdeaCentre K450 dmi.sys.vendor: LENOVO ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866900 Title: Javascript clipboard does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1866900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
