file triggers in rawhide
by Matthias Clasen
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:
7 years, 3 months
Let's reconsider some more applications installed by default
by Michael Catanzaro
>From the latest revision of our PRD :
"Fedora Workstation follows the GNOME Human Interface Guidelines. These
guidelines are mandatory for applications installed by default."
Currently we have applications that clearly do not follow these
guidelines. Unless we plan to revisit this section of the PRD, we
should remove them, or set a deadline for them to be improved.
* Devassistant. Needs an app menu, plus a serious sit-down with the
GNOME designers. We want to make it easy to develop apps for Fedora,
but not at the cost of leaving a bad quality impression.
* Evolution: Needs a major redesign that is not going to happen. Geary
is not yet a suitable replacement. Options: (1) Not install any email
client, because most users will use webmail; we can feature Evolution
in GNOME Software. (2) If we want to keep Evolution installed by
default, it's time to require the maintainers to add an app menu.
* Firefox. I see two options here: (1) replace it with Epiphany (FWIW,
I think Epiphany has matured enough recently for this to be reasonable,
but I am biased ;) (2) enable the GNOME extensions, mandate that they
be updated in tandem with updates to Firefox in Fedora, and patch in an
application menu. The extensions are good, and Mozilla is a reasonable
upstream we can work with to get permission for this. The status quo
should not be an option.
* setroubleshoot. This app is completely hopeless. SELinux issues are
sufficiently rare nowadays that we simply do not need this anymore,
although it would be ideal for ABRT to detect the issues and handle bug
* Shotwell. Eventually we can replace it with GNOME Photos, but in the
meantime, users can just install a photo management app if they want
one. Also, I suspect Shotwell sends your password to Facebook without
verifying its TLS certificate....
* Transmission. Its only significant legal use is to download our
competitor's products (Linux ISOs), hardly something we need to
encourage. It's featured in GNOME Software already.
7 years, 6 months
Intel GPU error, PCH transcoder A FIFO underrun
by Alex G.S.
Every time I browse my 'journactl -b' logs I always see the following error:
[drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch
fifo underrun on pch transcoder A
[drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A
It also happens around times when I'm doing something graphically intensive
and often precedes lockups. But these lockups are rare and do not happen
often. The error message itself appears on nearly all of the Intel HD
graphics chips I've used which are both the Intel HD 4000 and Intel HD 4600.
I'm just curious as to any workarounds that could solve this in the
short-term. Of all the bug reports I've read they always end with no
resolution or "version 4.0 of the Kernel will solve this", but I'm on
Kernel 4.1+ and it's still not solved yet.
Thank you for any information you can provide...
7 years, 6 months
dual boot release criteria, secure boot exempted
by Chris Murphy
The final release criterion for Fedora 23 Windows dual boot has an
exemption that reads:
The bootloader entry part of this criterion does not apply when Secure
Boot is enabled (because it has not yet been made to work, and fixing
it is not trivial). cases.
I don't know the provenance of this exemption, but this bug explains
the problem and work around. The gist is that openSUSE has a patch to
avoid using LoadImage so that GRUB can chainload the Windows
bootloader with Secure Boot enabled, and it's been working for years.
The ideal scenario is to fix the problem with LoadImage, but I think
in the meantime it's better to have the work around rather than users
being told to disable Secure Boot.
So I'm wondering if the WG can take this up at their next meeting and
decide when this exemption should be removed.
7 years, 6 months
GNOME Shell extensions
by Michael Schwendt
How do users find Fedora's gnome-shell-extension-* packages?
They don't appear in GNOME Software, because of missing appdata files.
Is gnome-tweak-tool and its link to the the extensions web site the
only way to find more extensions? Or the only "supported" way other
than using command-line tools to search for packages?
7 years, 7 months