Description of problem: https://bugs.winehq.org/show_bug.cgi?id=41459 Sorry if I suck at reporting bugs in WineHQ but I don't know how to do a proper retrace, leaving the bug report there ignored since wine 1.9.19, but I just don't get it why other distro work as reported in Wine AppDB TLDR The 32bit 7zip cannot access drive Z (the / directory), it just crashes... Version-Release number of selected component (if applicable): 2.10-1.fc26 How reproducible: This happens on both 32bit and 64bit Wine prefixes. Steps to Reproduce: 1. Grab any 32bit 7zip installers version 9.35 or later (see add. info) 2. Install it and run 7zFM.exe 3. Open Computers 4. Open Drive Z Actual results: Crashes with the error "The system cannot allocate the required amount of memory" and exits briefly after OK-ing A line triggered in the console just when the error occurred: warn:heap:allocate_large_block Could not allocate block for 7e0c28f1 bytes Expected results: Can access drive Z normally like the 64bit counterpart Additional info: You can grab a history of 7zip installers at http://filehippo.com/download_7zip/history/2/ Anything 9.22 or older works though... As of now, 32bit 7zip version 17.00 still crashes when opening drive Z whereas 64bit 7zip works correctly.
AppDB is not perfect. One user installs the app and sees it can decompress a .7z file. I doubt they went and purposely clicked on Z: and it works for them. I can reproduce your issue, but I'm not sure if it is a Wine bug or an app bug. If I ever have time I will try to debug it further, but you're best off trying to ask upstream to look at it. FYI: Fedora does not compile any custom patches or features into the Wine package. It is a vanilla Wine-staging build.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.