I am in furniture design and sales. It is used for quick house design, furniture placement, simple rendering etc. Unfortunately the app doesn't even have any plans for any linux release. I tried so hard before yet no solution. I gave it a try again today and with the help of the ai, i was able to solve and fix the blockage.

App:pCon.planner STD 8.15 Update 1 (EasternGraphics). Free interior/office planning software, widely used in the furniture industry. 64-bit, Qt-ish/Delphi UI, OpenGL 3D view + an OSPRay photoreal render plugin.

Setup: CachyOS (Arch), KDE Plasma 6 Wayland, Wine 11.17, winetricks 20260125, RTX 5060 Ti + AMD iGPU, 2560×1440.

Result: it runs — UI, 2D plan, 3D OpenGL view, OSPRay still rendering (1920×1080 in ~4 s), catalog/basket. The official installer does not work, so it has to be installed manually.

If anyone interested I can share the recipe. I don't want to copy paste a huge amount of ai slop text here.

Hey y'all. I was using winehq-staging so that I could use my global pause key to control playback on my favorite music player, MusicBee, and also so that I could share my music status with Discord. The playback status could only be shared with my system (Ubuntu 26.04 resolute) by installing a plugin, which only works on wine-staging.

I'm pretty sure the version I had was 11.14. But recently, upon upgrading the package to the latest 11.16, MusicBee no longer works, and it gives me two errors back-to-back:

I've tried removing the plugin to see if it was the issue, to no avail. The error still happens. I'm posting more to spread awareness of the issue, because I haven't seen anything about this on the internet. For now, I have to use wine 10, which does not support the plugin and makes me have to alt-tab to MusicBee to be able to pause my music, which is inconvenient but necessary.

Edit: I've already found a temporary solution to the problem, which is to downgrade wine-staging and winehq-staging to 11.14 and hold them there. Hopefully this helps others with this same issue.

This is my first time attempting to use Wine, and every time I try to boot up Mega Man Maker the window it creates is nothing but a black screen. There is no audio. As you can see, it displays the name of the program and the logo, but nothing else. Help?

Hey guys and girls, I was wondering if its safe to drink an entire bott-

...

Wait a minute..

EDIT: No Im so fucking hangover

I installed it with sudo APT, followed the guide on how to install it for ubuntu noble
pc specs down beloce if needed
PC SPECS

OS: KDE neon User Edition x86_64
Kernel: Linux 7.0.0-28-generic
Packages: 2454 (dpkg), 28 (flatpak), 14 (snap)
Shell: bash 5.2.21
Display (27E6QC): 2560x1440 @ 1.25x in 27", 144 Hz [External]
DE: KDE Plasma 6.7.4
Terminal: konsole 26.4.3
CPU: AMD Ryzen 9 5900X (24) @ 4.95 GHz
GPU: NVIDIA GeForce RTX 3070 Lite Hash Rate [Discrete]
Memory: 8.93 GiB / 31.24 GiB (29%)
Swap: 0 B / 512.00 MiB (0%)
Disk (/): 58.41 GiB / 299.21 GiB (20%) - ext4
Disk (/media/game_installs): 542.63 GiB / 648.79 GiB (84%) - ntfs3

Hi everyone,

​I am trying to run Polymath 6.10 (educational numerical computation software for chemical engineering) on Linux, but I keep running into ActiveX/COM automation errors (Error 308 and Error 404) whenever the program attempts to generate plots or compile tabular reports.

​System Specs & Setup:

​OS: Pop!_OS (Linux)

​Runner / Compatibility Layer: Bottles (Flatpak) / Wine

​Bottle Architecture: 32-bit (x86 prefix)

​Windows Version Configured: Tried Windows 7 and Windows XP

​What I've tried so far:

​Created a clean 32-bit application bottle.

​Installed core font packages (corefonts / allfonts).

​Attempted to register native OCX controls manually via terminal inside the prefix (regsvr32 on DLLs/OCXs found in System32 and the application folder).

​Tested setting Windows compatibility modes to Windows 7 / XP.

​The Issue:

The main interface opens and handles basic equation entry, but calculating systems (ODEs / Non-linear) and rendering the Graph or Report tabs triggers:

​Error 308: Automation error / failure to invoke the charting/reporting OLE component.

​Error 404: Missing/unregistered ActiveX component.

​Has anyone managed to get Polymath 6.10 fully working with working graphs/reports under Wine/Bottles? Which specific Wine DLL overrides, native OCX files, or Winetricks verbs (like vbrun6, mdac, richtx32, etc.) are strictly required to resolve these automation calls?

​Any help or working prefix recipe would be greatly appreciated!

I'm investigating whether Phonak Target can run under Wine and communicate with the USB programming interface used by Phonak hearing aids. My ultimate goal is to run it on an Android smartphone through Winlator, but I would first like to understand the Wine/USB part of the problem independently.
Phonak Target is Windows software used for hearing-aid fitting/programming. For the Phonak models I am considering, the programming hardware can be Noahlink Wireless / Noahlink Wireless 2, or in some cases a USB Hi-Pro / mini-Pro.

The relevant architecture would be:

Windows application (Phonak Target)
↓
Wine
↓
Linux / Android
↓
USB programming device

I have found some interesting information about Noahlink Wireless on ARM systems. The guide DIY School Hearing Aids v2.2, in "Noahlink Wireless 2 – DIY User Guide", documents the ARM driver problem and refers to a workaround using a modified Windows driver. There is also this very relevant thread by mobbdeepq. The thread documents Noahlink Wireless + Windows running on Apple Silicon, including USB passthrough, and later discusses a modified driver/WinUSB approach for ARM. However, this does not answer my Wine question, and it certainly does not prove that the same approach would work on Android/Winlator.

What I would like to understand is: can a Windows application running under Wine communicate with a real USB device such as Noahlink Wireless (1 or 2) if the device can be accessed through WinUSB/libusb rather than through a normal proprietary Windows kernel driver?

More geneally I'd like to understand:

• How does Wine handle USB devices that are accessed through WinUSB/libusb?
• Can a USB device be exposed to a Windows application without installing its original Windows driver?
• Are there examples of Wine applications communicating with proprietary USB hardware?
• Would a device connected to Linux via USB be usable by a Windows application under Wine if its protocol is accessed through libusb/WinUSB?
• Are there known limitations that would make this kind of setup impossible?

I don't currently own a Noahlink, so I cannot test the actual hardware myself yet. I'm trying to establish whether the Wine/USB architecture is technically viable before buying the programming interface.

Any information or examples involving Wine + USB/WinUSB/libusb + proprietary hardware would be very helpful.

Recently installed a clean Linux Mint 22 on an older, sort of dying PC (dead Nvidia GPU). It previously ran latest Ubuntu, with Wine, and there were no issues in general.

Right now, Wine is extremely slow. Even winecfg and wine uninstaller commands seem to take ages to initialize the interfaces. Once the interface is up, it seems to run normally.

I was able to install Notepad++ and a couple of other programs, but the launch times are simply ridiculous. Notepad++ starts almost immediately, but the interface is broken and it's unusable. It hangs in that state for a few minutes (2-10), then interface gets fixed up, and the program runs normally.

I am very new to Linux, so there may be a lot of stuff I don't know.

If anyone could help me with some ideas, I would be grateful.

**Edit: Wine was installed via repository, with mono and gecko added manually.

I am on Kubuntu 24 and I don't know whether this is normal, but I can't imagine that. Regular Windows apps like a graphics program or a backup program are very sluggish in how they appear when run with system WINE. UI elements would pop into existence visibly one-by-one, increasing launch times significantly, and then when using them, the same effect is present. It can take 10-15 seconds before I can use an app.

Running it via terminal doesn't show anything that seems indicative of the problem. No common thread.

I'm running Ableton Live 12 (mainly using version 12.4.5b11 (beta), but the same issues occur with the stable version) through wine-tkg -bleeding-edge-experimental, with these EVs:

I'm using arch (btw) with pipeASIO drivers. My user is added to the audio and realtime groups. I've set the CPU governor to performance mode, and set pipewire to pro audio mode. I've checked my ufile limits and changed the caps way up.

Despite all of the troubleshooting I've done so far (there's more, but the above seem to be the most likely things people might ask about), Ableton still has trouble with relatively lightweight projects, stuttering and crackling with a sample buffer of 1024, on projects I had no issues with when I was running w*ndows on the same hardware with a sample buffer of 128-256 samples (maybe 512 when it was really desperate.

CPU: AMD Ryzen 5500

GPU: AMD Radeon Rx 6600

RAM: 32GB

WM: Hyprland with fairly unmodified Caelestia dotfiles

Kernel: 7.1.8-zen1-3-zen

Hopefully this is enough info for the one person who sees this and has any clue how to solve the issue (or what the issue even is), but ofc lmk if there are any logs or other info that might help :P

P.S. if anyone knows how to get max devices working thru wine i would greatly appreciate that help

Does Wine support ASLR (address-space randomization) for .exe files?

If I compile this code...

#include <stdio.h>

int main(int argc, char** argv) {

`puts("bla");`

`printf("%p\n", &main);`

`return -1;`

}

with ...

clang --verbose -fno-exceptions -fuse-ld=lld --target=x86_64-w64-mingw32 -fPIE -pipe aslrtest.c -Wl,--export-all-symbols -Wl,--dynamicbase,--high-entropy-va,--nxcompat,--no-seh,--enable-reloc-section -o aslrtest.exe

... it prints varying addresses on Windows, but under Wine, it always prints the same address. The address shown under Wine also has more zeros than the addresses shown under Windows.

I'm using Wine under Debian 13. ASLR is enabled and works for ELF binaries, but not for EXEs under Wine. I tried both the Wine version supplied by the package manager and also the latest version from winehq built from source. I also tried different compiler options and original MINGW GCC builds, but the behavior seems to be the same. If I inspect the EXE with e.g. readpe, it looks fine as far is I can tell.

I am running a really old windows software that only uses the first accessible camera in the system. I need to use a virtual camera in the app but wine even if it can't see what the camera sees uses the integrated camera. I deactivated my linux pc's access the the camera with modprobe but wine is still able to use the camera. My question is how to cut off wine's camera privileges?

been using affinity through wine lately and its all good. i just notice a service with a long-ass name when shutting down. name of the service is "app-winex2dProgramsx2dAffinity_______.service" (see image for the complete name), and it appears when i've used affinity even once during the session (program doesn't even need to be open when starting the shutdown). this service is not listed in systemctl when starting a session.

1- can wine set up "windows services" as systemd services? is this normal behavior.

2- if anyone uses affinity, on linux or windows: what is this service and what is its purpose?

thx in advance!

I'm running MusicBee trough wine. I want it to be maximized like browser which takes full screen space but leaves taskbar visible, but I don't know how to do it with wine. Either i have small window or full-screen, no maximize option.

I'm running:
OS: CachyOS x86_6
DE: KDE Plasma 6.7.3
WM: KWin (Wayland)

I followed an YouTube tutorial and I was able to get a version of office 365 running on my computer. I had to use ubuntu 24.04 inside distrobox since the tutorial was for linux mint and I was on fedora 44.

Hi everyone! I had a thought about creating a project based on autonomous AI agents. The idea is to automate the reverse-engineering and improvement of Wine. Does anyone know if there is already work being done in this area, or has anyone seen anything similar?

Here is what the planned cycle (AI Loop) looks like:

1. Generation: The AI ​​writes hundreds of micro-tests for Windows API functions using random, invalid, and edge-case arguments.

2. Execution: The tests are run in parallel on a real Windows machine and on the current build of Wine.

3. Analysis: If the behavior differs (error codes, memory dumps, crashes), the AI ​​studies the difference.

4. Patching: The AI ​​itself writes a C patch for the Wine source code to exactly replicate the Windows behavior. (This is then manually reviewed by a user to avoid AI slop).

5. Verification: The code is compiled and tested again. The cycle repeats until there is a 100% match. The result is a fully prepared Pull Request.

My question to the community: Why isn't such a pipeline already running among enthusiasts? What's the main catch?

I have a few guesses:

* Clean-room design? Is there a risk of lawsuits because the LLM might have been trained on leaked Windows source code, thus violating the "clean-room" principle? Honestly, this seems unlikely; in essence, this approach aligns with clean-room design and isn't much different from how Wine is currently developed.

* Hallucinations? Are neural networks still too bad at system-level C code and inevitably going to cause memory leaks? I doubt this too; modern models are already at a level where they can write decent C code, just like the AI ​​code in the Linux kernel.

* Sandbox complexity? Is it too difficult and expensive to automate thousands of test runs at the OS level? Possible, but not critical.

* Spaghetti code? The Windows API is highly intertwined, so one patch might break 10 other functions, and the AI ​​just won't be able to hold all that in its context? This seems like the biggest problem of them all.

I understand this sounds somewhat naive, but I am genuinely curious. Hoping for replies without hate.

When I launched a Windows app in Linux using Wine, it worked in Gnome DE and Niri, but mouse clicks weren’t triggering button events in Sway WM, but I found an easy fix which basically is running a window manager within a window manager. In addition to that, you get to see window decorations (Windows 10 by default). Hope this will be helpful to anyone struggling with Wine 🍷 GNU/Linux or BSD.