Hi there,

`man schroot` has the following example in the "Sessions" subsection:
```

       Note that the Session Managed option is set to ‘true’.  This is
       a requirement in order to use session manage‐ ment, and is
       supported by most chroot types.  Next, we will create a new
       session:

       % schroot -b -c sid-snap↵
       sid-snap-46195b04-0893-49bf-beb8-0d4ccc899f0f

       The session ID of the newly-created session is returned on
       standard output.  It is common to store it like this:

       % SESSION=$(schroot -b -c sid-snap)↵
       % echo $SESSION↵
       sid-snap-46195b04-0893-49bf-beb8-0d4ccc899f0f

       The session may be used just like any normal chroot.  This is
       what the session looks like:

       % schroot -i -c sid-snap-46195b04-0893-49bf-beb8-0d4ccc899f0f↵
         ——— Session ———
         Name                   sid-snap-46195b04-0893-49bf-beb8-0d4ccc899f0f
         Description            Debian sid snapshot
         Type                   lvm-snapshot
         Priority               3
[...]
         Mount Location         /var/lib/schroot/mount/sid-snap-46195b04-0893-49bf-beb8-0d4ccc899f0f
         Path                   /var/lib/schroot/mount/sid-snap-46195b04-0893-49bf-beb8-0d4ccc899f0f
```

However, the above example does not work:
```
root@harlock:~# SCHROOT_SESSION_ID="$(schroot -b -c bookworm-amd64-sbuild)"
root@harlock:~# echo "${SCHROOT_SESSION_ID}"
bookworm-amd64-sbuild-638d6de1-c6b8-4fe8-9ce9-a9d0717c7397
root@harlock:~# schroot -i -c "${SCHROOT_SESSION_ID}"
E: bookworm-amd64-sbuild-638d6de1-c6b8-4fe8-9ce9-a9d0717c7397: Chroot not found
root@harlock:~# schroot -l --all
chroot:bookworm-amd64-sbuild
session:bookworm-amd64-sbuild-638d6de1-c6b8-4fe8-9ce9-a9d0717c7397
source:bookworm-amd64-sbuild
root@harlock:~# schroot -r -c "${SCHROOT_SESSION_ID}" -- uname -sr
Linux 6.5.0-0.deb12.4-amd64
root@harlock:~#
```

Thx, bye,
Gismo / Luca