** 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
S
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” pac
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
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/bug
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 rectang
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
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
** 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 windo
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:
supert
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 re
** 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:
[enhan
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 Deskt
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.
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.launchp
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
** 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.
$ 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 h
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/16661
** 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
** 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
** 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 =>
** 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 d
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
** 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 s
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
** 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: mi
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
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
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 :
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
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
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
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: q
** 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
+
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
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)
Stat
** 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
St
** 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 tool
** 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/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
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
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
** 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
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
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
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
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)
I
** 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
I
** 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
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
** Descrip
** 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
** 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
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 D
; 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.launchp
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
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).
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?
** 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) =>
** 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
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
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:
** 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 mo
62 matches
Mail list logo
