https://bugs.winehq.org/show_bug.cgi?id=44939
Bug ID: 44939
Summary: WININET crashes GTAV Launcher
Product: Wine
Version: 3.0
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: xinput
Assignee: wine-bugs(a)winehq.org
Reporter: jhntipo(a)gmail.com
While launching GTAV from steam, steam crashes (and closes) in the background
and GTAV shows the crashing dialogue. According to
https://appdb.winehq.org/objectManager.php?sClass=version&iId=32054&iTestin…,
the crash is caused by:
fixme:wininet:HTTPREQ_ReadFile these dwFlags aren't implemented: 0x4
--
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=47097
Bug ID: 47097
Summary: The Superlatives: Shattered Worlds Demo (from Steam)
crashes inside RegisterDeviceNotificationW
Product: Wine
Version: 4.7
Hardware: x86
URL: https://store.steampowered.com/app/1050210/The_Superla
tives_Shattered_Worlds/
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: Debian
Created attachment 64295
--> https://bugs.winehq.org/attachment.cgi?id=64295
crash log
As the title says, demo is free to download.
Yet another one, adding DECLSPEC_HOTPATCH (see below) works around the bug.
I`ll send a patch.
diff --git a/dlls/user32/misc.c b/dlls/user32/misc.c
index d28cd9fd05..bd4795a346 100644
--- a/dlls/user32/misc.c
+++ b/dlls/user32/misc.c
@@ -363,7 +363,7 @@ DWORD WINAPI RegisterTasklist (DWORD x)
*
* See RegisterDeviceNotificationW.
*/
-HDEVNOTIFY WINAPI RegisterDeviceNotificationA(HANDLE hnd, LPVOID notifyfilter,
DWORD flags)
+HDEVNOTIFY WINAPI DECLSPEC_HOTPATCH RegisterDeviceNotificationA(HANDLE hnd,
LPVOID notifyfilter, DWORD flags)
{
FIXME("(hwnd=%p, filter=%p,flags=0x%08x) returns a fake device
notification handle!\n",
hnd,notifyfilter,flags );
@@ -393,7 +393,7 @@ HDEVNOTIFY WINAPI RegisterDeviceNotificationA(HANDLE hnd,
LPVOID notifyfilter, D
*| DEVICE_NOTIFY_WINDOW_HANDLE - hRecipient is a window handle
*| DEVICE_NOTIFY_SERVICE_HANDLE - hRecipient is a service status handle
*/
-HDEVNOTIFY WINAPI RegisterDeviceNotificationW(HANDLE hRecipient, LPVOID
pNotificationFilter, DWORD dwFlags)
+HDEVNOTIFY WINAPI DECLSPEC_HOTPATCH RegisterDeviceNotificationW(HANDLE
hRecipient, LPVOID pNotificationFilter, DWORD dwFlags)
{
FIXME("(hwnd=%p, filter=%p,flags=0x%08x) returns a fake device
notification handle!\n",
hRecipient,pNotificationFilter,dwFlags );
--
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=39755
Bug ID: 39755
Summary: Spintires lags when driving through mud
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: klavkalashj(a)gmail.com
Distribution: ---
Created attachment 53029
--> https://bugs.winehq.org/attachment.cgi?id=53029
Console output from the point of starting game, enter map, driving around to
check bug and then exiting game
When standing still or driving on asphalt or grass, the game runs fine and at a
high frame rate. However, as soon as the wheels enter mud or rocky mud, the
game slows to a crawl. This happens on both highest and lowest graphics
settings. The game works fine in Windows.
System specs:
Intel cpu, i2500k
Nvidia gfx, 970GTX with newest proprietary driver
8gb ram
--
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=47021
Bug ID: 47021
Summary: Malformed entry 58 in list file /etc/apt/sources.list
(Component)
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jfairbanks37(a)gmail.com
Distribution: ---
trying to update wine in ubuntu 18.04 and ran into problems with repository
read.
--
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=46797
Bug ID: 46797
Summary: Wine does not build correctly on armv8l platforms
Product: Wine
Version: unspecified
Hardware: aarch64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: calcprogrammer1(a)gmail.com
Distribution: ---
I'm attempting to compile Hangover (https://github.com/AndreRH/hangover) for my
Raspberry Pi 3 running Gentoo aarch64, but I decided that since my Galaxy Note
8 has a better processor, I could use it for the build process. The Note 8 (at
least the version that can be unlocked) has a 64-bit Exynos processor. I
rooted it and was able to mount my Raspberry Pi's SD card in a USB reader and
chroot into the Gentoo installation.
While Hangover isn't upstream Wine, I looked at the upstream Wine's
configuration script and it has the same issues as the version used in
Hangover.
I cd'd to the Hangover directory (same as I have done on the Pi) and tried to
build. The build failed even though it worked on the Pi. The difference seems
to be that the Note 8's kernel reports "armv8l" while the Pi reports "aarch64".
Both are running the 64-bit Gentoo installation just fine, but the armv8l
architecture string breaks the configure script on Wine. Instead of hitting
the aarch64 configuration steps for 64-bit, it hits the 32-bit arm* steps and
fails.
I manually edited the existing instances of "arm*" in the configure script to
"armv7*" and added conditions for "armv8*" anywhere that aarch64 is used. This
seems to get further in the build and is still building on my phone at this
moment.
I'm not sure what the exact distinction between armv8l and aarch64 is, but I do
know armv8l kernel seems to be able to run 64-bit code.
--
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=46765
Bug ID: 46765
Summary: Ori and The Blind Forest - Definitive Edition fails to
start on Ubuntu
Product: Wine
Version: 4.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ahmed.com(a)protonmail.com
Distribution: ---
Created attachment 63774
--> https://bugs.winehq.org/attachment.cgi?id=63774
WINEDEBUG=warn+all
Ori and The Blind Forest - Definitive Edition fails to start on Kubuntu 18.10
or Linux Mint 19.1 but run without any problems on Manjaro Linux 18.03.
--
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=46764
Bug ID: 46764
Summary: Cuphead fails to start on Ubuntu
Product: Wine
Version: 4.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ahmed.com(a)protonmail.com
Distribution: ---
Created attachment 63773
--> https://bugs.winehq.org/attachment.cgi?id=63773
WINEDEBUG=warn+all
Cuphead fails to start on Kubuntu 18.10 or Linux Mint 19.1 but run without any
problems on Manjaro Linux 18.03
--
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=47025
Bug ID: 47025
Summary: wine cannot run exe created with winegcc: "Bad EXE
Format"
Product: Wine
Version: 4.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jeffersoncarpenter2(a)gmail.com
Distribution: ---
Full steps to reproduce from cloning the Wine source tree:
$ git clone git://source.winehq.org/git/wine.git
$ mkdir wine64_build
$ cd wine64_build
$ ../wine/configure --enable-win64
$ make
$ cd ..
$ mkdir test_program
$ cd test_program
$ echo 'int main() { return 0; }' > main.c
$ PATH="$PATH:../wine64_build/tools/winebuild/"
/home/rofl/wine64-build-debug/tools/winegcc/winegcc
-L/home/rofl/wine64-build-debug/dlls/advapi32
-L/home/rofl/wine64-build-debug/dlls/user32
-L/home/rofl/wine64-build-debug/dlls/ntdll/
-L/home/rofl/wine64-build-debug/dlls/winecrt0
-L/home/rofl/wine64-build-debug/dlls/kernel32
-L/home/rofl/wine64-build-debug/libs/wine/ main.c -o main
$ ../wine64_build/wine64 ./main.exe
On my machine, the last command outputs
wine: Bad EXE format for Z:\home\rofl\test_program\main.exe.
Is this expected behavior meaning I'm using winegcc incorrectly, or is this a
bug?
--
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=47094
Bug ID: 47094
Summary: Foobar2000 memory leak
Product: Wine
Version: 4.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: just4steam778(a)gmail.com
Distribution: ---
Created attachment 64291
--> https://bugs.winehq.org/attachment.cgi?id=64291
Terminal output
I have an issue with foobar2000 taking up 15-25% of CPU power and 0.4-1GB of
RAM and eventually crashing. This happens soon after launch even when it's idle
as a fresh installation. I've also tried installing it in a 32-bit Windows XP
prefix.
I'm running foobar2000 1.4.3 on Arch Linux.
--
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.