[Bug 2061167] Re: python3-distutils is not built for noble
Thanks all for the details. Assuming it is safe to be removed and that the new conflict in -proposed will help to do so automatically for users that upgrade, once mainlined. apt autoremove python3-distutils -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061167 Title: python3-distutils is not built for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-stdlib-extensions/+bug/2061167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
I can confirm the behaviour after a recent upgrade from mantic to noble and has also been reported in https://discourse.ubuntu.com/t/noble-dev- branch-why-does-the-keyring-stay-locked-upon-login-also-why-did-apt- install-work-but-apt-upgrade-fail/43979 Another oddity is, that I seem to have to type the password twice into the second, non-overlay password prompt, which has me type my password four times for a complete login. This may also be connected to recent changes about how the ssh-agent is initialised, which may or may not involve problems with the Keyring or the new GCR. (Does anybody know what the abbreviation means? Its readme stays silent about it.) - https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2061288 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2060575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061288] [NEW] Multiple conflicting SSH agents and SSH_AUTH_SOCK not set after upgrade to noble
Public bug reported: After upgrading mantic to noble, there are multiple SSH agents who are independently trying to set SSH_AUTH_SOCK, none of which is successful. 1. ~/.config/autostart/gnome-keyring-ssh.desktop (identical to /etc/xdg/autostart/gnome-keyring-ssh.desktop, if not modified) This will start the regular GNOME Keyring SSH Agent. It will set the Agent location to /run/user/1000/ssh, while the Socket is initialised at /run/user/1000/.ssh 2. If that one is not running, the user unit ssh-agent.service kicks in. It sets the Socket to live at /run/user/1000/openssh_agent 3. Parallely, there is also a GPG agent emulating SSH support gpg-agent- ssh.socket Socket at /run/user/1000/gnupg/S.gpg-agent.ssh 4. There is also the (new?) user unit gcr-ssh-agent.socket It sets its Socket to live at /run/user/1000/gcr/ssh --- The last one seems to be preferred by GNOME upstream nowadays, but also comes with caveats, as its unit does not set the SSH_AUTH_SOCK variable. This commit from !137 (see below) does not seem to be included in /usr/lib/systemd/user/gcr-ssh-agent.socket - https://gitlab.gnome.org/GNOME/gcr/-/commit/b12cc639949c4b548d84625b292a2aff1faaf195 Apparently it's solved upstream with the gcr 4.2.1 release. Installed is 4.2.0-4build1 There are discussions about how this is possibly resolved in - https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/770 closed - https://gitlab.gnome.org/GNOME/gnome-build-meta/-/merge_requests/2623 open - https://gitlab.gnome.org/GNOME/gcr/-/issues/55 closed - https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/137 merged - https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/138 closed - https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/139 reverts 137 Similar regressions around GCR (What does that abbreviation even mean? It's not explained in the readme) are described in the following, including other possible workarounds: - https://www.adamsdesk.com/posts/fix-gnome-keyring-ssh-auth-sock/ - https://bbs.archlinux.org/viewtopic.php?id=292403 ** Affects: gnome-keyring (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/2061288 Title: Multiple conflicting SSH agents and SSH_AUTH_SOCK not set after upgrade to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2061288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061167] [NEW] python3-distutils is not built for noble
Public bug reported: After upgrading to noble, there appears to be a regression between the to-be-installed python3-distutils package and its dependency python3-lib2to3. The old packages from mantic remain installed. python3-distutils Depends on: python3-lib2to3 (= 3.12.2-3ubuntu1.1) Installation candidate: 3.12.2-3ubuntu4 - https://packages.ubuntu.com/noble/python3-distutils dependency version pinned - https://packages.ubuntu.com/noble/python3-lib2to3 version not available - https://launchpad.net/ubuntu/noble/+package/python3-lib2to3 - https://launchpad.net/ubuntu/noble/+package/python3-distutils The published versions and their version requirements just don't match up. It seems no 'binary' distribution distutils is produced in noble: - https://launchpad.net/ubuntu/+source/python3-stdlib-extensions/ See 'Packages built by this source': - https://launchpad.net/ubuntu/+source/python3-stdlib-extensions/3.11.5-1 mantic has distutils - https://launchpad.net/ubuntu/+source/python3-stdlib-extensions/3.12.3-0ubuntu1 noble not - https://launchpad.net/ubuntu/+source/python3-stdlib-extensions/3.12.2-3ubuntu4 yet? Maybe this is because distutils is no longer part of the source package named in the package registry: - https://git.launchpad.net/ubuntu/+source/python3-stdlib-extensions/tree/3.11/Lib - https://git.launchpad.net/ubuntu/+source/python3-stdlib-extensions/tree/3.12/Lib It appears some refactoring is going on, or build errors persist, which might settle sooner or later. ** Affects: python3-stdlib-extensions (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/2061167 Title: python3-distutils is not built for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-stdlib-extensions/+bug/2061167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971427] Re: gdm in jammy defaults to wrong keymap option with no UI for fixing it
Yes, I can second the notion that this seems independent from the two proposed upstream issues, since this has also happened here when upgrading to 22.04. $ sudo cat /etc/default/keyboard XKBLAYOUT="de,us" XKBVARIANT="," BACKSPACE="guess" XKBMODEL="pc105" XKBOPTIONS="grp:alt_caps_toggle,grp_led:scroll" $ sudo cat /var/lib/AccountsService/users/yala [User] Session=ubuntu XSession=ubuntu Icon=/var/lib/AccountsService/icons/yala SystemAccount=false [InputSource0] xkb=de [InputSource1] xkb=us German (de) used to be the primary keymap on this system, but now English (en) is always preselected. This is a pretty nasty change in behaviour, as it blocks the boot up and login flow. jammy 5.15.0-33-generic gdm3 42.0-1ubuntu7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971427 Title: gdm in jammy defaults to wrong keymap option with no UI for fixing it To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1971427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
