VirtualConfusion

Nothing serious!

KDE Neon on MacBook Pro

I have a MacBook Pro Retina 13" early 2015. I wanted to test the KDE NEON distribution on it.

After googling the best way to install it I found this article describing the different steps and it looked easy...

I first downloaded the User Edition Live/Install image.

I had some issues to write the image on a USB stick on Mac OSX with ROSA Image writer and decided to go with UNetbootin.

I decided to completely wipe out my OSX installation instead of having a dual boot. I just prepared a Sierra restoration USB stick in case things were going wrong.

I booted the macbook from the USB stick: Hold the Option (⌥) and choose the USB stick to boot from.

I first tested the live mode to see what are the potential problem I will face and nice surprise, the wifi chipset is supported out of the box, the magic mouse is recognized and paired (as my mouse is an apple magic mouse 2, the scrolling is not working).

I decided to install it and followed the normal installation of KDE Neon as on any PC.

So far I enjoy my KDE Neon on my MacBook.

My comments on the current setup:

  • Kmail is still not really a good email application, switching to Thunderbird, with firetray extension is a very good move.
  • Mouse sensitivity by default requires a bit of tweaking to be usable.
  • Screen size is providing much more place to have several windows opened but requires good eyes ;-)
  • I did not manage to have Scale Display setting working correctly.
  • LibreOffice on KDE is really ugly out of the box, I need to dig a bit around styles, but after a while I realized the Libreoffice version provided by KDE Neon is not the latest. Installing the latest Libreoffice (Fresh) gives a much better interface.
  • KDE Neon is working very well, no crashes or big issues.

Jabra Evolve Link headset problem with KDE neon

Connecting a Jabra Evolve Link MS headset to my KDE Neon laptop creates a problem by preventing my mouse & trackpad to stop functioning correctly.

This post helped me to understand the problem.

I just had to create the /etc/X11/xorg.conf file like this:

Section "InputClass"
Identifier "Jabra"
MatchUSBID "0b0e:0305"
Option "Ignore" "on"
EndSection

To find the correct MatchUSBID I just run the command dmesg to view the system message when I connected the headset to my laptop.

Forgot password on QNAP Linux VM

Reset of a forgotten password on a linux computer is quite easy when you have physical access to the machine.

The mandatory operation is to boot the machine in recovery mode. When running a VM it is quite difficult to reboot and get the prompt and change the boot option to a recovery kernel.

The solution is to go to the QNAP virtual machine console and click the Control-Alt-Delete icon to restart the machine.

control-alt-delete

Then you will be able to choose the boot option to recovery mode.

Once done you just have to type this command to mount the filesystem:

mount -rw -o remount /

and then:

passwd myuser

to reset the forgotten password.

Rise of dridex

There is currently a wave of phising emails sent to a lot of people, these emails are really well imitating a swisscom invoice (Swisscom being one of the main telecom service provider in Switzerland). The risk is to have the computer infected by Dridex type virus

There is a very good blog article made by a Swiss government organization in charge of alerting on internet risks which explains the attack, the consequences and the response.

Worth checking it…

Nextcloud virtualhost configuration

I was using the Qsync function of my Qnap NAS for several months, but I reverted back to a Nextcloud self hosted solution. The Linux installation guide made my life really easier.

The only problem I had was with the following error message:

Your data directory and your files are probably accessible from the internet. The .htaccess file that ownCloud provides is not working. We strongly suggest that you configure your webserver in a way that the data directory is no longer accessible or you move the data directory outside the webserver document root.

My solution was to remove Satisfy Any from the below virtualhost file

<VirtualHost XXXXX>
  DocumentRoot "/var/www/nextcloud"
  ServerName my.nextcloud.site

  ErrorLog ${APACHE_LOG_DIR}/error.log
  CustomLog ${APACHE_LOG_DIR}/access.log combined

  <Directory /var/www/nextcloud/>
    Options +FollowSymlinks
    AllowOverride All

    <IfModule mod_dav.c>
      Dav off
    </IfModule>

    SetEnv HOME /var/www/nextcloud
    SetEnv HTTP_HOME /var/www/nextcloud
    #Satisfy Any
  </Directory>
</VirtualHost>

Next step is to implement SSL.

Stranger Thing 2