[Ubuntu-x-swat] [Bug 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-04-04 Thread Daniel van Vugt
Fixed in: xorg-server (2:1.19.3-1ubuntu1) zesty; urgency=medium ** Changed in: xorg-server (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu.

[Ubuntu-x-swat] [Bug 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-03-24 Thread Michał Sawicz
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1521403 Title: Unity8 crashes on suspend/standby

[Ubuntu-x-swat] [Bug 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-03-14 Thread Pat McGowan
** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1521403 Title: Unity8 crashes on suspend/standby

[Ubuntu-x-swat] [Bug 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-03-06 Thread kevin gunn
** Changed in: canonical-devices-system-image Milestone: None => u8c-1 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1521403 Title: Unity8 crashes on suspend/standby with SIGSEGV in

[Ubuntu-x-swat] [Bug 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-02-21 Thread Launchpad Bug Tracker
This bug was fixed in the package qtmir - 0.5.1+17.04.20170215.1-0ubuntu1 --- qtmir (0.5.1+17.04.20170215.1-0ubuntu1) zesty; urgency=medium [ Michał Sawicz ] * We're at provides 26 already (LP: #1662608) [ Alan Griffiths ] * Identify the code that depends directly on

[Ubuntu-x-swat] [Bug 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-31 Thread Daniel van Vugt
And furthermore: https://git.launchpad.net/~xmir-team/xorg- server/+git/xmir/commit/?id=8a53ab14880167946e805d3c16bab167fbb03683 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1521403

[Ubuntu-x-swat] [Bug 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-24 Thread Daniel van Vugt
Fortunately that's already the case. An app in Unity8 is always asking Unity8 to ask USC to turn the screen off. Unity8 already has the option of rejecting it, in theory. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu.

[Ubuntu-x-swat] [Bug 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-24 Thread Michał Sawicz
There definitely are usecases for applications requesting display power changes, but yes they need to be filtered/mangled by the shell, and only applied when the requesting app, and session, are in focus. Whether that should be a privileged operation, I'm not sure. As long as the user can easily

[Ubuntu-x-swat] [Bug 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-22 Thread Daniel van Vugt
I have now prevented Xmir from turning the physical display off under Unity8: https://git.launchpad.net/~xmir-team/xorg- server/+git/xmir/commit/?id=9a508dc77fd68f8ba321e82ed0d7c36df1ddf745 However it appears Xmir will still blank the Xmir window to black. Sounds like we need to launch Xmir with