search

Adamcake / Bolt

An alternative launcher for your favourite MMO
GNU Affero General Public License v3.0
122 stars 18 forks source link

Minor bug: unable to launch RuneLite on Fedora 39 after adding a new character on first launch #52

Closed ajaypillay closed 1 week ago

ajaypillay commented 1 week ago

This happened when I did a specific sequence of actions on Fedora 39. I added a new character to my account while the launcher was open and I was logged in, then I closed and re-opened the launcher. When I tried to launch the RuneLite client on my new character, the following error was shown:

Error from https://api.github.com/repos/runelite/launcher/releases: 0:

I tried this on all the characters on my account, and the same error was thrown when attempting to launch RuneLite. HDOS didn't work either (though I didn't record the error message).

Re-launching the client seemed to fix this and RuneLite works now. Just figured I'd report it anyway.

Adamcake commented 1 week ago

The error would suggest you didn't have an Internet connection at the time, or maybe some DNS level outage.

On Thu, 20 Jun 2024, 09:23 Ajay Pillay, @.***> wrote:

This happened when I did a specific sequence of actions on Fedora 39. I added a new character to my account while the launcher was open and I was logged in, then I closed and re-opened the launcher. When I tried to launch the RuneLite client on my new character, the following error was shown:

Error from https://api.github.com/repos/runelite/launcher/releases: 0:

I tried this on all the characters on my account, and the same error was thrown when attempting to launch RuneLite. HDOS didn't work either (though I didn't record the error message).

Re-launching the client seemed to fix this and RuneLite works now. Just figured I'd report it anyway.

— Reply to this email directly, view it on GitHub https://github.com/Adamcake/Bolt/issues/52, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHG6BIC2KBGKXT3NPFMZDVLZIKGQZAVCNFSM6AAAAABJTOJIESVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3DGOBTG42DMOI . You are receiving this because you are subscribed to this thread.Message ID: @.***>

ajaypillay commented 1 week ago

I did have a connection as I was accessing the rest of the Internet via my web browser, and I was also logged in to another character on RS3. I visited the API link as well via my browser to verify that it was accessible too.

Adamcake commented 1 week ago

Possibly a one-time error in flatpak's sandboxing then? "0" in xml means a non-http failure such as a connection timeout or a network failure. It can't really mean anything else.

Let me know if it happens again or you can get it to happen consistently, but currently this sounds very much like a transient one-time occurrence.

On Thu, 20 Jun 2024, 10:00 Ajay Pillay, @.***> wrote:

I did have a connection as I was accessing the rest of the Internet via my web browser, and I was also logged in to another character on RS3. I visited the API link as well via my browser to verify that it was accessible too.

— Reply to this email directly, view it on GitHub https://github.com/Adamcake/Bolt/issues/52#issuecomment-2180176174, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHG6BIEVF6C5XJPHYLKXKDDZIKK4JAVCNFSM6AAAAABJTOJIESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBQGE3TMMJXGQ . You are receiving this because you commented.Message ID: @.***>

ajaypillay commented 1 week ago

Will do. I'll close this issue for now. If I'm able to reproduce it I'll report back. Thanks!