Powered by Arkdep from the Arkane Linux project this exciting new Manjaro variant is available for public testing right now! The goal of this release is to gather community feedback on the technology powering Manjaro Immutable. Note that this is only an experimental release and not representative of the final version, there is also no support guarantee, so hold off on installing it as your primary operating system, at least for now. We are hugely interested in gathering your feedback on Ma...
Immutables are cool—I’ve been running Silverblue for over half a year now. However, this seems half baked?
Unless I’ve misunderstood, you can no longer use pacman (without losing your changes after the next update).
And arkdep itself is just a shell script without any tests or continuous integration. I would be skeptical of using such a tool to control the integrity of my system.
it’s a manjaro project, ofc it’s half baked
It’s half baked: like the post says, it’s the first testing version. It will be developed more, like a member of the team said:
It’s clearly not ready.
It kinda feels like it goes against what Manjaro was supposed to be though. A safer version of Arch but with about the same features, including its massive software pool to pull from - and that exactly is what would fall flat in this case, since you’d need very selectively maintained “packages”, which would be extremely limited in comparison to someone with access to regular repos and the AUR.
I don’t know how Manjaro plans to do it, but Universal Blue distros have access to the entire set of
dnf
repositories, including non-free packages. You runrpm-ostree install
, and it layers the package you want. Each system update re-layers the custom package layer after upgrading the system layer.But since this is pre-alphaware, it’s kind of early to be passing judgement on how/if they’ll have access to the AUR and whether you could layer packages. Seems like the “safety” aspect is served through having an immutable system, which ensures end users have the same base as everyone else.
And it’s fine if that’s not your cup of tea. Sounds like it’s not. Arch, openSUSE, Debian, and their mutable descendants aren’t going anywhere.
I don’t know for the AUR, but the regular repos seem to be already accessible. You can try them with pacman, but the installed packages will be deleted at the moment of the update, or you can create a custom image and add the wanted packages which will be reinstalled at every update.
I don’t understand the hype of immutables, or usability even. I tried Bazzite today after Nobara nuked itself, and I couldn’t even paste my old Firefox profile since the actual folder apparently sits within the immutable folder structure. Maybe that’s fine for grandmas who just want to casually browse the internet but this seems extremely counter intuitive and an incredible hassle. I didn’t even have time to reach the software limitations with how fast I tried the next distro. Still hopping though, because apparently Fedora just nukes itself when you try to install codecs and I think I have about every major distro tested by now. Linux is cursed.
This is wrong. I run Bazzite and have transfered my FF profile over without issue. The Ublue “distros” just use the FF flatpak. You can follow the same instructions as you would on any other distro to move your FF profile with the flatpak version.
I haven’t had any problems with Bazzite, either, save for figuring out how to install Private Internet Access’s client, but that’s not immutable distros’ fault. The fault lies with PIA for not packaging their client in a sane way.
I couldn’t find jack shit, other than posts where people were saying that it sits within the immutable part of the distro and the profile manager just opened some temporary profile folder, with the permanent path being invalid / nonexistent. If that information is wrong then they should work at least on their documentation, which I checked for FF profiles and could find 0 entries.
I could probably summarize your experience as “skill issue”.
I suppose this article/blogpost by Lennart Poettering should suffice. Though, this article/blogpost by Colin Walters is also cool.
This is simply false as pointed out by others already.
You will have a very hard time on Linux with that mindset. And, to be honest, literally any OS you aren’t already familiar with.
I wouldn’t be surprised if you just searched this through your favorite search engine and settled with whatever random solution you came across instead of relying upon RPM Fusion’s documentation on the matter.
While this could be true, I wonder what prevented you from sticking with any one of them.
It’s definitely a lot harder if you’ve got major skill issues.
Blaming users for a lack of proper UX is always the best excuse.
Yet the only information I could find by other users of the distro. I even checked the official documentation, which contained 0 information on Firefox profiles. The FF profile manager only led to temporary folders and the absolute path led to an inexistent / invalid one (the one you’d expect them to go normally). So yes, I guess my skills are low, but so is the possibility for me to even learn anything when the only barely scrapped info I could find is wrong.
No, that and the rpm fusion install page is quite literally exactly what I used. Then no applications would launch, no UI functions would work and after I hard reset the PC it wouldn’t show me anything but a broken welcome page, which, when closed, left me with a blank black screen and my mouse cursor. I’m not sure what else you would expect me to do when following seemingly official command guidelines. But I guess it’s still my fault after all.
Let’s see…
Especially since absolutely no one is willing to help and rather throws insults and personal attacks around when facing people who struggle with all the major bugs.
I had a similar story, in fact EOS has a problem that they use dracut by default and is set to overwrite the kernel parameters every time you update the system lol.
I’m very sorry you had to deal with some users from here btw, specially the nixos people.
And people thought Arch users were stupidly entitled and toxic. My favorite part right now is him trying to repeatedly berate me for not being able to read out the correct profile folder within Firefox (which shows the default .mozilla/firefox/), even though I already mentioned that it does not show the actually correct one (.var/app/org.mozilla.firefox/.mozilla/firefox/). I guess he has “skill issues”.
Thank you for the elaborate answer! I appreciate it 😊. It’s also been instrumental to put your earlier statements into perspective. Incoming long comment…
With all due respect, blaming UX doesn’t help your case 😅.
Bazzite, a SteamOS clone based on Fedora plus some extra sauce, comes very close to the best UX out there (on desktop Linux). If you choose to blame that instead of (primarily) looking at yourself, then I simply don’t know what to say.
Where? I want to see it. A quick search didn’t yield anything like that.
The issue you’ve faced is peculiar for a multitude of reasons:
apt
/dnf
/pacman
on Arch/Debian/Fedora.about:support
contains information on where you may find the profile directory.about:support
.about:support
.The three points that start with ‘(possibly)’ are especially curious, as they shouldn’t have happened in the first place IF you had read the simple instructions on Firefox Profilemaker; which you reference elsewhere. You can blame documentation all you want. But, honestly, I’m not confident you would even make proper use of it based on this awful track record.
Why would it have to mention information on Firefox profiles? This is literally not even an issue. Even referring to it as a ‘you problem’ would be nice. Same applies to referring to this as ‘skill issue’. Which you actually took as offensive (or something), but it was actually just me being nice.
Documentation efforts should be spent on stuff that are otherwise literally undocumented. Firefox profiles works identical across the board. But you somehow failed at it and chose to blame immutability smh and called it quits based on (seemingly) a single user report that I’ve yet to see/find.
I simply fail to reproduce this. I’ve got no clue what you were doing. Consider making a video.
I appreciate your honesty.
Like, I assume you went to the Firefox profile manager website, downloaded whatever config you ended up with and followed its instructions related to implementing it. When I do this, I just go over the folder as found on
about:support
, paste it there and done. Like, with all due respect, how did you fail at this? Sorry, I simply fail to understand. Again, consider recording this.Furthermore, I implore you to link me to the misinformation you’ve found; I tried finding it on my own, but I simply failed.
Thank you for correcting my incorrect assumption. Though, I wonder; did you update your complete system before you applied the steps as found on RPM Fusion’s documentation? Knowing that you’ve been a user of Manjaro for two years, it only makes sense to assume you did. And, if that’s the case, then that’s an unfortunate bug and/or breakage that you’re not guilty of. Consider reporting it.
All of this is unexpected behavior. Again, if you did nothing wrong, then this seems to be simply on Fedora. They aren’t saints, so they can definitely miss the mark. Though, I can’t recall anyone else experiencing this due to legit reasons. However, I am aware there’s a first to everything.
Again, if you updated your system after installation, then did a reboot (perhaps more than one). And finally followed the steps as per RPM Fusion’s documentation. Then I simply fail to see what you would have done wrong.
Regarding the distros you’ve tried and your experiences with them, I would like to note the following:
Don’t get me wrong. I’ve crapped my pants with Arch, EndeavourOS and Nobara. So, I very much understand that (semi-)rolling distros are far from perfect and can definitely break at seemingly random times. But, I choose to blame myself:
And, if you choose to equate/define or refer to all of the above as “lack of proper UX”, then I got a surprise for you… There are distros to which the above does not apply. So…, why do you choose to stick to distros that are known to be less trouble-free?
Based on the above, a very curious observation would be that you somehow seem to attract problems that are otherwise observed a lot more rarely. At that point, I’m inclined to think that either you or the hardware is the main culprit. I wouldn’t blame the software that seems to be working for everyone else. But, that’s just me.
Another curious observation would be that you (seemingly) have not tried anything based on Debian (and/or Ubuntu). Are you perhaps biased towards it? Or, are you simply aware that your hardware is too new for it (which I doubt unless you’ve continually changed to newer hardware in the past two years)? Or, you simply consciously choose to use ‘more current’ distros for whatever (perhaps legit) reason. Please feel free to inform us on this.
So, in my experience, the community has been lovely at large. Sure, it ain’t perfect, but what even is. Therefore, I’m sorry to hear that your experience has been different. Though, again, it might be the community reacting to someone they perceive as misinformed OR not diligent on making it work OR not being helpful towards those offering help.
Furthermore, I’ve actually not found any post of yours in hopes of resolving any of these issues. Perhaps you chose to ask individual users in comments instead, but your track record on Lemmy doesn’t portray you as someone that’s diligent on solving the problem. For example, regarding Bazzite, if you had just joined their Discord and asked your question there, then they would have solved the issue for you that very moment and you wouldn’t have made a joke out of yourself.
Though, I understand you might have lost interest to engage with communities like that based on some past experiences (e.g. with EndeavourOS’ community as you had already pointed out). FWIW, a single bad experience shouldn’t have deterred you from ever (re)commencing and/or (re-)engaging.
Regardless, again, thanks for your elaborate answer. At this point, it genuinely makes most sense to me if you choose to give Bazzite another go if you’re willing to stick to distros with (at least relatively) up to date packages. If not, then consider trying something based on Debian (and/or Ubuntu) for once. Perhaps it’s the one thing you actually needed. Or, simply return back to Manjaro if it most successfully managed to satisfy your needs without putting you into too much trouble.
If installing shit is 50 times more inconvenient & more or a hassle compared to pretty much any other distro I have ever used, then that’s clearly not the case.
Some Reddit comment. Dunno which submission as I can’t seem to install even Mullvad on it, so I can’t hop DNS servers so I can’t circumvent Reddit’s VPN block to even bother looking for it again. But it’s definitely not a UX issue!
I’m not gonna read the rest of your text wall since your entitlement & insults just show the clownery that is your person after you clearly failed to even acknowledge the correct profile folder while trying to berate me. So, take up your own advise and work on your SKILL ISSUES.
lol, the full answer I had written somehow was ripped to pieces. I’ll therefore keep it brief.
about:support
while it’s found (as seen below) inabout:profiles
instead. I know it’s found in Firefox, I (just) messed up the exact spot. Therefore, thank you for countering misinformation!It was not found in either page, as I already explained. Maybe they’ve fixed it by now but at the time of my comment the page led to the mentioned empty standard folder path you’d expect on a regular installation.
Alright, so through the
flathub remote-info --log flathub org.mozilla.firefox
command, we can view which commit was active at that moment.Command yields:
So, at the time of your comment, commit
6a16f6a509340ad3bb833c9d9aa794ed78910aa43803a7420438b880aa0a6ce0
was active and deployed on your system. Let’s find out what downgrading to this commit yields.Downgrading through
sudo flatpak update --commit=6a16f6a509340ad3bb833c9d9aa794ed78910aa43803a7420438b880aa0a6ce0 org.mozilla.firefox
, after which theabout:profiles
page is opened on this downgraded Firefox yields:The beautiful part is that, as Flatpak is containerized anyways, anyone can downgrade to the earlier commit and it yields the exact same result. So, please feel free to verify this for yourself.
So, as a result, if the logic and the appliance is sound, then this showcases that your claim is either still true and portrays an anomaly -which I would deem as highly unlikely- or it’s simply false and you were just mistaken.
Finally, if I’ve messed up at any of the steps, then please feel free to correct me.
Skill issue. I use NixOS btw. You can manage your dot files the immutable way as well if you develop the skills rather than yelling from your horse and buggy at the model T passing you.
Same reply that I wrote to the other entitled asshole: https://fedia.io/m/linux@programming.dev/t/1045299/Manjaro-Immutable-Out-Now-for-Community-Testing/comment/6595387#entry-comment-6595387
So you think immutable distros aren’t the future of Linux? I’ve got some bad news for you: This style of distribution is catching on like wildfire and IMO someday they’ll almost all be structured like this and you’ll actually have to learn how to work with it.
I’m not sure how what I said is entitled. I’m a REALLY mediocre programmer with limited time to learn and I STILL learned Nix and work comfortably with immutable distros.
SKILL ISSUE
If you make your distros even more unintuitive and a hassle than before, then no, it certainly won’t be the future. You people need a reality check.
It’s really not unintuitive, honestly. It is just very different than FHS.
“You people”?
If many things go from 1-2 steps to 20+ steps that I also have to read up on, but aren’t even documented anywhere which means I also have to be some sort of all knowing mystic (meaning they might as well be not possible to do), then yes, that’s very much unintuitive.
Maybe you “forward-thinking generation of software engineers that make elegant, reliable, declarative systems but are totally not entitled shitheads that insult everyone who clearly struggle with such elegancy” should actually listen to the issues that your potential user base is facing instead of dismissing them. Otherwise it will be hard to sell that “future” to them.
Thank you for perfectly playing your role of aging luddite principle Skinner who is stuck in the past and can’t (won’t) adapt to new paradigms.