GNOME Shell crashing on Fedora 38 (LInux) After 100's of ssh sessions through keyring

You can find the 1Password logs at $HOME/.config/1Password/logs. What may also be useful is to enable SSH agent diagnostics by running mkdir $HOME/.config/1Password/ssh-diagnostics. This will log each SSH request made to the agent.

Is there a certain pattern that triggers this behavior?

I’ll check out the logs. I think I did create that folder a bit ago. The notes I saw about doing so didn’t say much about what to expect after that.

I’m not sure what sort of pattern you mean. The jobs have been running for years using pubkeys. It wasn’t until I began using using the identity agent that this behavior began.

In looking at the messages log, I did see DBus errors, which is likely to have resulted in the GNOME shell crash. I think I also saw messages suggesting that letting May have been complaining about memory secure memory issues. My guess would be a cascading effect of a process not responding to messages.

I wasn’t really sure why keyring there would be involved because ssh is configured to talk to the 1Password socket directly, so those may have been normal messages that Ives’s just noticing kow.

I’ll have a look at the 1Password logs and see what they have.

The ssh-diagnostics folder I created a while ago has literally nothing in it. Is this wiped on each application launch? What causes things to drop in here? I have the messages log from the last time I dug around in there, so I'll try re-locating and pulling out the messages I made reference to here. Not sure what smoking gun I need to look for or if indeed it might not be a 1Password issue at all. I only know that the behavior began after I started using the ssh-agent.