http://bugs.winehq.org/show_bug.cgi?id=2666
Warday <warday27(a)hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |warday27(a)hotmail.com
--- Comment #39 from Warday <warday27(a)hotmail.com> 2011-03-18 13:40:30 CDT ---
Well I could fix it a litle using
$sudo apt-get install msttcorefonts
$sudo fc-cache -fv
What change? Well in games in stead of been all the time black it blinks black
and wite.
Sory if I expres my self bad Im an spanish speaker.
--
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=4066
Warday <warday27(a)hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |warday27(a)hotmail.com
--- Comment #32 from Warday <warday27(a)hotmail.com> 2011-03-18 13:38:34 CDT ---
Well I could fix it a litle using
$sudo apt-get install msttcorefonts
$sudo fc-cache -fv
What change? Well in games in stead of been all the time black it blinks black
and wite.
Sory if I expres my self bad Im an spanish speaker.
--
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=3930
--- Comment #41 from Jörg Höhle <hoehle(a)users.sourceforge.net> 2011-03-18 12:13:31 CDT ---
I repeated the GetCurrentThreadId() callback test from comment #37 as testbot
jobs 9892 and 9891.
There's an incredibly simple explanation of the behaviour observed since w2k
that does not require QueueUserAPC() or other delayed procedure calls (DP): let
the application thread execute the player!
Obviously then, callbacks invoked synchronously will be executed in the app's
thread, which is the test result for systems since w2k.
Execution in the app's thread is not unknown to Wine, e.g. MCI_PLAY does that
with the MCI_WAIT flag in mciwave and mciseq.
>From a system reliability perspective, hijacking the app's thread is a sensible
move on the side of MS, as by killing the one thread (or process) you remove
everything it does, hence the rest of the system can continue to work
unaffected.
>From a compatibility POV, this is a bad move.
If since w2k calls like midiStreamRestart() and midiStreamOut() are not
asynchronous messages to a concurrently running player and instead drive the
player loop on the calling thread (= the application one's), then I can imagine
a whole class of programs that worked on w9x but hang on newer systems -- e.g.
Heroes, says comment #18.
Not all programs would hang though, those designed around message dispatching
delivered to the app's message queue have a good chance of working with
recursive invocations of Wait/Peek/DispatchMessageA() by a winmm player
executing in the application's thread.
As far as Wine is concerned, I'd favour the w9x behaviour: have the multimedia
players sit in their own thread, even though a proper design causes me
headaches with concurrency and locking issues.
Under this perspective, it looks like an error when player loops that execute
synchronously in the app's thread (like all MCI players, e.g. MCIAVI) never
drain and DispatchMessageA() the app's message queue -- the app may dead-lock
when expected callbacks are not invoked. Is this perhaps an explanation to the
bugs listed in bug #21060, comment #2?
--
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=7640
--- Comment #62 from MacNean <dardack(a)gmail.com> 2011-03-18 08:09:36 CDT ---
(In reply to comment #61)
> So could you please tell me, what is the latest patch for wine1.3.15, and where
> i can get it. Or another, if you just upgraded, maybe you have a deb with patch
> in it, and can upload it somewhere?
Here's the diff file:
http://www.2shared.com/document/r5_Fn4fd/HWCursor-Wine12rc1diff.html
To patch wine, download the source, extract it, enter the directory where you
extracted it to:
patch -p1 < /path/to/HWCursor-Wine1.2rc1.diff.txt
./configure
make
I won't do a PPA since my wine has Wine-pulse compiled into it.
--
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=26453
Summary: Europa Universalis III: Divine Wind - freezes while
using in-game main menu
Product: Wine
Version: 1.3.15
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: danielmicay(a)gmail.com
Created an attachment (id=33684)
--> (http://bugs.winehq.org/attachment.cgi?id=33684)
console output
EU3 will occasionally lock-up while using the main menu, for example to save
the game. It will almost always freeze after using the menu to save the game.
This issue doesn't occur on Windows and it didn't occur before the Divine Wind
expansion (EU3 Complete + HTTT).
note: I'm using the Steam version of the game (in-game overlay is disabled).
note2: there were 17000 identical lines of
fixme:quartz:DSoundRender_SendSampleData Sample dropped 2906455712 of 4608
bytes
fixme:quartz:Parser_OutputPin_QueryInterface No interface for
{56a868a5-0ad4-11ce-b03a-0020af0ba770}!
so I trimmed them from the log, everything else is untouched.
--
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=26460
Summary: Dragon Age: Origins crashes in pulseaudio on startup
sometimes
Product: Wine
Version: 1.3.15
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
On an i7 running Ubuntu 10.10, about every second run, I get
mmap() failed: Cannot allocate memory
Assertion 'b' failed at pulsecore/memblock.c:451, function
pa_memblock_acquire(). Aborting.
and the app terminates very quickly.
Running the app under taskset 1 seems to prevent the problem.
--
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=26289
Summary: Perfectworld Internation Crashes on Entering the Game
Product: Wine
Version: 1.3.14
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: eli(a)orbsky.homelinux.org
Created an attachment (id=33516)
--> (http://bugs.winehq.org/attachment.cgi?id=33516)
This is the output of elementclient.exe from the time its started to the time
it crashes
Perfectworld has just updated their game called Perfectworld with an expansion
called Genesis (not as silly as it sounds - they have other games).
I've been playing the game without problems for the last couple of years.
However, after this most recent update I am experiencing a great many problems.
The short of it is that after I login and try to enter the game, the game
crashes. The output is included in the attachement.
I hope that we can work together to fix the issues that are making trouble,
because after 2 really fun years with the game, it would be a real shame to
have to stop playing it.
*****************************************
OBSERVATIONS WHILE TRYING TO RUN THE GAME
*****************************************
The game client is called elementclient.exe and symptoms when running under kde
4.6 and gnome are quite different. I've tested this with and without
compositing.
I'm using Fedora 14 with wine 1.3.14
The visible symptoms are as follows.
**** LOADING SCREEN *************
WITH KDE:
---------
The loading screen comes up and as the progress bar progresses the screen
flickers after some delay the login sequence begin
WITH GNOME:
-----------
The loading screen comes up and things seems to progress smoothly and with no
delay the login sequence begins
******** LOGIN ********
The login sequence begins with an animated sequence which can be escaped out of
to login.
WITH KDE
--------
The animation starts fine but then before getting to the login screen the
program will freeze for a bit. Sometimes the login screen appears. Sometimes it
does not
WITH GNOME
----------
The animation starts and continues smoothly until the login sequence begins
****** CHARACTER SELECTION ******
WITH KDE
--------
After quite a long delay the character selection screen comes up, usually the
background is completely black. Sometimes the graphics comes up. Sometimes the
screen completely freezes. Sometimes the elements that allow me to select
characters and enter the game appears. If successful, then the Entering the
Game sequence begins.
WITH GNOME
----------
The character selection screen comes up smoohly and I am able to select which
character I would like to enter the game with. I am then able to start the
Entering the Game sequence.
*********** Entering the Game ***********
WITH KDE
--------
Again.... Sometimes I get the Entering the Game Screen. Sometimes the game
freezes at this point. If the client sucessfully begins to enter the game, then
the screen with progress bar flickers. and then the game crashes.
WITH GNOME
----------
The client goes to the Entering the Game Screen. The screen's animation seems
to work smoothly and then, probably, as the client transits into the game, the
client crashes.
I hope we can get is fixed.
--
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=7640
--- Comment #61 from Alexander <zah_al(a)rambler.ru> 2011-03-18 00:12:50 CDT ---
So could you please tell me, what is the latest patch for wine1.3.15, and where
i can get it. Or another, if you just upgraded, maybe you have a deb with patch
in it, and can upload it somewhere?
--
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=23163
Summary: World of Warcraft Crashes in Dalaran with "mmap()
failed: Cannot allocate memory"
Product: Wine
Version: 1.2-rc2
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wintrust
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jeremydyoung(a)sbcglobal.net
Created an attachment (id=28809)
--> (http://bugs.winehq.org/attachment.cgi?id=28809)
Stack trace from crash.
This has been happening on OpenSuSE 11.2 with 2GB RAM or 4GB RAM. It's almost
always a crash in Dalaran, though sometimes it crashes in raids or flying to
other zones.
Stack information in attachment.
--
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=7640
--- Comment #60 from MacNean <dardack(a)gmail.com> 2011-03-17 07:52:02 CDT ---
(In reply to comment #59)
> Is there an easy solution, insteat of patching source wine, and build it? It's
> not hard, but as I understand, next update wine, will kill it patch.
You have to patch each Wine that you use. I just upgraded from 1.3.1 to
1.3.15, you don't have to upgrade each wine release, especially if the wine you
have is working great for what you use it for.
The problem is a software mouse. In windows it's probably a HW mouse cause of
DirectX, (or the software mouse behaves better because of directX, i'm not
really sure). The reason I know it's a software mouse, is cause if you compile
my patch into wine you generally see 2 mouse pointers. Your themed pointer and
the games pointer that lags behind the themed pointer.
Basically the patch gives you a Faux HW mouse. What I can do is add code that
looks for different mouse pointers, and for each game you could put a cursor
you like just rename it to what I say, and it would use that mouse pointer,
instead of the default Left Pointer.
But again you don't have to update wine if everything is working.
--
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.