I'm interested in using Firestorm on Solus. The Alchemy Viewer didn't show any Linux downloads. Can someone more proficient check whether it would build on Linux or whether Firestorm should be preferred?

I think you've misunderstood my request. I don't request a minimal image in addition to the Solus editions but only an option in the installer.

If accepted, I also volunteer and try my hand at packaging it.

Yes, I'm using the flatpak version but would like to reduce my dependency on flatpaks when applications are offered with FOSS licenses. The javascript code quality of the project has a few issues but I think it has matured enough as a project over the last three years. I use it on mobile without any problems.

@moore-bryan I've reinstalled Solus on the same machine and it's fixed for me now. If you don't mind a reinstallation, try if that fixes your issue.

@moore-bryan Saw your bug report on kernel.org, thanks! Relevant to this are also Bug 206395, Bug 202399, and Bug 203709. Maybe there are some more that I missed. Let's keep an eye on these.

It's probably related to a firmware update. Maybe this can help: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893952

I have the same Wifi card Intel 8260 (rev 3a) and can confirm that for some time Wifi is broken. I'm on Kernel: Linux 5.5.4-148.current

Same, HDA-Intel - HDA Intel PCH

I thought this is the latest kernel. After sudo eopkg check, this turned up:
`Checking integrity of udisks Broken
Corrupted file: /usr/lib/tmpfiles.d/udisks2.conf`
I doubt this is related but to be sure, how would I fix this?

I ran a full update. The kernel according to hostnamectl | grep -i kernel is Linux 5.4.12-144.current.

Fixed, no longer an issue.

My wifi is also broken.
Kernel: 5.4.12-144.current
Device-2: Intel Wireless 8260 driver: iwlwifi

[✗] Reloading systemd configuration failed
[✗] Re-executing systemd failed

Same issue here. If you need any help with testing or finding a solution, let us know what we can help with.

I just tried to install another flatpak and got this:

What do you suggest that I try?

It looks like the same problem appears with any other flatpak. Is it due to the flatpak version on Solus being out of date?

As of late, I haven't been able to install or update any flatpaks. Looks like there is an issue with NetworkManager? https://bugzilla.suse.com/show_bug.cgi?id=1128358#c4 and https://github.com/flatpak/flatpak/issues/2921

@JoshStrobl It's not that speech-to-text isn't working. It is indeed working in Google Chrome under Solus but the quality of the engine is just not good and doesn't match the results I get under Windows 10 using an identical version of Google Chrome. I'm wondering whether the Chrome built is a totally different one under Solus or maybe there are any other optimizations that can be done?
@mate-user Did you compare the engine in an identical version of Google Chrome under Windows 10?

inxi gives this output:
CPU: Dual Core Intel Core i5-6200U (-MT MCP-)
speed/min/max: 800/400/2800 MHz Kernel: 4.20.3-108.current x86_64 Up: 3m
Mem: 1297.6/7859.9 MiB (16.5%)

It's a trackpoint, not a mouse. I just realized that this also sometimes happens before login.

Will do :) Learnt a lot in the process and it was worth the effort. Thanks again!

I clicked y. It says:
Inode 3670134 was part of the orphaned inode list. FIXED.
Deleted inode 4194399 has zero dtime. Fix<y>?

When I check my previous screenshots/pictures, it looks that udev and systemd configurations were skipped?

I typed journalctl and looked through most of the lines. The error messages that stood out were two systemd related messages in bold:

I see, sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall worked better than before but still some items were skipped as seen in the screenshot. @Girtablulu

I ran sudo eopkg up and it upated nearly 1.1 GB. This is quite a lot and I remember having kept my system always up to do. Not sure why it is so much to update. It looks like some were skipped:

Thanks a lot! Internet is working now in chroot. I ran sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall again and got another system error "25, inappropriate ioctl for device":

This is how it looks like:

@Girtablulu Thanks, there's indeed no internet connection when in chroot. I typed nano /etc/resolv.conf but don't know how to save the addition of the nameserver with the IP. How can I do that?

In my terminal window it says root@solus / #
I guess I should be correctly in chroot?

The output of eopkg list-repo is https://mirrors.rit.edu/solus/packages/shannon/eopkg-index.xml.xz
While the output of eopkg ur points to the .../eopkg-index.xml.xz.sha1sum
Is this correct?
When opening mirrors.rit.edu/solus/packages/shannon through a web browser there's three options: .xml.sha1sum, .xml.xz, and .xml.xz.sha1sum?

I connect with a cable and it is still the same issue. Is the repo mirror down or an alternative one I can try?

It looks like the repo link doesn't work? Wifi is working well and I can open other websites from the live iso.

It says: https://mirrors.rit.edu/solus/packages/shannon/eopkg-index.xml.xz

@Girtablulu After the previous terminal command I exited chroot and rebooted but it still boots to emergency mode. Is there a command to add system.base and to update the repositories while in chroot?

Thanks, I got this result now:

I followed the suggestions by @Girtablulu but I'm not sure what to look for or how to interpret the results I've got. This is how it looks like:

Interesting. Is this related to the rollback functionality of clr-boot-manager so that there are always automatically two kernels installed? I hit the "space bar" several times and booted into Solus-current-4.18.16-96 first and then tried with Solus-current-4.18.16-97 but both lead to emergency mode.

Just exit chroot, the rebooted and I am still stuck in emergency mode.

Apparently, this happened before: https://getsol.us/forums/viewtopic.php?t=10871
@sunnyflunk You replied to this message in the forums. Does that mean this is perfectly normal and the sudo clr-boot-manager update command was successful despite the error?

Thanks for your help. Yes, I first typed mount /dev/sda3/target, then mount /dev/sda1/target/boot and then the three mount --bind ones, and after that chroot /target. Not sure why - as in the screenshot - the Solus repository could not be reached and clr-boot-manager cannot determine the currently running kernel.

I found out that I'm using EFI and I followed all steps - at least I think - however, the sudo clr-boot-manager update command failed with the following error: [Error] cbm (src/bootman/update.c:L270): Cannot determine currently running kernel. I tried following the instructions via https://www.reddit.com/r/SolusProject/comments/9gc4gk/help_with_fresh_installation/ by sudo eopkg dr Solus, sudo eopkg rr Solus, and sudo eopkg ar Solus https://mirrors.rit.edu/solus/packages/shannon/eopkg-index.xml.xz and got the following error: No repository found. Automatically adding Solus stable. Repo already present with name Solus and same URL. Removing first. Repo Solus added to system. Updating repository: Solus. Solus repository could not be reached. Removing Solus from system. Is there anyone who could give a hint what seems to be the problem?

@Girtablulu I don't understand the instructions in the Help Center. I booted the Live ISO and typed sudo su. Not sure how to proceed. Do I need to replace the mkdir /target command with something and if yes, with what? I think my system uses Grub.

@Girtablulu I'm afraid that I will lose all my data if I run a LiveISO. Could you walk me through the steps I have to take? I can have a LiveISO ready tomorrow.

@Girtablulu Thank you for trying to help me with this but I already cannot pass the first issue as I don't understand the instructions for boot rescue given in the Help Center. All commands I entered are not working in emergency mode but most likely I'm not sure with which one to proceed. For example I started with sudo su but it says: command not found.

@Girtablulu How would I do this? I use Solus because it's easy to use but never had to deal with the emergency mode before.

Regarding plugins I'd only say as much as don't trust any plugin as long as you didn't enable it yourself.

@der_eismann Thank you, I'll check them out. AFAIK there's no automatic enablement and auto-renewal of SSL certificates though.

Thank you @sunnyflunk I totally overlooked the fact that I had a local Publii text file which was indeed the problem. Sorry for the trouble. It is indeed solved now and the .AppImage is starting just fine. I'd still very much prefer a native package to work with though: T7031. I suppose there'll be an advantage performance-wise and receiving the latest updates will be easier?

+1 for caddy! Is there an easy to use alternative to caddy in the Solus repo that I can use?

I deleted the file and downloaded with wget but I still get the same error message as mentioned above.

Apologies, I took the following steps to launch the .AppImage: chmod a+x Publii_0.31.3.AppImage, and then ./Publii_0.31.3.AppImage. This resulted in: