Stuck in 99% when "generating retroarch path units..."

[enagonius]

After creating a rclone.config file on Windows 10 and putting it on /easyroms/backup/rclone/ on my ArkOS device (a R36S running https://github.com/AeolusUX/ArkOS-R3XS/releases/tag/ArkOS.V2.0.07312024) and then running a script containing the .sh install commands, I try to start Cloud Settings on it, but when it starts doing its first run procedures, it gets stuck in 99% while "generating retroarch path units..."

[ridgekuhn]

Hello, I'm sorry you're having issues. I'm not sure if it's related, but there is currently an issue in the install script where it's unable to install rclone due to rclone changing their download URL, and that user mentioned they also experienced a problem with path unit generation. I apologize, the manual solution for that particular issue is simple, but fixing it in the project would be a little more involved because I need to do some extra work to make sure it won't happen again and take care of a few other things. Please see here for that solution, hopefully it also fixes your issue: https://github.com/ridgekuhn/arklone-retropie/issues/3#issuecomment-2201448323 After that, try running the "regenerate retroarch units" command from the main menu, and please feel free to update me on how it goes

[enagonius]

Thanks for letting me know of that other (possibly related) issue. I have ran the uninstall script and I was waiting for a solution to try again. So should I run the normal install script and then run the other script you linked on that other thread?

[enagonius]

Okay, I tried running that code as script (by adding #!/bin/bash to the start of it and, even though it didn't show anything on screen besides the blinking _ on the terminal screen, I think it worked because now I'm facing a different error:

But I do have a remote file called rclone.conf set up to access my Google Drive both on /easyroms/backup/rclone/ and in /home/ark/.config/.rclone/

[enagonius]

Tried again from scratch: uninstalled Arklone with the uninstall script and deleted rclone.conf from both the backup and .config folders. Then I put the rclone.conf remote file on backup and installed Arklone and then rclone (with this fix you linked) but the 99% problem persists.

[enagonius]

Tried the same as above but inverting the steps: doing the Arklone install first and then the rclone install fix, but the issue persists. I don't know how else to try it.

[ridgekuhn]

So sorry. Maybe it's a bug where the UI isn't getting updated. What happens if you save and run this script? (You may need to run with sudo or it will prompt you for your password)

#!/bin/bash

source "/opt/arklone/src/config.sh"
source "${ARKLONE[installDir]}/src/systemd/scripts/functions/deletePathUnits.sh"

deletePathUnits "$(find "${ARKLONE[unitsDir]}/arkloned-retroarch"*".auto.path")"

. "${ARKLONE[installDir]}/src/systemd/scripts/generate-retroarch-units.sh"

[enagonius]

Unfortunately, when I run the script, the command line shows that it's indeed cleaning up old paths and generating them again, but as soon as I open Cloud Settings, Arklone runs as if it's the first time again and starts generating paths once more, which leads to the eternal 99% problem again.

[ridgekuhn]

Ah, okay, almost there, hopefully! You can bypass the first-run screen by editing the Arklone config and setting remote to the name of your preferred rclone remote:

~/.config/arklone/arklone.cfg:

remote = "dropbox"

[enagonius]

I appreciate your attention and help! Sadly, it also didn't work: I went to the file and modified the line to remote = "drive", since I have configured my rclone.conf file with a token for my Google Drive account, but when I try to run Cloud Settings again I get stuck on a terminal screen with a blinking _

It's like Arklone doesn't have a main menu here. It gets stuck in 99% on the first-run session, and, if I skip it while generating paths with a script and selecting my remote on the .cfg file, it doesn't know where to go next.

[enagonius]

I also tried setting it to remote = "remote" but the issue persists.

[enagonius]

For reference, this is my rclone.conf file (which is in both the backup folder in easyroms and in rclone folder in .config):

And my arklone.cfg file:

[ridgekuhn]

Oh, no... I'm so sorry, but I'm not sure if I can address this. Which handheld is this, one of PowKiddy's models? I have an Anbernic RG351P, which ArkOS hasn't supported in years, so I can't test anything on newer builds, which is why there are so many issues piling up here on GitHub. Arklone changes how ArkOS handles shell redirection for launching util scripts from EmulationStation because ArkOS does not attach the scripts to a tty by default, which caused input or display issues like this one. Thinking about that other issue I linked earlier, and now this, Arklone may not be compatible at all with how the newer ArkOS builds handle shell scripts, and may even break EmulationStation's ability to launch other util scripts. 😩

[enagonius]

This model is a R36S, which is a clone of the Powkiddy RGB205, which is a clone of the RG351MP, which is a clone of the Odroid Go Advance. I'm using the most recent community maintained image of ArkOS: https://github.com/AeolusUX/ArkOS-R3XS/releases/tag/ArkOS.V2.0.07312024

I was afraid that would be the answer :/ I imagined Arklone might have stopped following ArkOS and it's not compatible anymore. Guess I'll have to do it without syncing my saves.

Thanks again for all the help and support. And good job!

[ridgekuhn]

Sorry again! Please keep this issue open so others with the same device might be able to find it. I don't know anything about it, but I've heard people mention SyncThing often in recent years, maybe it could be the answer?