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=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=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.
https://bugs.winehq.org/show_bug.cgi?id=42584
Bug ID: 42584
Summary: League of Legends: LeagueClient.exe hangs at startup
logo
Product: Wine
Version: 2.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: hevanen(a)googlemail.com
Distribution: ---
Created attachment 57504
--> https://bugs.winehq.org/attachment.cgi?id=57504
Full console output
When launching LeagueClient.exe, the application often hangs at the "League of
Legends" logo. This happens about 2 out of 3 times on average, but sometimes it
takes up to 10 attempts to get it to run.
The terminal shows an endless repeat of errors like the following:
err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c:
HEAP.critSection" wait timed out in thread 005c, blocked by 007e, retrying (60
sec)
err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c:
HEAP.critSection" wait timed out in thread 0051, blocked by 007e, retrying (60
sec)
err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c:
HEAP.critSection" wait timed out in thread 008d, blocked by 007e, retrying (60
sec)
err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c:
HEAP.critSection" wait timed out in thread 0052, blocked by 007e, retrying (60
sec)
err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c:
HEAP.critSection" wait timed out in thread 0060, blocked by 007e, retrying (60
sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bcebaa0 "loader.c:
loader_section" wait timed out in thread 007d, blocked by 007c, retrying (60
sec)
err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c:
HEAP.critSection" wait timed out in thread 007c, blocked by 007e, retrying (60
sec)
err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c:
HEAP.critSection" wait timed out in thread 0063, blocked by 007e, retrying (60
sec)
--
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.