[Bug 1617932] Re: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension

2017-02-02 Thread Brian Murray
** Also affects: xorg-server-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: xorg-server-lts-xenial (Ubuntu Trusty) Importance: Undecided Status: New ** Changed

[Bug 1617932] Re: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension

2017-01-10 Thread Chris Halse Rogers
Hello Daniel, or anyone else affected, Accepted xorg-server-lts-xenial into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server-lts-xenial/2:1.18.4-0ubuntu0.2~trusty1 in a few hours, and then in the -proposed repository. Please help

[Bug 1617932] Re: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension

2016-10-05 Thread Launchpad Bug Tracker
This bug was fixed in the package xorg-server - 2:1.18.4-0ubuntu0.1 --- xorg-server (2:1.18.4-0ubuntu0.1) xenial; urgency=medium * New upstream bugfix release. (LP: #1619142) * randr-adjust-masters-last-set-time.diff, randr-do-not-check-the-screen-size.diff: Fix issues

[Bug 1617932] Re: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension

2016-09-16 Thread Christopher Townsend
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617932 Title: Xmir with glamor is spending 11% of its CPU time in

[Bug 1617932] Re: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension

2016-09-14 Thread Daniel van Vugt
I don't think we need to verify this one. Maybe just jump to verification-done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617932 Title: Xmir with glamor is spending 11% of its CPU time in

[Bug 1617932] Re: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension

2016-09-14 Thread Andy Whitcroft
Hello Daniel, or anyone else affected, Accepted xorg-server into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Bug 1617932] Re: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension

2016-09-07 Thread Launchpad Bug Tracker
This bug was fixed in the package xorg-server - 2:1.18.4-1ubuntu6 --- xorg-server (2:1.18.4-1ubuntu6) yakkety; urgency=medium * debian/patches/xmir.patch: - Don't call epoxy every frame (LP: #1617932) - Ignore 'unknown 11 event' (LP: #1617925) - Improve root window

[Bug 1617932] Re: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension

2016-08-31 Thread Daniel van Vugt
** Changed in: xorg-server (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617932 Title: Xmir with glamor is spending 11% of its CPU

[Bug 1617932] Re: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension

2016-08-29 Thread Daniel van Vugt
https://git.launchpad.net/~xmir-team/xorg- server/+git/xmir/commit/?id=2d3665870945c0dc363cc09abedf10121d51d43b ** Changed in: xorg-server (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1617932] Re: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension

2016-08-29 Thread Daniel van Vugt
And the docs say: bool epoxy_has_gl_extension() returns whether a GL extension is available (GL_ARB_texture_buffer_object, for example). Note that this is not terribly fast, so keep it out of your hot paths, ok? https://github.com/anholt/libepoxy -- You received this bug notification because