Closed dhwalker closed 3 years ago
Thank you for reporting the issue.
Can you please:
~/.ssh/known_hosts
, restart gnome shell, login on this host and try to find the host using gnome shell.journalctl -S '5 minutes ago'
(assuming you've reproduced the problem within the 5 minutes before running journalctl
)ls -la ~/.ssh
Thanks for your quick reply.
I think I wasn't clear about the problem I'm having. The "session" I referred to in my original post is the Gnome session that's running ssh-search-provider, not the ssh session, and I'm searching for a host that's already in my known_hosts. Figuring you though I meant a session with a new ssh host in your instructions to reproduce the problem, here's what I've done instead:
I hope this helps. If you still want me to follow your step 2, let me know.
OK. If I understand your symptoms, you're saying that after logging in a Gnome session, SSH Search Provider isn't able to complete any hosts until it is toggled off and back on.
That is consistent with what I'm seeing in the log files: in journalctl2.txt
I can see that you are performing a search:
journalctl2.txt:Jan 02 15:49:29 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.getInitialResultSet(fi)
journalctl2.txt:Jan 02 15:49:29 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.getInitialResultSet(fi) = 1[fitlet2]
journalctl2.txt:Jan 02 15:49:29 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.filterResults(5)
journalctl2.txt:Jan 02 15:49:29 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.getResultMetas(fitlet2)
journalctl2.txt:Jan 02 15:49:30 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.getSubsearchResultSet(fitl)
journalctl2.txt:Jan 02 15:49:30 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.getSubsearchResultSet(fitl) = 1[fitlet2]
journalctl2.txt:Jan 02 15:49:30 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.filterResults(5)
journalctl2.txt:Jan 02 15:49:30 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.getSubsearchResultSet(fitlet)
journalctl2.txt:Jan 02 15:49:30 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.getSubsearchResultSet(fitlet) = 1[fitlet2]
journalctl2.txt:Jan 02 15:49:30 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.filterResults(5)
journalctl2.txt:Jan 02 15:49:30 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.getSubsearchResultSet(fitlet2)
journalctl2.txt:Jan 02 15:49:30 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.getSubsearchResultSet(fitlet2) = 1[fitlet2]
journalctl2.txt:Jan 02 15:49:30 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.filterResults(5)
journalctl2.txt:Jan 02 15:49:31 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.activateResult(fitlet2)
journalctl2.txt:Jan 02 15:49:31 homelap7 gnome-shell[28940]: Ssh-Search-Provider: SshSearchProvider.activateResult(): cmd=gnome-terminal,--,ssh,fitlet2
However, I don't see any trace of such a search in journalctl.txt
.
This seems to indicate that either:
Gnome-shell is buggy and doesn't pass the search to the SSH Search Provider
or
Can you try to rule out [1] by:
When the problem is occurring, can you open looking glass (ALT-f2 lg
with default keybindings, then type this expression in the javascript console:
var iter=Main.overview.viewSelector._searchResults._providers.values(); var a = []; while(1) { var d = iter.next(); if (d.done) break; a.push(d.value.id); }; a
This will print something like:
r(0) = a-very-long-line
Click on the value (eg. a-very-long-line
in the example above to get it broken down. Your screen should look like this:
Please attach a screenshot, or report if you see ssh-search-provider@extensions.gnome-shell.fifi.org
in the list (in my screenshot, it is the last).
Yes, your understanding of my symptoms is correct.
Disabling all extensions except for SSH Search Provider Reborn didn't change anything. The information from Looking Glass, though, was interesting. If I display that information immediately after logging in, it doesn't show ssh-search-provider@extensions.gnome-shell.fifi.org on the list: After using Tweaks to disable and enable it, though, it's on the list:
The interesting thing is that the pre-disable/enable list has org.gnome.Terminal.desktop at position 12, which is where ssh-search-provider shows up after disable/enable.
I think it may be fixed with the latest release (v8). Would you mind checking?
That did it. Thanks!
David
On 3/25/21 11:52 PM, F-i-f wrote:
I think it may be fixed with the latest release (v8) @.***>. Would you mind checking?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/F-i-f/ssh-search-provider/issues/5#issuecomment-807983562, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABRCDWXR5UQFGINPR66VP2DTFQVLVANCNFSM4VQ4GMYA.
For the record, the fix is to work around a bug in Gnome Shell. But it's working now.
Yeah, I suspected that.
Thanks again!
David
On 3/26/21 11:21 AM, F-i-f wrote:
For the record, the fix is to work around a bug in Gnome Shell. But it's working now.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/F-i-f/ssh-search-provider/issues/5#issuecomment-808426917, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABRCDWUZRCB5JVOYTC4V3Q3TFTGDJANCNFSM4VQ4GMYA.
In Gnome 3.38 / openSUSE Tumbleweed, attempts to find an ssh host after logging into a new session result in only "Searching..." displayed on the screen. Disabling and enabling the extension fixes the problem for the rest of the session; matching ssh hosts are shown on the screen and can be selected.