Opensuse 42.2 emergency mode after install

Reinstalling my system, clean install of OpenSuse 42.2, but then at boot, after passing grub and kernel selection, it logs into the emergency shell.

Fokkow instructions in shell, give root password, and look for errors from logs using systemctl -xb 

It turns out that it was not able to mount /home

Checked /etc/fstab and the filesystem type was marked as unknown.

Edited to ext4, save, reboot, and Presto!


Running BOINC on OpenSuse

Notes on how to run BOINC on Opensuse (Leap 42.2) from command line as deamon.

Install the packages from packman repository

zypper in boinc-client boinc-manager

After installation verify that user and group boinc is created

cat /etc/passwd | grep boinc

cat /etc/groups | grep boinc

Add the user boinc to the group boinc.

usermod -G boinc -a boinc (repeat with any other user if necessary)

verify that boinc-client is already running as a daemon

ps -aux | grep boinc or systemctl status -l boinc-client.service

verify that all files under /var/lib/boinc are owned boinc:boinc

change permissions of /var/lib/boinc/gui_rpc_auth.cfg 

chmod 664 /var/lib/boinc/gui_rpc_auth.cfg

Optional, create simbolic link for user account logged in while running boinc

ls -s  /var/lib/boinc/gui_rpc_auth.cfg /home/<user>/gui_rpc_auth.cfg

Now, if previously attached to a project, retrieve your key:

boinccmd –lookup_account <project url> <email> <password>

Or create an account if needed:

boinccomd –create_account <project url> <email> <password> <name>

Attach to the project

boinccmd –project_attach <project url> <key>

Voila! you should be running now as a daemon and connected to the project.

Verify by issuing:

boinccmd –get_project_status or boinccmd –get_state

OpenSuse Linux, Citrix and Certs

I needed to remote in from my personal laptop running OpenSUSE Leap 42.1 into my work’s Citrix Remote Desktop runnin on a Windows Server farm.

After logging in, install the Citrix Reciever from your Citrix server (if provided), or from Citrix directly.

My version of receiver is 11.100 for linux x86.

The Linux installation is straight forward, accept the defaults.

Now, the tricky part.

Upon logging in and launching a RDP session, I received the following error message:

You have not chosen to trust “XXXYYY”, the issuer of the server’s security certificate (SSL error 61).

Upon some googling I decided to go to my certificate provider XXX, and download their Public Root Certificate Bundle.

After opening the tar file, found the certificates of type YYY. Then copied those certificates into the path of my Citrix Reciever installation, in my case:



btrfs adventures on opensuse

I am currently using OpenSuse 13.2, and started using Picard for sorting my music, around 12000 files. Later I started doing some BASH script to further clean up the names of the mp3 files.

Anyhow, all of this to say, that I have been working the file system, copying, moving and erasing (hundreds) of files around.

At the end, the system started to be very slow, and at some point, gnome started to crash, funny enough, there is no /var/log/messages to check, 13.2 implements Systemd, so there is journalctl to check the error messages, but in the console (F12) many errors for different systemd components complaining that there was no space left on device, but doesn’t says which one, and doing a “df -h” shows still free space on the hard drives.


At the end, the OpenSUSE forums gave me the solution on this thread.

If you keep reading, the problem is not the file system, it the meta data of the file system.

The default file system of OpenSuse13.2 is btrfs, which implements journalling and snapshot capabilities, and if not correctly tuned and configured, can generate this kind of scenarios.

The key commands to fix my issues were:

btrfs filesystem show

btrfs filesystem df (here you can see the meta data space full)

snapper -c root list (lists snapshots of root the file system)

snapper -c delete (this will clean the snapshots of the file system that are taking space, leaving the current one (0) and the last one)

btrfs balance start (in my case / for root, the closest explanation this is similar to a defrag>

Et Voila! space magically appears, and system is usable again.

Similar case, with explainations from “The Nerdy Room“.

OpenSUSE, Handbrake and VLC

After installing OpenSUSE, in order to have access to more software, a common step is to add the "Packman" repository from the communtity.
One big advantage is that it provides many linux applications ported to Open Suse.
One of them is Handbrake for video re-coding into other formats.
One problem is that Handbrake won’t open most DVDs because it lacks the libdvdcss library used to decode the DVDs.
This library could not be installed on it’s own from the repositories.
A solution, install VLC following the instructions from the project web page (there are specific instructions for SUSE), add their project repository, install VLC, and install the libdvdcss library.

Presto! Now Handbrake will open most DVDs.

Happy Encoding.

XBMC on Open Suse

My current setup is my Desktop PC, with an AMD A5 processor which has an integrated Radeon HD7000 series video processor.

I am running Open Suse 12.2 “Mantis”, included the “packman” repository and installed XBMC 11 “Eden”.

When I upgraded XBMC 11 from “Eden” to XBMC 12 “Frodo”, when executing xbmc I had an error sort of “unresolved symbols”.

After uninstalling and reinstalling XBMC and doing a Zypper Update, to no avail.
I also did a Zypper Install New Recommends, also unsuccesfully.

Finally I fixed the issue by doing a Zypper Distribution Upgrade, this changes the ownership of some libraries from the main Open Suse reposotory to the Packman repository, removes an offenting library, and re-installs with a previous version.

Et Voila!

XBMC 12 Frodo working on OpenSuse 12.2 Mantis.