Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not working on Ubuntu 24.04.1 / Gnome 46 - neither X11 nor Wayland. #12

Open
zweifeln opened this issue Jan 30, 2025 · 3 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@zweifeln
Copy link

It is not working on Ubuntu 24.04.1 / Gnome 46.
Neither on Wayland (my default) nor on X11.

I installed it through Gnome extensions, logged out and in, rebootet, toggled the extension … it's not showing up.
I assume it should show up under settings => search as an option, but it doesn't.

When searching it is also not popping up.

Is it me or is there some bug? (Any way I can help make it work?)

@MrMarble MrMarble self-assigned this Jan 30, 2025
@MrMarble MrMarble added the bug Something isn't working label Jan 30, 2025
@MrMarble
Copy link
Owner

MrMarble commented Jan 30, 2025

Hi! Thanks for reaching out,
I've only tested the extension in Fedora with Wayland (is what I use), so this might be a bug.

I assume it should show up under settings => search as an option, but it doesn't.

It does not appears as a provider, it just returns the results when you search (registering the provider needs to configure an event bus and other things I haven't done)

Is the extension reporting an error in the installed extensions page? It is a red ERROR message instead of the toggle switch.
You can use "Looking Glass" to see the status of the extensions as well, use alt + F2 and run lg to open the window.

Image

Maybe your version of vscode is not properly detected, you can find the ID of your version in "Looking Glass" as well, open a vscode window and look at the ID in the "Windows" tab

Image

only these are supported (new ones can be added)

const ids = [
"code",
"code-insiders",
"code-oss",
"codium",
"codium-insiders",
"com.vscodium.codium",
"com.vscodium.codium-insiders",

It could be also that the folder holding the configuration is not found, these are the available folders:
const appDirs = [
// XDG_CONFIG_DIRS
"Code",
"Code - Insiders",
"VSCodium",
"VSCodium - Insiders",
// Flatpak
"com.vscodium.codium/config/VSCodium",
"com.vscodium.codium-insiders/config/VSCodium - Insiders",
];

@zweifeln
Copy link
Author

zweifeln commented Feb 1, 2025

Thanks for your reply.

My issue is/was: I was using vscode via snap. So the configuration folder was indeed not found.
I installed vscodium via .deb and it works fine.

(A couple of months ago vscode didn't provide any apt/deb install any more but only snap. It seems they reversed that decision.)

So … it works for me.

Maybe productive outcome of this: do you want to include the snap config direction too?

@MrMarble
Copy link
Owner

MrMarble commented Feb 1, 2025

Glad to know it's fixed!
You can create a pull request adding the new path if you want to contribute, if not, I can do it myself but I'll appreciate if you shared the path so I don't have to install snap :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants