https://bugs.winehq.org/show_bug.cgi?id=45363
Bug ID: 45363
Summary: CreateToolhelp32Snapshot(TH32CS_SNAPMODULE, 0) return
empty snapshot
Product: Wine-staging
Version: 3.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sr-tream(a)yandex.ru
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
function CreateToolhelp32Snapshot sometimes returns an empty snapshot, while in
Windows this function works correctly
--
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=40794
Bug ID: 40794
Summary: PlayOnline Viewer crashes when using a game
controller.
Product: Wine
Version: 1.8.2
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: valkerie.asura(a)icloud.com
Created attachment 54707
--> https://bugs.winehq.org/attachment.cgi?id=54707
PlayOnline Viewer Backtrace
PlayOnline Viewer randomly crash when using gamepad input.
--
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=38015
Bug ID: 38015
Summary: El Matador: problem with rendering shadows
Product: Wine
Version: 1.7.35
Hardware: x86
URL: http://www.gamershell.com/download_15089.shtml
OS: Linux
Status: NEW
Keywords: download
Severity: minor
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
Distribution: ---
Created attachment 50655
--> https://bugs.winehq.org/attachment.cgi?id=50655
terminal output
Both indoor and outdoor shadows are rendered incorrectly in the game as you can
see on the attached screenshot or you can reproduce the problem in the demo
version.
The game uses cascaded shadow maps..if that helps anything for the d3d gurus.
After some googling I found that old Nvidia Windows drivers had problems with
rendering shadows in the game, but Nvidia fixed the issue in their Windows
drivers ages ago:
https://forums.geforce.com/default/topic/365860/pc-games/el-matador-gf8800-…
Without going into speculation, shadows are rendered in a similar way in Two
Worlds 2 and in Ghost Recon: Advanced Warfighter 1 & 2 on my system.
Fedora 21
Nvidia binary drivers 340.76
--
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=49802
Bug ID: 49802
Summary: Crash at AfxBeginThread of x64 apps on macOS when
built with VS2019
Product: Wine
Version: 5.16
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: reinhold.hoffmann(a)hotmail.com
Created attachment 68117
--> https://bugs.winehq.org/attachment.cgi?id=68117
Samples to demonstrate the issue
Our x64 apps built with Visual Studio 2010 (VS2010) run on macOS for a long
time. We recently have started a project to move to Visual Studion 2019
(VS2019). The same x64 app which works fine when built with VS2010 crashes on
macOS when it is built with VS2019. The crash occurs when the MFC function
AfxBeginThread is called. Static linking is used for linking the MFC and other
libs.
After a very painful research we identified that a simular report has been made
in Nov. 2019 in the Wineskin area
(see https://github.com/Gcenx/WineskinServer/issues/22).
The reporter said "I ended up replacing the AfxBeginThread call with a call to
CreateThread which works fine on all versions." We did the same thing with the
same result. Replacing AfxBeginThread by CreateThread works fine with VS2019.
However, according to
https://stackoverflow.com/questions/21718674/difference-between-afxbeginthr…
a replacement of AfxBeginThread by CreateThread is not really recommended when
MFC is used.
The crash happens on all macOS versions with Wine 5.4, 5.7 and 5.16 (we took
5.16 from Gcenx (https://github.com/Gcenx/macOS_Wine_builds)). On Windows and
Linux the VS2019 app runs fine. Further, the Win32 equivalent app runs fine on
macOS.
In summary:
A crash happens for AfxbeginThread in an x64 app on macOS with Wine 5.4, 5.7,
5.16.
We did a deeper dive and found that the crash happens inside AfxbeginThread,
module Thread.cpp inside the function __acrt_get_begin_thread_init_policy.
See address:
0001:001ab7cc __acrt_get_begin_thread_init_policy 00000001401ac7cc f
libucrt:win_policies.obj
According to the backtrace.txt (attached) the exception happens when reading
from a 32 bit address. This sounds strange to me for a x64 app.
Any help is highly appreciated.
Reinhold
==========================================================================
As a C++ sample I have compiled a trivial app which AfxBeginThread which
demonstrate the problem.
In the attached zip file you can find
backtrace.txt
Test_of_AfxBeginThread_VS2019.exe
Test_of_AfxBeginThread_VS2010.exe
The code and project files for VS2010 and VS2019 can be downloaded from
www.notation.com/download/Wine/Bugzilla/Project_Files_AfxBeginThread_sample…
--
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=43937
Bug ID: 43937
Summary: wine-mono does not have an arm build
Product: Wine
Version: 2.19
Hardware: arm
OS: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: ---
This is blocked until mingw64 supports arm targets in a release, but for now,
dlls/mscoree/tests/* fails, due to missing mono.
--
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=51061
Bug ID: 51061
Summary: Solid Edge 2021 Academic Edition: can't create new
file
Product: Wine
Version: 6.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aerkiaga3(a)gmail.com
Distribution: ---
Created attachment 69921
--> https://bugs.winehq.org/attachment.cgi?id=69921
Last few lines of output
Trying to create a new file results in the application halting for a few
seconds and then closing (not crashing).
The points in time at which the new file creation dialog was closed by
accepting the selected input, and at which the application hung for several
seconds, are marked by double presses of the Enter/Return key in the console
output, which results in the prompt appearing twice.
Version was 6.7-staging.
--
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=33967
Bug #: 33967
Summary: Mavis Beacon 8: Page fault on all typing lessons/games
Product: Wine
Version: 1.6-rc4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gaming4jc2(a)yahoo.com
Classification: Unclassified
Created attachment 45118
--> http://bugs.winehq.org/attachment.cgi?id=45118
Wine 1.6-rc4 crash log
This is version 8 of Mavis Beacon Teaches Typing and it has a pagefault on all
lessons and games. Attached is the log running first in WinXP mode and then in
Win98 with backtrace.
--
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=51039
Bug ID: 51039
Summary: foobar2000 + iPod Manager does not recognize iPod
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: justice.hoffpauer(a)gmail.com
Distribution: ---
When mounting iPod and attempting to click any related options in foobar2000
(File > iPod > Eject/Load Library), an error window pops up simply saying "No
iPod found."
--
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=49075
Bug ID: 49075
Summary: foobar2000 reports 'No CD drives found.' because
GetDriveTypeW returns DRIVE_FIXED for audio CD
Product: Wine
Version: 5.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: spoon0042(a)hotmail.com
Distribution: ---
Created attachment 67048
--> https://bugs.winehq.org/attachment.cgi?id=67048
foobar2000 log +volume
Summary should be self-explanatory. ;) Attached a log with +volume starting
foobar2000 and selecting File -> Open audio CD. Relevant line would be
0033:trace:volume:GetDriveTypeW L"\\\\.\\D:\\" -> 3
Confusingly running winecfg with +volume correctly finds an audio CD. (And
incorrectly an extra one?)
0009:trace:volume:GetVolumeInformationW L"\\??\\D:\\": found audio CD
0009:trace:volume:GetVolumeInformationW L"\\??\\E:\\": found audio CD
Hacking GetDriveTypeW to return 5 for D: things work as expected. Can play a
CD, fetch tags, rip.
--
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=44172
Bug ID: 44172
Summary: Side scrolling via trackpad in foobar2000 skips tracks
Product: Wine
Version: 3.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: de.wood(a)gmail.com
Distribution: ---
Created attachment 59937
--> https://bugs.winehq.org/attachment.cgi?id=59937
WINEDEBUG=trace+cursor log observing the behaviour
Scrolling to the left or right in foobar2000 will skip to the previous/next
track in the playlist (it doesn't do this in windows). I can isolate up/down
scrolling specifically by using edge scrolling (trackpad) or connecting a
mouse, and the skipping doesn't occur.
Attached is a log running the program and observing the skipping with
WINEDEBUG=trace+cursor; button 4 is either up or down while button 6 is either
left or right.
Machine is a laptop running fedora 27. Program is the latest version 1.3.17
final.
--
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.