[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2020-01-28 Thread Timo Aaltonen
** Changed in: libxpresent (Ubuntu Disco) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxpresent in Ubuntu. https://bugs.launchpad.net/bugs/1801071 Title: XPresentPixmap() BadWindow, recompiling

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-09-02 Thread Daniel van Vugt
** Tags added: rls-bb-incoming rls-dd-incoming -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxpresent in Ubuntu. https://bugs.launchpad.net/bugs/1801071 Title: XPresentPixmap() BadWindow, recompiling fixes it To manage notifications

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-09-02 Thread Matteo Panella
I can confirm that the package from eoan fixes the xpresent compatibility error with marco/compton on 18.04 (and consequently compositing actually works). I hope this qualifies as a potential SRU for 18.04. -- You received this bug notification because you are a member of Ubuntu-X, which is

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-07-16 Thread agent 8131
I consider this a regression from 16.04 to 18.04. However, installing from eoan on 18.04 resolved this set of issues for me: https://packages.ubuntu.com/eoan/amd64/libxpresent1/download It would be great to get this into other versions as it seems like a trivial fix. -- You received this bug

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-07-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libxpresent (Ubuntu Disco) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxpresent in Ubuntu.

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-07-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libxpresent (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxpresent in Ubuntu.

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-05-16 Thread Daniel van Vugt
Modesetting provides vsync and avoids tearing in all cases except in some edge cases: * Multi-monitor * Xrandr scaling * Other broken packages like this bug But those are just bugs. One of them is fixed here and the rest should be fixed eventually in:

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-05-16 Thread Pedro Fleck
Since when? What I know is that modesetting doesn't provide VSync and it's up to the DE to enable something to avoid tearing. From what I understood from this merge request is that TearFree isn't ready yet. But the Eoan package works just fine. -- You received this bug notification because you

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-05-15 Thread Daniel van Vugt
> modesetting doesn't have a VSync option like Intel did The modesetting driver shouldn't ever tear in the single monitor case. If it does then that's a bug like this one. Although modesetting may tear in the multi-monitor case and there is an effort underway by Intel to fix that:

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-05-15 Thread Pedro Fleck
I know it is not, but I found this issue trying to fix the tearing since modesetting doesn't have a VSync option like Intel did and XFWM 4.12 VSync option didn't fix it. But I just tried the Eoan package and now XPresent works for XFWM 4.13 and my tearing problem is solved! Any chance that it will

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-05-14 Thread Daniel van Vugt
By the way, this particular bug is not about tearing, even if the aforementioned fix is. If you want to talk about tearing in MATE then please use bug 1565496. If you want to talk about tearing in XFCE or any other desktop then please open a new bug. -- You received this bug notification

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-05-14 Thread Daniel van Vugt
I haven't verified this works on disco, but first you can try installing the package from eoan on disco: https://launchpad.net/ubuntu/+archive/primary/+files/libxpresent1_1.0.0-2build1_amd64.deb -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-05-14 Thread Pedro Fleck
How to install the updated package in Disco? I'm suffering from terrible tearing using XFCE and modesetting driver, Compton works really bad and I don't want to use the old Intel DDX driver. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to

[Ubuntu-x-swat] [Bug 1801071] Re: XPresentPixmap() BadWindow, recompiling fixes it

2019-05-14 Thread Pedro Fleck
How to install the updated package in Disco? I'm suffering from terrible tearing using XFCE and modesetting driver, Compton works really bad and I don't want to use the old Intel DDX driver. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to