Jiri found this review (among many) of Fedora 25:
It includes a couple recommendations:
* We should restore systemd-readahead to speed boot time by ~30% for
users without SSDs. Endless has a downstream patch for this. Or we
could use Ubuntu's readahead utility.
* We should switch from CFQ to deadline I/O scheduler (which Ubuntu
has been using for years) for subjective massive responsiveness
improvements when the system is under load
Of these, the later seems easier to change and more important. Anyone
know why we're still using CFQ? If the answer is "it's better for
servers" then perhaps we need a mechanism to adjust this on a per-
Just wanted to put these issues back on the radar....
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  , 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.
Hey there, I thought that I had posted about this earlier but the thread doesn't seem to be showing up anywhere so I'm going to put it out here again (apologies if this is coming up for a second time for some of you!). I'm with the Design Team and I've been working on a redesign for the Anaconda install banners and was hoping to get some input about the content/ functionality of what I've got after doing a couple of different iterations based on the design team feedback. I'm attaching a link to the design team ticket for this project so that you can see the progression of the banner. The latest version is the last one posted. If you have any ideas/ comments/ or other feedback feel free to email me at mshaksho(a)redhat.com, comment here, do leave comments right in the design team ticket! Thanks!
Hi Desktop/Workstation team,
as we are moving forward with Fedora 26 I would like to make sure we
have all the deliverables, which might or might not be blocking for
the release, identified on time. As such, I would like to ask you to
review the list of deliverables the Desktop/Workstation team delivers
for Fedora 26 release. The list is available on
In case you find any discrepancy in the list, feel free to correct it
or let me know and I will correct it then.
Thanks for your help and Best Regards,
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
A reminder that we have a Workstation WG early morning on Monday. This
seems like kinda bad timing, since it's a holiday in the US. But it
would be good to make an effort to sign in to IRC for an hour anyway,
since the last meeting was six weeks ago and we probably don't want to
go eight weeks between meetings. I'd like to discuss an ongoing issue
with SELinux blocking our coredumpctl feature.
**NOTE** We will move our meeting to 9:00am US Eastern time (that's
1400 UTC) Monday, 2016-Dec-05.
Below are current agenda items I know about. Corrections and
additions are welcome; please send them by Sunday evening. In the
future I plan to get this agenda out on Wednesday evening before the
meeting, with agenda items due by Friday night.
* Branding -- cschaller
* Christian was to have a proposal ready to walk the WG through and
start gathering input. Does this exist yet on the wiki?
* coredumpctl -- mcatanzaro
* Michael did a Change page for F26. Let's make sure we know what
the next steps are so it gets picked up by the wrangler/FESCo, and
plan developer contact as needed.
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com