In my recent review of “chromium”, I mentioned that it offers to save passwords, and stores them in kwallet. This suggests that they should be stored in encrypted form, due to the way that kwallet works.
Unfortunately, things may be worse. I recently tested out “chromium” while logged into Gnome. And when I visited a site where chromium had a saved password, it filled in the password field. But I was never prompted for the key to unlock kwallet.
It now looks as if “chromium” is saving the passwords in kwallet, where they are encrypted. But it is apparently also saving them in an unencrypted (but obscured) file in the user chromium profile directory.
This is not good.
This review of “seamonkey” completes my series of browser reviews for this year.
“Seamonkey” comes from Mozilla, the same group that give us firefox. So it should come as no surprise that there is a lot of similarity with firefox. There are also some difference. In this review, I will mainly comment on the differences.
Mail support (not tested)
The biggest difference, is that “seamonkey” supports email. Roughly speaking, the “seamonkey” project got under way, when Mozilla decided to split the browser functions from the email functions, with “firefox” for browsing and “thunderbird” for email. It is probably fair to say that most of the people who use “seamonkey” do so because they want a single combined application for both web browing and email.
“Firefox” is a familiar browser. The original “Netscape” was the first browser that I used, and the mainstay of my browsing for many years. That changed to “mozilla”, and then to “firefox”. And I continue to use “firefox” for much of my browsing, though I have recently been using “konqueror” for browsing pages initiated from “akregator” (the RSS reader).
I normally use “firefox” with the “noscript” and “flashblock” extensions. I disabled those for this review, to better compare with the way that I tested other browsers. However, I kept the “secure login” extension, since that does not have a noticeable effect on most ordinary browsing. I set “firefox” to be the KDE default browser, and allowed “akregator” to pick that up for showing pages in an external browser.
“Firefox” probably works the best of all of the browsers that I have been testing. No doubt this is partly a matter of personal experience and familiarity. During two days of testing, it did not falter. It never crashed. It is fast in loading pages — perhaps not as fast as “midori”, but much faster than “konqueror”. Read More…
I have been doing most of my browsing with chromium for the last two days. So it’s time for that chromium review.
A quick note on “chromium” vs. “chrome”. The “chrome” browser is a proprietary google product, based on “chromium”. I tested only “chromium” because that’s the open source browser and is available in the standard repos. It, too, is a google product. But it is entirely open source. “Chromium” and “chrome” were originally based on the Webkit browser engine. However, more recently, webkit has been forked, with “blink” as the new fork and the base engine for “chromium.” Read More…
Some recent examples:
- Yesterday, my wife called me on my cell phone. I never received the call. So she left voice mail. I didn’t receive that, either. Fortunately, we still have a land line, and she was able to get me there. As usual, I turned off the cell phone overnight. When I turned it on this morning, the voice mail was waiting for me. My best guess is that the cell network somehow lost a database entry, so lost track of my phone. Read More…
I started seriously testing “epiphany” this morning, in preparation for writing this review. But “epiphany” turned out to be so poor, that I cut my testing period short. In my opinion, this browser is not suitable for prime time.
I first came across “epiphany” several years ago. I seem to recall that it was part of a standard install of SUSE 10.1. I briefly tried it, but did not pay much attention. I believe that it was based on Gecko (the mozilla engine) at that time.
I’ll start with a quick summary. “Midori” is a congenial browser, with some defects. But it is not a browser that I would normally use. It messes up copy/paste, and that’s enough of a problem for me to rule it out.
“Midori” is apparently a recommended browser for the XFCE desktop, though opensuse provides “firefox” with its XFCE. “Midori” is light weight, and is very fast in rendering pages. It is a pleasant browser to use, as long as you do not run into its shortcomings. Read More…
This is a followup to my earlier review of the 32bit edition. I noticed the announcement of the 64-bit version on the lizards mailing list (which I do not closely follow):
So, naturally, I decided to take a look.
Download and boot
I followed the “download” link on that announcement. I used “aria2c” on the metalink provided, then checked the SHA256 sum. The download went smoothly. I then “burned” the iso file to a USB, using “dd_rescue”. I presume that I could have burned to a DVD, but I did not test that. The format looks correct for a USB, though the announcement did not mention that possibility.
I have been running opensuse Tumbleweed on my older desktop. It has an Nvidia graphics card (6150LE). So I have been installing the Nvidia drivers the hard way, which is not really all that hard.
A few days ago, when I ran Tumbleweed updates, that installed a 3.13 kernel. On reboot with the new kernel, the graphics driver did not load. This is expected. So I ran the script to reinstall the Nvidia driver.
# sh /usr/local/src/NVID*.run
The updated driver seemed to build. But then it would not load.