https://bugs.winehq.org/show_bug.cgi?id=51464
Bug ID: 51464
Summary: Pagefault error caused by qt5webenginecore
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: shadowbranch(a)gmail.com
Distribution: ---
Created attachment 70305
--> https://bugs.winehq.org/attachment.cgi?id=70305
Backtrace from Pagefault
Running the latest Kaseya Live Connect 9.5.0.24. When connecting to server
program crashes with pagefault 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.
https://bugs.winehq.org/show_bug.cgi?id=47412
Bug ID: 47412
Summary: Kaseya Live Connect: crashes on first run after
install
Product: Wine
Version: 4.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: registry
Assignee: wine-bugs(a)winehq.org
Reporter: alero5752(a)hotmail.com
Distribution: ---
Created attachment 64760
--> https://bugs.winehq.org/attachment.cgi?id=64760
Progam Error details
Hello,
Linux noob here. My company recently upgraded our Kaseya VSA version to 9.5.0.2
and ever since this was completed it broke my Kaseya Live Connect app
compatibility within Wine. I've attached the log to review and also a link to
the EXE file for the application below. This is the very latest version of
Kaseya. When attempting to launch the program, it stops and displays an error,
(The program QtWebEngineProcess.exe has encountered a serious problem and needs
to close. We are sorry for the inconvenience).
https://drive.google.com/file/d/1StEVxsaQFKTVX8pb6htmo8r_4R14btJz/view?usp=…
--
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=34377
Bug #: 34377
Summary: Paint Shop Pro X5 Installer fails
Product: Wine
Version: 1.6
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: maikwagner(a)yahoo.com
Classification: Unclassified
Created attachment 45757
--> http://bugs.winehq.org/attachment.cgi?id=45757
Backtrace
Hello everyone,
I have been testing "Paint Shop Pro X5" from Corel but I am having problems to
get it to install correctly. Please find my backtrace attached and please let
me know should you require further information.
--
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=53345
Bug ID: 53345
Summary: finder claims WINE needs to be updated, no updates
available
Product: Wine
Version: 0.9.3.
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: boxylid(a)gmail.com
Created attachment 72730
--> https://bugs.winehq.org/attachment.cgi?id=72730
WINE inaccessible
After installing WINE it cannot be opened, finder reports that it needs to be
updated to run yet there is no update currently available on 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=53626
Bug ID: 53626
Summary: Wine crash due to long filename when saving file in
Framemaker
Product: Wine
Version: 7.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de
Distribution: ---
When saving a file with a long filename (more than 28 chars) in Framemaker wine
crashes (not the application, wine itself including wineserver).
A bisect shows this commit as cause
commit 0ad2db66a109b4c0a46d04ff8231706fff540941
Author: Jacek Caban <jacek(a)codeweavers.com>
Date: Sun Aug 14 20:49:53 2022 +0200
win32u: Pack messages sent directly from win32u.
Instead of leaking kernel pointers.
dlls/win32u/message.c | 216 +++++++++++++++++++++++++++++++++++++++++--
dlls/win32u/ntuser_private.h | 9 --
2 files changed, 208 insertions(+), 17 deletions(-)
Reverting this commit in top of current git solves the problem.
It seems to be a memory corruption. If you give me a hint how
to further debug this I will do.
--
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=52562
Bug ID: 52562
Summary: advapi32:registry fails in Wine because some French
timezone name translations are too long
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
advapi32:registry fails in the timezone tests in a French locale:
registry.c:4413: Test failed: L"Aleutian Standard Time": expected L"Heure
d'\00e9t\00e9 des \00celes Al\00e9outiennes", got L"Aleutian Daylight Time"
registry.c:4395: Test failed: L"Dateline Standard Time": expected L"Heure de la
ligne de changement de date", got L"Dateline Standard Time"
registry.c:4413: Test failed: L"Dateline Standard Time": expected L"Heure
d'\00e9t\00e9 de la ligne de changement de date", got L"Dateline Daylight Time"
registry.c:4395: Test failed: L"Turks And Caicos Standard Time": expected
L"Heure des \00celes Turques-et-Ca\00efques", got L"Turks And Caicos Standard
Time"
registry.c:4413: Test failed: L"Turks And Caicos Standard Time": expected
L"Heure d'\00e9t\00e9 des \00celes Turques-et-Ca\00efques", got L"Turks And
Caicos Daylight Time"
http://winetest.dolphin/data/patterns.html#advapi32:registry
This issue is already happening in German also because the timezone name
translation is too long. See bug 51619 for more details.
The new translations were introduced by the following commits:
commit a38ced9354aa7d74f396fb91372dbbb7dccd2e2e
Author: Eric Pouech <eric.pouech(a)gmail.com>
Date: Sun Jan 2 15:49:09 2022 +0100
po: Some more French translations.
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
commit 39f77b25aacf248e18e747bf31c2055a9cfbc89a
Author: Eric Pouech <eric.pouech(a)gmail.com>
Date: Mon Jan 3 15:43:21 2022 +0100
po: Some more French translations.
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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=53430
Bug ID: 53430
Summary: urlmon:url fails due to unexpected redirection
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
urlmon:url fails due to unexpected redirection:
url.c:4093: asynchronous https test (invalid CN, accept)
url.c:1796: Test failed: unexpected code 64
url.c:1466: Test failed: progress 64: status = 302
url.c:1662: Test failed: unexpected call OnProgress_REDIRECTING
url.c:1663: Test failed: unexpected status text
L"https://www.winehq.org/robots.txt"
url.c:1466: Test failed: progress 3: status = 302
url.c:1492: Test failed: wrong thread 8148
url.c:1642: Test failed: unexpected call OnProgress_FINDINGRESOURCE
url.c:1675: Test failed: unexpected call OnProgress_SENDINGREQUEST
url.c:1706: Test failed: wrong szStatusText
L"https://www.winehq.org/robots.txt"
url.c:1743: Test failed: wrong szStatusText
L"https://www.winehq.org/robots.txt"
url.c:4097: asynchronous https test (invalid CN, dialog 2)
url.c:1492: Test failed: wrong thread 8148
url.c:1796: Test failed: unexpected code 64
url.c:1662: Test failed: unexpected call OnProgress_REDIRECTING
url.c:1663: Test failed: unexpected status text
L"https://www.winehq.org/robots.txt"
url.c:1466: Test failed: progress 3: status = 200
url.c:1706: Test failed: wrong szStatusText
L"https://www.winehq.org/robots.txt"
url.c:1743: Test failed: wrong szStatusText
L"https://www.winehq.org/robots.txt"
url.c:4102: asynchronous https test...
https://test.winehq.org/data/patterns.html#urlmon:url
The failures happen on all Windows versions and in Wine too.
Furthermore they started on 2022-07-06 and are reproducible even with older
Wine builds. So something changed that day, probably on winehq.org, and broke
the tests.
--
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=52953
Bug ID: 52953
Summary: GuiPy will not start because of unimplemented function
unimplemented function
xmllite.dll.CreateXmlReaderInputWithEncodingCodePage
Product: Wine
Version: 7.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mywine(a)schiermeier-it.de
Distribution: ---
Created attachment 72323
--> https://bugs.winehq.org/attachment.cgi?id=72323
Console log file during start of "guipy.exe"
The application GuiPy.exe will not start. The function "unimplemented function
xmllite.dll.CreateXmlReaderInputWithEncodingCodePage" is missing.
To install GuiPy.exe please download the installer "GuiPy-1.0.5-x64-Setup.exe"
on the listed URL above.
--
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=52626
Bug ID: 52626
Summary: unimplement of combase.dll.RoSetErrorReportingFlags
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: l12436(a)yahoo.com.tw
Distribution: ---
Some game need this function implemented to work
Relative game: MahjongSoul on steam
LOG
wine: Call from 7B0113E6 to unimplemented function
combase.dll.RoSetErrorReportingFlags, aborting
wine: Unimplemented function combase.dll.RoSetErrorReportingFlags called at
address 7B0113E6 (thread 0024), starting debugger...
--
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=52618
Bug ID: 52618
Summary: 32-bit EXEs do not launch from build dir on macOS
10.14 in WOW64
Product: Wine
Version: 7.3
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build-env
Assignee: wine-bugs(a)winehq.org
Reporter: bshanks(a)codeweavers.com
Created attachment 71943
--> https://bugs.winehq.org/attachment.cgi?id=71943
patch to use @rpath
On macOS 10.14, when running Wine built for WOW64 from the build dir, 32-bit
EXEs do not launch correctly (including rundll32 on prefix creation to set up
syswow64).
64-bit EXEs launch correctly, and a standalone 32-bit build also works
correctly.
I'm building the 64-bit side with Xcode 10, and the 32-bit side with Xcode 9.
The problem is a crash on the first NtUser* call, since the
__wine_syscall_dispatcher was never set in win32u. The root cause is that
dlopen() on the unixlibs is failing because ntdll.so cannot be loaded. Here's
the dlerror():
177158.077:00ac:00b0:trace:virtual:load_builtin_unixlib loading
/Users/pip/wine/build32/dlls/win32u/win32u.so failed dlerror
dlopen(/Users/pip/wine/build32/dlls/win32u/win32u.so, 2): Library not loaded:
@loader_path/ntdll.so
Referenced from: /Users/pip/wine/build32/dlls/win32u/win32u.so
Reason: no suitable image found. Did find:
/Users/pip/wine/build64/dlls/ntdll/ntdll.so: mach-o, but wrong
architecture
/Users/pip/wine/build64/dlls/ntdll/ntdll.so: mach-o, but wrong
architecture
This doesn't make sense, it almost seems like @loader_path is still set to the
64-bit dlls/ntdll, which it obviously shouldn't be.
Changing the install name to '@rpath/(lib).so' and adding an rpath of
'@loader_path/' seems to fix the issue, even though that should be equivalent
to the current approach.
Can anyone else reproduce this problem? If so, does the attached patch help?
--
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.