Change:
vikunja-frontend = throw "'vikunja-frontend' has been replaced by 'vikunja'"; # Added 2024-02-19 vimHugeX = vim-full; # Added 2022-12-04 vim_configurable = vim-full; # Added 2022-12-04 <ins> vinegar = throw "'vinegar' was removed due to being blocked by Roblox, rendering the package useless"; # Added 2024-08-23 </ins> virtmanager = throw "'virtmanager' has been renamed to/replaced by 'virt-manager'"; # Converted to throw 2023-09-10 virtmanager-qt = throw "'virtmanager-qt' has been renamed to/replaced by 'virt-manager-qt'"; # Converted to throw 2023-09-10 vivaldi-widevine = throw "'vivaldi-widevine' has been renamed to/replaced by 'widevine-cdm'"; # Added 2023-02-25

Discussion:
The "Studio" option is not working in Vinegar. The application does download, the application does launch. However, once it is open, the window is almost unusable. Steps to reproduce the behavior: vinegar from nixpkgs (unstable) in the terminal the mess in front of your eyes... So, instead of getting the usual Studio look, I see the username, question cicrle, notification bell, and "FILE" buttons (all of the mentioned buttons do work, so I AM able to click on them and get a popup, as well as use the options from there, as well as hover effects). Everything else looks like a badly margined css page. (Replaced the actual username with "username" in the picture below, might not be perfectly aligned, just to make no misconceptions, the button IS properly aligned in the original image!) !
I was able to reproduce this, and I believe is the issue you are getting. The Vinegar wiki states that you need the patch to fix this issue, however the problem is that all the upstream vinegar patches are on an older version of wine (except for the patch which was rebased to 9.0rc2). Currently the Vinegar team is working on porting these patches to 9.0 stable.
I see, thank you. Unless you told me not to, I'll leave the issue until it is resolved (mostly so that people know what's going on, in case they're experiencing it as well).
Also, if you want to test studio out for now, you can get wine-ge from the nix-gaming flake and override the vinegar package with it.
Oh, thank you. I'm not quite sure how to override vinegar's wine though.. Here is what fellas who were nice enough to help me came up with: And it does build. However, when I run , here's the bunch of nonsense I get:
need to also be overriden:
Oh, got it! Thank you

So, whenever I open Player, it starts installing Roblox, finishes, and does nothing. Even when launched from the website, starts installing, finishes, and most likely just exits. Logs show nothing important. However, when trying open Studio, the error saying " not found". Steps to reproduce the behavior: the grapejuice package (just write grapejuice in the with pkgs section) wine-wayland package (not sure if it is required, however I did) Grapejuice (I used rofi (drun), but I suppose $ would work) the message box that pops out (from wine), press "Install" to install the wine-mono thingy press the Open RobloxPlayer button, or go into Player, Initialize and Install Roblox, the behavior is the same Roblox installing and doing nothing... I expected RobloxPlayer to actually open, not install and exit... <!-- --
This is already tracked in issue

When a new version of wine is packaged, the version pointed to by the config () (a store link) becomes invalid. At best, this will use an old wine version, and at worst will cause the app to fail to launch. Steps to reproduce the behavior: old wine initial config () wine The app should not crash. N/A Unsure how Nix should handle this one. The best solution is to update the config file (which conforms to xdg), however that may be out of scope. A warning / doc would also help.
upstream should stop embedding a full path or if there's some valid reason for why they do it then maybe the could grab a new path from $PATH if the current one doesn't exist
It stores it under the key , implying that will be used as a fallback(?) Could open an issue on the grapejuice repo and see what they have to say. Worth noting that regenerating the config file with will resolve the new path and work fine.
ah looks like its our fault which was in i didn't do the update myself so i don't know why the substitution was and if its necessary anymore
you tagged the wrong helium btw
I figured haha. Couldn't determine who it was supposed to be lol. As for the substitution, I'm not sure why it wouldn't update for newer wine builds? Seems kinda weird..
seems grapejuice copies the file to $HOME on first setup so the path won't be changed on wine hash changes
Sure. I think the issue mainly lies with the fact Nix does not edit the resulting config file, but the source itself. Unless Nix prods into XDG config home, there's not much we can do about it.