Mir on X11 server crashed: mir_proving_server: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

[dinamic]

mir_proving_server assert failure: mir_proving_server: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

mousing arround with mir on x

 mir_proving_server --platform-input-lib server-mesa-x11.so.4
 mir_demo_client_egltriangle

died wile mousing arround egltriangle's window

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: mir-demos 0.15.1+15.10.20150903-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
Uname: Linux 4.2.0-10-generic x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
AssertionMessage: mir_proving_server: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
CurrentDesktop: Unity
Date: Sat Sep 19 15:13:02 2015
ExecutablePath: /usr/bin/mir_proving_server
InstallationDate: Installed on 2015-09-18 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150918)
ProcCmdline: mir_proving_server --platform-input-lib server-mesa-x11.so.4
Signal: 6
SourcePackage: mir
StacktraceTop:
 __assert_fail_base (fmt=0x7fbfd6d7c028 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fbfd294a7a0 "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7fbfd294a5eb "../../src/xcb_io.c", line=line@entry=274, function=function@entry=0x7fbfd294aaa6 "poll_for_event") at assert.c:92
 __GI___assert_fail (assertion=0x7fbfd294a7a0 "!xcb_xlib_threads_sequence_lost", file=0x7fbfd294a5eb "../../src/xcb_io.c", line=274, function=0x7fbfd294aaa6 "poll_for_event") at assert.c:101
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReadEvents () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: mir_proving_server assert failure: mir_proving_server: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 __assert_fail_base (fmt=0x7fbfd6d7c028 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fbfd294a7a0 <_XkeyTable+43392> "teChar", file=file@entry=0x7fbfd294a5eb <_XkeyTable+42955> "\020\004\377XosfBeginLine", line=line@entry=274, function=function@entry=0x7fbfd294aaa6 "Aborting, sorry about that.\n") at assert.c:92
 __GI___assert_fail (assertion=0x7fbfd294a7a0 <_XkeyTable+43392> "teChar", file=0x7fbfd294a5eb <_XkeyTable+42955> "\020\004\377XosfBeginLine", line=274, function=0x7fbfd294aaa6 "Aborting, sorry about that.\n") at assert.c:101
 Format_Image (resultsize=<synthetic pointer>, image=0x7fbfd6fb1820 <stderr>) at ../../src/WrBitF.c:66
 XWriteBitmapFile (display=<optimized out>, filename=<optimized out>, bitmap=<optimized out>, width=0, height=3564184537, x_hot=32886696, y_hot=32864032) at ../../src/WrBitF.c:122
 check_internal_connections (dpy=0x665e) at ../../src/xcb_io.c:119

[Daniel van Vugt (vanvugt)]

As a workaround you can run Mir natively using the option: --vt 1
Then just switch to it with Ctrl+Alt+F1/F7

[dinamic (dinamic6661)]

i'm not really sure what you want me to do :D

mir_proving_server --vt 1
[1443011089.977848] mirplatform: Found graphics driver: mesa-x11
[1443011089.978396] mirplatform: Found graphics driver: mesa-kms
Unknown command line options: --vt 1

if i run mir_demo_server on tty1 it locks my PC (it will probably work sith sudo mir_demo_server)

[dinamic (dinamic6661)]

ok so "sudo mir_demo_server --platform-graphics-lib /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.4 --vt 1"
works

[Daniel van Vugt (vanvugt)]

That's weird. You should just be able to:

    sudo mir_demo_server --vt 1

and it will recognise what vt 1 means. However I recall I have seen the same bug you describe where Mir 'forgot' what "--vt 1" means.

[Daniel van Vugt (vanvugt)]

Is this bug still a problem at all? I haven't seen it.

[Launchpad Janitor (janitor)]

[Expired for mir (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for Mir because there has been no activity for 60 days.]