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.
RC1 (release candidate 1) was announced two days ago. And I guess I’m a bit slow posting that.
I downloaded and installed. I have now completed three installs:
- on a desktop system, with a clean install using the 64-bit DVD installer;
- on a laptop system, a clean install using the 64-bit live KDE installer;
- on an older laptop, a clean install using the 32-bit DVD installer.
All of the installs went well. By “clean install” here, I mean that I did not do an upgrade. I did install into existing partitions. For the second install, I kept “/home” as used with Beta1. For the other installs, I mounted my 13.1 home file system as “/xhome”, so that “/home” was part of the root file system, but I could add symlinks back to existing files. That allows new desktop settings files without interfering with my 13.1 systems.
Here’s my desktop, as requested by a commenter. This shows the default KDE wallpaper “openSUSE default”, and the default theme “openSUSElight”. I have left the Window Decorations and the Cursor Theme at the default (“Oxygen” and “Oxygen White”. Click on the image to enlarge.
The weather applet icon is the leftmost item in the tray, to the left of the akregator icon. I had clicked on the weather icon, so the window is showing. In case you are not familiar with it, the akregator icon is the one with the number “4” (the number of unread items). You can see that the icon for the weather applet has too little contrast (in my opinion).
Other icons showing are that for Amarok (the music note), and for gapcmon (the monitor for an APC UPS). There are actually two icons showing for gapcmon. The one on the right (looks like a battery) is the general one for configuring multiple UPC devices, while the other (looks like a power plug) is the specific one for my UPS.
The question mark at the end of the title, is because 13.2 is not yet released. The theme could change by the time of the release.
There was a holdup in updates to opensuse factory, due to testing failures. Soon after that problem was solved, snapshot 20140928 was released. And no sooner had I updated to that version, there was a release of 20141001. This post will review both.
I downloaded the DVD installer for for 20140928 (64-bit, and I then did a clean installs from that. This was intended as a test of the installer.
And a download note. On two already-installed factory systems, I added that DVD (actually written to a USB) as a repo. To do that, I opened Yast Software Repositories, clicked the “Add” button, then checked the box for “USB”. I had to select which partition (the second, since the first was just for EFI).
The result of adding the DVD image as a repo, was that an upgrade using “zypper dup” was far faster. When a particular rpm was on both the DVD image and the online repo, it was installed from the DVD image. That is a lot faster than network speeds with my current ISP connection. Read More…
[Update: 9/25/2014 - A quick check shows that opensuse has a patch for this for 13.1, and presumably for 12.3. You should update your system as soon as possible. An email message in the factory mailing list explains why this is not yet fixed for factor and contains a pointer to where you can update bash if your system is running public services (such as a web server.]
This will be brief. Information is coming out about CVE-2014-6271, a bash bug which is potentially remotely exploitable.
I suggest you do a web search for “CVE-2014-6271″ if you are looking for information. Information on this bug was embargoed until a few hours ago, so better information will soon start turning up.
The bug itself is with the use (and mishandling) of environmental variables, particularly when they define shell functions. The concern is that this might be a vector of attack via shell scripts that can be invoked remotely, such as cgi-scripts on web servers.
I’m not personally concerned. I am not running a web server, and I doubt that I have any easy attack points for this bug.
There’s no information on when opensuse will fix this, though they are working on it. The bug is mentioned in the opensuse mailing list, which is where I heard about it.
The beta1 release of 13.2 was made available yesterday. Here’s the announcement:
and here’s the download page:
Yesterday, I downloaded and did a couple of installs.
My installs went pretty smoothly. They are better than I have previously seen with beta releases. Still, there were some install quirks and I’ll go through those below.
Here are a couple of interesting links that I saw today:
I’ll add my own comments here.
The first of those links is about the number of adoptions of factory. It is good to see that the number has been growing. However, I’l suggest a bit of caution in interpreting them.
I’ll use myself as an example. When went with Tumbleweed on one of my systems, I first installed 13.1 as a clean install, then switched it to Tumbleweed. I expected to continue to update that until 13.2 is released.
Most of my installs have been with the DVD image. I decided it was time to try out the live KDE image.
I mainly wanted to test out the new NetworkManager applet for KDE, and for a good test I needed to do that on my laptop. I had previously been using factory snapshots on desktop machines rather than laptops, so with an ethernet connection rather than WiFi.
It was easy enough to download the image. I looked in the download directory to see what was there, and then copied the link for the 64-bit KDE live image. I used “aria2c” to download the iso. Then I downloaded the sha256 checksum (I just appended “.sha256″ to the link I had copied). I used the checksum to verify that I had a good download. I would have preferred a gpg signature, but we make do with whatever is available.
Next, I wrote that iso file to a USB. The USB device shows up as “/dev/sdd”, so I used the command:
# dd_rescue openSUSE-Factory-KDE-Live-x86_64-Snapshot20140820-Media.iso /dev/sdd
to create the live USB. Read More…
A few days ago, I decided to install the latest factory snapshot on my older computer — the one with a Nvidia Geforce 6150LE graphics card. Mostly, it was uneventful, except for issues related to the Nvidia graphics. The install itself went smoothly. As we move closer to the release time for opensuse 13.2, the factory installs seem to be going well.
I actually installed factory snapshot 20140813, in spite of what I listed in the title above. This replaced the kubuntu 14.04 that I had previously installed in the spare partition of this computer.
As is my usual practice, I downloaded the iso image for the full DVD installer from the factory download page. I used “aria2c” for the download. I gave “aria2c” the link for the iso, and it managed to find the meta file that it needs. The download was smooth.
I am continuing to use opensuse factory. Today, it updated to the 20140805 snapshot. Factory continues to be mostly working as it should. Here I’ll post a few notes about how it looks.
The Gnome Classic extension was introduced for opensuse 13.1. However, it never quite worked. I was able to get it working by switching to “gdm” as login manager. But I don’t much care for “gdm”, so I soon switched back.
Both “kdm” and “lightdm” have menu selections to login to Gnome. However, they didn’t work. With either of those as login manager, selecting “Gnome Classic” resulted in a login to Gnome. The Classic extension was not activated.
There is a way to manually load Classic once you are in Gnome. I’ve tried that, but I don’t remember the details (it did work).