http://bugs.winehq.org/show_bug.cgi?id=26269
Summary: BioShock 2: Loss of keyboard input on loading screen
Product: Wine
Version: 1.3.14
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mgavl69(a)juno.com
Created an attachment (id=33488)
--> (http://bugs.winehq.org/attachment.cgi?id=33488)
trace +keyboard
On the inital 'New Game' loading screen you cannot use the space bar to
continue.
Keyboard and mouse input is recognised correctly when adjusting settings in the
menus.
Wine version 1.3.14-git
Xserver v1.10.0
--
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=46203
Bug ID: 46203
Summary: Renaming a file to a different capitalization of
itself doesn't work
Product: Wine
Version: 3.21
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: gabrielopcode(a)gmail.com
Distribution: ---
Created attachment 62878
--> https://bugs.winehq.org/attachment.cgi?id=62878
Example fix + tests
Renaming a file in Wine to the same name but in different capitalization
doesn't work. For example, renaming "foobar" to "FooBar" doesn't work and is
basically a no-op. It works under Windows.
This is actually very annoying in practice when using file managers or file
browsers or anything else with Wine and trying to do that, so it's not just an
academic fix, but a practical one.
This should be special cased because now it finds that the target filename
already exists in the original case (which is good for other cases but not this
one) and thus uses that, effectively being a no-op.
Example patch + tests attached to fix this issue. It will probably need some
refinement, but it shouldn't break any current behavior except for fixing this
issue.
--
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=29582
Bug #: 29582
Summary: Star Wars Battlefront (I and II) "Loading" screen very
slow.
Product: Wine
Version: 1.3.36
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: daniel.santos(a)pobox.com
Classification: Unclassified
The "Loading" screen takes so long (in SW Battlefront II) that I can't connect
to network games because when it finally finishes loading the level, I get a
message that says "lost connection to host" (presumably because it timed out).
I haven't timed it, but it seems to be about 2 minutes, whereas running it on
windows takes roughly 5-10 seconds.
WINEDEBUG=+relay did show that PeekMessageA was being called about 2700 times a
second (probably not a big deal) but then GetForgroundWindows was being called
right after that (a wineserver call). I suspected that as a possible culprit,
but haven't dug in too deeply yet.
I'll do some profiling on this later and try to get some better info. Maybe I
can find a hack-around to positively isolate the cause.
--
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=46301
Bug ID: 46301
Summary: TimeShift DEMO: freezes during the startup
Product: Wine
Version: 4.0-rc2
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wylda(a)volny.cz
Distribution: ---
Created attachment 63025
--> https://bugs.winehq.org/attachment.cgi?id=63025
console log
TimeShift Demo freezes during the startup immediately after "Processing
Shaders" phase (Loading cca 80%).
$ du -h timeshift_sp_us_demo.exe
984M timeshift_sp_us_demo.exe
$ sha1sum -b timeshift_sp_us_demo.exe
efe37b94ea907c5d663b8b5bebe934945d814e31 *timeshift_sp_us_demo.exe
--
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=31046
Bug #: 31046
Summary: Wine advertises 32bit depth buffer, behaves like 24bit
Product: Wine
Version: 1.5.7
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: billy65bob(a)gmail.com
Classification: Unclassified
Created attachment 40757
--> http://bugs.winehq.org/attachment.cgi?id=40757
title screen: 32-bit Z buffer on wine (DirectX9 Hardware)
Title says it all really.
I'm currently playing a game in PCSX2 (Persona 4) and frankly it looks really
bad.
According to the application, wine is reporting a 32bit Z-buffer, but amusingly
it behaves precisely how a 24bit buffer behaves in windows with this
application.
--
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=46501
Bug ID: 46501
Summary: GFWL: fails to verify cert file
Product: Wine
Version: 3.20
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bcrypt
Assignee: wine-bugs(a)winehq.org
Reporter: lilyrivers48(a)gmail.com
Distribution: ---
Created attachment 63349
--> https://bugs.winehq.org/attachment.cgi?id=63349
Backtrace of Universe at War Earth Assault GFWL startup
The bcrypt functions don't work for verifying the cert
Wintrust fails to get information from the CAT file
--
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=48291
Bug ID: 48291
Summary: Detroit: Become Human crashes on launch
Product: Wine
Version: 5.0-rc1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sashok.olen(a)gmail.com
Distribution: ---
Created attachment 65990
--> https://bugs.winehq.org/attachment.cgi?id=65990
backtrace
For now I've only uploaded a backtrace, but it's a bit unusual:
0x0000000000000000: -- no code accessible --
Let me know if you need anything else.
--
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=44740
Bug ID: 44740
Summary: "A Hat in Time" any x360 joystick's sticks seems to be
stuck in upper right corner.
Product: Wine
Version: 3.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: xinput
Assignee: wine-bugs(a)winehq.org
Reporter: spam(a)hjkos.com
Distribution: ---
Game: https://appdb.winehq.org/objectManager.php?sClass=version&iId=36033
Game recognizes joystick correctly, buttons work as expected, however game sees
analog stick as if it's stuck in some corner, making character run in circles.
Jiggling the joystick makes it slightly change direction, but game is still
unplayable this way. Joystick appears to be working correctly - it works fine
in Linux games, and joystick control panel also shows correct positions. I
tried two joysticks:
Logitech F710 (XInput mode)
Steam Controller (sc-controller x360 joystick emulation)
both yield same result.
dumbxinputemu makes game see two controllers, one real and one emulated by
dumbxinputemu, and seems this time around emulated one works normally, but the
real one keeps overriding it, so character just changes directions frequently
and in with drastic direction changes.
Also, Logitech F710 has DirectInput mode, which has working sticks, however it
has weird bindings and i am unable to rebind it in-game.
--
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=44856
Bug ID: 44856
Summary: DOOM 2016 is no longer working
Product: Wine
Version: 3.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: justinrun(a)gmail.com
Distribution: ---
Created attachment 60912
--> https://bugs.winehq.org/attachment.cgi?id=60912
crash log
A new update to the DOOM 2016 game on steam is no longer working on wine. I
tested this in wine 3.4, 3.0, and 2.21. I also tried it with both OpenGL and
Vulkan rendering. I also tried it with nvidia drivers 390.48 and 384.130.
It always just starts up to a black screen. I have to kill the process to close
it. This did not happen prior to the most recent game update.
I also tried adding a launch argument to disable the intro video in case
playing it was the issue. It still did not work.
I attached a crash log.
--
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.