As a longtime user of Fedora's Xfce spin, naturally I'm interested.
The reasons why Xfce 4.11 is not in Fedora Rawhide (because there is no 4.12 release imminent, and 4.11 in "stable" Fedora would be bad, but there is a COPR repo for those who want it)
Rumors that Xfce, the project, is dead (It's not -- fixes and small changes continue to be committed; there's just no timetable for a 4.12 release)
The Xfce spin leaving its 700MB CD size behind and now aiming at 1 GB USB flash drive size in Fedora 22
Xfce continuing to be available for RHEL/CentOS users in EPEL
Ways of making Xfce work better on HIDPI displays (but don't expect miracles until Xfce adopts gtk3)
Read the original post. It's well worth it.
I've been running the Fedora Xfce Spin since F18, and I think it's one of the best-kept secrets in the Xfce-running distro world. It comes well-configured out of the box, looks great, is as cutting-edge as you'd want and really does just work most of the time.
Yep, one of the new features of the GNOME 3.14-running Fedora 21 is a preview of the next-generation, post-X Window Wayland display manager, and you can choose "GNOME with Wayland" in the login/session manager.
I'm running Wayland right now. I've heard the caveat many times: Not all applications will work in Wayland. But so far, every application I've tried (Firefox, Gedit, Transmission, FileZilla, VLC, Files/Nautilus, Liferea, Yumex, Google Chrome, Geany, even apps in Wine) has run in Wayland with no trouble.
I've been running Fedora 21 for a few days now, spending most of my time in the non-Wayland world of Xfce and GNOME with X, and the system is as solid as ever. And by that I mean pretty damn solid.
The only glitch I've had with Wayland has been in suspend/resume, which is pretty touchy anyway with my hardware. (I've probably written 50 posts about it since I got this laptop.) When running Wayland, the laptop will suspend and then resume, but I'm seemingly "detached" from my session and have to log in again. At this point I'm logged in twice. This doesn't happen in X. If this is the only thing I can find wrong with Wayland, I'll still consider it pretty remarkable.
Just from a "look and feel" perspective, GNOME 3.14 is working better and faster than version 3.10 did in Fedora 20. I'm not saying I'm going to throw Xfce over for it, but the environment is more usable than ever. I moved to the Adiwata Dark theme while still in F20, and everything looks that much better in F21.
As I've said since I began running Fedora 18 on this laptop and upgrading via Fedup to each subsequent release, a system as forward-looking as Fedora shouldn't be anywhere near as stable as it is. It's a tribute to the developers for Fedora and the many upstream projects that go into the distribution.
Today marks only nine days since Fedora 21 went stable, and my system is running like a well-maintained watch.
So if you think of yourself as the adventurous type, someone who likes everything to be pretty new all the time but doesn't really want to deal with a lot of breakage and is curious about Wayland in the real world, give Fedora 21 a try.
Later: You know what got fixed in Fedora 21 that was broken in F20? Mounting of Apple iOS 8 devices.
So I haven't upgraded my daily-drive Fedora 20 system to Fedora 21, which was released two short days ago.
From what I can see, the RPM Fusion repositories are ready for F21. Google Chrome might break, but a quick removal and reinstall should fix that.
In F21, there will be many changes in the GNOME desktop environment and applications.
But for my go-to desktop environment, Xfce, it's going to be pretty much the same. (Yes, Xfce is moving glacially slow, and I've heard talk of people turning to the GNOME 2-inspired Mate desktop because it's under heavy development.)
My web browsers (Firefox and Chrome) won't fall behind. I get the latest versions from Fedora and Google, respectively.
I'm dabbling in Ruby, and F20 has version 2.0. F21 has 2.1, but at the level I'm at, it doesn't matter.
And now that all the heat is on F21, it's been relatively quiet, update-wise for F20. It's a bit closer to running Debian Stable. After awhile you get a few security patches here and there, but updates are quiet and quick.
Even an old (but still supported) Fedora release gets more updates than a current Debian Stable, but for the moment, I'm enjoying the ritual of staring Yumex and seeing either only a few or, better yet, no updates waiting to be installed.
Sure I'll move to F21. It could be tomorrow (probably not) or next month (you're getting warm). But what's the hurry?
I needed to do a bare-metal install of Fedora 21 today, and I used the beta image for the live Xfce Spin.
I didn’t do anything special. The whole disk was devoted to Fedora. I encrypted everything.
It was probably the quickest Linux install I’ve ever done — even quicker than OpenBSD’s excellent text-based installer, where if you go with the defaults you have a working system within minutes.
Sure Ananconda isn’t “linear” like other installers, but once you get used to its “hub and spoke” logic, you can bring up a Fedora system very, very quickly.
As much as I love Debian, whenever I try to do anything complicated with disk partitioning, I run into trouble. Ubuntu’s Ubiquity installer is pretty good, too. But considering the bad press that Fedora/RHEL’s Anaconda installer has gotten over the past few years, once you get to know it, you can do installs very quickly and efficiently.
After a year and half, I've finally cracked suspend/resume in Linux on the HP Pavilion g6-2210us laptop (AMD A4-4300M APU with AMD Radeon HD 7420G graphics) with the open-source Radeon driver.
I've been able to successfully suspend/resume for some time on this laptop with the closed-source AMD Catalyst driver, but two things have prompted me to give that driver up for the open Radeon driver:
1) AMD Catalyst hasn't been packaged for Fedora since Fedora 19, and we're about to see Fedora 21 released with no indication that things will change. There are at least a couple of workarounds that will get Catalyst/fglrx on your Fedora 20 system, both of which I've written about at length, but I'm tired of doing them. While the Catalyst/fglrx experience is somewhat smoother on distributions that are serious about packaging the driver (Debian and Ubuntu come to mind), breakage is inevitable on fast-moving distros like Fedora that get new Linux kernels all the time.
2) While AMD Catalyst allows the laptop to run cooler at idle (I'm pretty sure it runs at a similar temperature under load), the quality of video -- actual videos in applications like VLC, that is -- is better with the latest Radeon driver than with Catalyst. Briefly, when I'm watching something and the image is "moving," it breaks up horizontally in Catalyst, not at all in Radeon.
But suspend/resume trumps all. Having it with Catalyst kept me ... running Catalyst.
Now that I've cracked the code for successful suspend/resume without Catalyst, the infrequently updated, not-packaged-for-Fedora, closed-source driver is fading in my virtual rear-view mirror.
So how do you get suspend/resume working on this particular HP Pavilion g6 (or similarly equipped) laptop?
There are two changes you need to make in GRUB.