https://bugs.winehq.org/show_bug.cgi?id=56761
Bug ID: 56761
Summary: So when I install Blizzard.net setup exe its crashes
and gives me the backtrace log
Product: Wine
Version: 6.0.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adampigeons(a)gmail.com
Distribution: ---
Created attachment 76555
--> https://bugs.winehq.org/attachment.cgi?id=76555
the log of the error
i launch battlenet exe setup then the window becomes unusable then i get the
backtrace 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.
http://bugs.winehq.org/show_bug.cgi?id=32342
Bug #: 32342
Summary: PlanetSide2 Error message and bugreport.txt and
debug.log in Steam.
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: linards.liepins(a)gmail.com
Classification: Unclassified
Created attachment 42683
--> http://bugs.winehq.org/attachment.cgi?id=42683
PlanetSide2 bugreport.txt
Cannot run PlanetSide 2 on x64 Fedora 17. Popuing up three similar error log
message with attached bugreport. Also attached debug.log is generated in Steam
install dir.
--
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=55979
Bug ID: 55979
Summary: Blizzard Battle.net Launcher: New Version Released On
11/30/2023 Hangs During Installation
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: crashdance(a)charter.net
Distribution: ---
Created attachment 75569
--> https://bugs.winehq.org/attachment.cgi?id=75569
Terminal output when running the Battle.net client installer in a clean Wine
prefix
When attempting to install Battle.net in a clean 64-bit prefix on a clean
install of Linux Mint 21.2 with all needed dependencies, I get the attached
terminal output and the progress hangs at 45%.
Also, I know the maintainers of Bugzilla encourage reporting only one problem
per bug. That being said, the exact same time this started happening, my
existing Wine prefix for Battle.net (and my Battle.net games) caused thread
crashes when opening Battle.net after installing yesterday's update. The update
was installed from within the Battle.net client by clicking the green icon to
install the update. Prior to this update released yesterday on November 30,
2023, Battle.net and the games were running flawlessly.
Because I can only add a single attachment, the Pastebin links below will give
more detail on the related issue of thread crashes described above:
Existing prefix terminal output when the thread crash occurs:
https://pastebin.com/4UwxTsEP
Here is my system information:
https://pastebin.com/v3MVemgg
Was able to save a crash report for the thread crash issue:
https://pastebin.com/mYX68NrX
--
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=58046
Bug ID: 58046
Summary: Horizon Chase Turbo: gamepad hotplugging doesn't work
Product: Wine
Version: 10.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: tinozzo123(a)gmail.com
Distribution: ---
Created attachment 78302
--> https://bugs.winehq.org/attachment.cgi?id=78302
`WINEDEBUG=+dinput`, launch game with one gamepad, disonnected, reconnected.
In Horizon Chase Turbo (tested Epic Games Store version), gamepads are only
usable if they have always been connected since the game has been launched.
Otherwise, their inputs are completely ignored, and these gamepads will not be
listed in the player mapping screen (Multiplayer). This is not the case on
Windows.
The only exception is in the title screen: "Press Any Button" does work with
hotplugged gamepads.
Logs are taken on a fresh prefix with `WINEDEBUG=+dinput`. Without this, the
only dinput-related log is:
```
0208:fixme:dinput:hid_joystick_device_try_open device usage ff72:00a1 not
implemented!
```
--
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=57980
Bug ID: 57980
Summary: Adobe Creative Cloud requires unimplemented function
KERNEL32.dll.SetThreadpoolTimerEx
Product: Wine
Version: 10.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: asdfghrbljzmkd(a)outlook.com
Distribution: ---
Every so often I test installing Adobe CC on Wine to see if it will work. With
the recent fixes relating to libcef/edge/chromium sandboxing, I gave it another
go. Seems like this is now an issue:
```
wine: Call from 00006FFFFFC75D38 to unimplemented function
KERNEL32.dll.SetThreadpoolTimerEx, aborting
```
--
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=48746
Bug ID: 48746
Summary: Null_DC stops with error on Emulator Startup (not
opening the application)
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: apphelp
Assignee: wine-bugs(a)winehq.org
Reporter: starfirehyper(a)gmail.com
Distribution: ---
Hello,
I am having issues with Wine and Null DC
I do have Crossover on a Chromebook, but whatever I start the emulator (not
opening the application) I get a error that tells me " The program (the full
name of the exe) has encountered a serious problem and needs to close." The
link on the error wasn't very helpful. (I am running nullDC 1.0.4 and I don't
know what is causing it)
Thank you and good bye.
Have a nice day! :)
--
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=48771
Bug ID: 48771
Summary: SoulWorker from Official Launcher
Product: Wine
Version: 5.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: full01(a)linuxmail.org
Distribution: ---
I can't start the game from the Official Launcher. The launcher starts with
Wine-staging but I get the error (The Directory is Invalid) when I try to start
the game client.
The game worked flawlessly before they changed the launcher.
I think the problem is the second launcher called "Soulworkerlauncher.exe".
The game is free to play: https://en.soulworker.gameforge.com/landingpage/
--
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=53407
Bug ID: 53407
Summary: Hogia Hemekonomi Missing date picker widget
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)jonass.user.lysator.liu.se
Distribution: ---
Created attachment 72799
--> https://bugs.winehq.org/attachment.cgi?id=72799
How the calendar widget looks when run on Windows XP.
When showing transactions there is a date entry field where the user can enter
a date. Or press "enter" to get a date picker widget. The widget seems to be
missing in Wine.
To reproduce:
- Run the software like "wine Hemeko.exe"
- There will be dialogue asking about number format, click Yes.
- On first run you get an intro (or error see Bug 53384). If error, just
dismiss. If intro, press "Återgå till Hemekonomi" to dismiss.
- Click "Arkiv" and "Ny" to create a new database to work with. When asked
"Ange namnet på den nya databasen" enter something like "foo.mdb" and click OK.
- Click "Fortsätt med Hemekonomi" to dismiss setup wizard.
- Press CTRL-K or click on icon Kontoutdrag.
- Click OK.
- Use mouse to set focus on entry field in lower right corner called "Fr o m"
- Press enter.
- See Program Error.
On subsequent runs click Arkiv/Öppna instead to use the existing foo.mdb
database.
--
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=55138
Bug ID: 55138
Summary: msys2: bash.exe is not able to fork/start another
process.
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
Created attachment 74697
--> https://bugs.winehq.org/attachment.cgi?id=74697
allocation stacks in parent and child bash.exe
This is a followup to bug 47808.
If I understand it right, bug 47808 was primarily about native libraries
getting called at a win32 stack which was not yet committed.
Those native libraries then jumped over the guard page, therefore the stack
got not grown, instead a crash reported.
This aspect was fixed by using the syscall interface and
therefore bug 47808 was closed.
But there is another issue that causes a msys2-forked process crashing,
because after the stack was grown it still misses the PAGE_READWRITE flags.
For this Zeb Figura included in the first attachement to bug 47808
"always expand the stack if within the stack reserve"
a line adding the flags "VPROT_COMMITTED | VPROT_READ | VPROT_WRITE"
to the page that gets the VPROT_GUARD removed in grow_thread_stack.
This modification still enables a forked process to run.
The issue can be reproduced with an unmodified wine by just
- running msys2 bash.exe interactively
- then trying to start e.g. notepad from it.
Attached file shows the stack when the stack gets allocated
- in a working msys2-parent process and
- in a failing msys2-forked child process.
Therefore it looks like the forked stack get really setup differently,
but it is still not clear if or when this memory gets the READ/WRITE
added in native 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=37131
Bug ID: 37131
Summary: Clang Static Analyzer: Division by zero
Product: Wine
Version: 1.7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lukebenes(a)hotmail.com
Clang Static Analyzer identifies Division by zero
File: dlls/winex11.drv/palette.c
Location: line 601, column 43
Description: Division by zero
#define NB_RESERVED_COLORS 20
...
static void X11DRV_PALETTE_FillDefaultColors(....)
{
...
int i = 0, idx = 0;
int red, no_r, inc_r;
...
if (palette_size <= NB_RESERVED_COLORS)
return;
while (i*i*i < (palette_size - NB_RESERVED_COLORS)) i++;
no_r = no_g = no_b = --i;
...
inc_r = (255 - NB_COLORCUBE_START_INDEX)/no_r;
//Clang: Division by zero
...
}
The code will continue executing if the palette_size variable is larger than or
equal to 21. With the value 21, the 'i' variable will be first incremented by
one and then decremented by one. As a result, the 'i' variable will remain
equal to zero, which will cause the division-by-zero error.
--
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.