http://bugs.winehq.org/show_bug.cgi?id=22978
Summary: SimCity2000: race condition causes crash in MCI during
startup
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winmm&mci
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hoehle(a)users.sourceforge.net
Created an attachment (id=28457)
--> (http://bugs.winehq.org/attachment.cgi?id=28457)
mci+winmm trace & crash backtrace
The attached log shows a crash that is triggered because the asynchronous
mciseq/mcimidi player is still attempting to open the device while the main
thread already successfully called MCI_CLOSE.
The mcimidi player does not implement proper locking. Unlike mciwave, its state
variable is not yet set to MCI_MODE_PLAY when opening the MIDI device, which
lets MCI_CLOSE not see something is busy playing.
Actually, even looking at mciwave, one can construct unfortunate sequences of
scheduling that would cause mciwave to hang in such a situation. So there's no
trivial patch simply moving
wmm->dwStatus = MCI_MODE_PLAY;
a couple of lines up.
The crash generally occurs when starting SimCity 2000 using
"wine 'C:\Program...\Game\simcity.exe'"
Curiously, "wine start simcity.exe" always works. As I said, it's a race
condition.
It seems like sometimes, the initialisation of WINMM and MIDI takes a long
time.
The bug is then triggered when MCI_CLOSE is called by the application.
MCI_CLOSE is called, among others, when clicking "exit" in the initial menu.
Often enough, the app crashes before showing this menu. IMHO, the fact that the
app calls MCI_CLOSE that early is triggered by another bug in Wine that AppDB
testers have mentioned every now and often, but never put to Bugzilla: SimCity
2000 starts fine (showing its logo) when using full screen mode, but needs a
resize or uniconify when using a virtual desktop: then presumably, the app
sends MCI_CLOSE to stop the music, causing or not a crash via the present race
condition.
BTW, since the crash occurs in the asynchronous MCI MIDI player, the app
nevertheless works...
This issue has nothing to do with the bug, presumably in the app, that "wine
simcity.exe" crashes whereas "wine 'c:\full\path\simcity.exe'" (should) work.
--
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=9848
Summary: flipviewer fails to load
Product: Wine
Version: 0.9.46.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: wine-advapi32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: eyecreate(a)gmail.com
Created an attachment (id=8321)
--> (http://bugs.winehq.org/attachment.cgi?id=8321)
Error log for flipviewer
The flipviewer(www.flipviewer.com) app installs and the library program works,
but the actual program fails. Backtrace log attached.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=28186
Summary: uninstaller has no proper usage message
Product: Wine
Version: 1.3.26
Platform: x86
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fgouget(a)codeweavers.com
First uninstaller uses WINE_ERR() to tell the user he got the usage wrong (like
when he forgets a parameter). That's wrong as this is not a Wine error.
Second it never prints a usage message thus leaving the user guessing.
Finally if run in the wineconsole the user will see no output at all but that's
a somewhat independent issue (see bug 28185).
--
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=14915
Summary: FlushFileBuffers() fails on disk volume, sets
ERROR_INVALID_HANDLE when handle supposedly valid
Product: Wine
Version: 1.1.2
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: vesselinpeev(a)hotmail.com
Ran under Wine, the following program receives ERROR_INVALID_HANDLE as a
Windows last error when the flushing call fails.
Note that if you are testing under Windows Vista, you need to run the program
with administrative privileges to be able to get the handle to the volume.
For brevity, I've omitted GetLastError() printing for failure cases except the
flushing one, but, needless to say, you may want to add them for full
correctness / error handling / safety, or do let me know and I'll happily add
these and re-post the code.
# include <windows.h>
# include <stdio.h>
# include <tchar.h>
int _tmain()
{
LPCTSTR volName = _T("\\\\.\\C:");
HANDLE hFile = CreateFile(volName, GENERIC_READ | GENERIC_WRITE,
FILE_SHARE_READ | FILE_SHARE_WRITE, 0,
OPEN_EXISTING, 0, 0);
if (hFile != INVALID_HANDLE_VALUE) {
_tprintf(_T("Opened volume %s\n"), volName);
SetLastError(0xdeadbeef); /* to make sure that it's really the next call
that sets the last error -- advice taken from Dmitry Timoshkov's comment at
http://bugs.winehq.org/show_bug.cgi?id=14855 */
if (FlushFileBuffers(hFile)) {
_tprintf(_T("File buffers flushed\n"));
}
else {
DWORD dwRet = GetLastError();
_ftprintf(stderr, _T("File buffers not flushed, GetLastError() returned
%lu"), dwRet);
if(dwRet == ERROR_INVALID_HANDLE) {
_ftprintf(stderr, _T(" (\"The handle is invalid\")"));
}
_ftprintf(stderr, ".\n");
}
}
else {
_ftprintf(stderr, _T("Could not open volume %s\n"), volName);
return -2;
}
if(! CloseHandle(hFile)) {
_ftprintf(stderr, _T("Could not close handle to volume %s\n"), volName);
return -3;
}
return 0;
}
--
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=19425
Summary: notepad: running notepad with a non-existent file and
choosing yes to create a new file should do so
immediately (appinstall)
Product: Wine
Version: 1.1.26
Platform: PC
OS/Version: Linux
Status: NEW
Keywords: download, source
Severity: trivial
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
'notepad foobar.txt'
pops up a dialog telling you that the file does not exist, and asking if you'd
like to create it.
Yes - Opens notepad with foobar.txt, but doesn't create a new file.
No - Opens notepad with a blank new document.
Cancel - Closes notepad.
On windows, choosing yes immediately creates the new (empty) file.
--
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=26688
Summary: Risen requires vcrun2005
Product: Wine
Version: 1.3.17
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: xvachon(a)gmail.com
The game outputs no missing functions and mscodescan reveals nothing either,
yet the game complains about vcrun2005. winetricks vcrun2005 works around it
xavier@xavier /wine/risen/drive_c/jeu/bin $ wine Risen.exe
fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.VC80.OpenMP" (8.0.50727.762)
fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.VC80.CRT" (8.0.50727.762)
err:module:import_dll Library vcomp.dll (which is needed by
L"C:\\jeu\\bin\\Engine.dll") not found
err:module:import_dll Library Engine.dll (which is needed by
L"C:\\jeu\\bin\\Risen.exe") not found
err:module:import_dll Loading library Engine.dll (which is needed by
L"C:\\jeu\\bin\\Game.dll") failed (error c0000018).
fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.VC80.CRT" (8.0.50727.762)
err:module:import_dll Library Game.dll (which is needed by
L"C:\\jeu\\bin\\Risen.exe") not found
err:module:import_dll Loading library Engine.dll (which is needed by
L"C:\\jeu\\bin\\Importer.dll") failed (error c0000018).
err:module:import_dll Loading library Game.dll (which is needed by
L"C:\\jeu\\bin\\Importer.dll") failed (error c0000018).
err:module:import_dll Library vcomp.dll (which is needed by
L"C:\\jeu\\bin\\Importer.dll") not found
err:module:import_dll Library Importer.dll (which is needed by
L"C:\\jeu\\bin\\Risen.exe") not found
err:module:LdrInitializeThunk Main exe initialization for
L"C:\\jeu\\bin\\Risen.exe" failed, status c0000135
--
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=17055
Summary: wine does not put wine executable path into desktop icon
Product: Wine
Version: 1.1.13
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: beagle7(a)shaw.ca
when installing an app, when wine installs a desktop icon (under KDE), it does
include the proper env WINEPREFIX, but it does not include the path to to wine
(e.g., /usr/local/1113/bin/wine) under which the app was installed. I.e., if I
do exactly this:
env WINEPREFIX=~/.wine-some-app /usr/local/wine-install-dir/wine
~/path/windows-app-installer.exe
the resulting desktop icon, in properties, would have under command, the
following:
env WINEPREFIX="~/.wine-app" wine "C:\Program Files\Path\app.exe"
or similar.
What I'd like it to have is:
env WINEPREFIX="~/.wine-app" /usr/local/wine-install-dir/wine "C:\Program
Files\Path\app.exe" (as appropriate)
--
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=27482
Summary: Tomb Raider III demo crashes in the launcher
Product: Wine
Version: 1.3.22
Platform: x86
URL: http://www.tombraiderchronicles.com/cgi-bin/dl03/dl.pl
?dm_tombraider3complete
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
Created an attachment (id=35145)
--> (http://bugs.winehq.org/attachment.cgi?id=35145)
terminal output
To reproduce the problem:
1) Install the demo as usual.
2) The launcher requires ie6 (winetricks ie6). Start the demo by tomb3.exe.
Click on <Start Free Trial button> ...a crash happens here.
The launcher started correctly in 1.3.21:
f3ae1b99f637c7a22546a7528edb0f9df2d57678 is the first bad commit
commit f3ae1b99f637c7a22546a7528edb0f9df2d57678
Author: Ričardas Barkauskas <rbarkauskas(a)codeweavers.com>
Date: Thu Jun 9 18:29:36 2011 +0300
ddraw: Separate IDirectDrawSurface vtable.
:040000 040000 375fc8c1597978349b5e1f9f8b418c6d5fa0a539
839c77ec396a4be43237f36c110c257a0db09131 M dlls
The patch can be reverted cleanly on wine-1.3.22-78-g4b2bfb4 and that fixed the
crash.
I couldn't add the author to the CC list.
Fedora 15
Nvidia GeForce 250 / driver 270.41.19
--
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=12454
Summary: iriver plus 3 doesn't start
Product: Wine
Version: 0.9.58.
Platform: PC
URL: http://www.iriver.com/plus/
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hewus.owns(a)gmail.com
iriver plus 3 installs, but does not start. I added mfc42u.dll to get rid of
missing dll messages, but it now ends here (0.9.59):
err:module:attach_process_dlls "iDeviceM.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program
Files\\iriver\\iriver plus 3\\iPlus3.exe" failed, status c0000142
I tried yesterday on 0.9.58 and got this:
err:module:LdrInitializeThunk "iDeviceM.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program
Files\\iriver\\iriver plus 3\\iPlus3.exe" failed, status c0000142
The errors are slightly different, if that helps at all. I am able to provide
more debugging if required.
Free download:
http://www.iriver.com.au/iriver/uploads/software/iplus3_setup_full.zip
--
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=23650
Summary: PowerPoint 2007 insensitive to changes in screen
resolution
Product: Wine
Version: 1.2-rc6
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: m.duelli(a)web.de
For presentations, you usually have to change your screen to the right
resolution such that the external monitor / projector can display your slides.
However, I found that when you start PowerPoint 2007 using wine 1.2rc7 or more
specifically the wine server before adopting the screen resolution, then
PowerPoint or at least parts of it will stick to the former screen resolution.
Steps to reproduce:
1. Start your computer with a certain screen resolution, say 1280x1024
2. Start up PowerPoint 2007 with wine.
(Everything is fine, presentation mode works as expected)
3. Change screen resolution
4. Activate presentation mode
-> The presentation will be rendered to fit in the old screen resolution and
there is no way to change this.
Possibly this also affects other applications.
--
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.