I’m a very happy GNOME user, but on my old 32 bit laptop I wanted to try something else and so my only candidate when it comes to a Spin, is Xfce. Not that the default configuration is very good, but it uses GTK libraries and if needed I can easily install also GNOME applications.
In this short blogpost I’d like to go beyond the normal setup and just share what I did to make Xfce working as desired. The installation of the Spin is really easy and fast, no useless applications are on board and the user really can choose what he likes more. There’s just a small “but”…..yes, settings are not working always and it depends on your usecase if the solution is easy or hard to achieve. Fedora 22 comes with the latest 4.12 Xfce release, which is so much better than 4.10 but still not perfect.
Another ~6 months down, another Fedora release. While Fedora 23 looks to be an interesting release over all -- with some initial changes coming to Anaconda, and some changes coming to the upgrade process -- this release was more low-key for most of Fedora-land. Workstation saw updates to notifications and general theme'ing improvements, Gnome Software got AppData integration to bring the Software Center closer to an app-store experience. Of course Gnome Boxes and Gnome Builder were included as well, allowing for more out-of-the-box developer improvements in the realm of Virutalization and IDE's, respectively. But there weren't any ground breaking features across the board -- no swapping of the init system, no BTRFS, no Wayland by default, although GDM is running the Login Screen through Wayland.
The Skrooge teams releases today the version 1.12.5 of its popular Personal Finances Management software. This release is a bugfix version, mostly aiming at fixing issues met on some distros when the SQLite version bundled in Qt is not aligned with the System version.
This is first update of the my GSoC project TV optimized dashboard support in the Plasma Media Center. First let me tell you what this project is about
Therefore today I installed the same setup on my work machine and will now use the KF5 based Kate for all of my day job, perhaps that motivates me more to take a look at the issues the Qt5/KF5 port still has.
DigitalOcean is a cloud provider that provides a one-click deployment of a Fedora Cloud instance to an all-SSD server in under a minute. After some quick work by the DigitalOcean and Fedora Cloud teams we are pleased to announce that you can now make it rain Fedora 22 droplets!
One significant change over previous Fedora droplets is that this is the first release to have support for managing your kernel internally. Meaning if you dnf update kernel-core and reboot then you’ll actually be running the kernel you updated to. Win!
Embedded in Whitehurst’s argument is that while public cloud can work for disparate workloads, nonvarying workloads are best “hard-wired” in a private cloud. If you know the compute/storage requirements, why not run those workloads on dedicated local resources? A modest capital investment ends up being a lot cheaper than long, drawn-out, public cloud operating costs.
The biggest new for Fedora 23 is that blivet-gui will no longer require root privilegies for the GUI part. There are now two separate processes, one for the UI, running as a regular user and second one for the "backend", running as root. But you'll still need to provide your root password to start the backend (it isn't a daemon). This feature is already finished and packaged in rawhide repos.
Other new features for Fedora 23 includes LVM thin-provisioning support and support for creating and managing LVM snapshots.
Fedora 22 is out and it’s again the most quality release we’ve ever released. Our quality assurance is improving and on the developer side, we’re also trying to do our best heavily using ABRT retrace server to prioritize bugs that affect many users. Unfortunately while the quality of releases itself is improving, the quality of updates that follow the release is not.
One of the main points regarding the functionality of the Fedora Hubs site is the idea that each user will have the ability both to become a member of various hubs, and also to subscribe to them. For easy access to these hubs, a list of the hubs each user ‘follows’ is collected sitewide in the header area of Fedora Hubs. The mockups in this post describe the ways that users will be able to customize their personal hub ‘bookmarks’.
Sorry to spam your feeds today! I’m trying to collect all my thoughts about what I’ve been working on before the Fedora Hubs workshop tomorrow morning. Since my last post was pretty long, I’m combining these two different concepts I’ve been designing over the past week into one post. While both of them are at least as complex as the hub bookmarks, I ran into a lot fewer mental roadblocks when figuring it out, so I have fewer random thought tangents to explain away, so (hopefully!) this post will be a little shorter. (edit: It really wasn’t. Sorry!)