http://bugs.winehq.org/show_bug.cgi?id=8796
--- Comment #26 from NSLW <lukasz.wojnilowicz(a)gmail.com> 2009-01-21 07:18:37 ---
Created an attachment (id=18866)
--> (http://bugs.winehq.org/attachment.cgi?id=18866)
Game hangs up (halting by Ctrl+c), there is an output (wine 1.1.13)
I'm using nvidia driver 180.22 and WINE 1.13 on Fedora 10 i386 and this game
still hangs up. I'm adding new log.
--
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=5552
--- Comment #16 from NSLW <lukasz.wojnilowicz(a)gmail.com> 2009-01-21 07:11:29 ---
Created an attachment (id=18865)
--> (http://bugs.winehq.org/attachment.cgi?id=18865)
Output from the 3DSetup program WINE 1.13
I'm using nvidia driver 180.22 and WINE 1.13 on Fedora 10 i386 and the bug is
still present.
--
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=17052
Summary: Star Wars Episode I Racer: swizzled attributes
regression
Product: Wine
Version: 1.1.13
Platform: PC
URL: http://downloads.pcworld.com/pub/new/fun_and_games/actio
n/racerdemo.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: plamen_h_x(a)yahoo.com
I track texture regression caused by commit
6791e6b752413a4d0e08e84fa565873b922cb1de
Look at screenshot for difference...
--
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=3254
--- Comment #48 from Dylan Smith <dylan.ah.smith(a)gmail.com> 2009-01-21 01:26:08 ---
It seems like the secur32 component is getting better, however, I believe
google talk is also affected a regression reported in Bug 16785. This is
causing an error dialog to show and google talk starts up, and then it would
exit.
Before this commit (8d28f09d8a582ff499b5947a5a2d1cf2700fb259) that caused the
regression it seemed like google talk would repetitively sign in, and get
disconnected (further than it got before). While this is happening the
following output would be repeated on the console.
GNUTLS ERROR: Function was interrupted.
GNUTLS ERROR: Decryption has failed.
err:secur32:schan_DecryptMessage Returning SEC_E_INTERNAL_ERROR
fixme:winhttp:WinHttpGetIEProxyConfigForCurrentUser returning no proxy used
fixme:secur32:schan_InitializeSecurityContextW Using hardcoded "NORMAL"
priority
--
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=6086
Vitaliy Margolen <vitaliy(a)kievinfo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
Component|directx-dinput |-unknown
--
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=17038
Summary: Broken link to Winelib guide on Winelib wiki page
Product: WineHQ.org
Version: unspecified
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jc.gervais(a)videotron.ca
The wikipage
http://wiki.winehq.org/Winelib
Contains a reference to the Winelib user guide in the Introduction paragraph
http://www.winehq.org/site/docs/winelib-guide/
which is a broken link
--
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=8854
--- Comment #31 from Reimar Döffinger <Reimar.Doeffinger(a)gmx.de> 2009-01-20 17:33:49 ---
Btw. I put my modified dinput.dll.so here:
http://natsuki.mplayerhq.hu/~reimar/dinput.dll.so
Replacing only that file of my Debian wine-installation worked for me, so it is
not necessary to compile all of wine yourself.
--
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=6086
--- Comment #68 from Pierre Willenbrock <pierre(a)pirsoft.de> 2009-01-20 15:45:35 ---
I think this has not been said clearly enough: For me(and Janosch), the hanging
cursor-problem gets better _when_ we use multiple cpu cores. It only manifests
itself in "cursor moves only every other minute" if wine is restricted to a
single cpu. Otherwise, one gets a jumpy, but otherwise working cursor. The
reason for this can be easily seen: the message thread gets more time to
actually handle messages.
I guess this happens: The kernel scheduler immediately schedules the drawing
thread after its WM_USER+1 message comes back from the message thread, and
completes so fast, that the next time the message thread runs and looks for
messages, there is another WM_USER+1 message asking for swap. This happens
inside the second nested GetMessage, and only the outer one processes
WM_MOUSEMOVEs, so there is not much that can be done from inside GetMessage.
--
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=6086
--- Comment #67 from H. Verbeet <hverbeet(a)gmail.com> 2009-01-20 15:34:11 ---
(In reply to comment #66)
> Wine claims to emulate Windows 95, and as such it should aim that each program
> (no matter how buggy) runs under Wine as good as under Windows 95.
>
We aim more at XP/Vista these days, actually. Regardless, this kind of problem
is hardly limited to applications originally written for Win95. There are
enough applications aimed at 2000 or XP that suffer from threading issues
simply because they were written before multicore machines were widespread. If
we wanted to do something about this in Wine, I'd say it would be more useful
to be able to set CPU affinity per application in winecfg, regardless of the
selected Windows version. I'm not convinced the existing Linux tools are
inadequate for this though.
--
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=6086
--- Comment #66 from Adrian Bunk <bunk(a)stusta.de> 2009-01-20 15:01:35 ---
(In reply to comment #65)
> I disagree on a technical basis that it should be Wine's job to deal with
> that(and thus essentially clone the functionality of taskset).
>
> Two points:
> 1) This is not a Wine-specific problem. There can be Linux apps that are broken
> in the same way too. As such Wine is the wrong place to deal with the problem
Wine claims to emulate Windows 95, and as such it should aim that each program
(no matter how buggy) runs under Wine as good as under Windows 95.
--
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.