https://bugs.winehq.org/show_bug.cgi?id=53312
Bug ID: 53312
Summary: Installers made with Inno Setup 4.2.2 fail to create
non-latin paths
Product: Wine
Version: 7.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: abacadacaba(a)gmail.com
Distribution: ---
Installers will throw errors with proper LC_ALL. Installers will create files
with odd names without LC_ALL.
Ubuntu 20.04.4 LTS
Kernel release: 5.13.0-52-generic
--
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.
http://bugs.winehq.org/show_bug.cgi?id=26871
Summary: Dawn of War demo uninstaller doesn't do anything
Product: Wine
Version: 1.3.18
Platform: x86-64
URL: http://download.cnet.com/Warhammer-40-000-Dawn-of-War-
demo/3000-7483_4-10317161.html
OS/Version: Linux
Status: NEW
Keywords: download, Installer
Severity: minor
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kennybobs(a)o2.co.uk
Created an attachment (id=34254)
--> (http://bugs.winehq.org/attachment.cgi?id=34254)
Wine 1.3.18 +msi +msidb [3.3MB]
The Warhammer 40k: Dawn of War demo uninstaller claims to complete
successfully, but doesn't actually do anything.
Nothing useful in the console.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=37466
Bug ID: 37466
Summary: Deadly Premonition: The Director's Cut 1.01b Steam
crash after logos
Product: Wine
Version: 1.7.29
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: david.gamiz(a)gmail.com
Distribution: ---
Created attachment 49840
--> https://bugs.winehq.org/attachment.cgi?id=49840
log and trace crash wine
Install, run launcher and run game. After logos the game crash.
Overlay steam is OFF.
WinXP config. 32bit wine 1.7.29
--
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=53012
Bug ID: 53012
Summary: wine: Read access denied for device L"\\??\\Z:\\", FS
volume label and serial are not available.
Product: Wine
Version: 7.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: robwie2004(a)gmail.com
Distribution: ---
It's happening on Arch with fresh wine install on btrfs filesystem & wayland.
Thanks in advance.
--
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=42284
Bug ID: 42284
Summary: Enable using Wine with Wayland and without X on Linux
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shtetldik(a)gmail.com
Distribution: ---
Currently, Wine on Linux is strongly dependent on X, and when used with the
desktop environment with new Wayland display server, Wine is forced to run
through XWayland, which so far remains a poor experience.
The whole Linux desktop is now strongly pushing the switch from X to Wayland,
and many major applications are now in the process of enabling this switch.
Is there some plan for such effort in Wine? Is it even feasible? I couldn't
find any bugs opened for it, so I'm opening one here to track this.
--
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=53831
Bug ID: 53831
Summary: Cockos REAPER fullscreen loses mouse input
responsiveness after other windows/menus are created
Product: Wine
Version: 7.19
Hardware: x86-64
URL: http://reaper.fm/download.php
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: gabrielopcode(a)gmail.com
Distribution: ---
After setting Fullscreen in Reaper (Menubar: View->Fullscreen, or Alt+Enter
shortcut), clicking on the menu disables all further mouse interaction after
the menu is closed, due to fullscreen clipping. This happens only in managed
windows (controlled by Window Manager).
To demonstrate it after launching Reaper:
1) Click on View on the menubar and select Fullscreen at the bottom, or press
Alt+Enter.
2) Try to click/drag around the timeline, should work fine.
3) Click on the menubar again, can be anywhere, and then simply unfocus it by
clicking on the timeline or anywhere.
4) Notice how no mouse input works on the Reaper fullscreen window anymore.
There's another problematic scenario that's related to the same underlying
issue:
1) Click on View on the menubar and select Fullscreen at the bottom, or press
Alt+Enter.
2) Try to click/drag around the timeline, should work fine.
3) Click on the menubar again, go to File->Project Settings.
4) Notice how not even the new popped up window with Project Settings responds
to mouse input.
The underlying problem is that the winex11.drv code currently deals with
clipping fullscreen windows as if they were most likely just games only. It
can't seem to handle case where other windows get popped up, created, or
moved/changing capture (size-move operation for example) while one fullscreen
window is already clipping.
--
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=55140
Bug ID: 55140
Summary: GPU Caps Viewer 1.60 can crash with Nvidia GPU when
additional Nvidia libraries are present
Product: Wine
Version: 8.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: saancreed(a)gmail.com
Regression SHA1: 354a8bb1f4a65bdec052606f2799db9e2907b5b1
Distribution: ---
Created attachment 74704
--> https://bugs.winehq.org/attachment.cgi?id=74704
Backtrace from wine-8.9
A particular setup of GPU Caps Viewer 1.60, when paired together with
reimplementations of some Nvidia libraries, crashes in its own code after
upgrading Wine to release 8.9 or later. I've bisected this problem to commit
354a8bb1f4a65bdec052606f2799db9e2907b5b1 which can be reverted to make the
program function again.
The setup required to reproduce the issue might be quite convoluted, so bear
with me:
1. Get a system with Nvidia GPU and their proprietary driver, making sure that
32-bit `libnvidia-ml.so.1` is installed and can be found by `dlopen`
2. Get a build of Wine that includes commit
354a8bb1f4a65bdec052606f2799db9e2907b5b1 and doesn't use experimental wow64
mode and drop wine-nvml into that Wine's libdirs
(https://github.com/Saancreed/wine-nvml, see build/install instructions, there
are prebuilt binaries on GH Actions)
3. Create a prefix and install into it at least 32-bit versions of:
a. DXVK (https://github.com/doitsujin/dxvk)
b. DXVK-NVAPI (https://github.com/jp7677/dxvk-nvapi)
4. Get GPU Caps Viewer from https://www.geeks3d.com/dl/show/718, sha256sum of
that zip should be
fcdd0992fdd36660a7561d6d5a9d3e64e653c7d5cc5cae2856634f6a003ae731. Unzip it
somewhere and run `wine GPU_Caps_Viewer.exe`. If everything went right, it
should see Nvidia GPU, load NVAPI, then load NVML, make a few NVML calls and
cause a segfault after one such call returns.
Attached is the backtrace made with Wine 8.9 from Arch Linux repositories.
Unfortunately, the application seems to enter the problematic code path only
when all the mentioned libraries are present, which actually suggests another
possibility: that this is an application bug that simply went undetected on
Windows because there is no 32-bit `nvml.dll` provided by Nvidia. I have no
idea if this works on Windows, or if it ever worked at all, but I find it
curious that it used to work in Wine (when my wine-nvml wrapper was present)
and it doesn't anymore.
--
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=54010
Bug ID: 54010
Summary: Star Citizen has low fps
Product: Wine
Version: 7.19
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Created attachment 73588
--> https://bugs.winehq.org/attachment.cgi?id=73588
Star Citizen - Wine 7.19 output (600Mb uncompressed)
Hello,
I have low FPS in the game 'Star Citizen'.
After reading various reports on the web, here is what I did to make the game
start at least:
- Use wine 7.19 (I didn't try any other version; staging was not needed);
- install arial with winetricks (fixes missing text in launcher);
- set windows version to 8.1 (to avoid an annoying error message about
unsupported config);
- Disable Easy Anti-cheat (to avoid an error message preventing the game from
starting);
- Increase vm.max_map_count (from 65530 to 16777216; to avoid a crash at the
loading screen before the game reaches the main menu).
Although the game is in alpha stage and not optimized, some users have reported
good performance using Wine-based third party projects (namely lutris with
custom runner + dxvk), so I think this is not an application issue.
I was unable to compare performance with DXVK as my OS is out of date for that
(DXVK requires Vulkan 1.3, Debian 8 jessie ships Vulkan 1.2).
The recommended minimum memory is 16Gb. My system has 16Gb, but the game
consumes all memory, plus a few GB of swap and starts 'trashing' to the disk
(not an SSD). I don't think this is the cause of the low FPS however.
Debian GNU/Linux 8 (jessie) 64 bits
Intel® Core™ i7-4930K CPU @ 3.40GHz × 12
NVIDIA GeForce RTX 2070/PCIe/SSE2
The current Star Citizen Free Fly event ends Nov 30. I will not be able to test
the application further until the next event. This bug report is mostly to
remind me of the issue.
Regards.
--
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=45477
Bug ID: 45477
Summary: the forest - settings not saved
Product: Wine
Version: 3.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bronsonmathews(a)gmail.com
Distribution: ---
The settings for this game are stored in the registry. And when changing the
settings in game they are not saved into the registry.
Settings are located at the following location:
HKEY_CURRENT_USER\Software\SKS\TheForest
--
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=41429
Bug ID: 41429
Summary: The Forest: Game crashes if started from Steam
Product: Wine
Version: 1.9.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sworddragon2(a)aol.com
Distribution: ---
Created attachment 55803
--> https://bugs.winehq.org/attachment.cgi?id=55803
Terminal output
If The Forest gets started from Steam the game shows its configuration dialog
and on clicking "Play!" the game crashes after a few seconds. But if the game
gets directly started all is working fine no matter if Steam is already running
or not (and if the multiplayer works too).
--
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.