http://bugs.winehq.org/show_bug.cgi?id=35823
Bug ID: 35823
Summary: Widl should check for duplicated uuids when generating
typelib
Product: Wine
Version: 1.7.14
Hardware: x86
OS: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: bunglehead(a)gmail.com
Duplicated uuids in a typelib will cause troubles with typeinfo lookup. Midl
refuses to generated such typelibs, but it looks like it might have a more
strict constraint - uuid should be unique in a file, and we don't want it to be
that strict (see bug 27718).
--
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=31232
Bug #: 31232
Summary: The Way Things Work 2.0 installer froze after finished
copying files
Product: Wine
Version: 1.1.21
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: Nachanon_Vetjasit(a)hotmail.com
Classification: Unclassified
Regression SHA1: 54d7c8012d1d7369a56779955ced5a09e448a1cd
When started The Way Things Work 2.0 installer (setup.exe),
the setup proceeds normally, through the welcome screen,
quicktime installer prompt (though QuickTime 16bit 2.1.1 installation didn't
work [bug #18260]),
installation options (express/custom), files copying progress window.
But as soon as the file copying window disappeared, the installer froze, no
screen repainting, no message from WINE's console.
(Normally this stage should be creating program groups and ends at the 'Setup
Complete' window)
54d7c8012d1d7369a56779955ced5a09e448a1cd is first bad commit
commit 54d7c8012d1d7369a56779955ced5a09e448a1cd
Author: Dmitry Timoshkov <dmitry(a)codeweavers.com>
Date: Wed Apr 29 15:17:35 2009 +0900
explorer: Initialize the Progman DDE interface when starting explorer.
:040000 040000 4a347655bb6f41b8b8377d8e3e3e25c1551d1730
05513d15b76a99fe5033c4422a82008667425088 M programs
With WINE before this commit, the installation would continue, with WINE's
Program Manager (progman)
popped up with a dialog from the setup program: "Unable to start DDE
communication with Program Manager." [Abort/Retry/Ignore]
If clicked 'Ignore' (aka. continue despite the error), this step will be
repeated for another five time, each time leaving one Program Manager window
opened (6 window total at the end).
And finished with 'Setup Complete' window.
Note:
The Way Things Work is a 16-bit application, and supports Windows 3.1.
Tested using WINE's Windows version 98.
WINE: wine-1.1.21 source distribution
System: Debian GNU/Linux 5.0 "Lenny" i386 (Intel Pentium 4 2.66GHz)
--
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.
http://bugs.winehq.org/show_bug.cgi?id=36871
Bug ID: 36871
Summary: Chronology with native .NET is postage stamp sized
Product: Wine
Version: 1.7.21
Hardware: x86
URL: http://store.steampowered.com/app/269330/
OS: Linux
Status: NEW
Keywords: dotnet
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
This is with 'winetricks dotnet20' in a 32-bit prefix.
Chronology appears to run OK, except that it creates a large black window with
a tiny image in the upper-left corner. Maybe it's the title screen? It's too
small to be sure.
--
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=36648
Bug ID: 36648
Summary: Alt+F4 key function error
Product: Wine
Version: 1.7.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: szilipeter(a)freemail.hu
1. settings winecfg:
-- Graphics: Emulate a virtual desktop (UNCHECK)
When I run a program, for example "winecfg", and
- Select "Drives"
- Select "Add"
- press "Alt-F4"
This time : Close "Select Drive Letter" window, and focused the "Wine
configuration" windows.
When I setting 2. version:
-- Graphics: Emulate a virtual desktop (CHECK)
When I run a program, for example "winecfg", and
- Select "Drives"
- Select "Add"
- press "Alt-F4"
This time : Close the "winecfg" application. Why ?
--
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=8067
--- Comment #22 from Austin English <austinenglish(a)gmail.com> ---
This is your friendly reminder that there has been no bug activity for over a
year. Is this still an issue in current (1.7.51 or newer) wine?
--
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=35813
Bug ID: 35813
Summary: SolidWorks 2013: Crash at the beginning
Product: Wine
Version: 1.7.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lukasz.wojnilowicz(a)gmail.com
Created attachment 47811
--> http://bugs.winehq.org/attachment.cgi?id=47811
Crash window
Steps to reproduce:
1) remove ~/.wine
2) winetricks vcrun2010 dotnet40
3) install SolidWorks 2013
4) wine SLDWORKS.exe
Behaviour:
Crash (See attachment)
Expected behaviour:
No crash.
Additional info:
1) Window from attachment is "sldexitapp.exe"
2) "sldProcMon.exe" started by "SLDWORKS.exe" takes all CPU resources
--
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=35752
Bug ID: 35752
Summary: Autodesk Inventor LT: Setup crashes after winetricks
dotnet35sp1 dotnet40
Product: Wine
Version: 1.7.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lukasz.wojnilowicz(a)gmail.com
Created attachment 47744
--> http://bugs.winehq.org/attachment.cgi?id=47744
Crash window
Steps to reproduce:
1) remove ~/.wine
2) winetricks dotnet35sp1 dotnet40
3) wine Setup.exe
4) wait in initializing window
Behaviour:
Crash window (see attachment)
Expected behaviour:
No crash window.
Additional information:
There is no crash if I do not do step
"2) winetricks dotnet35sp1 dotnet40"
but these components are required to subsequent Inventor installation.
If I do only
"winetricks dotnet40"
then there is no crash too.
WINETRICKS_VERSION=20140302
--
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=37169
Bug ID: 37169
Summary: Powerdirector 11 Ultra: Run as Administrator
Product: Wine
Version: 1.7.25
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mewtwo2643(a)yahoo.com
Created attachment 49403
--> https://bugs.winehq.org/attachment.cgi?id=49403
Output from Wine on the terminal
To get this issue:
Create new prefix, install Windows Media Player 9 (winetricks wmp9), run the
AutoRun.exe found on the disc, install it, and run it. After clicking on the
button to enter the full editor, it starts to load but then a window pops up
complaining it doesn't have administrator access and it quits afterwards.
I couldn't find a trial because powerdirector 12 is out now. This torrent might
work though:
https://kickass.to/cyberlink-powerdirector-11-ultra-11-0-0-3026-multilingua…
You also might be able to try using the Powerdirector 12 trial. The steps
should be the similar for 11 (tell me if they don't):
http://download.cnet.com/CyberLink-PowerDirector/3000-13631_4-10483012.html
The important thing is that Windows Media Player 9 is installed.
--
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=37133
Bug ID: 37133
Summary: Clang Static Analyzer: Null path
Product: Wine
Version: 1.7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lukebenes(a)hotmail.com
Clang Static Analyzer identifies Null path
File: dlls/crypt32/rootstore.c
Location: line 413, column 10
Description: Null pointer passed as an argument to a 'nonnull' parameter
static BOOL import_certs_from_path(LPCSTR path,
HCERTSTORE store, BOOL allow_dir)
{
...
fd = open(path, O_RDONLY);
//Clang: Null pointer passed as
//an argument to a 'nonnull' parameter
...
}
To understand why Clang suspects that NULL may get here, let's examine the
fragment where this function is called:
static BOOL import_certs_from_dir(LPCSTR path, HCERTSTORE store)
{
...
char *filebuf = NULL;
//Clang: 'filebuf' initialized to a null pointer value
struct dirent *entry;
while ((entry = readdir(dir)))
{
...
size_t name_len = strlen(entry->d_name);
//Calling function to change filebuf
if (!check_buffer_resize(&filebuf, &bufsize,
path_len + 1 + name_len + 1))
{
ERR(...);
break;
}
snprintf(filebuf, bufsize, "%s/%s", path, entry->d_name);
if (import_certs_from_path(filebuf, store, FALSE) && !ret)
//Clang: Passing null pointer value via 1st parameter 'path'
//Clang: Calling 'import_certs_from_path'
ret = TRUE;
...
}
}
In this code, the check_buffer_resize function is called where either the value
of the filebuf variable must change or FALSE must be returned; but the function
may fail to change filebuf and return TRUE instead. Take a look at the
function's code below:
static BOOL check_buffer_resize(char **ptr_buf,
size_t *buf_size, size_t check_size)
{
if (check_size > *buf_size)
{
...
*ptr_buf = CryptMemAlloc(*buf_size);
...
}
return TRUE;
}
The function contains only one condition where the ptr_buf variable is changed,
and if this condition is false, the true return result will allow you to use
this variable further on.
A similar issue is with the memcpy() function:
File: server/directory.c
Location: line 548, column 21
Description: Null pointer passed as an argument to a 'nonnull' parameter
--
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.