I don't run Google Chrome all that often in Linux, though I run it all the time in Windows.

But I do keep Chrome, via Google's repository, on my Fedora 20 system.

So I try to run it today and it segfaults (I know because it kills X and I see "segfault" in the console messages).

I searched (yes, using Google) and couldn't find anything on this.

I can't remember if I've used this particular version of Google Chrome successfully before my most recent reinstall of AMD Catalyst (via the Fedora 19 packages in RPM Fusion).

Right now I'm unwilling to uninstall Catalyst just to test Chrome, especially because I'm primarily a Firefox user on this machine.

(This is what the Fedora 19 AMD Catalyst packages look like on my Fedora 20 system when seen in Yumex. Click the image above for a bigger version.)

Who better to tell you how to find and install an RPM package for the AMD Catalyst driver in Fedora 20 than the very person who ophaned the driver for that very release?

That's right, Leigh Scott, who had every right to drop the packaging of the AMD Catalyst driver in RPM Fusion for Fedora 20, is still maintaining it for Fedora 19.

He has an easy recipe for using the F19 driver on F20 systems. I can confirm that his method works. As is, this RPM of the Catalyst driver does not work with GNOME 3 (due to previously mentioned Wayland code that GNOME is now including). It does work with Xfce and KDE (and everything else that isn't GNOME 3, I presume).

Here are the instructions, originally from Leigh's post on the Fedora Forums, with my annotations:

First, make a directory and cd into it. Leigh suggests calling it 'catalyst':

$ mkdir catalyst

$ cd catalyst

Grab the needed Fedora 19 packages with yumdownloader:

$ yumdownloader --releasever 19 xorg-x11-drv-catalyst-libs.i686 akmod-catalyst.$(uname -m) xorg-x11-drv-catalyst.$(uname -m) xorg-x11-drv-catalyst-libs.$(uname -m)

Use yum to install the packages (shown here using sudo, though you can also su to root if you wish):

$ sudo yum --nogpgcheck install *.rpm

After this installation, I rebooted and had a working Catalyst/fglrx driver on my system. As I said above, it doesn't work with GNOME 3, but neither did the upstream AMD package before it stopped working altogether with the 3.14 kernel.

Configuration note: I did NOT need to do this, but if you have problems, you might want to use the aticonfig utility as suggested here:

$ sudo aticonfig --initial

Again, I did NOT need to do this.

Also, I'm not sure if these Fedora 19 packages will be updated with when I run Yumex or yum update. I do know that it's a good idea to keep an eye on the latest packages in RPM Fusion (in this case the non-free F19 updates repository) to make sure that you don't install any kernels before a new Catalyst is ready for them.

I will update this post when I have more information on how long this fix continues to work.

I'd like to thank Leigh both for his work on AMD Catalyst in RPM Fusion until now as well as for this temporary Fedora 20 fix.

At the same time, I once again call attention to how the lack of an RPM package of AMD Catalyst for Fedora takes away choice and functionality from the distribution and its users.

As much as I love Fedora and its community, if you have a newish AMD-running computer, I really can't recommend Fedora because of this continuing problem. Sure, the open Radeon driver for AMD graphics chips/cards is better than ever, but I can't get suspend/resume with it. Once that starts working for me, I'll shut up.

So what do you do if you need AMD Catalyst? Distributions that haven't fallen into this rabbit hole include Debian, Ubuntu, and every single other one I can think of.

I'll ride this fix as long as I can, but you can bet I'm thinking of where I can go in terms of a new Linux distribution in order to have my choice of video driver.

Read the rest of this post

Since Phoronix is the best source of news on Linux graphics hardware (and probably Linux hardware and benchmarking, too), I decided to e-mail the site's Michael Larabel and see what he thought about the fact that there has never been an RPM-packaged AMD Catalyst driver for Fedora 20, and at the moment even the upstream AMD installer won't work with the 3.14.x Linux kernel.

I'd like to thank Michael for turning that e-mail into this article: AMD Catalyst On Fedora 20 Is Left In An Awkward State.

The next day, he followed it up with How-To Install AMD Catalyst 14.4 On Fedora 20 With Linux 3.14.

I'd like to thank Michael for this, and for all the day-to-day reporting he does on Linux (and often BSD) in regard to drivers and hardware.

In a forum post for the last article, I found a different, better way to get AMD Catalyst/fglrx working in Fedora 20.

Ironically (or perhaps coincidentally), this tip comes from the guy who orphaned the Catalyst packages in RPM Fusion for Fedora 20 but still maintains them for Fedora 19 (and it involves using the F19 packages in F20).

I have to do a few more tests of this method before I detail it in another post, but first I'd like thank Michael again for his posts, and Leigh Scott right now for this too-easy way of getting the Catalyst driver working again.

Final word: I don't blame Leigh, per se, for dropping the Catalyst package in RPM Fusion. It's every maintainer's right to quit whenever they want. I'm just continually stunned and saddened that in the many months since Leigh made this decision, nobody else has stepped in to fill this crucial gap in the Fedora/RPM Fusion/Catalyst world.

I'm only speculating as to what caused 3D acceleration to stop working on my Fedora 20 system using the upstream-installed AMD Catalyst driver.

But I'm pretty sure it is the new Mesa packages that rolled into Fedora a day or so ago.

Even if Mesa isn't the culprit, apps that require 3D hardware acceleration are either throwing warnings about the lack of this particular feature, or just crashing immediately.

Running glxinfo in a terminal gave me the following message:

direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)

I suspected that the AMD Catalyst video driver, which I'm installing with AMD own .run installer because there is no Fedora 20 package for it in RPM Fusion, was somehow broken.

When I have problems with the proprietary video driver, I usually uninstall Catalyst, check whatever's broken while running the open Radeon driver and then reinstall Catalyst and check again.

Except this time Catalyst wouldn't uninstall. The error message I received said something about the configuration being changed.

Catalyst wouldn't reinstall, either.

The script output suggested that using --force would overcome the errors in either case -- uninstalling or reinstalling.

So I decided to reinstall AMD Catalyst over the current installation.

Since I was already running the latest Catalyst driver from AMD, I had previously downloaded, unzipped it and installed it, and the .run file was already on my system for the reinstall.

I did this as root:

# ./amd-driver-installer-14.10-x86.x86_64.run --force

Catalyst reinstalled with no trouble, I rebooted, and 3D hardware acceleration was back.

You need more than just kernel packages to successfully install the upstream AMD Catalyst driver in Fedora, and you might not need every last one of these packages. But it couldn't hurt to have:

kernel-devel
kernel-headers
kernel-modules-extras
kernel-tools
kernel-tools-libs

Other packages that you need or are helpful include:

dkms
gcc
binutils
make

Then you can go to the AMD Catalyst site for Linux, download a .zip file, unpack it and use the resulting .run file to install the driver.

I wrote up more detailed instructions on how to install the driver in January. Those instructions are probably due for an update. I'll do that soon -- maybe when AMD updates the driver for the 3.14 Linux kernel.

The new Firefox, version 29, brings a whole new look to Mozilla's web browser.

I hope it brings a lot of other new things, too. I pretty much run Firefox exclusively in Linux, and I'd love to do the same at my day job, in Windows 7, where I use Google Chrome for the most part. In my day job, I have a whole lot of tabs open, and Chrome seems to handle it better. I would welcome a more robust Firefox in this regard.

Better or not, Firefox 29 is now in Fedora. The image above comes from the Fedora Magazine post announcing the update, which already flowed onto my installation via the Yumex package manager.

In my Ode system running on an Apache web server, I'm "exposing" the existence of the /documents directory by stashing HTML there for my site archive.

Normally only text files and images live in that directory, and Ode uses them to produce the HTML pages it serves out of another directory.

I'm not crazy about exposing the contents of directories that don't, for the most part, serve HTML. So I decided to disallow directory listings on my Ode site with this line in .htaccess:

Options -Indexes

Now my readers can see http://stevenrosenberg.net/documents/archive.html but not http://stevenrosenberg.net/documents and the entire structure under that.

Even if I do decide to move my archive file to another directory (and I am seriously thinking about doing that), it still seems like a good idea to block access to the "raw" directories in Apache.

I stopped using stand-alone mail clients about a year ago.

This week I decided to give Thunderbird another try. I'm keeping it simple this time around.

I'm using Thunderbird for a single e-mail account via IMAP. No Gmail. No shared Google Calendar. No newsgroups (yeah, I said newsgroups, which I had running in Thunderbird my last go-round)

What pushed me back to a mail client was the lack of speed in my webmail client of choice, RoundCube, with my mail provider.

So I'm keeping it simple and enjoying the speed and ease of a traditional desktop mail client.

Thunderbird has seen quite an update in its UI since the last time I used it, and that's enough progress for an app that has seemingly been abandoned by its parent company/foundation Mozilla.

As long as they keep it patched from a security standpoint, I don't need any new features.

It happened a day later than it should have, meaning Fedora got spanked by Debian, but the Fedora 20 patch for the OpenSSL 'Heartbleed' bug did roll onto my system today.

I would have liked Fedora to be ahead of Debian rather than behind it, but a day's delay isn't a deal-breaker. And I could have installed the OpenSSL update from Koji early if this were a server installation.

Overall, the free-software community's response to the 'Heartbleed' bug shows the power of open development and how these projects and products are stronger through transparency and sharing.

I don't look on the OpenBSD Misc mailing list very often, but today a message from that list introduced me to Neomailbox, which offers services that include secure, encrypted e-mail and anonymous web surfing for prices that are very reasonable.

So why would you want to pay for e-mail? Well, you do get what you pay for, and while services like Gmail have a lot to offer, one of those things is Google's servers crawling the text of your mail and serving you ads based on what's in there.

And while Google is continually boosting its use of encryption, there are plenty of reasons why you might want an offshore, encrypted mail service that you actually pay for.

Did I forget to mention that Neomailbox uses OpenBSD?

Neomailbox also offers an anonymous web surfing service that uses encrypted tunneling and anonymous IP to add a whole lot of privacy and security to your daily comings and goings on the Internet.

And they do offer discounts if you get both e-mail and anonymous web, plus additional "family" discounts.

If your paranoid (or have reason to be) and don't want to run these services yourself on either home or colocated servers, Neomailbox is definitely worth a look.