Hi All, I will start this one with `how busy I've been` excuse that I wasn't even aware about the ongoing **grub 2:2.06.r322.gd9b4638c5-1** issue.

***

**Symptom**: Unable to boot system after upgrading to grub 2:2.06.r322.gd9b4638c5-1

**Cause**: As per user "dalto" on FS#75701, this  seems to be related to the changes to 30\_uefi-firmware, where a call to fwsetup was added to the code.

**Resolution**: As on 31st Aug, there's no direct resolution to this issue, however there's a workaround, which is (also proposed by user dalto on 26th Aug 2022):

Either install Arch on a UEFI machine and follow the below steps after upgrade *or downgrade grub* on a non-uefi machine.

1\. Update grub

2\. Run `grub-install` followed by `grub-mkconfig`

3\. Reboot and it should work, if not then from the boot menu, select your boot partition (usually the name of your distro)

**Notes**:

The first bug report was registered on 22nd Aug 2022, link to the issue is: [FS#75763](https://bugs.archlinux.org/task/75673)

The second report was on 26th Aug 2022, link to the issue is: [FS#75701](https://bugs.archlinux.org/task/75701#comment210566) (proposed work around can be found here)

Have a good one!

DN-debug


GRUB Borked Arch and its derivative systems

Recent blog posts section example

Discontinuing Gnome ISO

How to enable power-management on WMs?

This has been a known issue for 
sometime and I didn't get time to address this properly. So what is the 
issue that I'm talking about?

Brief:

During the 
installation, when "swap with hibernate" option is selected, the 
installer fails to complete the installation, only a handful of such 
cases are known to me atm.

I am currently not aware of the cause 
behind this, it could very well be a "Calamares" issue, or could be some
 "dependency" issue, as there's no configuration changes done yet hence 
can't call it a configuration issue either, but I am not sure at this 
point as I didn't test it.

Solution ( alternative ):

There are two alternatives to this problem, that too, if you really want to use hibernation:

1.  Use "swap to file"

2.  Manual partition with swap enabled.

Remember
 that when you'll use "swap-to-file", you will have to make manual 
confiuration changes for the hibernation to actually work. Suspend will 
work oob. 

Hope that works.

Cheers!



Installer fails -- swap issue

This post is solely for pure 
arch-based systems such as Peux OS itself, that does not ship the custom
 mirror-list. When these pure arch-based systems are outdated the system
 upgrade process would become a little hectic for people who don't know 
what to do next, for example, if you use any couple of months ol Peux OS
 ISO then after installing the system, you most likely won't be able to 
update/upgrade the system.

The reason is simple, Arch routinely 
updates its mirror-list and keyrings, which when encounters the 
unmatched and outdated keyring or mirror-list in the system \[ that 
doesn't match with the one in the 'Servers'], fails to pull the database
 information into the system. At some point it might even  try to update
 the pgp key value during the upgrade process but would most likely 
fail.

The below steps would help you upgrade the outdated systems smoothly:

1.  Go to 

    [Pacman Mirrorlist Generator](https://archlinux.org/mirrorlist/)

     website and select the country of your choice then generate the mirrorlist.

2.  Launch the terminal, then open the '

    **/etc/pacman.d/mirrorlist**

    ' file with root privileges in the text editor of your choice. For example, if I want to use leafpad, I'd type: "

    **sudo leafpad /etc/pacman.d/mirrorlist**

    " or to use kate, I'd type "

    **kate /etc/pacman.d/mirrorlist**

    ".

3.  Remove the contents of the 

    **mirrorlist**


     file and paste the newly generated mirrorlist from Step 1 into this 
    file. Remove the hash symbols "#" in front of the lines that says "

    **Server**

    ". Save and exit.

4.  Now in the terminal, we will update the database and install the package "archlinux-keyring" using the command : "

    **sudo pacman -Sy archlinux-keyring**

    ".

5.  Once done, populate the keys using the command : "

    **sudo pacman-key --populate archlinux**

    ", followed by "

    **sudo pacman -Syy**

    ".

6.  Now you should be good to go, run "

    **sudo pacman -Syu**

    " to upgrade the system.

**\*You may also start directly at Step 4, sometimes it is not necessary to update the mirrorlist at all. \***

If above steps doesn't work out for you, then you may reach out to me using the means listed in the '[Connect](https://peux-os.netlify.app/#con)' section.

Thanks!



How to update the outdated pure arch-based systems?

Hi All,

I am planning to release some of the Wayland Compositor ISOs. Even though the ISOs are **Stable**, I am still releasing them under **Beta**
 tag. I am still part of the crowd that heavily believes Wayland to be 
overestimated and that it still needs a lot of work. However, the 
progress has been great over the last couple of years. The sole reason 
behind releasing these as Beta is due to the belief mentioned above and I
 am sure that on most machines it may cause problems, especially the 
ones with NVIDIA graphics card as Wayland doesn't sit well with NVIDIA.

Another
 reminder, Wayland compositors has a bad reputation when it comes to 
running them on VMs, hence I'd suggest you try these on either live-usb 
or on a hardware other than your primary machine.

Please also note
 that I am deciding not to put the Beta versions on FOSSTorrents, as 
it'd be easy for me to take down the ISOs or upload a new one to test 
whenever I wish to, once the stability is confirmed, the stable ones 
would be available on FOSSTorrents. The maintainer does a lot of work 
along with maintaining the FOSSTorrents site with multiple projects in 
it, which is why I don't want to bother him with back to back 
beta-releases, which would happen anytime.

Any 
inputs/feedback/adjustments/advises related to Beta are warmly welcomed.
 Let me know via Discord/Telegram/Sourceforge, you may also drop a 
message to me on Twitter.

Have a great day!

\-DN-debug



Upcoming Beta ISOs -- Wayland Compositors

Ratpoison is often considered as 
the 'King of WMs', modeled after GNU screen. If you would like to use a 
window manager which is keyboard-centric and you wouldn't have to rely 
on the mouse, then Ratpoison is the right choice. It has no fancy 
decorations and its beyond minimalist approach is its greatest strength.

The
 way to use Ratpoison is very simple, it uses EMACS notations for 
keyboard controls. The default modifier usually is 'C-t', however in 
case of Peux OS Ratpoison, it is 'Super*L'.  Once you press 'Super*L',
 wait for the cursor to change its shape like a box, which hints that 
you can now use the sequence key to perform the tasks specified in your 
Ratpoison's configuration, located in your home directory \[ 
\~/.ratpoisonrc ].

For example, to list the available keybindings, 
use 'Super_L', wait for the pointer to change to a box, then press '?'. 
You will get to see the list of available keybindings.

The 
keybinds that you'd specify using 'definekey' in your ~/.ratpoisonrc 
file, would not appear in the keybinding listings. To understand this, 
you'd need to understand the term 'keymap'.

When you press the 
modifier ( also known as escape-key ), you are accessing the 'root' 
keymap where all the commands are reserved by default. The 'Super_L ?' 
help list shows you the 'root' keymap entries.

However, there is 
another keymap entry, the top level keymap known as 'top'. When you'd 
use 'definekey' and attach the bindings to the 'top' keymap, it can be 
used without using the modifier/escape-key. I usually create aliases 
first, which makes it easy for me to call the command by the name 
defined in alias.

An example would be :

1.  create an alias for reboot

    ```
    alias reb exec systemctl reboot

    ```

2\. use the alias with keybinding

```
   definekey top C-M-r reb

```

It basically tells Ratpoison to reboot the system whenever  'Ctrl+Alt+r'  is pressed.

The
 way to progress through the Ratpoison environment is very simple once 
you get to know your keys, it is very productive and minimal. Once you 
get the hang of it, you'd most likely going to use it for a long long 
time.

Note: Sdorfehs is a successor of Ratpoison and is very handy
 for those who prefers to have a status bar. Sdorfehs is compatible with
 Ratpoison's configuration and all of the concepts of Ratpoison would be
 applicable to Sdorfehs as well.

For more details on Ratpoison: [check this doc](https://www.mankier.com/1/ratpoison#Synopsis)

For more details on Sdorfehs: [check this doc](https://github.com/jcs/sdorfehs)

Thanks for reading!



How to use Peux OS Ratpoison/Sdorfehs?

The face-recognition app on Peux 
OS KDE is known as HOWDY. It uses the inbuilt IR emitters and camera. If
 you have any external camera attached to your system, it'd still work 
with it. Peux OS automates the configuration for you, so you don't have 
to worry about it unless you change your cam during the process or do 
some manual interference. Changing your cam would require you to restart
 the desktop session before continuing with the configuration.

Now
 coming to the part where it does not initiate during the login screen. 
The problem doesn't lie with Howdy, rather with SDDM and KDE's lock 
screen. 

To initiate it during login and while attempting to unlock the screen lock, follow the below procedure:

1.  At
     your login screen, when the password field automatically adjusts for 
    you to type your password, instead of typing it, press enter. This will 
    fail the attempt in the background and will cause "HOWDY" to take over.

2.  When
     the screen lock appears, just move your mouse once and hit enter ( 
    either immediately or wait for the password field to show up ). This 
    will initiate "HOWDY" and it will unlock your screen.

The 
authentication speed usually depends upon your camera and the background
 light as well. Fast camera response would give you quick access. If due
 to some background light or camera issues your face is not properly 
identified, then HOWDY would wait for 10s before showing failed attempt.

One
 more important point to consider: you can implement system 
authentication using  HOWDY, to do that you will have to modify certain 
files in the /etc/pam.d/ folder. 

If you are using WiFi, the 
system will prompt you to enter the password right away after you log in
 to the desktop session, i.e, after sddm login. The reason is pretty 
simple, Peux OS will not configure HOWDY for system-level or so to say 
admin-level authentications. You can go to the path mentioned above to 
implement this feature. All you have to do is to add the below line at 
the beginning of the file that you want to modify:

##### auth sufficient pam_python.so /lib/security/howdy/pam.py

Few useful links:

[Howdy on Github](https://github.com/boltgolt/howdy)   |    [Arch wiki reference](https://wiki.archlinux.org/index.php/Howdy)

######

###### photo credit: firebase&#xA;&#xA;


Trouble with Face-Recognition?

#### Gnome-FIles on XFCE? What type of madness is this?

I know right.

**Then why? Isn't it the worst file-manager?**

Well, Nautilus ( I am going to refer Gnome-Files as Nautilus in this article ) is nowhere near worse. Let me explain.

Nautilus
 uses something called "metatracker" ( now tracker, for file-indexing ),
 which uses metadata to locate files throughout the system. You can add 
"tags" as well to the files, this would free you from organizing your 
folder list.

People may say that strigi,recoll,baloo, etc also use
 metadata. Well, I am not denying it. What they can't do is crawling 
through unorganized lists in a proper way. Nautilus' search indexing is 
the fastest in the list of GUI File-Managers.

\*\*Need some more explanations? \*\*

Nautilus
 uses something called GIO (gnome-input/output) to process the requests.
 Now, the specialty in this is, it uses single API calls for both remote
 and local files. This means no back-to-back calls to slow the system 
down. This not only increases the robustness of FTP connections using 
Nautilus but SFTP/WebDAV/Samba and etc. would be equally robust.

In the worst-case scenario, tracking the file would hardly take 5-7 MB of RAM, hence no pressure on the system.

While
 I do believe that every piece of software has its pros-and-cons and the
 same goes for Nautilus. However, I don't support the idea of completely
 bashing a piece of software. The reason being, there's a lot of effort 
put behind every piece of software that's out there, and the community 
can only grow and attract more people when we'll stop being harsh 
towards each other. Don't like it no problem, politely disagree and 
decline. If possible, then provide some suggestions. 

Peux OS does
 come with Thunar as well, no restrictions, it has good features too.  
You can replace both thunar and nautilus with something else, after all,
 it's Linux and we have plenty of file-managers to choose from unlike 
WIndows ;)

Want me to change the default FM? Sure, if you provide a
 detailed enough explanation of the GUI FM that you opt-for and has 
better indexing than Nautilus, then I can consider it.

**Side-Note**: Thunar uses "GVFS" which is a gnome-component to manage remote-fs/trash among few other things.



Gnome-Files on XFCE? Huh!

Free Open Source Software (FOSS) 
Torrents, is more like a platform for Open Source Community, that helps 
to spread the Open Source Softwares using torrents as its medium. The 
idea is to promote FOSS throughout the web, extend its reachability 
while trusting the platform that promotes it.

Dev, are you writing
 this because you have a partnership with them? NO. I am writing this 
because I want like-minded guys to come forth and support the FOSS 
community. There are other FOSS platforms, which I will share in another
 blog-post.

**But isn't there a price to everything?** FOSS community survives with the help of **Donations**.
 The aim of FOSS is directly proportional to its name: Free Open Source 
Software. Those that follow FOSS, follows the principle behind it as 
well. It has survived this long because of its huge community and 
of-course some generous people and organizations have contributed to the
 cause as well ( there are good people out there and not everyone is an 
@$$ )

**How to start?** If you have any open source 
projects that you want to spread using trustworthy torrenting ( Idk if 
torrenting is really a word or not), reach out to FOSSTorrents on 
Twitter, Discord, Facebook.

Check their website at [FOSSTorrents](https://fosstorrents.com/)

If you wish to, then donate: [Patreon](https://www.patreon.com/fosstorrents) / Kofi or visit the [Shop](https://www.redbubble.com/people/crimson-art/shop?asc=u)

Unable to donate: not a problem, spread the word ;)

Enjoy!



Blog