FS#29895 - [cairo] Slow gtk apps after cairo upgrade

Attached to Project: Arch Linux
Opened by Mefistofeles (mefistofeles) - Tuesday, 15 May 2012, 05:10 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 20 May 2012, 08:14 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After upgrading awesome and replacing cairo-xcb with cairo (seems to have xcb enabled by default now) I noticed that my gtk apps (firefox, chromium, lilyterm, etc) are very slow.

Additional info:
* Cairo version 1.12.2-1
* Tried recompiling cairo package from ABS with --disable-xcb option and it didn't work (same issue).
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Sunday, 20 May 2012, 08:14 GMT
Reason for closing:  Upstream
Comment by Andreas Radke (AndyRTR) - Tuesday, 15 May 2012, 13:08 GMT
NVidia closed driver? Search for existing known upstream bugs.
Comment by Luciano A. Ferrer (luuuciano) - Tuesday, 15 May 2012, 16:34 GMT
Im using intel video, same problem, cairo downgraded, problem solved...

00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)

I noticed the slowness on xchat (when switching to it you can see the window drawing it, like a vertical blind up down...). Im using kde...
Comment by Andreas Radke (AndyRTR) - Tuesday, 15 May 2012, 17:56 GMT
Check for existing upstream cairo bugs or file a new one and report the URL here.
Comment by Mefistofeles (mefistofeles) - Tuesday, 15 May 2012, 20:31 GMT
I'm using nvidia closed driver indeed. Gonna check for known upstream bugs.
Comment by Mefistofeles (mefistofeles) - Wednesday, 16 May 2012, 06:12 GMT
I'm using nvidia closed driver indeed. Gonna check for known upstream bugs.
Comment by Andreas Radke (AndyRTR) - Sunday, 20 May 2012, 08:14 GMT
https://bugs.freedesktop.org/show_bug.cgi?id=48395 - should be solved with a future nvidia update.

Loading...