http://bugs.winehq.org/show_bug.cgi?id=421
------- Additional Comments From willie(a)froq.net 2006-06-11 14:43 -------
Your DIB-copy patch introduced a regression, or exposed a bug. I just tested
Reason 3.0, a pro-audio application by Propellerhead*. The colors of one part
of the interface are completely messed up with your patch applied - hard to
describe. One of the "devices" (MClass Mastering Suite Combi) used to be light
gray, now it's grainy blue/ red/ yellow. The bug seems to be similar to bug
#1973, which is also supposed to be fixable using a real DIB engine.
*) Demo available at: http://www.propellerheads.se
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=4924
------- Additional Comments From xerox_xerox2000(a)yahoo.co.uk 2006-06-11 13:36 -------
Tested with current git, there's quite some progress: it starts now without any
native dlls. However, if i try to connect , with username and password it fails
with a messagebox: OLE Error 0x80004001. Last lines in console:
fixme:shdocvw:ClOleCommandTarget_Exec
(0x1ae2b4)->({de4ba900-59ca-11cf-9592-444553540000} 2315 0 (nil) (nil))
fixme:shdocvw:ClOleCommandTarget_Exec (0x1ae2b4)->((null) 35 0 (nil) (nil))
fixme:shdocvw:ClOleCommandTarget_Exec (0x1ae2b4)->((null) 28 2 0x34eb10 (nil))
fixme:shdocvw:ClientSite_GetContainer (0x1ae2b4)->(0x34ea2c)
fixme:shdocvw:InPlaceFrame_SetStatusText (0x1ae2b4)->(0x6003b611)
fixme:shdocvw:ClOleCommandTarget_Exec (0x1ae2b4)->((null) 25 2 0x34e968 (nil))
fixme:shdocvw:ClOleCommandTarget_Exec (0x1ae2b4)->((null) 26 2 0x34e968 (nil))
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6301
xerox_xerox2000(a)yahoo.co.uk changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From xerox_xerox2000(a)yahoo.co.uk 2006-06-11 13:25 -------
ok, for now a'll resolve it as a WONTFIX. I have not yet seen a real app crash
on this.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3063
------- Additional Comments From zthg4821(a)gmail.com 2006-06-11 13:16 -------
Stéphane: I'm not sure if this is coincidence, but I applied the patch to Wine
0.9.24, fired up eMule and loaded it down, and it crashed 14 hours later with
~800 sockets (counted using the lsof method you described). As usual, a couple
of .met and .dat files were wiped during the crash (yes, this bug does cause
data loss).
For the record, in eMule I have TCP and UDP both enabled, and I'm using both
ED2K and Kad for transfers. Under "Options: Connection" I have "Max
sources/file: Hard limit" set to 500 and "Connection limits: Max connections"
set to 400.
I'm not up for trying the patch against Wine CVS head, so I'll wait for the next
Wine release and test eMule again.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6301
------- Additional Comments From julliard(a)winehq.com 2006-06-11 12:52 -------
There is no guarantee that you would get longdi~1 on Windows either, so I don't
think that's a bug. You can close it with wontfix instead of invalid if you
prefer, but either way unless there's a real app broken enough to depend on this
it's not something to worry about.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6616
------- Additional Comments From the3dfxdude(a)gmail.com 2006-06-11 12:35 -------
Please try again with latest wine git or 0.9.25. Another thing to do when you
get a lockup is attach winedbg to the process and get a backtrace. War3 should
not hang your entire system. You can also try disabling sound completely in
winecfg or in the game and see if it's reproducible. You can also check to see
if the game produces a crash dump in the Errors directory (relative to game
directory).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6609
xerox_xerox2000(a)yahoo.co.uk changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |http://codecpack.nl/klcodec2
| |72f.exe
Keywords| |download
------- Additional Comments From xerox_xerox2000(a)yahoo.co.uk 2006-06-11 12:31 -------
added downloadlink
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6616
Summary: Wine Hangs the System in Warcraft3, Battle.net (Only
There)
Product: Wine
Version: 0.9.22.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: test
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dahacks(a)gmail.com
(ubuntu 6.06, wine 0.9.22, Warcraft3:the Frozen Throne version 1.20e)
I have got this problem with wine hanging the whole system when im
playing warcraft3 in battle.net. I have tried reinstalling the game,
reinstalling wine, installing an older wine version and disabling the
sound emulators. No use - the system still hangs, but ONLY in warcraft
3 battle.net ranking games about 30 seconds after starting the game.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4487
------- Additional Comments From bryan.christ(a)gmail.com 2006-06-11 12:24 -------
Would it be possible to add some set affinity code to wine for this?
...something that could be used in winecfg on a per app basis?
Without a fix, this will continue to be an issue as the new breeds of CPUs are
all multi-core.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.