https://bugs.winehq.org/show_bug.cgi?id=55253
Bug ID: 55253
Summary: Error during update
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bahman.davoudi.dehaghi(a)gmail.com
Distribution: ---
Created attachment 74860
--> https://bugs.winehq.org/attachment.cgi?id=74860
It seems that release file is not reachable
I am using Ubuntu 20.04 with a Kubuntu desktop. My computer is:
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.8
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.15.0-76-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i3 CPU M 330 @ 2.13GHz
Memory: 3.7 GiB of RAM
I am recently receiving an error during the update saying that the release
file is not available. It seems that the release file is available here:
https://dl.winehq.org/wine-builds/ubuntu/dists/focal/. I don't know what to do.
Thanks for your time and help in advance.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=50692
Bug ID: 50692
Summary: Office 2019 Professional Plus doesn't install
Product: Wine
Version: 6.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: atillolann-1815(a)yopmail.com
Distribution: ---
Created attachment 69422
--> https://bugs.winehq.org/attachment.cgi?id=69422
Terminal Log
Tried intalling Office 2019 ProPlus Retail, after the loading screen the
installer crashes.
Using Wine 6.2-developer
Arch: x86_64
Distro: Linux Mint 19.0 Cinnamon 64 bit
--
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=56210
Bug ID: 56210
Summary: Very slow event processing (seconds)
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nagle(a)animats.com
Distribution: ---
The Windows event queue, as emulated under Wine, appears to work differently
than the real one under Windows 10.
If you build my Rust test program, ui-mock, arc branch:
[code]
git clone https://github.com/John-Nagle/ui-mock.git
cd ui-mock
git checkout arc
cargo build --release --target x86_64-pc-windows-gnu --examples
cd target/x86_64-pc-windows-gnu/release/examples
wine ui-mock.exe
[/code]
it will run fine under real Windows 10. But, built on Ubuntu 22.04 LTS with
current Rust, it behaves strangely.
Click on one of the big bars that says "placeholder", and you get get a login
popup. It doesn't do anything; this is just a GUI dummy.
Type something into the user name box.
On real Windows, characters are echoed at full speed.
[b]Under Wine 8 or 9, character echo is delayed about 3-4 seconds.[/b]
What seems to be happening is that the endless refreshing of the screen (this
is a game-type program) is starving out event processing.
This uses the Rust crates Rend3, Winit, egui, and wgpu, all of which work
cross-platform.
A newer version of Rend3 (see the Cargo.toml file for the rev number) has a
different approach to the event loop. There are two callback functions -
"event", and "redraw" in Rend3's framework. The framework itself does a
request-redraw at the end of each redraw. This seems to starve out non-redraw
event processing.
An earlier version of Rend3 did not have this problem. That older version can
be built as above, by removing the line
git checkout arc
This uses a different version of the Rend3 framework, one which only redraws
when the event queue is empty.
"winit", a standard Rust crate, claims in its documentation that non-redraw
events are always processed before redraws. But "winit", which has
platform-dependent code for Windows, seems to assume, in the Windows platform
code, that the underlying platform event queue does that. For real Windows, it
does seem to do that. But Wine's event queue does not seem to work that way.
If someone reports this problem in a commercial game, it's probably going to be
reported as "keys are sluggish". Here, you have sources for everything and can
reproduce the 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=56259
Bug ID: 56259
Summary: Microsoft Webview 2 installer hangs forever
Product: Wine
Version: 9.1
Hardware: x86-64
URL: https://developer.microsoft.com/en-us/microsoft-edge/w
ebview2/?form=MA13LH
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: Debian
Created attachment 75970
--> https://bugs.winehq.org/attachment.cgi?id=75970
stub that lets installer finish
A user reported troubles with this at the forum. Apparently (didn't verify
this) the installer works in win 7 because it downloads an older version of
webview2. When version is set to win10 another version seems to be downloaded.
See https://forum.winehq.org/viewtopic.php?t=38443
A +relay showed following trace, the kernelbase.SleepConditionVariableCS
sequence keeps going on and on forever.
Adding a stub for the function that the program tries to find
(RtlGetDeviceFamilyInfoEnum) just before the "loop" of
SleepConditionVariableCS, makes the installer succeed for me (it exits without
a success message, but the files seem to be installed).
I'll try to add a test and submit the patch later
+relay log:
0204:Call KERNEL32.GetProcAddress(6fffffc50000,14038602f
"RtlGetDeviceFamilyInfoEnum") ret=1401736ba
0204:Ret KERNEL32.GetProcAddress() retval=00000000 ret=1401736ba
0204:Call kernelbase.SleepConditionVariableCS(1403deb48,1403deb58,00000064)
ret=14020442a
0204:Call ntdll.RtlSleepConditionVariableCS(1403deb48,1403deb58,7ffffe1ff2f8)
ret=6fffff4cbd7d
0204:Ret ntdll.RtlSleepConditionVariableCS() retval=00000102 ret=6fffff4cbd7d
0204:Call ntdll.RtlNtStatusToDosError(00000102) ret=6fffff4cbd98
0204:Ret ntdll.RtlNtStatusToDosError() retval=000005b4 ret=6fffff4cbd98
0204:Ret kernelbase.SleepConditionVariableCS() retval=00000000 ret=14020442a
0204:Call kernelbase.SleepConditionVariableCS(1403deb48,1403deb58,00000064)
ret=14020442a
0204:Call ntdll.RtlSleepConditionVariableCS(1403deb48,1403deb58,7ffffe1ff2f8)
ret=6fffff4cbd7d
0204:Ret ntdll.RtlSleepConditionVariableCS() retval=00000102 ret=6fffff4cbd7d
--
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=56250
Bug ID: 56250
Summary: Elite Dangerous client gets stuck on black screen
after launch
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: brendan(a)redmandi.com
Distribution: ---
When using WINE_D3D_CONFIG='renderer=vulkan' to launch Elite, the game will
launch but then get stuck on a black screen.
The problem appears to be related to the following entry in the log:
fixme:d3d11:d3d11_device_CheckFeatureSupport Unhandled feature 0xe.
--
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=51360
Bug ID: 51360
Summary: vkGetDeviceProcAddr invalid behavior for functions
from extensions unsupported by host Vulkan instance
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winevulkan
Assignee: wine-bugs(a)winehq.org
Reporter: loothelion(a)nvidia.com
Distribution: ---
I believe the below may also be true for vkGetInstanceProcAddr, but I haven't
confirmed this locally.
The Vulkan 1.2.182 specification states the following about the behavior of
vkGetDeviceProcAddr:
> The table below defines the various use cases for vkGetDeviceProcAddr and
> expected return value for each case.
>
> The returned function pointer is of type PFN_vkVoidFunction, and must be cast to
> the type of the command being queried before use. The function pointer must only
> be called with a dispatchable object (the first parameter) that is device or a
> child of device.
>
> Table 2. vkGetDeviceProcAddr behavior
>
> device | pName | return value
> ---------------------------------------------------------------------------------------
> NULL | *[1] | undefined
> ---------------------------------------------------------------------------------------
> invalid device | *[1] | undefined
> ---------------------------------------------------------------------------------------
> device | NULL | undefined
> ---------------------------------------------------------------------------------------
> device | core device-level Vulkan command [2] | fp[3]
> ---------------------------------------------------------------------------------------
> device | enabled extension device-level commands [2] | fp[3]
> ---------------------------------------------------------------------------------------
> any other case, not covered above | NULL
>
> [1] - "*" means any representable value for the parameter (including valid
> values, invalid values, and NULL).
>
> [2] - In this function, device-level excludes all physical-device-level
> commands.
>
> [3] - The returned function pointer must only be called with a dispatchable
> object (the first parameter) that is device or a child of device e.g.
> VkDevice, VkQueue, or VkCommandBuffer.
Winevulkan's behavior differs from this slightly. Note the fifth row of the
table uses the language "enabled extension device-level commands", this means
that if a command is queried via vkGetDeviceProcAddr and isn't part of core,
the extension which introduces it must be enabled for the given VkDevice object
in order for vkGetDeviceProcAddr to return a valid function pointer, and
otherwise it should return NULL.
In order to properly conform to the Vulkan specification Winevulkan should only
expose device-level commands whose extensions have been enabled.
Note that applications should not be querying for Vulkan commands via
vkGetDeviceProcAddr if they know the extension is not supported by the
underlying implementation. However in the case of an application which does
rely on this bad behavior, Winevulkan will return a function pointer to one of
its thunks and then proceed to deference a null function pointer when it tries
to call into the underlying host Vulkan implementation.
--
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.