https://bugs.winehq.org/show_bug.cgi?id=49390
Bug ID: 49390
Summary: ETaskbarException in CSS HTML Validator 2020 and Batch
Wizard
Product: Wine
Version: 5.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: support(a)htmlvalidator.com
Distribution: ---
Created attachment 67458
--> https://bugs.winehq.org/attachment.cgi?id=67458
Screenshots of user email reporting the bug
Download and install CSS HTML Validator Pro Trial 2020:
https://www.htmlvalidator.com/css-html-validator-trial-setup.exe
Perform the following steps to reproduce the exception which causes program
malfunction:
1. Open CSS HTML Validator (version 20.03, under Wine 5.10 on Arch Linux, bare
metal)
2. Main Menu Bar > Tools > Batch Wizard
3. In the Batch Wizard dialog, do Options > Force Toolbar
4. If necessary, increase width of the Batch Wizard dialog, so that the entire
toolbar is visible.
5. Click the "Add Target" button.
6. Click the "Add file target(s)" option (or any other of the three options).
7. Select an HTML file, and click the "Open" button.
8. In the toolbar, click the "Start" button.
9. In the "HTML Validator: Confirm Job" dialog, click the "Start processing
now" option.
10. The "ETaskbarException: Could not register tab." error window appears.
11. Program ceases to function properly after exception (i.e. cannot be closed
properly).
Also see attachments which are screenshots provided by a user.
Sidenote: Toolbar (which contains the "New List" button) is still not
displaying properly as it displays fully justified when it should display left
justified. Can see this in the first screenshot (EmailPart1.png) in the
attachment.
--
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=20456
Summary: FEAR's installer will not let me enter the serial
number
Product: Wine
Version: 1.1.32
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wylda(a)volny.cz
Hi, F.E.A.R. installer requires entering serial number. It has several fields
for entering 4 characters (clasic 1234-5678-9abc-def0-1234).
I can enter:
* 4 "narrow" chars like 1111, iiii, etc.
or
* only 3 "fat" chars like AAA, CCC, etc.
or
* only 2 "extra fat" like WW
There are other pepole affected in AppDB:
http://appdb.winehq.org/objectManager.php?sClass=version&iId=5159&iTestingI…http://appdb.winehq.org/objectManager.php?sClass=version&iId=5159&iTestingI…
Based on other confirmations in AppDB consider UNCONFIRMED->NEW. Tested wine
versions: 0.9.50, 0.9.60, 1.0.1, 1.1.7, 1.1.10, 1.1.13, 1.1.22, 1.1.29, 1.1.31,
1.1.32 ...so it probably never worked correctly.
This is show stopper. I own two original and none is usable under wine because
of too wide chars in serial :-/
--
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=43680
Bug ID: 43680
Summary: Epic Games Launcher crashes if tool-tip is shown in
D3D11 mode
Product: Wine
Version: 2.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx11
Assignee: wine-bugs(a)winehq.org
Reporter: plata(a)mailbox.org
Distribution: ---
Tested with Wine staging 2.16.
How to reproduce:
- run EpicGamesLauncher.exe (maybe you need the "-SkipBuildPatchPrereq"
parameter)
- wait until the login window is shown
- everything seems to be ok
- move the mouse over one of the fields where you can enter email/password
- the window starts to flicker and finally EpicGamesLauncher.exe crashes
If you launch EpicGamesLauncher.exe with "-OpenGL", you do not get the crash.
Therefore I assume that it is a problem with D3D11.
--
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=30938
Bug #: 30938
Summary: Update a XIM candidate position when cursor location
changed
Product: Wine
Version: 1.5.6
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: felixonmars(a)gmail.com
Classification: Unclassified
How to reproduce:
1. $ wine notepad
2. Activate input method (SCIM/IBUS/FCITX, etc), input something
Result:
Candidate window is below the notepad window, and never moved.
Expected result:
Candidate window moves as it is in gedit.
Probably related to these patches I found:
http://markmail.org/message/haq2zykslfkhwdilhttp://markmail.org/thread/2bfrrce47cqzga4l
--
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=37732
Bug ID: 37732
Summary: Corel Paint Shop Pro X7 Installer fails
Product: Wine
Version: 1.7.32
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 50235
--> https://bugs.winehq.org/attachment.cgi?id=50235
PSP X7 Backtrace on wine 1.7.32
Hello everyone,
I would like to share my experiences installing "Corel Paint Shop Pro X7" with
you. The installation starts up okay but a fatal error comes up when
initialising the trial installation.
I am assuming this is related to bug 27240 and 35057.
Some further info:
mwagner@linux-dnat:~/Downloads> shasum PSPX7_TBYB30.exe
7958bacb4ab198f7408066d269ca787c5b66042f PSPX7_TBYB30.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=41607
Bug ID: 41607
Summary: Piggi 2 Demo version fails to start and throws runtime
and fatal error
Product: Wine
Version: 1.9.20
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 55951
--> https://bugs.winehq.org/attachment.cgi?id=55951
Backtrace wine 1.9.20
Dear wine-team,
I had a request from somebody working in agriculture to test an application in
wine and used wine 1.9.20 as 1.9.21 is not currently available on openSUSE.
A demo version is available at the following URL:
http://www.oask.de/Sauenplaner/piggi20_setup.exe
$ md5sum piggi20_setup.exe
bfd61acc354000a14e2974d383e7bd5f piggi20_setup.exe
The application throws a runtime error of 3633 (Laufzeitfehler) and then
crashes producing the debugging output shown in the attachment.
Is there anything I can do with winetricks to work aroud this issue?
Kind regards,
Maik
--
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=42997
Bug ID: 42997
Summary: Opera Neon Installation throws backtrace
Product: Wine
Version: 2.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 58133
--> https://bugs.winehq.org/attachment.cgi?id=58133
Opera Neon Backtrace on wine 2.7
Hello everyone,
I tried installing Opera Neon in a fresh prefix but the installation wouldn't
even start and throws a backtrace on 2.7 which is attached.
--
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=45106
Bug ID: 45106
Summary: OOB write in gdi32
Product: Wine
Version: 3.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: robert.gawlik(a)rub.de
Distribution: ---
Created attachment 61285
--> https://bugs.winehq.org/attachment.cgi?id=61285
affected source code
Original submitted report can be found here:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1764719
The attachment also contains more details.
If more info is needed, please let me know!
--
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=45105
Bug ID: 45105
Summary: heap-buffer overflow in gdi32
Product: Wine
Version: 3.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: robert.gawlik(a)rub.de
Distribution: ---
Created attachment 61284
--> https://bugs.winehq.org/attachment.cgi?id=61284
affected source code
Original submitted report can be found here:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1764719
The attachment also contains more details.
If more info is needed, please let me know!
--
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=48521
Bug ID: 48521
Summary: StaxRip throes errors: Win32Exception (2.0.6.0)
Invalid function System.ComponentModel.Win32Exception
(0x80004005): Invalid function
Product: Wine
Version: 5.0
Hardware: x86
URL: https://github.com/staxrip/staxrip/releases
OS: Linux
Status: NEW
Keywords: dotnet, download, source
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: Debian
Steps to reproduce:
Use Staging (workaround https://bugs.winehq.org/show_bug.cgi?id=45868) and do
- winetricks -q dotnet40 dotnet48
- Invoke like ''wine start /unix /home/louis/StaxRip.exe'' otherwise you run
into
https://bugs.winehq.org/show_bug.cgi?id=48503
Try open an avi, it`ll tell you to install AviSynth, let it complete, then try
convert it; In the end an errormessage pops up:
Win32Exception (2.0.6.0)
Invalid function
System.ComponentModel.Win32Exception (0x80004005): Invalid function
at StaxRip.PowerRequest.SuppressStandby() in
D:\Projekte\VB\staxrip\General\General.vb:line 1532
at StaxRip.GlobalClass.ProcessJobs() in
D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 36
The source is available from github:
Public Class PowerRequest
Private Shared CurrentPowerRequest As IntPtr
Shared Sub SuppressStandby()
If CurrentPowerRequest <> IntPtr.Zero Then
PowerClearRequest(CurrentPowerRequest,
PowerRequestType.PowerRequestSystemRequired)
CurrentPowerRequest = IntPtr.Zero
End If
Dim pContext As POWER_REQUEST_CONTEXT
pContext.Flags = &H1 'POWER_REQUEST_CONTEXT_SIMPLE_STRING
pContext.Version = 0 'POWER_REQUEST_CONTEXT_VERSION
pContext.SimpleReasonString = "Standby suppressed by StaxRip" 'shown
when the command "powercfg -requests" is executed
CurrentPowerRequest = PowerCreateRequest(pContext)
If CurrentPowerRequest = IntPtr.Zero Then
Dim err = Marshal.GetLastWin32Error()
If err <> 0 Then Throw New Win32Exception(err)
End If
Dim success = PowerSetRequest(CurrentPowerRequest,
PowerRequestType.PowerRequestSystemRequired)
If Not success Then
CurrentPowerRequest = IntPtr.Zero
Dim err = Marshal.GetLastWin32Error()
If err <> 0 Then Throw New Win32Exception(err)
End If
End Sub
Shared Sub EnableStandby()
If CurrentPowerRequest <> IntPtr.Zero Then
Dim success = PowerClearRequest(CurrentPowerRequest,
PowerRequestType.PowerRequestSystemRequired)
If Not success Then
CurrentPowerRequest = IntPtr.Zero
Dim err = Marshal.GetLastWin32Error()
If err <> 0 Then Throw New Win32Exception(err)
Else
CurrentPowerRequest = IntPtr.Zero
End If
End If
End Sub
Enum PowerRequestType
PowerRequestDisplayRequired
PowerRequestSystemRequired
PowerRequestAwayModeRequired
PowerRequestExecutionRequired
End Enum
<DllImport("kernel32.dll", SetLastError:=True)>
Shared Function PowerCreateRequest(ByRef Context As POWER_REQUEST_CONTEXT)
As IntPtr
End Function
<DllImport("kernel32.dll", SetLastError:=True)>
Shared Function PowerSetRequest(PowerRequestHandle As IntPtr, RequestType
As PowerRequestType) As Boolean
End Function
<DllImport("kernel32.dll", SetLastError:=True)>
Shared Function PowerClearRequest(PowerRequestHandle As IntPtr, RequestType
As PowerRequestType) As Boolean
End Function
<StructLayout(LayoutKind.Sequential, CharSet:=CharSet.Unicode)>
Structure POWER_REQUEST_CONTEXT
Public Version As UInt32
Public Flags As UInt32
<MarshalAs(UnmanagedType.LPWStr)>
Public SimpleReasonString As String
End Structure
End Class
Returning STATUS_SUCCESS for Nt{Create,Set,Clear}PowerRequest gets rid of the
errors. AFAICT it should be pretty safe to just return success from these three
functions, right?
Relevant console-output:
009c:fixme:ntdll:NtCreatePowerRequest (0x22d5e8, 0x22d5f0): stub
009c:fixme:ntdll:NtSetPowerRequest (0x110ea80, 1): stub
.
.
009c:fixme:ntdll:NtClearPowerRequest (0x110ea80, 1): stub
--
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.