I have seen a lot of posts where users are asking how to get a similar shortcut in KDE or other desktop environments.
The unicode shortcut, Ctrl + Shift + U, to insert special characters isn't a built-in feature in GNOME. It is a feature available from IBus, an input framework for Linux. Installing it along KDE or any other desktop environment will provide the feature. Use your distro's package manager to search for ibus and install the appropriate packages.
I expected disabling the single-click option in order to open files/folders in Dolphin to be straightforward and under Configure Dolphin, but alas that was not the case. It was not after several Google search that I got a hint that this is a system feature in KDE Plasma and not something specific to Dolphin.
How do we change it?
Type General Behaviour in Krunner and the option should be under Click behaviour.
I prefer to double-click in order to open files/folders.
I thought of putting this here in case someone else is looking for this. 😉
“The Linux User Group of Mauritius takes note of MITM measures on ICTA’s request for public consultation for regulating the use and misuse of social media in Mauritius.
From a technical perspective, the MITM proxy toolset involving a Certificate Authority not in the default trust store of major web browsers and operating systems will undermine the security model of Transport Layer Security and weaken the security of users on the Internet.
The proposed solution also poses issues such as not being compatible with the enhanced security mechanisms of some smartphones, and internet enabled-devices such as gaming consoles, smart televisions etc. For these technical reasons, the LUGM considers the MITM model in the consultation paper as bringing more negative results than perceived positive results”
The Information and Communication Technologies Authority (ICTA) is asking for public consultations on a framework to regulate use of social networks in Mauritius. One of the ideas is requiring Internet users using social networks to install as an ICTA-issued Certificate Authority certificate in their operating system or browser so that certificates can be issued for domains such as facebook.com. This is required to allow a Man in the Middle (MITM) proxy server intercept, decrypt, inspect, log, and/or block access to URLs. The public consultation paper is accessible on: https://www.icta.mu/docs/2021/Social_Media_Public_Consultation.pdf The public has up to May 20th 2021 to send their comments about the consultation paper to the email address contained in the PDF document linked above.
I generally have a lot of text files with such content:
Unlove this track
Playing the Angel
Unlove this track
The Singles 86>98
Unlove this track
These are the three tracks I have listened to most since I started using Last.fm way back in 2005.
What I want to achieve is to easily convert these 21 lines (3 x 7) into 3 tab-separated lines which can then be easily imported into, say, Libreoffice Calc:
1<TAB>Play track<TAB>Turn Around<TAB>Unlove this track<TAB>Panic Attack<TAB>Avinash Meetoo<TAB>110 scrobbles
2<TAB>Play track<TAB>Playing the Angel<TAB>Unlove this track<TAB>Precious<TAB>Depeche Mode<TAB>101
3<TAB>Play track<TAB>The Singles 86>98<TAB>Unlove this track<TAB>Personal Jesus<TAB>Depeche Mode<TAB>98
Previously, it would take someone new to the project quite some time to learn about the distributions and understand their differences. Not every new openSUSE user would know that it's ideal to use openSUSE MicroOS for single-purpose server hosting and Kubic for container orchestration with Kubernetes.
Thanks to a revamp of the openSUSE Project website, now the distributions get a dedicated page at get.opensuse.org.
A little work is still needed on the documentation part for each specific distribution. If you would like to help with that, you are most welcome. Join the openSUSE Documentation mailing list and coordinate with what's already being done to improve doc.opensuse.org or head to GitHub to have a look at the current opened issues. You will also find instructions on how to start contributing to the openSUSE Documentation.
For now, each distribution's individual page on get.opensuse.org points to the same official documentation guide which is Leap-centric. The documentation does not cover specific instructions for MicroOS, Kubic or even Tumbleweed.
Once you have created your account, we will need to find a region of lowest latency for us and the easiest way is to go to this website that runs the AWS latency test. https://ping.psa.fun/ . For Mauritius, it is the af-south-1 region (Cape Town, Africa) which has the lowest latency.
On the top right corner, choose your preferred region
From the console dashboard, choose Launch Instance.
The Choose an Amazon Machine Image (AMI) page displays a list of basic configurations, called Amazon Machine Images (AMIs), that serve as templates for your instance. Select an Ubuntu Server 20.04 (Free tier eligible).
On the Choose an Instance Type page, you can select the hardware configuration of your instance. Select the t3.micro instance type, which is eligible for the free tier. For more information, see AWS Free Tier.
Choose Review and Launch to let the wizard complete the other configuration settings for you.
On the Review Instance Launch page, under Security Groups, you'll see that the wizard created and selected a security group for you. You can use this security group, or alternatively you can select the security group that you created when getting set up using the following steps:
Choose Edit security groups.
On the Configure Security Group page, ensure that Select an existing security group is selected.
Select your security group from the list of existing security groups, and then choose Review and Launch.
On the Review Instance Launch page, choose Launch.
When prompted for a key pair, select Choose an existing key pair, then select the key pair that you created when getting set up. Warning Don't select Proceed without a key pair. If you launch your instance without a key pair, then you can't connect to it. When you are ready, select the acknowledgement check box, and then choose Launch Instances.
A confirmation page lets you know that your instance is launching. Choose View Instances to close the confirmation page and return to the console.
On the Instances screen, you can view the status of the launch. It takes a short time for an instance to launch. When you launch an instance, its initial state is pending. After the instance starts, its state changes to running and it receives a public DNS name. (If the Public DNS (IPv4) column is hidden, choose Show/Hide Columns (the gear-shaped icon) in the top right corner of the page and then select Public DNS (IPv4).)It can take a few minutes for the instance to be ready so that you can connect to it. Check that your instance has passed its status checks; you can view this information in the Status Checks column.
Connecting to your newly created Ubuntu Instance
Open an SSH client.
Locate your private key file. The key used to launch this instance is nu-server.pem
Run this command, if necessary, to ensure your key is not publicly viewable. chmod 400 *.pem
Connect to your instance using its Public DNS as provided in your dashboard
I tweeted about a blog post which I published on opensuse.mu, explaining how I configured the GNOME desktop theme Yaru (by the Ubuntu community) on my openSUSE Tumbleweed machine. The tweet got a lot of reaction, not just for the blog post or cool Yaru theme but also for the nice wallpaper showing penguins using a computer.
Ever since Red Hat announced that they are changing the development model of CentOS and making it an upstream project rather than downstream, it left many CentOS users frowning. No matter what argument brought forward, CentOS users, especially running production machines, relied on the stability of an enterprise-grade Linux distribution. Compiled from RHEL sources, CentOS offered such stability that it powered many web servers and enjoyed a massive 20% share of the top 500 supercomputers of the world.
Some time back, Red Hat made another annoucement, about new Red Hat Enterprise Linux programs. Under the new program RHEL can be used in production for up to 16 systems (which Red Hat considers a small workload) at zero license costs. Also, Red Hat is making it easier for a customer's development team to join the program and reap the benefits.
What risks lie ahead for an enterprise if Red Hat changes or cancels the program in the future? 🤔
On the other hand, since 2018, SUSE has worked closely with the openSUSE community to bring the Leap distribution closer to SUSE Enterprise Linux (SLE), such that now Leap and SLE are binary compatible.
openSUSE currently offers two distinct distributions, Leap & Tumbleweed.
Tumbleweed is a rolling distribution constantly getting updated software whereas Leap has planned releases that sync with SUSE Linux Enterprise and its Service Packs.
The above image depicts how openSUSE & SUSE Linux Enterprise are developed together. Factory is the rolling development codebase for both openSUSE & SLE. In the pipeline we can see that Leap & SLE are synced and both receive software packages from the same source; that is why they are both binary compatible.
Red Hat allows its clients to use RHEL for free on up to 16 machines. On the other hand, openSUSE Leap boasts binary compatibility with SUSE Linux Enterprise and comes without any restriction on usage.
I am using the SOGo Groupware. I noticed that certain emojis in the event title would prevent calendar apps from synchronizing using the CalDAV protocol. I checked the logs but could not find much. I had my doubts about what could be causing it. Then, this bug report confirmed that I should investigate on the UTF-8 encoding support.
I checked the database character set.
MariaDB [sogo]> select @@character_set_database;
| @@character_set_database |
| utf8 |
1 row in set (0.001 sec)
The database name is sogo and we are using MariaDB.
I found the character set to be utf8, to my surprise. I had to dig a little further to understand what was wrong with it.
It turned out that the MariaDB utf8 character set supports a maximum of three bytes per character. Therefore, emojis being four bytes long weren't being inserted into the database. Consequently, that breaks the calendar synchronization. The solution was to use the utf8mb4 character set which supports four bytes per multi-byte character.
I altered the database character set and collation.
MariaDB [sogo]> ALTER DATABASE sogo CHARACTER SET = utf8mb4 COLLATE = utf8mb4_unicode_ci;
I also applied it to every table in the database, e.g:
MariaDB [sogo]> ALTER TABLE sogo_store CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
Afterwards, I could create events using an emoji in the title. The event would synchronize across my calendar apps but the emoji would not show. It would appear as four questions marks (????) instead.
A little bit of further digging and I found that SOGo needs to be made aware of the full unicode support. It should be specified in the /etc/sogo/sogo.conf configuration file.
MySQL4Encoding = "utf8mb4";
Restart the SOGo service. Emojis should be then accepted in the event titles.
I can now put my recurrent coffee breaks in the calendar. ☕