** Changed in: miral
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1420334
Title:
[enhancement] Missing client API for relative surface movement (
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 Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/186606
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
** 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 Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bug
** Changed in: miral
Milestone: 1.5 => None
--
You received this bug notification because you are a member of Ubuntu-X,
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.
draggi
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 Ubuntu-X,
which is subscribed to mesa in Ubunt
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 Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/b
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: miral
Status: Incomplete => In Progress
** Changed in: miral
Milestone: None => 1.5
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1420334
Title:
[enhancement]
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
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 rela
** 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.
+
+ Late
** 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
+
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
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_windo
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 :
Also affects VM (qemu/kvm) lp:1646532
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1639745
Title:
Mir GL clients never appear at all on VirtualBox
To manage notifications about this bug go to
** Changed in: miral
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1590099
Title:
Need to support pointer confinement in Mir and toolkits usi
** Changed in: miral
Milestone: None => 0.2
--
You received this bug notification because you are a member of Ubuntu-X,
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
To manage
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
** 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
** 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
** 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 =>
** 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 Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https
** 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 mem
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 Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1605074
Title:
supertux2 has
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 Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1420334
Title:
[enhancement] Missing client API for relative s
"Cancelled" would appear to be a behaviour that is "out there" - so
adding it to libinput & Mir is a natural solution.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1547864
Title:
libinput
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?
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).
Can't reproduce on wily
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1526209
Title:
[regression] Clients of nested Mir servers silently crash/exit
instantly
To manage notifications about th
** Branch linked: lp:~alan-griffiths/mir/fix-1503450
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1503450
Title:
mesa FTBFS due to missing Requires in mirclient
To manage notifications about
** Changed in: mir
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1417581
Title:
USC - mouse cursor on AMD graphics is drawing incorrectly
To manage
33 matches
Mail list logo
