Seems fixed here too. I'm running testing on a Quadro NVS 135M. I unhold
libcairo2:i386 1.10.2-7 -> 1.12.2-2 last week and I did not experienced the
reported problem since then.
pp
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
On Wed, Sep 12, 2012 at 6:58 AM, Alex Goebel wrote:
> Is this still an issue with radeon?
> For my nvidia system it disappeared several weeks ago with a nouveau update.
Seems fixed for us here too !
--
Julien Palard -
CTO - meltyNetwork
Mobile : +33 (0)6 21 19 49 10
Office : +33 (0)1 83 62 00
Is this still an issue with radeon?
For my nvidia system it disappeared several weeks ago with a nouveau update.
It's tagged RC, so we should be sure it's still a "grave" bug?!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contac
I'd also like to add that I have an Nvidia card which has the same
problem. I used the advice on the following post to downgrade to 1.10
and there is no more screen corruption, smudging or blurring.
http://forums.debian.net/viewtopic.php?f=7&t=79467
--
To UNSUBSCRIBE, email to debian-bugs-
Problem reproduced here with
* libcairo 1.12.2.1
* Nouveau driver
* Linux 3.2.0-2-amd64
Temporarily fixed using Option "NoAccel" "true".
--
Julien Palard -
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@l
Package: libcairo2:amd64
Followup-For: Bug #658252
FYI, this appears to be an upstream bug (or bugs):
"Current git: Xorg display corruption with radeon driver (bisected)"
... which appears to actually be a bug in somewhere in X:
"Graphics corruption and performance problems using recent Cairo"
h
Package: libcairo2
Followup-For: Bug #658252
I also can confirm that problem occurs in libcairo2 1.12.0-2, but after
downgrading libcairo2 and libcairo-gobject2 to 1.10.2-7 (I haven't tried
downgrading only libcairo2) problem disappears.
Also disabling graphics acceleration in X.org helps:
Option
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today I have been able to test this a little more.
I have tried building pidgin using the source from debian (apt-get
source pidgin) and the resulting build has exactly the same problem.
I have tried running pidgin as another user, under gnome instea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Sorry, this keeps changing. The rectangles are back, so I suppose this
is still a live issue. I haven't tried re-compiling pidgin yet since my
latest round of updates. Any advice would be useful. At the moment
some of the text is replaced with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now I've updated more packages and restarted (without changing pidgin or
building it again) and it is fully working, drawing all the text
properly even in the error dialogue that didn't work last time. Perhaps
it was a dependency problem? It does see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, I spoke too soon, my newly built pidgin's text is becoming
rectangles again after a reboot.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8uNXsACgkQA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
More information on this issue:
The issue became apparent after upgrading a number of packages with
libcairo2, including build-essential from 11.4 to 11.5.
I just tried downgrading build-essential back to 11.4, and rebuilt
pidgin from source, and the
Package: libcairo2
Version: 1.10.2-6.2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Recently I upgraded libcairo2 on my system, and found that pidgin (the program
I use most that uses libcairo2) was misbehaving. It rendered text incorrectly
and crashed often. I did s
13 matches
Mail list logo
