May 2019 - Wine-bugs - list.winehq.org

[Bug 17743] New: Undocked toolbars are displayed incorrectly
by wine-bugs＠winehq.org 24 Feb '25

24 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=17743 Summary: Undocked toolbars are displayed incorrectly Product: Wine Version: 1.0.1 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Created an attachment (id=19959) --> (http://bugs.winehq.org/attachment.cgi?id=19959) Text toolbar I'm using Wine 1.1.17 (compiled from source using gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) ) on Fedora 10 i386. The problem is with undocked toolbars which are incorrectly displayed. The problem is also with dragging them. They should be also draggable when I click and hold mouse pointer over title of the toolbar. Problem exists in AutoCAD 2008 and AutoCAD Mechanical 2008. I attached image that shows the problem. All cuttings were done with unchecked option "Allow the window manager to decorate the windows". Last cutting was done in MS Windows XP running AutoCAD 2007. The problem exists also in Wine 1.0.1 -- 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 18

[Bug 36781] New: palringo: The Chat Box view not txt !!
by wine-bugs＠winehq.org 23 Feb '25

23 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=36781 Bug ID: 36781 Summary: palringo: The Chat Box view not txt !! Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ahmedsaber20005(a)gmail.com Created attachment 48850 --> http://bugs.winehq.org/attachment.cgi?id=48850 Log of palringo crash when i want to chat with someone the palringo not show any text :/ and some times it is crash -- 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 4

[Bug 11336] New: typing an open parenthesis "(" in vba causes an error
by wine-bugs＠winehq.org 23 Feb '25

23 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=11336 Summary: typing an open parenthesis "(" in vba causes an error Product: Wine Version: 0.9.54. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ead1234(a)hotmail.com Created an attachment (id=10442) --> (http://bugs.winehq.org/attachment.cgi?id=10442) picture of the error When programming in VBA under excel the application throws up an error when I try to enter the open parenthesis -- 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 21

[Bug 33211] New: C&C: Red Alert 2 still runs very slowly and mouse cursor flickers
by wine-bugs＠winehq.org 22 Feb '25

22 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=33211 Bug #: 33211 Summary: C&C: Red Alert 2 still runs very slowly and mouse cursor flickers Product: Wine Version: 1.5.25 Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: brymaster(a)gmail.com Classification: Unclassified The game runs slowly, especially while moving the cursor in-game. I've tried various winetricks configs with: ddr=opengl/ddr=gdi, rtlm=readtex, orm=backbuffer as well as setting a flag in ra2.ini for [Video]VideoBackBuffer=no - nothing works. Even looked at a 'lag fix' here that does nothing: http://www.stuffhost.de/files/cnc/CnCPatcher.html >From looking at past related issues (http://bugs.winehq.org/show_bug.cgi?id=2784, http://bugs.winehq.org/show_bug.cgi?id=5526, http://bugs.winehq.org/show_bug.cgi?id=14438) I get the feeling that someone was trigger happy and 'CLOSED FIXED' these without actually testing - people are still reporting its a problem. -- 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 27

[Bug 40738] New: Notepad open file dialog does not remember its location
by wine-bugs＠winehq.org 22 Feb '25

22 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=40738 Bug ID: 40738 Summary: Notepad open file dialog does not remember its location Product: Wine Version: 1.9.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gur.stavi(a)gmail.com Distribution: --- Reproduced in notepad when using File->Open... dialog. In Windows if dragging the open file dialog to a new location, on the next time it is opened it will be opened at the same location. In Wine it is always opened at the top left corner of the application. This is quite inconvenient on a big screen with maximized app. Note that when resizing the dialog, wine does remember the size on the next open so hopefully the position could be a slight extension to this. Regards, Gur -- 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 3

[Bug 39474] New: MSWT Kart 2004 does not work
by wine-bugs＠winehq.org 21 Feb '25

21 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=39474 Bug ID: 39474 Summary: MSWT Kart 2004 does not work Product: Wine Version: 1.7.53 Hardware: x86-64 URL: http://www.gamershell.com/download_5628.shtml OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 00cpxxx(a)gmail.com Distribution: Debian Download and install the game, after the intro videos the game will crash while loading bitmaps. The crash happens shortly after a BMP image is loaded. This is a continuation of bug 21012. -- 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 15

[Bug 39057] New: Support for Indexed Vertex Blending
by wine-bugs＠winehq.org 21 Feb '25

21 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=39057 Bug ID: 39057 Summary: Support for Indexed Vertex Blending Product: Wine Version: 1.7.47 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: swswine(a)gmail.com Distribution: --- Created attachment 52025 --> https://bugs.winehq.org/attachment.cgi?id=52025 Patch to implement indexed vertex blending support Vertex blending support has been added recently (https://bugs.winehq.org/show_bug.cgi?id=6955 was closed). But indexed vertex blending is not supported yet. I've implemented rather straightforward patch to do it which works for me, it is attached. Though I am far not familiar with wined3d development and not quite sure that my patch is complete and does not have any caveats. A potential caveat with this patch is the following. Besides using indexes in vertex shaders, a big enough number of supported vertex blend matrices is required to really support this Direct3D feature. It was 4 in 1.7.47, I changed to 128 using the same framework developed in 1.7.47. It may potentially fail on some graphic cards due to large number of uniforms in vertex shader generated. Besides the transfer of those uniforms may probably be optimized not to call glUniformMatrix for every matrix when only one or few has changed. -- 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 133

[Bug 46206] New: Altium Designer 17 account sign in fails as of 3.19
by wine-bugs＠winehq.org 21 Feb '25

21 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=46206 Bug ID: 46206 Summary: Altium Designer 17 account sign in fails as of 3.19 Product: Wine Version: 3.19 Hardware: x86-64 URL: https://s3.amazonaws.com/altium-release-manager/Altium _Designer_17/OfflineSetup_Altium_Designer_Public_17_1_ 9.zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jhansonxi(a)gmail.com Distribution: Ubuntu Account sign-ins are broken in Altium Designer 17.1.9 (and probably other releases) as of Wine 3.19. Steps to reproduce: 1. Launch Altium Designer. 2. Close floating window (Storage, etc.) which will likely trigger an error (probably bug #39765 which I'll verify later) 3. At MyAccount/License Management page click "Sign in" link 4. At "Account Sign In" dialog (which can get stuck behind main window) enter anything for user name and password, check the "I have read and understand the warning" privacy invasion checkbox, then the "Sign in" button. Expected behavior: Dialog box closes then reappears a moment later when sign-in fails. Wine 3.19-3.21 behavior: Dialog closes then an "Out of memory" error dialog is displayed. Installation: 1. Download the offline installer from the URL (3.6GB). Extract to subdirectory. 2. winetricks -q corefonts dotnet461 mdac28 win7 I used winetricks 20180815-next. Verified NET Runtimes with netfx_setupverifier-20180517.exe. Manually triggered GAC rebuild via ngen.exe since winetricks didn't seem to do so and it cluttered up the logs when it randomly started on its own. 3. Run the Altium installer. To save time deselect the optional items. Other: There's a nuisance rundll32.exe error at start-up reporting "This application could not be started". It doesn't seem to be related to this bug although I haven't found the cause of it yet. -- 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 14

[Bug 24308] New: Fullscreen fails for MechWarrior 4 games (Only one D3D device per DirectDraw object)
by wine-bugs＠winehq.org 21 Feb '25

21 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=24308 Summary: Fullscreen fails for MechWarrior 4 games (Only one D3D device per DirectDraw object) Product: Wine Version: 1.3.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: georg298(a)gmx.de For all MechWarrior 4 games, fullscreen fails with message fixme:ddraw:d3d7_CreateDevice Only one Direct3D device per DirectDraw object supported. Obviously, the game falls back to window'ed mode, as static HRESULT WINAPI d3d7_CreateDevice(IDirect3D7 *iface, REFCLSID riid, IDirectDrawSurface7 *surface, IDirect3DDevice7 **device) returns DDERR_INVALIDPARAMS changing this behaviour (returning D3D_OK instead): if (ddraw->d3ddevice) { FIXME("Only one Direct3D device per DirectDraw object supported.\n"); LeaveCriticalSection(&ddraw_cs); return D3D_OK; // return DDERR_INVALIDPARAMS; } makes fullscreen work for these games. Probably it's not "legal" to return D3D_OK in this case, but maybe there is a real solution for this problem? -- 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 26

[Bug 10522] New: endless WM_PAINT loop bug (update regions, queue paint count)
by wine-bugs＠winehq.org 17 Feb '25

17 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=10522 Summary: endless WM_PAINT loop bug (update regions, queue paint count) Product: Wine Version: CVS/GIT Platform: PC URL: http://www.microsoft.com/whdc/devtools/debugging/install x86.mspx OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-user AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Created an attachment (id=9265) --> (http://bugs.winehq.org/attachment.cgi?id=9265) trace with WINEDEBUG=+tid,+message,+win,+server Hello, I've seen this bug a while ago in other apps but ignored it because it was not easily to reproduce. Well until recently when I tested some stuff with windbg from "Debugging Tools for Windows" (Microsoft). I used debugging tools version 6.8.4.0 and recent GIT (wine-0.9.49-302-g58b85bb). Immediately when a child window was opened using toolbar (register, locals, .. whatever), windbg would become unresponsive, eating most CPU. Happens in both GUI modes - "floating/docking toolwindow" and "MDI emulation. Though "MDI emulation" is more obvious, it actually shows the endless refreshing (window caption). Attached is WINEDEBUG=+tid,+message,+win,+server log. Additionally I added a trace message which prints the current queue paint count (when incremented or fetched) which makes some things easier to spot. Printed as "inc_queue_paint_count: %d" and "get_message_paint_count: %d". The window hierarchy is as follows: --- snip --- *root*=0x10020 Shell_TrayWnd=0x10022 WinDbgFrameClass=0x10024 DockClass=0x10026 ToolbarWindow32=0x10028 msctls_statusbar32=0x1002a tooltips_class32=0x1002e WinBaseClass=0x10030 ToolbarWindow32=0x10032 SysListView32=0x10034 SysHeader32=0x10036 RichEdit20W=0x10038 --- snip --- After the child windows are created the queue paint count never drops to zero, resulting in endless WM_PAINT processing. Maybe some update (region) code path missed or flags problem? I played a bit with ignoring null region updates and it seemed to help a bit (preventing endless WM_PAINT loop) though other stuff wasn't drawn properly then. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 41