UXA is only applicable for the -intel driver. -ati only supports
XAA and EXA.
Yes, EXA is now the default for -ati starting with Jaunty.
Pardon for your discomfort; I simply have been completely focused on
intel problems the last couple months. With over 1800 X bugs it is hard
to give
** Description changed:
Binary package hint: wine
After upgrading to Jaunty, I experienced the ia32libs problems reported
earlier due to the missing libuuid. This showed up in wine as well as
other programs. The ia32libs problem has now been addressed, but wine
still behaves
Further checking: comparing Intrepid and Jaunty on same machine -
both using radeon OS drivers, most recent versions in each case;
Intrepid - specifying either XAA or EXA in Device section of xorg.conf
(or leaving no option specified) gives normal behavior in the specific
situation I described -
I believe I have found the problem. The empty xorg.conf results in my
case in the video driver (radeon) trying to use exa acceleration, not
uxa, which I believe is the new default. Adding the Option AccelMethod
XAA line to the device section removes the problem. I haven't tried
explicitly
Nope - setting Option AccelMethod UXA results in the driver
defaulting to EXA. It seems I shall have to continue to specify XAA
acceleration..
--
wine screen updates faulty in Jaunty
https://bugs.launchpad.net/bugs/314205
You received this bug notification because you are a member of Ubuntu
Marking as invalid in compiz:
- see #237209 in wine for the desktop effects / wine issue
- follow this bug in xserver-xorg-video-ati for the probable driver issue
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
wine screen updates faulty in Jaunty
Thanks Julien; there doesn't seem to have been any progress on #237209,
does there? I have confirmed that the problem is not related to compiz
itself; it happens with metacity set to use compositing. So there is a
problem with the Composite extension, that shows itself in Wine for some
reason on
Very disappointed to see no response! I have upgraded to the Wine
1.1.19 beta, but no change in this unacceptable behavior. Jaunty is up
to date, now in beta; Wine is the latest available version, and the
problem persists. It is NOT a problem with compiz, as it occurs with
metacity/compositing as
Hello Stephen,
You may not know it, but we switched to X.org server 1.6 in Jaunty,
which may have, as a result, an increase of instability for the GPUs.
This issue is, imho, nonely related to Wine, and you're likely to run
into same trouble with any OpenGL game, because Compiz + openGL have
Sorry I couldn't figure this one out sooner Stephen, but unfortunately I
believe Steve is right that this is a binary driver bug.
** Also affects: xserver-xorg-driver-ati (Ubuntu)
Importance: Undecided
Status: New
** Package changed: xserver-xorg-driver-ati (Ubuntu) = xserver-xorg-
You could both be right - should I file another bug against xserver-xorg
1.6 itself?
I don't play many games - mostly the standard gnome set, which don't
show any problems for me. The only one I use Wine for is spider
solitaire. From what you say, this might be a problem with the composite
Hello,
You might want to try OpenArena / ET:QW / Nexuiz in order to see if you
have a big FPS difference between Intrepid and Jaunty, this may help to
confirm the problem.
--
wine screen updates faulty in Jaunty
https://bugs.launchpad.net/bugs/314205
You received this bug notification because
That would not work for me - I don't want my machine to play violent
shooting games. I want it to run regular everyday apps without showing
video artefacts and crashing. If OpenGL is only useful for fast-action
games it doesn't bother me whether it works or not; but please would
developers not try
Please attach your Xorg.0.log, and the output of 'lspci -vvnn'. If
you've made any customizations to your xorg.conf, attach that as well.
One point of confusion we need cleared up: This bug is filed against
the open source -ati driver, but some comments are referring to the
proprietary driver
Hello Bryce,
I'm the one who referred to proprietary drivers but I was probably
wrong, i really can't recognise ATi prop/free drivers' names, I
apologize for that.
Cordially, SD.
--
wine screen updates faulty in Jaunty
https://bugs.launchpad.net/bugs/314205
You received this bug notification
On Sat, Apr 11, 2009 at 09:42:49PM -, Steve Dodier wrote:
Hello Bryce,
I'm the one who referred to proprietary drivers but I was probably
wrong, i really can't recognise ATi prop/free drivers' names, I
apologize for that.
No prob, once you attach your Xorg.0.log that should tell. Also,
I am using the opensource drivers - have been exclusively since early
testing Intrepid, AFAIK. The current Jaunty install was upgraded from
Intrepid last week, after beta release, and updated daily since.
Here is lspci -vvnn, and Xorg.0.log as an attachment:
s...@sc-laptop:~$ lspci -vvnn
00:00.0
I checked, but could only find fglrx-modaliases; I've removed that to be
quite sure. The dpkg -l '*fglrx*' call gave a list including the xorg-
driver-fglrx and fglrx-driver, but they don't appear to be installed (no
version #,flagged pn and un respectively. apt-get remove fglrx* didn't
find them.
Further information:
I get the same errors in screen re-drawing in Wine even with compiz
disabled, i.e. using the Normal setting in Visual Effects tab of the
Appearance Preferences. This suggests to me that the errors occur with
any window manager that tries to use compositing, including
metacity --replace wine foo.
--
wine screen updates faulty in Jaunty
https://bugs.launchpad.net/bugs/314205
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
That looks as if it switches window manager to metacity - thus turning
off compiz.
If there is a general problem with Wine in jaunty, let's talk about it
and help to get it fixed.
If there is a general problem with compiz in Jaunty, ditto.
If the problem is some esoteric interaction between
Is anything happening? Wine and programs running under Wine in Jaunty
continue to behave strangely. Some of the strange behavior (progressive
failure of the Wine desktop window to update correctly, leaving blue
patches in place of card images in Spider, for instance) does appear to
be due to some
Compiz has always messed up Wine:
https://bugs.edge.launchpad.net/ubuntu/+source/wine/+bug/237209
** Also affects: compiz (Ubuntu)
Importance: Undecided
Status: New
--
wine screen updates faulty in Jaunty
https://bugs.launchpad.net/bugs/314205
You received this bug notification
Thanks, Scott. They play together just fine in Intrepid, at least on my
machine (same one as above).
I've tried turning off various effects, but haven't found a sub-set that
restores Wine to normality in Jaunty. Now that Compiz seems to be on
by default it would be good if Wine was working
24 matches
Mail list logo
