-
Notifications
You must be signed in to change notification settings - Fork 43
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
Cannot see games in bottles #268
Comments
Same for me, actually it never found Bottles games. |
If you go in and rename the Program in bottles, does it appear then? That worked for me, I just added a letter scanned with Boilr and it was found. The removed the letter, rescanned and it found it with the original name. |
This works however its tedious to do each time. I hope this issue gets fixed. |
I have a strong feeling that this is a bottles CLI issue and not a BoilR one, with the symptoms you describe. To test it (in case someone gets time before me, which is very likely currently) you have to do the following:
|
It worked, but it's still an issue 🤕 |
I have the exact same issue; Steam Deck on the latest stable OS, Boilr and Bottles from Discover, a couple pieces of software installed in Bottles and Boilr only sees the apps after a rename. |
I've been able to get around this by renaming the game, it seems like if BoilR doesn't know what it is it just gets ignored. |
I have a bottle with Ubisoft Connect, AC Valhalla and Trackmania. I did run
So you were right, it looks like there is an issue on Bottles' side. |
I have opened a bug report with the bottle devs, hopefully they can solve it. I am going to close this issue since it is not related to BoilR. |
Describe the bug
It knows that bottles is installed, however it fails to locate anything
To Reproduce
Start BoilR thru flatpak or standalone executable
Expected behavior
Detect games installed thru Bottles
Screenshots
Desktop (please complete the following information):
Steam Deck, latest flatpak version of Bottles, latest version of BoilR (tried both flatpak and standalone)
Additional context
none
The text was updated successfully, but these errors were encountered: