Login Loop issue when using Vinegar within studio

Help and Feedback Platform Usage Support
#1

No matter what method of login I try whether its Email, Normal login, Mobile App etc It still throws the same error.

I have tried opening a place from create.roblox.com and that hadn’t worked either

Vinegar Info:

* Vinegar: v1.7.4 
* Distro: Freedesktop SDK 23.08 (Flatpak runtime)
* Processor: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz
  * Supports AVX: true
  * Supports split lock detection: false
* Kernel: 6.6.9-amd64
* Wine (Player): v9.2 (Staging)
* Wine (Studio): v9.2 (Staging)
* Flatpak: [x]
* Cards:
  * Card 0: i915 0000:00:02.0 /sys/class/drm/card0
2 Likes
#2

This may be now no more true but I think it’s still like that. Even tho I am not a linux user (wine user)

Wine blocked

1 Like
#3

Its not because of wine. They blocked it ONLY on the player not studio.

2 Likes
#4

So you can’t login on roblox studio but you have Roblox open?

#5

I cant login to studio yeah? Can you imply what you mean?

#6

Yeah, sorry just to be sure. You can go to the rapid acess and use it for roblox studio, maybe it will work.

#7

Whats “rapid access”? I have no clue what you’re talking about.

#8

Sorry, I meant quick login, I had to translate by myself as I have it in Italian.

#9

Did you read this? Like I said No matter the login method it still throws an error.

#10

You mentioned 3 things and said: “etc” I was just trying to help, maybe it’s just a Roblox Studio error, or an unsupported, version or OS, still I don’t know.

#11

Its a login error.

I did that to shorten the list as it would be redundant to list every single login method.

#12

Said it just to be sure you tried all.

#13

You could try to contact the Roblox Support. They may know the cause.

#14

Maybe. Going through support is such a pain though so I’m gonna hold off on that for now.

#15

I know, I have experienced that, but in this case it seems the only option.

#17

This sounds a lot like an issue I had in the past called stale wineserver.

you can run flatpak run org.vinegarhq.Vinegar studio kill to see if there is any sort of esync_init that throws a stale wineserver error.

If it is to do with stale wineserver. Here’s the steps I used to solve it:

  1. I uninstalled the flatpak completely.

  2. Remove any instances left. In my case I deleted the org.vinegarhq.Vinegar folder in the ~/.var/app location to be sure there wasn’t any remnant left behind oif the stale wineserver.

  3. Reinstall vinegar flatpak. You can use flathub or install from the flatpakref.

  4. Run the command flatpak run org.vinegarhq.Vinegar -firstrun studio run to go through the updated webview login.

Hopefully this helps. It was annoying to have to figure this out after trying to create an issue about it on vinegarhq github. However I did finally receive enough information to diagnose and fix the problem.

1 Like
#18

Would be great if you stated the error.