I see similar behavior, but not the same, on a Budgie VM running unstable, updated. It was created with the 4.4 ISO.
After rebooting, I see "Unlock Login Keyring"

I forgot an important piece of info but maybe it's better be added here:

Just a comment:
I would also like to check any connection to the OLD, FIXED language indicator crash/empty non responding panel successfully fixed by last sync and last Ibus 1.5.28-28's revision by Ebon Jaeger, and to the logs from the PAST, OLD, resolved issue.

Much appreciated - Can confirm host sees all available cpus.

https://dev.getsol.us/R3571:39fd7666ddbf3f0f2b94162273de321294e63f11 and https://dev.getsol.us/R1966:c2a30b68f7b831ec3eebdfb5a7dc159bc2403914

Hm, I cannot reproduce this problem, either on latest stable or unstable...

@jjporee , hplip was recently updated. Is this still a problem on your system?

@ReillyBrogan : Do we want to switch this to 128?

incapable of doing stuff ulimit, as i have switched to arch linux as i am one to do, should be default. However, i can confirm that i have 16gb system ram and swap available, but I was trying to copy a hundred gigs or more, (my entire home folder with a few steam games installed). Rsync and Rclone may both work but have separate issues.

Note to anyone fulfilling this. You need to double check the license on the guest additions ISO to ensure that we (Solus) are able to legally re-distribute it. You should install the file to /usr/share/virtualbox/VBoxGuestAdditions.iso and also subpackage it out to a new subpackage (virtualbox-guest-additions-iso or similar).

@anoraktrend: Ping? See above.

Do you want us to disable your account then?

Thanks for the report.

It does not but at the very least you won't receive those emails anymore.

I guess you are requesting to update cava, right?

Possibly, do you know if disabling one's account notifies/signals to others trying to @ someone in a conversation that this person is no longer around/not to expect a response?

AIUI, the way phabricator works makes it a _Bad Idea™_ to outright delete an account, as deleting an object in the store has all sorts of bad side effects.

Update. all above activity was with X11. I just noticed that I can choose Wayland desktop instead of X11 at login on the lower left.
When I'm using Wayland the HDMI display is 100% stable. It was flickering when I was on the login screen but after I chose Wayland and logged in, the issue was resolved. This is ok to close, but If you want to further triage X11 you can keep it open and let me know if you have any updates I can test. Thanks! ~S

Budgie Desktop tested and working in VM and on host machine with LightDM + Slick Greeter.

Full 8nstall still flickers. {F10963376}

Hi Reilly -- I tested the live ISOs with a different display and cable at work and encountered the same problems on gnome and budgie, and it seemed less dramatically flickery on kde. All attached files are at first bootup.
One other thing I did was since my work screen is in portrait orientation I changed the display config in each to portrait for the extended display and the problem seemed to go away (I did this in gnome and kde and there was still some intermittent flickering on kde)

Does KDE have the same behavior? Also does it go away if you install Solus and then update it?

Apologies for google translate. Run the following command, then restart your computer: sudo eopkg install sof-firmware

Buen día, no he probado, mil disculpas, pero no conozco mucho de línea de comandos, si ud puede brindarme esa información muy agradecido.

Entonces, ¿ha intentado instalar sof-firmware desde el repositorio? (Google Translate because my Spanish is more than rusty)

El fabricante no me provee de los Drivers para linux

Maybe something that can be fixed by installing sof-firmware (and rebooting)

I suppose we would expect both libreswan and networkmanager-libreswan as conflicts for networkmanager-strongswan? Also, should we add the conflict for libreswan and networkmanager-libreswan in the other direction as well?

FALSE ALARM: I checked the account settings again, and discovered that I hadn't checked the { X } Use HTML property on that account's settings. The text box entries were all nearly identical, but not the checkbox.

This Thunderbird instance supports three email accounts. So there are three entries in the Account Settings, all of them using the same method to define a signiture. After I created this report, it occurred to me to check whether the other accounts are working.

¿Cuándo este problema occuride? También, ¿puede rellenar los detalles en la plantilla de problema, por favor? Será ayudar con identificando el problema. ¡Gracias!

Since this seems to have resolved itself, I'll close this one out.

It turns out that the problem was a space after the user name. The installation is now continuing. Since adding a space after typing a word is a common habit in most circumstances, this could be a frequent problem for users. They wouldn't expect that to be the problem any more than I did. I suggest that these text fields be trimmed to prevent errors like this from happening.

Looking at that page again in the forum, I'm now aware that the field for my user name does not have a checkmark. It has the 0 with a diagonal line through it, My user name, jerry, has never been rejected before. I was paying attention to make sure my password matched the confirmation field, and didn't notice that the user name was not checked.

I installed VirtualBox and created a new VM with the same setup, and it also works there, so I am unsure what the difference is.

Did you format the disk as GPT?

In T10563#202099, @EbonJaeger wrote:

I am unable to reproduce the issue using the downloaded MATE ISO.

The only difference in setup is that I'm using GNOME Boxes for virtual machines. Besides that, the VM is set up for EFI, I set up the disk for GPT, created a 1 GB fat32 partition as the first partition, then created partitions for swap and root. After the partitions were created, I changed the flags for the boot partition to boot + esp. In the installer, I assigned mount points to swap and root, and on the next page the fat32 partition was identified and pre-selected for installing the bootloader.

In T10563#202095, @joebonrichie wrote:

Any reason for not allowing the installer to auto create the ESP partition? We know in general that os-installer sucks when trying to use custom ESP partitions but it's not super likely to get fixed as we're looking to drop os-installer and switch to calamares.

I am unable to reproduce the issue using the downloaded MATE ISO.

Not wetgeek here obviously but I like to keep my computer clean, so whenever I can I make the ESP partition shared among Linux and Windows.

Any reason for not allowing the installer to auto create the ESP partition? We know in general that os-installer sucks when trying to use custom ESP partitions but it's not super likely to get fixed as we're looking to drop os-installer and switch to calamares.

Apparently this can be ignored. When I returned to the VM, I was able to assign the mount points normally. I have no idea why it didn't work the first time I tried. I had already created the Budgie and GNOME VMs, where I didn't run into this problem. I'll continue with the installation and testing.

The last change to how Solus sets directory permissions was made in 2018, so this probably wasn't caused by an update
The permissions are set in baselayout/actions.py
https://dev.getsol.us/source/baselayout/history/master/actions.py

Current version in the repo is 1.7.1. Latest version is 2.1.1

Closing since the author is no longer in the system, and as mentioned, Nautilus is now usikng libadwaita