With Leap 42.1, opensuse no longer provides the flash plugin for firefox. However, the folk who maintain the packman repos have added flash there. So I have been using flash from packman until now.
Unfortunately, the flash in packman is a tad out of date. And I’m getting annoyed at firefox telling me that flash is vulnerable and requiring me to jump through extra hoops when I use it.
I don’t actually use flash very much. But there are a few sites where I need it. I have the flashblock extension installed, so flash does not activate until I tell it to, so the risk of an out-of-date flash is small. But firefox still makes me jump through extra hoops. For that matter, I really don’t like firefox “phoning home” to decide that flash is vulnerable. But that’s the way it is.
A brief note on konqueror.
It is crashing badly for me on opensuse factory and on opensuse 13.2-RC1.
It seems that there is some kind of conflict between konqueror and the other desktops (Gnome, XFCE and LXDE) that I usually install. If I install only KDE, then konqueror works well. But if I also install Gnome, XFCE and LXDE, then konqueror crashes on many sites.
If I switch konqueror to use the KHTML engine instead of the WebKit engine, then it is stable. But I’m not a fan of KHTML, so I prefer it with WebKit.
When 13.2 final is released, I guess I will install only KDE on my main desktop, so that I can have a stable konqueror. I’ll continue to install the other desktops (in addition to KDE) on my laptop and backup systems.
This problem has been reported as bug 901006.
I recently tested the firefox extension “KDE Wallet password integration“, mainly in response to an opensuse forum question. So I thought I would post a review of it here.
I tested this in my test-user account, rather than my regular account. I had long ago decided that I probably didn’t want this extension for my regular use. I’ll also explain that below.
What does it do?
The main purpose of this extension, is to allow firefox saved passwords, such as you might use to login to web sites, to be saved in KDE wallet (or “kwallet”), instead of the usual place where firefox saves it. This protects the saved passwords, assuming that you have set a password to open kwallet. And it allows you to keep passwords for various software components, all in the same place.
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…
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…
I did not have to change much to try out konqueror. I have been using it, in association with “akregator”, for reading blogs.
The good news about konqueror in opensuse 13.1 (and KDE 4.11.3), is that it is a lot more reliable than what I experienced with 12.3. I can use konqueror for several days without it crashing. Previously, with 12.3, it would often crash several times per day.
I have konqueror set to load plugins (such as the flash plugin) on request. That works pretty well. When there is a flash video, there is a little button “load plugin” that I must click before it loads. This is very similar to using the “flashblock” extension with firefox. And I do use that extension. Otherwise some of the flash in advertisements would be annoying.