Keychain initialization encountered an error: libsecret-1.so.0: cannot open shared object file: No such file or directory Using FileKeychain fallback for secure storage.

[craigvphillips]

What happened?

Worked on friday, now i'm receiving this error, changed nothing. Even specifying the version of gemini to 0.34.0 doesn't fix. Get this error and it refuses to use the model i am specifying in the command "--model xxx"

What did you expect to happen?

Work as normal.

Client information

Client Information

Run gemini to enter the interactive CLI, then run the /about command.

> /about
# paste output here

Login information

No response

Anything else we need to know?

No response

[bs76]

The same error here on Linux Mint . I run all in sandbox. When sandbox disabled, gemini updates to 0.35.0 and seems to run ok.

I manually updated the docker image from 0.33.0 to 0.35.0 but behaves the same.
After start, it displays :

Please visit the following URL to authorize the application:

<auth url>

Enter the authorization code:

/about:

╭──────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                              │
│ About Gemini CLI                                                                             │
│                                                                                              │
│ CLI Version                     0.35.0                                                       │
│ Git Commit                      9804bd696                                                    │
│ Model                           Auto (Gemini 3)                                              │
│ Sandbox                         no sandbox                                                   │
│ OS                              linux                                                        │
│ Auth Method                     Signed in with Google ()              │
│ Tier                            ------                     │
│                                                                                              │
╰──────────────────────────────────────────────────────────────────────────────────────────────╯

[ZandercraftGames]

Same error here. Turning off sandbox fixed it for me, so it's definitely something wrong with the sandbox integration.

[tuapuikia]

0.35.0 now will create it own docker network and default is private only (no internet). The temporary fix is

remove the newly created network (no internet)
docker network rm gemini-cli-sandbox

create a new bridge network that will be used by the container

docker network create --driver bridge --subnet XXXXXX --gateway XXXXX gemini-cli-sandbox

you can replace the subnet and gateway based on ur local setup by inspect the network

docker inspect gemini-cli-sandbox

This is the new breaking change

gemini-cli/packages/cli/src/utils/sandbox.ts

Line 465 in 9e7f52b

const isInternal = !config.networkAccess || !!proxyCommand;

[artemy]

Sandbox has a more extensive configuration now and network access is disabled by default. You can enable it like that (in your ~/.gemini/settings.json:

{
    "tools": {
        "sandbox": {
            "enabled": true, // make sure not include this flag too, otherwise the sandbox won't be enabled
            "command": "docker",
            "networkAccess": true
        }
    }
}

[bs76]

I confirm the the ^ from artemy (#23701 (comment)) works ok

How is it going to work (as it does not) when the network is disabled ?

This info is missing in the documentation , had it been there gemini could have informed me (I asked wht 0.35.0 containers did not work)

[galz10]

Hi there, apologies for the bug. We're currently making some updates to our sandboxing, which is why the documentation isn't available just yet. The patch is already included in the latest stable release and is currently rolling out to the preview channel. Please retag me in a comment if you're running into other issues.

[bs76]

Hi there, apologies for the bug. We're currently making some updates to our sandboxing, which is why the documentation isn't available just yet. The patch is already included in the latest stable release and is currently rolling out to the preview channel. Please retag me in a comment if you're running into other issues.

I was able to resolve the issue. I did not search for specifical changes, nor release notes, but I wonder:

do you think it would be possible to have gemini generate a 'breaking changes' portion of release notes and have a link in the gemini-cli tool after upgrade ? I expect the upgrade to pass and IF there are any thing breaking I want to be notified.