wine-bugs January 2013

wine-bugs@winehq.org

1 participants
9264 discussions

[Bug 32165] New: .NET installer does not set file dates
by wine-bugs＠winehq.org 31 Dec '14

31 Dec '14

http://bugs.winehq.org/show_bug.cgi?id=32165 Bug #: 32165 Summary: .NET installer does not set file dates Product: Wine Version: 1.5.16 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: djelinski1(a)gmail.com Classification: Unclassified While testing for bug 30681 I noticed that .NET installer stopped setting date/time on installed files. Regression testing points to this commit: 7b704102a8f172ae307b10914c70851b8c9ac44c is the first bad commit commit 7b704102a8f172ae307b10914c70851b8c9ac44c Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue Oct 30 11:44:10 2012 +0100 ntdll: Add a helper function to set file times. To reproduce: winetricks dotnet20 ls -l drive_c/windows/Microsoft.NET/Framework/v2.0.50727 | grep System.Data Dates should be from year 2005 -- 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.

1 5

[Bug 32276] New: Railworks Trainsimulator 2013 fails to run
by wine-bugs＠winehq.org 31 Dec '14

31 Dec '14

http://bugs.winehq.org/show_bug.cgi?id=32276 Bug #: 32276 Summary: Railworks Trainsimulator 2013 fails to run Product: Wine Version: 1.5.17 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: salamanderrake(a)gmail.com Classification: Unclassified Created attachment 42598 --> http://bugs.winehq.org/attachment.cgi?id=42598 output from terminal running steam/railworks. Railworks Trainsimulator fails to load/start/run I installed d3dx9, gdiplus, dotnet40, vcrun2010, and vcrun2005 through wine. Attached is the output from steam/railworks. -- 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.

1 23

[Bug 32295] New: WinUAE emulation window not refreshed properly when other windows move in front of it
by wine-bugs＠winehq.org 31 Dec '14

31 Dec '14

http://bugs.winehq.org/show_bug.cgi?id=32295 Bug #: 32295 Summary: WinUAE emulation window not refreshed properly when other windows move in front of it Product: Wine Version: 1.5.18 Platform: x86-64 URL: http://www.winuae.net/ OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: markk(a)clara.co.uk Classification: Unclassified Regression SHA1: 33ac850c80634c891b0c157bbffa612f70954a40 Created attachment 42625 --> http://bugs.winehq.org/attachment.cgi?id=42625 Shows window refresh issue with Wine 1.5.18 I'm testing with Lubuntu 11.10 x86-64, Nvidia driver 304.51. Openbox (non-compositing) window manager. With Wine 1.5.18, the WinUAE emulation window is not refreshed properly if you move another window in front of it. Things were fine with Wine 1.5.5. I tested several Wine releases and there are two changes in behaviour. Things first break in 1.5.13, then with 1.5.15 things break differently. I've attached a screenshot showing the 1.5.15-and-later problem. To test, install and run WinUAE. Click Start to start emulation. After a few seconds you should see some non-black graphics in the emulation window. Press F12 to open the settings window and drag it around. With Wine 1.5.13, 1.5.14: Normal mode: On pressing F12 and dragging the settings window over the emulation window, newly-exposed parts are all black. Drag the settings window so it covers most of the emulation window and release the mouse button. Now drag the setting window away so most of the emulation window is exposed. When you release the mouse button, the exposed area is rendered with the correct contents, but that is immediately overwritten with black. (You may have to repeat that a few times until you see the effect.) Virtual desktop mode: On pressing F12 the emulation window is blanked (all black). If you drag the settings window quickly over the emulation window, you can see the correct contents being rendered, then immediately overwritten with black. With Wine 1.5.15/16/18: Normal mode: Moving the settings window in front of the emulation window, newly-exposed parts of the emulation window are not refreshed properly. The only newly-exposed part which is refreshed, is that corresponding to the previous position of the settings window client area. The previous settings window decorations remain as "trash" in the emulation window. Also, Wine does not know that other parts of the emulation window may need to be refreshed. For example if the user drags (without releasing the mouse button) the settings window all over the emulation window, the emulation window fills with "trash" (copies of settings window decorations) as the settings window is moved around. Once the user releases the button, Wine refreshes only the part corresponding to the original settings window client area. Virtual desktop mode: Moving the settings window in front of the emulation window works correctly. The emulation window is refreshed properly. However, due to bug 24352 the emulation window can be brought in front of the settings window. If you click in the emulation window to do that, the emulation window frame is rendered, but the window contents are not refreshed. So the part which was under the settings window shows the old settings window contents. Drag the emulation window around. Notice that if you move it partially off the desktop and back again, newly-revealed parts are refreshed properly. So some of the settings window trash disappears as you move that part of the emulation window past the edge of the desktop and back. A regression test for the 1.5.12->1.5.13 change gave this: 33ac850c80634c891b0c157bbffa612f70954a40 is the first bad commit commit 33ac850c80634c891b0c157bbffa612f70954a40 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Sep 6 12:39:34 2012 +0200 winex11: Use window surfaces for rendering top-level windows. It can be disabled by setting "ClientSideGraphics"="n". :040000 040000 704eac5fc311e63d373e399c63a2488a6b3dedca 33fb0e5963c1326f8765334e4714060c89b21b5e M dlls I did another regression test for the 1.5.14->1.5.15 change, saying "git bisect good" for like-1.5.14 behaviour. The result: cc7bf355c50b17b2e04f754c80464289df2a9ee7 is the first bad commit commit cc7bf355c50b17b2e04f754c80464289df2a9ee7 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue Oct 9 15:21:21 2012 +0200 user32: Add support for setting the window surface visible region. :040000 040000 ca9c6946038c5e8346d67e4ce02f576034fbdaf1 230c7328031dd70f529463ac959a43dbe35b040b M dlls :040000 040000 f31ee15864da2825f030f94bba46c5e07fa0cede bde3439027c457a464fc77b95f1da4ea8f4ad161 M include -- 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.

1 7

[Bug 32366] New: Moving objets in Circuitmaker 2000 schematic is delayed (slowed down)
by wine-bugs＠winehq.org 31 Dec '14

31 Dec '14

http://bugs.winehq.org/show_bug.cgi?id=32366 Bug #: 32366 Summary: Moving objets in Circuitmaker 2000 schematic is delayed (slowed down) Product: Wine Version: 1.5.13 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: brodo(a)o2.pl Classification: Unclassified Moving objets using mouse in Circuitmaker 2000 schematic is delayed (slowed down) by appr 1 second. I made a regression test that yielded this: bash-4.2$ git bisect good 33ac850c80634c891b0c157bbffa612f70954a40 is the first bad commit commit 33ac850c80634c891b0c157bbffa612f70954a40 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Sep 6 12:39:34 2012 +0200 winex11: Use window surfaces for rendering top-level windows. It can be disabled by setting "ClientSideGraphics"="n". :040000 040000 704eac5fc311e63d373e399c63a2488a6b3dedca 33fb0e5963c1326f8765334e4714060c89b21b5e M dlls Cheers, Olek A. -- 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.

1 4

[Bug 32394] New: WinUAE GUI does not resize when its window size increases
by wine-bugs＠winehq.org 31 Dec '14

31 Dec '14

http://bugs.winehq.org/show_bug.cgi?id=32394 Bug #: 32394 Summary: WinUAE GUI does not resize when its window size increases Product: Wine Version: 1.5.19 Platform: x86-64 URL: http://www.winuae.net/files/InstallWinUAE2500.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: markk(a)clara.co.uk Classification: Unclassified Created attachment 42744 --> http://bugs.winehq.org/attachment.cgi?id=42744 After increasing window size in Wine This issue applies to the WinUAE Amiga emulator. The WinUAE GUI can be made resizeable. With that option, the user can increase the size of the WinUAE settings window and the GUI layout changes to match the new size. Under Wine however the GUI elements do not change. Newly-revealed areas of the larger window are filled with grey. To reproduce: - Download and run the WinUAE installer. Check the box to run WinUAE at the end. - When the WinUAE Properties window opens, click Miscellaneous in the treeview on the left side of the window. - Under GUI there is a "Resizeable GUI" checkbox. Check that. - The window closes and reopens and is now resizeable. - Increase the size of the window. Notice how the GUI elements don't change in size. -- 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.

1 11

[Bug 32405] New: Children of the Nile (& Demo): mouse buggy
by wine-bugs＠winehq.org 31 Dec '14

31 Dec '14

http://bugs.winehq.org/show_bug.cgi?id=32405 Bug #: 32405 Summary: Children of the Nile (& Demo): mouse buggy Product: Wine Version: 1.5.19 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: rtpublic1(a)gmail.com Classification: Unclassified When the game (version 1.3.0.1) or the demo (http://immortalcities.com/cotn/downloads/demo.php) reaches the main menu, no mouse cursor is visible. When running without emulating a virtual desktop, the buttons on the main menu show no reaction even when moving the (invisible) mouse onto them and clicking. When running with a virtual desktop that is the same size as the the main menu (1024x768), the buttons react to clicking on them, but wrongly: they act as if the mouse had only been moved onto them (showing a tooltip) instead of doing what they should (e.g open the settings menu). When running in a larger virtual desktop (e.g. 1440x900), the situation is like with the 1024x768 virtual desktop, except that, when moving the mouse off of the main menu to the right, so that it is between the main menu and the right edge of the virtual desktop, the game recognizes the mouse as being on one of the buttons on the right edge of the main menu, if the y-coordinates match, and reacts correctly to clicks. Tested with in a new wine prefix with no dll overrides. Please ask for more information if needed. -- 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.

1 10

[Bug 32410] New: Circuitmaker 2000 schematic hangs when editing text strings
by wine-bugs＠winehq.org 31 Dec '14

31 Dec '14

http://bugs.winehq.org/show_bug.cgi?id=32410 Bug #: 32410 Summary: Circuitmaker 2000 schematic hangs when editing text strings Product: Wine Version: 1.5.18 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: brodo(a)o2.pl Classification: Unclassified Circuitmaker 2000 (schematic section) hangs while editing text strings. Regression test gives this: bash-4.2$ git bisect bad 841214ddb4d4dc620e6b51dfe6655b585d423edc is the first bad commit commit 841214ddb4d4dc620e6b51dfe6655b585d423edc Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Nov 21 19:20:27 2012 +0100 user32: Don't check for driver events before normal messages in PeekMessage. :040000 040000 79793f282ab4ee789b1f07d7e8dd89c82e4e02ab 504f597e5c86ae4e9ae21713e8a8bb27969f0d5a M dlls -- 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.

1 4

[Bug 32444] New: Incorrect graphic rendendering when using Circuit Wizard
by wine-bugs＠winehq.org 31 Dec '14

31 Dec '14

http://bugs.winehq.org/show_bug.cgi?id=32444 Bug #: 32444 Summary: Incorrect graphic rendendering when using Circuit Wizard Product: Wine Version: 1.4.1 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mcmurchy1917-wine(a)yahoo.co.uk Classification: Unclassified Created attachment 42803 --> http://bugs.winehq.org/attachment.cgi?id=42803 Illustrates complete circuit in wine 1.3.34 and 1.5.19 I've been using Circuit Wizard for some time. It's been perfect up to an including 1.3.34. However, all subsequent versions since 1.3.35 have had incorrect screen rendering. For example the symbol for a resistor is only showing one wire connector whereas it should be showing two, one at each end of the resistor. It works perfectly on 1.3.9, 1.3.22, 1.3.29, 1.3.33 and 1.3.34, screen shot attached for version 1.3.34 but not on 1.3.35, 1.3.37, 1.4.1, 1.5.18 and 1.5.19, screen shot attached for version 1.5.19 However, even though the circuit looks incomplete it still works and it prints perfectly on all versions. To recreate the problem - Log on to your account and start a terminal change to you home directory cd Secure a copy and remove any current wine configuration mv .wine .wine.$(date +"%Y%m%d-%H%M%S") Apply for a copy of the free trial Professional edition demo here - http://www.new-wave-concepts.com/demo.html Download the trial Professional edition demo from your mail box to your home directory Install it wine cw11d_pr.exe where cw11d_pr.exe is the executable Professional edition demo Start the demo as you would any other wine application by navigating through your desktop start menu. Once the application has started - click on the gallery tab click on the passive components link. Note there are a number of “resistor” symbols all of which have connectors either top and bottom or left and right. Select the standard resistor and drag to the main window. Until such time as the mouse button is released the resistor has connectors top and bottom. When the mouse button is released to finally place the resistor in the circuit the bottom connector disappears. Irrespective of the above to prove that functionality is retained - Close and restart Circuit Wizard click on Sample Circuits click on Basic Circuits click on Capacitor Charging Click on the Circuit Diagram tab, bottom left. And note the circuit appears not joined up. Click the Run button on the tool bar to see the circuit charging the capacitor Click the switch on the circuit to see the capacitor discharge. Iain -- 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.

1 4

[Bug 32537] New: unimplemented function cfgmgr32.dll.CM_Reenumerate_DevNode, aborting
by wine-bugs＠winehq.org 31 Dec '14

31 Dec '14

http://bugs.winehq.org/show_bug.cgi?id=32537 Bug #: 32537 Summary: unimplemented function cfgmgr32.dll.CM_Reenumerate_DevNode, aborting Product: Wine Version: 1.4.1 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: goonstk(a)yahoo.com Classification: Unclassified Created attachment 42934 --> http://bugs.winehq.org/attachment.cgi?id=42934 Log after installing under Wine 1.4.1 Failed installing driver for MediaLink USB300N using CD. Log attached. Failed at wine: Call from 0x7b83bce2 to unimplemented function cfgmgr32.dll.CM_Reenumerate_DevNode, aborting Install zip can be found here under MWN-USB300N: http://medialinkproducts.com/support.php -- 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.

1 7

[Bug 32585] New: Post Apocalyptic Mayhem crashes on start
by wine-bugs＠winehq.org 31 Dec '14

31 Dec '14

http://bugs.winehq.org/show_bug.cgi?id=32585 Bug #: 32585 Summary: Post Apocalyptic Mayhem crashes on start Product: Wine Version: 1.5.20 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Classification: Unclassified Created attachment 42997 --> http://bugs.winehq.org/attachment.cgi?id=42997 terminal output This might be a fishy one, and I couldn't decide what component would be appropriate but I think it's somehow related to wined3d. The fact is that P.A.M (Steam) crashes immediately on startup with a backtrace as shown in the attachment. I found these workarounds: - either native d3dx9_36 or native d3dcompiler_43 works around the crash on startup (but d3dx9_42 must be set built-in) - native d3dxof also works around the crash (everything else is built-in) The strange is that neither +d3dxof nor +d3dx,+d3dcompiler channels produce *any* output before the game crashes. I should add that even if the game is able to run using those workarounds, it is very unstable. It tends to crash when - loading a new track - on exit (this seems to happen if blur effect was enabled) After these crashes I frequently receive backtraces that indicate heap corruption and wined3d is involved too. Reducing detail level, disabling audio don't help. No demo has been released. Let me know if you need further logs/tests. Fedora 17 x86 Nvidia 250 / driver 304.64 X.Org X Server 1.12.4 -- 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.

1 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs January 2013