https://bugs.winehq.org/show_bug.cgi?id=42601
Bug ID: 42601
Summary: Foxit Reader Crashes after running for an extended
period of time
Product: Wine
Version: 2.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: seanaubin(a)gmail.com
Distribution: ---
Created attachment 57546
--> https://bugs.winehq.org/attachment.cgi?id=57546
Backtrace of the crash
After running Foxit Reader for an extended period of time (30 minutes) the
reader crashes. Before crashing, the graphics fail to render and are only
updated if the mouse click on them. However, the PDF itself is never updated.
Foxit Reader Version: 8.2.1.6871
--
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=18154
Summary: cmd.exe: failure to handle file extension association
Product: Wine
Version: 1.1.19
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P4
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: swelef(a)post.sk
cmd.exe doesn't handle extension association.
Test case:
Install ActivePerl, create a dummy perl script test.pl and run
wine cmd /c test.pl
cmd.exe will try to run test.pl as Unix binary
trace:process:CreateProcessW starting L"C:\\\\test.pl" as Unix binary
and (probably) fail instead of running Perl.exe as the Windows XP command
cmd /c perl.pl
Source code analysis:
The function programs/cmd/wcmdmain.c:WCMD_run_program calls FindExecutable
but mostly ignores the result. This looks like an unfinished work.
Remark:
Theoretically, some program could rely on the association. As long as such
program is not known, this is a low priority issue. Users should prefer
the explicit command
wine perl test.pl
(or "wine start /W test.pl" if they want a new console).
--
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=49244
Bug ID: 49244
Summary: GdipDeleteFontFamily is declared, but does nothing
Product: Wine
Version: 5.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdiplus
Assignee: wine-bugs(a)winehq.org
Reporter: mikrutrafal54(a)gmail.com
Distribution: ---
Function just check if FontFamily is null and return value without doing
anything.
https://github.com/wine-mirror/wine/blame/056c9df854817670dc4fb9c095cba29c9…
--
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=55964
Bug ID: 55964
Summary: wine-mono: Dlls include reference to filenames
different to the files in
wine-mono-8.1.0-dbgsym.tar.xz
Product: Wine
Version: 8.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
I was trying get a backtrace from #55736 with debug symbols.
Therefore I tried using a windows build of LLDB.
Unfortunately it took me some time to figure out that the PDB file name
embedded in the dll files did not match the filename
in the archive wine-mono-8.1.0-dbgsym.tar.xz.
After renaming to the name libmonosgen-2.0.pdb it got found by LLDB.
Maybe either the build can be modified to build with the expected file names
in the first place, or add a short readme to the archive file describing
this issue?
$ strings windows/mono/mono-2.0/bin/libmono-2.0-x86*.dll | grep -i
"mono.*\.pdb"
/vagrant/build/mono-x86_64/mono/mini/.libs/libmonosgen-2.0.pdb
/vagrant/build/mono-x86/mono/mini/.libs/libmonosgen-2.0.pdb
--
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=54212
Bug ID: 54212
Summary: Nexus ECU Tuning Software for HALTECH ECU
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: nbehnken(a)gmail.com
Distribution: ---
Created attachment 73755
--> https://bugs.winehq.org/attachment.cgi?id=73755
Startup Trace before error message is Displayed about Windows Installer
The Nexus software is a DOTNET application that controls the Haltech ECU for
automotive tuning.
ERROR from APP
"Nexus Software cannot be installed on systems with Windows Installer version
lower than 5.0."
Download Location
https://www.haltech.com/wp-admin/admin-ajax.php?action=ht_latest_software
wine NexusInstallPackageWeb_v1.40.2.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=55343
Bug ID: 55343
Summary: Game Constantine Doesn't Work
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jon9097(a)gmail.com
Distribution: ---
Constantine's game doesn't work.
I've been trying to run it for years and it's all to no avail. Either it starts
but doesn't respond to any key, or it doesn't start at all.
Here is the link to the game: https://archive.org/details/constantine_202007
--
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=55410
Bug ID: 55410
Summary: msi:package fails on w8adm
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
msi:package fails on w8adm:
package.c:8054: Test failed: Expected ERROR_SUCCESS, got 1605
package.c:8055: Test failed: Expected a valid product handle
package.c:8099: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8100: Test failed: Expected "", got "apple"
package.c:8101: Test failed: Expected 0, got 260
package.c:8106: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8107: Test failed: Expected "", got L"apple"
package.c:8108: Test failed: Expected 0, got 260
package.c:8114: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8115: Test failed: Expected "{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}",
got "apple"
package.c:8117: Test failed: Expected 38, got 260
package.c:8123: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8124: Test failed: Expected
L"{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got L"apple"
package.c:8126: Test failed: Expected 38, got 260
package.c:8132: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8133: Test failed: Expected 38, got 260
package.c:8138: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8139: Test failed: Expected 38, got 260
package.c:8149: Test failed: Expected 38, got 260
package.c:8158: Test failed: Expected 38, got 260
package.c:8165: Test failed: Expected ERROR_MORE_DATA, got 6
package.c:8166: Test failed: Expected first 3 chars of
"{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got "apple"
package.c:8168: Test failed: Expected 38, got 4
package.c:8174: Test failed: Expected ERROR_MORE_DATA, got 6
package.c:8175: Test failed: Expected first 3 chars of
L"{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got L"apple"
package.c:8177: Test failed: Expected 38, got 4
package.c:8184: Test failed: Expected ERROR_MORE_DATA, got 6
package.c:8185: Test failed: Expected first 37 chars of
"{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got "apple"
package.c:8193: Test failed: Expected ERROR_MORE_DATA, got 6
package.c:8194: Test failed: Expected first 37 chars of
L"{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got L"apple"
package.c:8203: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8204: Test failed: Expected "{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}",
got "apple"
package.c:8206: Test failed: Expected 38, got 39
package.c:8212: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8213: Test failed: Expected
L"{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got L"apple"
package.c:8215: Test failed: Expected 38, got 39
package.c:8222: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8223: Test failed: Expected "", got "apple"
package.c:8224: Test failed: Expected 0, got 260
package.c:8229: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8230: Test failed: Expected "", got L"apple"
package.c:8231: Test failed: Expected 0, got 260
package.c:8234: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8240: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8241: Test failed: Expected "", got "apple"
package.c:8242: Test failed: Expected 0, got 260
package.c:8247: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8248: Test failed: Expected "", got L"apple"
package.c:8249: Test failed: Expected 0, got 260
package.c:8252: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8258: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8259: Test failed: Expected "{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}",
got "apple"
package.c:8261: Test failed: Expected 38, got 260
package.c:8267: Test failed: Expected ERROR_SUCCESS, got 6
package.c:8268: Test failed: Expected
L"{1DF3BC35-22CE-4AE5-8CB6-CD8312577038}", got L"apple"
package.c:8270: Test failed: Expected 38, got 260
See https://test.winehq.org/data/patterns.html#msi:package
These failures started on 2023-07-27 which is when the w8 VM's memory was
increased to 4GB, and older WineTest builds still produce the failures. So the
2023-07-27 VM change is the cause of these failures but it's not clear why.
Also note that, unlike msi:msi and msi:source, msi:package fails even if run on
its own (see bug 55396).
--
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=53154
Bug ID: 53154
Summary: Crash of EpicOnlineServicesUserHelper.exe" --setup
Product: Wine
Version: 7.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: me(a)janryll.de
Distribution: ---
Created attachment 72586
--> https://bugs.winehq.org/attachment.cgi?id=72586
Unhandled exception: page fault on read access.
1. Start "Epic Games Lauchner"
2. Goto Settings
3. Click on Install Epic Online Services
4. Crash after some seconds
Epic Games Launcher displays Error EOS-ERR-1603.
--
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=55804
Bug ID: 55804
Summary: DICOM Viewer (eFilm Workstation 2.x/3.x) aborts
because libxml2 doesn't like "ISO8859-1" (builtin
msxml6).
Product: Wine
Version: 8.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msxml3
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
Created attachment 75294
--> https://bugs.winehq.org/attachment.cgi?id=75294
xml2: Allow encoding="ISO8859-1".
Bug #13340 is for the same application but with native msxml6.
This bug is about the nearly same error message when using builtin msxml6:
> XML Parser Error
> LoadXMLFile 'C:\efilmlite_dvd\eFilmLite\Profiles
> \Default\ToolBarMiniCfg.xml':
> Error:
> Code = 0x80004005
> Source = Line: 0; Char: 0
> Error Description = error
But this seems to be caused by the bundled libxml2 not accepting
as encoding "ISO8859-1", just "ISO-8859-1".
--
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=43472
Bug ID: 43472
Summary: R-Link 2 Toolbox crashes on startup
Product: Wine
Version: 2.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sb(a)monkey-mind.net
Distribution: ---
Created attachment 58852
--> https://bugs.winehq.org/attachment.cgi?id=58852
R-Link 2 Toolbox Backtrace
The Renault R-Link 2 Toolbox application crashes upon launch.
The installer manages to install just fine, but when trying to launch the
actual application, the crash dialog pops up. See attached backtrace.
The shell window from which the application was started says:
wine: Unhandled page fault on execute access to 0x00000000 at address
(nil) (thread 0009), starting debugger...
Tried with emulation set to Windows 10, Windows 7, Windows Server 2003; all
failed with the same error. SELinux is in permissive mode.
--
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.