http://bugs.winehq.org/show_bug.cgi?id=18390
Summary: Roblox can't join a game
Product: Wine
Version: 1.1.20
Platform: Other
URL: http://roblox.com
OS/Version: other
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
After working around bug 18388 and bug 18389,
trying to join a game fails; the browser says
it can't start the game, and tells you to start
the app (which you already did). On the console,
one sees a suspicious error message from gecko:
fixme:shdocvw:HttpNegotiate_BeginningTransaction (0x5c239a8)->(L"" L"" 0
0x33c794)
0[15c4c8]: file (null), line 0: uncaught exception: [Exception... "Unexpected
error" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame ::
http://www.roblox.com/ScriptResource.axd?d=lz2oPY8_Yxfc8W_Nr5tWGxJ8z2w_ENPF…
:: anonymous :: line 2144" data: no]
Possible workaround: launch games directly using e.g.
wine roblox.exe -play
http://www.roblox.com/Game/join.ashx?jobID=cc310936-d9bd-46a5-99cd-494d6b14…
as mentioned at http://forums.roblox4linux.co.cc/index.php?topic=37.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=20232
Summary: mciwave breaks on MSDN example
Product: Wine
Version: 1.1.30
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winmm&mci
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hoehle(a)users.sourceforge.net
I'm reviewing mciwave and mciseq and found numerous issues. Concurrently, I'm
augmenting the MCI testsuite. I've attached my current mciwave
work-in-progress tests to give you an early insight into my work.
The tests so far confirm my model of MCI: I view it like an old-fashioned tape
deck with buttons, which you can press in any order. Still there's error
checking, e.g. you can't resume when stopped. Like a tape deck, you can switch
from playing to recording at any time.
Oddly, you can combine fast forward and play in one command, but not rewind
with play.
The attached tests work fine on (at least one machine with) MS-Windows, but
cause Wine to fail and hang in multiple ways. You've been warned!
I'd be pleased if people could run the tests on more instances of MS-Windows.
I plan to strip down this test file until it at least does not hang anymore in
Wine. Then only can it be submitted. Concurrently, I can submit patches to
the mci* codebase.
Current issues with the mci code in Wine are:
- not distinguishing between STOPPING and STOPPED, PLAYING and GOING TO PLAY,
etc.;
- seriously broken asynchronous execution;
- non-error-proof use of InterlockDecrement. It must only be called
when waveInAddBuffer and waveOutWrite succeed, as those cause
callbacks to happen;
- RIFF .wav file not always correctly written;
- the mmio is as much as resource as the wave device and must be
properly released (mmioAscend, not only when saving);
- many items here and there:
+ bogus 44000Hz frequency;
+ premature return (in mcicda);
+ conversion between #bytes and samples;
+ switching fInput while playing;
+ copy&paste errors (InterlockedDecrement need be initialised
differently when recording and playing)
The major issue is concurrency. There I'm not sure how to proceed and rewrite
mciwave (and mciseq and mcicda).
o One model, Erlang-like, which the OSS driver also implements, is one thread
per play and exclusively using message passing to receive commands. This would
simplify NOTIFY everywhere. It clearly offers the advantage of being closest
to the sequential execution model that is easy to reason about. IMHO, it does
not play nicely with the pause command (state machine).
o Continue as currently written, but then think twice and even 3-7 times about
how to perform locking among the concurrent threads:
- Put InterlockIncrement() to more uses?
- Put Events to more uses?
- Unlike mciavi, there's no CriticalSection in mciwave and mcicda, yet
I'm unconvinced that the current synchronisation via volatile dwStatus
can suffice.
- But then, identifying the critical sections will be tedious and error prone.
o Combinations of both, e.g. one thread per play or record (not unlike the
present code), and dealing (correctly) with PAUSE, STOP and RESUME inside it
(via e.g. events to restart a paused thread, or indirectly, by relying on the
callbacks+events sent when invoking waveOutRestart and waveInStart -- is it
legal at all to call those from a different thread)?
o Is there any other concurrency model suitable in Wine?
Regards,
Jörg Höhle
--
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=14055
Summary: Occasional wine crash during Heroes of Might and Magic
III gameplay
Product: Wine
Version: 1.0.0
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: riklaunim(a)gmail.com
Created an attachment (id=14275)
--> (http://bugs.winehq.org/attachment.cgi?id=14275)
Crash log
During gameplay the game may sometimes crash. It looks like the bug is related
to mp3/sound – “mp3dec.asi” (using OOS in wine). The log shows the
backtrace.
--
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=15689
Summary: Onenote 2007: no drawing.
Product: Wine
Version: 1.1.6
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: ole
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: Crazedhamster(a)hotmail.com
Created an attachment (id=16752)
--> (http://bugs.winehq.org/attachment.cgi?id=16752)
Backtrace
Clicking on the drawing tool causes it to go grey and disappear.
--
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=12804
Summary: winecfg: pressing enter in library override closes
winecfg
Product: Wine
Version: 0.9.60
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
CC: jeffzaroyko(a)gmail.com
Pressing enter when entering a dll override doesn't add the override. For those
of us that find mice an exercise in masochism and prefer keyboards, it's quite
a pain...
--
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=20194
Summary: Far Cry 2: major graphical glitches
Product: Wine
Version: 1.1.30
Platform: PC-x86-64
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jeffz(a)jeffz.name
Created an attachment (id=23807)
--> (http://bugs.winehq.org/attachment.cgi?id=23807)
terminal output, first 5000 lines
The main menu loads, the level loading screen works fine. When starting a new
game, the screen is mostly black, part of the light from the sun is seen and
some other parts of the scenery creep into view for a moment here and there.
OpenGL renderer string: GeForce 8800 GTS/PCI/SSE2
OpenGL version string: 3.1.0 NVIDIA 190.18
--
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=26378
Summary: Can`t play a game
Product: Wine
Version: unspecified
Platform: All
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: danirtoma(a)gmail.com
J can`t play the game 4story.
--
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=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.