fix: revert to two-step gnome-keyring setup for CI

The combined --unlock --start with 2>/dev/null broke keyring init
entirely ("no result found"). Revert to the original two-step process
but use eval "$()" for robust env var export and add debug logging
to verify GNOME_KEYRING_CONTROL is set.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Mohammod Al Amin Ashik <maa.ashik00@gmail.com>

Author: its-mash

.github/workflows/e2e-desktop.yml

@@ -116,10 +116,13 @@ jobs:
         if: matrix.os == 'ubuntu-latest'
         run: |
           # Start dbus session and unlock gnome-keyring with a dummy password for CI.
-          # Use a single daemon invocation (--unlock + --start) and eval to export
-          # GNOME_KEYRING_CONTROL so the keyring stays unlocked across all test specs.
+          # Two-step process: unlock creates the login keyring, start exports env vars.
+          # Use eval to robustly export GNOME_KEYRING_CONTROL so the keyring stays
+          # accessible across all test specs (avoids "unlock prompt was dismissed").
           dbus-run-session -- bash -c '
-            eval $(echo "test" | gnome-keyring-daemon --unlock --start --components=secrets 2>/dev/null)
+            echo "test" | gnome-keyring-daemon --unlock --components=secrets
+            eval "$(gnome-keyring-daemon --start --components=secrets)"
+            echo "GNOME_KEYRING_CONTROL=$GNOME_KEYRING_CONTROL"
             sleep 1
             xvfb-run --auto-servernum pnpm test:e2e
           '