Opensuse 13.1 after one week
It is now a little more than a week since 13.1 was released. There are things that one only notices with sustained use. So, here, I’ll mention some of what I have been noticing since switching my main desktop over to 13.1.
This one is really good news. Konqueror has been running continuously for over three days, with nary a problem. Previously, it was likely to crash after 12 hours or less, and sometimes it would crash when minimized. It looks as if a long standing bug has finally been fixed.
Normally, I close and reopen the browser once per day, as a way of deleting session cookies (and thus reducing tracking). But I’ve kept it open to see how long it lasts. I will close it shortly after posting this.
Full Disclosure — I am posting this with firefox. I still prefer firefox for normal browsing, but have been using konqueror or rekonq for most blog reading (in association with akregator). I’ll shortly switch to rekonq, so I can test whether it is also proving to be rock solid.
I have also had akregator running for over three days. And, thus far, it has been quite reliable. In particular, it has not messed up on its count of unread articles. This looks promising, though I’m inclined to say it is too early to say that the problem is solved.
Previously, an icon for akregator showed up in the tray. With 13.1, it only shows up in the tray when there are unread articles. If I click the little triangle to show hidden tray entries, I can find it there. However, I like to see it in the tray. So I used the tray settings to make the akregator tray icon permanently visible. And that seems to be working.
Whenever I login, the volume control shows at 66%. There is no memory of previous settings. This is a minor annoyance, but not a great concern.
There’s a “Ibus panel” in the tray for setting the input method. I’m doubting that I will ever need this, so I could probably uninstall. I did use the tray settings, to make it always hidden. But it does not seem to work when hidden — that is, no menu is brought up by clicking or right clicking. So switched back to “auto” mode which, in the case of “ibus”, seems to be the same as “alway visible”.
There’s an instance of “systemd” running as me, with the option “–user”, and this seems to be referred to as a user manager. I’m not quite sure what it does. However, it does interfere with “ecryptfs” (see below).
After install, and after adding “ecrypts-utils”, my ecryptfs private directory was not being mounted on login. I fixed that with
# pam-config -a --ecryptfs
However, now it is not being unmounted at logout, and this seems to be associated with that systemd user manager. I tried
# pam-config -d --systemd
which turns off the startup of the system user manager. And then ecryptfs starts behaving properly (unmounting at logout). If I do not disable the user manager in that way, but instead shut it down with
systemctl --user exit
as a KDE shutdown command, then the user manager is shutdown, but ecryptfs still fails to unmount the private directory. This is currently being discussed in bug 849870.