https://bugs.winehq.org/show_bug.cgi?id=37517
Bug ID: 37517
Summary: VideoReDo TVSuite H.264 crashes on loading video when
using VMR9
Product: Wine
Version: 1.7.30
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: gordon.lack(a)dsl.pipex.com
Distribution: ---
Created attachment 49929
--> https://bugs.winehq.org/attachment.cgi?id=49929
backtrace saved from crash
VideoReDo TVSuite H.264 (http://www.videoredo.com/en/ProductTVS.htm) starts up
OK.
Under Tools/Options/Playback Devices you can select VMR9 as the Video Driver
(FYI: DirectX is also listed there, but it isn't supported any more, and
actually used VMR7 as well - the option is going away). This determines the
driver used when running the editing page.
If you now load a video (mpeg, or h.264) into the program 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.
http://bugs.winehq.org/show_bug.cgi?id=21790
Summary: 3D Rad demo "BeltBall" can't use its bundled
mfc80u.dll?
Product: Wine
Version: 1.1.38
Platform: x86
URL: http://www.3drad.com/games/BeltBall%20v102.exe
OS/Version: Linux
Status: UNCONFIRMED
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
The smallest demo from http://www.3drad.com/free-pc-games.php is the 8MB
http://www.3drad.com/games/BeltBall%20v102.exe, sha1sum
d8827274480b0391ad200478b2ebe26a2658166d BeltBall v102.exe
It installs fine, but when you start it, it complains
fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.VC80.CRT" (8.0.50727.762)
and puts up a dialog saying
"The dynamic link library 'MFC80U.DLL' could not be found"
even though it's installed in
./3D Rad Games/BeltBall v102/Microsoft.VC80.MFC/mfc80u.dll
Perhaps the installer forgot to set an app path or a manifest or something?
winetricks vc2005 works around the problem.
The game installs and runs fine on Vista; I guess we need to try it
on an old XP box that doesn't have vc2005 runtimes already and see
if it works there to confirm this bug.
(I checked on Vista, and there's no entry for the app in
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths, for what it's worth.
And there doesn't seem to be a manifest file next to the .exe.)
--
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=55927
Bug ID: 55927
Summary: RestoreDC appears to fail with printers
Product: Wine
Version: 8.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kadlecf(a)fzu.cz
Distribution: ---
My wine is packed within the OpenSuse Tumbleweed distribution. Since recently,
I experience problems with printing from a custom application which worked in
earlier wine versions. Its graphical output (mostly data represented as lines
and text) is normally shown on the screen where I encounter no problems.
However, currently, when the data is sent to a printer - either one with paper
or the CUPS pdf printer -, it is clipped to a rectangle defined by the SaveDC
function. This would be OK except that the function RestoreDC
BOOL RestoreDC
(
[in] HDC hdc,
[in]
int
nSavedDC
)
;
does not work properly with the device context hdc connected to a printer
device.
In brief, the sequence
SaveDC
(functions involving clipping of the output region)
RestoreDC
does not restore the clipping region to the original one for the printer
(however, it does for the screen device context).
--
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=55986
Bug ID: 55986
Summary: Gunner3 has flickering in fullscreen
Product: Wine
Version: 8.21
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Since wine-6.1 there is flickering when running Gunner3 in fullscreen mode.
Also, from time to time old frame data is shown for a few moments making the
game
It works with winecfg virtual desktop mode, and making screenshots in
fullscreen is hard. It looks similar to the glitches in bug 45168 (but it is
unrelated).
Don't try to click on a level without having the fix from bug 41977 though, it
might crash. The menu is enough to reproduce the issue.
--
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=8051
--- Comment #190 from Alexandr Oleynikov <sashok.olen(a)gmail.com> ---
(In reply to Zeb Figura from comment #189)
> (In reply to Alexandr Oleynikov from comment #188)
> > What kind of an update do you want exactly?
> > It doesn't look like Wine 9.0-rc1 had any changes related to software vertex
> > processing, so the bug stands as it is. And it's probably unlikely that this
> > will change, especially with DXVK now being the preferred backend for games
> > (which like I mentioned before fully implements this feature).
>
> I don't know whom DXVK is "preferred" by, but it's not the position of the
> Wine project, and it's certainly our intent to implement software vertex
> processing mode. It's just not exactly trivial, and there are some
> unresolved design questions.
Of course, I was not stating it's an official position of the Wine project,
it's just merely what vast majority Linux gamers prefer for its far better
compatibility and performance for both D3D9 and D3D11 games (if hardware is
compatible), and what is used in Proton too.
--
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=56019
Bug ID: 56019
Summary: LOCAL_GetBlock not enough space in local heap
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: elias_0000_0000(a)yahoo.com
Distribution: ---
wine-8.0 (Debian 8.0~repack-4)
See this game:
https://archive.org/details/connections-1995
Same bug with that: https://bugs.winehq.org/show_bug.cgi?id=1490
both with win32 win64 prefix.
0180:err:local:LOCAL_GetBlock not enough space in local heap 076f for 1948
bytes
(etc.)
--
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=56018
Bug ID: 56018
Summary: Respondus LockDown Browser fatally hangs on loading
screen
Product: Wine
Version: 9.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: micah.haber(a)gmail.com
Distribution: ---
Created attachment 75659
--> https://bugs.winehq.org/attachment.cgi?id=75659
No backtrace available, list of deferred .dlls
Respondus LockDown Browser v. 2.1.1.05.
--
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=8051
--- Comment #189 from Zeb Figura <z.figura12(a)gmail.com> ---
(In reply to Alexandr Oleynikov from comment #188)
> What kind of an update do you want exactly?
> It doesn't look like Wine 9.0-rc1 had any changes related to software vertex
> processing, so the bug stands as it is. And it's probably unlikely that this
> will change, especially with DXVK now being the preferred backend for games
> (which like I mentioned before fully implements this feature).
I don't know whom DXVK is "preferred" by, but it's not the position of the Wine
project, and it's certainly our intent to implement software vertex processing
mode. It's just not exactly trivial, and there are some unresolved design
questions.
--
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=54396
Bug ID: 54396
Summary: Rutoken driver cannot install.
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: setupapi
Assignee: wine-bugs(a)winehq.org
Reporter: igor.bz(a)list.ru
Distribution: ---
Created attachment 73963
--> https://bugs.winehq.org/attachment.cgi?id=73963
Wine log.
Distro: Ubuntu 20.04 x64
Kernel: Linux 6.0.9
Download link:
https://download.rutoken.ru/Rutoken/Drivers/Current/rtDrivers.exe
Steps to reproduce:
- Running the installation file (rtDrivers.exe).
- An error is reported during the installation process: Error. Error code: 120
(0x00000078): Function not implemented
- Installation failure.
- The program cannot be installed.
Translation:
- Установить => Install
- Ошибка. Код ошибки: 120 (0x00000078): Функция не реализована => Error. Error
code: 120 (0x00000078): Function not implemented
- Ошибка. Код ошибки: 3758096907 (0xe000020b) => Error. Error code: 3758096907
(0xe000020b)
- 0x80070643 Сбой установки => 0x80070643 Installation failure.
--
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=16957
Summary: CreateProcess handles are inherited even when
bInheritHandles=FALSE
Product: Wine
Version: 1.1.2
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ben(a)salilab.org
Created an attachment (id=18729)
--> (http://bugs.winehq.org/attachment.cgi?id=18729)
test.c
The attached file uses CreateProcess to create a subprocess (gzip in this case)
with redirected standard output. In order for this to work properly, the output
handle created in this code must be inherited by the subprocess - thus the
bInheritHandles argument to CreateProcess must be TRUE. And indeed if this
program is compiled to test-true.exe, a simple text file 'test.in' and the gzip
binary are placed in the same directory, and then test-true.exe is run, it
successfully produces the output test.gz.
If the TRUE argument is switched to FALSE and the file is compiled again to
test-false.exe, when the program is run in the same way on a 'real' Windows
sytem (32 bit Vista Business in this case) the following is output:
gzip: stdout: Bad file descriptor
This is also fine and expected, since the output file handle was not passed to
gzip. *However* if the same test-false.exe program is run with Wine (the Fedora
10 wine-core-1.1.12-1.fc10.i386 package in this case) it runs in just the same
way as test-true.exe, generating the test.gz output.
This suggests to me that the bInheritHandles argument is ignored by Wine. As
stated, this is a minor bug but it would be nice if Wine behaved the same way
as Windows here. (In our case we discovered this problem after we tested our
program successfully under Wine, but then had it fail on a real Windows
system.) I am not familiar with the code, but hopefully it should be
straightforward enough to provide the subprocess with invalid handles if
bInheritHandles=FALSE?
--
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.