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

[Bug 16188] New: Wine should prompt users to save files upon system shutdown
by wine-bugs＠winehq.org Nov. 3, 2019

Nov. 3, 2019

http://bugs.winehq.org/show_bug.cgi?id=16188 Summary: Wine should prompt users to save files upon system shutdown Product: Wine Version: 1.1.9 Platform: Other URL: http://www.x.org/docs/SM/SMlib.pdf OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com http://groups.google.com/group/comp.emulators.ms-windows.wine/msg/9f45abb0f… asks, reasonably, "When I have unsaved document in any wine application (like notepad) and I log out or shut down the PC, Wine application doesn't offer me to save the document, it just kills everything. Can something be done about it?" My google-fu led me to http://lists.freedesktop.org/archives/xdg/2004-August/002898.html which led me to http://www.x.org/docs/SM/xsmp.pdf and http://www.x.org/docs/SM/SMlib.pdf Wine should probably support those somehow, and use them to notify applications of impending system shutdown. -- 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 16

[Bug 48036] New: RestoreVM: Save the commands to set up the VM in --extract-only mode
by WineHQ Bugzilla Nov. 3, 2019

Nov. 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=48036 Bug ID: 48036 Summary: RestoreVM: Save the commands to set up the VM in --extract-only mode Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- In --extract-only mode RestoreVM prints the commands to use to restore the VM. It would be better if it saved them in a file in the extract directory. This would minimize the risk that they get lost from the shell history and make it easier to edit and adjust them. -- 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 48038] New: Add an --image-dir option to RestoreVM
by WineHQ Bugzilla Nov. 3, 2019

Nov. 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=48038 Bug ID: 48038 Summary: Add an --image-dir option to RestoreVM Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- When restoring a VM on a machine that does not have much disk space in /var/lib/libvirt/images it's necessary to move the qcow images elsewhere and create a symbolic link in their place. The goal of the '--image-dir DIR' option is to automate this process. -- 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 47927] New: Is the win32/win64 VM Type distinction redundant with the Missions field
by WineHQ Bugzilla Nov. 3, 2019

Nov. 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=47927 Bug ID: 47927 Summary: Is the win32/win64 VM Type distinction redundant with the Missions field Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Currently the TestBot has four types of VMs: build, win32, win64 and wine. As expected the win32 and win64 VM types respectively correspond to 32 and 64 bit Windows VMs which directly correlates with their intrisic ability to run 32 and 64 bit Windows executables. In contrast whether a wine VM can (or should) run 32 bit Windows executables, 64 bit ones or both is not indicated by its type. Instead this is determined by the VM's Missions field. A Wine VM, a NetBSD one for instance, could be able to run 64 bit executables but not 32 bit ones. Or testing the win32 build could be done on one VM and testing the wow32 and wow64 one on another to spread the load. All VMs have this mission field, including the win32 and win64 VMs, where, like elsewhere, it will determine whether the TestBot allows running 32 and/or 64 bit executables. In other words a win64 VM will not run 64 bit executables if exe64 is not in its Missions. That makes the win32 vs. win64 distinction somewhat redundant. So maybe the two types should be merged into a single 'windows' VM type. Or maybe it should be preserved as a way to record what the VM is capable of independently of the missions currently assigned to 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.

1 1

[Bug 48033] New: Do Wine's source analysis on the TestBot server
by WineHQ Bugzilla Nov. 3, 2019

Nov. 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=48033 Bug ID: 48033 Summary: Do Wine's source analysis on the TestBot server Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The TestBot needs to collect some information about the Wine source: * The list of Wine source files (to separate Wine patches from patches for other projects). * The list of test source files (so it knows which tests to rerun when a Wine dll / program is patched). * The PARENTSRC dll dependencies (again so it knows which tests to rerun when a PARENTSRC dll is patched). This information is currently gathered on the build / Wine VMs and retrieved by the TestBot server when their reconfiguration completes. However once the TestBot has access to the Wine source (see bug 47839), it could perform this analysis itself and thus use the results as soon as a Wine update has been detected. -- 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 48030] New: Retrieve the reports/logs while the task runs
by WineHQ Bugzilla Nov. 3, 2019

Nov. 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=48030 Bug ID: 48030 Summary: Retrieve the reports/logs while the task runs Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Currently the TestBot only retrieves the task reports and logs once the VM-side script running the tests has completed (or timed out). It could be better to start downloading the reports and logs earlier, retrieving additional chunks as the files grow: * The developer could get feedback a bit sooner (but presenting partial results may require adjustments, particularly one should avoid errors such as 'it looks like the report has been truncated'). * The download could happen concurrently with the task running which could provide a small speedup. * The TestBot would at least get a partial report if the test causes the VM to crash, though that would likely not be the most interesting part. * If taking multiple screenshots (see bug 44709) we'd also likely want to start downloading them before the test has completed. We would not necessarily need to download them piecemeal but this would still imply interleaving GetFile() RPCs with the Wait() one. In all cases we'd want to limit the time we get stuck in GetFile(). -- 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 47509] New: Touhou 15.5: Antinomy of Common Flowers stopped running after upgrading the Wine version from 4.10 to 4.12.2
by wine-bugs＠winehq.org Nov. 1, 2019

Nov. 1, 2019

https://bugs.winehq.org/show_bug.cgi?id=47509 Bug ID: 47509 Summary: Touhou 15.5:Antinomy of Common Flowers stopped running after upgrading the Wine version from 4.10 to 4.12.2 Product: Wine Version: 4.12.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexsandr.2002.m(a)gmail.com Distribution: --- Created attachment 64896 --> https://bugs.winehq.org/attachment.cgi?id=64896 Console output After launch via shortcut or console with the command "wine ./th155.exe", the process "./th155.exe" works for a couple of seconds, and then the process "th155.exe -1" starts up, which just hangs in the task manager. It didn't start even after manual cleaning of Wine Prefix. After rolling back to the Stable branch, everything worked as it was. -- 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 9

[Bug 35801] New: Tweet Attacks hang when entering invalid login details
by wine-bugs＠winehq.org Nov. 1, 2019

Nov. 1, 2019

http://bugs.winehq.org/show_bug.cgi?id=35801 Bug ID: 35801 Summary: Tweet Attacks hang when entering invalid login details Product: Wine Version: 1.7.14 Hardware: x86-64 URL: http://www.tweetattackspro.com/tweetattackspro.zip OS: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Created attachment 47796 --> http://bugs.winehq.org/attachment.cgi?id=47796 Wine 1.7.14 console output 1. Run Tweet Attacks Pro where you are faced with the log-in/registration window. 2. Enter no details and hit log in. 3. Hang. System.NullReferenceException: Object reference not set to an instance of an object Workaround is dotnet20. I don't have an account to check if it does this with valid details, but with dotnet20 installed it simply tells you to enter the correct information. $ sha1sum tweetattackspro.zip 22b10a75d233882b1ccfbd36ffea2eb2282858d2 tweetattackspro.zip $ sha1sum tap/TweetAttacksProII.exe b7eb4ce3bf9fd7d7d1033b8db45fb927bd3ba78a tap/TweetAttacksProII.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.

2 6

[Bug 41741] New: The Adventures of Lomax demo crash on startup.
by wine-bugs＠winehq.org Nov. 1, 2019

Nov. 1, 2019

https://bugs.winehq.org/show_bug.cgi?id=41741 Bug ID: 41741 Summary: The Adventures of Lomax demo crash on startup. Product: Wine Version: 1.9.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: marc-alexandre.espiaut(a)etu.u-bordeaux.fr Distribution: --- Created attachment 56181 --> https://bugs.winehq.org/attachment.cgi?id=56181 Demo of The Adventures of Lomax I've tried to launch a demo of The Adventures of Lomax on la clean win32 prefix, windows version is set to Windows 95 and it crashes at launch. The demo works nicely on genuine windows. Attached here is the demo and the output log with the WINEDEBUG flags ddraw and d3d activated. -- 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 7

[Bug 38795] New: Netgear Powerline 3.1 update check fails on second run
by wine-bugs＠winehq.org Nov. 1, 2019

Nov. 1, 2019

https://bugs.winehq.org/show_bug.cgi?id=38795 Bug ID: 38795 Summary: Netgear Powerline 3.1 update check fails on second run Product: Wine Version: 1.7.45 Hardware: x86-64 URL: http://www.downloads.netgear.com/files/GDC/XAVN2001/NE TGEAR_Powerline_Setup_V3.1.0.4_230-10802-06.zip OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: Ubuntu Created attachment 51722 --> https://bugs.winehq.org/attachment.cgi?id=51722 wine-1.7.45-146-gaf55ae1 console output (first run) When the Netgear Powerline 3.1 utility is first run (automatically following the installation) it is able to check for updates. However, after closing and reopening the application it fails with the error message "Could not connect to the NETGEAR servers". The second log adds this: vfnRecordDevices open file error $ sha1sum NETGEAR_Powerline_Setup_V3.1.0.4_230-10802-06.* 5a7506b35fb1e2b70f300b9cfc8df417e9d5f651 NETGEAR_Powerline_Setup_V3.1.0.4_230-10802-06.exe f6934705fec39c02a938473d6d55065dd0550e72 NETGEAR_Powerline_Setup_V3.1.0.4_230-10802-06.zip http://www.downloads.netgear.com/files/GDC/XAVN2001/NETGEAR_Powerline_Setup… -- 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 6