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.
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.
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.
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.
https://bugs.winehq.org/show_bug.cgi?id=57635
Bug ID: 57635
Summary: Battle.net Launcher invisible/black with the Wayland
driver
Product: Wine
Version: 10.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)xarov.net
Distribution: ArchLinux
Created attachment 77764
--> https://bugs.winehq.org/attachment.cgi?id=77764
Black window with Wayland driver
Works fine with the X11 driver. Is completely black with the Wayland driver.
--
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.
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.
https://bugs.winehq.org/show_bug.cgi?id=57697
Bug ID: 57697
Summary: PeekMessage + GetMessage issue with multiple windows
Product: Wine
Version: 9.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: oldcastlehq(a)protonmail.com
Distribution: ---
Created attachment 77885
--> https://bugs.winehq.org/attachment.cgi?id=77885
Video showing the issue.
When you drag-drop a color MuLab starts a modal event loop and polls the
PeekMessage + GetMessage functions for mouse move and mouse click events. When
the mouse moves over different windows this should deliver mouse move events
with the respective window handle of the window under the mouse. If there are
several floating windows then Wine doesn't deliver such events, which is odd.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=57820
Bug ID: 57820
Summary: Cannot drag and drop files into apps with the Wayland
driver enabled
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: agarplayerarlon(a)gmail.com
Distribution: ---
Created attachment 78030
--> https://bugs.winehq.org/attachment.cgi?id=78030
Video of the issue
As the title says I cannot drag and drop files into applications when using the
Wayland driver, I've only tested FL Studio and when I try to drag and drop a
file inside it, an "x" symbol appears to the cursor and doesen't let me drop
the file into the application.
I've attached a video of the issue.
Also using the x11 driver, drag and drop works fine.
--
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.
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.
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.