https://bugs.winehq.org/show_bug.cgi?id=56668
Bug ID: 56668
Summary: Visual Studio 2022 Community Edition doesn't install
in quiet mode (Mono.Security.X509.X509Store.get_Crls)
Product: Wine
Version: 9.8
Hardware: x86-64
URL: https://visualstudio.microsoft.com/vs/community/
OS: Linux
Status: NEW
Keywords: download, Installer
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Debian
Created attachment 76454
--> https://bugs.winehq.org/attachment.cgi?id=76454
installer log
austin@debian:~/Downloads$ du -sh VisualStudioSetup.exe
3.9M VisualStudioSetup.exe
austin@debian:~/Downloads$ sha1sum VisualStudioSetup.exe
5d0923c690a40a5113a0dec506c14a412b4ee2e4 VisualStudioSetup.exe
The installer will fail early if run normally / with the GUI (see bug 56644).
If quiet mode is used:
wine VisualStudioSetup-2022.exe --quiet --noweb --norestart --installPath
"%ProgramFiles%\\Microsoft Visual Studio\\2022" --add
Microsoft.Component.MSBuild
It gets a bit further, but then fails to download anything.
--
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=56644
Bug ID: 56644
Summary: Visual Studio 2022 Community Edition doesn't install
(exits before showing installer window)
Product: Wine
Version: 9.8
Hardware: x86-64
URL: https://visualstudio.microsoft.com/vs/community/
OS: Linux
Status: NEW
Keywords: download, Installer
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Debian
Created attachment 76417
--> https://bugs.winehq.org/attachment.cgi?id=76417
terminal output
austin@debian:~/Downloads$ du -sh VisualStudioSetup.exe
3.9M VisualStudioSetup.exe
austin@debian:~/Downloads$ sha1sum VisualStudioSetup.exe
5d0923c690a40a5113a0dec506c14a412b4ee2e4 VisualStudioSetup.exe
Looking at the output, I initially suspected it was a wine-mono issue.
Installing `winetricks dotnet472` doesn't help, so it's not that.
--
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=51099
Bug ID: 51099
Summary: Visual Studio Installer refuses to run with unelevated
token in quiet mode
Product: Wine-staging
Version: 6.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: w(a)zeroitlab.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
This patchset:
https://github.com/wine-staging/wine-staging/commit/811467bf6a4c43de2485b37…
breaks the second stage of Visual Studio Installer (needed for products: Visual
Studio 2015, Visual Studio 2017, Visual Studio 2019, Visual Studio Build Tools
2015, Visual Studio Build Tools 2017, Visual Studio Build Tools 2019)
Reproduction:
Skip first stage installer blocked by another bug:
wget https://aka.ms/vs/16/release/installer -O installer.zip
unzip installer.zip
mkdir "~/.wine/drive_c/Program Files (x86)/Microsoft Visual Studio"
mv Contents "~/.wine/drive_c/Program Files (x86)/Microsoft Visual
Studio/Installer"
Try invoking installer:
wine "C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\setup.exe"
/finalizeInstall install --locale en-US --productId
Microsoft.VisualStudio.Product.BuildTools --channelId VisualStudio.16.Release
--channelUri "https://aka.ms/vs/16/release/channel" --quiet --norestart
--nocache --installPath C:\BuildTools --add
Microsoft.VisualStudio.Workload.VCTools --includeRecommended
After it fails check log at `C:\Users\user\Temp`, latest one starting with
dd_installer:
[0108:0001][2021-05-05T14:22:56] Commands with --quiet or --passive should be
run elevated from the beginning.
--
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=51511
Bug ID: 51511
Summary: Cleans at startup.
Product: Wine
Version: 6.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: and.68320(a)gmail.com
Distribution: Ubuntu
Created attachment 70351
--> https://bugs.winehq.org/attachment.cgi?id=70351
Backtrace
Departure PC Radio application version 6.0.2 immediately after launch. Link to
download this program http://pcradio.ru/player/player_win/pcradio_6.0.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=56723
Bug ID: 56723
Summary: Vegas Pro 14: crash upon creating the main window
Product: Wine
Version: 9.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: paper(a)paper.us.eu.org
Distribution: ---
Created attachment 76504
--> https://bugs.winehq.org/attachment.cgi?id=76504
Terminal output from running Vegas
Wine 9.8 crashes when starting Vegas Pro 14; this looks to be specific to AMD
graphics cards as Vegas starts fine under both Intel and Nvidia. Other users[1]
seem to report this as well:
Installer works and program "runs" at first when clicked. Will eventually
crash once reaching "Creating Windows" step.
Between the time of the last test and this test, I had switched from an
NVIDIA video card to an AMD video card. I'm unsure if this hardware change
caused or contributed to this error.
A trial version of Vegas 14 can be retrieved from Magix's download center at
https://dl03.magix.com/trial_vegaspro14.exe
[1]:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=39145&iTestin…
--
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=54995
Bug ID: 54995
Summary: msys2: git clone fails with 'Socket operation on
non-socket'
Product: Wine
Version: 8.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
git clone --mirror git://sourceware.org/git/newlib-cygwin.git msys2-runtime
Cloning into bare repository '.../msys2-runtime'
010c:fixme:winsock:addrinfo_flags_to_unix unhandled flags 0x80000
fatal: packet write failed: Socket operation on non-socket
--
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=57397
Bug ID: 57397
Summary: Apps hang when trying to show tooltip
Product: Wine
Version: 9.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: bigfoothart(a)gmail.com
Distribution: ---
Created attachment 77380
--> https://bugs.winehq.org/attachment.cgi?id=77380
mso 2007 wayland debug
Apps hang when trying to show button tooltips. May require several attempts for
hovering over buttons to show tooltips to trigger the hang.
Reproduced for MS Office 2007, 2010, 2013.
Tried 9.17-9.20 versions and main branch 9.20-233-g24694dabfc5
--
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=51248
Bug ID: 51248
Summary: UrlGetPart produces different results from Windows
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: shlwapi
Assignee: wine-bugs(a)winehq.org
Reporter: jp-dev(a)inbox.ru
Distribution: ---
Created attachment 70120
--> https://bugs.winehq.org/attachment.cgi?id=70120
test program, logs
It produces difference result codes.
There is a test case on some URLs and relevant output from Windows 10 vs Wine
6.10.
Sometimes it will return a different HRESULT, or it will fail parsing the query
string.
--
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=57148
Bug ID: 57148
Summary: ghidraRun.bat shows: Syntax error: unexpected IN
Product: Wine
Version: 9.16
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
For starting up ghidra a batch file "ghidraRun.bat" can be used.
This shows the messages:
C:\ghidra_11.1.2_PUBLIC>:: Ghidra launch
Syntax error
Syntax error: unexpected IN
...
This is because there developers decided to use %# as iterator variable.
Indeed native can handle almost all ascii character
above space until tilde except these: "&,;<=>^|
The application starts up successfully because this should just detect
if it got started via a doubleclick or from a console window,
so this is just a minor issue.
https://github.com/NationalSecurityAgency/ghidra/blob/184180d54dbdf3db3c030…
--
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=37813
Bug ID: 37813
Summary: Defiance fails to connect to login Server
Product: Wine
Version: 1.7.31
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Bastyjuice(a)aol.com
The Game is patching and ist Starting without any Trouble but after launching
Defiance, the Game pop ups with a Dialog "The defiance service is unavailable
please try again later"
Michael Bond tells that he Have turned on all debug for winsock and dug through
the log. He see it create a socket and connect to login-live-us-pc.defiance.com
port 50000. After that there's a handful of failed setsockopt calls for send
and recv buffer sizes followed by a series of select and WSAFDIsSet calls
waiting for socket activity, and finally shutdown and closesocket.
--
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.