Tag Archives: Fedora


Here is the first preview of KDE’s Plasma Next

The KDE community is working hard on the next major release of KDE software, most notably Framework 5 and Plasma Next. While Arch users can already play with KDE Framework 5 packages via extra repository and also run some components of Plasma Next via kde-unstable repo (which already has KWin), rest of those who can’t get Arch to work (though we have a very user-friendly tutorial), they can get a preview of Plasma Next using the live image of Fedora.

Daniel Vrátil, a Red Hat developer, says
, “First, our Copr repository with KDE Frameworks has been updated to 4.99.0 release, so go get it! All frameworks are co-installable with KDE 4, so you can develop against KF5 without needing any special setup. Also KDE Frameworks 5 were approved as feature for Fedora 21, which means that in next Fedora release, we will ship all Frameworks in the Fedora repositories! There are already some packages imported into rawhide, the rest will follow in next weeks.”

So what all will you get to see? Daniel says they “packaged as much as we could (but still not everything!), including Rekonq, Dolphin, System Settings, Baloo, Milou and more – all built against Qt 5 and KDE Frameworks 5 of course.”

He are some screenshots of Plasma Next running in VM on my system:

[gss ids=”27602,27603,27604,27605,27606″]

If you want to test Plasma Next, download the live iso of Fedora from the link below.

[epiclink link = ‘http://dvratil.fedorapeople.org/kde5/iso/’ color = ‘btn’ target = ‘_blank’ shorticon = ‘left’ itype = ‘ icon-download-alt’ icol = ‘black’ ]Fedora Plasma Next Preview[/epiclink]

Fedora Project Leader Quits

Robyn Bergeron, project lead of The Fedora Project for over two years had decided to step down from the role. As noted in her blog, she thanked all people associated with the project and said she is “much obliged” to others for the experience she had working with Fedora till date.

Robyn worked as a program manager for Fedora before, and wore multiple hats like marketing team leader, Cloud SIG wrangler and rest as noted in her Wiki page. She blogged regarding her experience:

“Being in this role certainly is humbling and daunting at times, and amazingly gratifying at others, but it has also afforded me an almost overwhelming opportunity to learn about anything and everything going on in open source outside the Fedora universe, with the hopes of bringing those people, projects, and ideas into our folds. Some of it is incredibly interesting, and some of it brings incredibly creative thinking into solving problems that we face in the technology space today — and, like those before me, it has also led me inevitably into exploring new opportunities.”

She thinks that its the best time to step down as Fedora 20 is already released and the next version of Fedora is on the way. Fedora 21 is scheduled to release October this year. It has some exciting features which will make Fedora more ready for the cloud. Along with that, it will ship with SDDM as the default display manager instead of KDM, latest version of KDE frameworks 5 Mate desktop 1.8, Java 8 and others.


Fedora revives transparent gnome-terminals

Background transparency, which was removed after GNOME 3.6 release on Fedora 2 years back is enabled once again. There were both requests from users and workarounds to make transparency work again. On popular demand, the feature is back on Fedora 20 and GNOME 3.12 COPR. Rawhide will also have it soon.

In his blog update Debarshi Ray points out that this downstream patch from Fedora has been rejected by the upstream gnome-terminal maintainer. So non-Fedora users may need to request corresponding distribution maintainer to include it.

To have this feature on Fedora 20, update the gnome-terminal package. You can set the transparency from the Profile Preferences, Colors tab. Also note that this feature reveals a bug in the Adwaita theme – the background of the menubar is not drawn when transparency is on. However, this should get fixed soon.


Wayland changes approved for Fedora 21

Wayland on Fedora as default has been eluding us for a while now. Experimental support for Wayland was added in Fedora 20 but X11 still remained the default display server. The weekly FESCo meeting approved the Wayland Fedora 21 changes among other Fedora 21 features to continue the works on replacing X11 with Wayland.

Wayland couldn’t make it as the default on Fedora 20 as there’s still a lot to be done around the desktop infrastructure like port packages and switch APIs like gnome-settings-daemon and gnome-control-center. As a matter of fact, X.Org Server 1.16 is also expected by the time Fedora 21 is released. It will integrate basic XWaylad support to run X11 applications on Wayland without the need of any separate X.Org patches.

The main focus of Fedora 21’s Wayland support will be to address user-visible regressions and fixing limitations of GNOME on Wayland with respect to GNOME on X11. The end result will be an improved and polished GNOME Wayland session experience. If the work remains incomplete by the planned release time for Fedora 21, which is no earlier than mid October 2014, it won’t be a blocker as switching back to X is always an option. So it’s not sure that Wayland would be the default but it would surely be in better state.

A lot is being discussed on Fedora 21on the developer mailing list right now and if you are interested keep an eye on it. Currently the tentative release schedule of Fedora 21 is on track.

You can see 'Application Folders'.

Gnome 3.12 review – work Ubuntu could have benefited from

The Gnome project announced the release of version 3.12 yesterday which is a major release. Unfortunately, unlike KDE, the release is not yet available for Ubuntu, Arch Linux or openSUSE. Only way to get it is by using Fedora which, in my opinion, has really become extremely stable – except for the extremely confusing partition manager. If you want to install Gnome 3.12 on your Fedora box, you can safely use a repository created by Red Hat developer Richard Hughes. Check out instructions here.

My history with Gnome & Ubuntu

I have been a Gnome user since 2005 when I ditched Windows and started using GNU/Linux. However, things changed when Ubuntu (the OS that I was using then) chose to drop Gnome and create their own Unity. There was no safe way to use Gnome without breaking things, so I dropped Gnome and tried Unity for two releases and realized it’s not the GNU/Linux that I got fond of. The control had moved out of my hands, it was a very rigid system which could not be customized to an individual’s needs. So I started looking for an alternative and settled with openSUSE with KDE. I was really impressed with openSUSE as it was extremely easy to install KDE and Gnome side-by-side without breaking things. So, while I primarily became a KDE user (thanks to Ubunutu) I do keep GNOME just for the sake of testing it from time to time and keep an eye on development.

I have been following Gnome development from the early days and must say that post 3.8, it’s really heading in the right direction – something simple (a little inspired by Apple’s Mac OX, as usual), elegant, and just works out of the box. Gnome has become visually appealing since 3.10 and the latest version takes that experience one notch over.

Application Folders

If you are also a Mac OSX user, you will see influences of Mac’s design on Gnome – and that has been true from early days (remember the top panel?). One of the notable features of Gnome 3.12 is ‘Application Folders’. As the name states, you can keep your preferred apps together in folders for quick access. By default, there are two folders ‘Utility’ and ‘Sundry’ but you can now create more such folders so you can club all media applications in one folder, development folder in another and so on.

You can see 'Application Folders'.
You can see ‘Application Folders’.

However, it’s a bit tricky to create a new folder. Unlike Mac’s Launchpad where you can drag apps on top of each other to create a folder (the way it also happens on stock Android), in GNOME you have to do it from Software application. There is no way of doing it in ‘Activity’ mode. I wish developers will make it as easy as it is on Android/Mac so users can easily create folders and put apps as they prefer.


What to expect from GNOME 3.12

After 6 months of hard work, GNOME 3.12 will be finally unleashed tomorrow. Here is a list of what to expect from the newer release.

Videos Replacing Totem

Totem will now be called Videos (or GNOME Videos). The project will still be called Totem but user viewable name will be Videos. This is akin to renaming of Epiphany to web in 3.4 release. The “discover” menu will receive an UI overhaul. Pocket videos, Guardian Videos and Freebox TV support is enabled via grillo plug-ins.

GNOME software

GNOME software received lot for bug fixes and new feature. Screenshot are available for popular applications. Depending on how an application is integrated with desktop, user rating will be auto-generated. Users can now control and delete software sources.

Facebook Integration in Photos

You can now view Facebook photos from the Photos app.

Pocket Integration

Pocket has now been integrated within GNOME. Pocket is available in GNOME accounts and it is integrated with Videos via grillo. The integration with Web is still in works.

Windows Live Integration

It will be possible to use Windows Live (hotmail/outlook/live) emails over IMAP and SMTP using OAuth2 tokens for authentication. Windows Live Accounts are now available in gnome online accounts (GOA). Evolution will pickup Windows Live Mail via GOA.

Web (Epiphany)

Web receives new history dialog, passwords dialog, cookies dialog, page title, address UI. Other Visual improvements will be noticed in oops screen, most visited page.


Gedit receives a massive UI overhaul in this version.

These are some of stuff you will get to see in GNOME 3.12. We will be back tomorrow with the official release announcement.


Developers from Cuba, Iran, North Korea, Sudan & Syria can’t contribute to US based open source projects?

Unless they choose not to tell where they are from. To tackle the issue Fedora project has adopted the “don’t ask don’t tell” policy for contribution.

I am aware of situations where Open Source companies based out of US can’t offer free software to those countries which are in US’s embargo list, but something interesting popped out today when FESCo debated the issue whether Fedora should allow ‘contribution’ from such countries. Fedora’s sponsor Red Hat is a US based company and thus has to adhere to US laws so it’s tricky whether they can use the free software contribution from embargoed countries or not.

A ticket was created by lkundrak asking:

It has come to my attention that a sponsor suspecting contributor’s residence due to his nationality might exclude him from participating in the project. I’m wondering whether it’s encouraged, discouraged, mandatory or forbidden that sponsors try to determine contributor’s nationality and area of residence. If it’s not discouraged or forbidden, I’d like to be aware what reliable means of determining the location and nationality should we use. I’d like to find out a reliable way to find out whether a piece of third party open-source code can be included in Fedora, taking the country of origin restrictions into account.

lkundrak seek advice from FESCo to suggest “changes to contributor’s documentation so that next time we know in advance and make no mistakes.”

The issue was triggered when a developer from Sudan, named Mohammed Isam, wanted to get involved with Fedora development. Petr Šabata said that while he would love to sponsor Islam he would have to check with Fedora legal as Sudan is in the Sanctioned list. Mohammed Isam added that he doesn’t live or work from Sudan; he was based out of Quatar.

Today FESCo made a decision about it. The solution is – ‘Don’t ask, don’t tell.’ FESCo recommends that “Sponsors (or any other contributors) in Fedora should not make any effort to determine a contributor’s nationality, country of origin, or area of residence.”

But there can be cases where the nationality of the contributor is revealed then they have to ‘tell. “If a potential contributor independently (and explicitly) reveals their nationality, country of origin, or area of residence, and that nationality, country of origin, or area of residence is in one of the export restricted countries, then they are required to bring that information to the attention of Fedora Legal ”

In case of Mohammed Isam, Fedora Legal team cleared the he can contribute.

There are quite some open source projects based out of US, what will they do? We will talk to some projects and update the story.


Want to test out GNOME 3.12 on Fedora?

If you’re up for testing some exciting new features in Fedora’s GNOME 3.12 build, Richard Hughes, a UK based software hacker for GNOME, has made that possible through an early release COPR instance. Copr is a build system designed to be very lightweight, so that contributors can create packages, put them in repositories, and make it easy for users to install the packages them onto their system. The Fedora Project uses this build system to make 3rd party repositories.  Early this morning, Richard sent out a blast detailing how to do so in brief.

Caveats before testing
Please only run this on a Virtual Machine, and not a physical machine of your own, unless it is designated for testing. The release is about 99% done, but potential bugs are likely to crop up, due to the unfinished nature of the build.  The install was confirmed working on a fresh Fedora VM, but be sure to disable SELinux, as a new policy has not yet been implemented.

To disable SELinux:

  1. Click “System,” go to the “Administration” menu and select “Security Level and Firewall.” Enter the administrator password when prompted.
  2. Click the “SELinux” tab.
  3. Click “Disabled” in the SELinux settings and press “OK.”
  4. Reboot your system.

Be advised this build of GNOME 3.12 is for testing purposes only, and not meant for release just yet.  Please refrain from contacting fedora-devel or fedora on IRC for help concerning this “pre-release.”  This is meant for users familiar with adding yum repos manually themselves, not for new users of Fedora.  I’ve outlined the basic steps below, but please proceed with caution.

Brief overview
You will want to create a custom repository for this.  If you are not familar with adding custom repositories, you can read about them here.  With that understood, you can move forward.

Change directory to

cd /etc/yum.repos.d

Then create a repo file

vi rhughes-f20-gnome-3-12.rep

Paste the following lines in the file

name=Copr repo for f20-gnome-3-12 owned by rhughes (i386)

name=Copr repo for f20-gnome-3-12 owned by rhughes (x86_64)

Now, update your repositories

yum update

You should be able to grab the gnome 3.12 package at this point from the new repo.  For those interested, a list of GNOME 3.12 features can be found on the GNOME wiki.

Source: Google+


Gnome 3.12 to be delayed [not] to sync with Wayland release

Gnome developers are planning to delay the release of Gnome 3.12 by approximately a week. It’s a deliberate delay to sync the release with the availability of Wayland 1.5.

Gnome, like all other major FLOSS projects, have put their weight behind Wayland and the move will ensure that Gnome and Wayland will work together well.

Matthias Clasen explains that “the GNOME release team is pondering moving the date for 3.12.0 out by approximately a week, to align the schedule with the Wayland release plans (a 1.4.91 release including all the xdg-shell API we need is planned for April 1). The latter 3.11.x milestones would be shifted as well, to avoid lengthening the freeze period unnecessarily.”

Writing to distributors (distros) he said that if this delay affects their own release schedule they can speak up now.

Since he himself is a Fedora developer he clarifies that it won’t “cause problems for Fedora, since the f21 schedule is going to be longer than usual, anyway.”

Update(20, Feb): It will be released on schedule which is 26th of March.


Future Fedora releases to be nameless, next release in August

Fedora, like other Linux distributions, has had some colourful names. The current release is named Heisenbug while the previous two releases were named Schrödinger’s Cat and Spherical Cow. And that may be it. The Fedora board has decided that it no longer will be coming up with names for future releases, starting from Fedora 21.

Fedora releases were named based on nomination and voting. It is now up to the community to name a release if they are willing to.  Says Jaroslav Reznik of Red Hat in his blog post, “What will be the code name for Fedora 21. And again short answer: null. Not null as null string but null. Fedora Board decided to end release names process. It does not mean “no more release names” but it’s up to community or working groups, if anyone wants to step into the role of Name Wrangler and helps running this process. Or reform it in any way.”

In a related news, Fedora 21 is targeted to be released not before August this year. The gap in time between Fedora 20 and 21 is considerable given that releases happen approximately six months apart. The time between the two releases will be used to work on tooling for quality control and release automation. “But this time we are in a bit different situation – there are several working groups trying to redefine, how Fedora should look like in the future and it does not make sense to create schedule. We need resolution from this effort. It’s planned for January.”, states Jarolsav. Apart from that, we may also be looking at releases happening at different times for different products.

Source: Softpedia