http://bugs.winehq.org/show_bug.cgi?id=29380
Bug #: 29380
Summary: sonic Generations: The detected configuration does not
match your current hardware
Product: Wine
Version: 1.3.35
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: eunbolt(a)gmail.com
Classification: Unclassified
Created attachment 38027
--> http://bugs.winehq.org/attachment.cgi?id=38027
Terminal output when starting Sonic Generations
First you Select what hardware you have in the sonic generations configuration
tool.
Then when you run sonic generations, it tells you "The detected configuration
does not match your current hardware"
--
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=29880
Bug #: 29880
Summary: Sonic Generations: no audio
Product: Wine
Version: 1.4-rc2
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: eunbolt(a)gmail.com
Classification: Unclassified
Created attachment 38852
--> http://bugs.winehq.org/attachment.cgi?id=38852
Terminal output while playing sonic generations
There is no sound when playing sonic generations
--
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=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=30170
Bug #: 30170
Summary: Afterburner 3D: screen not drawn properly (orm=fbo)
Product: Wine
Version: 1.4
Platform: x86
URL: http://digilander.iol.it/brodarodasoft2/AB3D_Setup.exe
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
Classification: Unclassified
Created attachment 39373
--> http://bugs.winehq.org/attachment.cgi?id=39373
terminal output (orm=fbo)
Now that bug #8433 has been fixed, the game can get past the initial loading
screen without crashing, but the screen is not refreshing after the loading
screen is displayed. You can hear audio playing and various text is displayed
(overwritten) on the loading screen.
At some point menu options appear at the bottom of the screen and you can start
a new game by pressing <Enter>. You can hear audio from the game but the screen
is still showing the corrupted loading screen.
Setting OffscreenRenderingMode to backbuffer acts as a workaround. One of the
drawbacks of this setting is that the opening screens showing the graphic card
and input setup are displayed upside down. Once the game begins to load, the
screen is displayed normally.
Performance is abysmal when you start a new game but I don't know if this is
due to the backbuffer setting.
Fedora 16
Nvidia 250 / driver 290.10
X.Org X Server 1.11.4
--
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=28770
Bug #: 28770
Summary: Diablo 2 - sound works in menu, stops after starting
game (kind of regression)
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: zajec5(a)gmail.com
Classification: Unclassified
I've noticed that with recent Wine I don't hear any sound in Diablo 2 when
playing my character. When I start Game.exe - sound is here during watching
into and as long as I'm in the menu. When I start playing (the map and my
character show up) it stops. After that I don't hear anything anymore.
Bisection has resulted in the following:
There are only 'skip'ped commits left to test.
The first bad commit could be any of:
901af51ea32f2d192a598808abab2d1b6a940773
be158e48ad8ee556941bd3f1ff94ca7116680d00
We cannot bisect more!
commit be158e48ad8ee556941bd3f1ff94ca7116680d00
Author: Andrew Eikum <aeikum(a)codeweavers.com>
Date: Mon Jul 11 08:28:30 2011 -0500
winmm: Implement waveOut* on top of MMDevAPI.
commit 901af51ea32f2d192a598808abab2d1b6a940773
Author: Andrew Eikum <aeikum(a)codeweavers.com>
Date: Mon Jul 11 08:28:24 2011 -0500
winmm: Remove driver implementation of waveOut*.
I'm using ALSA in Wine and Pulseaudio in my system.
I'm almost sure it's duplicate of #27908, but I was asked by Austin to create
new bugzilla report.
Right after starting Game.exe with affected Wine I get following fixmes:
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels,
pretending there's only 2 channels
fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels,
pretending there's only 2 channels
When starting real game (map and character, sounds goes away) nothing appears
in the console.
--
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.