GNOME 3.12 on Fedora 20

I’ve finished building the packages for GNOME 3.11.90. I’ve done this as a Fedora 20 COPR. It’s probably a really good idea to test this in a VM rather than your production systems as it’s only had a small amount of testing.

If it breaks, you get to keep all 132 pieces. It’s probably also not a good idea to be asking fedora-devel or fedoraforums for help when using these packages. If you don’t know how to install a yum repo these packages are not for you.

Comments and suggestions, welcome. Thanks.

Published by


Richard has over 10 years of experience developing open source software. He is the maintainer of GNOME Software, PackageKit, GNOME Packagekit, GNOME Power Manager, GNOME Color Manager, colord, and UPower and also contributes to many other projects and opensource standards. Richard has three main areas of interest on the free desktop, color management, package management, and power management. Richard graduated a few years ago from the University of Surrey with a Masters in Electronics Engineering. He now works for Red Hat in the desktop group, and also manages a company selling open source calibration equipment. Richard's outside interests include taking photos and eating good food.

17 thoughts on “GNOME 3.12 on Fedora 20”

  1. Thanks! One question, has fedora decided if this will be pushed throght the regular updates repo once gnome 3.12 is released or will users have to use the corp repo?

  2. Thanks Richard! Makes it much easy for me to record videos of 3.12 to show off the new features at our dear GNOME youtube channel. Will have a go at installing Fedora 20 tonight.

  3. Hi
    I have a couple of bugs. The location item in gnome-shell is not working for me. Also, for some reason the wifi icon shows a ? icon. If I restart the shell the icon is then loaded correctly.


  4. Hi

    gnome-photos is not working:
    $ gnome-photos
    error sending Activate message to application: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

  5. needed this, it sucks having to wait months to enjoy the fixes and polishes of gnome.
    I actually started looking at one the the rolling release distros to replace my fedora machine.
    gnome development is so exciting you feel dated in a month or two.
    thanks mr. Hughes

  6. Nice work packaging GNOME 3.12 up for Fedora 20!
    I just wanted to mention that gnome-software doesn’t list installed applications.
    The warning I get from stdout:

    (gnome-software:4340): Gs-WARNING **: failed to get installed apps: Error on line 14 char 7: Element ‘p’ was closed, but the currently open element is ‘P’

    Maybe updating the package to 3.11.91 fixes the problem, haven’t tried that one.

  7. Hi Richard,
    Thanks for the repo. I installed 3.11.9 from the repo and found that my machine became very slow.
    May it be the case that pre-released version is compiled in debugging mode? any idea?

  8. Hi,
    Another problem faced.
    I use skype in my 64bit machine. So, in my copr repo I have both i686 and x86_64.
    But, after installing skype, and its needed packages, I can see that yum now wants to install more i686 packages then needed:
    As, I only have:
    $rpm -qa|/usr/bin/grep NetworkManager-glib

    but an #yum update gives:
    NetworkManager-glib i686 1:
    rhughes-f20-gnome-3-12-i386 357 k
    NetworkManager-glib x86_64 1:
    rhughes-f20-gnome-3-12-x86_64 357 k

    (Though it currently fails for dependency problem in webkitgtk3)
    Any help please?

  9. Some update during the last few days seems so have broken something about permissions on both of my Fedora 20 (+this COPR) systems: sound stopped working, the UI got slow (maybe this is what rudrab is talking about above), I get asked for passwords a lot, for example on shutdown or when mounting external drives.

    By looking at glxinfo I found out that my user does not have the permission to access the DRI interface anymore, same for the sound devices. Adding the user to the groups “video” and “audio” works as a workaround.

    Still this seems to be a bug with permission handling in GNOME. Maybe something broke in GDM or gnome-session etc?

Comments are closed.