https://bugs.winehq.org/show_bug.cgi?id=48929
Bug ID: 48929
Summary: Yandere simulator crashes can't even open MAC CATALINA
Product: Wine
Version: unspecified
Hardware: Other
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bdinitha2(a)gmail.com
Created attachment 66894
--> https://bugs.winehq.org/attachment.cgi?id=66894
this is the log I got
Hey so im using a Mac book bro 2017 13 inch and I upgraded my Mac to
Catalina(10.15.3)recently. So after that I couldn't run 32 bit apps on this
Mac. I downloaded Wine64 using Homebrew and I had installed the latest version
of Yandere simulator. As explained in tutorials I typed the command to open the
app " Wine64 YandereSimulator.exe" It takes like 2 seconds and then I get a
issue saying "UnityCrashHandler64.exe" has encountered a serious issue and this
program needs to be closed". It also said this can be caused by a deficiency in
wine. Please I wanna play this game so bad I hope I get a fix. I've attached
the log report I got when wine crashed.
--
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=45391
Bug ID: 45391
Summary: winehq.org is distributing compiled LGPL code packages
but withholding their sources
Product: Packaging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: forestcode(a)ixio.org
CC: michael(a)fds-team.de, sebastian(a)fds-team.de
Distribution: ---
The source code tarballs and package build scripts for winehq's ubuntu and
debian packages are not published. They are not where they are supposed to be
according to the official debian/ubuntu sources.list file (the deb-src entry
that gets created when someone follows the official apt-add-repository
instructions), they don't seem to be referenced anywhere else obvious, and
nobody at the wine project has been forthcoming about how to get them.
[1][2][3]
So, winehq.org is distributing binary packages without making their sources
available. This makes it impossible for the people using those packages to
audit the code, reproduce the packages, test patches on known-good packaged
versions, or port them to different OS releases (the latter leading to issues
like bug 45085).
>From what I can tell, this is also likely an LGPL violation:
"4. You may copy and distribute the Library (or a portion or derivative of it,
under Section 2) in object code or executable form under the terms of Sections
1 and 2 above provided that you accompany it with the complete corresponding
machine-readable source code"
What will it take to remedy this situation?
[1] Notice the absence of an answer in this thread:
https://www.winehq.org/pipermail/wine-devel/2018-May/127507.html
[2] Nobody had an answer for me on the two occasions when I asked on
#winehackers irc this week.
[3] Nobody responded when I emailed the package maintainers listed at
https://wiki.winehq.org/Download
--
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=42908
Bug ID: 42908
Summary: Monopoly (2000) crashes on launch
Product: Wine
Version: 2.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Distribution: ---
Created attachment 58049
--> https://bugs.winehq.org/attachment.cgi?id=58049
backtrace
Crashes trying to read 0x0000000. Backtrace attached.
--
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=49001
Bug ID: 49001
Summary: www.sharescope.co.uk Program Error Details box pops up
on start. Program stalls in download of data. Try to
start the program again and it stalls further along
the data download according to the progress bar. Start
again and the download process completes
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: a.hardiestorey(a)btinternet.com
Distribution: ---
Created attachment 66976
--> https://bugs.winehq.org/attachment.cgi?id=66976
Program Error Detail Log
Failure to load and run on first start up. Requires 2 or 3 attempts to download
the information before the application will run.
--
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=45936
Bug ID: 45936
Summary: IW4x crashes on keyboard input
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: huematrix(a)mailinator.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 62464
--> https://bugs.winehq.org/attachment.cgi?id=62464
Log
Upon pressing a key in IW4x (A Call of Duty: Modern Warfare 2 client), the
program crashes. Full log below.
--
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=48560
Bug ID: 48560
Summary: Default color scheme
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: depositmail(a)mail.ru
Distribution: ---
Created attachment 66374
--> https://bugs.winehq.org/attachment.cgi?id=66374
Breeze color scheme
Good afternoon!
Is it possible to make the default "Breeze" color scheme in Wine?
(Files are attached).
Link to the resource:
https://store.kde.org/p/1259774/
--
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=39415
Bug ID: 39415
Summary: Make configuration settings accessible through the
website
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Currently the way to change a configuration setting is to send a patch to
wine-patches and have Alexandre apply it. This is the case for instance for all
the VM host configuration settings ($MaxRevertingVMs,
$MaxRevertsWhileRunningVMs, etc.), but also $JobPurgeDays, $RegistrationQ, etc.
This is not very practical and prevents experimentation or quickly adjusting
the settings when a problem arises.
Instead these should be stored in a Parameters table and be accessible through
an administrator-only section of the website.
--
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=39416
Bug ID: 39416
Summary: Many settings should be per VM host
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The following global settings should in fact be customizable on a per VM host
basis:
* $MaxRevertingVMs - Hosts with SSDs may be able to handle multiple reverts in
parallel.
* $MaxRevertsWhileRunningVMs - Again this may depend on disk speed and QEmu
version.
* $MaxActiveVMs - Depends on disk and CPU speed, number of cores, etc.
* $SuiteTimeout & $SingleTimeout - Might need to be adjusted based on the CPU
speed.
* $BuildTimeout & $ReconfigTimeout - Might need to be adjusted based on the CPU
speed. Fortunately we can currently only have one build VM so that's not too
much of an issue.
One way to do so would be to introduce a VMHosts table storing the settings for
each VM host (see the schema attachment of bug 39412). VMs (VMInstances really)
would then be linked to the relevant VM host so to indicate which set of
constraints apply.
Note that this would be different from the handling of the truly global
settings described in bug 39415.
--
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=48772
Bug ID: 48772
Summary: Attack on Titan 2 continually clips the cursor,
resulting in incorrect cursor events
Product: Wine
Version: 5.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: qsniyg(a)mail.com
Distribution: ---
For example:
...
0009:trace:cursor:SetCursor 0x20046
0009:trace:cursor:ClipCursor Clipping to (-3,-12)-(1923,1093)
0009:trace:cursor:ungrab_clipping_window no longer clipping
0009:trace:cursor:ClipCursor Clipping to (-3,-12)-(1923,1093)
0009:trace:cursor:ungrab_clipping_window no longer clipping
0009:trace:cursor:ClipCursor Clipping to (-3,-12)-(1923,1093)
0009:trace:cursor:ungrab_clipping_window no longer clipping
...
0009:trace:cursor:SetCursor 0x20046
0009:trace:cursor:X11DRV_MotionNotify hwnd 0x10052/4400003 pos 963,543 is_hint
0 serial 6080
0009:trace:cursor:ClipCursor Clipping to (-3,-12)-(1923,1093)
0009:trace:cursor:ungrab_clipping_window no longer clipping
0009:trace:cursor:X11DRV_MotionNotify hwnd 0x10052/4400003 pos 924,521 is_hint
0 serial 6083
00ce:trace:cursor:X11DRV_SetCursorPos warped to 960,540 serial 6413
001f:trace:cursor:X11DRV_EnterNotify hwnd 0x10020/3a0000a pos 921,509 detail 2
0009:trace:cursor:ClipCursor Clipping to (-3,-12)-(1923,1093)
0009:trace:cursor:ungrab_clipping_window no longer clipping
0009:trace:cursor:ClipCursor Clipping to (-3,-12)-(1923,1093)
0009:trace:cursor:ungrab_clipping_window no longer clipping
...
Since the cursor is continually warped to the center of the screen, when
ungrab_clipping_window calls XUnmapWindow, it reports to the game that the
cursor has moved back to the center, resulting in the common "camera refuses to
move" bug.
Although the documentation[1] states that XUnmapWindow does nothing if called
on a window that's already unmapped, when adding a variable to keep track of
whether it's mapped or not and only unmapping it when needed, the issue is
fixed.
[1] https://tronche.com/gui/x/xlib/window/XUnmapWindow.html
--
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.