blue-systems / netrunner-next

https://pub.netrunner.com/.testing/?C=M;O=D
0 stars 0 forks source link

doublecheck if to make firefox esr use the kwin window deco, this has always worked fine before and it doesnt seem a Libadwaita only app #130

Open star-buck opened 5 months ago

star-buck commented 5 months ago

i actually have firefox esr 115 working fine here with normal kwin deco on manajaro arch: Screenshot_20240522_141407

star-buck commented 5 months ago

i guess it is due to missing plasma integration extensions.... so i stop tetsing and wait for new iso which has all settings applied after install and reboot.... lots of issues could come from that

UriHerrera commented 5 months ago

Captura de pantalla de 2024-05-25 15-40-35

Ah, you meant that this is how it looks in the Live session (above), but it looks different after installation (below).

Captura de pantalla de 2024-05-25 15-48-58


This problem occurred randomly once in the five times I installed the distribution. At first, I thought it was because of the language used for installation. When this occurred, I selected Spanish, and subsequently, I selected American English and German. When I selected these other two languages, the settings were applied correctly.

However, I did a fourth installation, selecting Spanish again, and the problem did not occur this time.

At first, I thought that Calamares didn't copy something right or that whatever Calamares ran to set up the locale failed, which caused the Firefox settings not to be copied when creating the user account. Still, there are no errors in the installation log.

The fifth time I installed the distribution, I selected Arabic, and the problem did not occur again.

Captura de pantalla de 2024-05-25 16-16-27

As I can observe, this problem seems to occur at random. If there's a bug somewhere, it's not in the settings package that adds the Firefox profile or the packages that add the settings for Plasma or Calamares.

UriHerrera commented 5 months ago

Through a thorough troubleshooting process, I have consistently reproduced the problem.

It occurs every time I don't select automatic login in Calamares. Whenever I don't do this, after rebooting, booting the installation, and getting to SDDM, once I enter the password, the cursor changes to Breeze instead of RED-Modern. Firefox does not use the KWin decoration, among other things.

If I select automatic login in Calamares, the cursor will be RED-Modern once the user logs in; Firefox will use the KWin decoration, and the other software will use their intended custom settings properly.

Notably, this issue also affects new users. After creating a new user post-installation using the Users KCM, the problem persisted when I did not select the automatic login in Calamares. This lack of custom settings for Firefox, Dolphin, etc., could potentially deter new users.


Netrunner has a package that adds a script to /etc/X11/Xsession.d to customize the environment in an X11 session and add a custom directory where most of the settings are stored. 

I have included screenshots below as evidence. These clearly show none of the scripts in the /etc/X11/Xsession. d directory was running, further confirming the issue. Notice that the environment variables XDG_DATA_DIRS and XDG_CONFIG_DIRS differ.

Captura de pantalla de 2024-05-27 03-44-52

Fig 1. The environment variables are not modified when the user does not select automatic login in Calamares.

Captura de pantalla de 2024-05-27 03-52-05

Fig 2. The environment variables are modified by a script when selecting automatic login in Calamares.

That is also why, even after installation and creating a new user, all the custom settings are unavailable if the user does not select the checkbox to log in automatically.

For that purpose, I've updated the Calamares configuration to enable the checkbox by default. Without editing the UI directly, there's no way to hide this checkbox, so a user can still uncheck the checkbox and thus land on the issue.

Captura de pantalla de 2024-05-27 17-17-10


I just noticed. Upon installation, it defaults to the Wayland session.

Disabling, i.e., renaming, the Plasma Wayland session file "forces" SDDM to use the only available session file, which is Plasma X11. Given that the Netrunner settings revolve around X11 (see above) doing this, technically fixes the problem.