Hey,
I've added file triggers for a number of desktop things:
- gsettings schemas
- gio modules
- desktop files
- mime types
- gdk-pixbuf loaders
- gtk im modules
If you are updating a desktop package in rawhide that uses any of
glib-compile-schemas, gio-querymodules, update-desktop-database, update
-mime-database, gdk-pixbuf-query-loaders or gtk-query-immodules-3.0 in
its %post, %postun or %posttrans, you can simply drop those calls - the
file triggers will take care of things.
For the time being, it might be a good idea to add a dependency on a
new-enough build of the package(s) whose file triggers you are using.
Here is a representative commit:
http://pkgs.fedoraproject.org/cgit/gedit.git/commit/?id=1cd2537b862233c
c4b4b1d59a56d26224e8b5b8a
Matthias

Hi,
I spent some time with F24 comps tonight, removing a bunch of packages
from gnome-desktop that we don't ship in Workstation, and removing
GNOME packages from workstation-product, then included gnome-desktop in
workstation-product-environment. If I didn't make any mistakes then
there should be no changes to what gets installed... but if you find
something does break, please revert it or fix it or let me know.
This solves the problem of having two big lists of GNOME apps, one
unmaintained yet an inviting place to add more GNOME apps, so it should
reduce future accidents where gnome-desktop gets edited by mistake
(remember that caused us to accidentally release F21 without Maps).
Going forward, you really do want to add GNOME stuff there once again.
I didn't touch F23.
Michael

Hi,
While we haven't gotten F23 out the door yet, the time has come to plan for Fedora Workstation 24. Here is what we have so far.
This was originally written for some of our internal planning, but I thought this content could be of general interest to the community and the working group. It is basically the areas we are looking at internally at RH in terms of features to go into Fedora Workstation 24.
Hopefully publishing this will allow people in the community to align your efforts with ours. Of course these are just our plans, as it always is with such things they might slip as we get closer to the actual release.
Christian
Codecs
------------
H264 - I expect us to have sorted through our Koji changes and have this ready for F24, unless we suddenly start blocking on Cisco. Wim Taymans should start looking at getting Main support added at some point. People involved - Kalev Lember (mclasen), Wim Taymans (Kem), Kevin Fenzi (pfrields)
Hardware enablement
-------------------
Optimus Handling - Better support in the stack for Optimus systems is another item I expect us to have ready for Fedora 24. People involved: Adam Jackson (kem), Ray Strode (mclasen)
GL Dispatch, EGLstreams and EGL Device - While we would be depending on NVidia supporting this to make a practical step forward for most users I expect us to have the framework ready for Fedora 24. People involved - Adam Jackson (kem)
GPU passthrough in Boxes - I expect us to be able to land this feature in time for Fedora 24 unless we end up blocking on the QEMU/KVM team somehow. People involved - Zeeshan Ali (mclasen)
Laptop certification improvements - While not directly Fedora related I expect that we have started doing some serious work in this field by the time Fedora 24 is out and hopefully can start see some benefit coming out of it in terms of better Fedora and RHEL support on new laptop hardware. People involved - Marek Kasik ( Jiri Eischmann)
Battery life - I am expecting to see some tangible results here in time for Fedora Workstation 24. Initial discussions with HW partner underway. People involved - Josh Boyer (pfrields), Laura Abbot (pfrields), Bastien Nocera (mclasen), Owen Taylor (cschalle)
Enterprise features
-------------------
GDM/KDC proxy access - Integrate two-factor authentication into GDM. Allan Day investigating design. - Allan Day (mclasen), Ray Strode (mclasen), Alexander Bokovoy (dpal).
Improve Firefox integration and kerberos handling. Martin Stransky (jeischma), Simo Source
libsoup/gssapi integration with kerberos framework. Tomas Popela (jeischma)
Further improvements in GOA UI in relation to kerberos handling. Derbashi Ray (mclasen)
Fleet Commander - I want us to have a initial fleet commander to release alongside Fedora 24. It should support GNOME, Firefox and LibreOffice. People involved (Alberto Ruiz)
Windows RDP remoting - We should tie this into the enterprise login and make sure freerdp can use it to authenticate with the windows system. We should try to test it tested by internal IT. People involved - Ondrej Holy (dblechter), Tomas Popela (jeishma), Oliver Haesller (Internal IT)
System Polish
-----------------
GUI system upgrade - I expect us to have operating system upgrade available during the Fedora 23 lifecycle in GNOME Software, enabling people to upgrade from Fedora 23 to Fedora 24 through GNOME Software. People involved - Richard Hughes (mclasen) and Kalev Lember (mclasen).
USB Creator - ideally this should be ready in time for Fedora 23 already. With full support for Windows, Mac and Linux. People involved - Martin Briza (jeischma).
Qt integration - In theory we already got a bit of stuff ready here, but we need to do some work to ensure that major 3rd party software using Qt are using the Adwaita theme we made by default. I also hope we can land the high contrast version in time for Fedora 24. People involved - Martin Briza (jeischma).
3rd party software - I expect us to have and agreement with Matthew Miller on a final design of labeling and availability of 3rd party software in time for it to be implemented and available in Fedora 24. So that people can install major software like Chrome, Skype, Spotify, Steam, Viber and more through GNOME Software in Fedora Workstation 24. People involved - Richard Hughes (mclasen), Kalev Lember (mclasen), Matthew Miller (Fedora)
Wayland - I expect us to be shipping Wayland as default in Fedora 24. People involved (Jonas Ådahl (mclasen), Olivier Fourdan (kem) and many more.
XDG app in GNOME Software - We need to have the infrastructure ready to make XDG apps available and upgradable in GNOME Software. People involved - Richard Hughes (mclasen) and Alex Larsson (mclasen)
Developer tooling
--------------------
Screencasting - top notch screencasting tool built with Pinos - Wim Taymans (kem)
XDG App - We will have Builder ready to make the building and deployment of XDG-apps very simple for Fedora Workstation 24, targeting a CentOS derived runtime. People involved - Christian Hergert (mclasen), Alexander Larsson (mclasen), David King (mclasen)
More developer tools packages - We should look at ways to package some major developer tools as XDG app bundles like PyCharm, Visual Studio (?), MonoDevelop etc. Maybe try to work with upstream projects to make them own this. People involved - TBD.

hi all
I've just read christian's fedora workstation update article. This got
me thinking. I would like to, if possible, have by fedora 24, at least a
basic level of functioning accessibility for xdg-app compliant
applications. I'll be happy to work with upstream or fedora developers
directly and do as much work as I can to improve this. I seem to recall
some talk about this on the mailing list to the equivalent of there
needs to be some redesign of the accessibility stack to improve
accessibility. While I believe this is extremely important, I think it
is more important to get accessibility working with the apps first, and
then focus on the redesign, possibly to be ready by f25 or f26? I'm not
an accessibility developer in the sense that I write code. I am,
however, a passionate open source advocate despite my occasional rants
and my long silences as I try to juggle accessibility improvements for
all the major desktops on my own, gnome, mate, cinnamon. Michael
katanzaro and bastian nosira help me out a lot on the gnome end, but no
one else on those other desktops does so I'm left to file the bugs and
so on. i have not actually tested xdg compliant apps. Can someone with
vision attempt this with orca, magnifier, onscreen keyboard, etc? If
we're going to do this, we need to do it right so that accessibility
support is equal among the various tools.
Thanks
Kendell clark

hi all
I'm asking hear on behalf of a couple of blind and disabled users that
have been trying to get fedora and sonar working on their laptops, but
they report that as soon as the live systems boot up and they log in or
the gnome desktops load, gnome immediately presents them with this
dialog. I've seen this once or twice on my machine, and the only choice
is to log out and then log back in. I'm writing hear to see if any gnome
developers can give me some pointers as to what might be happening so I
can try to fix this in sonar, and give them instructions on how to work
around it in fedora. Most of them are using macs, which I don't own. One
person says he gets this dialog if he doesn't have a screen connected.
I'm wondering if maybe it has something to do with video card support?
The one and only mac I have access to both fedora and sonar have worked
flawlessly on, including wifi, sound and bluetooth. What causes this
dialog to show up, and are there workarounds? Thoughts?
Thanks
Kendell clark

I forgot to CC the desktop list on this email from last night. Given
kdbus was likely most active among Workstation, I wanted to be sure
people saw this.
josh
---------- Forwarded message ----------
From: Josh Boyer <jwboyer(a)fedoraproject.org>
Date: Thu, Oct 29, 2015 at 7:36 PM
Subject: kdbus module being removed from Rawhide
To: Development discussions related to Fedora
<devel(a)lists.fedoraproject.org>, Kernel Fedora
<kernel(a)lists.fedoraproject.org>
Hi All,
We will be removing the kdbus driver from Rawhide kernels before the
4.3 final release upstream. Realistically, this means kdbus will be
gone from Fedora by Monday November 2nd at the latest. If you have a
setup using kdbus, please adjust it accordingly.
The upstream developers asked me to remove the module from Fedora
while they rethink some of the approach they are taking with kdbus.
josh

Hi,
I filed this bug a while ago,
https://bugzilla.redhat.com/show_bug.cgi?id=1252839
Seems that a small change (http -> https) in the captive portal detection
configuration file broke it.
If we want captive portal detection (I think we do), this should probably
be fixed. Otherwise, we should remove
NetworkManager-config-connectivity-fedora from our default install.
--
-Elad.

hi all
This one is an odd question to ask, since I'm not a windows user.
Mellisa tells me that on her windows box she can see our belkin n300
wireless router in the network section of file explorer. I've tried to
get this working in gnome, since it would be nice to simply click on an
icon and have the browser open to my gateway's setup page instead of
having to remember an IP address. Normally I'd just bite the bullet and
remember the IP address, since it's no big deal. However, I'm going to
be getting a new router soon and sometimes the IP address varies from
192.168.2.1, 192.168.1.1 and 192.168.0.1, and others. Does anyone know
if this is possible? Nautilus seems to be fairly hardcoded in it's
network view. There's always a windows network option, even if no samba
servers are active, and there's a "tigger" option, which refers to my
computer, but I get a connection refused error when clicking on that,
but no router. I'm a novice at networking and only understand the
basics. Does anyone know how I might get this working in fedora? By the
way, fedora 23 rc6 is fantastic, great job everyone! I'll be sure to
inline quote if I get responses this time.
Thanks
Kendell clark