Containerized Apps Will Not Launch
Hello, I really do like the concept of the OS and really want it to work. However, it has given me nothing but trouble.
Most of the time, a .deb or .rpm install will go through. The deb installations tend to fail more often, but that is a different issue and I can deal with that a bit.
What I am struggling with is that the apps installed in a container will not launch. For example, I installed anytype to Fedora and it said that it was installed successfully. When I went to try and launch it, the icon would spin. However, the application would not launch at all.
I have tried restarting the computer and then launching.
I have tried installing the same application across various other containers.
I have tried different .deb packages.
The only .deb package I have gotten to work was appimagelauncher. And even that threw some errors during installation. For whatever reason though, it launched.
Any help would be appreciated.
11 Replies
try opening apps from the terminal
Binaries on blendOS
Call a binary like so:
[BINARY_NAME].[CONTAINER_NAME]
More info: https://docs.blendos.co/guides/container-guideHow would I go about finding the right command to launch the app? I tried to open the .desktop file but wasn't able to figure out how to properly use hte command. And would I launch it from inside the container or from the native terminal?
The package name should do
Use Tab from within a container shell to autocomplete
Thanks, this is what I got in the output.
[hiccup@debian ~]$ vencorddesktop
vencorddesktop: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory
[hiccup@debian ~]$
ﾑ丂ｲ乇尺ﾉ丂ズ received a thank you Jao!
k, vencord desktop is in alpha
I'd recommend Armcord
Let me see if it does it with another app.
but I assume this isn't the only app to fail
Yep, same thing happened with anytype deb
[hiccup@blend ~]$ anytype.debian
anytype: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory
[hiccup@blend ~]$
Haha! Solution!
I did what I normally did when I don't know how to fix a problem on linux. Search the output and start running commands. Turns out, "sudo apt install libasound2" will allow everything to launch easily. Thanks for the help everyone and I hope this will help someone else.
lmao