[Touch-packages] [Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-18 Thread Daniel van Vugt
Yeah, sorry I was meaning to tell you but never caught you on IRC... I noticed Xmir does modify the display config, but only to implement DPMS. That's legacy code from the days when Xmir was full screen. Although full screen mode is also the default mode. So I'm wondering if we need to make the

[Touch-packages] [Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-18 Thread Gerry Boland
Yeah I figured it out. Non rootless (rooted!) XMir wants to decide the display power state (DPMS). Unity8/QtMir never had to deal with clients doing that before. Longer term Unity8 should filter such requests as it's quite rude for an app to be able to turn off your display on you, but I've a

[Touch-packages] [Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-11 Thread Daniel van Vugt
You might find it useful to look through stack traces from other users: https://errors.ubuntu.com/problem/6cee045a96ab5c9a03847aeb290f4860eea1034d -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu.

[Touch-packages] [Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-11 Thread Gerry Boland
I'm failing to reproduce this unfortunately. I'm also failing to create a libertine container. It was failing due to bug 1653973, so I installed silo 2341, but now it fails with: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user LxcContainer.py:254: ERROR:

[Touch-packages] [Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-10 Thread Christopher Townsend
Some more data points... I disabled the screen blanking, but that made no difference. But with the screen not blanked, I started an X app through Xmir and left U8 idle and observed at almost exactly 10 minutes of idle time, U8 crashed. This is what was in unity8.log at the time of the crash:

[Touch-packages] [Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-09 Thread Christopher Townsend
This is the easiest way to reproduce for me: - Unity 8 desktop session, either X+O or Zesty - Create a Libertine container and install an app in it such as Firefox. - Start the X app. - Wait ~30 minutes, ie, leave the system alone. Xmir seems to exacerbate the issue, but I have observed the

[Touch-packages] [Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-09 Thread Christopher Townsend
Bug #1654581 was duped to this one, but I will say that the crash has become much more prevalent, like nearly 100% reproducible after the last qtmir release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu.

[Touch-packages] [Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtmir (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu.

[Touch-packages] [Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-08 Thread Daniel van Vugt
** Summary changed: - /usr/bin/unity8:11:Screen::makeCurrent:ScreenWindow::makeCurrent:MirOpenGLContext::makeCurrent:QOpenGLContext::makeCurrent:QSGRenderThread::run + Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406) ** Also affects: unity8 (Ubuntu)

[Touch-packages] [Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu.