this time I went directly from 13.2 to Leap 42.2, skipping the intermediate step of Leap 42.1…. and no problems. I like that.
For your convenience here is the link to how I do this.
For your convenience here is the link to how I do this.
I finally updated my last machine from openSUSE 12.3 to 13.1 (in the usual way), and with that one I had a bit more fun than the other few times I’ve done this by now.
First mysql refused to start, then quite a few services that were enabled on 12.3 decided to be disabled on 13.1, but nothing during the update “told me so”… but now all seems to work fine.
Seeing that there are only two more weeks until openSUSE 12.2 reaches end of life, I’m doing my usual upgrade with zypper.
If you are about to say “didn’t you do that already some months ago“, that was a virtual machine…now it’s my “production” system. Let’s hope all goes as well as it did on the VM.
So far all is looking good, but 4500 packages takes some time, so I can’t really say anything yet. I’m doing 12.2 -> 12.3 and KDE 4.11 -> KDE 4.12 at the same time, so it might get a bit hairy at some point.
The fun part comes next week… if this goes well I’ll do the same to my wife’s laptop, where a failure will be way more painful…
Update: finished, all seems to be working fine.
…at least with KDE4 on openSUSE 12.2.
In a previous post I mentioned that there are single-sign-on methods available for KDE to open the wallet right on login, but they do not work when you’re using NIS accounts.
Turns out they do work after all, you just need make sure that the references to the pam_kwallet module is after pam_unix2.so in common-auth, like this:
#%PAM-1.0 # # This file is autogenerated by pam-config. All changes # will be overwritten. # # Authentication-related modules common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of the authentication modules that define # the central authentication scheme for use on the system # (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the # traditional Unix authentication mechanisms. # auth required pam_env.so auth required pam_unix2.so auth optional pam_kwalletopener.so use_first_pass auth optional pam_gnome_keyring.so
After this, you just add the two modules pam_dbus_launch and pam_kwallet in common-session like this (pam_dbus_launch needs to be before pam_systemd, and pam_kwallet at the end):
#%PAM-1.0 # # This file is autogenerated by pam-config. All changes # will be overwritten. # # Session-related modules common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of modules that define tasks to be performed # at the start and end of sessions of *any* kind (both interactive and # non-interactive # session required pam_limits.so session required pam_unix2.so session optional pam_umask.so session optional pam_dbus_launch.so dbus-launch=/usr/bin/dbus-launch session optional pam_systemd.so session optional pam_kwalletopener.so maxwait=60 session_timeout=360 localwallet start_daemon kwalletopener=/usr/bin/kwalletopener session optional pam_gnome_keyring.so auto_start only_if=gdm,gdm-password,lxdm,lightdm
With these settings the pam modules work with any kind of useraccounts. Keep in mind that it will not work for automated logins where the system doesn’t actually prompt for a password.
The required pam modules can be installed from this OBS project.
Today, openSUSE 12.3 got released after 6 months of hard work by openSUSE members and contributors.
As usual, I’m doing a zypper live upgrade, but so far it’s still downloading packages, so I can’t say anything about 12.3 just yet.
I am going to post a review of the process and the results after it is finished. In the mean time, if you’re in the area (southern Germany), why not go to the release party in Nürnberg? It starts at 7pm at artefakt.
As announced on the Heise newsticker (article in german) the linux kernel version 3.8 has been released. If you look closely on kernel.org though, you’ll find that the latest stable version is still 3.7.9, but I don’t know if that’s because of something about the 3.8 kernel, or just because I looked there too early.
There are several interesting things in that version:
On the server-side the most important new feature, in my opinion, is the possibility to create namespace containers as a regular user. Such a container can be understood similar to a chroot jail, or a virtual machine, so that regular users can run privileged applications inside a container and not endanger the integrity of the system as a whole. Also there’s now a Ballon driver for Hyper-V which means that a Virtual Machine with a linux guest running 3.8 can release memory to the Windows host that runs it, and reclaim that memory later.
Also, there is improved support for the modern NUMA architectures, and lots of improvements for btrfs and ext4fs.
On the desktop the most important changes are better 3d hardware acceleration support with the Nouveau driver, a driver for Phillips PSC724 “Ultimate Edge” sound cards, and several improvements for DMA handling in regard with video streaming.
For mobile devices (and of course, servers and desktops with SSD storage) there is a new filesystem, f2fs, which is specifically designed for flash storage.
The upcoming openSUSE 12.3 release, which is scheduled for around mid-March, is still using the 3.7.7 kernel, or at least was last time I looked, and I don’t think the openSUSE team is going to switch kernels just 3 weeks before the gold master.
If you want to read about the 3.8 kernel in greater detail the kernel log on heise open is quite good (but in german).
KDE 4.10 has been released, and I have upgraded my old desktop computer that sits on a shelf in our home server room and runs a NoMachine server to have KDE 4.10.0 on it.
First attempt: migrate my existing KDE 4.9.5 desktop environment.
First result: failure. Basically nothing related to kontact/KDEPIM works after this.
Second attempt: delete everything kde related from that home folder (basically ~/.kde*, ~/.local and ~/.config) and try again.
Second result: after going through the “wizard”, kontact/KDEPIM still needs too many additional steps to be actually usable, but after that it sort of works. I have no idea how much of it will still work if ~ is on a nfs drive, though.
Overall opinion: I hope that KDE 4.10 has matured enough once openSUSE 12.3 rolls around with it as the default KDE desktop.
If you notice that your ssh agent and/or gpg agent aren’t running after logging in to KDE4 on openSUSE, and you just upgraded your KDE from the KDE:Release:49 buildservice repository, there is a simple fix.
Run this command as root:
ln -sf /etc/X11/xdm/Xsession /usr/share/kde4/config/kdm/Xsession
That will do it. By the way, the bug report for this bug is here. Please add your 2 cents worth if you are hit by it.