** Changed in: qtmir (Ubuntu)
Importance: Undecided => High
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Gerry Boland (gerboland)
** No longer affects: qtmir
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This doesn't seem to occur anymore. Not sure what fixed it, so I'm just
going to close Invalid.
** Changed in: mir
Status: New = Invalid
** Changed in: qtmir
Status: Confirmed = Invalid
** Changed in: qtmir (Ubuntu)
Status: New = Invalid
** Changed in: unity8 (Ubuntu)
** Tags added: desktop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410457
Title:
DisplayWindow::makeCurrent crash with xmir apps
To manage notifications about this bug go to:
The stack traces are a little confused as always by the fact that QtMir
names some of its things Mir* while not being a part of Mir. There
doesn't seem to be any Mir code in the stack traces.
That and the same bug doesn't exist in the mir_proving_server.
--
You received this bug notification
A little more digging: bringing up mir_proving_server and xeyes manually:
1. sudo stop lightdm
2. sudo mir_proving_server
3. sudo chown $USER /tmp/mir_socket
4. sudo chmod 777 /tmp/mir_socket
5. Xmir :1 -mirSocket /tmp/mir_socket
6. in separate shell, do:
DISPLAY=:1 xeyes
I can tell X to blank
