January 2022 - Wine-Bugs - list.winehq.org

[Bug 52317] Microsoft Visual Studio 2008 debugger reports 'Unable to attach to the process. Operation not supported. Unknown error: 0x8000ffff' in 'Windows Vista+' mode (needs kernel32.GetNamedPipeClientComputerNameW)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52317 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://web.archive.org/web | |/20200226201149/http://down | |load.microsoft.com/download | |/8/1/d/81d3f35e-fa03-485b-9 | |53b-ff952e402520/VS2008ProE | |dition90dayTrialENUX1435622 | |.iso Keywords| |download -- 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.

Jan. 1, 2022

[Bug 52317] New: Microsoft Visual Studio 2008 debugger reports 'Unable to attach to the process. Operation not supported. Unknown error: 0x8000ffff' in 'Windows Vista+' mode (needs kernel32.GetNamedPipeClientComputerNameW)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52317 Bug ID: 52317 Summary: Microsoft Visual Studio 2008 debugger reports 'Unable to attach to the process. Operation not supported. Unknown error: 0x8000ffff' in 'Windows Vista+' mode (needs kernel32.GetNamedPipeClientComputerNameW) Product: Wine Version: 7.0-rc3 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. For the installer you need to work around bug 29354. --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/Microsoft Visual Studio 9.0/Common7/IDE $ WINEDEBUG=+seh,+relay wine ./devenv.exe >>log.txt 2>&1 ... 0120:Call KERNEL32.GetVersion() ret=3f082ff0 ... 0120:Call ntdll.wcscpy(0021e558,7b086e88 L"Service Pack 1") ret=7b052c15 0120:Ret ntdll.wcscpy() retval=0021e558 ret=7b052c15 0120:Ret KERNEL32.GetVersion() retval=1db10106 ret=3f082ff0 0120:Call KERNEL32.GetModuleHandleW(3f081cdc L"KERNEL32.DLL") ret=3f08b158 ... 0120:Ret KERNEL32.GetModuleHandleW() retval=7b600000 ret=3f08b158 0120:Call KERNEL32.GetProcAddress(7b600000,3f08b2c8 "GetNamedPipeClientProcessId") ret=3f08b168 0120:Ret KERNEL32.GetProcAddress() retval=7b6052d0 ret=3f08b168 0120:Call KERNEL32.GetProcAddress(7b600000,3f08b2e4 "GetNamedPipeClientComputerNameW") ret=3f08b176 0120:Ret KERNEL32.GetProcAddress() retval=00000000 ret=3f08b176 ... 0120:Call KERNEL32.LoadLibraryExW(02a2f018 L"C:\\Program Files\\Microsoft Visual Studio 9.0\\Common7\\Packages\\Debugger\\1033\\vsdebugui.dll",00000000,00000002) ret=3f23cd7c ... 0120:Ret KERNEL32.LoadLibraryExW() retval=3f470000 ret=3f23cd7c ... 0120:Call KERNEL32.FormatMessageW(00001300,00000000,8000ffff,00000400,0021eb18,00000000,00000000) ret=3f2b9072 ... 0120:Ret KERNEL32.FormatMessageW() retval=00000000 ret=3f2b9072 ... 0120:Call oleaut32.SysAllocString(02a2df58 L"Operation not supported. Unknown error: 0x8000ffff.") ret=3f247a9f ... 0120:Call user32.DrawTextW(0f01003f,02a2db40 L"Unable to attach to the process. Operation not supported. Unknown error: 0x8000ffff.",ffffffff,0021e7ec,00000850) ret=02036e1b ... --- snip --- Wine source: https://source.winehq.org/git/wine.git/blob/b6dc83990872106fdb957b2947b71f0… --- snip --- 733 # @ stub GetNamedPipeClientComputerNameA 734 # @ stub GetNamedPipeClientComputerNameW --- snip --- Microsoft docs: https://docs.microsoft.com/en-us/windows/win32/api/namedpipeapi/nf-namedpip… Stable download link Internet Archive for documentation. https://web.archive.org/web/20200226201149/http://download.microsoft.com/do… $ sha1sum VS2008ProEdition90dayTrialENUX1435622.iso dfb601096f62fd75af6ad62b277be79793f53b56 VS2008ProEdition90dayTrialENUX1435622.iso $ du -sh VS2008ProEdition90dayTrialENUX1435622.iso 3.4G VS2008ProEdition90dayTrialENUX1435622.iso Regards -- 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.

Jan. 1, 2022

[Bug 52316] Windows Error

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52316 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC| |o.dierick(a)piezo-forte.be --- Comment #1 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Please read and follow the instructions there: https://wiki.winehq.org/Bugs Regards. -- 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.

Jan. 1, 2022

[Bug 52316] New: Windows Error

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52316 Bug ID: 52316 Summary: Windows Error Product: Wine Version: 7.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: api-ms-win-* Assignee: wine-bugs(a)winehq.org Reporter: liaolllll5(a)iCloud.com Distribution: --- Created attachment 71477 --> https://bugs.winehq.org/attachment.cgi?id=71477 The record $winecfg open a window in a strange shape -- 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.

Jan. 1, 2022

[Bug 52315] Fractal AX8 Edit: Crash after I/O operations

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52315 --- Comment #2 from nurtyll(a)pm.me --- (In reply to Nikolay Sivov from comment #1) > Please first retest with latest wine 7.0-rc3, if it doesn't work, it will be > necessary to find what was the last wine version that worked correctly (I'm > assuming your crash started after wine upgrade and not e.g. application > upgrade?). If this is really a regression, a test would be very useful, as > described here [1]. > > [1] https://wiki.winehq.org/Regression_Testing Thank you for your help! I guess you are right, maybe an update "messed it up". I tried to upgrade to devel branch. I know that is not the right place but I couldn't do the update. I'm on Manjaro and there is no easy possibility to upgrade to wine devel, since wine devel is not supported by the software repos (including AUR). I tried to build it, but there seems to be a loop - the compiler jumps between two files, reports warnings and starts all over again. Shall I try the staging branch? -- 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.

Jan. 1, 2022

[Bug 25462] Unable to break using 'Break All' button while remote debugging with VS2008 (software breakpoint overwrites syscall instruction in VDSO page)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=25462 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- URL|http://download.microsoft.c |https://web.archive.org/web |om/download/8/1/d/81d3f35e- |/20200226201149/http://down |fa03-485b-953b-ff952e402520 |load.microsoft.com/download |/VS2008ProEdition90dayTrial |/8/1/d/81d3f35e-fa03-485b-9 |ENUX1435622.iso |53b-ff952e402520/VS2008ProE | |dition90dayTrialENUX1435622 | |.iso --- Comment #8 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, VS 2008 debugging can't be tested, it has multiple regressions in XP and Vista+ mode. Since you've tested with newer Visual Studio/debugger let's assume this specific problem is fixed with VS 2008 as well. Stable download link Internet Archive for documentation. https://web.archive.org/web/20200226201149/http://download.microsoft.com/do… $ sha1sum VS2008ProEdition90dayTrialENUX1435622.iso dfb601096f62fd75af6ad62b277be79793f53b56 VS2008ProEdition90dayTrialENUX1435622.iso $ du -sh VS2008ProEdition90dayTrialENUX1435622.iso 3.4G VS2008ProEdition90dayTrialENUX1435622.iso Regards -- 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.

Jan. 1, 2022

[Bug 48023] Visual Studio 2019 not starting

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=48023 --- Comment #5 from Lorenzo Ferrillo <lorenzofer(a)live.it> --- Edit it seems that in the current prefix the exception is present whetever I use schedtool -a 0 to launch an application, disregard (but this can be a symptom of another issue, involving maybe dotnet) -- 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.

Jan. 1, 2022

[Bug 48023] Visual Studio 2019 not starting

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=48023 Lorenzo Ferrillo <lorenzofer(a)live.it> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lorenzofer(a)live.it --- Comment #4 from Lorenzo Ferrillo <lorenzofer(a)live.it> --- I was able to make the Login UI come on screen, but it hang/close immediatly after. The hang/close seems related to an ACCESS_VIOLATION_EXCPETION being rised, sometimes failing in a seh overflow. Most times the resulting logs is different that seems to suggest that there is an initialization failure that is preventing some threaded operations to run. (For example the SetBlanket, QueryBlanket pair apeared in the log 2 times in 10 runs). Using schedtool -a0 seem to make this better, but still close/hang. +relay traces aren't useful. VS in that case exit with "Some component not found" failing to find some registry keys (in normal +reg log we can see it check for a key in VisualStudio\16.xxxxxx\Packages and then in VisualStudio\16.xxx_Config\Packages, the key being in the second one, while in +relay trace it only check the first location). Startng devenv seems to trigger a "Unhandled page fault on execute access" in winedevice.exe, then it's trying to start vsjitdebugger.exe (unlcear if it's failing to start it or just can't debug the exception) Remade winedbg the default debugger, still no info appears. (Maybe devenv is changing the protection of some memory page?) -- 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.

Jan. 1, 2022

[Bug 52315] Fractal AX8 Edit: Crash after I/O operations

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52315 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal --- Comment #1 from Nikolay Sivov <bunglehead(a)gmail.com> --- Please first retest with latest wine 7.0-rc3, if it doesn't work, it will be necessary to find what was the last wine version that worked correctly (I'm assuming your crash started after wine upgrade and not e.g. application upgrade?). If this is really a regression, a test would be very useful, as described here [1]. [1] https://wiki.winehq.org/Regression_Testing -- 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.

Jan. 1, 2022

[Bug 25462] Unable to break using 'Break All' button while remote debugging with VS2008 (software breakpoint overwrites syscall instruction in VDSO page)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=25462 Jacek Caban <jacek(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jacek(a)codeweavers.com Status|NEW |RESOLVED Resolution|--- |FIXED Fixed by SHA1| |af74bd31229e0f065448253b248 | |ec0cb3b51af26 --- Comment #7 from Jacek Caban <jacek(a)codeweavers.com> --- Yes, that mentioned commit was meant to fix this (there is another one for 32-bit syscalls). I didn't test with VS2008, but VS2019 has the same problem and it's mostly fixed there. We still have a few non-PE modules that may execute host libraries without going through our syscalls, but it already works fine in majority cases. -- 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.

Jan. 1, 2022