wine-bugs December 2016

wine-bugs@winehq.org

1 participants
7924 discussions

[Bug 39051] New: TabbedTextOut() incorrect output on tab character
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=39051 Bug ID: 39051 Summary: TabbedTextOut() incorrect output on tab character Product: Wine Version: 1.7.29 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: wine(a)goabq.org Distribution: --- Created attachment 52021 --> https://bugs.winehq.org/attachment.cgi?id=52021 testcase (tto.exe) and files to build it Tab characters do not output correctly when they are output one at a time. This is much worse using a memory device context than a screen device context. Attached is a testcase. It outputs text to a window using 2 different methods. Clicking in the client area toggles the method. When iterating over each character, TabbedTextOut() produces apparently garbage from the previous line instead of filling the rectangle appropriately as windows does. When drawing the line in a single call, the behavior is as expected. Spaces do not suffer from this problem (illustrated also by the testcase). -- 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 19

[Bug 35504] New: LibreOffice installation creates two wrong files
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=35504 Bug ID: 35504 Summary: LibreOffice installation creates two wrong files Product: Wine Version: 1.7.10 Hardware: x86 URL: http://sourceforge.net/projects/libreoffice.mirror/fil es/LibreOffice%204.2.0/LibreOffice_4.2.0_Win_x86.msi/d ownload OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: t.artem(a)mailcity.com Classification: Unclassified After installing LibreOffice_4.2.0_Win_x86.msi in Wine two illicit files can be found: C:\Win\System\msvcp100.dll C:\Win\System\msvcr100.dll $ sha1sum LibreOffice_4.2.0_Win_x86.msi 0c306a717aff4499b0abe2d2e3caaa63c62dfa0a LibreOffice_4.2.0_Win_x86.msi -- 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 15

[Bug 40303] New: Control Data passed in DIALOGEX Resource passes pointer with offset sizeof(WORD)
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=40303 Bug ID: 40303 Summary: Control Data passed in DIALOGEX Resource passes pointer with offset sizeof(WORD) Product: Wine Version: 1.9.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: vendor2013(a)herdsoft.com Distribution: --- Created attachment 53942 --> https://bugs.winehq.org/attachment.cgi?id=53942 Sourcecode for a test program When DIALOGEX Resources contain Custom data like in: DEFPUSHBUTTON "OK", IDOK, 148, 6, 50, 14 { 1, 2, 3, 4, 5 } The pointer passed in WM_CREATE is two bytes higher than in windows. In Windows (Tested with Vista an Windows 7 64-Bit) it Points to the Number of Words, in Wine it points to the first data byte. Microsoft Specs for this stuff are here: https://msdn.microsoft.com/de-de/library/windows/desktop/ms645389%28v=vs.85… Attached file dialogtest.zip is sourcecode for a test program with a simple custom control that displays the passed control data. Bug is in Version 1.6.2 (Debian Jessie) and 1.9.5 (Last Download). My suggestion for a patch: --- wine-1.6.2.orig/dlls/user32/dialog.c +++ wine-1.6.2/dlls/user32/dialog.c @@ -234,7 +234,8 @@ static const WORD *DIALOG_GetControl32( TRACE("\n"); TRACE(" END\n" ); } - info->data = p + 1; + info->data = p; p += GET_WORD(p) / sizeof(WORD); } else info->data = NULL; -- 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 41356] New: The Crew(Uplay) won't launch[STAGING]
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=41356 Bug ID: 41356 Summary: The Crew(Uplay) won't launch[STAGING] Product: Wine Version: 1.9.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: spleefer90(a)gmail.com Distribution: --- Created attachment 55708 --> https://bugs.winehq.org/attachment.cgi?id=55708 launching the game Using wine STAGING Absolutely no idea what's the problem. Running the game just stays at the uplay game loading screen 64 bit 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.

1 36

[Bug 40264] New: Iris Online cannot connect to login server
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=40264 Bug ID: 40264 Summary: Iris Online cannot connect to login server Product: Wine Version: 1.9.4 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: noscrubs.net(a)gmail.com Created attachment 53881 --> https://bugs.winehq.org/attachment.cgi?id=53881 Winsock trace from Linux and Mac OS X versions of wine. The game client cannot connect to the login server to authenticate the account. This works perfectly when running under the same version of Wine under Linux, and of course Windows. I have attached a short winsock trace that shows the differences when running under Linux and Mac OS X versions of Wine. I am also including a snippet of the client source relating to this log. The game client can be downloaded from http://noscrubs.net/downloads/NoScrubs_Iris_Online_Nov_2015.zip The launcher/patcher works fine apart from some HTML display issues. AppDB page: https://appdb.winehq.org/objectManager.php?sClass=version&iId=33421&iTestin… -- 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 17

[Bug 20104] New: Fujiprint/Fotokasten albums cannot be created due to missing richtext query interface
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=20104 Summary: Fujiprint/Fotokasten albums cannot be created due to missing richtext query interface Product: Wine Version: 1.1.29 Platform: PC URL: http://www.fotokasten.de/index.php?ftkPage=static&ftkV iew=ftksoftware OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: richedit AssignedTo: wine-bugs(a)winehq.org ReportedBy: cweiske(a)cweiske.de Running the "fotokasten" photo album creation software fails to create certain photo books with the following error: > fixme:richedit:fnTextSrv_QueryInterface Unknown interface: > {01c25500-4268-11d1-883a-3c8b00c10000} > fixme:richedit:fnTextSrv_OnTxInplaceDeactivate 0x3a1e8e0: STUB How to reproduce: 1. Run software 2. Click on tab "Fotobücher" 3. Click on "Fotobücher" icon 4. Click on "Fun" 5. Click on "Fun A4" 6. A loading window appears but is hidden soon after. When using Fotobücher->Fotobücher->Soft->A4, the richtext window has not to be shown, and I get to the next window (meaning it works without richtext). -- 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 9

[Bug 10913] New: start.exe doesn't support optional process title argument
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=10913 Summary: start.exe doesn't support optional process title argument Product: Wine Version: CVS/GIT Platform: Other URL: http://jedit.org OS/Version: other Status: NEW Keywords: download Severity: normal Priority: P2 Component: wine-programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Running real Java apps under the latest Sun win32 JRE on Wine seems like a fine stress test, even though in many cases users should run with the Linux JRE instead. The Sun JRE and jEdit install ok, but jedit has many startup problems. Here's the first one. Invoking it with the batch file provided by jEdit fails. Here's what's in the batch file: start "jEdit startup" "c:\windows\system32\javaw.exe" -Xms64M -Xmx192M -jar "C:\Program Files\jEdit\jedit.jar" -reuseview %* And here's what happens when you run it: $ cd ~/.wine/drive_c/Program Files/jEdit $ ~/wine-git/wine cmd /c jedit.bat fixme:exec:SHELL_execute flags ignored: 0x00000500 trace:process:CreateProcessW app (null) cmdline L"jEdit startup c:\\windows\\system32\\javaw.exe -Xms64M -Xmx192M -jar \"C:\\Program Files\\jEdit\\jedit.jar\" -reuseview" trace:process:find_exe_file looking for L"jEdit" trace:process:find_exe_file Trying native exe L"c:\\windows\\system32\\jEdit.exe" ... trace:process:find_exe_file Trying built-in exe L"c:\\windows\\system32\\jEdit startup.exe" ... trace:process:find_exe_file looking for L"jEdit startup c:\\windows\\system32\\javaw.exe -Xms64M -Xmx192M -jar \"C:\\Program Files\\jEdit\\jedit.jar\" -reuseview" Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found So it seems that start takes an optional process title argument. Sure enough, http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en… documents it. Who knew? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 20

[Bug 31644] New: glMapBufferRange is extremely slow while playing Resident Evil 5 ( happens only on nvidia binary driver )
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=31644 Bug #: 31644 Summary: glMapBufferRange is extremely slow while playing Resident Evil 5 ( happens only on nvidia binary driver ) Product: Wine Version: 1.5.12 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: tizbac2(a)gmail.com Classification: Unclassified Calls to glMapBufferRange are extremely slow on nvidia drivers with resident evil 5, if this should be reported to nvidia instead just close it over 90% of frame time is taken by glMapBufferRange -- 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 20

[Bug 38488] New: Wrong taces in functions *_invalidate_location
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=38488 Bug ID: 38488 Summary: Wrong taces in functions *_invalidate_location Product: Wine Version: 1.7.41 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Distribution: --- I got a plenty of messages like fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. It rises because the function wined3d_volume_invalidate_location() is used with reversed parameter For example dlls/wined3d/device.c: wined3d_volume_invalidate_location(dst_volume, ~WINED3D_LOCATION_TEXTURE_RGB); The function assumed location and not ~location. ----- void wined3d_volume_invalidate_location(struct wined3d_volume *volume, DWORD location) { TRACE("Volume %p, clearing %s.\n", volume, wined3d_debug_location(location)); volume->locations &= ~location; TRACE("new location flags are %s.\n", wined3d_debug_location(volume->locations)); } ----- Here wined3d_debug_location() will message like above. Same about wined3d_resource_invalidate_location(struct wined3d_resource *resource, DWORD location) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 18496] New: BREW simulator always shows a black display
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=18496 Summary: BREW simulator always shows a black display Product: Wine Version: 1.1.21 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jon.dufresne(a)gmail.com Tested with wine-1.1.21 I am attempting to use the Qualcomm BREW simulator under wine. After installing, I attempted to run the example applets. The application launches and I am able to select an applet directory, but the simulated device's screen always shows black and not the usual list of icons that represent available applets. The BREW simulator installer is found here: https://brewx.qualcomm.com/bws/content/gi/products/sdk/3.1/en/3.1.5.179/ins… Steps to reproduce: 1. Download and install BREW SDK simulator 2. Run simulator 3. Use menu to selec "File->Change Applet Dir..." 4. Navigate to c:/Program Files/BREW 3.1.5/sdk/examples/ 5. Hit "OK" 6. Notice screen is black Expected results: Under windows, the BREW simulator will show a listing of the available BREW applets (one for each *.mif file in the directory chosen). This list appears as a series of icons inside the device's display area. -- 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 17

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 December 2016