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=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=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.