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.
https://bugs.winehq.org/show_bug.cgi?id=41304
Bug ID: 41304
Summary: Obscure Steam version freezes at launch with 100% CPU
usage
Product: Wine
Version: 1.9.18
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ikk_pl(a)yahoo.co.uk
Distribution: ---
Created attachment 55632
--> https://bugs.winehq.org/attachment.cgi?id=55632
Log after starting steam, attempting to launch Obscure, killing it and quitting
Steam
When trying to launch the game Obscure from Steam, it freezes, using 100% of
the CPU without launching any windows.
--
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=55141
Bug ID: 55141
Summary: virtual desktop not rendering with some dual monitor
setups (regression: 8.10 -> 8.11)
Product: Wine
Version: 8.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: kolAflash(a)kolahilft.de
Distribution: ---
When having a dual monitor setup and the right monitor is primary, the virtual
desktop is not rendering.
First bad commit:
https://gitlab.winehq.org/wine/wine/-/commit/9b7669592d6f8b40976b571b70f854…
I just had another problem with the virtual desktop. Is there maybe some
relation?
https://bugs.winehq.org/show_bug.cgi?id=55046
--
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=52168
Bug ID: 52168
Summary: League of Legends: RiotClientUxRender.exe crash
Product: Wine
Version: 6.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: joseskvolpe(a)gmail.com
Distribution: ---
Created attachment 71216
--> https://bugs.winehq.org/attachment.cgi?id=71216
Shell debug log
League of Legends launcher crashes right after it's installed
Tried on plain Wine 6.22, running with Wine Mono 7.0.0
Operating system: Manjaro Linux
Kernel: Linux 5.10.82-1-MANJARO
GPU: Intel HD Graphics 620
RAM: 12GB
Driver: Open-source Mesa
Procedure:
*Download League of Legends: www.leagueoflegends.com
*Install it
*Open launcher (RiotClientServices.exe)
There's 3 different crash logs that is generated after the crash, i'm attaching
all of them
--
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=49373
Bug ID: 49373
Summary: League of Legends crashes at game start (wine 5.10
regression)
Product: Wine-staging
Version: 5.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aguertin+wine(a)aguertin.net
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Regression SHA1: c96ef78b6d6d9184d8ec4cd18924a3049d388583
Distribution: ---
League of Legends crashes at game start. This is a regression from
c96ef78b6d6 ntdll: Move the virtual memory functions to the Unix library.
...or more likely the staging patch rebase needed to accommodate it.
STEPS TO REPRODUCE A WORKING LOL
1) Check out wine 7c32b2dd936
2) Apply staging 6387991c, making the necessary merges
*) (May be an easier merge workflow if you check out wine 3c86adab766, apply
staging 6387991c, and then cherry-pick wine b4a868b8add..7c32b2dd936)
3) Apply patch from Bug 49025 comment 14
4) Apply patch from Bug 47198 comment 95
STEPS TO REPRODUCE A BROKEN LOL
1) Check out wine c96ef78b6d6
2) Apply staging a4d98c48
*) (Beware of Bug 49326! Apply with -W ntdll-ForceBottomUpAlloc. To do that,
you will need to undo an update to the ntdll-NtQueryVirtualMemory patch: `git
checkout 6387991c --
patches/ntdll-NtQueryVirtualMemory/0008-ntdll-Resolve-drive-symlinks-before-returning-sectio.patch`)
3) Apply patch from Bug 49025 comment 14
4) Apply patch from Bug 47198 comment 95
These two sets of steps put you one wine commit apart, with a minimal set of
staging and other changes. This demonstrates that the regression comes from
either c96ef78b6d6 or the staging changes related to it.
There is no relevant console output.
System info:
Gentoo
x86_64
GCC 9.3.0
For testing, please be aware that you do not need to log in to LoL. You can
just run C:\Riot Games\League of Legends\Game\League of Legends.exe - if it
pops up a message that you need to log in first, it is working; if it pops up a
System Error message, it is broken. This makes testing much faster.
--
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=45934
Bug ID: 45934
Summary: League of legends : No sound in-game
Product: Wine-staging
Version: 3.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: scrimekiler(a)yahoo.fr
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 62462
--> https://bugs.winehq.org/attachment.cgi?id=62462
WINEDEBUG=-all,+dsound
When starting league of legends, the sound works, even in champion select.
But after the game has loaded, there is no more sound.
Using alsa-lib-1.1.6-r1, tried with 1.1.2, the 32 bits version are also
installed.
Kernel : 4.14.8-gentoo-r1
Please tell me if you need additionnal logs or specific WINEDEBUG channels
--
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=45706
Bug ID: 45706
Summary: League of Legends fails to reconnect
Product: Wine-staging
Version: 3.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ads200002(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
League of Legends fails to reconnect after a disconnection in game.
When in game, if you disconnect, you get a 'Reconnecting to game' box come up
with a pulsating progress bar. Even upon reconnecting to the Internet, however,
the game fails to automatically reconnect as it has done before the anti-cheat
was implemented.
Lutris 0.4.14 with Wine Staging 3.14+110a6f6 esync 5898a69 on Ubuntu 18.04
I'm sorry I'm not using a more vanilla environment, if someone with vanilla
Wine Staging can't reproduce this bug then please close it.
--
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.