https://bugs.winehq.org/show_bug.cgi?id=40160
Bug ID: 40160
Summary: cant install mobogenie
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: madscientistkustomz(a)gmx.com
Distribution: ---
Created attachment 53662
--> https://bugs.winehq.org/attachment.cgi?id=53662
trace log
problem installing MOBOGENIE for ubuntu
--
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=38402
Bug ID: 38402
Summary: glDebugMessageCallback is broken
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: opengl
Assignee: wine-bugs(a)winehq.org
Reporter: chris.kcat(a)gmail.com
Distribution: ---
According to the KHR_debug extension spec, the function glDebugMessageCallback
takes a function pointer callback with the type:
typedef void (APIENTRY *GLDEBUGPROC)(GLenum source,
GLenum type,
GLuint id,
GLenum severity,
GLsizei length,
const GLchar* message,
const void* userParam);
https://www.opengl.org/registry/specs/KHR/debug.txt
In particular, it notes that the function callback uses the same calling
convention as the other GL functions. The problem is that on Windows, GL uses
the stdcall calling convention, while on Linux it uses cdecl. Wine's
glDebugMessageCallback thunk passes the callback through as-is, so the system's
libGL tries to call an stdcall function as though it was cdecl, causing it to
crash upon returning.
Another problem is that the spec says:
"When DEBUG_OUTPUT_SYNCHRONOUS is disabled, the driver is optionally allowed to
concurrently call the debug callback routine from potentially multiple threads,
including threads that the context that generated the message is not currently
bound to."
meaning the callback can be called on threads other than the one OpenGL is
being used on. This is a problem because it may be called on one or more
internal driver threads that were not created using the Windows API, and if the
callback function tries to do anything that relies on Windows-related thread
information, it won't be there.
--
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=41419
Bug ID: 41419
Summary: Visio 2013 crashes with unimplemented function
msvcp100.dll.?_GetCombinableSize@details@Concurrency@@
YAIXZ
Product: Wine
Version: 1.9.20
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
wine: Call from 0x7b43b53c to unimplemented function
msvcp100.dll.?_GetCombinableSize@details@Concurrency@@YAIXZ, aborting
--
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.
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=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.
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.