Errors when trying to make a Wayland-native kiosk snapHow to troubleshoot Wayland problems in Ubuntu?Trying to install via snapFailure when trying to install any snapWhy do snap packages disappear when using the Fish shell?Is there any way to make snap installed apps look more native?Hugo Snap error when startingCan't open shared libraries (snap)
Can you have a permanent become all permanent types at the same time?
Can a landlord ask a tenant to sign an addendum to the lease that changes the terms of the first lease?
Paying to leave without notice in at-will employment state
What DC should I use for someone trying to survive indefinitely solely with an alchemy jug as their only source of food and water? (survival campaign)
How do I experimentally measure the surface area of a rock?
Average Two Letters
Why rounding odd font sizes to even?
Create virtual block device which writes to /dev/null
unite 3 Circuitikz Topologys into one Tikzpicture
Customize sysctl parameters by user
If Space Shuttle flies "like a brick", why does it need the wings?
Doubt on pronunciation of verbs (stressing)
Was there a clearly identifiable "first computer" to use or demonstrate the use of virtual memory?
Is there any point in adding more than 6 months' runway in savings instead of investing everything after that?
Is policy routing bad?
When nothing is defined, what does Mathematica take for #1?
Pattern Matching, FullForm and DisplayForm
Parsing C-like code to extract info
Why was the DC-9-80 so successful despite being obsolete almost from birth?
Horizontally mirror a brainflak program
Should I report a security vulnerability?
In a topological space , if a subset is both closed and open then the toplogy is discrete?
find a condition on B,C so set difference is associative (AB)C=A(BC)
Why do aircraft sometimes bounce while landing?
Errors when trying to make a Wayland-native kiosk snap
How to troubleshoot Wayland problems in Ubuntu?Trying to install via snapFailure when trying to install any snapWhy do snap packages disappear when using the Fish shell?Is there any way to make snap installed apps look more native?Hugo Snap error when startingCan't open shared libraries (snap)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
1
Running Ubuntu 16.04. From https://tutorials.ubuntu.com/tutorial/wayland-kiosk#0 Make a Wayland-native Kiosk snap
At https://tutorials.ubuntu.com/tutorial/wayland-kiosk#4, the following errors occur:
user@machine:~$ miral-app -kiosk -launcher 'glmark2-wayland produces Error: eglGetDisplay() failed with error: 0x3000
Terminal output below.
user@machine:~$ miral-app produces an orange Mir On X window, whereupon a black terminal window later appears.
user@machine:~$ miral-app -kiosk produces a black Mir on X window with unresponsive File, Edit etc.
user@machine:~$ miral-app -kiosk -launcher produces a black window which then closes immediately.
Do you have any suggestions on how to progress through this tutorial?
user@machine:~$ miral-app -kiosk -launcher 'glmark2-wayland'
waiting for /run/user/1000/miral_socket
[2019-07-30 11:56:59.964833] <information> mirserver: Starting
[2019-07-30 11:56:59.965756] < - debug - > mirserver: Not trying logind: "DISPLAY" is set and X need not have claimed the VT
[2019-07-30 11:56:59.966590] < - debug - > mirserver: Not using Linux VT subsystem for session management: Failed to find the current VT
[2019-07-30 11:56:59.966626] < - debug - > mirserver: No session management supported
[2019-07-30 11:56:59.967042] <information> VT switch key handler: No VT switching support available: MinimalConsoleServices does not support VT switching
[2019-07-30 11:56:59.967707] <information> mircommon: Loading modules from: /usr/lib/x86_64-linux-gnu/mir/server-platform
[2019-07-30 11:56:59.967767] <information> mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/server-mesa-x11.so.16
[2019-07-30 11:56:59.967804] <information> mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.16
[2019-07-30 11:56:59.967823] <information> mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/input-evdev.so.7
[2019-07-30 11:56:59.973179] <information> mirplatform: Found graphics driver: mir:mesa-x11 (version 1.3.0) Support priority: 128
[2019-07-30 11:56:59.973479] <information> mesa-kms: EGL platform does not support EGL_KHR_platform_gbm extension
[2019-07-30 11:56:59.973496] <information> mesa-kms: Unsupported: EGL platform supports neither EGL_KHR_platform_gbm nor EGL_MESA_platform_gbm
[2019-07-30 11:56:59.973510] <information> mirplatform: Found graphics driver: mir:mesa-kms (version 1.3.0) Support priority: 0
[2019-07-30 11:56:59.973747] <information> mirserver: Selected driver: mir:mesa-x11 (version 1.3.0)
[2019-07-30 11:57:00.223551] <information> display: Screen resolution = 1920x1080
[2019-07-30 11:57:00.223580] <information> display: ... is smaller than the requested size (1280x1024) plus border (150). Clipping to (1280x930).
[2019-07-30 11:57:00.223600] <information> display: 1 visual(s) found
[2019-07-30 11:57:00.223607] <information> display: Using the first one :
[2019-07-30 11:57:00.223614] <information> display: ID : 44
[2019-07-30 11:57:00.223621] <information> display: screen : 0
[2019-07-30 11:57:00.223629] <information> display: depth : 24
[2019-07-30 11:57:00.223636] <information> display: red_mask : 0xFF0000
[2019-07-30 11:57:00.223644] <information> display: green_mask : 0xFF00
[2019-07-30 11:57:00.223652] <information> display: blue_mask : 0xFF
[2019-07-30 11:57:00.223660] <information> display: colormap_size : 256
[2019-07-30 11:57:00.223667] <information> display: bits_per_rgb : 11
[2019-07-30 11:57:00.297508] <information> mirserver: Using software cursor
[2019-07-30 11:57:00.333119] <information> mirserver: Selected input driver: mir:x11-input (version: 1.3.0)
[2019-07-30 11:57:00.334962] < -warning- > Wayland: Failed to bind Wayland EGL display. Accelerated EGL will be unavailable.: /build/mir-zqFSab/mir-1.3.0/src/platforms/mesa/server/buffer_allocator.cpp(604): Throw in function virtual void mir::graphics::mesa::BufferAllocator::bind_display(wl_display*, std::shared_ptr<mir::Executor>)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::system_error> >
std::exception::what: Failed to bind Wayland EGL display: EGL_SUCCESS (0x3000)
[2019-07-30 11:57:00.335015] < -warning- > mirserver: Cannot set Wayland protocol filter: wl_display_set_global_filter() is unavailable in libwayland-dev 1.12.0
[2019-07-30 11:57:00.335245] <information> mirserver: Mir version 1.3.0
[2019-07-30 11:57:00.365286] <information> GLRenderer: EGL vendor: NVIDIA
[2019-07-30 11:57:00.365313] <information> GLRenderer: EGL version: 1.4
[2019-07-30 11:57:00.365325] <information> GLRenderer: EGL client APIs: OpenGL_ES OpenGL
[2019-07-30 11:57:00.365334] <information> GLRenderer: GL vendor: NVIDIA Corporation
[2019-07-30 11:57:00.365340] <information> GLRenderer: GL renderer: Quadro M1000M/PCIe/SSE2
[2019-07-30 11:57:00.365345] <information> GLRenderer: GL version: OpenGL ES 3.2 NVIDIA 384.130
[2019-07-30 11:57:00.365351] <information> GLRenderer: GLSL version: OpenGL ES GLSL ES 3.20
[2019-07-30 11:57:00.365751] <information> GLRenderer: GL max texture size = 16384
[2019-07-30 11:57:00.365767] <information> GLRenderer: GL framebuffer bits: RGBA=8888, depth=0, stencil=0
[2019-07-30 11:57:00.369455] <information> mirserver: Initial display configuration:
[2019-07-30 11:57:00.369481] <information> mirserver: * Output 1: unknown connected, used
[2019-07-30 11:57:00.369496] <information> mirserver: . |_ Physical size 16.5" 338x246mm
[2019-07-30 11:57:00.369506] <information> mirserver: . |_ Power is on
[2019-07-30 11:57:00.369517] <information> mirserver: . |_ Current mode 1280x930 60.00Hz
[2019-07-30 11:57:00.369527] <information> mirserver: . |_ Preferred mode 1280x930 60.00Hz
[2019-07-30 11:57:00.369536] <information> mirserver: . |_ Orientation normal
[2019-07-30 11:57:00.369549] <information> mirserver: . |_ Logical size 1280x930
[2019-07-30 11:57:00.369559] <information> mirserver: . |_ Logical position +0+0
[2019-07-30 11:57:00.369569] <information> mirserver: . |_ Scaling factor: 1.00
Error: eglGetDisplay() failed with error: 0x3000
Error: eglGetDisplay() failed with error: 0x3000
Error: main: Could not initialize canvas
user@machine:~$ [2019-07-30 11:57:02.451237] < -warning- > mirserver: Attempt to read from WlShmBuffer after the wl_buffer has been destroyed
snap wayland kiosk mir
edited Jul 31 at 8:34
karel
70.1k15 gold badges158 silver badges184 bronze badges
asked Jul 30 at 13:51
nisplaydamenisplaydame
63 bronze badges
add a comment
|
1
Running Ubuntu 16.04. From https://tutorials.ubuntu.com/tutorial/wayland-kiosk#0 Make a Wayland-native Kiosk snap
At https://tutorials.ubuntu.com/tutorial/wayland-kiosk#4, the following errors occur:
user@machine:~$ miral-app -kiosk -launcher 'glmark2-wayland produces Error: eglGetDisplay() failed with error: 0x3000
Terminal output below.
user@machine:~$ miral-app produces an orange Mir On X window, whereupon a black terminal window later appears.
user@machine:~$ miral-app -kiosk produces a black Mir on X window with unresponsive File, Edit etc.
user@machine:~$ miral-app -kiosk -launcher produces a black window which then closes immediately.
Do you have any suggestions on how to progress through this tutorial?
user@machine:~$ miral-app -kiosk -launcher 'glmark2-wayland'
waiting for /run/user/1000/miral_socket
[2019-07-30 11:56:59.964833] <information> mirserver: Starting
[2019-07-30 11:56:59.965756] < - debug - > mirserver: Not trying logind: "DISPLAY" is set and X need not have claimed the VT
[2019-07-30 11:56:59.966590] < - debug - > mirserver: Not using Linux VT subsystem for session management: Failed to find the current VT
[2019-07-30 11:56:59.966626] < - debug - > mirserver: No session management supported
[2019-07-30 11:56:59.967042] <information> VT switch key handler: No VT switching support available: MinimalConsoleServices does not support VT switching
[2019-07-30 11:56:59.967707] <information> mircommon: Loading modules from: /usr/lib/x86_64-linux-gnu/mir/server-platform
[2019-07-30 11:56:59.967767] <information> mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/server-mesa-x11.so.16
[2019-07-30 11:56:59.967804] <information> mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.16
[2019-07-30 11:56:59.967823] <information> mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/input-evdev.so.7
[2019-07-30 11:56:59.973179] <information> mirplatform: Found graphics driver: mir:mesa-x11 (version 1.3.0) Support priority: 128
[2019-07-30 11:56:59.973479] <information> mesa-kms: EGL platform does not support EGL_KHR_platform_gbm extension
[2019-07-30 11:56:59.973496] <information> mesa-kms: Unsupported: EGL platform supports neither EGL_KHR_platform_gbm nor EGL_MESA_platform_gbm
[2019-07-30 11:56:59.973510] <information> mirplatform: Found graphics driver: mir:mesa-kms (version 1.3.0) Support priority: 0
[2019-07-30 11:56:59.973747] <information> mirserver: Selected driver: mir:mesa-x11 (version 1.3.0)
[2019-07-30 11:57:00.223551] <information> display: Screen resolution = 1920x1080
[2019-07-30 11:57:00.223580] <information> display: ... is smaller than the requested size (1280x1024) plus border (150). Clipping to (1280x930).
[2019-07-30 11:57:00.223600] <information> display: 1 visual(s) found
[2019-07-30 11:57:00.223607] <information> display: Using the first one :
[2019-07-30 11:57:00.223614] <information> display: ID : 44
[2019-07-30 11:57:00.223621] <information> display: screen : 0
[2019-07-30 11:57:00.223629] <information> display: depth : 24
[2019-07-30 11:57:00.223636] <information> display: red_mask : 0xFF0000
[2019-07-30 11:57:00.223644] <information> display: green_mask : 0xFF00
[2019-07-30 11:57:00.223652] <information> display: blue_mask : 0xFF
[2019-07-30 11:57:00.223660] <information> display: colormap_size : 256
[2019-07-30 11:57:00.223667] <information> display: bits_per_rgb : 11
[2019-07-30 11:57:00.297508] <information> mirserver: Using software cursor
[2019-07-30 11:57:00.333119] <information> mirserver: Selected input driver: mir:x11-input (version: 1.3.0)
[2019-07-30 11:57:00.334962] < -warning- > Wayland: Failed to bind Wayland EGL display. Accelerated EGL will be unavailable.: /build/mir-zqFSab/mir-1.3.0/src/platforms/mesa/server/buffer_allocator.cpp(604): Throw in function virtual void mir::graphics::mesa::BufferAllocator::bind_display(wl_display*, std::shared_ptr<mir::Executor>)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::system_error> >
std::exception::what: Failed to bind Wayland EGL display: EGL_SUCCESS (0x3000)
[2019-07-30 11:57:00.335015] < -warning- > mirserver: Cannot set Wayland protocol filter: wl_display_set_global_filter() is unavailable in libwayland-dev 1.12.0
[2019-07-30 11:57:00.335245] <information> mirserver: Mir version 1.3.0
[2019-07-30 11:57:00.365286] <information> GLRenderer: EGL vendor: NVIDIA
[2019-07-30 11:57:00.365313] <information> GLRenderer: EGL version: 1.4
[2019-07-30 11:57:00.365325] <information> GLRenderer: EGL client APIs: OpenGL_ES OpenGL
[2019-07-30 11:57:00.365334] <information> GLRenderer: GL vendor: NVIDIA Corporation
[2019-07-30 11:57:00.365340] <information> GLRenderer: GL renderer: Quadro M1000M/PCIe/SSE2
[2019-07-30 11:57:00.365345] <information> GLRenderer: GL version: OpenGL ES 3.2 NVIDIA 384.130
[2019-07-30 11:57:00.365351] <information> GLRenderer: GLSL version: OpenGL ES GLSL ES 3.20
[2019-07-30 11:57:00.365751] <information> GLRenderer: GL max texture size = 16384
[2019-07-30 11:57:00.365767] <information> GLRenderer: GL framebuffer bits: RGBA=8888, depth=0, stencil=0
[2019-07-30 11:57:00.369455] <information> mirserver: Initial display configuration:
[2019-07-30 11:57:00.369481] <information> mirserver: * Output 1: unknown connected, used
[2019-07-30 11:57:00.369496] <information> mirserver: . |_ Physical size 16.5" 338x246mm
[2019-07-30 11:57:00.369506] <information> mirserver: . |_ Power is on
[2019-07-30 11:57:00.369517] <information> mirserver: . |_ Current mode 1280x930 60.00Hz
[2019-07-30 11:57:00.369527] <information> mirserver: . |_ Preferred mode 1280x930 60.00Hz
[2019-07-30 11:57:00.369536] <information> mirserver: . |_ Orientation normal
[2019-07-30 11:57:00.369549] <information> mirserver: . |_ Logical size 1280x930
[2019-07-30 11:57:00.369559] <information> mirserver: . |_ Logical position +0+0
[2019-07-30 11:57:00.369569] <information> mirserver: . |_ Scaling factor: 1.00
Error: eglGetDisplay() failed with error: 0x3000
Error: eglGetDisplay() failed with error: 0x3000
Error: main: Could not initialize canvas
user@machine:~$ [2019-07-30 11:57:02.451237] < -warning- > mirserver: Attempt to read from WlShmBuffer after the wl_buffer has been destroyed
snap wayland kiosk mir
edited Jul 31 at 8:34
karel
70.1k15 gold badges158 silver badges184 bronze badges
asked Jul 30 at 13:51
nisplaydamenisplaydame
63 bronze badges
add a comment
|
1
1
1
Running Ubuntu 16.04. From https://tutorials.ubuntu.com/tutorial/wayland-kiosk#0 Make a Wayland-native Kiosk snap
At https://tutorials.ubuntu.com/tutorial/wayland-kiosk#4, the following errors occur:
user@machine:~$ miral-app -kiosk -launcher 'glmark2-wayland produces Error: eglGetDisplay() failed with error: 0x3000
Terminal output below.
user@machine:~$ miral-app produces an orange Mir On X window, whereupon a black terminal window later appears.
user@machine:~$ miral-app -kiosk produces a black Mir on X window with unresponsive File, Edit etc.
user@machine:~$ miral-app -kiosk -launcher produces a black window which then closes immediately.
Do you have any suggestions on how to progress through this tutorial?
user@machine:~$ miral-app -kiosk -launcher 'glmark2-wayland'
waiting for /run/user/1000/miral_socket
[2019-07-30 11:56:59.964833] <information> mirserver: Starting
[2019-07-30 11:56:59.965756] < - debug - > mirserver: Not trying logind: "DISPLAY" is set and X need not have claimed the VT
[2019-07-30 11:56:59.966590] < - debug - > mirserver: Not using Linux VT subsystem for session management: Failed to find the current VT
[2019-07-30 11:56:59.966626] < - debug - > mirserver: No session management supported
[2019-07-30 11:56:59.967042] <information> VT switch key handler: No VT switching support available: MinimalConsoleServices does not support VT switching
[2019-07-30 11:56:59.967707] <information> mircommon: Loading modules from: /usr/lib/x86_64-linux-gnu/mir/server-platform
[2019-07-30 11:56:59.967767] <information> mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/server-mesa-x11.so.16
[2019-07-30 11:56:59.967804] <information> mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.16
[2019-07-30 11:56:59.967823] <information> mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/input-evdev.so.7
[2019-07-30 11:56:59.973179] <information> mirplatform: Found graphics driver: mir:mesa-x11 (version 1.3.0) Support priority: 128
[2019-07-30 11:56:59.973479] <information> mesa-kms: EGL platform does not support EGL_KHR_platform_gbm extension
[2019-07-30 11:56:59.973496] <information> mesa-kms: Unsupported: EGL platform supports neither EGL_KHR_platform_gbm nor EGL_MESA_platform_gbm
[2019-07-30 11:56:59.973510] <information> mirplatform: Found graphics driver: mir:mesa-kms (version 1.3.0) Support priority: 0
[2019-07-30 11:56:59.973747] <information> mirserver: Selected driver: mir:mesa-x11 (version 1.3.0)
[2019-07-30 11:57:00.223551] <information> display: Screen resolution = 1920x1080
[2019-07-30 11:57:00.223580] <information> display: ... is smaller than the requested size (1280x1024) plus border (150). Clipping to (1280x930).
[2019-07-30 11:57:00.223600] <information> display: 1 visual(s) found
[2019-07-30 11:57:00.223607] <information> display: Using the first one :
[2019-07-30 11:57:00.223614] <information> display: ID : 44
[2019-07-30 11:57:00.223621] <information> display: screen : 0
[2019-07-30 11:57:00.223629] <information> display: depth : 24
[2019-07-30 11:57:00.223636] <information> display: red_mask : 0xFF0000
[2019-07-30 11:57:00.223644] <information> display: green_mask : 0xFF00
[2019-07-30 11:57:00.223652] <information> display: blue_mask : 0xFF
[2019-07-30 11:57:00.223660] <information> display: colormap_size : 256
[2019-07-30 11:57:00.223667] <information> display: bits_per_rgb : 11
[2019-07-30 11:57:00.297508] <information> mirserver: Using software cursor
[2019-07-30 11:57:00.333119] <information> mirserver: Selected input driver: mir:x11-input (version: 1.3.0)
[2019-07-30 11:57:00.334962] < -warning- > Wayland: Failed to bind Wayland EGL display. Accelerated EGL will be unavailable.: /build/mir-zqFSab/mir-1.3.0/src/platforms/mesa/server/buffer_allocator.cpp(604): Throw in function virtual void mir::graphics::mesa::BufferAllocator::bind_display(wl_display*, std::shared_ptr<mir::Executor>)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::system_error> >
std::exception::what: Failed to bind Wayland EGL display: EGL_SUCCESS (0x3000)
[2019-07-30 11:57:00.335015] < -warning- > mirserver: Cannot set Wayland protocol filter: wl_display_set_global_filter() is unavailable in libwayland-dev 1.12.0
[2019-07-30 11:57:00.335245] <information> mirserver: Mir version 1.3.0
[2019-07-30 11:57:00.365286] <information> GLRenderer: EGL vendor: NVIDIA
[2019-07-30 11:57:00.365313] <information> GLRenderer: EGL version: 1.4
[2019-07-30 11:57:00.365325] <information> GLRenderer: EGL client APIs: OpenGL_ES OpenGL
[2019-07-30 11:57:00.365334] <information> GLRenderer: GL vendor: NVIDIA Corporation
[2019-07-30 11:57:00.365340] <information> GLRenderer: GL renderer: Quadro M1000M/PCIe/SSE2
[2019-07-30 11:57:00.365345] <information> GLRenderer: GL version: OpenGL ES 3.2 NVIDIA 384.130
[2019-07-30 11:57:00.365351] <information> GLRenderer: GLSL version: OpenGL ES GLSL ES 3.20
[2019-07-30 11:57:00.365751] <information> GLRenderer: GL max texture size = 16384
[2019-07-30 11:57:00.365767] <information> GLRenderer: GL framebuffer bits: RGBA=8888, depth=0, stencil=0
[2019-07-30 11:57:00.369455] <information> mirserver: Initial display configuration:
[2019-07-30 11:57:00.369481] <information> mirserver: * Output 1: unknown connected, used
[2019-07-30 11:57:00.369496] <information> mirserver: . |_ Physical size 16.5" 338x246mm
[2019-07-30 11:57:00.369506] <information> mirserver: . |_ Power is on
[2019-07-30 11:57:00.369517] <information> mirserver: . |_ Current mode 1280x930 60.00Hz
[2019-07-30 11:57:00.369527] <information> mirserver: . |_ Preferred mode 1280x930 60.00Hz
[2019-07-30 11:57:00.369536] <information> mirserver: . |_ Orientation normal
[2019-07-30 11:57:00.369549] <information> mirserver: . |_ Logical size 1280x930
[2019-07-30 11:57:00.369559] <information> mirserver: . |_ Logical position +0+0
[2019-07-30 11:57:00.369569] <information> mirserver: . |_ Scaling factor: 1.00
Error: eglGetDisplay() failed with error: 0x3000
Error: eglGetDisplay() failed with error: 0x3000
Error: main: Could not initialize canvas
user@machine:~$ [2019-07-30 11:57:02.451237] < -warning- > mirserver: Attempt to read from WlShmBuffer after the wl_buffer has been destroyed
snap wayland kiosk mir
edited Jul 31 at 8:34
karel
70.1k15 gold badges158 silver badges184 bronze badges
asked Jul 30 at 13:51
nisplaydamenisplaydame
63 bronze badges
Running Ubuntu 16.04. From https://tutorials.ubuntu.com/tutorial/wayland-kiosk#0 Make a Wayland-native Kiosk snap
At https://tutorials.ubuntu.com/tutorial/wayland-kiosk#4, the following errors occur:
user@machine:~$ miral-app -kiosk -launcher 'glmark2-wayland produces Error: eglGetDisplay() failed with error: 0x3000
Terminal output below.
user@machine:~$ miral-app produces an orange Mir On X window, whereupon a black terminal window later appears.
user@machine:~$ miral-app -kiosk produces a black Mir on X window with unresponsive File, Edit etc.
user@machine:~$ miral-app -kiosk -launcher produces a black window which then closes immediately.
Do you have any suggestions on how to progress through this tutorial?
user@machine:~$ miral-app -kiosk -launcher 'glmark2-wayland'
waiting for /run/user/1000/miral_socket
[2019-07-30 11:56:59.964833] <information> mirserver: Starting
[2019-07-30 11:56:59.965756] < - debug - > mirserver: Not trying logind: "DISPLAY" is set and X need not have claimed the VT
[2019-07-30 11:56:59.966590] < - debug - > mirserver: Not using Linux VT subsystem for session management: Failed to find the current VT
[2019-07-30 11:56:59.966626] < - debug - > mirserver: No session management supported
[2019-07-30 11:56:59.967042] <information> VT switch key handler: No VT switching support available: MinimalConsoleServices does not support VT switching
[2019-07-30 11:56:59.967707] <information> mircommon: Loading modules from: /usr/lib/x86_64-linux-gnu/mir/server-platform
[2019-07-30 11:56:59.967767] <information> mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/server-mesa-x11.so.16
[2019-07-30 11:56:59.967804] <information> mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.16
[2019-07-30 11:56:59.967823] <information> mircommon: Loading module: /usr/lib/x86_64-linux-gnu/mir/server-platform/input-evdev.so.7
[2019-07-30 11:56:59.973179] <information> mirplatform: Found graphics driver: mir:mesa-x11 (version 1.3.0) Support priority: 128
[2019-07-30 11:56:59.973479] <information> mesa-kms: EGL platform does not support EGL_KHR_platform_gbm extension
[2019-07-30 11:56:59.973496] <information> mesa-kms: Unsupported: EGL platform supports neither EGL_KHR_platform_gbm nor EGL_MESA_platform_gbm
[2019-07-30 11:56:59.973510] <information> mirplatform: Found graphics driver: mir:mesa-kms (version 1.3.0) Support priority: 0
[2019-07-30 11:56:59.973747] <information> mirserver: Selected driver: mir:mesa-x11 (version 1.3.0)
[2019-07-30 11:57:00.223551] <information> display: Screen resolution = 1920x1080
[2019-07-30 11:57:00.223580] <information> display: ... is smaller than the requested size (1280x1024) plus border (150). Clipping to (1280x930).
[2019-07-30 11:57:00.223600] <information> display: 1 visual(s) found
[2019-07-30 11:57:00.223607] <information> display: Using the first one :
[2019-07-30 11:57:00.223614] <information> display: ID : 44
[2019-07-30 11:57:00.223621] <information> display: screen : 0
[2019-07-30 11:57:00.223629] <information> display: depth : 24
[2019-07-30 11:57:00.223636] <information> display: red_mask : 0xFF0000
[2019-07-30 11:57:00.223644] <information> display: green_mask : 0xFF00
[2019-07-30 11:57:00.223652] <information> display: blue_mask : 0xFF
[2019-07-30 11:57:00.223660] <information> display: colormap_size : 256
[2019-07-30 11:57:00.223667] <information> display: bits_per_rgb : 11
[2019-07-30 11:57:00.297508] <information> mirserver: Using software cursor
[2019-07-30 11:57:00.333119] <information> mirserver: Selected input driver: mir:x11-input (version: 1.3.0)
[2019-07-30 11:57:00.334962] < -warning- > Wayland: Failed to bind Wayland EGL display. Accelerated EGL will be unavailable.: /build/mir-zqFSab/mir-1.3.0/src/platforms/mesa/server/buffer_allocator.cpp(604): Throw in function virtual void mir::graphics::mesa::BufferAllocator::bind_display(wl_display*, std::shared_ptr<mir::Executor>)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::system_error> >
std::exception::what: Failed to bind Wayland EGL display: EGL_SUCCESS (0x3000)
[2019-07-30 11:57:00.335015] < -warning- > mirserver: Cannot set Wayland protocol filter: wl_display_set_global_filter() is unavailable in libwayland-dev 1.12.0
[2019-07-30 11:57:00.335245] <information> mirserver: Mir version 1.3.0
[2019-07-30 11:57:00.365286] <information> GLRenderer: EGL vendor: NVIDIA
[2019-07-30 11:57:00.365313] <information> GLRenderer: EGL version: 1.4
[2019-07-30 11:57:00.365325] <information> GLRenderer: EGL client APIs: OpenGL_ES OpenGL
[2019-07-30 11:57:00.365334] <information> GLRenderer: GL vendor: NVIDIA Corporation
[2019-07-30 11:57:00.365340] <information> GLRenderer: GL renderer: Quadro M1000M/PCIe/SSE2
[2019-07-30 11:57:00.365345] <information> GLRenderer: GL version: OpenGL ES 3.2 NVIDIA 384.130
[2019-07-30 11:57:00.365351] <information> GLRenderer: GLSL version: OpenGL ES GLSL ES 3.20
[2019-07-30 11:57:00.365751] <information> GLRenderer: GL max texture size = 16384
[2019-07-30 11:57:00.365767] <information> GLRenderer: GL framebuffer bits: RGBA=8888, depth=0, stencil=0
[2019-07-30 11:57:00.369455] <information> mirserver: Initial display configuration:
[2019-07-30 11:57:00.369481] <information> mirserver: * Output 1: unknown connected, used
[2019-07-30 11:57:00.369496] <information> mirserver: . |_ Physical size 16.5" 338x246mm
[2019-07-30 11:57:00.369506] <information> mirserver: . |_ Power is on
[2019-07-30 11:57:00.369517] <information> mirserver: . |_ Current mode 1280x930 60.00Hz
[2019-07-30 11:57:00.369527] <information> mirserver: . |_ Preferred mode 1280x930 60.00Hz
[2019-07-30 11:57:00.369536] <information> mirserver: . |_ Orientation normal
[2019-07-30 11:57:00.369549] <information> mirserver: . |_ Logical size 1280x930
[2019-07-30 11:57:00.369559] <information> mirserver: . |_ Logical position +0+0
[2019-07-30 11:57:00.369569] <information> mirserver: . |_ Scaling factor: 1.00
Error: eglGetDisplay() failed with error: 0x3000
Error: eglGetDisplay() failed with error: 0x3000
Error: main: Could not initialize canvas
user@machine:~$ [2019-07-30 11:57:02.451237] < -warning- > mirserver: Attempt to read from WlShmBuffer after the wl_buffer has been destroyed
snap wayland kiosk mir
snap wayland kiosk mir
edited Jul 31 at 8:34
karel
70.1k15 gold badges158 silver badges184 bronze badges
asked Jul 30 at 13:51
nisplaydamenisplaydame
63 bronze badges
edited Jul 31 at 8:34
karel
70.1k15 gold badges158 silver badges184 bronze badges
asked Jul 30 at 13:51
nisplaydamenisplaydame
63 bronze badges
edited Jul 31 at 8:34
karel
70.1k15 gold badges158 silver badges184 bronze badges
edited Jul 31 at 8:34
karel
70.1k15 gold badges158 silver badges184 bronze badges
edited Jul 31 at 8:34
karel
70.1k15 gold badges158 silver badges184 bronze badges
70.1k15 gold badges158 silver badges184 bronze badges
asked Jul 30 at 13:51
nisplaydamenisplaydame
63 bronze badges
asked Jul 30 at 13:51
nisplaydamenisplaydame
63 bronze badges
asked Jul 30 at 13:51
nisplaydamenisplaydame
63 bronze badges
63 bronze badges
add a comment
|
add a comment
|
1 Answer
1
active
oldest
votes
1
I can explain some of what you are seeing. The following message is unusual (but not fatal to Mir) and suggests your graphics hardware is different to anything I've access to:
[2019-07-30 11:57:00.334962] < -warning- > Wayland: Failed to bind Wayland EGL display. Accelerated EGL will be unavailable.: /build/mir-zqFSab/mir-1.3.0/src/platforms/mesa/server/buffer_allocator.cpp(604): Throw in function virtual void mir::graphics::mesa::BufferAllocator::bind_display(wl_display*, std::shared_ptr<mir::Executor>)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::system_error> >
std::exception::what: Failed to bind Wayland EGL display: EGL_SUCCESS (0x3000)
While Mir continues to work, it could well be that glmark2-wayland fails when it encounters the same thing.
You will likely see better results on Ubuntu 18.04 as a lot of things in the Wayland stack improved between 16.04 and 18.04.
The problems you see with other incantations (miral-app and miral-app -kiosk) are due to the poor support for Wayland in 16.04. They are not worth explaining here as they do not relate to the tutorial.
answered Jul 31 at 14:25
Alan GriffithsAlan Griffiths
112 bronze badges
Thanks.sudo lshw -C displaygivesproduct: GM107GLM [Quadro M1000M], which is NVIDIA. I will keep upgrading to 18.04 as a last resort for now as it may introduce issues with other installed apps.
– nisplaydame
Jul 31 at 15:02
If your laptop has the option to switch to Intel rather than Nvidia graphics that allow you to may work around this problem.
– Alan Griffiths
Aug 1 at 14:31
Thanks. I am currently upgrading another machine from 16.04 to 18.04 and will them try the tutorial on the 18.04 machine.
– nisplaydame
Aug 1 at 15:55
From Software & Updates on 16.04 machine the current nvidia binary driver version is 384.130 whereas nvidia.com/object/unix.html has Latest Long Lived Branch Version as 430.40 but installing that may open a can of worms.
– nisplaydame
Aug 1 at 16:02
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1162153%2ferrors-when-trying-to-make-a-wayland-native-kiosk-snap%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
I can explain some of what you are seeing. The following message is unusual (but not fatal to Mir) and suggests your graphics hardware is different to anything I've access to:
[2019-07-30 11:57:00.334962] < -warning- > Wayland: Failed to bind Wayland EGL display. Accelerated EGL will be unavailable.: /build/mir-zqFSab/mir-1.3.0/src/platforms/mesa/server/buffer_allocator.cpp(604): Throw in function virtual void mir::graphics::mesa::BufferAllocator::bind_display(wl_display*, std::shared_ptr<mir::Executor>)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::system_error> >
std::exception::what: Failed to bind Wayland EGL display: EGL_SUCCESS (0x3000)
While Mir continues to work, it could well be that glmark2-wayland fails when it encounters the same thing.
You will likely see better results on Ubuntu 18.04 as a lot of things in the Wayland stack improved between 16.04 and 18.04.
The problems you see with other incantations (miral-app and miral-app -kiosk) are due to the poor support for Wayland in 16.04. They are not worth explaining here as they do not relate to the tutorial.
answered Jul 31 at 14:25
Alan GriffithsAlan Griffiths
112 bronze badges
Thanks.sudo lshw -C displaygivesproduct: GM107GLM [Quadro M1000M], which is NVIDIA. I will keep upgrading to 18.04 as a last resort for now as it may introduce issues with other installed apps.
– nisplaydame
Jul 31 at 15:02
If your laptop has the option to switch to Intel rather than Nvidia graphics that allow you to may work around this problem.
– Alan Griffiths
Aug 1 at 14:31
Thanks. I am currently upgrading another machine from 16.04 to 18.04 and will them try the tutorial on the 18.04 machine.
– nisplaydame
Aug 1 at 15:55
From Software & Updates on 16.04 machine the current nvidia binary driver version is 384.130 whereas nvidia.com/object/unix.html has Latest Long Lived Branch Version as 430.40 but installing that may open a can of worms.
– nisplaydame
Aug 1 at 16:02
add a comment
|
1
I can explain some of what you are seeing. The following message is unusual (but not fatal to Mir) and suggests your graphics hardware is different to anything I've access to:
[2019-07-30 11:57:00.334962] < -warning- > Wayland: Failed to bind Wayland EGL display. Accelerated EGL will be unavailable.: /build/mir-zqFSab/mir-1.3.0/src/platforms/mesa/server/buffer_allocator.cpp(604): Throw in function virtual void mir::graphics::mesa::BufferAllocator::bind_display(wl_display*, std::shared_ptr<mir::Executor>)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::system_error> >
std::exception::what: Failed to bind Wayland EGL display: EGL_SUCCESS (0x3000)
While Mir continues to work, it could well be that glmark2-wayland fails when it encounters the same thing.
You will likely see better results on Ubuntu 18.04 as a lot of things in the Wayland stack improved between 16.04 and 18.04.
The problems you see with other incantations (miral-app and miral-app -kiosk) are due to the poor support for Wayland in 16.04. They are not worth explaining here as they do not relate to the tutorial.
answered Jul 31 at 14:25
Alan GriffithsAlan Griffiths
112 bronze badges
Thanks.sudo lshw -C displaygivesproduct: GM107GLM [Quadro M1000M], which is NVIDIA. I will keep upgrading to 18.04 as a last resort for now as it may introduce issues with other installed apps.
– nisplaydame
Jul 31 at 15:02
If your laptop has the option to switch to Intel rather than Nvidia graphics that allow you to may work around this problem.
– Alan Griffiths
Aug 1 at 14:31
Thanks. I am currently upgrading another machine from 16.04 to 18.04 and will them try the tutorial on the 18.04 machine.
– nisplaydame
Aug 1 at 15:55
From Software & Updates on 16.04 machine the current nvidia binary driver version is 384.130 whereas nvidia.com/object/unix.html has Latest Long Lived Branch Version as 430.40 but installing that may open a can of worms.
– nisplaydame
Aug 1 at 16:02
add a comment
|
1
1
1
I can explain some of what you are seeing. The following message is unusual (but not fatal to Mir) and suggests your graphics hardware is different to anything I've access to:
[2019-07-30 11:57:00.334962] < -warning- > Wayland: Failed to bind Wayland EGL display. Accelerated EGL will be unavailable.: /build/mir-zqFSab/mir-1.3.0/src/platforms/mesa/server/buffer_allocator.cpp(604): Throw in function virtual void mir::graphics::mesa::BufferAllocator::bind_display(wl_display*, std::shared_ptr<mir::Executor>)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::system_error> >
std::exception::what: Failed to bind Wayland EGL display: EGL_SUCCESS (0x3000)
While Mir continues to work, it could well be that glmark2-wayland fails when it encounters the same thing.
You will likely see better results on Ubuntu 18.04 as a lot of things in the Wayland stack improved between 16.04 and 18.04.
The problems you see with other incantations (miral-app and miral-app -kiosk) are due to the poor support for Wayland in 16.04. They are not worth explaining here as they do not relate to the tutorial.
answered Jul 31 at 14:25
Alan GriffithsAlan Griffiths
112 bronze badges
I can explain some of what you are seeing. The following message is unusual (but not fatal to Mir) and suggests your graphics hardware is different to anything I've access to:
[2019-07-30 11:57:00.334962] < -warning- > Wayland: Failed to bind Wayland EGL display. Accelerated EGL will be unavailable.: /build/mir-zqFSab/mir-1.3.0/src/platforms/mesa/server/buffer_allocator.cpp(604): Throw in function virtual void mir::graphics::mesa::BufferAllocator::bind_display(wl_display*, std::shared_ptr<mir::Executor>)
Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::system_error> >
std::exception::what: Failed to bind Wayland EGL display: EGL_SUCCESS (0x3000)
While Mir continues to work, it could well be that glmark2-wayland fails when it encounters the same thing.
You will likely see better results on Ubuntu 18.04 as a lot of things in the Wayland stack improved between 16.04 and 18.04.
The problems you see with other incantations (miral-app and miral-app -kiosk) are due to the poor support for Wayland in 16.04. They are not worth explaining here as they do not relate to the tutorial.
answered Jul 31 at 14:25
Alan GriffithsAlan Griffiths
112 bronze badges
answered Jul 31 at 14:25
Alan GriffithsAlan Griffiths
112 bronze badges
answered Jul 31 at 14:25
Alan GriffithsAlan Griffiths
112 bronze badges
answered Jul 31 at 14:25
Alan GriffithsAlan Griffiths
112 bronze badges
112 bronze badges
Thanks.sudo lshw -C displaygivesproduct: GM107GLM [Quadro M1000M], which is NVIDIA. I will keep upgrading to 18.04 as a last resort for now as it may introduce issues with other installed apps.
– nisplaydame
Jul 31 at 15:02
If your laptop has the option to switch to Intel rather than Nvidia graphics that allow you to may work around this problem.
– Alan Griffiths
Aug 1 at 14:31
Thanks. I am currently upgrading another machine from 16.04 to 18.04 and will them try the tutorial on the 18.04 machine.
– nisplaydame
Aug 1 at 15:55
From Software & Updates on 16.04 machine the current nvidia binary driver version is 384.130 whereas nvidia.com/object/unix.html has Latest Long Lived Branch Version as 430.40 but installing that may open a can of worms.
– nisplaydame
Aug 1 at 16:02
add a comment
|
Thanks.sudo lshw -C displaygivesproduct: GM107GLM [Quadro M1000M], which is NVIDIA. I will keep upgrading to 18.04 as a last resort for now as it may introduce issues with other installed apps.
– nisplaydame
Jul 31 at 15:02
If your laptop has the option to switch to Intel rather than Nvidia graphics that allow you to may work around this problem.
– Alan Griffiths
Aug 1 at 14:31
Thanks. I am currently upgrading another machine from 16.04 to 18.04 and will them try the tutorial on the 18.04 machine.
– nisplaydame
Aug 1 at 15:55
From Software & Updates on 16.04 machine the current nvidia binary driver version is 384.130 whereas nvidia.com/object/unix.html has Latest Long Lived Branch Version as 430.40 but installing that may open a can of worms.
– nisplaydame
Aug 1 at 16:02
Thanks.
sudo lshw -C display gives product: GM107GLM [Quadro M1000M], which is NVIDIA. I will keep upgrading to 18.04 as a last resort for now as it may introduce issues with other installed apps.– nisplaydame
Jul 31 at 15:02
Thanks.
sudo lshw -C display gives product: GM107GLM [Quadro M1000M], which is NVIDIA. I will keep upgrading to 18.04 as a last resort for now as it may introduce issues with other installed apps.– nisplaydame
Jul 31 at 15:02
If your laptop has the option to switch to Intel rather than Nvidia graphics that allow you to may work around this problem.
– Alan Griffiths
Aug 1 at 14:31
If your laptop has the option to switch to Intel rather than Nvidia graphics that allow you to may work around this problem.
– Alan Griffiths
Aug 1 at 14:31
Thanks. I am currently upgrading another machine from 16.04 to 18.04 and will them try the tutorial on the 18.04 machine.
– nisplaydame
Aug 1 at 15:55
Thanks. I am currently upgrading another machine from 16.04 to 18.04 and will them try the tutorial on the 18.04 machine.
– nisplaydame
Aug 1 at 15:55
From Software & Updates on 16.04 machine the current nvidia binary driver version is 384.130 whereas nvidia.com/object/unix.html has Latest Long Lived Branch Version as 430.40 but installing that may open a can of worms.
– nisplaydame
Aug 1 at 16:02
From Software & Updates on 16.04 machine the current nvidia binary driver version is 384.130 whereas nvidia.com/object/unix.html has Latest Long Lived Branch Version as 430.40 but installing that may open a can of worms.
– nisplaydame
Aug 1 at 16:02
add a comment
|
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1162153%2ferrors-when-trying-to-make-a-wayland-native-kiosk-snap%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
