Rafael Brucart

I now believe I could not get it to work on Fedora because I had set in my bash env: QT_QPA_PLATFORM=wayland to force QT applications to use wayland. Evidently this breaks stuff. I should have left QT as xcb, rendering in x11... so essentially I forced Wine into a bug outside its control, my mistake. https://bugs.winehq.org/show_bug.cgi?id=41182 https://bbs.archlinux.org/viewtopic.php?id=266967

So perhaps I wasn't clear in my post but I was adding some suggestions strictly for people having issues with Fedora, because I had issues with Fedora, now I am on Arch and all is fine. But I challenge you to build your patched wine on native Fedora (no containers) by simply following the Building Wine and have it run -goodluck. Also I don't even think Wine is the issue, for whatever reason the Affinity installer runs but with no visible UI on Fedora, hence someone could try to emulate the desktop to fix. Also it maybe worth considering you're on a graphics design forum (not a linux forum) for software that doesn't supply a native Linux installer. What you consider simple can be challenging for others like myself who are not the greatest with the terminal but would rather spend hours in a struggle than stay with a working Microsoft Windows. Moreover I had no issues using containers as the Wine builds are the same file size and number as people have posted on this forum. So for Fedora you need to use toolbox or podman. Not only to avoid flooding your system with needless packages but because to my knowledge, experience, and research Wine does not build natively on Fedora either easily or without missing functionality - again prove me wrong, and I welcome others to try. Tldr; Whatever guide you want to post up however simple is irrelevant to my post unless you did it on Fedora. --- Lastly thank you. Your efforts along Wanesty have allowed me (and I would bet many others) to leave Microsoft for good. ... goodluck with Debian

I just came from Fedora. I tried manually building in a Debian container, then tried Grunts PKGBUILD in an Arch container, and Daegalus's podman. Nothing worked, so I assumed it was something I was doing. But now I've just switched to native Arch and did Daegalus's pod again. It is working. I can think of only these things: I believe the installer was running in Fedora only that for whatever reason it occupied 0 pixels on screen. If someone has Fedora they could try the following: 1. Before running the installer rum ElementalWarrior-[version] $HOME/.wineAffinity winecfg 2. Go to Graphics setting and enable "Emulate a virtual desktop", put in your monitor resolution 3. Now run the installer command: rum ElementalWarrior-[version] $HOME/.wineAffinity wine [Path to the installer].exe The second thing I can think of was case sensitivity for the "WinMetadata" in which case someone could try duplicating it and changing it to lower case. And the third is perhaps Fedora needs more than "wine" and "winetricks" installed, maybe some other supporting package. Has anybody got Affinity running on Fedora as of yet? Also on another note, I am using Affinity Suite 2.1.1 and for me it crashes on creating a New Document. I have to run "winetricks renderer=vulkan" to get it working in virtual desktop which breaks native desktop, for which I revert back with ..."winetricks renderer=gl". However I started again with a fresh prefix and it all worked fine, so not sure what was going on.

Prob stupid question. Did Wine 8.10 finish PE conversion? and is the goal of PE meant so you only have to build 64bit wine yet still run 32bit applications; in other words no reliance on building 32bit wine? or have a misunderstood? I ask because it may be worth switching to that instead as it may solve fedora issues as fedora ain't great to build 32bit wine, come to think most distros it is a hassle.

I am not to sure whether it is helpful to you or anyone but Fedora comes pre-installed with toolbox and podman. So for those who don't want to flood their OS with a million wine dev packages when attempting to build wine, you can create this environment before following Elemantal's guide. just type: $ toolbox create then $ toolbox enter Then install wine dev packages and follow Elemental's build instructions. --- Alternatively Wine is far easier to build on Debian/Ubuntu. So Alternatively (and I have no idea if this would work) you can build Wine from a Fedora terminal by entering Debian environment with the following: podman run --rm -it docker.io/library/debian Then install the debian wine dev packages, and then follow Elemental's guide. However I have no idea if the built wine will then work on a Fedora machine so...

Fantastic, this gives me hope. Thanks @ElementalWarrior Has anyone had any success with Bottles (flatpak)? so placing the compiled wine into ~/.var/app/com.usebottles.bottles/data/bottles/runners Then creating a Bottle for Affinity? That said. Is there any chance @ElementalWarrior of putting out a compiled/binary release of this wine so others don't have to figure out why official wine dependency lists are missing packages, or miss naming them, and all the other strange things that happen when inexperienced peeps like myself end up flooding their OS with hundreds of dev packages and wasting hours or days until they finally give up. I just switched to Windows at start of the year just for Affinity. Windows is the worst OS, and I miss Fedora dearly. I hope these patches make it to a precompiled Wine version. I know my limitations and have spent days trying to compile software in the past with no success, I must be dumb or cursed

Dragging and dropping JPG Xl onto a Picture Frame in a Publisher Document does not work

A large goal and purpose of JPEG XL is to provide a more efficient and flexible file format for photographers. At this time Affinity does not support the metadata in this format. Without metadata photographers like myself cannot utilize the format because contained in metadata is very important camera info, lenses, exposure info, and gps location. It would be great to have this implemented. In an export test I took a RAW photo of 28mb and converted it to a lossless 16bit jxl of 3.5mb, that is 7 times smaller, at raw color bitrate, and no loss of quality. In other words I could reduce my photo library around 87 percent with no loss in quality and high fidelity, EXCEPT I cannot give up the 1kb per photo of metadata. I hope it is implemented, I cannot imagine it being a difficult process.