wine-bugs

wine-bugs@winehq.org

1 participants
158754 discussions

[Bug 57776] New: Wine Approach startup crash
by WineHQ Bugzilla 12 Feb '25

12 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57776 Bug ID: 57776 Summary: Wine Approach startup crash Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com Distribution: --- SmartSuite-N99.8.0208.0800 Fedora 41 wine-stable-10.0.0-1.1.x86_64 winehq-stable-10.0.0-1.1.x86_64 Wine Approach startup crash: wine approach.exe Error on LSIOpen, or "Couldn't load the Lotus Dialogs DynaLink" wine: Unhandled page fault on read access to 00000024 at address 1660170C (thread 0144), starting debugger... Show Detains on crash reporter: Unhandled exception: page fault on read access to 0x00000024 in wow64 32-bit code (0x1660170c). This is due to Wine not using lotus' paths correctly (from the registry). Work Around: $ cd ~/.wine/drive_c/lotus $ mkdir jumble $ cp -R approach/* jumble/. $ cp -R compnent/* jumble/. Simple start: $ wine ~/.wine/drive_c/lotus/jumble/approach.exe Fancy start: $ bash -c "cd $HOME/.wine/drive_c/lotus/jumble; wine explorer /desktop=Approach_`date +%%H:%%M:%%S`_1680x1050,1680x1050 ./approach.exe" -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 57783] New: Approach will not run in a virgin 10.0 wineprefix
by WineHQ Bugzilla 12 Feb '25

12 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57783 Bug ID: 57783 Summary: Approach will not run in a virgin 10.0 wineprefix Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com Distribution: --- Created attachment 77980 --> https://bugs.winehq.org/attachment.cgi?id=77980 debugg message on crash What a disaster! Please correct. I need my accounting system back. SmartSuite-N99.8.0208.0800 Fedora 41 wine-stable-10.0.0-1.1.x86_64 winehq-stable-10.0.0-1.1.x86_64 Lotus Approach will not run in a fresh WINEPREFIX under WineHQ Stable 10.0, unless you have leftover stuff from a prior wine install. But that would not be a fresh WINEPREFIX. Both Approach and WordPro were selected on a customer install and a fulkl install too after wiping the .wine directory and starting fresh The following error occurs at the end of installation from the smart suite ISO. regedit: Unable to open the registry key 'HKEY_CURRENT_USER\Software\Lotus\SmartSuite'. and regedit: Unable to open the registry key 'HKEY_CURRENT_USER\Software\Lotus\ScreenCam'. Only Approach and WordPro were selected on a customer install. When starting Approach: $ cd /home/todd/.wine/drive_c/lotus/approach $ wine ./approach.exe The following pop occurs "Lotus Approach: Couldn't load Lotus Dialog DynaLink" Pressing okay, opens a Program Error box and presents this error in the command line: wine: Unhandled exception 0xe06d7363 in thread 24 at address 7B5F7448 (thread 0024), starting debugger... I will attach the full debug message message. I have one for one checked a qemu-kvm Windows 10 install of Approach against my wine registry and they are identical Many thanks -T -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 53910] New: windows get moved around when dpms blankout happens
by WineHQ Bugzilla 12 Feb '25

12 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=53910 Bug ID: 53910 Summary: windows get moved around when dpms blankout happens Product: Wine Version: 7.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- Technically, it's a regression, but not sufficiently significant (for me) to check when it began - I initially thought it was something even more random. Anyway, as the summary says, relatively recently (I'd say within last two months, perhaps less) I've noticed than under some at the time unclear condition, some of the windows get randomly moved around their respective desktops without any of my interaction. For the most part it was only slightly annoying and seemingly random, so I've just lived with it. But today I had an idea and successfully tested it. All that's needed was 'xset dpms force off'. It's also quite generic - can be triggered with notepad and winecfg. My setup is of two monitors, but one of them is quite old and most of the time turned off (that still allows for stumbling upon various quirks of winex11.drv's multi-screen handling). Once 'xset dpms force off' is fully in effect, upon restoring from the blankout the windows get somewhat randomly moved. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 57816] New: Splinter Cell: Pandora Tomorrow (2004): crashes when changing game resolution when used with DXVK
by WineHQ Bugzilla 11 Feb '25

11 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57816 Bug ID: 57816 Summary: Splinter Cell: Pandora Tomorrow (2004): crashes when changing game resolution when used with DXVK Product: Wine Version: 10.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: daniel.penalized(a)proton.me Distribution: ArchLinux Created attachment 78026 --> https://bugs.winehq.org/attachment.cgi?id=78026 output log When I change the game resolution via the options menu, the game crashes. You can also crash when you start the game (right after the introductory video). Just change the game resolution via the SplinterCell2.ini configuration file: WindowedViewportX=1600 WindowedViewportY=1200 and the SplinterCell2.ini configuration file: Resolution=1600x1200 This behavior only happens when used with DXVK. It doesn't happen with WineD3D OpenGL (it's impossible to test with WineD3D Vulkan, as it completely breaks the look of the game). And of course, it doesn't happen with winex11.drv either. - The game was installed via CD-ROM and is up to date with the latest update (v1.31). - I use labwc/wlroots as WM. - Although I'm on Arch Linux, I compile wine manually with these options: ./configure --prefix=/usr --enable-archs=i386,x86_64 --enable-win64. So I'm using the new WoW64 mode, but this behavior also happens in normal wine. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 53847] New: NfRemote: mouse input ignored
by WineHQ Bugzilla 11 Feb '25

11 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=53847 Bug ID: 53847 Summary: NfRemote: mouse input ignored Product: Wine Version: 7.0 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thelen(a)radiomankato.com https://www.telosalliance.com/uploads/Omnia%20Products/Software/NfRemote.exe Say hello to nfremote. It's a little piece of software used to administer a particular manufacturer's equipment, commonly used at radio and TV stations. I can confirm it has, and does, work fine under Wine 2.21 - just tested today on a MacBookPro8,1 running the official binaries (https://dl.winehq.org/wine-builds/macosx/pool/winehq-staging-2.21.pkg) under OS 10.13.6. Meanwhile, I have a new Mac (MacBookPro16,2 - Intel-based), on which I’ve deployed Wine 7.0 via homebrew under OS 12.6.1. There I can start nfremote just fine... but it ignores my mouse input. If I were to start it with the command-line argument "run", it presents me with a window where both keyboard and mouse input are accepted; there I can type in the text fields, so I know it's responsive. But when I hover the cursor over buttons, they do not 'light up’ to indicate such. And when I click, nothing happens. Even in years past, I found that newer versions of Wine exhibited the issue I describe below, so I simply never updated beyond 2.21. Wonder if this might be a long-undiscovered regression of some sort? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 57821] New: Formlabs PreForm: Balck loading screen
by WineHQ Bugzilla 11 Feb '25

11 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57821 Bug ID: 57821 Summary: Formlabs PreForm: Balck loading screen Product: Wine Version: 10.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: skala.antonin(a)gmail.com Distribution: --- Created attachment 78032 --> https://bugs.winehq.org/attachment.cgi?id=78032 Wine standart output Hello, when I start Formlabs PreForm tool for slicing 3D models for printer, initial loading window is solid black so information about loading progress is not visible. Running on Ubuntu 24.10 trough Xwayland. Behavior is same for Wine 9.??-10.1 It can be obtained there: https://formlabs.com/eu/software/preform/ (free - just ask some questions, no registration no SN of device needed) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 57459] New: Wine Regedit and Wine Control don't minimize and become unresponsive
by WineHQ Bugzilla 10 Feb '25

10 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57459 Bug ID: 57459 Summary: Wine Regedit and Wine Control don't minimize and become unresponsive Product: Wine Version: 9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: agarplayerarlon(a)gmail.com Distribution: --- Created attachment 77457 --> https://bugs.winehq.org/attachment.cgi?id=77457 video of the issue I've attached a video of the issue Basically those apps instead of minimizing they compress and become unresponsive afterwards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 57812] New: Roblox Studio cursor locking on wayland is faulty
by WineHQ Bugzilla 10 Feb '25

10 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57812 Bug ID: 57812 Summary: Roblox Studio cursor locking on wayland is faulty Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: sewn(a)disroot.org Distribution: --- When running Roblox Studio with or without using Vinegar, the cursor locking in Wayland does not function properly, making the cursor move randomly and sporadically all over the window. It functions the same in Xwayland. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 57637] New: Regression: Crash on exit in Age of Empires
by WineHQ Bugzilla 10 Feb '25

10 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57637 Bug ID: 57637 Summary: Regression: Crash on exit in Age of Empires Product: Wine Version: 9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dplay Assignee: wine-bugs(a)winehq.org Reporter: krkos(a)mail.muni.cz Distribution: --- Created attachment 77765 --> https://bugs.winehq.org/attachment.cgi?id=77765 AoE exit crash backtrace The bug affects original Age of Empires with UPatch HD 1.2 Release 3. Upon program exit, it crashes with page fault on write access to 0x00000005, see attached backtrace. This was bisected to be caused by 490d5f0fcf8556548743ad65a2a9951c2f503809 "dplayx: Merged IDirectPlayLobby/2A in to IDirectPlayLobby3A.", which seems strange as the backtrace indicates something audio related, but was reproduced repeatedly. The bug manifests on wow64 32bit (configure --enable-win64 --enable-archs=i386,x86_64), compiled with both mingw and clang. I did not test pure 32b wine. The bug is still present in wine 10.0-rc4. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 57811] New: wikis/Building-Wine contains broken/obsolete link
by WineHQ Bugzilla 09 Feb '25

09 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57811 Bug ID: 57811 Summary: wikis/Building-Wine contains broken/obsolete link Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: depaoli.renzo(a)gmail.com Distribution: --- As per instruction on the 404 website "If you followed a link from a WineHQ.org page and reached this page in error, please report it to the WineHQ.org Bugzilla.": The link on the Wine Wiki https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine https://www.winehq.org/pipermail/wine-devel/2016-January/111245.html is broken resulting in 404. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs