https://bugs.winehq.org/show_bug.cgi?id=47068
Bug ID: 47068
Summary: fixme:ntdll:create_logical_proc_info Only 64 Threads
are usable
Product: Wine
Version: 4.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: coolx67(a)gmx.at
Distribution: ---
When running heavy multi threaded programs such as scientific applications or
benchmarks it shows that only 64 threads can be used.
> 002a:fixme:ntdll:create_logical_proc_info Improve CPU info reporting: system supports 96 logical cores, but only 64 supported!
The problem is here
https://github.com/wine-mirror/wine/blob/master/dlls/ntdll/nt.c#L1687
I don't know how much time I have to fix this.
But if someone would brainstorm this with me.
It were my first 5 minutes in the Wine code so please have some understanding.
If there would be some mentor who would give me some advice I could probably
fix some of the 22k+ FIMES in the code :)
Here the WINEDBG from Cinebench
https://pastebin.com/FrgSGxGw
--
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=46263
Bug ID: 46263
Summary: Final Fantasy XI crashes after accepting EULA when
using Ashita
Product: Wine-staging
Version: 3.21
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)foreversmall.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 62965
--> https://bugs.winehq.org/attachment.cgi?id=62965
Terminal Output with backtrace of crash.
When using Ashita with FFXI the game crashes shortly after accepting the EULA.
I've confirmed this with all the versions of wine starting from version 3.0
stable, all the way up to 3.21 staging. The only way I've been able to get the
game to launch is to compile wine myself with the following patch:
https://gitlab.com/farmboy0/wine/commit/54aea128e91a6b03bff05e79d9a09bea572…
Its very easy to recreate, use all the standard AppDB info to get FFXI setup.
Download ashita from the website:
https://git.ashitaxi.com/Ashita/Ashitav3-Launcher/raw/master/Ashita.exe
>From here you need all the ashita pre-reqs:
http://docs.ashitaxi.com/requirements/
Setup a config file with the settings ../Ashita/Config/Boot/
You can launch the game via this command: wine %path_to_Ashita%/injector.exe
"%CONFIGFILE%.xml"
If it properly loads then once you accept the EULA it will crash.
--
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=46839
Bug ID: 46839
Summary: Happy Foto Designer Font not found "Fehler (Code 1)
[Font is not supported: Roboto]"
Product: Wine
Version: 4.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdiplus
Assignee: wine-bugs(a)winehq.org
Reporter: martin.marmsoler(a)gmail.com
Distribution: ---
Hello,
while creating a new Photo book in Happy Foto
Designer(https://www.happyfoto.at/) I get the following error:
"Fehler (Code 1) [Font is not supported: Roboto]"
The error can be solved by installing gdiplus, but the fonts are not drawn
properly and only the first character is shown.
--
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=45901
Bug ID: 45901
Summary: Avoid GPU synchronization due to GPU-CPU transfer
(Overwatch)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: awesie(a)gmail.com
Distribution: ---
Created attachment 62422
--> https://bugs.winehq.org/attachment.cgi?id=62422
Patch to avoid GPU synchronization
One performance gap with Overwatch on Wine + AMD + Mesa is GPU synchronization
due to transfers from GPU texture to CPU texture. By using PBOs and
glReadPixels with GL_PIXEL_PACK_BUFFER, we can avoid this synchronization
leading to improved performance.
The attached patch is one approach to resolve the performance issue, but I am
not sure that it is the best way. Feedback is appreciated.
Also attached is before and after screenshots with Mesa's HUD. You can observe
that the buffer wait time decreases with the patched version. Both the before
and after screenshots are on wine-staging master plus my patch for 45723.
--
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=16911
Summary: WriteProcessMemory() not working for memory protected by
X11DRV_DIB_DoProtectDIBSection()
Product: Wine
Version: 1.1.12
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Keywords: patch, source
Severity: minor
Priority: P2
Component: winex11.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thestig(a)google.com
Created an attachment (id=18660)
--> (http://bugs.winehq.org/attachment.cgi?id=18660)
test program
Hi, I have a test case here that works on WinXP but not Wine. I deliberately
wrote a standalone test case because I'm not sure which unit test to put it in.
It's in fact based off of dlls/kernel32/tests/virtual.c where the other
WriteProcessMemory() test is.
In this test case, we call CreateDIBSection() which returns a HBITMAP (hbitmap)
and some memory (mem). Next, we call SetDIBits() with hbitmap. We get into
X11DRV_SetDIBits(), where it calls X11DRV_DIB_Lock( physBitmap,
DIB_Status_GdiMod );.
This marks the memory (mem) as PAGE_NOACCESS, and leaves it in that state as
SetDIBts() returns. Normally if the process tries to access it, we get a page
fault that's handled by X11DRV_DIB_FaultHandler(), and everything works.
However, when the test code calls WriteProcessMemory(), we talk to wineserver
in NtWriteVirtualMemory(). In wine_server_call(), we do send_request(), where
writev() tries to read 'mem' and fails with EFAULT. This doesn't trigger
X11DRV_DIB_FaultHandler(), and WriteProcessMemory() fails.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=12401
Summary: Support junction points, i.e.
DeviceIoCtl(FSCTL_SET_REPARSE_POINT/FSCTL_GET_REPARSE_PO
INT)
Product: Wine
Version: CVS/GIT
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Junction points are one of Microsoft's answers to symlinks.
Unix symlinks could be mapped into junction points.
This would allow applications (e.g. Picasa) avoid following
symlinks if they wanted to.
Also, the .net 2 installer would be happier in winxp mode if wine supported
junction points (see bug 10601):
"The .NET 2.0 Framework installer checks if the target volume is NTFS
filesystem
type and then uses the FSCTL_SET_REPARSE_POINT ioctl (used for mount points and
junctions) to create junction points for each registered assembly in Windows
SxS directory to GAC assembly directory (link target).
Basically the junction point is used to redirect access from one directory to
another."
Tommy Kho posted a patch to add a conformance test for
getting and setting junction points,
http://www.winehq.org/pipermail/wine-patches/2006-March/024956.html
but it was not accepted.
--
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=47116
Bug ID: 47116
Summary: Indiana Jones and the Emperor's Tomb: white line
Product: Wine
Version: 4.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: legluondunet(a)free.fr
Distribution: ---
Created attachment 64326
--> https://bugs.winehq.org/attachment.cgi?id=64326
screen captures with white lines
Hello,
to play Indiana Jones and the Emperor's Tomb with Wine, I know I have to:
- override dll msvcrt bug 27594
- disable vertex shader 12400
But now I have a new graphic issue with Wine 4.7 (even with staging version):
look at the screen captures I joined to this bug report, there are white lines.
--
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=39859
Bug ID: 39859
Summary: WineHQ packages for wine-gecko and wine-mono
Product: Packaging
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: dimesio(a)earthlink.net
CC: michael(a)fds-team.de, sebastian(a)fds-team.de
Distribution: ---
Most users of the distros we now package for are accustomed to installing
wine-gecko and wine-mono from packages. We should provide them.
--
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=47558
Bug ID: 47558
Summary: Ubuntu package for 4.12.1 cannot open project in Adobe
Premiere Pro 2.0
Product: Packaging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: julius.schwartzenberg(a)gmail.com
CC: dimesio(a)earthlink.net, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 64946
--> https://bugs.winehq.org/attachment.cgi?id=64946
output of Wine
When I run Adobe Premiere Pro 2.0 with Wine 4.12.1 in Ubuntu, I get the
following dialog when trying to open a project:
Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut
down. We will attempt to save your current project.
Rebuilding Wine myself from Git, currently the latest commit matches 4.12.1,
does not show this problem.
--
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=14010
Summary: RivaTuner 2.09 not work ,no overclocking or sensor
ability
Product: Wine
Version: 1.0.0
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dj--alex(a)ya.ru
RivaTuner 2.09 not work ,no overclocking or sensor ability
My videocard is very loud without this program!!
I and not only i, want to overclocking without BIOS VRAM rewrite.
Program can be downloaded free from
http://www.radeon.ru/
(Main menu left - newest version)
--
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.