[Bug 49611] New: All 16 & 32 bit windows apps crash when opening a file
https://bugs.winehq.org/show_bug.cgi?id=49611 Bug ID: 49611 Summary: All 16 & 32 bit windows apps crash when opening a file 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: michael.f.winthrop(a)gmail.com Distribution: --- Created attachment 67786 --> https://bugs.winehq.org/attachment.cgi?id=67786 Program Error Details From WINE 5.0.1 opend as user After upgrade from WINE 3.x and wineRT to WINE 5.0.1 under KDE Ubuntu 18.04 LTS, 16 bit applications such as MidiPiano and STUDIO crash when opening a file. STUDIO is running very well on this machine under VirtualBox with no file problems. Under previous version of WINE (KDE Ubuntu 16.04 LTS and 18.04 LTS), STUDIO crashed when storing a new file but always succeeded storage first. WINE 5.0.1 was installed as upgrade to previous WINE 3x. I provided the information as taken from WINE started by root, which gave me full screen of applications, error in windows box and in Terminal screen. Example STUDIO included. When opening as 'user' the WINE screen with ornaments opens application, and on crash, leaves info only on terminal screen. -- 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=49611 --- Comment #1 from Austin English <austinenglish(a)gmail.com> --- You say all applications crash when opening a file..does this occur with 'wine notepad'? In any event, please try reinstalling your application in a new WINEPREFIX. -- 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=49611 --- Comment #2 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- @ Austin English. I just say your note and did as you suggested. Yes it crashes the same way when I try to open a file from WINE Notepad. -- 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=49611 --- Comment #3 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to Austin English from comment #1)
You say all applications crash when opening a file..does this occur with 'wine notepad'?
In any event, please try reinstalling your application in a new WINEPREFIX.
I just saw your note and did open Notepad and try to open a file. It crashed the same was as noted above. -- 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=49611 --- Comment #4 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to Michael F Winthrop from comment #2)
@ Austin English. I just saw your note and did as you suggested. Yes it crashes the same way when I try to open a file from WINE Notepad.
-- 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=49611 --- Comment #5 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- Do not know about reinstalling in a new WINEPREFIX. Please tell what I should do. Also, please excuse my feeble errors at an initial response. Could not edit my first note to correct "say" to "saw". -- 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=49611 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #6 from joaopa <jeremielapuree(a)yahoo.fr> --- In a terminal, it is enough (I assume you are at /home/"mylogin"): rm -fR .wine winecfg -- 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=49611 --- Comment #7 from joaopa <jeremielapuree(a)yahoo.fr> --- I forgot to say: when you report a bug, please use the latest vanilla wine. Currently, it is wine-5.13. So update wine before reporting. -- 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=49611 --- Comment #8 from joaopa <jeremielapuree(a)yahoo.fr> --- And the lats: Does there exist free download of the applications that you use. -- 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=49611 --- Comment #9 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to joaopa from comment #7)
I forgot to say: when you report a bug, please use the latest vanilla wine. Currently, it is wine-5.13. So update wine before reporting.
I am using the latest compatible with KDE Ubuntu 18.04 per Ubuntu source ppas. I cannot be sure that WINE 5.1.3 will run in this O/S. -- 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=49611 --- Comment #10 from joaopa <jeremielapuree(a)yahoo.fr> ---
I cannot be sure that WINE 5.1.3 will run in this O/S.
https://wiki.winehq.org/Ubuntu -- 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=49611 --- Comment #11 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to Michael F Winthrop from comment #9)
(In reply to joaopa from comment #7)
I forgot to say: when you report a bug, please use the latest vanilla wine. Currently, it is wine-5.13. So update wine before reporting.
I am using the latest compatible with KDE Ubuntu 18.04 per Ubuntu source ppas. I cannot be sure that WINE 5.1.3 will run in this O/S.
Also, I bought my program in 1996. I still have the CD. A newer version surfaced on the internet as abandonware. That is the version I am using. The ID to search is Midisoft Studio 4 for Windows 95. This site claims to currently have a copy. Several say they have it as a free download, but I cannot find it. https://vetusware.com/download/MIDISOFT Studio 4.0 4.0/?id=5666 -- 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=49611 --- Comment #12 from joaopa <jeremielapuree(a)yahoo.fr> --- Is it this software: https://vetusabandonware.com/download/MIDISOFT%20Studio%204.0%204.0/?id=8824 ? -- 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=49611 --- Comment #13 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- Installing wine-devel 5.1.3 First complaint: Wine could not find a wine-mono package which is needed for .NET applications to work correctly. Wine can automatically download and install it for you. Note: it is recommended to use your distribution's recommended packages instead. See https://wiki.winehq.org/Mono for details. I started this as sudo with: apt-get install --install-suggests winehq-devel from console dad(a)dad314159:~$ wine /home/dad/.wine/drive_c/Studio4/STUDIO.EXE & [1] 11238 dad(a)dad314159:~$ 00b8:err:module:import_dll Library msdmo.dll (which is needed by L"C:\\windows\\system32\\mp3dmod.dll") not found 00b8:fixme:file:NtLockFile I/O completion on lock not implemented yet 00b8:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0024:err:environ:run_wineboot boot event wait timed out 00d4:err:environ:run_wineboot boot event wait timed out 00d8:err:vulkan:wine_vk_init Failed to load libvulkan.so.1. 00d8:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION Killed via "Close window" wine: Unhandled page fault on read access to FFFFFFFF at address 00000EF1 (thread 00d8), starting debugger... winedbg: Internal crash at 0x7bc25735 Will try again and accept wine suggestion: Loaded applicatio without complaint but crashed on "open file" Will re-install and try again. -- 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=49611 --- Comment #14 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- dad(a)dad314159:~$ wine /home/dad/.wine/drive_c/Studio4/STUDIO.EXE & [1] 16642 dad(a)dad314159:~$ 00c4:err:vulkan:wine_vk_init Failed to load libvulkan.so.1. 00c4:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION wine: Unhandled page fault on read access to FFFFFFFF at address 000004D8 (thread 00c4), starting debugger... winedbg: Internal crash at 0x7bc25735 wine client error:e0: write: Bad file descriptor [1]+ Exit 1 wine /home/dad/.wine/drive_c/Studio4/STUDIO.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=49611 --- Comment #15 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- Note latest install did not recommend missing dependency. The first time (when it did) it timed out while I was typing h\what had occurred up till 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.
https://bugs.winehq.org/show_bug.cgi?id=49611 --- Comment #16 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to joaopa from comment #12)
Is it this software: https://vetusabandonware.com/download/MIDISOFT%20Studio%204.0%204.0/?id=8824 ?
Looks like it. I have been using my copy for 20+ years. -- 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=49611 --- Comment #17 from joaopa <jeremielapuree(a)yahoo.fr> --- For problems to install wine, please use the users forum. Bugzilla is not here to help to install wine. Can you attach a file that makes wine crash for you?
wine /home/dad/.wine/drive_c/Studio4/STUDIO.EXE That is a bad way to launch an application with wine. Good way: cd /home/dad/.wine/drive_c/Studio4 wine STUDIO.EXE
Did you check you set up wine version at win98 in winecfg?
I provided the information as taken from WINE started by root That is a terribly bad way to use wine. Always use wine as normal user.
-- 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=49611 --- Comment #18 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to joaopa from comment #17)
For problems to install wine, please use the users forum. Bugzilla is not here to help to install wine.
Can you attach a file that makes wine crash for you?
wine /home/dad/.wine/drive_c/Studio4/STUDIO.EXE That is a bad way to launch an application with wine. Good way: cd /home/dad/.wine/drive_c/Studio4 wine STUDIO.EXE
Did you check you set up wine version at win98 in winecfg?
I provided the information as taken from WINE started by root That is a terribly bad way to use wine. Always use wine as normal user.
followed revised start for studio4. Same result. Followed information listed in https://wiki.winehq.org/Mono removed wine-mono 4.5. Instructions were: Prefix Local Install Wine will automatically download and install the appropriate Wine Mono MSI on prefix update, so this shouldn't usually be necessary. If you wish to use a different MSI installer than the one you'd get automatically: Obtain the MSI file you wish to use, either from https://dl.winehq.org/wine/wine-mono/ or by running "make msi" in a build tree. It's possible you already have the one you want in ~/.cache/wine. Run "wine uninstaller" and remove "Wine Mono Runtime" and "Wine Mono Windows Support" if you have them. Run "wine msiexec /i path/to/wine-mono.msi" Last instruction does not work in root. (wine msiexec /i etc.) Ran wine uninstaller as user and have wine-mono and support 4.9.4. -- 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=49611 --- Comment #19 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- https://github.com/BeRo1985/pasvulkan/issues/13 Deals with the following error, but I do not know if it matters: dad(a)dad314159:~/.wine/drive_c/Studio4$ wine STUDIO.EXE winearch=win32 00cc:err:vulkan:wine_vk_init Failed to load libvulkan.so.1. 00cc:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION wine: Unhandled page fault on read access to FFFFFFFF at address 000004D8 (thread 00cc), starting debugger... winedbg: Internal crash at 0x7bc25735 wine client error:e8: write: Bad file descriptor -- 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=49611 --- Comment #20 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to joaopa from comment #17)
For problems to install wine, please use the users forum. Bugzilla is not here to help to install wine.
Can you attach a file that makes wine crash for you?
wine /home/dad/.wine/drive_c/Studio4/STUDIO.EXE That is a bad way to launch an application with wine. Good way: cd /home/dad/.wine/drive_c/Studio4 wine STUDIO.EXE
Did you check you set up wine version at win98 in winecfg?
I provided the information as taken from WINE started by root That is a terribly bad way to use wine. Always use wine as normal user.
Yes. It is configured doe WinXP (same way as before upgrade) -- 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=49611 --- Comment #21 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- I believe this is the problem: dad(a)dad314159:/usr/lib/x86_64-linux-gnu$ ls -l libvulkan* lrwxrwxrwx 1 root root 14 Jan 25 2019 libvulkan.so -> libvulkan.so.1 lrwxrwxrwx 1 root root 19 Jan 25 2019 libvulkan.so.1 -> libvulkan.so.1.1.70 -rw-r--r-- 1 root root 322096 Jan 25 2019 libvulkan.so.1.1.70 For some reason wine is not accepting the link from libvulkan.so.1 to libvulkan.so.1.1.70 as the correct file to use. This crashed the file lookup by wine. -- 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=49611 --- Comment #22 from joaopa <jeremielapuree(a)yahoo.fr> --- You have to install the 32 bit version of libraries. -- 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=49611 --- Comment #23 from joaopa <jeremielapuree(a)yahoo.fr> --- and again
Can you attach a file that makes wine crash for you?
-- 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=49611 Michael F Winthrop <michael.f.winthrop(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michael.f.winthrop(a)gmail.co | |m --- Comment #24 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- Created attachment 67809 --> https://bugs.winehq.org/attachment.cgi?id=67809 Studio That I used on VirtualBox and Wine 3.x but 5.1.3 fails file open -- 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=49611 --- Comment #25 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to joaopa from comment #23)
and again
Can you attach a file that makes wine crash for you?
Done -- 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=49611 --- Comment #26 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to joaopa from comment #22)
You have to install the 32 bit version of libraries.
Was done before, but did again. nojoy -- 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=49611 --- Comment #27 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to Michael F Winthrop from comment #25)
(In reply to joaopa from comment #23)
and again
Can you attach a file that makes wine crash for you?
Done
I have several other apps that do the same, but Studio is the only one I need wine for. -- 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=49611 --- Comment #28 from joaopa <jeremielapuree(a)yahoo.fr> --- Please attach the console output when launching wine in a terminal with the following command: WINEDEBUG=+loaddll wine notepad&>log.txt -- 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=49611 --- Comment #29 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to joaopa from comment #28)
Please attach the console output when launching wine in a terminal with the following command: WINEDEBUG=+loaddll wine notepad&>log.txt
I did a cut and paste of the command as user. It crashed with no console output. I repeated the command as sudo and was able to open a file selection window. This also left no console 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.
https://bugs.winehq.org/show_bug.cgi?id=49611 --- Comment #30 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to Michael F Winthrop from comment #29)
(In reply to joaopa from comment #28)
Please attach the console output when launching wine in a terminal with the following command: WINEDEBUG=+loaddll wine notepad&>log.txt
I did a cut and paste of the command as user. It crashed with no console output.
I repeated the command as sudo and was able to open a file selection window. I opened a file and this worked as root. This also left no console output.
Correction: I repeated the command as sudosu and was able to open a file selection window.
This also left no console output.
I used sudo from user prompt and nothing happened at all. -- 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=49611 --- Comment #31 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to Michael F Winthrop from comment #30)
(In reply to Michael F Winthrop from comment #29)
(In reply to joaopa from comment #28)
Please attach the console output when launching wine in a terminal with the following command: WINEDEBUG=+loaddll wine notepad&>log.txt
I did a cut and paste of the command as user. It crashed with no console output.
I repeated the command as sudo and was able to open a file selection window. This also left no console output.
Correction: I repeated the command as sudosu and was able to open a file selection window. I opened a file and this worked as root. <<<< This was misplaced above
This also left no console output.
I used sudo from user prompt and nothing happened at all.
-- 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=49611 --- Comment #32 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- Created attachment 67811 --> https://bugs.winehq.org/attachment.cgi?id=67811 Attempt to workaround links to libvulkan.so.1 via replace with actual files -- 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=49611 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 CC| |o.dierick(a)piezo-forte.be Status|UNCONFIRMED |NEEDINFO --- Comment #33 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, "NEVER run Wine as root!" - Wine FAQ, Section 6.2 https://wiki.winehq.org/FAQ#Should_I_run_Wine_as_root.3F Please STOP running Wine as root (or sudo variations). This is unsupported and invalid. Any attempt at using a wineprefix with root access will break the prefix and you have to restart from scratch. This includes all files outside of wineprefix opened by the application as root. Using root as an attempt to fix issues can only make them worse. "NEVER run Wine as root!", not even once. And please, out of respect for the people trying to help you here, STOP taking initiatives and listen to what people say. Only do what is asked and don't change things that nobody asked you to change. Otherwise, we'll be unable to follow you and give proper advice. If 'wine notepad' doesn't work, your Wine install is broken. That must be fixed first. So, please attach a normal (=without WINEDEBUG) terminal output of notepad. Instructions to get a log can be found there: https://wiki.winehq.org/FAQ#get_log And I repeat: Unless you know what you're doing, don't change anything to your system. Just give us the log file and wait until we tell you what to try next. 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.
https://bugs.winehq.org/show_bug.cgi?id=49611 --- Comment #34 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Michael F Winthrop from comment #32)
Created attachment 67811 [details] Attempt to workaround links to libvulkan.so.1 via replace with actual files
Restore those files to their original state. There is no problem with them. MIDISOFT Studio 4 is a 32-bit application so Wine runs in 32-bit mode and depends on 32-bit libraries. As joaopa said, you need to install the 32-bit version of the libvulkan library. The files in /usr/lib/x86_64-linux-gnu are 64-bit version of the libraries. Wine 3.x didn't depend on vulkan library. Wine 5.x does, so installing the 32-bit libvulkan ~may~ fix your issue. On Debian and Ubuntu this can be done with the command: sudo apt-get install libvulkan1:i386 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.
https://bugs.winehq.org/show_bug.cgi?id=49611 --- Comment #35 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to Olivier F. R. Dierick from comment #34)
(In reply to Michael F Winthrop from comment #32)
Created attachment 67811 [details] Attempt to workaround links to libvulkan.so.1 via replace with actual files
Restore those files to their original state. There is no problem with them.
MIDISOFT Studio 4 is a 32-bit application so Wine runs in 32-bit mode and depends on 32-bit libraries.
As joaopa said, you need to install the 32-bit version of the libvulkan library.
The files in /usr/lib/x86_64-linux-gnu are 64-bit version of the libraries.
Wine 3.x didn't depend on vulkan library. Wine 5.x does, so installing the 32-bit libvulkan ~may~ fix your issue.
On Debian and Ubuntu this can be done with the command: sudo apt-get install libvulkan1:i386
Regards.
Took you advice. Restored .w as noted in link ou provided. Checked that no files were root (own or group) [will refrain from root as directed.] lrwxrwxrwx 1 root root 14 Jan 25 2019 libvulkan.so -> libvulkan.so.1 lrwxrwxrwx 1 root root 19 Jan 25 2019 libvulkan.so.1 -> libvulkan.so.1.1.70 -rw-r--r-- 1 root root 322096 Jan 25 2019 libvulkan.so.1.1.70
>>>>>>>Returned all links as originally found
>>>>>>>then performed "sudo apt-get install libvulkan1:i386"
>>>>>>>no problems encountered
>>>>>>>rebooted
dad(a)dad314159:~$ wine notepad &> log.txt dad(a)dad314159:~$ cat log.txt 0024:err:module:DelayLoadFailureHook failed to delay load comctl32.dll.HIMAGELIST_QueryInterface wine: Call from 7B00F0BF to unimplemented function comctl32.dll.HIMAGELIST_QueryInterface, aborting wine: Unimplemented function comctl32.dll.HIMAGELIST_QueryInterface called at address 7B00F0BF (thread 0024), starting debugger... winedbg: Internal crash at 0x7bc25735 -- 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=49611 --- Comment #36 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- Created attachment 67812 --> https://bugs.winehq.org/attachment.cgi?id=67812 Notepad (normal wine exec) log.txt file -- 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=49611 --- Comment #37 from joaopa <jeremielapuree(a)yahoo.fr> --- Is it the console output with a fresh new wine prefix? -- 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=49611 --- Comment #38 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- No. So I created a new prefix (see log for that and log for notepad execution. Note. notepad could open, close, and save a file. Crazy number of errors recorded. -- 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=49611 --- Comment #39 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- Created attachment 67813 --> https://bugs.winehq.org/attachment.cgi?id=67813 notepad log and new-prefix-complaints Essentially original problem seems settled, but was asked to allow install of gecko and another file while new prefix was created. 2020-07-27-1128PM-EST-log-and-nrw-prefix-complaints.txt file is disturbing. -- 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=49611 --- Comment #40 from joaopa <jeremielapuree(a)yahoo.fr> --- try: rm -fR .wine rm -f ~/.local/share/mime/packages/x-wine* rm -f ~/.local/share/applications/wine-extension* rm -f ~/.local/share/icons/hicolor/*/*/application-x-wine-extension* rm -f ~/.local/share/mime/application/x-wine-extension* WINEARCH=win32 wine notepad -- 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=49611 --- Comment #41 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- Created attachment 67814 --> https://bugs.winehq.org/attachment.cgi?id=67814 Cleanup of .local files to remove execution errors almost clear for notebook. -- 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=49611 --- Comment #42 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to joaopa from comment #40)
try: rm -fR .wine rm -f ~/.local/share/mime/packages/x-wine* rm -f ~/.local/share/applications/wine-extension* rm -f ~/.local/share/icons/hicolor/*/*/application-x-wine-extension* rm -f ~/.local/share/mime/application/x-wine-extension* WINEARCH=win32 wine notepad
Repeated suggestion and this time less problems with notebook, but still some: dad(a)dad314159:~$ WINEARCH=win32 wine notepad Could not parse file "/home/dad/.local/share/applications/gsview-2.desktop": Invalid key name: Path[$e] Could not parse file "/home/dad/.local/share/applications/gedit-2.desktop": Invalid key name: Path[$e] Could not parse file "/home/dad/.local/share/applications/gsview.desktop": Invalid key name: Path[$e] Could not parse file "/home/dad/.local/share/applications/Kate.desktop": Invalid key name: Path[$e] -- 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=49611 --- Comment #43 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- notebook should say notepad (sorry) -- 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=49611 --- Comment #44 from joaopa <jeremielapuree(a)yahoo.fr> --- As already said, it is not a user forum. It is a bugzilla. Clearly, it is not a bug in wine. You broke your user folder when using wine as root. rm -fR .wine rm -f ~/.local/share/mime/packages/x-wine* rm -fR ~/.local/share/applications rm -f ~/.local/share/icons/hicolor/*/*/application-x-wine-extension* rm -f ~/.local/share/mime/application/x-wine-extension* WINEARCH=win32 wine notepad -- 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=49611 --- Comment #45 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- Then what is, is. Thank you for your persistence helping me. I will stay away from root with wine. I suggest that you put a control on wine such that it will not work from root, or give a nasty warning. I did look up wine faq and followed that advice after my error with root was specified. If there are deeper errors still, I cannot say. Cheers -- 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=49611 --- Comment #46 from joaopa <jeremielapuree(a)yahoo.fr> --- At least, does your application (studio4) work now? -- 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=49611 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |UNCONFIRMED Ever confirmed|1 |0 --- Comment #47 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, (In reply to joaopa from comment #44)
As already said, it is not a user forum. It is a bugzilla. Clearly, it is not a bug in wine. You broke your user folder when using wine as root.
Yes, but we still have to check if the original issue with MIDISOFT Studio 4 was fixed by installing 32-bit libvulkan, so we kind-of need to fix the file permissions too. (In reply to joaopa from comment #44)
rm -fR .wine rm -f ~/.local/share/mime/packages/x-wine* rm -fR ~/.local/share/applications rm -f ~/.local/share/icons/hicolor/*/*/application-x-wine-extension* rm -f ~/.local/share/mime/application/x-wine-extension* WINEARCH=win32 wine notepad
Be careful when asking to 'rm' things. That deletes the files definitively. Make sure to backup any valuable file before deleting them. It is usually better to rename, or move the files/directories away when renaming is not enough. (In reply to Michael F Winthrop from comment #39)
Created attachment 67813 [details] notepad log and new-prefix-complaints
wineboot output is ok (it is normal to have those few ERR and FIXME lines). notepad output is ok, except for the broken files.
Essentially original problem seems settled, but was asked to allow install of gecko and another file while new prefix was created. 2020-07-27-1128PM-EST-log-and-nrw-prefix-complaints.txt file is disturbing.
If you installed them, Wine will not ask you for Mono or Gecko again, until the next version upgrade. (In reply to Michael F Winthrop from comment #42)
Repeated suggestion and this time less problems with notebook, but still some: dad(a)dad314159:~$ WINEARCH=win32 wine notepad Could not parse file "/home/dad/.local/share/applications/gsview-2.desktop": Invalid key name: Path[$e] Could not parse file "/home/dad/.local/share/applications/gedit-2.desktop": Invalid key name: Path[$e] Could not parse file "/home/dad/.local/share/applications/gsview.desktop": Invalid key name: Path[$e] Could not parse file "/home/dad/.local/share/applications/Kate.desktop": Invalid key name: Path[$e]
To fix your file permissions you have to find all files owned by root in your HOME directory and change the ownership back to your normal user (owner and group). Bugzilla is not meant to be a user help forum, so you'll have to search the web to get help for that: https://unix.stackexchange.com/questions/22747/finding-files-by-their-owner-... https://askubuntu.com/questions/6723/change-folder-permissions-and-ownership Once the files and directories are owned by your user again, you may either try to restore the wineprefix of your old MIDISOFT Studio 4 installation. If it still doesn't work, reinstall the application in a new wineprefix, as you did with notepad. 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.
https://bugs.winehq.org/show_bug.cgi?id=49611 --- Comment #48 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to joaopa from comment #46)
At least, does your application (studio4) work now?
No better than originally except different problems. Notepad works OK. My application reads MIDI connection and converts to music notation as it was designed to do. When I try to save the file (midi file) a window pops up telling me there was a big error. The error details can be viewed by mousing a button. When I do, everything crashes. See attachment. -- 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=49611 --- Comment #49 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- Created attachment 67815 --> https://bugs.winehq.org/attachment.cgi?id=67815 Studio Crash record from terminal -- 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=49611 --- Comment #50 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- repeated and: "The program winevdm.exe has encountered a serious problem and needs to close." I killed the window and saw this info: dad(a)dad314159:~/.wine/drive_c/Studio4$ wine studio.exe 00c0:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION wine: Unhandled page fault on read access to FFFFFFFF at address 000004D8 (thread 00c0), starting debugger... Killed -- 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=49611 --- Comment #51 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to Olivier F. R. Dierick from comment #47)
Hello,
(In reply to joaopa from comment #44)
As already said, it is not a user forum. It is a bugzilla. Clearly, it is not a bug in wine. You broke your user folder when using wine as root.
Yes, but we still have to check if the original issue with MIDISOFT Studio 4 was fixed by installing 32-bit libvulkan, so we kind-of need to fix the file permissions too.
(In reply to joaopa from comment #44)
rm -fR .wine rm -f ~/.local/share/mime/packages/x-wine* rm -fR ~/.local/share/applications rm -f ~/.local/share/icons/hicolor/*/*/application-x-wine-extension* rm -f ~/.local/share/mime/application/x-wine-extension* WINEARCH=win32 wine notepad
Be careful when asking to 'rm' things. That deletes the files definitively. Make sure to backup any valuable file before deleting them. It is usually better to rename, or move the files/directories away when renaming is not enough.
(In reply to Michael F Winthrop from comment #39)
Created attachment 67813 [details] notepad log and new-prefix-complaints
wineboot output is ok (it is normal to have those few ERR and FIXME lines). notepad output is ok, except for the broken files.
Essentially original problem seems settled, but was asked to allow install of gecko and another file while new prefix was created. 2020-07-27-1128PM-EST-log-and-nrw-prefix-complaints.txt file is disturbing.
If you installed them, Wine will not ask you for Mono or Gecko again, until the next version upgrade.
(In reply to Michael F Winthrop from comment #42)
Repeated suggestion and this time less problems with notebook, but still some: dad(a)dad314159:~$ WINEARCH=win32 wine notepad Could not parse file "/home/dad/.local/share/applications/gsview-2.desktop": Invalid key name: Path[$e] Could not parse file "/home/dad/.local/share/applications/gedit-2.desktop": Invalid key name: Path[$e] Could not parse file "/home/dad/.local/share/applications/gsview.desktop": Invalid key name: Path[$e] Could not parse file "/home/dad/.local/share/applications/Kate.desktop": Invalid key name: Path[$e]
To fix your file permissions you have to find all files owned by root in your HOME directory and change the ownership back to your normal user (owner and group). Bugzilla is not meant to be a user help forum, so you'll have to search the web to get help for that: https://unix.stackexchange.com/questions/22747/finding-files-by-their-owner- and-file-permissions https://askubuntu.com/questions/6723/change-folder-permissions-and-ownership
Once the files and directories are owned by your user again, you may either try to restore the wineprefix of your old MIDISOFT Studio 4 installation. If it still doesn't work, reinstall the application in a new wineprefix, as you did with notepad.
Regards.
sudo ls -Rl | grep root no root owner or group in and below home directory. -- 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=49611 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #52 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, I downloaded Midisoft Studio 4 from a torrent archive (and scanned it for viruses). I could create a simple track and save/open it in SNG and MID format. However, opening one of the more complex sample MID files provided by the application itself results in a 'Out of Memory' error followed by various warnings and incomplete track loading, or by an application lock. So, there is definitely an issue. The terminal output is nearly empty and doesn't give any clue. --- terminal output after an unsuccessful MID loading --- 0074:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000142 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"wineusb" failed to start: 1114 0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 00c8:fixme:midi:handle_midi_event Unexpected event received, type = a from 14:0 (... the previous line repeats with the following occuring every few lines) 00c8:fixme:midi:handle_midi_event Unexpected event received, type = d from 14:0 (... same as above) 0024:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d --- end of terminal output --- --- terminal output when loading a file result in a process lock --- 00c4:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION wine: Unhandled page fault on read access to 01CF0298 at address 7ECC1AD1 (thread 00c4), starting debugger... 00e4:err:ntdll:RtlpWaitForCriticalSection section 00110060 "/media/wine-shares/git/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 00e4, blocked by 00c4, retrying (60 sec) --- end of terminal output --- I couldn't get a backtrace or even a winedbg crash dialog. My version of Wine 5.13 is a vanilla PE build (without wineusb support but that shouldn't make any difference here). The application doesn't start in WinME or lower mode (app crashes at startup). It runs in Win2000 and above mode, so I settled for the default win7 mode. Through it is not clear yet what it is, I confirm the issue. 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.
https://bugs.winehq.org/show_bug.cgi?id=49611 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|All 16 & 32 bit windows |Midisoft Studio 4 crashes |apps crash when opening a |when opening a file |file | -- 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=49611 --- Comment #53 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, For the record, here are possible duplicates (winevdm issues): bug 49405, bug 49619 and bug 49628. 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.
https://bugs.winehq.org/show_bug.cgi?id=49611 --- Comment #54 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- (In reply to Olivier F. R. Dierick from comment #52)
Hello,
I downloaded Midisoft Studio 4 from a torrent archive (and scanned it for viruses).
I could create a simple track and save/open it in SNG and MID format.
However, opening one of the more complex sample MID files provided by the application itself results in a 'Out of Memory' error followed by various warnings and incomplete track loading, or by an application lock.
So, there is definitely an issue.
The terminal output is nearly empty and doesn't give any clue.
--- terminal output after an unsuccessful MID loading --- 0074:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000142 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"wineusb" failed to start: 1114 0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 00c8:fixme:midi:handle_midi_event Unexpected event received, type = a from 14:0 (... the previous line repeats with the following occuring every few lines) 00c8:fixme:midi:handle_midi_event Unexpected event received, type = d from 14:0 (... same as above) 0024:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d --- end of terminal output ---
--- terminal output when loading a file result in a process lock --- 00c4:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION wine: Unhandled page fault on read access to 01CF0298 at address 7ECC1AD1 (thread 00c4), starting debugger... 00e4:err:ntdll:RtlpWaitForCriticalSection section 00110060 "/media/wine-shares/git/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 00e4, blocked by 00c4, retrying (60 sec) --- end of terminal output ---
I couldn't get a backtrace or even a winedbg crash dialog.
My version of Wine 5.13 is a vanilla PE build (without wineusb support but that shouldn't make any difference here).
The application doesn't start in WinME or lower mode (app crashes at startup). It runs in Win2000 and above mode, so I settled for the default win7 mode.
Through it is not clear yet what it is, I confirm the issue.
Regards.
Sir, I decided to do a fresh install of wine: I did the following in a terminal: "sudo apt autoremove wine-devel wine-devel-amd64 wine-devel-i386 winehq-devel winetricks" "sudo apt-get remove --autoremove wine-*" "sudo apt install wine-devel" (I already have the development ppa installed so this was no problem) "sudo nano /etc/environment"
added new line above PATH ==> WINEARCH=win32
"export WINEPREFIX=/home/dad/.prefix32" "env WINEARCH=win32 winecfg" wine: created the configuration directory '/home/dad/.prefix32' 0012:err:ole:marshal_object couldn't get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046} 0012:err:ole:marshal_object couldn't get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa} 0012:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002 0012:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002 0012:err:ole:get_local_server_stream Failed: 80004002 0014:err:ole:marshal_object couldn't get IPSFactory buffer for interface {00000131-0000-0000-c000-000000000046} 0014:err:ole:marshal_object couldn't get IPSFactory buffer for interface {6d5140c1-7436-11ce-8034-00aa006009fa} 0014:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002 0014:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002 0014:err:ole:get_local_server_stream Failed: 80004002 Could not load wine-gecko. HTML rendering will be disabled. wine: configuration in '/home/dad/.prefix32' has been updated.
Created a file called Downloads on /home/dad/.prefix/drive_c Copied the install application here
In Downloads directory executed "wine explorer"
In Explorer, double clicked install app.
0009:err:shell:HCR_GetFolderAttributes should be called for simple PIDL's only! dad(a)dad314159:~/.prefix32/drive_c/Downloads$ cd .. dad(a)dad314159:~/.prefix32/drive_c$ cls Command 'cls' not found, but there are 17 similar ones.
Ran: ( #!/bin/bash timidity -iA -Os & ) in a shell script. Can only be run once before starting WINE.
Ran "aconnect --list"
client 0: 'System' [type=kernel] 0 'Timer ' 1 'Announce ' client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 20: 'USB Uno MIDI Interface' [type=kernel,card=1] 0 'USB Uno MIDI Interface MIDI 1' client 128: 'TiMidity' [type=user,pid=25442] 0 'TiMidity port 0 ' 1 'TiMidity port 1 ' 2 'TiMidity port 2 ' 3 'TiMidity port 3 ' NOTE: Unless client 128: 'Timidity' exists, no audio will be heard. Any other client number fails. "winecfg"
Located and added ASWVEDIT.EXE and STUDIO.EXE and made both WinXP O/S
From a Studio4 Icon on my desktop: command in properties->application tab is: env WINEPREFIX="/home/dad/.prefix32" wine C:\\windows\\command\\start.exe /Unix /home/dad/.prefix32/drive_c/Studio4/STUDIO.EXE
Other than notes on the screen were off by three extra steps (e.g., middle E was shown as middle C, but the audio output was actually E, everything worked perfectly!!!! (Always this way in WINE, but offset in notation does not happen in VirtualBox) ============================================================================== I always had a MIDI device on usb when running this app, so I never saw what it would do without one. You might try the "settings" tab set to "No MIDI". Close, and restart. The WINE 5.13 installed Studio recognizes usb input from a MIDI piano without problems as long as there is a MIDI input on a USB port. The MIDI setup is via "settings" tab in the program. When the app was running under wine 3.x I used WinXP mode (32 bit). It noted about a Gig of memory space available. It played output through timidity ( #!/bin/bash timidity -iA -Os & ) in a shell script. Can only be run once before starting WINE. At some point, "timidity" was no longer reachable under old and updated O/S because "aconnect" had the default output assigned to another application. Thereafter I could not get audio because wine uses the default output every time. Also the notes on the screen were off by three extra steps (e.g., middle E was shown as middle C, but the audio output was actually E. The MIDI output was correct and the output was excellent. I used its' MIDI files with other programs. The notation is the best I have ever seen. Beats Rosegarden and MuseScore all to death. I do/did not have any problems running on VirtualBox with a WinXP O/S when in KDE Ubuntu 16.04 and now in Kubuntu 18.04. I think WINE is better (safer) to use than VirtualBox so I made a project of many years duration until it worked, but as you see, it is a problem again. My very best to the WINE team. -- 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=49611 --- Comment #55 from Michael F Winthrop <michael.f.winthrop(a)gmail.com> --- Middle C is shown as Middle E. My bad. -- 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.
participants (1)
-
WineHQ Bugzilla