https://bugs.winehq.org/show_bug.cgi?id=44229
Bug ID: 44229
Summary: Visual C++ 1.51 can't add files to project
(GetOpenFileName16() doesn't support custom templates
or hooks)
Product: Wine
Version: 3.0-rc3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: comdlg32
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Regression SHA1: 424472c20d8059057277ae13a0ffe5c51a818e52
Distribution: ---
The Project -> Edit menu is missing the "Files in Project" box as well as the
Add / Add All / Delete buttons. This is because we don't support custom
templates or hooks anymore:
0031:fixme:commdlg:GetOpenFileName16 custom templates no longer supported,
using default
0031:fixme:commdlg:GetOpenFileName16 custom hook 0x16670010 no longer supported
While hooks would probably be simple enough to implement, templates will be
much more difficult and will probably require significant duplication of code
from user.exe16:dialog.c. Is there a reason to implement commdlg on top of
comdlg32 besides avoiding duplication?
--
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=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.
https://bugs.winehq.org/show_bug.cgi?id=45320
Bug ID: 45320
Summary: cmd creates an environment variable with an empty name
Product: Wine
Version: 3.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: dima(a)gmail.com
Distribution: ---
CMD creates an environment variable with an empty name when it starts up. That
doesn't match the behavior on Windows (at least, Win10) and breaks programs
like Python.
Apparently, CMD is trying to save the current working directory; the code was
added in
https://source.winehq.org/git/wine.git/commit/d0db751e0cb7a0526c3aecca48918…,
but without an explanation.
To reproduce, run this:
#include <stdio.h>
int main(int argc, char **argv, char **envp) {
for (char **env = envp; *env != 0; env++) {
printf("%s\n", *env);
}
return 0;
}
The last line of the output will be similar to this:
=Z:=Z:\home\dima
Python gets an exception if it tries to unset that variable:
>>> import os
>>> os.environ.clear()
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "C:\ProgramData\Miniconda3\lib\_collections_abc.py", line 820, in clear
self.popitem()
File "C:\ProgramData\Miniconda3\lib\_collections_abc.py", line 813, in
popitem
del self[key]
File "C:\ProgramData\Miniconda3\lib\os.py", line 680, in __delitem__
self.unsetenv(encodedkey)
File "C:\ProgramData\Miniconda3\lib\os.py", line 718, in <lambda>
_unsetenv = lambda key: _putenv(key, "")
OSError: [Errno 0] Error
This is arguably a Python bug, and it happens on UNIX, too:
https://bugs.python.org/issue20658 . However, cmd should probably match the
Windows behavior and not trigger the Python bug unnecessarily.
--
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.
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.
https://bugs.winehq.org/show_bug.cgi?id=44177
Bug ID: 44177
Summary: Guitar Pro 5: Long freezes during draw process of
dashed lines (P.M. or let ring markers)
Product: Wine
Version: 3.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kitsunyan(a)inbox.ru
Distribution: ArchLinux
Created attachment 59941
--> https://bugs.winehq.org/attachment.cgi?id=59941
log
Guitar Pro 5 always hangs when tries to draw dashed lines (like these
https://imgur.com/GgvrEuq.png). The longer the line, the longer the freeze. CPU
core is loaded to 100% during this freeze. Sometimes it even draws odd lines
(https://imgur.com/1efGsF2.png).
This bug is regression. About 6 months ago everything was fine. It begins ~4
months ago. I don't know what causes this problem so I started wine with
WINEDEBUG=+all and tried to find where it hangs. I noticed a lot of gdi calls
which can cause this hangs. I restarted wine with WINEDEBUG=+gdi and grabbed
the log which I've attached to the bug.
I'm using Arch Linux. WINEARCH=win32.
--
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=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.
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.
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.