search

buttercup / buttercup-browser-extension

:earth_asia: Buttercup browser extension
https://buttercup.pw
MIT License
227 stars 42 forks source link

Arch linux desktop browser connection error #480

Closed JulienRaynal closed 3 months ago

JulienRaynal commented 3 months ago

Hello, I have noted that on my arch linux, when going through the connection pipeline between the browser extension and the desktop application a 403 error appears in the browser extension after entering the connection code. After this I get a 404 error in the browser extension: Failed searching for entries: Background task failed: Desktop request failed: 404 Not Found.

Is it somehow solvable ? Have a great day

perry-mitchell commented 3 months ago

Are you using the latest desktop application version? 2.26.2?

JulienRaynal commented 3 months ago

It seems that the current version on the AUR package is: v2.24.4. Guess I'll have to wait for an upgrade for it to work again with the desktop app. Sorry for the bothering

perry-mitchell commented 3 months ago

Oh.. that's a pity.

I definitely need to familiarise myself with the AUR - I'd like releases there to be automatic and managed by this project, ideally.

No sweat - there's a lot of moving parts to this..

heberuriegas commented 3 months ago

I have 2.26.3 installed from the AppImage and have the same error in Arch linux in firefox

Failed starting connection: Background task failed: NetworkError when attempting to fetch resource.

heberuriegas commented 3 months ago

Ok I did solve it by enable the browser access in the desktop application

Connection -> Enable browser access

Oxalin commented 3 months ago

I was willing to help with this issue, but I'm glad it has been solved.

And yes, the buttercup-desktop package has not been updated yet (I flagged it as being outdated no later than yesterday).

Also, from the three buttercup-desktop packages available [bin|git], it is the only one that is correctly integrated for handling the buttercup protocol.

Maybe the extension error should be more "human understandable" or propose to look at the desktop application setting.

perry-mitchell commented 3 months ago

Agree on the error message. Perhaps we should link to the most up to date AUR item if we don't already.

Oxalin commented 3 months ago

Perhaps we should link to the most up to date AUR item if we don't already.

We already do, we link to the package where it is always the latest version unless it hasn't been updated by the maintainer. The maintainer just need to update the package (PKGBUILD and .SRCINFO) and Arch users should be good to update/use the latest version.

perry-mitchell commented 3 months ago

Couldn't this be setup as a pipeline though? So when desktop is published the AUR copy is updated automatically?

Oxalin commented 3 months ago

Not in a direct way that I know of...

However, if you were to be the maintainer of the said package, you could change the PKGBUILD file (change the latest version in the file), build/test the package (makepkg takes care of it for you according to the PKGBUILD file), update the .SRCINFO file (makepkg --printsrcinfo > .SRCINFO), commit PKGBUILD and .SRCINFO changes and push it in AUR, that would work.

perry-mitchell commented 3 months ago

Thanks for the info. Might have to try that some day.

It strikes me as strange that it's not automatic however. I don't see a reason why such a process should be manual. The build/test phase can be done by a pipeline (action) imo.

perry-mitchell commented 3 months ago

I'm going to close this for now. It's not relevant to the browser extension - it's more to do with the desktop app's AUR support.