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

[Bug 53947] Daily Chthonicle is extremely slow and laggy

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53947 --- Comment #2 from Bartosz <gang65(a)poczta.onet.pl> --- Please attach terminal output. -- 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.

Nov. 30, 2022

[Bug 53947] Daily Chthonicle is extremely slow and laggy

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53947 Bartosz <gang65(a)poczta.onet.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gang65(a)poczta.onet.pl --- Comment #1 from Bartosz <gang65(a)poczta.onet.pl> --- Does "winetricks gdiplus" makes it faster? -- 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.

Nov. 30, 2022

[Bug 54027] CCDC Mercury crystallographic software is not even launched, an immediate crash occurs

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54027 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x(a)gmail.com --- Comment #3 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Hi, > Wine build: wine-6.0.3 (Ubuntu 6.0.3~repack-1) We`re almost at wine-8.0 so wine-6.0.3 is really kind of outdated. Could you update and retry in wine-7.22 and see if things change? Also: please attach console output _before_ the crash 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.

Nov. 30, 2022

[Bug 54025] Quixel Mixer 2022.1.0 Beta installer cannot find the specified path

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54025 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download CC| |xerox.xerox2000x(a)gmail.com URL| |https://quixel.com/products | |/mixer --- Comment #2 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Hi, are you trying this in wine-staging? If so, could you try vanilla wine? It installs fine here in vanilla wine, but while trying to use Staging it blocks for me with (yet) a different error that a directory is not writable. (Could be a bug Staging bug?) -- 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.

Nov. 30, 2022

[Bug 54030] New: Snagit needs Win32_Volume class ( 'select deviceid from win32_volume where driveletter =C:')

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54030 Bug ID: 54030 Summary: Snagit needs Win32_Volume class ( 'select deviceid from win32_volume where driveletter =C:') Product: Wine Version: 7.22 Hardware: x86-64 URL: https://download.techsmith.com/snagit/releases/snagit. exe OS: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: Debian Created attachment 73598 --> https://bugs.winehq.org/attachment.cgi?id=73598 +wbemprox log (prerequisite: winetricks -q dotnet48 d3dcompiler_47 arial) The program stops instantly with: 03e4:fixme:wmic:wmain command line switch L"/namespace:'\\\\root\\virtualization\\v2'" not supported so I disabled wmic (google says it is deprecated in win10) but this might really deserve a seperate bugreport. After that there's a crash, which seems to be related to: 014c:trace:wbemprox:wbem_services_ExecQuery 0000000003CD4FB0, L"WQL", L"select deviceid from win32_volume where driveletter =\"C:\"", 0x30, 0000000000000000, 000000000011E1B0 After fixing up some hacky patch with bogus values (i don't know how to implement this properly) it starts into the loginscreen, so this seems enough to get it running. There`s also a query for L"SELECT * FROM WmiMonitorBasicDisplayParams" that seems missing, but this doesn't seem to affect the startup of the program. Attached log (+wbemprox) (with bogus hack applied) -- 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.

Nov. 30, 2022

[Bug 54024] Memory Conty Installer stop working

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54024 --- Comment #1 from Rafał Mużyło <galtgendo(a)o2.pl> --- So, I'm not familiar with msvidc32 code and not sure if I'm looking at the correct file (I didn't run the installer, just unpacked it), but the one avi file I found inside seems to have following properties: ffprobe: Input #0, avi, from 'blue.avi': Duration: 00:00:02.00, start: 0.000000, bitrate: 413 kb/s Stream #0:0: Video: rawvideo, bgr24, 107x31, 10 fps, 10 tbr, 10 tbn, 10 tbc gst-discoverer-1.0: Properties: Duration: 0:00:02.000000000 Seekable: yes Live: no container #0: Audio Video Interleave (AVI) video #1: Microsoft Video 1 Stream ID: 2b419b5dc176f727bae108c00b27d1ac6d709274667d40e7876b974104c14fb6/001 Width: 107 Height: 31 Depth: 15 Frame rate: 10/1 Pixel aspect ratio: 1/1 Interlaced: false Bitrate: 401760 Max bitrate: 0 Given the mentioned commit, most likely the depth is 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.

Nov. 30, 2022

[Bug 18923] Post Mortem starts out of bounds

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=18923 imaxm <memax(a)gmx.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |memax(a)gmx.fr --- Comment #22 from imaxm <memax(a)gmx.fr> --- Bug still present in 7.22 This black screen problem is exactly the same as the one affecting the game Syberia (bug 21796) from the same developer (Microids). The workaround is the same: launch the game using "wine /path/to/Game.exe & xdotool selectwindow windowunmap" then click anywhere on the screen when you hear the game introduction (bug 21796, comment 67). -- 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.

Nov. 30, 2022

[Bug 54029] New: PDF-XChange Editor - Error [System]: Call not implemented

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54029 Bug ID: 54029 Summary: PDF-XChange Editor - Error [System]: Call not implemented 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: klasse(a)partyheld.de Distribution: --- Created attachment 73597 --> https://bugs.winehq.org/attachment.cgi?id=73597 Screenshot of the error message Upon closing of the PDF-XChange Editor, the attached error message appears. When the PDF-XChange Editor is started from the terminal, "010c:err:ole:CoUninitialize Mismatched CoUninitialize" appears upon closure of the Editor as follows: joe(a)PC:~$ env WINEPREFIX="/home/joe/.wine" wine-stable C:\\PROG\~FBU\\TRAC\~EK1\\PDF_\~VHK\\PDFXEdit.exe 010c:err:ole:CoUninitialize Mismatched CoUninitialize joe(a)PC:~$ Other than that, PDF-XChange Editor appears to work normally. (Only a brief trial was done.) The default Ubuntu Mate 22.10 installation of Wine is used: wine-7.0 (Ubuntu 7.0~repack-8) PDF-XChange Editor: Version: 9.5, build 365.0 [ ] (Nov 28 2022; 16:25:46) The issue did not appear with the previous Ubuntu Mate version (22.04) and the previously used PDF-XChange Editor version 9.5, build 361.0. -- 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.

Nov. 30, 2022

[Bug 51484] dmloader:loader fails randomly with a DMUS_E_LOADER_BADPATH error

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51484 --- Comment #3 from Michael Stefaniuc <mstefani(a)winehq.org> --- Sure, but is it actually crashing in dmloader? I'm confused about the "03f0:loader: 104 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0 skipped. dmloader:loader:03f0 done (-1073741819) in 0s 88B" https://test.winehq.org/data/e3f00bf7c944f1cde6151fde969f2b49649c3de7/linux… or "0564:loader: 104 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0 skipped. dmloader:loader:0564 done (258) in 120s 88B" from https://test.winehq.org/data/81a6c8c882e9d00a3f459983d8281327f25e333a/linux… The "104 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0 skipped." matches what we have in a successful run e.g. https://test.winehq.org/data/81a6c8c882e9d00a3f459983d8281327f25e333a/linux… But yeah, I'll need to see if I can run it under valgrind and get something useful out of it. -- 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.

Nov. 30, 2022

[Bug 54015] Accessing shared memory from Linux

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54015 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #7 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Bernat Arlandis from comment #0) > Since I guess Wine is already using Linux shared memory mechanism to > implement Windows shared memory, the blocks are already available at > /dev/shm but they use generic names that can't be associated to the tag used > on Windows. Not exactly; we use anonymous shared mappings instead. > Having these shared memory blocks created in the prefix directory with a > name containing the tag used on creation would allow us to use it from our > native applications. Or any other way to find them using the tags used on > Windows. This is not impossible in some cases, but it's also harder than it sounds. There's a bit of an impedance mismatch between NT and POSIX wrt naming: notably POSIX has a NAME_MAX restriction which doesn't apply to Windows; Windows allows all characters (including \0 I think?) except backslashes and Unix all characters except \0 and forward slashes; Windows uses UTF-16 while Unix uses a non-constant character set. -- 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.

Nov. 30, 2022