-
Notifications
You must be signed in to change notification settings - Fork 19
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
Flatpak: am2r crashes on startup #46
Comments
Hmm, opening the shortcut directly should not open the launcher. |
I tried and it crashed. I just dumped the whole terminal output in a textfile.
|
Thanks, will need to check later on my deck to see whether i can repro. The game itself crashes and I'm not quite sure why. |
Yes, looking back I realize my description is bad. I apologize. |
Just out of curiosity, in Discover, have you made sure that you have everything updated? |
Everyday, it's part of my routine :) |
Cool, just wanted to make sure that a partial upgrade didn't somehow happen. |
Hm, would this show when fetching updates in Discover? |
Not that I'm aware of. It's possible to partial update in Discover tho IIRC by only selecting and then updating that one specific application. Since flatpak applications often depend on other dependencies, this could lead to them not working correctly. Do wanna say on that note that I never tried to do partial updates, so maybe discover is just smart enough and automatically updates the dependencies of a flatpak application. I just thought i'd try this simple thing first cause I havent done any updates to the flatpak in a while and it works fine on my main PC, so there's either something specific about your setup, or the general steam deck setup. |
I misunderstood, I thought you meant an update can crash leaving an individual flatpak only partially updated. I always update all flatpaks anyway. |
@benstor214 Why did you close this? Is this not happening for you anymore? |
Still the same. AM2R will not run on the steam deck. I just don't think that I can provide enough information to find the root of the issue. |
Gotcha For what it's worth, I tested it on my Deck, and I have no issues there :/ |
At this moment I suspect it is because how I set up my deck. |
I tried to run this file in konsole and I got this: /home/deck/.var/app/io.github.am2r_community_developers.AM2RLauncher/data/AM2RLauncher/Profiles/Community Updates (Latest)/runner: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory |
@BluesM18A1 I can't see your message now here, but I've gotten an email notification about it - the issue you're having is #33 . It was fixed in dev commits, and has been backported to flatpak releases only for now. @benstor214 can you post the full log please, and does it differ from the one you showed here? |
Yeah I almost immediately after sending that reply here, I figured that out so it was deleted. Funny how the email notification stuck though. |
Sure! Which command would that be? I just right-clicked on the runner file to execute it in terminal. |
See the comment here: #46 (comment) |
Not much, just a few values for gamepad and screen P.S. I changed the title of the issue to a much shorter and less passiv-aggressiv one :)
|
Okay so no difference, it still crashes trying to initialize graphics. |
Where can I find the .appimage? I'd like to test it. |
There is no .appimage for flatpak builds. |
I'm getting the same issue, using both Flatpak and the AUR packages. I've attached the output file to this comment. System info: |
Describe the bug
The same behavior as described in the previously, already closed issue. But the workaround of creating a desktop shortcut under mod settings and launching the just created .desktop file does not solve the issues. Instead the Launcher just minimizes and unminimizes without launching the game.
Expected behavior
The game should launch.
To Reproduce
Steps to reproduce the behavior:
Platform
AM2RLauncher.log
EDIT: The .desktop shortcut just makes the game window show up only to close again after a second or two.
The text was updated successfully, but these errors were encountered: