![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.one/pictrs/image/0f5e05b5-d351-4add-9667-1df4c43091b4.png)
IIRC, it stops working whenever you disable JavaScript.
IIRC, it stops working whenever you disable JavaScript.
Currently I got no time to go over this in more length. So apologies*. However, I still want to offer/provide a brief and concise answer. I will (hopefully tomorrow) return at this in more length.
Now i already setup my container & install some packages in it but the shortcut is missing from application launcher (a.k.a start menu), how i can link the shortcut from package inside toolbox to host application launcher ?
Short answer is that Toolbx for a long time (and perhaps still) didn’t really support this feature. Sure, you could make it work, but it was a bit hacky. If this is a concern of yours, consider switching over to Distrobox. With distrobox, it’s as easy as (while inside the container) distrobox-export --app <name app>
. I will return at this tomorrow with the Toolbx way to do the same. I will also explore how Distrobox fares compared to Toolbx etc.
If i made a file (ex text file) from inside container will it show in Home directory ?
Yes if you’ve saved it in the Home directory to begin with.
If something crashed inside container will it also crashed my host system ?
Nope.
Why some packages doesn’t work inside container like Wine, Lutris, or Bottles ?
Interesting. I don’t recall ever experiencing problems with either Wine or Lutris inside a Toolbx/Distrobox container. I’m also confident that Bottles should work.
Does it’s need special dependencies to make it work ?
This is definitely something that might be at play. Consider reporting the terminal output whenever you try to work with Wine, Lutris and Bottles.
Furthermore, expect some containerized solutions tomorrow for these 😉.
Can packages that modifying system (ex green tunnel, vmware, or QEMU, & hblock ) work fine ?
I’m not familiar with all of them. Though, you may expect troubles. I do recall I had to resort to rpm-ostree
in order to make QEMU work. However, it’s a fast moving space, so I wouldn’t be surprised if Toolbx/Distrobox-based solutions exist for this. For example, since relatively recently, it has been possible to have a functioning Waydroid within Distrobox. I will also more exhaustively go over this matter tomorrow.
but photoshop/Adobe Creative suite is a must have… how is that on Linux these days?
This.
I could probably summarize your experience as “skill issue”.
I don’t understand the hype of immutables, or usability even.
I suppose this article/blogpost by Lennart Poettering should suffice. Though, this article/blogpost by Colin Walters is also cool.
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.
This is simply false as pointed out by others already.
I didn’t even have time to reach the software limitations with how fast I tried the next distro.
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.
Still hopping though, because apparently Fedora just nukes itself when you try to install codecs
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.
and I think I have about every major distro tested by now.
While this could be true, I wonder what prevented you from sticking with any one of them.
Linux is cursed.
It’s definitely a lot harder if you’ve got major skill issues.
Those definitely amount to a major difference. Thanks for clarifying!
Wait for Ubuntu Core Desktop to come out.
They offer ovpn configs that I can just add to the Network Manager, but a part of me doesn’t want to give up!
Does running the .run
script do substantially and functionally more than putting the ovpn configs in Network Manager?
Been trying for days to install Private Internet Access’s client in a custom Bazzite image, but it’s slow-going to troubleshoot each failure to build, and I feel like I’m fighting GitHub more than the install script.
Have you contacted the Discord servers for Bazzite/uBlue and/or BlueBuild in hopes of resolving the issue?
They’re cool and very much willing to help out. They solved my issues a bunch of times with my own custom image. Perhaps, they are even capable of offering a solution to resolve the problem without requiring a custom image.
Wish ya good luck!
Thank you so much for correcting me! I’ll edit my earlier post to reflect this! Your work on Bazzite is much appreciated! Thank you!
Thanks for the clarification! We actually run very similar systems; I’m on the hardened Bluefin-dx image as per secureblue.
Regarding Steam, Bazzite -one of Bluefin’s uBlue siblings- actually switched over to RPM Fusion’s Steam due to issues with the Flatpak. EDIT: The former is false. The Deck images have always been on RPM Steam. Only the Desktop images moved to RPM Steam (from Distrobox-Arch) for support consistency reasons. Appreciation goes out to quarterlife@lemmy.sdf.org for correcting me!
I don’t know what exactly is the way to go for you. But I can suggest the following possibilities (from own experience):
rpm-ostree
.Is this on one of Fedora’s images or on one of uBlue’s images? Regardless, could you specify what exactly we’re dealing with?
Thank you for the quick reply!
Thank you.
It has been my pleasure 😊!
I haven’t been following them lately so I do not know their reasons for deprecating hardened malloc, I assume there’s an explanation for it.
Pragmatism 😅; at least, that’s how I interpret their justifications.
Thanks for the note
Again. it has been my pleasure 😊!
Interesting. Thank you for sharing your experiences! Would you be so kind to elaborate on that experience? Did you like it? Are you still using it? Why or why not? Pros and Cons? Thank you in advance!
Unfortunately, neither do I. I hope this will be the last time you’ll have to face this issue.
First of all, apologies for delaying this answer.
Disclaimer:
Qubes OS >> secureblue >~ Kicksecure
Context: Answering this question puts me in a genuinely conflicted position 😅. I have immense respect for the Kicksecure project, its maintainers and/or developers. Their contributions have been invaluable, inspiring many others to pursue similar goals. Unsurprisingly, some of their work is also found in secureblue. So, to me, it feels unappreciative and/or ungrateful to criticize them beyond what I’ve already done. However, I will honor your request for the sake of providing a comprehensive and balanced perspective on the project’s current state and potential areas for improvement.
Considerations: It’s important to approach this critique with nuance. Kicksecure has been around for over a decade, and their initial decisions likely made the most sense when they started. However, the Linux ecosystem has changed dramatically over the last few years, causing some of their choices to age less gracefully. Unfortunately, like most similar projects, there’s insufficient manpower to retroactively redo some of their earlier work. Consequently, many current decisions might be made for pragmatic rather than idealistic reasons. Note that the criticisms raised below lean more towards the idealistic side. If resources allowed, I wouldn’t be surprised if the team would love to address these issues. Finally, it’s worth noting that the project has sound justifications for their decisions. It’s simply not all black and white.
With that out of the way, here’s my additional criticism along with comparisons to Qubes OS and secureblue:
Thanks for sharing the solution! Though, I wonder… What caused this issue in the first place?
Lacking features
It’s important to mention that the specific way by which ‘immutability’ and all of its associations are implemented, is key to determine what possible limitations are. Perhaps to gain a better grasp on this, consider reading this blog post. Note that due to the (very) active development ‘immutable’ distros enjoy, not everything found within that article is accurate.
and having to take weird extra steps to get what I want and tweak the system the way I want.
Does uninstalling Jokes aside, the way that ‘immutable’ distros want you to do stuff is simply unconventional compared to traditional distros. Heck, even the need to (soft-)reboot to apply changes to the base system is almost unheard of on traditional distros. However, unconventional does not necessarily imply weird. Care to elaborate when something goes from unconventional to weird?snapd
on Kubuntu fall under this?
I’m a bit of a power user and I’m wondering if a immutable distro could work for me over a regular one.
It depends on your priorities. There’s a ‘cost’ that comes with going ‘immutable’; mostly related to how it’s still relatively immature and/or unpopular. However, even in this state, there are problems it solves and tackles that traditional distros don’t.
Regarding ‘being a power user’, like what’s even the wildest thing you’d want to do?
Thanks for the reply and thanks for sharing your experiences!
Is this eduroam?