One main difference between x11 and wayland is that in x11 all applications receive all input whereas in wayland the compositor receives input and decides which application may receive it.
This causes a major issue with application which need input grab for running or showing a nested desktop. This affects e.g. GUI virtual machines (SPICE clients), RDP clients, VNC clients, nested kwin/gnome-shell/whatever. See also: https://bugzilla.redhat.com/show_bug.cgi?id=1285770 . Games might also be affected, I don't know.
I'm posting this here to raise attention because
1. to fix this we need another protocol (extension)
2. this issue can't be fixed in a single application, it needs the whole stack (wayland library, compositors, affected applications) to change
Compared to the other bugs in "WaylandRelated" lists [1] [2], these bugs need architecture design, not just fixing bugs in one package.
I don't know whether this mailing list is the right place to discuss an issue like this. If you know better, please tell me.
[1] https://bugzilla.redhat.com/showdependencytree.cgi?id=1277927&hide_resolv...
[2] https://bugzilla.gnome.org/showdependencytree.cgi?id=757579&hide_resolved=1

Hi folks, due to travel and various obstacles, we're not able to host a recorded demo this month. Instead we've put together a status report that includes some additional highlights we think you might be interested in. If you have feedback and/or think this works well, I'd love to know b/c I think this vehicle covers more information than a demo alone so I might do both in the future if it's worth it.
Apologies for missing the actual show and tell - if there's anything you'd like to see specifically, I'm sure we can arrange something.
https://fedoraproject.org/wiki/ReleaseEngineering/StatusReport#13SEP2016
--
Amanda Carter

Hi,
Currently we have coredumpctl installed by default, but it doesn't work
because core dumps are consumed by ABRT instead. I'd like to get
coredumpctl working out-of-the-box. We can do this by changing our
systemd presets [1] to disable abrt-ccpp.service.
ABRT will continue to function thanks to the ABRT developers' work on
coredumpctl integration via abrt-vmcore.service. There is a somewhat-
reduced feature set, but I've been running this for several months
happily and I haven't noticed any issues; my crashes are being reported
to FAF, and I can manually report to Bugzilla. See [2] for details.
This might be slightly controversial for two reasons. First, the big
change here is that core dumps will appear in the magical and super-
awesome coredumpctl tool in addition to ABRT, but would no longer be
created in the cwd when ulimit is set appropriately (we would need to
feature that in the release notes). This aligns us with upstream
systemd behavior, but diverges from Debian and Ubuntu, which still
create the old-style coredumps in the cwd. Second, my understanding is
that the ABRT developers prefer to improve abrt-cli and tell people to
use that rather than coredumpctl. But as coredumpctl is very mature
(nicer) and cross-distro so it gets many more contributors, I
definitely prefer to instruct people to use coredumpctl instead for
C/C++ crashes.
We could totally do this change for F24 as well as it should be just a
one-line change, but in the spirit of beta freeze I figure it's
probably best left for F25.
Michael
[1] https://pagure.io/fedora-release/blob/master/f/90-default.preset
[2] https://github.com/abrt/abrt/issues/1108

Hi folks! It seems like a sensible idea to hold a Wayland Test Day for
Fedora 25, with the switch to using it by default for Workstation. I've
opened a Test Day ticket in QA trac:
https://fedorahosted.org/fedora-qa/ticket/492
it'd be great to get feedback on the date - ideally it'd be great to
have some devs around, so please, if you're one of the main
upstream/downstream devs/maintainers give your feedback on the proposed
date, 2016-10-06 - and it'd also be great to have ideas for what stuff
we should test outside of the standard desktop validation tests:
https://fedoraproject.org/wiki/Category:Desktop_Acceptance_Test_Cases
Thanks everyone!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

Hey folks! Wanted to send a heads-up that I've made some fairly
significant changes to the wiki regarding writing Fedora to USB.
I've done (yet another) revision of the main wiki instructions for
writing USB sticks:
https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB
since the Fedora Media Writer tool - the rewrite (of the rewrite?) of
LiveUSB Creator - now looks to be working well in testing, and is
available on all our target platforms, the page now heavily promotes it
as the best tool to use in almost all cases. Some other methods have
been entirely removed - FMW should be a better choice for Windows and
macOS than the tools that were listed before.
I retained sections for:
* livecd-iso-to-disk, as it's now the only tool that supports non-
destructive write and data persistence
* gnome-disk-utility, for non-Fedora *nix without Flatpak support
* dd, for non-Fedora *nix without Flatpak or GNOME and people who just
like dd
* unetbootin, because the section basically exists to explicitly state
that we don't support it (maybe we should add a similar section for
Rufus...)
Please do tell me about any problems you note, or if you think I
removed something wrongly, or anything. Note that as of right now the
best version of mediawriter for F23 and F24 is in updates-testing, so I
had the instructions to install it include `--enablerepo=updates-
testing`; I'm expecting the updates will go stable soon and we can
remove that.
For validation testing folks, I have also revised the USB validation
test cases. I really kinda hated the way the Installation matrix was
set up with test names that didn't match the test case page names for
no good reason, and also didn't think we really needed all the
different test cases, so I've consolidated them into three
consistently-named test cases with more result columns:
https://fedoraproject.org/wiki/QA:Testcase_USB_ddhttps://fedoraproject.org/wiki/QA:Testcase_USB_fmwhttps://fedoraproject.org/wiki/QA:Testcase_USB_litd
The effect is pretty much the same as before - except that we now
include the FMW test instead of the LiveUSB Creator test - we test all
three methods for both BIOS and UEFI and for both live and DVD images,
but it's just arranged a little differently (and, I hope, better). I
combined the separate 'live' and 'dvd' versions of the dd and litd test
cases (which were barely different at all) into single test cases, and
consolidated common wording between all the test cases using templates.
I've put this change live on the current Installation validation page -
https://fedoraproject.org/wiki/Test_Results:Fedora_25_Branched_20160930.n...
again, please let me know of any problems you see with this change :)
Thanks everyone!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

Hi Workstation WG,
I would like to request review of the WG deliverables for Fedora 25
release. The list of deliverables is available on wiki:
https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/...
Please let me know, or edit the wiki page, in case there are missing
deliverables or the current ones have wrong blocking status.
There is going to be overall review done by FESCo, probably on
2016-Sep-30 for all the blocking deliverables.
Thanks and Best Regards,
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic