Sep 142016

I upgraded my laptop to Leap 42.1 the other day, using the good old method that I’ve been talking about a few times. Worked without major issues, I just had to manually fix the repository URL in a couple of the repositories I’m using.

Now I’m on 42.1 using Plasma 5, and so far I mostly like it. A few features and settings have gone from parts of the kdepim suite, and there is one weird glitch-error where starting kopete gets me a weird “file: ioslave has been terminated” error, that I’m sure is somehow related to kopete styles. Maybe when I’ll do my desktop I’ll do the upgrade to Leap first, and then the upgrade to the latest plasma5, and not the other way around like on this laptop.

On the whole I’m happy with what I have here.

One little thought just keeps nagging me:

How come that Plasma 5 with the breeze style looks a LOT like Windows 10? …, wait, Windows 10 came after Plasma 5, right?

Edit, 2016-09-14: Turns out I should have done the upgrade to Leap 42.1 first, and THEN the KF5 update. I had some repositories enabled that should not be mixed. Disabled the bad ones, zypper dup -l, all is well.

 Posted by at 08:29
May 142016

I just finished a major heart surgery on my laptop. Many thanks to the guys who made some youtube tutorials about taking that laptop apart! The Acer E5-571G is definitely NOT built to be taken (apart) lightly (Here is the german tutorial that I was following, and here is an english one).

After swapping out the 2x 4G memory modules for 2x 8G ones, and the 1TB laptop hard disk drive for a 1TB SSD disk, and putting everything back together, the real fun began.

  • install the old harddisk in an external USB3.0 harddisk enclosure (the drive was still good after all)
  • boot from a Windows 10 installer
  • partition the disk and install Windows 10 in about half of the available space
  • the usual windows installation hijinx: install a driver, reboot, repeat ad nauseam
  • when windows is about done with the initial installation stuff, plug in the old harddisk on USB3.0 and copy the data from your old user account to your new

Then the linux fun begins, but be aware that this method will only work if the existing linux installation on the old disk was based on a LVM setup!

  • boot from openSUSE 13.2 installer DVD, but boot into rescue mode!
  • partition the unused space on the new disk as follows:
    • 250MB /boot
    • one LVM physical volume from the remaining space, but do not create the actual PV yet
  • plug in the old disk again
  • mount the /boot partition from the old system somewhere
  • create ext4 filesystem on the new /boot partition, and mount it somewhere
  • rsync the content of the old /boot to the new one
  • unmount the old and new /boot partitions
  • check that you can see and access your old logical volumes via the usb3 connection to your old disk (lvs, lvdisplay, vgs, vgdisplay, pvs, pvdisplay)
  • now create a PV on the new partition that you created a few steps ago
  • add that PV to the volumegroup on your old disk
  • move all used extents away from the old disk with pvmove
  • once this is done you can remove the pv that is located on the old disk, unplug the disk and use it for something else.
  • make sure the /boot partition on the new disk is not mounted
  • mount your root volume to /mnt
  • prepare your mounted root for chroot
    mount -o bind /dev /mnt/dev
    mount -o bind /sys /mnt/sys
    mount -o bind /proc /mnt/proc
  • Change into your installed system with chroot
    chroot /mnt /bin/bash --login
  • Edit /etc/fstab, make sure all references to mounted filesystems are correct (partition label/identifer for the EFI partition, UUID for /boot, etc)
  • regenerate the initrd with mkinitrd
  • recreate the grub2 configuration with grub2-mkconfig
  • reboot, enter the BIOS setup, go to the UEFI boot settings and make sure the boot order is correct and secure boot is OFF.
  • the next reboot should get you into a working GRUB2 that lets you boot linux but not windows, so boot linux, start yast2 and reinstall the grub bootloader again from there.

That’s it folks!

Jan 092015

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.

Dec 022014

I have suggested firewalld from fedora/RHEL7 for inclusion in openSUSE, as an alternative for SuSEfirewall2 for setups with highly volatile networking.

test rpm packages for openSUSE 13.2 can be obtained here:





You will also need to enable the repository from here to get the dependencies.

Nov 232014

I’ve done it again… a live upgrade from openSUSE 13.1 to 13.2.

I’ve been following the usual process that I’ve outlined in a few posts so far, and it went pretty smoothly on three different computers.

The actual process has evolved into this:

  1. run this script (after editing to fix the version numbers):
    mkdir -p ${newrepodir}
    cd ${repodir}
    for repofile in *repo; do
        echo -n converting ${repofile} to ${newrepodir}/$(echo ${repofile}|sed -e "s/${old}/${new}/g") ... ;
        cat "${repofile}" | sed -e "s/${old}/${new}/g" > "${newrepodir}/$(echo ${repofile}|sed -e "s/${old}/${new}/g")" ;
        echo done.
  2. move /etc/zypp/repos.d out of the way, for example rename it to /etc/zypp/repos.d_old
  3. move /etc/zypp/repos.d_13.2 to /etc/zypp/repos.d
  4. clean zyppers cache:
    zypper cc --all
  5. refresh zypper:
    zypper ref

    When you do this, you might get errors for some repositories because they don’t exist yet for 13.2. To disable them, do this:

    zypper mr -d -R 

    On the other hand you might want to investigate if there are 13.2 versions of those repositories, and edit the repo files accordingly.
    Then, repeat the zypper ref command.

  6. Once you can run through zypper ref without errors, get updated versions of zypper, libzypp and rpm, and install them:
    zypper up --download only zypper libzypp rpm
    zypper up zypper libzypp rpm
  7. Once that finished without errors, do the same two commands for the whole distribution (Pay attention to any warnings and/or conflicts here. You’ll have to make the right choices about what should be done to resolve them, and I can’t really give you a recipe):
    zypper dup -l --download only
    zypper dup -l
  8. After all is done you can reboot. The first reboot should lead into textmode in case you have to re-install/upgrade your nvidia or AMD binary drivers. To boot into text mode, append this kernel parameter:

Have a lot of fun!

Jun 252014

Lately I’ve noticed a trend in mobile apps that started on iOS, and even is understandable there due to the sandbox nature of that os.

“Every mobile app will continue to evolve until it contains a web browser, antivirus, and anti theft features, no matter what is initial purpose was.”

In German we call that “eierlegende Wollmilchsau“.
An animal that produces wool, milk, eggs, and meat.
Sure would be nice to have for a farmer, but can’t be done.

So what is the connection to mobiles?

Well, look at this: right now I have on my tablet the different apps that can provide me with anti theft services, but only one of them had that when I installed it.
Same goes for anti virus, two of those, only one had such a feature when I choose to install it.
Or how about memory and storage cleaning… two again, one when I started with them.

Like I said, on iOS this can be understood, since the sand box nature of ios separates apps from each other to a much higher degree than on android…

But android should be different, its Unix after all, where the long standing tradition is to have small tools that do one job really well, and let them talk to each other.

May 312014

In my never ending story for single sign on on KDE4 the last post I had was this one.

There was just one little problem with that method: It stopped working when KDE 4.13 came around…

Now there is a new candidate for solving this, and it works just fine so far.

At this point all I can say is that anyone interested should read this blog post, and that the pam_kwallet package in my OBS project has been updated to the code in that post.

Have a lot of fun!

Dec 282013

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.

Optimization WordPress Plugins & Solutions by W3 EDGE
%d bloggers like this: