April 2021 - Wine-bugs - list.winehq.org

[Bug 24624] New: Audacity 1.3.12 treats all file type selections as "all files" when exporting
by wine-bugs＠winehq.org 27 Apr '21

27 Apr '21

http://bugs.winehq.org/show_bug.cgi?id=24624 Summary: Audacity 1.3.12 treats all file type selections as "all files" when exporting Product: Wine Version: 1.3.4 Platform: x86-64 URL: http://audacity.sourceforge.net/ OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: RandomAccountName(a)mail.com Created an attachment (id=31111) --> (http://bugs.winehq.org/attachment.cgi?id=31111) Terminal output In Audacity, open an audio file and then go to file -> export. On this file dialog, any selection from the "files of type" drop-down list will (apparently) be treated as "all files", which leads to two minor annoyances: 1. DLLs and other unrelated file types will be listed while browsing for a destination folder. (This doesn't happen immediately when the dialog opens, only after changing the destination directory and/or file type.) 2. If the file extension isn't specified manually, Audacity will try to append ".*" to the end of the file name and then warn that this is a non-standard extension for this type of file. -- 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.

2 10

[Bug 51068] New: winecfg doesn't open if using the intel xorg driver
by WineHQ Bugzilla 26 Apr '21

26 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=51068 Bug ID: 51068 Summary: winecfg doesn't open if using the intel xorg driver Product: Wine Version: 6.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ak-su(a)iname.com Distribution: --- Created attachment 69929 --> https://bugs.winehq.org/attachment.cgi?id=69929 winecfg 6.7 opening problem with intel xorg driver If I am using the intel xorg driver with xorg: Driver "intel" # xorg config snippet winecfg from winehq-devel 6.7 is not able to open its window. If I change to using the modesetting xorg driver in Fedora 33, winecfg 6.7 opens properly. But if I install winehq-stable 5.0.4-4.1, winecfg works just fine. (In the attached log, I press ctrl+c at line 18) -- 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.

1 1

[Bug 50867] New: wine start /unix stopped working in 6.5
by WineHQ Bugzilla 26 Apr '21

26 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=50867 Bug ID: 50867 Summary: wine start /unix stopped working in 6.5 Product: Wine Version: 6.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: duck(a)duckcorp.org Distribution: --- Quack, I just upgraded to 6.5 using WineHQ's Debian packages. My computer is using Debian unstable. When starting my games using start /unix I now get: (leaving out fixme:font:opentype_enum_font_names lines) $ wine start /unix $WINEPREFIX/drive_c/GOG\ Games/Risen\ 3\ -\ Titan\ Lords/LanguageSetup.exe Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found. If I remove start /unix in this case it works but not all programs will be happy with this unless I manually go into the right workdir, that is why I use this feature as recommended in the user's guide. 6.4 worked fine and many versions before. I did not see anything about this in the news and changelog. Has anything changed? Regards. \_o< -- 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.

1 24

[Bug 49138] New: winegcc: argc and argv arguments of main() get corrupted
by WineHQ Bugzilla 26 Apr '21

26 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=49138 Bug ID: 49138 Summary: winegcc: argc and argv arguments of main() get corrupted Product: Wine Version: 5.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: mail(a)robbertvanderhelm.nl Distribution: --- I first came across this issue with winelib compilation in Wine 5.7 while I was working on yabridge, a Wine VST bridge. The issue still persists on the latest commit in the Wine repository as I'm writing this (commit bf1abba, with the release of Wine 5.8). I'm not exactly sure what is going on, but the issue can be reproduced as follows: #include <iostream> int main(int argc, char* argv[]) { std::cout << "argc = " << argc << std::endl; std::cout << "argv[0] = " << argv[0] << std::endl; } If you compile the above (or the C-equivalent) with `wineg++ test.cpp -o test` and run test.exe, then at least on my system it will always print 70624 as the value of argc and some uninitialized looking data for argv[0]. This happens regardless of whether the program receives any command line arguments or not. Winelib applications compiled with the toolchain that comes with Wine 5.6 can be run without problems under Wine 5.7 or 5.8. The winelib compilation issue with Wine 5.7+ exists on Ubuntu 18.04, Ubuntu 20.04, Arch Linux and Manjaro, both when using the distro provided packages and when building Wine from source. -- 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.

1 3

[Bug 51002] New: Wined3d: nothing is presented in 3D window.
by WineHQ Bugzilla 26 Apr '21

26 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=51002 Bug ID: 51002 Summary: Wined3d: nothing is presented in 3D window. Product: Packaging Version: unspecified Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: acyellow(a)gmail.com CC: dimesio(a)earthlink.net Created attachment 69845 --> https://bugs.winehq.org/attachment.cgi?id=69845 d3d-error-log OS: Windows OS GPU is Nvidia and driver is installed correctly. Use Wine dll to replace the original Windows dll, including d3d9.dll, d3d11.dll, wined3d.dll, dxgi.dll. Run the following D3D11 test case, the failed frame is attached. Nothing is presented in the 3D window. There are error logs which is attached. C:\Program Files (x86)\Microsoft DirectX SDK (June 2010)\Samples\C++\Direct3D11\Bin\x64\FluidCS11.exe Any question or suggestion is welcome. -- 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.

1 5

[Bug 50939] New: Solid Edge 15: "MoveElementTo failed" when loading document previously saved under Wine
by WineHQ Bugzilla 26 Apr '21

26 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=50939 Bug ID: 50939 Summary: Solid Edge 15: "MoveElementTo failed" when loading document previously saved under Wine Product: Wine Version: 6.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: arvidb(a)fripost.org Distribution: --- Wine version: wine-6.5-157-gb0319c404a1 (master + applied patch for bug 50917). When opening a document previously saved under Wine I have to dismiss several "MoveElementTo failed" error messages. The documents eventually open successfully (and open without error messages under Windows). Documents saved under Windows does not exhibit this problem: they open without error messages also under Wine. Saving failed completely due to missing "VT_BLOB support" until very recently, see bug 50917. Terminal output when opening document (newline between each dismissal of error - 2 times in this instance): --- 0024:fixme:shell:IPersistFile_fnSaveCompleted (0xbf6468)->(L"C:\\users\\arvidb\\Recent\\AllenScrewM8.par (13).lnk"): stub 0024:fixme:storage:StorageBaseImpl_MoveElementTo (00C08420 L"\0005Rfunnyd1AvtdbfkuIaamtae3Ie" 00BF6530 L"\0005Rfunnyd1AvtdbfkuIaamtae3Ie" 1): stub 010c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 010c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. 0024:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (00B1CC3C 1 C) semi-stub 0024:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (00B1C9F4 1 C) semi-stub 0024:fixme:storage:StorageBaseImpl_MoveElementTo (09E88B08 L"\0005C3teagxwOttdbfkuIaamtae3Ie" 00BD3778 L"\0005C3teagxwOttdbfkuIaamtae3Ie" 1): stub 0024:fixme:storage:Storage_ConstructTransacted Unimplemented flags 4110012 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. 0024:fixme:reg:RegQueryInfoKeyA security argument not supported. wine: Read access denied for device L"\\??\\E:\\", FS volume label and serial are not available. wine: Read access denied for device L"\\??\\Z:\\", FS volume label and serial are not available. --- -- 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.

1 1

[Bug 50918] New: Solid Edge 15: Save as... cannot save file
by WineHQ Bugzilla 26 Apr '21

26 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=50918 Bug ID: 50918 Summary: Solid Edge 15: Save as... cannot save file Product: Wine Version: 6.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: arvidb(a)fripost.org Distribution: --- Created attachment 69732 --> https://bugs.winehq.org/attachment.cgi?id=69732 Terminal log When trying to save a file using Save as... Solid Edge complains: "Cannot save the file. You may not have write-access to the file or the directory." Simultaneously a line like this is displayed in the terminal: 0024:fixme:storage:StorageBaseImpl_MoveElementTo (0020DD28 L"\0005SummaryInformation" 0A217E98 L"\0005SummaryInformation" 1): stub I have confirmed that I do have write access to the directory by creating an empty file there with 'touch <filename>'. -- 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.

1 3

[Bug 50919] New: Solid Edge 15: Cannot finalize any feature
by WineHQ Bugzilla 26 Apr '21

26 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=50919 Bug ID: 50919 Summary: Solid Edge 15: Cannot finalize any feature Product: Wine Version: 6.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: arvidb(a)fripost.org Distribution: --- Created attachment 69733 --> https://bugs.winehq.org/attachment.cgi?id=69733 Terminal log To repeat: Start program, create new part, create new Protrusion (or Revolved Protrusion). Click a reference plane and draw a Sketch (a simple square will do). Click Finish. Expected outcome: The program should switch to the next step of Protrusion creation (depth options). New edit boxes and buttons should appear to the right of the Finish button and the view should switch to isometric/3D. Actual outcome: The program "mostly" stays in the first step: the view stays in Sketch mode and no depth options appear, but the Sketch edit-boxes disappears (see attached images). When clicking the Finish button the following appears in the terminal: 0118:fixme:reg:RegQueryInfoKeyA security argument not supported. 0118:fixme:ole:OleSetMenuDescriptor (00000000, 000300C6, 00000000, 00000000, 0B798C88), Context sensitive help filtering not implemented! 0118:fixme:ole:OleSetMenuDescriptor (00000000, 000300C6, 00000000, 00000000, 0B798C88), Context sensitive help filtering not implemented! 0118:fixme:reg:RegQueryInfoKeyA security argument not supported. <and after a short delay:> 0118:err:tooltips:TOOLTIPS_WindowProc unknown msg 041f wp=00000001 lp=00c2dcb4 -- 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.

1 6

[Bug 5322] Both MSVC6 and MSVB6 installers die very early
by WineHQ Bugzilla 26 Apr '21

26 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=5322 Mathew Hodson <mathew.hodson(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mathew.hodson(a)gmail.com | -- 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.

1 0

[Bug 5322] Both MSVC6 and MSVB6 installers die very early
by WineHQ Bugzilla 26 Apr '21

26 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=5322 Mathew Hodson <mathew.hodson(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mathew.hodson(a)gmail.com --- Comment #47 from Mathew Hodson <mathew.hodson(a)gmail.com> --- (In reply to Anastasius Focht from comment #46) > Hello folks, > > while revisiting old tickets I already stumbled across this one multiple > times. Every time I have remember myself about the improper close here. > > In short: nothing was fixed here, VC6/VB6/eVC++ installers still crash due > to missing HKEY_PERFORMANCE_DATA. > > https://bugs.winehq.org/show_bug.cgi?id=33037#c12 Shouldn't this bug be marked as a duplicate of bug 33037 then? -- 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.

1 0