On opensuse forums, I often see complaints about KDEwallet (or “kwallet” for short). It can be annoying at times. In this post, I’ll indicate ways of keeping it under control.
While this is oriented toward opensuse, it should also apply to other distros with one caveat. In opensuse, some of the applications have their settings and configuration under the directory “$HOME/.kde4”. For other distros, it is more typical to use “$HOME/.kde” (without that final “4”). So just adjust my suggestions accordingly.
Starting with Leap 42.1 (and with Tumbleweed), opensuse now supports Plasma 5. And Plasma 5 keeps its configuration under “$HOME/.config” and under “$HOME/.local”. But there remain some older applications with configuration in the old location.
To further complicate things, there are now two versions of “kwallet”. I’ll call them “kwallet4” for the old version still used by some older software, and “kwallet5” for the newer version (for Plasma 5). That both wallets are there, and that they might independently prompt you to open the wallet, is part of the confusion.
I’ve simplified my life, so I am no longer doing regular monthly installs. But I still do occasional installs.
In this case, the occasion was a topic at opensuse forums:
A user was not sure how to install without a network. So I decided to do an install, to make sure that this was still possible.
I began by downloading the latest snapshot. I first used
to download the sha256 checksum file. That’s a small file (654 bytes), and I find it easier to use “wget” for small files. I then verified that file, using
gpg --verify openSUSE-Tumbleweed-DVD-x86_64-Snapshot20160813-Media.iso.sha256
The file itself has a gpg signature, so checking that signature is sufficient to verify the download.
There have been several recent updates to opensuse Leap 42.1. Toward the end of February, there was an update of KDE applications. And earlier this week there was a frameworks updates.
There was, at first, a problem with the update earlier this week. There were two updates that were supposed to be applied at the same time. And somehow they released the frameworks update without also releasing the QT update. That left some folk unable to login to the plasma 5 desktop until they released the complementary QT update.
I’ll note that I was affected by this on one of my computers. But it did not affect my main desktop, because I held off applying the update until all was back in order.
On Saturday, I noticed that snapshot 20160205 had been released. So I downloaded that for this month’s install.
The install itself went quite smoothly. I installed the KDE (i.e. Plasma 5) desktop. Additionally, I installed networkmanager-gnome, so that I could test that with KDE.
My install was into the same external drive that I have previously used. It was connected to my laptop. My install was into an encrypted LVM. I imported the mount points during the partitioning section of the install.
I noticed two problems. The first was a repeat of the problem that I had n noted for my January install. Namely, the entry added to “/etc/crypttab” was bad. I had to go into rescue mode to repair that. But this was expected. That bug report is still open. So the problem was not a surprise and I knew how to deal with it. On this occasion, I used the UUID of the LUKS partition in “/etc/crypttab”.
I last looked at NetworkManager when it was at version 1.0.0. It is now at version 1.0.6, and with some changes that persuaded me to do some more testing.
To test, I setup a connection and then did some tests. I repeated this for KDE/Plasma 5, for Gnome and for XFCE. It is also possible to run “nm-applet” and a polkit daemon in Icewm, where configuring the network is similar to what happens with XFCE (which also uses “nm-applet”).
Between series of tests, I cleared out all configuration. To do this, I booted a different system (booting a live CD would also work), and then mounted the root file system for Tumbleweed. That way, I could clear out the saved configuration while Tumbleweed was not actually running.
Last week, there was an announcement for Fedora 22. So I decided to take a look. I’ll note that I have only tested the KDE-live version. I have not attempted an install.
The Fedora site
From the announcement on distrowatch, I visited the Fedora project home page. There, I found lots of marketing hype but very little useful information. The home page mentions a server version, a workstation version and a cloud version. But I did not find a clear description of what is in those version and what distinguishes them.
Or, in simpler terms, the Fedora website sucks.
In previous experimenting with Fedora, I have found that installing from the DVD installer gives a better running system than installing from live media. So I tried to find an install DVD.
I recently did my April install of Tumbleweed. And it’s an interesting system. I also updated an existing Tumbleweed to the new level (20150330).
Of particular interest this month:
- there’s a newer version of NetworkManager;
- Gnome 3.16 is out and has some support for Wayland;
- “top” output format is changed.
I’ll start with Wayland, since that is the biggest change. If you have been living in a cave, and have not heard of Wayland, it has a web page HERE.
Briefly, Wayland is a proposed provider of graphic services as a possible replacement for X-windows. There are arguments around as to whether X needs a replacement. I am taking a wait and see attitude before I make up my mind on that.
As previously mentioned, I am doing an install every month. This is mostly to test installing with the Tumbleweed DVD image. You can think of it as early testing for opensuse 13.3. So yesterday (March 12) was my install day for this month.
I normally expect downloading to be unremarkable. I usually don’t have problems. I didn’t have problems with this download either, but it was surprisingly slow.
Browsing to the downloads site, I copied the download link. I then used:
wget download-link.sha256 aria2c -V -R download-link
I have substituted “download-link” for the actual link, since that change every time so the actual link isn’t very useful for posting here.
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…