With inspiration from Paul Mellors, I decided to start my personal Fedora Wiki page. Yes, I am a Fedora member, though I haven't yet blossomed into an active one. At this point I try to answer questions on Ask Fedora, and I'd like to start contributing to the Fedora Magazine.
So I'm mostly just a user of Fedora. But that doesn't mean I shouldn't be a Fedora member, or have a wiki page. So I am. And I do.
Fedora's motto is "Freedom. Friends. Features. First." I'm here to tell you Fedora lives up to that billing. Why do I say this now? I've just had another positive experience with Fedora, this time in finding a bug in my system, adding my information to an existing bug report and now seeing updated packages pushed to the Fedora 20 stable repositories and onto my system, where the problem has been fixed.
This all started a few weeks ago. After an update of the
wine software that allows Linux users to run many Windows programs, many of the fonts in both the Firefox and Chrome web browsers started to look horrible. I narrowed it down to anything resembling Arial and Helvetica.
After searching for information, I found a command that would tell me what the system was using when asked to display a certain font:
$ fc-match -v arial | grep file
Now that the problem has been fixed, the output is different, but at the time it clearly showed that a wine-installed Arial font had been installed in my system's decidedly non-wine (aka "normal") font path.
And that font was hideous.
I began searching for other Fedora users who might have this same problem and came across this bug report on wine-courier-fonts overriding the system Courier font. In that bug report was this Aug. 9, 2014 comment by Arun Raghavan:
This also seems to apply to the arial font which makes things in Firefox look weird as well.
I saw this on Aug. 13, and immediately got into the thread because I'm a Fedora member and already have a Bugzilla account:
I am seeing this same issue with Arial. The fonts look terrible in both Firefox and Google Chrome. I think this happened during the last Wine update.
Hours later, Peter Oliver confirmed the problem:
Indeed, wine-fonts-arial was first included in 1.7.22-2, pulled in automatically by wine-fonts.
I know there's disagreement about whether Wine fonts should be made available as system fonts, but, irrespective of that, this affects the existing user experience, so ideally shouldn't have been included in a stable update.
The next day Michael Cronenworth wrote that he was pushing an update to
wine that would take the fonts out of the system path:
The Font SIG has allowed us to remove Wine fonts from the system path. I'll be pushing a 1.7.24 update shortly to address this.
A few days after that, the update was available in the testing repository. I waited for it to make its way into Fedora 20 Stable, which it did today. In the course of today's Yum (in my case the GUI Yumex) update, new
wine packages were installed on my system, and now everything looks great again in Firefox and Chrome.
As asked in the bug report, I did add karma after installing the update.
Things do break in Fedora every once in a while, but not as often as you might think.
Pretty much every time something like happens on my system, even with the kernel, I've been able to either start a new bug report or chime in on an existing one. Soon thereafter, the wonderful developers who build packages for Fedora have addressed my problems and provided fixes that made those problems go away.
Chalk it up as another great experience with Fedora, both the Linux operating system and the community behind it.
I looked back in the archives and found out that I've been running Fedora on this particular laptop (HP Pavilion g6-2210us) for a year and two months.
Since this el-cheapo, about-$400 AMD laptop is NOT a top-of-the-line Intel-running Thinkpad, it hasn't gotten anywhere near the same level of love from the Linux kernel and driver developers.
But things have gotten better and better over time. And excepting the relentlessly rolling Arch Linux, things improve more quickly in Fedora than anywhere else. New kernels, drivers and applications, for the most part, fly onto Fedora systems via regular updates.
Probably the best "solution" I've found for the lack of AMD Catalyst packages in RPM Fusion for Fedora 20 has been to use the packages that are still being maintained in that repository for Fedora 19.
But as always with proprietary driver packages, there is a question as to whether or not they will work with a new Linux kernel.
Kernel 3.15.3-200 moved recently into Fedora 20, and I decided to make the leap into installing it today.
I can report that
akmod-catalyst handled it perfectly. Catalyst works in 3.15.3, and everything is running as it should.
One of the touted features in kernel 3.15 is faster suspend/resume. Does using a proprietary video driver negate this speedup? I don't know.
I do periodically test suspend/resume with the open Radeon driver to see if I can ditch Catalys, but at this point I'll wait for live Fedora 21 (and Ubuntu 14.10) media for my next foray into the free driver.
The title of this post is long. It says it all.
I'd like easy file-encryption from the file manager in Fedora (and every other version of Linux, for that matter).
I'd prefer that encryption be strictly password-based and not dependent on encrypted keys that I might lose, but encryption with keys that I have safely backed up offsite is better than no encryption at all, so I'm going to try using the GNOME application Seahorse to try this out.
I'll even ignore that I'm not using GNOME and instead relying on the Thunar file manager in Xfce.
But I do have a full GNOME environment installed, and I'd use it more if GNOME would run under the AMD Catalyst driver in Fedora 20. That it does not should be a much bigger deal than it appears to be among the greater Linux user base.
Anyway, I do have Nautilus, and to make Seahorse work in that file manager, Fedora offers the
seahorse-nautilus package. I installed it just now and will be giving it a try in the very near future.
Update: After installing
seahorse-nautilus, it is possible to encrypt files via right-click in Nautilus, but there is no right-click option to decrypt a file.
There is a Fedora 17-era bug on this issue, which appears to have been resolved.
An answer on Ask Fedora provided a workaround, but I'm reluctant to try it at this time, though I should probably look into it for help in creating a "custom action" in Thunar so I can encrypt/decrypt directly from my chosen Linux file manager.