I've tried clearing the cache, the data, reinstalling, etc. Same behavior every time.

If this also happens to you, your watch and phone probably won't connect to each other as well. Which is quite annoying.

The reason, apparently, it's because we're now on 2024! 🎉 The app seems to have a bug, unfixed until today, related to the year.

The solution: Change the date on your phone to 2023 (for example, 31/12/2023), and try to re-open the app. It should work!

Now connect your watch, go to the hamburger menu on the left and check if you have an update for the app or for the Galaxy Watch Plugin. Do the update.

Now you can restore the date on your phone to the correct one and the app should stop crashing!

🤦‍♂️

I'm currently using Kubuntu 23.04 on my desktop, with KDE Plasma 5.27.4, and Kernel version 6.2.0-27. I also use a Logitech G502 Lightspeed, wirelessly.

Sometimes, without an apparent reason and without any obvious pattern, the scrolling gets painfully slow, everywhere! I haven't been able to figure out why, nor how to fix it without a system reboot.

Not anymore! The "fix" is much easier! You just need to turn off the mouse, and turn it on again. 😒 The red arrow marks the spot:

OK, I know that's not a fix, but it's much easier and faster than a reboot.

Hope this helps someone having the same issue. 👋

#
# You can verify the status of security fixes using the `pro fix` command.
# E.g., a recent Ruby vulnerability can be checked with: `pro fix USN-6219-1`
# For more detail see: https://ubuntu.com/security/notices/USN-6219-1
#

I don't want or need useless information on my terminal, and removing it is quite simple. Just run the following command:

sudo pro config set apt_news=false

Now you're back to the regular APT behaviour.

Device manager was showing the following Hardware ID's:

vid_0000&pid_0002

I didn't want to waste a lot of time with this and went straight to a reboot. Which, as you can guess, didn't solve the issue. The second step was a full shutdown, followed by another boot. Still no Bluetooth.

Well, long story short, if you have encountered this type of issue, try this:

• Turn off your computer, turn off the button on your power supply (or take off the power cable), and press the power button on your desktop for around 10 seconds, to drain the remaining power of the components. After those 10 seconds just reconnect everything, turn on the computer and it should be working again!

🎮

And without using the command line, if that's not your jam. With a fast, one-time configuration, you can have a shortcut in Thunar (the default File Manager for XFCE) that allows you to right-click any file and restore it to a previous version.

I'm assuming that you have a working Déjà Dup backup. I use it with my Nextcloud instance, take a look here for a quick tutorial.

First open a Thunar window.

• Go to Edit and Configure custom actions...
• Click the + sign on the right side.
• Fill up the Name, Description and Command fields. The command should be:

deja-dup --restore %F

• Select an Icon if you like. It will show up on your context menu.
• Click on the Appearance Conditions tab and select all 6 boxes.
• Click on Ok.

It looks like this:

And that it! Now when you right click on a file or folder you should have a an option with the name Restore previous version (or any name you choose), and you just have to click it, select the backup, the date and it will be restored!

I've tried to use the Flatpak version of it, as described here, but I had some issues opening a local revelation file (something related to the way that Flatpak works), so that wouldn't cut it.

The alternative is getting the Ubuntu 21.04 version working on 20.04.

First install the required dependencies.

$ sudo apt install python3-pycryptodome python3-pwquality python3-cracklib

Then get the .deb file from the Ubuntu repositories.

$ cd /tmp && wget http://archive.ubuntu.com/ubuntu/pool/universe/r/revelation/revelation_0.5.4-3_amd64.deb

And install it.

$ sudo dpkg -i revelation_0.5.4-3_amd64.deb

And you're done!

P.S. You can also build it from source. The instructions are here.

Depois de perder algum tempo a tentar alterar o PIN do meu cartão Curve em duas ou três máquinas multibanco, resolvi procurar um bocadinho na internet e ver se era possível / como o fazer. Perdi mais tempo do que o desejado, mas lá encontrei.

Resumindo, em Portugal 🇵🇹 é possível mudar o PIN do cartão Curve nas máquinas da Euronet.

Há algumas em Lisboa, pelo menos. Basta procurarem "euronet" no Google Maps e devem obter as caixas mais próximas da vossa localização.

A partir daí é fácil, basta seguir as indicações no ecrã.

Nota: Estas instruções também são válidas para o cartão da Binance.

You can embed GitHub gists on your Ghost blog and make it look good by doing the following:

• On your post editor click the "+" and select "HTML":

• Then paste then following:

<script src="https://gist.github.com/<YOUR_GITHUB_USERNAME>/<YOUR_GIST_ID>.js"></script>

And you'll get something like this:

Beautiful. Don't forget the .js at the end.

If you want to remove a host from your BackupPC server you'll need to take the following steps.

1. First delete the host from the GUI. Go to Edit Hosts and delete the host you want. Click Save.

After that you'll need to login to your server and remove the folder where the backups are kept. By default BackupPC is installed on /var/lib/BackupPC/, and your machines should be on /var/lib/BackupPC/pc/.

2. Stop the BackupPC service:

$ sudo systemctl stop backuppc

3. Remove the folder of the host you want to delete:

$ sudo rm -rf /var/lib/BackupPC/pc/<my-host>

4. Run the nightly script (probably you'll need to run it as the backuppc user):

$ su - backuppc
$ /usr/share/BackupPC/bin/BackupPC_nightly 0 255

5. Start the BackupPC service again:

$ exit
$ sudo systemctl start backuppc

And now the host is removed.

When using Windows or Gnome I'm used to open the Applications menu with my Windows (Super) key and start typing away to open my programs.

Well, Xubuntu by default doesn't do that. So here are the steps to make it happen.

1. Open the Settings Manager:

$ xfce4-settings-manager

2. Look for Keyboard (or use the search on the top).

3. Choose Applications Shortcuts:

4. Click on Add.

5. On the Command write xfce4-popup-whiskermenu. Click Ok.

6. When it asks to press a key use your Windows key.

7. There is no step 7. It's done!

Now my muscle memory won't fail me when DE hopping.

If you're using BackupPC, and you're trying to backup a server that is behind a firewall and does not reply to ping, BackupPC will not start the backup, even if you have the SSH port open.

No ping (no ping response from) ...

You can override this behavior and force the backup by selecting the host on the web interface, then going to "Edit Config" and replace the default "PingCmd" command with:

/bin/echo

Check the override box and save. Now the next scheduled backup will run without an issue.

I'm using an wireless headset (HyperX Cloud Flight Wireless Gaming Headset) that has an USB receptor and some old Logitech speakers on my desktop, currently running Ubuntu 20.04 (dual booting with Windows 10).

Every time I reboot or turn on my computer and boot Ubuntu the default output audio device is set to my headset, which most of the time is off (I only use it when gaming).

Going to Settings - Sound and choosing the correct output device (Line Out) only changes it for the current session.

You can solve this by doing the following:

Edit the file default.pa:

$ sudo vim /etc/pulse/default.pa

And comment the following lines:

#.ifexists module-switch-on-connect.so
#load-module module-switch-on-connect
#.endif

Reboot. Now your computer should leave the output device you select in settings alone. My guess is that every time you turn on the computer it finds the USB receptor and change to it.

Grocy is a web-based self-hosted groceries & household management solution for your home.

I already have a few services running on my home server, sitting behind my faithful Apache, accessible from a custom domain.

I don't want it running as a subdomain. Every explanation I found assumes that.

TL:DR: If you want Grocy running behind an Apache proxy, on your own subdomain, set it up like this:

• Get Grocy:

$ cd /tmp
$ wget https://releases.grocy.info/latest
$ sudo unzip latest -d /var/www/html/grocy/

• Copy the Grocy configuration file and change it to your liking:

$ sudo cp /var/www/html/grocy/config-dist.php /var/www/html/grocy/data/config.php

• The important settings here are:

Setting('BASE_PATH', '');
Setting('BASE_URL', '/');
Setting('DISABLE_URL_REWRITING', false);

And they should be setup just like that for what we are looking to accomplish.

• Create a configuration file in Apache for Grocy:

$ sudo vim /etc/apache2/sites-available/grocy.home.your-domain.pt.conf

• Adapt the following to your configuration. The relevant part here is the DocumentRoot, and the Directory. Don't forget to set the full path to the Grocy public folder:

<VirtualHost *:80>
    ServerName grocy.home.your-domain.pt
    ServerAdmin your-name@your-domain.pt
    DocumentRoot /var/www/html/grocy/public
    ErrorLog /var/log/apache2/grocy-error.log
    CustomLog /var/log/apache2/grocy-access.log combined

<Directory /var/www/html/grocy/public>
    Options Indexes FollowSymLinks MultiViews
    AllowOverride All
    Require all granted
</Directory>
</VirtualHost>

• Enable the site:

$ sudo a2ensite grocy.home.your-domain.pt

• Reload Apache:

$ sudo systemctl reload apache2

And your instance if running on http://grocy.home.your-domain.pt!

I've made a few assumptions here (you have your own local domain, have Apache already setup with PHP, etc), but I hope is helpful to someone.

Maybe later I'll update this post with a more detailed explanation.

When this situation occurs, you can unblock them using the gitlab-rails console directly in the server.

Run the following:

$ gitlab-rails console production

And then inside the console you can find the user by email and set it to "Active" like this:

> user = User.find_by_email("[USER-EMAIL]")
> user.state = "active"
> user.save
> exit

Replace [USER-EMAIL] with the actual email you're looking for. The user should now be active and ready to login.

Installing Pi-hole on a CentOS 7 server (instead of a dedicated machine like a Raspberry Pi) is an option that the fine gentlemen who developed it gave us. Since I already had a server ready with Apache, I took that route.

I have a small Optiplex 3040 that I use as my home server (you can read more about what I use here) and decided that I’ve had enough with ads showing up on my devices. On my desktop and laptop I use uBlock Origin but my other devices don’t have that luck. Enter Pi-hole!

It’s actually quite easy to install it using Apache (the default setup is even easier, and well documented). It goes like this:

• Setup your server with a static IP. That is out of the scope of this post but you can find out instructions for CentOS 7 here.
• Run the install script as root: curl -sSL https://install.pi-hole.net | bash.
• If you got the chills from the previous command, I understand perfectly. You shouldn’t run scripts directly from the internet. Check the script before you do it. You can find it here.
• The relevant question of the script is if you want to install the lighttpd web server. You should answer *no* at this step.
• Now that the setup is over, proceed to install Apache and some necessary software for Pi-hole: yum install httpd php php-pdo.
• Edit the file /etc/sudoers.d/pihole and replace lighttpd with apache.
• Set SELinux to permissive (unfortunately it seems that Pi-hole doesn’t work too well with it). You shouldn’t do this if you don’t trust the security of your server or your network. Edit the file /etc/sysconfig/selinux and replace enforcing with permissive.
• That should do it! Reboot your server just to ensure everything is fine and go to http://YOUR_STATIC_IP/admin to check your new Pi-hole installation.

There are a few more things you can do, like setting up a Name-based Virtual Host:

• Create a new configuration file on /etc/httpd/conf.d/router.home.example.com.conf

Insert the following example (adapt it to your use):

<VirtualHost *:80>
ServerName router.home.example.com
DocumentRoot /var/www/html/admin
</VirtualHost>

Restart the Apache daemon:

systemctl restart httpd

You should now be able to access your Pi-hole dashboard using the name router.home.example.com. This assumes you have your own DNS Server at home. I’ll make a post about setting up one, but for now, you can look here for instructions.