debcrafters-packages team mailing list archive

[Nick Rosbrook <2125549@xxxxxxxxxxxxxxxxxx>]

Okay, I have had some assistance in debugging on Xubuntu 25.04 vs 25.10,
and this is what I have at the moment.

(1) openssh is indeed not a factor for the desktop use case, though ssh-
agent.socket uses the same method for setting the environment, and has
the same drawback

(2) It does not appear that xfce launches applications as transient
systemd user units. To see this, try running the following from a
terminal in a graphical session:

$ systemctl --user status $$

On GNOME, you will see something like:

ubuntu@q-vm:~$ systemctl --user status $$
● ptyxis-spawn-00f46578-4dcb-472e-8bda-8ea66aa37249.scope - [systemd-run] /usr/bin/bash
     Loaded: loaded (/run/user/1000/systemd/transient/ptyxis-spawn-00f46578-4dcb-472e-8bda-8ea66aa37249.scope; transient)
  Transient: yes
     Active: active (running) since Wed 2025-10-01 22:18:25 UTC; 8min ago
 Invocation: 0e1008e4a3964294b70663380994d239
      Tasks: 3 (limit: 3936)
     Memory: 5.6M (peak: 22M)
        CPU: 514ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/ptyxis-spawn-00f46578-4dcb-472e-8bda-8ea66aa37249.scope
             ├─3590 /usr/bin/bash
             ├─3900 systemctl --user status 3590
             └─3901 pager

Oct 01 22:18:25 q-vm systemd[2034]: Started ptyxis-
spawn-00f46578-4dcb-472e-8bda-8ea66aa37249.scope - [systemd-run]
/usr/bin/bash

On xfce (and e.g. an SSH session), you will see:

ubuntu@q-vm:~$ systemctl --user status $$
PID 3860 does not belong to any loaded unit.

(3) So, given that we moved from gnome-keyring to gcr4, my guess is that
gnome-keyring had another method of setting the SSH_AUTH_SOCK variable
in addition to the systemctl --user set-environment call in the socket
unit, and that gcr4 has no such mechanism. I have not verified this, but
setting gcr4 as an affected package based on that idea.

** Changed in: gcr4 (Ubuntu)
    Milestone: None => ubuntu-25.10

** Changed in: gcr4 (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to gcr4 in Ubuntu.
https://bugs.launchpad.net/bugs/2125549

Title:
  ssh agent no longer work a questing upgrade

Status in gcr4 package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  Fix Released
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  ssh agent worked fine in XUbuntu 25.04. After upgrading to 25.10
  (beta) it no longer works.

  * ssh-add reports "Could not open a connection to your authentication agent."
  * ssh keeps asking for key password
  * there is no graphical dialog asking for passwords when adding ssh-keys anymore
  * no SSH variable in terminal environment

  ProblemType: Bug
  DistroRelease: Ubuntu 25.10
  Package: openssh-client 1:10.0p1-5ubuntu4
  ProcVersionSignature: Ubuntu 6.17.0-4.4-generic 6.17.0-rc5
  Uname: Linux 6.17.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.33.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Sep 24 07:58:24 2025
  InstallationDate: Installed on 2017-09-26 (2920 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924)
  RelatedPackageVersions:
   ssh-askpass       N/A
   libpam-ssh        N/A
   keychain          N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_10.0p2 Ubuntu-5ubuntu4, OpenSSL 3.5.2 5 Aug 2025
  SourcePackage: openssh
  UpgradeStatus: Upgraded to questing on 2025-09-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcr4/+bug/2125549/+subscriptions