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=49199
Bug ID: 49199
Summary: Wine on macOS no longer loads dylibs from /lib(64)
Product: Wine
Version: 5.6
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gcenx83(a)gmail.com
Starting from Wine-5.6 the libwine wrappers have been removed in favor of using
dlopen() however this now causes component in question to no longer load
embedded dylibs into /lib(64)
Here’s an example;
```907aaf9e72714293909351648827e7c5aebc12a3 is the first bad commit
commit 907aaf9e72714293909351648827e7c5aebc12a3
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Mon Apr 6 11:46:10 2020 +0200
gdi32: Use standard dlopen() instead of the libwine wrappers.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
dlls/gdi32/dibdrv/opengl.c | 12 +++++-------
dlls/gdi32/freetype.c | 20 ++++++++++----------
2 files changed, 15 insertions(+), 17 deletions(-)```
Any commit doing “ Use standard dlopen() instead of the libwine wrappers.” will
now experience this.
Previous behavior was the ability to simply embed dylibs into /lib(64) and
wine(64) would load them as needed, now rpath is required.
Winehq packages will also experience this issue worse once the current embedded
libraries swap to using dlopen()
--
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.
https://bugs.winehq.org/show_bug.cgi?id=47521
Bug ID: 47521
Summary: digikam 6.10 crashes on start
Product: Wine
Version: 4.11
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Gentoo
Created attachment 64913
--> https://bugs.winehq.org/attachment.cgi?id=64913
crash output
Backtrace:
=>0 0x66401f0a EntryPoint+0xb6a() in qt5widgets (0x006ff4f8)
1 0x1084cf64 WXMPUtils_DuplicateSubtree_1+0x44c5d3() in libdigikamcore
(0x737adae8)
2 0x10388bb9 EntryPoint+0x387818() in libdigikamcore (0x006ff5f8)
3 0x104c0cba WXMPUtils_DuplicateSubtree_1+0xc0329() in libdigikamcore
(0x006ff688)
4 0x2278b630 EntryPoint+0xba28f() in libdigikamgui (0x006ffab8)
5 0x2276e7b3 EntryPoint+0x9d412() in libdigikamgui (0x006ffb98)
6 0x00404be5 _ZN7Digikam6DColor11premultiplyEv+0x15e4() in digikam
(0x006ffe88)
7 0x00401382 EntryPoint+0xffffffff() in digikam (0x006fff28)
8 0x7b47e022 call_process_entry+0x11() in kernel32 (0x006fff48)
9 0x7b480acc start_process+0xeb(entry=<couldn't compute location>,
peb=<couldn't compute location>)
[Z:\home\austin\wine-git\dlls\kernel32\process.c:1297] in kernel32 (0x006fffd8)
10 0x7b47e02e start_process_wrapper+0x9() in kernel32 (0x006fffec)
0x66401f0a EntryPoint+0xb6a in qt5widgets: movl 0x4(%eax),%ecx
austin@laptop:~/Downloads$ du -sh digiKam-6.1.0-Win32.exe
321M digiKam-6.1.0-Win32.exe
austin@laptop:~/Downloads$ sha256sum digiKam-6.1.0-Win32.exe
fb870263a8bb2bd178590dfacfe68110b68d8c5b0ca53606084162a1a5e42b44
digiKam-6.1.0-Win32.exe
--
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=43993
Bug ID: 43993
Summary: Quick3270 5.21: crashes when using the Connect
function
Product: Wine
Version: 2.0.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: q3270(a)grr.la
Distribution: ---
Application crashes when I choose Session -> Connect option.
Application error messages is: "Could not find imported function in DLL
C:\windows\system32\ws2_32.dll"
Console output relevant messages:
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:shell:SetCurrentProcessExplicitAppUserModelID
L"DN-Computing.Quick3270.DisplayEmulator": stub
fixme:htmlhelp:HtmlHelpW HH case HH_INITIALIZE not handled.
fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevation,
...) semi-stub
fixme:htmlhelp:HtmlHelpW HH_PRETRANSLATEMESSAGE unimplemented
Application is available as trial here:
https://www.dn-computing.com/download.htm
Prior to launching the application I've installed wine-mono and wine-gecko.
Unsuccessfully tried:
- replacing ws2_32.dll with an original one
- debugging with +relay, the log doesn't show the missing procedure name
--
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.