Infernio Posted January 11 Share Posted January 11 You're welcome And those two are known problems: 1. I honestly have no idea why we are trying to do that chmod thing. That code predates me, plus we're only doing it in two out of the 10+ places we extract files from an archive. It should probably just go. 2. I haven't been able to get the GTK webview to read the CSS. I've tried loading it as an external resource via several different methods, I've tried embedding the CSS directly in the HTML - nothing. The webview just will not load it Link to comment Share on other sites More sharing options...
Gamma Cavy Posted January 13 Share Posted January 13 Reporting error : Wrye Bash encountered an error. Please post the information below to the official thread at https://afkmods.com/index.php?/topic/4966-wrye-bash-all-games or to the Wrye Bash Discord at https://discord.gg/NwWvAFR Traceback (most recent call last): File "bash\bash.pyo", line 202, in main File "bash\bash.pyo", line 365, in _main File "bash\basher\__init__.pyo", line 4214, in Init File "bash\basher\__init__.pyo", line 4250, in InitData File "bash\bosh\__init__.pyo", line 1995, in refresh File "bash\bosh\__init__.pyo", line 1400, in refresh File "bash\bosh\__init__.pyo", line 2200, in new_info File "bash\bosh\__init__.pyo", line 1376, in new_info File "bash\bosh\__init__.pyo", line 1285, in new_info File "bash\bosh\__init__.pyo", line 366, in __init__ File "bash\bosh\__init__.pyo", line 175, in __init__ File "bash\bolt.pyo", line 1147, in __init__ File "bash\bosh\__init__.pyo", line 369, in _reset_cache File "bash\bosh\__init__.pyo", line 187, in _reset_cache File "bash\bosh\__init__.pyo", line 558, in readHeader File "bash\bolt.pyo", line 774, in open IOError: [Errno 13] Permission denied: u'E:\\Games\\Skyrim SE\\Skyrim Special Edition\\Data\\MLQ_ForswornSkinchangers.esp' I should add that I have no idea which version of BASH i'm using. Link to comment Share on other sites More sharing options...
Trollkin Posted February 2 Share Posted February 2 New error here; suddenly appeared when I first tried to run WB after updating Starfield from v1888 to v1951 yesterday: Traceback (most recent call last): File "bash\bash.py", line 425, in main File "bash\bash.py", line 572, in _main File "bash\basher\__init__.py", line 4283, in Init File "bash\basher\__init__.py", line 4311, in InitData File "bash\bosh\__init__.py", line 2397, in refresh File "bash\bosh\__init__.py", line 2139, in _modinfos_cache_wrapper File "bash\bosh\__init__.py", line 2257, in refreshLoadOrder File "bash\load_order.py", line 348, in refresh_lo File "bash\load_order.py", line 288, in _update_cache File "bash\_games_lo.py", line 271, in get_load_order File "bash\_games_lo.py", line 544, in _fix_active_plugins File "bash\_games_lo.py", line 616, in _check_active_order KeyError: FName('Starfield.esm') I was running the November WB312 build from Nexus at the time, so I updated to the Jan 7 build, and later to the Jan 26 installer dev build (I atempted to install -and later removed- the most recent nightly (and python 3121 alongside my existing v311 install) and missed something when trying to install the nightly - the .py launcher didn't fire at all, so I gave up, removed it, and installed the dev build from last week again). The 313.202401261753 build loads for SSE and Fallout 4 just fine, but still errors out for Starfield as pasted above. Hope I just did something dumb - Thoughts? Link to comment Share on other sites More sharing options...
sibir Posted February 2 Share Posted February 2 23 minutes ago, Trollkin said: New error here; suddenly appeared when I first tried to run WB after updating Starfield from v1888 to v1951 yesterday: Traceback (most recent call last): File "bash\bash.py", line 425, in main File "bash\bash.py", line 572, in _main File "bash\basher\__init__.py", line 4283, in Init File "bash\basher\__init__.py", line 4311, in InitData File "bash\bosh\__init__.py", line 2397, in refresh File "bash\bosh\__init__.py", line 2139, in _modinfos_cache_wrapper File "bash\bosh\__init__.py", line 2257, in refreshLoadOrder File "bash\load_order.py", line 348, in refresh_lo File "bash\load_order.py", line 288, in _update_cache File "bash\_games_lo.py", line 271, in get_load_order File "bash\_games_lo.py", line 544, in _fix_active_plugins File "bash\_games_lo.py", line 616, in _check_active_order KeyError: FName('Starfield.esm') I was running the November WB312 build from Nexus at the time, so I updated to the Jan 7 build, and later to the Jan 26 installer dev build (I atempted to install -and later removed- the most recent nightly (and python 3121 alongside my existing v311 install) and missed something when trying to install the nightly - the .py launcher didn't fire at all, so I gave up, removed it, and installed the dev build from last week again). The 313.202401261753 build loads for SSE and Fallout 4 just fine, but still errors out for Starfield as pasted above. Hope I just did something dumb - Thoughts? It's fixed in the most recent nightly, & the next WIP build will include the fix. Link to comment Share on other sites More sharing options...
Trollkin Posted February 2 Share Posted February 2 (edited) I'll grab it this weekend - EDIT: The nightly works beautifully - Thank you! Edited February 3 by Trollkin Link to comment Share on other sites More sharing options...
Trollkin Posted February 3 Share Posted February 3 Aand here's a new one; I get the attached error(s) during WB load, if I currently have any Starfield Saves created after updating SF to v1951. As you would expect, WB doesn't load these saves, or show them in the Saves tab. Saves created pre-1951 appear to load and behave as expected. Nothing horrible; just thought I should report some new 1951 weirdness - WB Error 20240202.txt Link to comment Share on other sites More sharing options...
Infernio Posted February 3 Share Posted February 3 (edited) @Trollkin Could you please upload the save in question (Save1597_907F103E_4D6172637573_141849_20240203013420_102_0_4.sfs)? And ideally also a save that works fine? Edited February 3 by Infernio Link to comment Share on other sites More sharing options...
Trollkin Posted February 5 Share Posted February 5 (edited) You bet - Here you go - Let me know if I should compress/zip these instead - Save1596_907F103E_4D6172637573_141841_20240131015718_102_0_4.sfs Save1606_907F103E_4D6172637573_142115_20240203053734_102_0_4.sfs Edited February 5 by Trollkin Link to comment Share on other sites More sharing options...
Infernio Posted March 22 Share Posted March 22 (edited) @Trollkin I completely forgot there were two people who'd sent me saves, sorry for never getting back to you The current WIP builds should support the new Starfield save format, I added support a couple weeks back. Edited March 22 by Infernio Link to comment Share on other sites More sharing options...
houckha Posted March 24 Share Posted March 24 Error after installing. i had a previous version 302 installled, but i couldnt find the launcher after updating to win11. Downloaded and installed the latest build and it gave me this error on launch. Traceback (most recent call last): File "bash\bash.py", line 425, in main File "bash\bash.py", line 573, in _main File "bash\basher\__init__.py", line 4349, in Init File "bash\basher\__init__.py", line 3928, in __init__ File "bash\basher\__init__.py", line 3798, in __init__ TypeError: list indices must be integers or slices, not str How do i fix this? Thanks Link to comment Share on other sites More sharing options...
Infernio Posted March 24 Share Posted March 24 @houckha Are you sure it was 302? That version is absolutely ancient, you'd probably have to upgrade your settings to newer formats by installing versions 306 and 309.1 first. If you meant 312 or something rather than 302, try the latest WIP build from the second post in this thread. If it still happens with that, please upload your BashBugDump.log. Link to comment Share on other sites More sharing options...
houckha Posted March 24 Share Posted March 24 @Infernio it was actually 304.3. sorry anyway. Thanks a lot for your help and absolutely top corporate grade response time! WIP build let me launch without issues. Link to comment Share on other sites More sharing options...
Arthmoor Posted April 4 Share Posted April 4 Latest WIP version, trying to do a "Sync From Data" operation. Traceback (most recent call last): File "bash\bolt.py", line 1209, in removedirs File "<frozen os>", line 243, in removedirs OSError: [WinError 145] The directory is not empty: 'C:\\Steam\\steamapps\\common\\Skyrim Special Edition Mods\\Bash Installers\\Unofficial Skyrim Special Edition Patch\\textures\\clothes\\farmclothes02' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "bash\balt.py", line 1684, in __Execute File "bash\basher\installer_links.py", line 1220, in Execute File "bash\bosh\bain.py", line 1765, in sync_from_data File "bash\bosh\bain.py", line 1381, in _do_sync_data File "bash\bosh\bain.py", line 72, in _remove_empty_dirs File "bash\bosh\bain.py", line 72, in _remove_empty_dirs File "bash\bosh\bain.py", line 77, in _remove_empty_dirs File "bash\bolt.py", line 1215, in removedirs File "<frozen os>", line 243, in removedirs OSError: [WinError 145] The directory is not empty: 'C:\\Steam\\steamapps\\common\\Skyrim Special Edition Mods\\Bash Installers\\Unofficial Skyrim Special Edition Patch\\textures\\clothes\\farmclothes02' The specified folder was deleted from Data because the files in it were fixed in an official patch. WB is apparently having issues removing the now empty folders from the project hierarchy. The actual files themselves are long gone, only empty folders remain. Full debug attached. BashBugDump.log Link to comment Share on other sites More sharing options...
Utumno Posted April 10 Author Share Posted April 10 (edited) On 4/4/2024 at 6:13 AM, Arthmoor said: Latest WIP version, trying to do a "Sync From Data" operation. Traceback (most recent call last): File "bash\bolt.py", line 1209, in removedirs File "<frozen os>", line 243, in removedirs OSError: [WinError 145] The directory is not empty: 'C:\\Steam\\steamapps\\common\\Skyrim Special Edition Mods\\Bash Installers\\Unofficial Skyrim Special Edition Patch\\textures\\clothes\\farmclothes02' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "bash\balt.py", line 1684, in __Execute File "bash\basher\installer_links.py", line 1220, in Execute File "bash\bosh\bain.py", line 1765, in sync_from_data File "bash\bosh\bain.py", line 1381, in _do_sync_data File "bash\bosh\bain.py", line 72, in _remove_empty_dirs File "bash\bosh\bain.py", line 72, in _remove_empty_dirs File "bash\bosh\bain.py", line 77, in _remove_empty_dirs File "bash\bolt.py", line 1215, in removedirs File "<frozen os>", line 243, in removedirs OSError: [WinError 145] The directory is not empty: 'C:\\Steam\\steamapps\\common\\Skyrim Special Edition Mods\\Bash Installers\\Unofficial Skyrim Special Edition Patch\\textures\\clothes\\farmclothes02' The specified folder was deleted from Data because the files in it were fixed in an official patch. WB is apparently having issues removing the now empty folders from the project hierarchy. The actual files themselves are long gone, only empty folders remain. Full debug attached. BashBugDump.log 8.98 kB · 0 downloads Hi @Arthmoor could you post me the directory/file structure under clothes\\? Also there are no hidden files like thumbs.db? nvm I think I fixed it - grab the build from https://github.com/wrye-bash/wrye-bash/actions/runs/8631863099/artifacts/1401500502 Edited April 10 by Utumno Link to comment Share on other sites More sharing options...
Arthmoor Posted April 10 Share Posted April 10 That appears to have fixed the issue. Thanks Utumno 1 Link to comment Share on other sites More sharing options...
DayDreamer Posted April 14 Share Posted April 14 In anticipation of this week's USSEP update, I've been looking into changing from Vortex to Wrye Bash. But I cannot fathom how the CK script source directories should be structured to be automatically maintained. Currently, (off the top of my head) I manually copy Data/Source/Scripts to Data/Scripts/Source, then the script extender script source files, then (after extracting) the USSEP script source files, then each of my own scripts (from their respective plugin directories). Likewise, I manually copy the script extender .pex files into Data/Scripts. But not the USSEP .pex, as they are automatically found by the engine in its .bsa and overridden in load order. Sometimes, I'll make mistakes and have to start all over again. When running the CK, they all have to be the same place for the CK's packager to send Bethesda. Ideally, when activating USSEP, it would extract the USSEP sources, and put them in the source directory, and remember which other scripts were overridden by it, so that there would be no need to do all the manual labor every time an updated game or USSEP is released. Link to comment Share on other sites More sharing options...
sibir Posted April 15 Share Posted April 15 Manually installed files won't be tracked, so install them through WB to track them. Link to comment Share on other sites More sharing options...
jaydawg55 Posted April 16 Share Posted April 16 The error attached appears whenever I try building a Bash Patch using the latest dev version of Wrye Bash. Prior to this error appearing a small window pops up that says: 'NoneType' object does nor support item assignment I don't know what object this refers to. 2024-04-15-WB-Error-after-trying-to-Rebuild-Bash-Patch_.txt Link to comment Share on other sites More sharing options...
sibir Posted April 16 Share Posted April 16 5 hours ago, jaydawg55 said: The error attached appears whenever I try building a Bash Patch using the latest dev version of Wrye Bash. Prior to this error appearing a small window pops up that says: 'NoneType' object does nor support item assignment I don't know what object this refers to. 2024-04-15-WB-Error-after-trying-to-Rebuild-Bash-Patch_.txt 898 B · 0 downloads Please upload the full BashBugDump.log in WB's installation folder. Link to comment Share on other sites More sharing options...
UnchainedJane Posted April 17 Share Posted April 17 Was trying to open Wrye after moving from Vortex to MO2 and I get the following error: Traceback (most recent call last): File "bash\bash.py", line 425, in main File "bash\bash.py", line 573, in _main File "bash\basher\__init__.py", line 4344, in Init File "bash\basher\__init__.py", line 4371, in InitData File "bash\bosh\__init__.py", line 2199, in __init__ bash.exception.FileError: Fallout4.esm: File is required, but could not be found I have had stream check the game files and have uninstalled and reinstalled the game Per the Error is states the Fallout.esm couldn't be found but the MO2 is able to see the file in the DATA folder. Should I just uninstalled Wrye and reinstall to see if the app is able to find the Fallout4.esm? Link to comment Share on other sites More sharing options...
Infernio Posted April 17 Share Posted April 17 @UnchainedJane Are you launching Wrye Bash through MO2? If you're not doing that, WB won't be able to see any of the files in the Data folder. Link to comment Share on other sites More sharing options...
UnchainedJane Posted April 17 Share Posted April 17 @Infernio I was not, going to try that now. Thank you. Sometimes you just need another set of eyes looking at the issue. Link to comment Share on other sites More sharing options...
Arthmoor Posted April 18 Share Posted April 18 Getting a new error using the nightly Utumno linked: Traceback (most recent call last): File "bash\balt.py", line 1684, in __Execute File "bash\basher\installer_links.py", line 681, in Execute File "bash\basher\installer_links.py", line 662, in _try_installer File "bash\balt.py", line 515, in _conversation_wrapper File "bash\basher\installer_links.py", line 577, in Execute File "bash\bosh\bain.py", line 2646, in bain_install File "bash\bosh\bain.py", line 2614, in _installer_install File "bash\bosh\bain.py", line 1268, in install File "bash\bosh\bain.py", line 1569, in _install File "bash\bosh\bain.py", line 1318, in _fs_install File "bash\bosh\__init__.py", line 3541, in new_info File "bash\bosh\__init__.py", line 1665, in new_info File "bash\bosh\__init__.py", line 221, in set_table_prop KeyError: 'installer' This is happening whenever I attempt to rename a package file, anneal a package, or do a full install from a package. Link to comment Share on other sites More sharing options...
sibir Posted April 18 Share Posted April 18 2 hours ago, Arthmoor said: Getting a new error using the nightly Utumno linked: Traceback (most recent call last): File "bash\balt.py", line 1684, in __Execute File "bash\basher\installer_links.py", line 681, in Execute File "bash\basher\installer_links.py", line 662, in _try_installer File "bash\balt.py", line 515, in _conversation_wrapper File "bash\basher\installer_links.py", line 577, in Execute File "bash\bosh\bain.py", line 2646, in bain_install File "bash\bosh\bain.py", line 2614, in _installer_install File "bash\bosh\bain.py", line 1268, in install File "bash\bosh\bain.py", line 1569, in _install File "bash\bosh\bain.py", line 1318, in _fs_install File "bash\bosh\__init__.py", line 3541, in new_info File "bash\bosh\__init__.py", line 1665, in new_info File "bash\bosh\__init__.py", line 221, in set_table_prop KeyError: 'installer' This is happening whenever I attempt to rename a package file, anneal a package, or do a full install from a package. @Utumno, the source of this traceback is 184ebf1, & it still happens in ut-336-drop-table. Link to comment Share on other sites More sharing options...
Utumno Posted April 18 Author Share Posted April 18 Thanks @sibir @Arthmoor - it's a big change I expect some things breaking but not much Actually this is fixed later on but should be fixed hackily in the build https://github.com/wrye-bash/wrye-bash/actions/runs/8737036059 when ready Link to comment Share on other sites More sharing options...
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