[Desktop-packages] [Bug 1420334] Re: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows)
** Changed in: miral Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1420334 Title: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows) Status in Mir: Fix Released Status in MirAL: Won't Fix Status in mir package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: Mir needs a client API to allow surfaces to move themselves relatively. This is required to support full client-side decorations (bug 1398849), and also other apps like Google Chrome and Gnome Nautilus which can be dragged using part of their client areas. Later additions that are so similar I think they are part of the same bug: there need to be client APIs for "always on top" and "client initiate resize". To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1420334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8
gtk-mir is no longer a thing ** No longer affects: unity8 (Ubuntu) ** No longer affects: qtmir (Ubuntu) ** No longer affects: mir (Ubuntu) ** No longer affects: gtk+3.0 (Ubuntu) ** No longer affects: miral ** No longer affects: mir ** Changed in: canonical-devices-system-image Status: In Progress => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1669524 Title: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8 Status in Canonical System Image: Invalid Bug description: ubuntu 17.04 unity8 [unity8] Always on Top, Move and Resize doesn't work open solitaire, right click on the title bar (see attachement) and then select Always on Top. the app doesn't stay on top. same with Move and Resize, does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866069] Re: Investigate segfault on Mir
Found the underlying bug in Mir. (Re-uploading to a texture from
multiple threads.)
** Changed in: mesa (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1866069
Title:
Investigate segfault on Mir
Status in mesa package in Ubuntu:
Invalid
Bug description:
This occurs with the development version of Mir running on 18.04LTS
(not seen on later series). (This version of Mir can be installed from
ppa:mir-team/dev).
1. Start multiscreen Mir-on-X: miral-app -demo-server --x11-output
640x480:800x600.
2. Position windows side-by-side to make it easy to move cursor across
windows.
3. Drag the terminal window back and forth between windows.
Expect: everything works smoothly.
Actual: Eventually (can take 30sec) a core dump.
It looks like internal mesa state is inconsistent as src_mt is assigned with
intelImage->mt and not changed in ntel_miptree_copy_teximage() but...
...
multi-thre Thread 0x7fee68b117 In: intel_miptree_copy_teximage
L1438 PC: 0x7fee6bd1739a
(gdb) f 1
#1 0x7fee6bd1739a in intel_miptree_copy_teximage (brw=0x55e9f1a066a0,
intelImage=0x7fee58075fc0, dst_mt=0x7fee5807b120)
at ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1438
(gdb) p src_mt
$1 = (struct intel_mipmap_tree *) 0x0
(gdb) p intelImage->mt
$2 = (struct intel_mipmap_tree *) 0x7fee5807b120
Backtrace:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7fee6bd16ea6 in intel_miptree_copy_slice (brw=0x55e9f1a066a0,
src_mt=0x0, src_level=0, src_layer=0, dst_mt=0x7fee5807b120,
dst_level=0, dst_layer=0) at
../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1332
1332 ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c: No such file or
directory.
[Current thread is 1 (Thread 0x7fee68b11700 (LWP 7872))]
(gdb) bt
#0 0x7fee6bd16ea6 in intel_miptree_copy_slice (brw=0x55e9f1a066a0,
src_mt=0x0, src_level=0, src_layer=0, dst_mt=
0x7fee5807b120, dst_level=0, dst_layer=0) at
../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1332
#1 0x7fee6bd1739a in intel_miptree_copy_teximage (brw=0x55e9f1a066a0,
intelImage=0x7fee58075fc0, dst_mt=0x7fee5807b120)
at ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1438
#2 0x7fee6bd280e6 in intel_finalize_mipmap_tree (brw=0x55e9f1a066a0,
tObj=0x7fee58086910)
at ../src/mesa/drivers/dri/i965/intel_tex_validate.c:179
#3 0x7fee6bd281fb in brw_validate_textures (brw=0x55e9f1a066a0) at
../src/mesa/drivers/dri/i965/intel_tex_validate.c:219
#4 0x7fee6bce3932 in brw_prepare_drawing (ctx=0x55e9f1a066a0, ib=0x0,
index_bounds_valid=true, min_index=0, max_index=3)
at ../src/mesa/drivers/dri/i965/brw_draw.c:816
#5 0x7fee6bce4496 in brw_draw_prims (ctx=0x55e9f1a066a0,
prims=0x7fee68b10480, nr_prims=1, ib=0x0, index_bounds_valid=1 '\001',
min_index=0, max_index=3, gl_xfb_obj=0x0, stream=0, indirect=0x0) at
../src/mesa/drivers/dri/i965/brw_draw.c:1148
#6 0x7fee6c0e4163 in _mesa_draw_arrays (ctx=0x55e9f1a066a0, mode=5,
start=0, count=4, numInstances=1, baseInstance=0, drawID=0)
at ../src/mesa/main/draw.c:374
#7 0x7fee6c0e48eb in _mesa_DrawArrays (mode=5, start=0, count=4) at
../src/mesa/main/draw.c:531
#8 0x7fee77148a8a in
mir::renderer::gl::Renderer::draw(mir::graphics::Renderable const&) const
(this=0x7fee58000b20, renderable=
...) at /home/alan/display_server/mir/src/renderers/gl/renderer.cpp:631
#9 0x7fee77147e13 in
mir::renderer::gl::Renderer::render(std::vector,
std::allocator > > const&) const
(this=0x7fee58000b20, renderables=std::vector of length 2, capacity 2 = {...})
at /home/alan/display_server/mir/src/renderers/gl/renderer.cpp:437
#10 0x7fee76f0c728 in
mir::compositor::DefaultDisplayBufferCompositor::composite(std::vector,
std::allocator > >&&)
(this=0x7fee5800c840, scene_elements=...)
at
/home/alan/display_server/mir/src/server/compositor/default_display_buffer_compositor.cpp:84
#11 0x7fee76f12781 in mir::compositor::CompositingFunctor::operator()()
(this=0x55e9f1b6a3a0)
at
/home/alan/display_server/mir/src/server/compositor/multi_threaded_compositor.cpp:141
#12 0x7fee76f18311 in std::__invoke_impl(std::__invoke_other,
mir::compositor::CompositingFunctor&) (__f=...) at
/usr/include/c++/7/bits/invoke.h:60
#13 0x7fee76f178b4 in
std::__invoke(mir::compositor::CompositingFunctor&)
(__fn=...)
at /usr/include/c++/7/bits/invoke.h:95
#14 0x7fee76f16ae0 in
std::reference_wrapper::operator()<>()
const (this=0x7fee68b10af0)
at /usr/include/c++/7/bits/refwrap.h:356
#15 0x7fee76f15aac in std::_Function_handler
>::_M_invoke(std::_Any_data const&) (__functor=...) at
/usr/include/c++/7/bits/std_function.h:316
#16 0x7fee76daedbc in
[Desktop-packages] [Bug 1866069] [NEW] Investigate segfault on Mir
Public bug reported:
This occurs with the development version of Mir running on 18.04LTS (not
seen on later series). (This version of Mir can be installed from ppa
:mir-team/dev).
1. Start multiscreen Mir-on-X: miral-app -demo-server --x11-output
640x480:800x600.
2. Position windows side-by-side to make it easy to move cursor across windows.
3. Drag the terminal window back and forth between windows.
Expect: everything works smoothly.
Actual: Eventually (can take 30sec) a core dump.
It looks like internal mesa state is inconsistent as src_mt is assigned with
intelImage->mt and not changed in ntel_miptree_copy_teximage() but...
...
multi-thre Thread 0x7fee68b117 In: intel_miptree_copy_teximage
L1438 PC: 0x7fee6bd1739a
(gdb) f 1
#1 0x7fee6bd1739a in intel_miptree_copy_teximage (brw=0x55e9f1a066a0,
intelImage=0x7fee58075fc0, dst_mt=0x7fee5807b120)
at ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1438
(gdb) p src_mt
$1 = (struct intel_mipmap_tree *) 0x0
(gdb) p intelImage->mt
$2 = (struct intel_mipmap_tree *) 0x7fee5807b120
Backtrace:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7fee6bd16ea6 in intel_miptree_copy_slice (brw=0x55e9f1a066a0,
src_mt=0x0, src_level=0, src_layer=0, dst_mt=0x7fee5807b120,
dst_level=0, dst_layer=0) at
../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1332
1332../src/mesa/drivers/dri/i965/intel_mipmap_tree.c: No such file or
directory.
[Current thread is 1 (Thread 0x7fee68b11700 (LWP 7872))]
(gdb) bt
#0 0x7fee6bd16ea6 in intel_miptree_copy_slice (brw=0x55e9f1a066a0,
src_mt=0x0, src_level=0, src_layer=0, dst_mt=
0x7fee5807b120, dst_level=0, dst_layer=0) at
../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1332
#1 0x7fee6bd1739a in intel_miptree_copy_teximage (brw=0x55e9f1a066a0,
intelImage=0x7fee58075fc0, dst_mt=0x7fee5807b120)
at ../src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1438
#2 0x7fee6bd280e6 in intel_finalize_mipmap_tree (brw=0x55e9f1a066a0,
tObj=0x7fee58086910)
at ../src/mesa/drivers/dri/i965/intel_tex_validate.c:179
#3 0x7fee6bd281fb in brw_validate_textures (brw=0x55e9f1a066a0) at
../src/mesa/drivers/dri/i965/intel_tex_validate.c:219
#4 0x7fee6bce3932 in brw_prepare_drawing (ctx=0x55e9f1a066a0, ib=0x0,
index_bounds_valid=true, min_index=0, max_index=3)
at ../src/mesa/drivers/dri/i965/brw_draw.c:816
#5 0x7fee6bce4496 in brw_draw_prims (ctx=0x55e9f1a066a0,
prims=0x7fee68b10480, nr_prims=1, ib=0x0, index_bounds_valid=1 '\001',
min_index=0, max_index=3, gl_xfb_obj=0x0, stream=0, indirect=0x0) at
../src/mesa/drivers/dri/i965/brw_draw.c:1148
#6 0x7fee6c0e4163 in _mesa_draw_arrays (ctx=0x55e9f1a066a0, mode=5,
start=0, count=4, numInstances=1, baseInstance=0, drawID=0)
at ../src/mesa/main/draw.c:374
#7 0x7fee6c0e48eb in _mesa_DrawArrays (mode=5, start=0, count=4) at
../src/mesa/main/draw.c:531
#8 0x7fee77148a8a in
mir::renderer::gl::Renderer::draw(mir::graphics::Renderable const&) const
(this=0x7fee58000b20, renderable=
...) at /home/alan/display_server/mir/src/renderers/gl/renderer.cpp:631
#9 0x7fee77147e13 in
mir::renderer::gl::Renderer::render(std::vector,
std::allocator > > const&) const
(this=0x7fee58000b20, renderables=std::vector of length 2, capacity 2 = {...})
at /home/alan/display_server/mir/src/renderers/gl/renderer.cpp:437
#10 0x7fee76f0c728 in
mir::compositor::DefaultDisplayBufferCompositor::composite(std::vector,
std::allocator > >&&)
(this=0x7fee5800c840, scene_elements=...)
at
/home/alan/display_server/mir/src/server/compositor/default_display_buffer_compositor.cpp:84
#11 0x7fee76f12781 in mir::compositor::CompositingFunctor::operator()()
(this=0x55e9f1b6a3a0)
at
/home/alan/display_server/mir/src/server/compositor/multi_threaded_compositor.cpp:141
#12 0x7fee76f18311 in std::__invoke_impl(std::__invoke_other,
mir::compositor::CompositingFunctor&) (__f=...) at
/usr/include/c++/7/bits/invoke.h:60
#13 0x7fee76f178b4 in
std::__invoke(mir::compositor::CompositingFunctor&)
(__fn=...)
at /usr/include/c++/7/bits/invoke.h:95
#14 0x7fee76f16ae0 in
std::reference_wrapper::operator()<>()
const (this=0x7fee68b10af0)
at /usr/include/c++/7/bits/refwrap.h:356
#15 0x7fee76f15aac in std::_Function_handler
>::_M_invoke(std::_Any_data const&) (__functor=...) at
/usr/include/c++/7/bits/std_function.h:316
#16 0x7fee76daedbc in std::function::operator()() const
(this=0x7fee68b10af0) at /usr/include/c++/7/bits/std_function.h:706
#17 0x7fee77108ed3 in (anonymous namespace)::Task::execute()
(this=0x7fee68b10af0)
at /home/alan/display_server/mir/src/server/thread/basic_thread_pool.cpp:40
#18 0x7fee7710922e in (anonymous namespace)::Worker::operator()()
(this=0x55e9f172f5d0)
at /home/alan/display_server/mir/src/server/thread/basic_thread_pool.cpp:91
#19 0x7fee7710bc51 in std::__invoke_impl(std::__invoke_other,
[Desktop-packages] [Bug 1844222] Re: Wayland session overlaid by black window when fullscreen SDL apps exits
** Summary changed: - Wayland session overlaid by black window when fullscreen scummvm exits + Wayland session overlaid by black window when fullscreen SDL apps exits ** Summary changed: - Wayland session overlaid by black window when fullscreen SDL apps exits + Wayland session overlaid by window when fullscreen SDL apps exits -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844222 Title: Wayland session overlaid by window when fullscreen SDL apps exits Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Seen on 18.04 and 19.10 In the "Ubuntu Wayland" desktop sudo apt install beneath-a-steel-sky SDL_VIDEODRIVER=wayland scummvm -f -p /usr/share/scummvm/beneath-a-steel-sky sky Press ESC a few times and Ctrl-Q to exit. Expect: session returns to normal Actual: a black rectangle covers the screen, even when switching workspaces. (I'm sure scummvm is doing something odd, but...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844222] Re: Wayland session overlaid by black window when fullscreen scummvm exits
Clarification, with neverputt the last frame overlays everything, not a black one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844222 Title: Wayland session overlaid by black window when fullscreen scummvm exits Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Seen on 18.04 and 19.10 In the "Ubuntu Wayland" desktop sudo apt install beneath-a-steel-sky SDL_VIDEODRIVER=wayland scummvm -f -p /usr/share/scummvm/beneath-a-steel-sky sky Press ESC a few times and Ctrl-Q to exit. Expect: session returns to normal Actual: a black rectangle covers the screen, even when switching workspaces. (I'm sure scummvm is doing something odd, but...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844222] Re: Wayland session overlaid by black window when fullscreen scummvm exits
I also see this behaviour with other SDL applications if fullscreened using the Wayland backend. E.g. snap install --edge mir-kiosk-neverputt mir-kiosk-neverputt I don't see the same effect on weston, sway or Mir based servers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844222 Title: Wayland session overlaid by black window when fullscreen scummvm exits Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Seen on 18.04 and 19.10 In the "Ubuntu Wayland" desktop sudo apt install beneath-a-steel-sky SDL_VIDEODRIVER=wayland scummvm -f -p /usr/share/scummvm/beneath-a-steel-sky sky Press ESC a few times and Ctrl-Q to exit. Expect: session returns to normal Actual: a black rectangle covers the screen, even when switching workspaces. (I'm sure scummvm is doing something odd, but...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844222] [NEW] Wayland session overlaid by black window when fullscreen scummvm exits
Public bug reported: Seen on 18.04 and 19.10 In the "Ubuntu Wayland" desktop sudo apt install beneath-a-steel-sky SDL_VIDEODRIVER=wayland scummvm -f -p /usr/share/scummvm/beneath-a-steel-sky sky Press ESC a few times and Ctrl-Q to exit. Expect: session returns to normal Actual: a black rectangle covers the screen, even when switching workspaces. (I'm sure scummvm is doing something odd, but...) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844222 Title: Wayland session overlaid by black window when fullscreen scummvm exits Status in gnome-shell package in Ubuntu: New Bug description: Seen on 18.04 and 19.10 In the "Ubuntu Wayland" desktop sudo apt install beneath-a-steel-sky SDL_VIDEODRIVER=wayland scummvm -f -p /usr/share/scummvm/beneath-a-steel-sky sky Press ESC a few times and Ctrl-Q to exit. Expect: session returns to normal Actual: a black rectangle covers the screen, even when switching workspaces. (I'm sure scummvm is doing something odd, but...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1118903] Re: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines)
** Changed in: canonical-devices-system-image Assignee: Stephen M. Webb (bregma) => (unassigned) ** Changed in: mir Importance: High => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1118903 Title: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines) Status in Canonical System Image: Triaged Status in Mir: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Bug description: As always, it's a critical requirement for Ubuntu to be able to render the same thing on any machine (metal or virtual), regardless of the availability of hardware acceleration. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1118903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1445543] Re: Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze
** Changed in: mir Status: Incomplete => Won't Fix ** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: gtk Assignee: Andreas Pokorny (andreas-pokorny) => (unassigned) ** Changed in: gtk+3.0 (Ubuntu) Assignee: Andreas Pokorny (andreas-pokorny) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1445543 Title: Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze Status in GTK+: New Status in Mir: Won't Fix Status in gtk+3.0 package in Ubuntu: Won't Fix Bug description: GTK apps on Mir: Input focus is unreliable and sporadic. Background windows ignore input and/or focus switches apparently randomly. Example: $ GDK_BACKEND=mir mir_demo_server --launch gnome-mahjongg Show the "Scores" - you can switch focus between this and the main window with Alt+` but doesn't respond to input. Other dialogs (e.g. "About") work fine. From the Mir side there's no obvious difference between these windows. In this example, MIR_CLIENT_INPUT_RECEIVER_REPORT=log shows the input events being correctly received on the client side. That shows most of the Mir stack is working correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1445543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666181] Re: gnome-system-monitor crashed with SIGSEGV in make_protobuf_object() from mir::client::rpc::MirProtobufRpcChannel::on_data_available()
Probably the same cause as lp:1675749 (but not marking as dup yet as need to confirm the problem isn't gtk-mir/qtubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1666181 Title: gnome-system-monitor crashed with SIGSEGV in make_protobuf_object() from mir::client::rpc::MirProtobufRpcChannel::on_data_available() Status in Mir: New Status in gnome-system-monitor package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Status in mir package in Ubuntu: New Bug description: ubuntu 17.04 unity8 deb session gnome-system-monitor crashed with SIGSEGV ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: gnome-system-monitor 3.23.90-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity8 Date: Mon Feb 20 12:29:22 2017 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2016-12-12 (69 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108) ProcCmdline: gnome-system-monitor Signal: 11 SourcePackage: gnome-system-monitor StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 Title: gnome-system-monitor crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1666181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1710789] Re: chromium does not open downloaded files
$ objdump -T /usr/lib/chromium-browser/libmirclient.so.9 | grep mir_display_config_release $ objdump -T /usr/lib/x86_64-linux-gnu/libmirclient.so.9 | grep mir_display_config_release 00072860 gDF .text 0012 MIR_CLIENT_0.21 mir_display_config_release What appears to be happening is that soffice.bin is loading a stub version of libmirclient.so.9 belonging to chromium-browser. That implies that chromium-browser has reconfigured link loading and then started an external program that needs the real libmirclient.so.9. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1710789 Title: chromium does not open downloaded files Status in chromium-browser package in Ubuntu: In Progress Bug description: I have up to date Ubuntu 17.04. Recently, Chromium stoped to open downloaded files. If i download and open doc file from chromium, in command line i see the following message: /usr/lib/libreoffice/program/soffice.bin: relocation error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: symbol mir_display_config_release, version MIR_CLIENT_0.21 not defined in file libmirclient.so.9 with link time reference If i download pdf file i see the same message with evince instead of libreoffice. It looks like more general problem, but I still can open files from these two applications or using xdg-open. I tried to work with new chromium profile, but i get the same message no matter what and files cannot be opened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1710789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1420334] Re: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows)
** Changed in: miral Milestone: 1.5 => None -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1420334 Title: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows) Status in Mir: Fix Released Status in MirAL: In Progress Status in mir package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Bug description: Mir needs a client API to allow surfaces to move themselves relatively. This is required to support full client-side decorations (bug 1398849), and also other apps like Google Chrome and Gnome Nautilus which can be dragged using part of their client areas. Later additions that are so similar I think they are part of the same bug: there need to be client APIs for "always on top" and "client initiate resize". To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1420334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
I don't think the problem description is clear that both the Mir and Unity8 compositors are affected. (It can be read as applying to the stack including Unity8.) Thanks for clarifying. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Triaged Status in Mir: Triaged Status in Nouveau Xorg driver: Unknown Status in Unity System Compositor: Triaged Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
Daniel, you are saying comment #20 states that Mir's thread-per-monitor rendering manifests the problem? (I don't have any nouveau based kit to test on.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Triaged Status in Mir: Triaged Status in Nouveau Xorg driver: Unknown Status in Unity System Compositor: Triaged Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
The nouveau isn't threadsafe and the Qt renderer uses threaded GL by default. We don't know if Mir's default renderer would also exhibit the same issue when running multimonitor. (The Mir renderer uses a thread per monitor, but this is a simpler usage pattern than Qt and may not manifest problems.) ** Changed in: mir Status: Triaged => Incomplete ** Changed in: mir Importance: High => Undecided ** Changed in: mir (Ubuntu) Status: Triaged => Incomplete ** Changed in: mir (Ubuntu) Importance: High => Undecided ** Changed in: canonical-devices-system-image Assignee: Stephen M. Webb (bregma) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Triaged Status in Mir: Incomplete Status in Nouveau Xorg driver: Unknown Status in Unity System Compositor: Triaged Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Incomplete Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8
The fix released in Mir 0.27 covers the API for only one of the three functions mentioned. ** Changed in: mir Status: Fix Released => In Progress ** Changed in: mir (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1669524 Title: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8 Status in Canonical System Image: In Progress Status in Mir: In Progress Status in MirAL: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in mir package in Ubuntu: In Progress Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: ubuntu 17.04 unity8 [unity8] Always on Top, Move and Resize doesn't work open solitaire, right click on the title bar (see attachement) and then select Always on Top. the app doesn't stay on top. same with Move and Resize, does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1420334] Re: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows)
** Changed in: miral Status: Incomplete => In Progress ** Changed in: miral Milestone: None => 1.5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1420334 Title: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows) Status in Mir: Fix Released Status in MirAL: In Progress Status in mir package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Bug description: Mir needs a client API to allow surfaces to move themselves relatively. This is required to support full client-side decorations (bug 1398849), and also other apps like Google Chrome and Gnome Nautilus which can be dragged using part of their client areas. Later additions that are so similar I think they are part of the same bug: there need to be client APIs for "always on top" and "client initiate resize". To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1420334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1701747] Re: Remove hard dependencies on libmir* in relevant packages
IMO this is a design issue in Mesa - it hard links to all the backends enabled at build time. That also means, for example that a Mir based system pulls in a bunch of X libraries. The same is true for Wayland. A runtime dependency would be more satisfactory for everyone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1701747 Title: Remove hard dependencies on libmir* in relevant packages Status in gtk+3.0 package in Ubuntu: New Status in mesa package in Ubuntu: Won't Fix Bug description: I think everyone will agree that Mir is not used by majority of users. So I don't understand why many packages have hard dependencies on libmir* packages. I don't want them in my system because I'll never user them. Make them optional, please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1701747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1625397] Re: [gtk] Focus is stuck on the save as window vs the main window
** Changed in: miral Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1625397 Title: [gtk] Focus is stuck on the save as window vs the main window Status in GTK+: Fix Released Status in MirAL: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: To reproduce: Open gedit in miral click save (the window should pop up) click back on the main window leaving the save window open type Expected: Text to appear in the main top most window Result: Text appears on the save as window behind the main window. I checked with mir_demo_server and same issue so this could be a gtk bug it self. Added by alan_g: As described in comment #5 this seems to be mostly a gtk-mir problem. (Where are they filed?) But there is a MirAL component (because even if gtk-mir was right, this problem would sill be seen). Added later by alan_g: The problem mentioned in lp:1626659 has been committed, everything left is a gtk-mir issue. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1625397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8
** Changed in: mir Assignee: (unassigned) => Alan Griffiths (alan-griffiths) ** Changed in: mir Status: Triaged => In Progress ** Also affects: miral Importance: Undecided Status: New ** Changed in: miral Status: New => Triaged ** Changed in: miral Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1669524 Title: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8 Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in MirAL: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: ubuntu 17.04 unity8 [unity8] Always on Top, Move and Resize doesn't work open solitaire, right click on the title bar (see attachement) and then select Always on Top. the app doesn't stay on top. same with Move and Resize, does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1675098] [NEW] Even when connecting to Mir soffice doesn't start without an X server
Public bug reported: Test scenario: $ apt install miral-examples $ miral-desktop (in the miral session) $ soffice Expected: soffice starts Actual: soffice hangs But curiously: $ miral-xrun soffice Seems to work, and appears to connect to Mir (not Xmir) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1675098 Title: Even when connecting to Mir soffice doesn't start without an X server Status in libreoffice package in Ubuntu: New Bug description: Test scenario: $ apt install miral-examples $ miral-desktop (in the miral session) $ soffice Expected: soffice starts Actual: soffice hangs But curiously: $ miral-xrun soffice Seems to work, and appears to connect to Mir (not Xmir) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1675098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1668467] Re: gnome-calculator, you can open the Preferences window multiple times, making the window transparent the second time
Not happening in miral-shell with the latest gtk to land in Zesty ** Changed in: miral (Ubuntu) Status: Incomplete => Invalid ** Changed in: miral Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1668467 Title: gnome-calculator, you can open the Preferences window multiple times, making the window transparent the second time Status in Canonical System Image: Confirmed Status in MirAL: Invalid Status in gtk+3.0 package in Ubuntu: Confirmed Status in miral package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: ubuntu 17.04 unity8 gnome-calculator, you can open the Preferences window many times, making the window transparent the second time (see screenshot) it doesn't work with About or Keyboard Shortcuts, only with Preferences. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1655997] Re: [gtk] Save as dialog: dropdown menu surface positioned wrong
Not happening with the latest gtk to land in zesty ** Changed in: miral Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1655997 Title: [gtk] Save as dialog: dropdown menu surface positioned wrong Status in GTK+: Fix Committed Status in MirAL: Invalid Status in gtk+3.0 package in Ubuntu: New Bug description: Running miral-shell and gedit: 1. Burger-menu -> Save As 2. Click the "Character encoding" or "Line ending" or "All files" dropdowns Bug: child surfaces are positioned incorrectly, should be under/over the widget that invoked them To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1655997/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1625846] Re: Xmir -rootless: Firefox menus pop up then close right away
Chris, although I agree with a lot of what you say, I'm not sure Xmir has all the information it needs at the right time. As mentioned in comment #11 Mir is unfocussing the one window before focussing the other. When Xmir receives the focus loss it cannot know whether the focus is moving to a related window. It may not even be any window it knows about, so it can't simply defer until receiving the focus gain event. A the "Locally Active focus model" is a thing, it meets a need. Maybe we should consider supporting it directly in Mir? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1625846 Title: Xmir -rootless: Firefox menus pop up then close right away Status in Canonical System Image: Confirmed Status in Mir: Triaged Status in MirAL: Confirmed Status in xorg-server package in Ubuntu: Triaged Bug description: To reproduce: 1) Open firefox on a rootless Xmir 2) Right click or attempt to open the menu on the top right Expected: Menu to open Result: Menu pops up then closes right away. I think this is an expected bug, but dont remember the bug# soo figure would make one here :) *NOTE*: similar cause, but different usecase to lp:1662733 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625846/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1420334] Re: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows)
** Description changed: Mir needs a client API to allow surfaces to move themselves relatively. This is required to support full client-side decorations (bug 1398849), and also other apps like Google Chrome and Gnome Nautilus which can be dragged using part of their client areas. + + Later additions that are so similar I think they are part of the same + bug: there need to be client APIs for "always on top" and "client + initiate resize". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1420334 Title: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows) Status in Mir: Incomplete Status in MirAL: Incomplete Status in xorg-server package in Ubuntu: Triaged Bug description: Mir needs a client API to allow surfaces to move themselves relatively. This is required to support full client-side decorations (bug 1398849), and also other apps like Google Chrome and Gnome Nautilus which can be dragged using part of their client areas. Later additions that are so similar I think they are part of the same bug: there need to be client APIs for "always on top" and "client initiate resize". To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1420334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1671849] [NEW] Probing backends doesn't seem to work
Public bug reported: $ sudo apt install miral-examples $ miral-app Then in the Mir-on-X session: $ unset DISPLAY $ unset GDK_BACKEND $ gedit Expect: can't connect to X, but can connect to Mir, so starts up Actual: hangs ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1671849 Title: Probing backends doesn't seem to work Status in gtk+3.0 package in Ubuntu: New Bug description: $ sudo apt install miral-examples $ miral-app Then in the Mir-on-X session: $ unset DISPLAY $ unset GDK_BACKEND $ gedit Expect: can't connect to X, but can connect to Mir, so starts up Actual: hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1671849/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1665312] Re: [unity8][gtk] wrong tooltips position
Cannot reproduce with miral-app: so probably not miral, mir or gtk ** Also affects: qtmir Importance: Undecided Status: New ** Changed in: mir Status: Confirmed => Incomplete ** Changed in: miral Status: Confirmed => Incomplete ** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: mir (Ubuntu) Status: Confirmed => Incomplete ** Changed in: miral (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1665312 Title: [unity8][gtk] wrong tooltips position Status in Canonical System Image: Confirmed Status in Mir: Incomplete Status in MirAL: Incomplete Status in QtMir: New Status in gtk+3.0 package in Ubuntu: Incomplete Status in mir package in Ubuntu: Incomplete Status in miral package in Ubuntu: Incomplete Bug description: Ubuntu 17.04 Unity8 launch some randome gtk3 apps (solitaire or terminix), hover some icons with the mouse. the tootip text possition is wrong. see attached screenshots To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1665312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1665286] Re: [unity8] A ghost (shadow only) window opens with some app windows/menus
Oh, and tiled is a Qt application, so I think gtk3+ is innocent ** No longer affects: gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1665286 Title: [unity8] A ghost (shadow only) window opens with some app windows/menus Status in Canonical System Image: Confirmed Status in Mir: Incomplete Status in MirAL: Incomplete Status in mir package in Ubuntu: Incomplete Status in miral package in Ubuntu: Incomplete Status in qtubuntu package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: ubuntu 17.04 unity8 install tiled, apt install tiled launch tiled, you'll see a transparent window opened beneath the main window called "Object Types Editor" see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1665286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1625846] Re: Xmir -rootless: Firefox menus pop up then close right away
** Description changed: To reproduce: 1) Open firefox on a rootless Xmir 2) Right click or attempt to open the menu on the top right Expected: Menu to open Result: Menu pops up then closes right away. + I think this is an expected bug, but dont remember the bug# soo figure + would make one here :) - I think this is an expected bug, but dont remember the bug# soo figure would make one here :) + *NOTE*: similar cause, but different usecase to lp:1662733 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1625846 Title: Xmir -rootless: Firefox menus pop up then close right away Status in Mir: Confirmed Status in MirAL: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: To reproduce: 1) Open firefox on a rootless Xmir 2) Right click or attempt to open the menu on the top right Expected: Menu to open Result: Menu pops up then closes right away. I think this is an expected bug, but dont remember the bug# soo figure would make one here :) *NOTE*: similar cause, but different usecase to lp:1662733 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1625846/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1668467] Re: gnome-calculator, you can open the Preferences window multiple times, making the window transparent the second time
Can reproduce in miral-app, so probably gtk-mir, miral or mir ** Tags added: gtk-mir ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: miral Status: New => Confirmed ** Changed in: miral (Ubuntu) Status: New => Confirmed ** Changed in: qtmir (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1668467 Title: gnome-calculator, you can open the Preferences window multiple times, making the window transparent the second time Status in Canonical System Image: Confirmed Status in MirAL: Confirmed Status in gtk+3.0 package in Ubuntu: New Status in miral package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: ubuntu 17.04 unity8 gnome-calculator, you can open the Preferences window many times, making the window transparent the second time (see screenshot) it doesn't work with About or Keyboard Shortcuts, only with Preferences. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1668415] Re: intermittent missing menu on calculator in u8 zesty
This seems to be gnome-calculator. So, not Xmir. Testing in miral-app (miral 1.2, Zesty with Mir 0.26.1) I don't reproduce the problem, so I think that's "Incomplete" for miral and gtk- mir until we locate the problem. ** Changed in: miral Status: New => Incomplete ** Changed in: gtk+3.0 (Ubuntu) Status: New => Incomplete ** Changed in: miral (Ubuntu) Status: New => Incomplete ** Also affects: qtmir Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1668415 Title: intermittent missing menu on calculator in u8 zesty Status in Canonical System Image: New Status in MirAL: Incomplete Status in QtMir: New Status in gtk+3.0 package in Ubuntu: Incomplete Status in miral package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: New Bug description: running daily iso of zesty, clean u8 Feb 27 build This seemed to happen about 1/2 of the time - so somehow intermittent to repro: 1) launch the calculator app from the app drawer 2) click on the concentric circles in the upper left corner expect a menu to appear, result is that sometimes it doesn't https://www.youtube.com/watch?v=-C-cPsLHc8g To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1625846] Re: Xmir -rootless: Firefox menus pop up then close right away
Incomplete for miral, we can't fix this in miral directly. The way focus works in Mir does seem odd and I'm surprised that the workarounds (ignoring focus loss) in the Qt and Gtk toolkits are "good enough". When we have a plan, then will reassess how miral is affected. ** Changed in: miral Status: New => Incomplete ** Changed in: mir Status: New => Triaged ** Changed in: mir Status: Triaged => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1625846 Title: Xmir -rootless: Firefox menus pop up then close right away Status in Mir: Confirmed Status in MirAL: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: To reproduce: 1) Open firefox on a rootless Xmir 2) Right click or attempt to open the menu on the top right Expected: Menu to open Result: Menu pops up then closes right away. I think this is an expected bug, but dont remember the bug# soo figure would make one here :) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1625846/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1625846] Re: Xmir -rootless: Firefox menus pop up then close right away
It seems that Daniel's analysis is correct. With Mir a newly opened menu surface gets focus. This takes place in msh::AbstractShell::set_focus_to_locked() and the sequence is: /1/ reconfigure the existing focus window to mir_window_focus_state_unfocused /2/ reconfigure the new window to mir_window_focus_state_focused Unfortunately, when it receive the notification for /1/ firefox (or Xterm) reacts by closing the window. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1625846 Title: Xmir -rootless: Firefox menus pop up then close right away Status in Mir: New Status in MirAL: New Status in xorg-server package in Ubuntu: Triaged Bug description: To reproduce: 1) Open firefox on a rootless Xmir 2) Right click or attempt to open the menu on the top right Expected: Menu to open Result: Menu pops up then closes right away. I think this is an expected bug, but dont remember the bug# soo figure would make one here :) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1625846/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1625846] Re: Xmir -rootless: Firefox menus pop up then close right away
I briefly wondered if this were related to lp:1660691 - but empirically
not:
$ miral-xrun firefox
creates (and immediately destroys a menu)...
[2017-02-14 09:21:08.828425] miral::Window Management: place_new_window
app_info={application=XMIR, windows={Merge into trunk : miral-toolkit-dev :
Code : MirAL - Mozilla Firefox}}, requested_specification={name=Firefox,
type=menu, top_left=(737, 71), size=(326, 512), output_id=0, state=restored,
aux_rect=((605, 59), (0, 0)), placement_hints=3, window_placement_gravity=5,
aux_rect_placement_gravity=6, parent=Merge into trunk : miral-toolkit-dev :
Code : MirAL - Mozilla Firefox} -> {name=Firefox, type=menu, top_left=(737,
71), size=(326, 512), output_id=0, state=restored, aux_rect=((605, 59), (0,
0)), placement_hints=3, window_placement_gravity=5,
aux_rect_placement_gravity=6, parent=Merge into trunk : miral-toolkit-dev :
Code : MirAL - Mozilla Firefox}
...
[2017-02-14 09:21:09.094497] miral::Window Management: advise_focus_lost
window_info={name=Merge into trunk : miral-toolkit-dev : Code : MirAL - Mozilla
Firefox, type=normal, state=restored, restore_rect=((132, 12), (936, 800)),
children={0x7f1238006520, Firefox}, min_width=0, min_height=0,
max_width=2147483647, max_height=2147483647, width_inc=1, height_inc=1,
min_aspect={0, 4294967295}, max_aspect={4294967295, 0},
preferred_orientation=15, confine_pointer=0, output_id=0}
[2017-02-14 09:21:09.094525] miral::Window Management: advise_focus_gained
window_info={name=Firefox, type=menu, state=restored, restore_rect=((737, 71),
(326, 512)), parent=Merge into trunk : miral-toolkit-dev : Code : MirAL -
Mozilla Firefox, children={}, min_width=0, min_height=0, max_width=2147483647,
max_height=2147483647, width_inc=1, height_inc=1, min_aspect={0, 4294967295},
max_aspect={4294967295, 0}, preferred_orientation=15, confine_pointer=0,
output_id=0}
[2017-02-14 09:21:09.094535] miral::Window Management: raise_tree root=Firefox
[2017-02-14 09:21:09.094548] miral::Window Management: advise_raise
window_info={Merge into trunk : miral-toolkit-dev : Code : MirAL - Mozilla
Firefox, 0x7f1238006520, Firefox}
[2017-02-14 09:21:09.094564] miral::Window Management: advise_raise
window_info={Firefox}
[2017-02-14 09:21:09.094574] miral::Window Management: select_active_window
hint=Firefox -> Firefox
[2017-02-14 09:21:09.094579] miral::Window Management:
...
[2017-02-14 09:21:09.133042] miral::Window Management: advise_delete_window
window_info={name=Firefox, type=menu, state=restored, restore_rect=((737, 71),
(326, 512)), parent=Merge into trunk : miral-toolkit-dev : Code : MirAL -
Mozilla Firefox, children={}, min_width=0, min_height=0, max_width=2147483647,
max_height=2147483647, width_inc=1, height_inc=1, min_aspect={0, 4294967295},
max_aspect={4294967295, 0}, preferred_orientation=15, confine_pointer=0,
output_id=0}
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1625846
Title:
Xmir -rootless: Firefox menus pop up then close right away
Status in Mir:
New
Status in MirAL:
New
Status in xorg-server package in Ubuntu:
Triaged
Bug description:
To reproduce:
1) Open firefox on a rootless Xmir
2) Right click or attempt to open the menu on the top right
Expected:
Menu to open
Result:
Menu pops up then closes right away.
I think this is an expected bug, but dont remember the bug# soo figure would
make one here :)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1625846/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1649662] Re: [regression] resizing a some apps in Unity8 makes them distorted and freeze (usually software clients)
Cannot reproduce in in miral-shell
** Changed in: miral
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1649662
Title:
[regression] resizing a some apps in Unity8 makes them distorted and
freeze (usually software clients)
Status in Canonical System Image:
Confirmed
Status in MirAL:
Invalid
Status in gtk+3.0 package in Ubuntu:
Invalid
Status in mir package in Ubuntu:
Invalid
Status in qtmir package in Ubuntu:
Confirmed
Status in unity8 package in Ubuntu:
Confirmed
Bug description:
ubuntu 17.04 unity8 + proposed and 16.04 + overlay PPA
mir 0.25
miral 0.25
unity8/zesty-proposed,now 8.15+17.04.20161207.1-0ubuntu1 amd64
[installed,automatic]
steps:
1)run gedit, nautilus, sol or whatever gtk+3 app ("ubuntu-app-launch sol" for
ex). if you are not sure how to launch a gtk3 app run
"ubuntu-app-launch-appids" first to see the appids and then "ubuntu-app-launch
"
2) resize the window (the context gets stretched in a weird way and
input doesn't work anymore)
see attached screenshot
Alternate test case:
$ mir_demo_client_progressbar 20 --desktop_file_hint=unity8
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1649662/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1625397] Re: [gtk] Focus is stuck on the save as window vs the main window
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** No longer affects: gtk -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1625397 Title: [gtk] Focus is stuck on the save as window vs the main window Status in MirAL: Triaged Status in gtk+3.0 package in Ubuntu: New Bug description: To reproduce: Open gedit in miral click save (the window should pop up) click back on the main window leaving the save window open type Expected: Text to appear in the main top most window Result: Text appears on the save as window behind the main window. I checked with mir_demo_server and same issue so this could be a gtk bug it self. Added by alan_g: As described in comment #5 this seems to be mostly a gtk-mir problem. (Where are they filed?) But there is a MirAL component (because even if gtk-mir was right, this problem would sill be seen). Added later by alan_g: The problem mentioned in lp:1626659 has been committed, everything left is a gtk-mir issue. To manage notifications about this bug go to: https://bugs.launchpad.net/miral/+bug/1625397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1445543] Re: Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze
Seems to be working with gtk 3 on zesty - so not Mir. ** Changed in: mir Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1445543 Title: Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze Status in GTK+: New Status in Mir: Invalid Status in gtk+3.0 package in Ubuntu: In Progress Bug description: GTK apps on Mir: Input focus is unreliable and sporadic. Background windows ignore input and/or focus switches apparently randomly. Example: $ GDK_BACKEND=mir mir_demo_server --launch gnome-mahjongg Show the "Scores" - you can switch focus between this and the main window with Alt+` but doesn't respond to input. Other dialogs (e.g. "About") work fine. From the Mir side there's no obvious difference between these windows. In this example, MIR_CLIENT_INPUT_RECEIVER_REPORT=log shows the input events being correctly received on the client side. That shows most of the Mir stack is working correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1445543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1627750] Re: gnome-terminal displays input in wrong window
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** No longer affects: gtk -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1627750 Title: gnome-terminal displays input in wrong window Status in MirAL: Triaged Status in gtk+3.0 package in Ubuntu: New Bug description: $ miral-server --startup gnome-terminal Go "File=>Open Terminal" to create a second window Type in the new window. Expect: typing to appear in the new window Actual: typing appears in the original window Focus *is* on the new window as can be verified by Alt-F4, which correctly closes the new window. To manage notifications about this bug go to: https://bugs.launchpad.net/miral/+bug/1627750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1639745] Re: Mir GL clients never appear at all on VirtualBox
Also affects VM (qemu/kvm) lp:1646532 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1639745 Title: Mir GL clients never appear at all on VirtualBox Status in Mir: In Progress Status in mesa package in Ubuntu: Confirmed Bug description: Mir GL clients never appear at all on VirtualBox. After digging for a while, it appears the issue is that vboxvideo does not support DRM_CAP_PRIME and so only supports GEM flink names. Sadly Mir is the opposite now: Mir only supports PRIME but not flink names. Internally some exceptions are being thrown in Mir at present, but we seem to catch and silence them all. So you never see any error messages at all. Just Mir GL clients never appear on screen in VirtualBox. For the record, Wayland supports falling back to flink names in the absence of PRIME. We should too. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1639745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1627697] Re: gnome-terminal crashes on resize
gtk seems to be fixed on 17.04 ** Changed in: miral Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1627697 Title: gnome-terminal crashes on resize Status in MirAL: Fix Released Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Yakkety, Mir-0.24, lp:miral Run gnome-terminal on a touchscreen laptop and resizing by three- finger pinch... $ miral-run gnome-terminal $ (gnome-terminal-server:4817): Gtk-WARNING **: GtkSettings Cursor Theme: Unsupported GDK backend ... (gnome-terminal-server:4817): Gdk-WARNING **: unknown property gtk-fontconfig-timestamp (gnome-terminal-server:4817): Gdk-WARNING **: Ignoring unknown Mir event 11 (gnome-terminal-server:4817): Gtk-WARNING **: Allocating size to GtkBox 0x55eb906c6900 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? *** Error in `/usr/lib/gnome-terminal/gnome-terminal-server': double free or corruption (out): 0x7f2e70258010 *** (Can't reproduce with Mir-0.1, but that may be because resize was too broken.) To manage notifications about this bug go to: https://bugs.launchpad.net/miral/+bug/1627697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1627697] Re: gnome-terminal crashes on resize
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk Importance: Undecided Status: New ** No longer affects: miral ** No longer affects: gtk+3.0 (Ubuntu) ** Also affects: miral Importance: Undecided Status: New ** Changed in: miral Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1627697 Title: gnome-terminal crashes on resize Status in GTK+: New Status in MirAL: Fix Committed Bug description: Yakkety, Mir-0.24, lp:miral Run gnome-terminal on a touchscreen laptop and resizing by three- finger pinch... $ miral-run gnome-terminal $ (gnome-terminal-server:4817): Gtk-WARNING **: GtkSettings Cursor Theme: Unsupported GDK backend ... (gnome-terminal-server:4817): Gdk-WARNING **: unknown property gtk-fontconfig-timestamp (gnome-terminal-server:4817): Gdk-WARNING **: Ignoring unknown Mir event 11 (gnome-terminal-server:4817): Gtk-WARNING **: Allocating size to GtkBox 0x55eb906c6900 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? *** Error in `/usr/lib/gnome-terminal/gnome-terminal-server': double free or corruption (out): 0x7f2e70258010 *** (Can't reproduce with Mir-0.1, but that may be because resize was too broken.) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1627697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir
** Changed in: miral Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1590099 Title: Need to support pointer confinement in Mir and toolkits using Mir Status in Canonical System Image: Fix Released Status in Mir: Fix Released Status in MirAL: Fix Released Status in libsdl2 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Bug description: We need to support pointer confinement set by the client. This way we can generate relative mouse events on a surface without the cursor being able to leave the edge of the window. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590099/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir
** Changed in: miral Milestone: None => 0.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1590099 Title: Need to support pointer confinement in Mir and toolkits using Mir Status in Canonical System Image: Fix Released Status in Mir: Fix Released Status in MirAL: Fix Committed Status in libsdl2 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Bug description: We need to support pointer confinement set by the client. This way we can generate relative mouse events on a surface without the cursor being able to leave the edge of the window. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590099/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1420334] Re: [enhancement] Missing client API for relative surface movement
I think the right way forward is to allow the client to request drag (similar to the existing mir_surface_raise() request). William, can you confirm this could work for you? ** Changed in: mir Status: In Progress => Incomplete ** Changed in: miral Status: In Progress => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1420334 Title: [enhancement] Missing client API for relative surface movement Status in Mir: Incomplete Status in MirAL: Incomplete Status in xorg-server package in Ubuntu: Triaged Bug description: Mir needs a client API to allow surfaces to move themselves relatively. This is required to support full client-side decorations (bug 1398849), and also other apps like Google Chrome and Gnome Nautilus which can be dragged using part of their client areas. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1420334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir
** Branch linked: lp:~alan-griffiths/miral/confine_pointer ** Changed in: miral Status: In Progress => Fix Committed ** Changed in: miral Assignee: Daniel d'Andrada (dandrader) => Alan Griffiths (alan-griffiths) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1590099 Title: Need to support pointer confinement in Mir and toolkits using Mir Status in Canonical System Image: Fix Released Status in Mir: Fix Released Status in MirAL: Fix Committed Status in libsdl2 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Triaged Bug description: We need to support pointer confinement set by the client. This way we can generate relative mouse events on a surface without the cursor being able to leave the edge of the window. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590099/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1590099] Re: Need to support pointer confinement in Mir and toolkits using Mir
** Changed in: miral Assignee: (unassigned) => Daniel d'Andrada (dandrader) ** Changed in: miral Status: Triaged => In Progress ** Branch linked: lp:~dandrader/miral/confine_pointer ** Changed in: miral Importance: Wishlist => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1590099 Title: Need to support pointer confinement in Mir and toolkits using Mir Status in Canonical System Image: Fix Released Status in Mir: Fix Released Status in MirAL: In Progress Status in libsdl2 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Triaged Bug description: We need to support pointer confinement set by the client. This way we can generate relative mouse events on a surface without the cursor being able to leave the edge of the window. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590099/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1420334] Re: [enhancement] Missing client API for relative surface movement
** Branch linked: lp:~alan-griffiths/miral/connect- gdk_window_move_to_rect-inspired-placement-logic-to-Mir-0.25-API ** Also affects: miral Importance: Undecided Status: New ** Changed in: miral Status: New => In Progress ** Changed in: miral Importance: Undecided => Medium ** Changed in: miral Assignee: (unassigned) => Alan Griffiths (alan-griffiths) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1420334 Title: [enhancement] Missing client API for relative surface movement Status in Mir: In Progress Status in MirAL: In Progress Status in xorg-server package in Ubuntu: Triaged Bug description: Mir needs a client API to allow surfaces to move themselves relatively. This is required to support full client-side decorations (bug 1398849), and also other apps like Google Chrome and Gnome Nautilus which can be dragged using part of their client areas. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1420334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1420334] Re: [enhancement] Missing client API for relative surface movement
** Branch linked: lp:~alan-griffiths/mir/support-gdk_window_move_to_rect ** Branch unlinked: lp:~alan-griffiths/mir/RFC-API-to-support- gdk_window_move_to_rect -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1420334 Title: [enhancement] Missing client API for relative surface movement Status in Mir: In Progress Status in xorg-server package in Ubuntu: Triaged Bug description: Mir needs a client API to allow surfaces to move themselves relatively. This is required to support full client-side decorations (bug 1398849), and also other apps like Google Chrome and Gnome Nautilus which can be dragged using part of their client areas. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1420334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1420334] Re: [enhancement] Missing client API for relative surface movement
** Changed in: mir Assignee: (unassigned) => Alan Griffiths (alan-griffiths) ** Changed in: mir Status: Triaged => In Progress ** Branch linked: lp:~alan-griffiths/mir/RFC-API-to-support- gdk_window_move_to_rect -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1420334 Title: [enhancement] Missing client API for relative surface movement Status in Mir: In Progress Status in xorg-server package in Ubuntu: Triaged Bug description: Mir needs a client API to allow surfaces to move themselves relatively. This is required to support full client-side decorations (bug 1398849), and also other apps like Google Chrome and Gnome Nautilus which can be dragged using part of their client areas. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1420334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1605074] Re: supertux2 has two mouse pointers (one should be hidden)
You can see the same thing running 7kaa on Xmir. 7kaa hides the cursor fine when run with SDL_VIDEODRIVER=mir. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1605074 Title: supertux2 has two mouse pointers (one should be hidden) Status in Mir: Invalid Status in QtMir: Invalid Status in libsdl2 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: 2 mouse pointers (one should be hidden) i've seen this in a lot (all?) the games on mir or Xmir see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1605074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1420334] Re: [enhancement] Missing client API for relative surface movement
How much of this need is addressed by mir_surface_spec_set_streams() et alia? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1420334 Title: [enhancement] Missing client API for relative surface movement Status in Mir: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: Mir needs a client API to allow surfaces to move themselves relatively. This is required to support full client-side decorations (bug 1398849), and also other apps like Google Chrome and Gnome Nautilus which can be dragged using part of their client areas. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1420334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1571556] Re: Some GTK windows lose interaction
MIR_CLIENT_INPUT_RECEIVER_REPORT=log shows the input events being correctly received on the client side. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: mir Status: New => Invalid ** Changed in: mir Status: Invalid => Triaged ** Description changed: Easiest example: $ GDK_BACKEND=mir mir_demo_server --launch gnome-mahjongg Show the "Scores" - you can switch focus between this and the main window with Alt+` but doesn't respond to input. I've not yet investigated what's unusual about this window. Some other dialogs (e.g. "About") work fine. Also relevent to focus handling, despite being able to set focus to the main window it doesn't respond to input - with the "About" option above, closing that window enables it. With the "Scores" example it isn't possible to close the unresponsive window. - (I guess it could also be a toolkit error - i.e. creating a surface type - that doesn't expect input, but then why do we allow focus to be set as - seen by titlebar?) + Looks as though the toolkit stops responding to input events - they are + being received by the client process. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1571556 Title: Some GTK windows lose interaction Status in Mir: Triaged Status in gtk+3.0 package in Ubuntu: New Bug description: Easiest example: $ GDK_BACKEND=mir mir_demo_server --launch gnome-mahjongg Show the "Scores" - you can switch focus between this and the main window with Alt+` but doesn't respond to input. I've not yet investigated what's unusual about this window. Some other dialogs (e.g. "About") work fine. Also relevent to focus handling, despite being able to set focus to the main window it doesn't respond to input - with the "About" option above, closing that window enables it. With the "Scores" example it isn't possible to close the unresponsive window. Looks as though the toolkit stops responding to input events - they are being received by the client process. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1571556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly
Missing information to aid reproducing: 1. Are you running from a terminal, a VT or a ssh session? 1.1. AFAICS the commands as given in the instructions can only work from a terminal session, but Mir-on-X doesn't *need* "sudo", so what happens without "sudo"? 2. Are you running a local build? (the commands as given in the instructions suggest a local build) 2.1. If so, which options to cmake (e.g. is --Duse_debflags=on? Or any other optimization?) 2.2. If so, are there any "old" modules in lib/server-modules/ or lib/client-modules/ ** Changed in: mir Status: Triaged => Incomplete ** Changed in: mir/0.18 Status: Triaged => Incomplete ** Changed in: mir (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1526209 Title: [regression] Clients of nested Mir servers silently crash/exit instantly Status in Mir: Incomplete Status in Mir 0.18 series: Incomplete Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Incomplete Bug description: Clients of nested Mir servers silently crash/exit instantly (on xenial) This happens in Mir trunk lp:mir and lp:mir/0.18, but not in lp:mir/0.17 sudo bin/mir_demo_server_minimal -f /tmp/outside & sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside & sudo bin/mir_demo_client_egltriangle -m /tmp/inside And the client silently exits with return code 139. Valgrind or gdb show the problem though: ==16515== Process terminating with default action of signal 11 (SIGSEGV) ==16515== Access not within mapped region at address 0x123460A8 ==16515==at 0x6EA16E0: XGetXCBConnection (in /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0) ==16515==by 0x517AC73: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174ADE: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174B98: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5170B31: eglInitialize (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x4031A9: mir_eglapp_init (eglapp.c:350) ==16515==by 0x4024EC: main (egltriangle.c:85) #0 0x75b6e6e0 in XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 #1 0x77893c74 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #2 0x7788dadf in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #3 0x7788db99 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #4 0x77889b32 in eglInitialize () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #5 0x004031aa in mir_eglapp_init (argc=3, argv=0x7fffe548, width=0x7fffdd48, height=0x7fffdd4c) at /home/dan/bzr/mir/0.18/examples/eglapp.c:350 #6 0x004024ed in main (argc=3, argv=0x7fffe548) at /home/dan/bzr/mir/0.18/examples/egltriangle.c:85 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly
Can't reproduce on wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1526209 Title: [regression] Clients of nested Mir servers silently crash/exit instantly Status in Mir: Triaged Status in Mir 0.18 series: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Bug description: Clients of nested Mir servers silently crash/exit instantly (on xenial) This happens in Mir trunk lp:mir and lp:mir/0.18, but not in lp:mir/0.17 sudo bin/mir_demo_server_minimal -f /tmp/outside & sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside & sudo bin/mir_demo_client_egltriangle -m /tmp/inside And the client silently exits with return code 139. Valgrind or gdb show the problem though: ==16515== Process terminating with default action of signal 11 (SIGSEGV) ==16515== Access not within mapped region at address 0x123460A8 ==16515==at 0x6EA16E0: XGetXCBConnection (in /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0) ==16515==by 0x517AC73: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174ADE: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174B98: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5170B31: eglInitialize (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x4031A9: mir_eglapp_init (eglapp.c:350) ==16515==by 0x4024EC: main (egltriangle.c:85) #0 0x75b6e6e0 in XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 #1 0x77893c74 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #2 0x7788dadf in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #3 0x7788db99 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #4 0x77889b32 in eglInitialize () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #5 0x004031aa in mir_eglapp_init (argc=3, argv=0x7fffe548, width=0x7fffdd48, height=0x7fffdd4c) at /home/dan/bzr/mir/0.18/examples/eglapp.c:350 #6 0x004024ed in main (argc=3, argv=0x7fffe548) at /home/dan/bzr/mir/0.18/examples/egltriangle.c:85 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly
Please clarify how to reproduce: If run from a terminal window we don't need any of the "sudo's" as we simply load up the Mir-on-X stack and connect via $DISPLAY. In any case, sudo should only be require for the host mir server when using kms (--arw-file will make the endpoint accessible to all). If running from a VT or ssh don't we need to specify a --vt to the servers? (C.f. lp:1515558) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1526209 Title: [regression] Clients of nested Mir servers silently crash/exit instantly Status in Mir: Triaged Status in Mir 0.18 series: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Bug description: Clients of nested Mir servers silently crash/exit instantly (on xenial) This happens in Mir trunk lp:mir and lp:mir/0.18, but not in lp:mir/0.17 sudo bin/mir_demo_server_minimal -f /tmp/outside & sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside & sudo bin/mir_demo_client_egltriangle -m /tmp/inside And the client silently exits with return code 139. Valgrind or gdb show the problem though: ==16515== Process terminating with default action of signal 11 (SIGSEGV) ==16515== Access not within mapped region at address 0x123460A8 ==16515==at 0x6EA16E0: XGetXCBConnection (in /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0) ==16515==by 0x517AC73: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174ADE: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174B98: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5170B31: eglInitialize (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x4031A9: mir_eglapp_init (eglapp.c:350) ==16515==by 0x4024EC: main (egltriangle.c:85) #0 0x75b6e6e0 in XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 #1 0x77893c74 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #2 0x7788dadf in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #3 0x7788db99 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #4 0x77889b32 in eglInitialize () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #5 0x004031aa in mir_eglapp_init (argc=3, argv=0x7fffe548, width=0x7fffdd48, height=0x7fffdd4c) at /home/dan/bzr/mir/0.18/examples/eglapp.c:350 #6 0x004024ed in main (argc=3, argv=0x7fffe548) at /home/dan/bzr/mir/0.18/examples/egltriangle.c:85 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1517615] Re: Need to disable "--enable-hardware-cursor=true" option in unity-system-compositor
The USC code isn't the clearest: "--enable-hardware-cursor" is an option to enable the default Mir cursor and defaults to disabling it. If Mir isn't hiding the cursor correctly that's a separate issue that ought to be addressed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1517615 Title: Need to disable "--enable-hardware-cursor=true" option in unity- system-compositor Status in lightdm package in Ubuntu: Confirmed Status in lightdm source package in Vivid: Confirmed Bug description: Recently, Unity 8 provides its own cursor, so we no longer need the "--enable-hardware-cursor=true" option in unity-system-compositor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1517615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1503450] Re: mesa FTBFS due to missing Requires in mirclient
** Branch linked: lp:~alan-griffiths/mir/fix-1503450
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1503450
Title:
mesa FTBFS due to missing Requires in mirclient
Status in Mir:
In Progress
Status in mesa package in Ubuntu:
Fix Committed
Bug description:
mesa currently FTBFS due to a missing mirclient dependency during
build time.
Failed build at
https://launchpad.net/ubuntu/+source/mesa/11.0.2-1ubuntu2/+build/8082519
Build log:
===
/bin/bash ../../libtool --tag=CC --mode=compile gcc
-DPACKAGE_NAME=\"Mesa\" -DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"11.0.2\"
-DPACKAGE_STRING=\"Mesa\ 11.0.2\"
-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\;
-DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"11.0.2\" -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1
-DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1
-DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1
-DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1
-DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1
-DHAVE_FUNC_ATTRIBUTE_CONST=1 -DHAVE_FUNC_ATTRIBUTE_FLATTEN=1
-DHAVE_FUNC_ATTRIBUTE_FORMAT=1 -DHAVE_FUNC_ATTRIBUTE_MALLOC=1
-DHAVE_FUNC_ATTRIBUTE_PACKED=
1 -DHAVE_FUNC_ATTRIBUTE_PURE=1 -DHAVE_FUNC_ATTRIBUTE_UNUSED=1
-DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT=1 -DHAVE_DLADDR=1
-DHAVE_CLOCK_GETTIME=1 -DHAVE_PTHREAD=1 -I. -I../../../../src/egl
-D_FORTIFY_SOURCE=2 -I../../../../include -I../../../../src/egl/main
-I../../../../src/gbm/main -I../../../../src -D__STDC_LIMIT_MACROS
-D_GNU_SOURCE -DUSE_SSE41 -DNDEBUG -DTEXTURE_FLOAT_ENABLED -DUSE_X86_64_ASM
-DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF -DHAVE_MKOSTEMP
-DHAVE_DLOPEN -DHAVE_POSIX_MEMALIGN -DHAVE_LIBDRM -DGLX_USE_DRM -DHAVE_LIBUDEV
-DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DGLX_USE_TLS -DHAVE_ALIAS
-DHAVE_DRI3 -DHAVE_MINCORE -DHAVE_LLVM=0x0306 -DMESA_LLVM_VERSION_PATCH=2
-fvisibility=hidden -I/usr/include/libdrm
-D_EGL_NATIVE_PLATFORM=_EGL_PLATFORM_X11 -DHAVE_X11_PLATFORM
-DHAVE_WAYLAND_PLATFORM -DHAVE_DRM_PLATFORM -DHAVE_MIR_PLATFORM
-I/usr/include/mirplatform -I/usr/include/mircommon -I../../../../src/loader
-I../../../../src/egl/drivers/dri2 -I../../../../sr
c/gbm/backends/dri -I../../../../src/egl/wayland/wayland-egl
-I../../../../src/egl/wayland/wayland-drm -I../../src/egl/wayland/wayland-drm
-DDEFAULT_DRIVER_DIR=\"/usr/lib/x86_64-linux-gnu/dri:\${ORIGIN}/dri:/usr/lib/dri\"
-D_EGL_BUILT_IN_DRIVER_DRI2 -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall -Wall -std=c99
-Werror=implicit-function-declaration -Werror=missing-prototypes
-fno-strict-aliasing -fno-math-errno -fno-trapping-math -fno-builtin-memcmp
-MT main/eglfallbacks.lo -MD -MP -MF $depbase.Tpo -c -o main/eglfallbacks.lo
../../../../src/egl/main/eglfallbacks.c &&\
In file included from ../../../../src/egl/main/egldisplay.c:61:0:
/usr/include/mirplatform/mir_toolkit/mesa/native_display.h:22:38: fatal
error: mir_toolkit/client_types.h: No such file or directory
compilation terminated.
make[3]: *** [main/egldisplay.lo] Error 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1503450/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1289072] Re: Nested servers need cursor support
** Branch linked: lp:~alan-griffiths/mir/fix-1308133 ** Branch linked: lp:~alan-griffiths/mir/fix-1496849 ** Branch linked: lp:~alan-griffiths/mir/first-test-for-cursors-in- nested ** Branch linked: lp:~alan-griffiths/mir/second-test-for-cursors-in- nested -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1289072 Title: Nested servers need cursor support Status in Light Display Manager: Fix Released Status in Mir: In Progress Status in unity-mir: Invalid Status in Unity System Compositor: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in unity-system-compositor package in Ubuntu: Fix Released Status in unity8-desktop-session package in Ubuntu: In Progress Bug description: Nested servers lack functional cursor support. The code just returns a null pointer. One of the symptoms of this is that it is not possible to use a mouse or trackpad when running Unity8 as the desktop shell. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1289072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1289072] Re: Nested servers need cursor support
I'm not sure at what point things landed in Mir, but there seems to be support for cursors in nested servers currently. (It's been broken, but recent commits have improved it.) What is still lacking is acceptance tests of this support. ** Changed in: mir Status: Incomplete => In Progress ** Changed in: mir Assignee: (unassigned) => Alan Griffiths (alan-griffiths) ** Changed in: mir Milestone: None => 0.17.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1289072 Title: Nested servers need cursor support Status in Light Display Manager: Fix Released Status in Mir: In Progress Status in unity-mir: Invalid Status in Unity System Compositor: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in unity-system-compositor package in Ubuntu: Fix Released Status in unity8-desktop-session package in Ubuntu: In Progress Bug description: Nested servers lack functional cursor support. The code just returns a null pointer. One of the symptoms of this is that it is not possible to use a mouse or trackpad when running Unity8 as the desktop shell. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1289072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417581] Re: USC - mouse cursor on AMD graphics is drawing incorrectly
** Changed in: mir Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1417581 Title: USC - mouse cursor on AMD graphics is drawing incorrectly Status in Mir: Fix Released Status in Mir 0.12 series: Fix Released Status in mesa package in Ubuntu: New Status in mir package in Ubuntu: Fix Released Bug description: I've a Lenovo Flex 2 14D, which has an AMD APU. In Unity-System-Compositor, the mouse cursor does not draw correctly. See previous version of this bug for visuals: https://bugs.launchpad.net/mir/+bug/1391975 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1417581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1102960] Re: dia crashes on startup
Workaround in #7 worked for me. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dia in Ubuntu. https://bugs.launchpad.net/bugs/1102960 Title: dia crashes on startup Status in Dia - Diagram Tool: Confirmed Status in “dia” package in Ubuntu: Confirmed Bug description: $ dia sys:1: Warning: attempting to add an interface (DiaInteractiveRendererInterface) to class (DiaGdkRenderer) after class_init ** (dia-normal:11678): CRITICAL **: dia_renderer_set_size: assertion `irenderer != NULL' failed ** (dia-normal:11678): CRITICAL **: dia_renderer_set_size: assertion `irenderer != NULL' failed Segmentation fault (core dumped) $ file core.11678 core.11678: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), SVR4-style, from 'dia-normal --integrated' $ gdb `which dia-normal` core.* GNU gdb (GDB) 7.5-ubuntu Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i686-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/dia-normal...(no debugging symbols found)...done. [New LWP 11678] [New LWP 11680] [New LWP 11679] [New LWP 11681] [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. Core was generated by `dia-normal --integrated'. Program terminated with signal 11, Segmentation fault. #0 0x08072d03 in ?? () (gdb) bt #0 0x08072d03 in ?? () #1 0xb6e2bab0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb6e2e973 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb6e2ed10 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb6e2f1eb in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb733a5c0 in gtk_main () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 #6 0x0805d1a5 in main () (gdb) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: dia 0.97.2-8 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu2 Architecture: i386 Date: Tue Jan 22 11:58:58 2013 InstallationDate: Installed on 2010-10-21 (824 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_CA.UTF8 SHELL=/bin/bash SourcePackage: dia UpgradeStatus: Upgraded to raring on 2012-12-20 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dia/+bug/1102960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
