banger Thank you. I have no idea what's going on. I did some spelunking in the depths of Mozilla's bug list and that error seems to crop up from time to time. Anyway, I installed the flatpak and it works. Fine by me.
EDIT: That didn't age well. FlatPak Firefox can't communicate with KeePassXC. I downloaded Firefox 130.0.1 from mozilla.org and installed in ~/ and the mail button works. It seems it's not a Firefox bug after all. I dunno.
pillmuncher Maybe there's a possibility to set permissions therefore with Flatseal
i trying new pc to install solus kde but iso image bootable drive not recognise image message.other distros boot & install properly. any problem in iso file?
Known issues
When running eopkg check, the LTS kernel shows as broken. This is a false positive, and can be disregarded.Should I get it for linux-current as well? Is it fixed for current and I shouldn't see it?
pillmuncher FlatPak Firefox can't communicate with KeePassXC
this is very well known known; it's happened to me and it's (sadly) normal since the flatpak is sandboxed. that doesn't mean it won't work in another browser. for a while. maybe it worked in firefox before but when it quits working it quits working. there's a thread where me and @axios spent days trying to figure out the flatpak to solus to keepass extension relationship. Could never get it to work was the conclusion because it wasn't a native package.
Anyway I solved this by liberating myself from the browser extension that I didn't trust anyway (it had too much control) and cutting and pasting [crtl b / ctrl c] straight from the keepassxc app itself. may seem primitive but its second nature now. edit: second nature for flatpak browsers.
2 cents
AlphaElwedritsch Sadly, no - probably. There are some possible workarounds (editing some files), but none of them seem to work reliably in all cases. Anyway, I have downloaded Firefox 130.0.1 from mozilla.org into my home directory and it works. I suspect it's a weird side effect from some compile flag that's the culprit.
BTW: According to the estimation on https://fossies.org/linux/www/firefox-130.0.1.source.tar.xz/cloc_cs.html Firefox has over 33 million lines of code. That's more than the Linux kernel with less than 28 million. Even the open-source AMD GPU Linux Kernel graphics driver now has almost 5.8 million lines of code. Nobody has a clue anymore why things even work in software. We've made a mess of things.
pillmuncher It's not actually a Mozilla bug. We have to set some environmental variables in the Firefox launch script in order to make Firefox work correctly on Solus. The problem is that these environmental variables are also used by Thunderbird since they share much of the same code and if they're set to the values FF needs it breaks Thunderbird. When you click on a link in FF that opens something registered to be handled by TB (like mail links or calendar invites) it opens TB as a child process of FF and TB inherits the environmental variables from FF (which breaks it).
Ideally there would be TB and FF specific versions of these variables so that they wouldn't conflict anymore, but as far as I can tell that isn't implemented yet upstream. I'll look into creating a patch to add them.
WhiteWolf Both will show as broken, both are false positives.
Alright, I added some patches to Firefox and Thunderbird to make this work and the fix should be in the next sync.
cherry-picked discord 0.0.69
ReillyBrogan Thank you!
update and usr merge went fine 
️
update and usr merge went great on my old machine, which was not updated for more than a year (1111 packages). My other machines got no usr merge yet. ️
Is the Caja file manager a requirement for Engrampa to work? I want to switch over from file roller but i dont like the idea of having 2 different file managers installed
tom73287428764 Hmm, sounds like the Caja package might have to be split up into extension libraries and the main program.
cherry-picked vivaldi-stable 6.9.3447.48
Cherry-picked cups-browsed (2.0.1-3), libcupsfilters (2.0.0-3) and libppd (2.0.0-2) for CVE-2024-47176, CVE-2024-47175 and CVE-2024-47076 respectively.
I thought Solus doesn't have anything listening to ports by default, as repeated countless times by the devs 
