https://bugs.winehq.org/show_bug.cgi?id=54825
Bug ID: 54825
Summary: Visual Studio C++ Build Tools fails to install with
'Could not find Windows Runtime type'
Product: Wine-staging
Version: 8.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lupino8211(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 74328
--> https://bugs.winehq.org/attachment.cgi?id=74328
full_install.log
I'm trying to install MSVC toolchain in wine in docker, but didn't succeed. I'm
installing tools in following order:
- dotnet48
- winecfg /v win10
- Visual Studio C++ Build Tools
Installation ends in the following error (from logs which can be found in wine
user's Temp directory):
[025c:000a][2023-04-13T20:48:57] Error 0x80131522: Rethrowing the exception
from the engine: Could not find Windows Runtime type
'Windows.Networking.Connectivity.NetworkCostType'.
but how I can inspect, these DLL's exist in the following paths:
/root/.wine/drive_c/windows/system32/windows.networking.connectivity
/root/.wine/drive_c/windows/syswow64/windows.networking.connectivity
and should contain mentioned type.
How to reproduce:
Download vs_BulidTools.exe from
https://download.visualstudio.microsoft.com/download/pr/d24d0627-f1e2-4a69-…
Install it via:
wine cmd /c start /wait vs_BuildTools.exe \--quiet --add
"Microsoft.VisualStudio.Workload.VCTools;includeRecommended" --add
"Microsoft.VisualStudio.Workload.MSBuildTools;includeRecommended" --add
"Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools;includeRecommended"
--add "Microsoft.VisualStudio.Component.VC.Tools.x86.x64;includeRecommended"
--
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=25100
Summary: the program don't start...
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: salvatore91salvatore(a)yahoo.it
....
--
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=55406
Bug ID: 55406
Summary: mIRC hangs on receiving a new PM
Product: Wine
Version: 8.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kooldioxide(a)gmail.com
Distribution: ---
This problem started once I upgraded mIRC to version 7.74.
When someone sends me a PM and this causes mIRC to open a new window, mIRC
hangs entirely, and the process keeps using a lot of CPU according to htop.
Only thing I can do at that point is kill the process.
The problem doesn't occur if I already have a query window open with the person
sending me a message.
An easy way to reproduce this is to connect to an IRC server, then from the
status window:
/msg <my_own_nick> hello
That will open a query window to yourself which triggers this behaviour as
well.
This problem occurs on two different Linux installations I tried, one with Wine
8.12 and one with Wine 8.0.2.
--
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=32900
Bug #: 32900
Summary: The Bat 5.2.2 - keyboard keys stick
Product: Wine
Version: 1.1.22
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sprog(a)online.ru
Classification: Unclassified
It happens rarely and may be related to RU keyboard layout.
You press Cntr-N a new message form is created but pressing letters on a
keyboard won't work as expected. If fact it's like you're constantly holding
right CTL key. You press right CTL again and the bug disappears....
The same happens happens with ALT key too. The probles was in Wine versions
starting from 1.4.1
Unfortunately I can't give you the conditions how to reproduce the bug. This
report is more like "think about what could go wrong". If you can advise how to
trace this problem - I'll do it.
The Bat all so has problems with ole32. From to time the Connection Center
causes OLE32 error. The conditions are unkown. It happens once if 2-3 days.
After that the connection center works but the status bar is showing OLE32
error...
--
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=55393
Bug ID: 55393
Summary: The process which started "The Bat!" is still running
after the app ist quieted
Product: Wine
Version: 8.13
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 74957
--> https://bugs.winehq.org/attachment.cgi?id=74957
Part of "ps faux" command
Setting: "The Bat!" is installed by its installer and "GnuPG" is also installed
with its installer. "The Bat!" is starting normally and the encrypting is
working.
A mail was created, encrypted, or signed and sent.
Now "The Bat!" is quieted by its menu entry.
The GUI disappears.
Now "(h)top" or "ps" shows still some processes running and can only be quieted
with "kill":
---ps faux---
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
(...)
joerg 3281 3.4 0.0 19668 19144 ? Ss 00:59 0:08
/opt/wine-devel/bin/wineserver
joerg 3285 0.0 0.0 2380696 16724 ? Ssl 00:59 0:00
C:\windows\system32\services.exe
joerg 3288 0.1 0.0 2055360 15552 ? Ssl 00:59 0:00
C:\windows\system32\winedevice.exe
joerg 3297 0.8 0.0 2297900 38264 ? Ssl 00:59 0:02
C:\windows\system32\winedevice.exe
joerg 3306 0.1 0.0 2142560 29912 ? Ssl 00:59 0:00
C:\windows\system32\plugplay.exe
joerg 3314 0.0 0.0 1919060 9596 ? Ssl 00:59 0:00
C:\windows\system32\svchost.exe -k LocalServiceNetworkRestricted
joerg 3325 0.1 0.1 2169640 86012 ? Sl 00:59 0:00
C:\windows\system32\explorer.exe /desktop
joerg 3330 0.0 0.0 2247080 14336 ? Ssl 00:59 0:00
C:\windows\system32\rpcss.exe
joerg 3618 0.4 0.0 2704816 30700 ? Ss 01:00 0:00
z:\opt\winprog\GnuPG\bin\gpg-agent.exe --homedir
c:\users\username\appdata\roaming\gnupg-tb --use-standard-socket --daemon
---///---
See also the attached log file.
Internally the GnuPG is started from The Bat! via the command line. For another
purpose (and wine bug) I wrote a little wrapper to log the commands which The
Bat!s hands over to GnuPGs exe-file (gpg.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=49845
Bug ID: 49845
Summary: Sacred Gold: very bad performance (low fps) when
zoomed out
Product: Wine
Version: 5.0.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: phaidros(a)gmx.at
Distribution: ---
Sacred 1 Gold provides 3 zoom levels: Very close, middle and zoomed out. I
guess most people really only use the zoomed out setting, the other two show
such a small portion of the world that i don't know how anybody could enjoy the
experience.
Unfortunately the zoomed out setting gives very bad performance, around 20fps
on a Ryzen 2700X @ 3.7GHz. Using the middle zoom setting fps go up to about
30-35fps and the very close zoom setting gives 55-60fps.
I don't really understand what's going on, I think this is a very old game and
a 8-core 3.7GHz CPU should have no problem whatsoever to run it. The 20fps i'm
getting make the game really unenjoyable to the extent where i would rather
boot windows to play it (where i'm getting 60fps at all zoom levels).
I tried with and without CSMT, fixing the process to a single CPU core etc.
Unfortunately no luck. It is really strange that the game would run at almost
60fps when zoomed in and then take such a massive performance hit when zooming
out.
--
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=53956
Bug ID: 53956
Summary: Sacred Underworld crashes after launching
Product: Wine
Version: 7.21
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Alexandr42suv(a)mail.ru
Distribution: ---
Created attachment 73536
--> https://bugs.winehq.org/attachment.cgi?id=73536
automatically generated backtrace
When I was trying to run Sacred Underworld 2.28, I got an error message and
game crashes. Other games or windows programs works well
CPU: Intel Core i3-4005u
GPU: Intel HD Graphics 4400
--
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=54124
Bug ID: 54124
Summary: Sacred Underworld black screen hanging
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: VladimirVSC(a)yandex.ru
Distribution: ---
Created attachment 73656
--> https://bugs.winehq.org/attachment.cgi?id=73656
Sacred Underworld crash report
When starting the game, the black screen appears which hangs until you press
Escape or anything else. Then "Application is not responding" message appears
and the game crashes to desktop. The same for stable 7.0.1 and 8.0-rc1.
--
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=39236
Bug ID: 39236
Summary: shell32:shlfileop fails if privileges not high enough
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
If the user cannot write to the root of the c: drive the test fails with the
following errors:
shlfileop.c:2497: Test failed: The file does not exist
shlfileop.c:2499: Test failed: File is not removed, ErrorCode: 1026
shlfileop.c:94: Test failed: Failure to open file
shlfileop.c:2505: Test failed: The file does not exist
shlfileop.c:2507: Test failed: File is not removed, ErrorCode: 1026
In particular one can notice this bug on the following WineTest box:
fg-win2000-rusr: Windows 2000 with a Restricted user account
The test should try to write its Unicode file in the temporary directory.
The test regression was introduced by this commit:
commit 1fc0cb75eebeb011a1f620fb96f32245d886916c
Author: Nigel Liang <ncliang(a)gmail.com>
Date: Fri Jun 8 14:25:24 2007 -0700
shell32: Conformance tests for unicode filenames and fix a bug for file
deletion.
--
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=55395
Bug ID: 55395
Summary: dinput:force_feedback - test_device_managed_effect()
sometimes fails on w8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: dinput
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
dinput:force_feedback - test_device_managed_effect() sometimes fails on w8:
driver_bus.c:290: Test failed: id 1: force_feedback.c:4180 got spurious packet
driver_bus.c:1098: Test failed: id 1: force_feedback.c:4180 expect[0]: got
0xb000f, expected 0
driver_bus.c:1099: Test failed: id 1: force_feedback.c:4180 expect[0]: got id 6
driver_bus.c:1100: Test failed: id 1: force_feedback.c:4180 expect[0]: got len
2
See https://test.winehq.org/data/patterns.html#dinput:force_feedback
These failures are specific to the 32-bit Windows 8 TestBot VM, w8, and they
happened 5 times over the past 8 months:
* 2022-12-09 win81_newtb-w8
* 2023-01-31 win81_newtb-w8
* 2023-05-05 win81_newtb-w8
* 2023-05-26 win81_newtb-w8
* 2023-07-27 win81_newtb-w8
--
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.