24. July 2019

Creating Python virtualenv fails with error: Could not find a suitable TLS CA

You can create Python virtualenv using command:

virtualenv -p /usr/bin/python3 py-env3

You may encounter following strange error:

  Collecting setuptools
Exception:
Traceback (most recent call last):
  File "/usr/share/python-wheels
...
OSError: Could not find a suitable TLS CA certificate bundle, invalid path: /etc/ssl/certs/ca-certificates.crt
...
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 145, in apport_excepthook
    os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/var/crash/_usr_bin_virtualenv.1000.crash'

The error message is not very clear. Problem is caused by ca-certificates and it could be fixed by command:

sudo update-ca-certificates

Posted in Software engineering (Tags: , , , ) | Comments Off on Creating Python virtualenv fails with error: Could not find a suitable TLS CA

21. February 2019

How to run openSUSE for PowerPC64LE on CPU x86_64

First of all install required package for running ppc:

sudo zypper install qemu-ppc

Download the ISO built for PowerPC architecture (ppc64le). E.g. openSUSE-Leap-42.3-NET-ppc64le-Build0130-Media.iso.

Create file which will contain disk image:

qemu-img create suse.img 10G

Now, start the ppc64le virtual and boot from cdrom:

qemu-system-ppc64 -boot d -cdrom openSUSE-Leap-42.3-NET-ppc64le-Build0130-Media.iso -m 1024 -hda suse.img

After the installation you can simply run the installed system:

qemu-system-ppc64 -m 1024 -hda suse.img

Note: -m 1024 stands for “memory 1 GB”

Posted in Software engineering (Tags: , , , , ) | Comments Off on How to run openSUSE for PowerPC64LE on CPU x86_64

20. February 2019

openSUSE firewall – YaST cannot continue the configuration

When you want to configure the firewall on openSUSE you can just type yast into the terminal.

Select Security and Users and from options select Firewall.

On fresh installation of openSUSE you might encounter following error:

Error
YaST cannot continue the configuration
without installing the required packages.

The fix is simple, just install yast2-firewall:

sudo zypper install yast2-firewall

Now you can start YaST and the firewall configuration will work.

Posted in Software engineering (Tags: , , , ) | Comments Off on openSUSE firewall – YaST cannot continue the configuration

28. July 2018

Unable to shut down Windows on computer with Linux dual boot

After installing Linux in dual boot on the computer with Windows you may experience a strange problem. It’s no longer possible to shut down the computer from Windows. The computer immediately re-spawns to the Windows login screen.

The issue is most likely caused by booting Windows from the incorrect bootloader. If you have two partitions (sda1, sda2) on the system, make sure that you’re booting Windows from the one with the operating system.

Booting from incorrect partition could cause other strange errors, like problems with updating Windows. You can read more in the article: Failed to install Feature update of Windows 10, version 1803 on machine with Linux dual boot.

Posted in Software engineering (Tags: , , , ) | Comments Off on Unable to shut down Windows on computer with Linux dual boot

28. July 2018

Failed to install Feature update of Windows 10, version 1803 on machine with Linux dual boot

I was chasing a very strange bug for a long time: Windows 10 was not able to install any feature update.

Update history in Windows contained just a message:

Feature update to Windows 10, version 1803
Failed to install on ‎2018-‎05-‎24 - 0xc1900101

To keep the long story short: I was starting Windows by the incorrect bootloader.

Grub from Linux Mint auto-discovered two Windows partitions /dev/sda1 and /dev/sda2. The first partition was just a small partition with bootloader from the previous installation of Windows. When booted by “chainloader +1” the boot automatically kicked in and started Windows stored on the second partition. Unfortunately it had an impact on updates and shutdown of the computer.

The correction was quite simple. Just start Windows from the second partition.

I rebooted the computer from sda2 partition and then I started the new installation of Windows 10, version 1803 update using Windows 10 Upgrade tool.

This correction also fixed another strange bug, that I was not able to shutdown Windows. When I selected “shutdown”, Windows respawned in a few seconds back into login screen. Again the problem was that old bootloader from the first partition kicked in, after the shutdown of Windows and resumed it.

Big thanks to Max Green for pointing out that the problem might be caused by invoking incorrect bootloader.

Posted in Software engineering (Tags: , , , , , , ) | Comments Off on Failed to install Feature update of Windows 10, version 1803 on machine with Linux dual boot

« Previous Entries
Next Entries »