autofire372 Posted April 25 Posted April 25 I set up a fresh wine prefix for PKHeX only on a new laptop, installed dotnet 10.0.6 into it, and I can't open the Trainer Info tab editing a Gen 5 save. All I get are CultureNotFound exceptions. I tried forcing en-US.UTF-8 using environment variables, but it still won't work.
Taku86 Posted April 25 Author Posted April 25 15 minutes ago, autofire372 said: I set up a fresh wine prefix for PKHeX only on a new laptop, installed dotnet 10.0.6 into it, and I can't open the Trainer Info tab editing a Gen 5 save. All I get are CultureNotFound exceptions. I tried forcing en-US.UTF-8 using environment variables, but it still won't work. I am aware of this. Starting from Wine version 11.5, there is currently a regression due to a new language code added to ICU, which for some reason is not recognized. There is already an open bug tracking this issue, hopefully someone will see and fix it. For now, use version 11.4, which is the latest safe version.
autofire372 Posted April 25 Posted April 25 3 minutes ago, Taku86 said: I am aware of this. Starting from Wine version 11.5, there is currently a regression due to a new language code added to ICU, which for some reason is not recognized. There is already an open bug tracking this issue, hopefully someone will see and fix it. For now, use version 11.4, which is the latest safe version. No can do; I'm on an Arch-based distro, so downgrading wine isn't really feasible. I guess I'm stuck waiting for a bugfix...
Taku86 Posted April 25 Author Posted April 25 Just now, autofire372 said: No can do; I'm on an Arch-based distro, so downgrading wine isn't really feasible. I guess I'm stuck waiting for a bugfix... You can easily downgrade packages with downgrade. That's exactly what I'm doing right now. 1
autofire372 Posted April 25 Posted April 25 11 minutes ago, Taku86 said: You can easily downgrade packages with downgrade. That's exactly what I'm doing right now. Figured it out; had to re-create PKHeX's wine prefix afterward, but it's working now. 1
ExBurningRaptor Posted 6 hours ago Posted 6 hours ago (edited) Hey made an account because I'm running into an issue. So I got to step four and followed all directions, including adding the bit of code you mentioned to add before. I received this string of code: Quote 002c:fixme:winediag:loader_init wine-staging 11.9 is a testing version containing experimental patches. 002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. libEGL warning: pci id for fd 31: 10de:2f58, driver (null) pci id for fd 33: 10de:2f58, driver (null) pci id for fd 34: 10de:2f58, driver (null) libEGL warning: egl: failed to create dri2 screen libEGL warning: pci id for fd 31: 10de:2f58, driver (null) pci id for fd 33: 10de:2f58, driver (null) pci id for fd 34: 10de:2f58, driver (null) libEGL warning: egl: failed to create dri2 screen libEGL warning: pci id for fd 31: 10de:2f58, driver (null) 00b8:fixme:xinput:pdo_pnp code 0xc, not implemented! 00b8:fixme:xinput:pdo_pnp code 0xc, not implemented! 0024:fixme:winediag:loader_init wine-staging 11.9 is a testing version containing experimental patches. 0024:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. 0110:err:virtual:virtual_setup_exception stack overflow 1792 bytes addr 0x6fffffc1d4a5 stack 0x120900 (0x120000-0x121000-0x2a0000) I've tried using stable Wine, I've tried using staging and received this exact error. PKHeX won't start and I'm confused, because when I followed this guide it started before and was working fine. When I got to when I wanted to use it it just crashed on startup. Any clue on how to fix this? EDIT: As a note I'm on Linux Mint 22.3 Edited 6 hours ago by ExBurningRaptor Needed to state which version of Linux I'm on.
Kaphotics Posted 5 hours ago Posted 5 hours ago 50 minutes ago, ExBurningRaptor said: Hey made an account because I'm running into an issue. So I got to step four and followed all directions, including adding the bit of code you mentioned to add before. I received this string of code: I've tried using stable Wine, I've tried using staging and received this exact error. PKHeX won't start and I'm confused, because when I followed this guide it started before and was working fine. When I got to when I wanted to use it it just crashed on startup. Any clue on how to fix this? EDIT: As a note I'm on Linux Mint 22.3 As mentioned above, try on a previous version of wine (such as 11.4).
ExBurningRaptor Posted 3 hours ago Posted 3 hours ago 2 hours ago, Kaphotics said: As mentioned above, try on a previous version of wine (such as 11.4). Just did, and sadly same error happened where it didn't even startup. Here's the log for that command. Quote 002c:fixme:winediag:loader_init wine-staging 11.4 is a testing version containing experimental patches. 002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. libEGL warning: pci id for fd 31: 10de:2f58, driver (null) pci id for fd 33: 10de:2f58, driver (null) pci id for fd 34: 10de:2f58, driver (null) libEGL warning: egl: failed to create dri2 screen libEGL warning: pci id for fd 31: 10de:2f58, driver (null) pci id for fd 33: 10de:2f58, driver (null) pci id for fd 34: 10de:2f58, driver (null) libEGL warning: egl: failed to create dri2 screen libEGL warning: pci id for fd 31: 10de:2f58, driver (null) 00b8:fixme:xinput:pdo_pnp code 0xc, not implemented! 00b8:fixme:xinput:pdo_pnp code 0xc, not implemented! 0024:fixme:winediag:loader_init wine-staging 11.4 is a testing version containing experimental patches. 0024:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. 00fc:err:virtual:virtual_setup_exception stack overflow 1856 bytes addr 0x6fffffc1d2a5 stack 0x1208c0 (0x120000-0x121000-0x2a0000)
Taku86 Posted 1 hour ago Author Posted 1 hour ago @ExBurningRaptor Did you try a clean wineprefix? Upgrading/downgrading/changing Wine version can break the wineprefix
ExBurningRaptor Posted 1 hour ago Posted 1 hour ago 16 minutes ago, Taku86 said: @ExBurningRaptor Did you try a clean wineprefix? Upgrading/downgrading/changing Wine version can break the wineprefix I did make a clean wineprefix. I followed each step mentioned, so I did make a fresh wineprefix.
Taku86 Posted 1 hour ago Author Posted 1 hour ago 4 minutes ago, ExBurningRaptor said: I did make a clean wineprefix. I followed each step mentioned, so I did make a fresh wineprefix. I mean, did you try to delete your current wineprefix and repeat the procedure on a completely clean one?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now