-
Notifications
You must be signed in to change notification settings - Fork 380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: cannot link container's themes to host home. #13
Comments
Hey @alxlg thanks for the report! Yes the idea is to link the hosts's themes (from /run/host) to the container so to try and have a bit of consistency for the graphical apps Seeing that seems a permission problem, is the themes folder in your home belonging to another user or has some restrictions? |
But that is not the reason it is failing to create the container seems like there is a problem in the what image are you using? |
I've pushed version 1.0.3, it should fix this issue putting a Also I've for now removed the themes/icon integration as it's not a solid solution and for now I prefer to be more reliable than featurefull 😅 |
Wow, just wow! It does indeed works now, I entered the Fedora 35 container, installed Nautilus and launched it: I am on KDE Neon and it works perfectly. I love how you carefully designed the UX for novices. With few intuitive commands now I able to run GTK apps without messing up my system. I can't wait to try this with the nightly images that KDE Neon provides. This should definetely be advertised also in KDE land, since now the best way to develop for KDE is using Neon's script that is a very simple version of yours but just for running Neon's images. About the themes/icons thing, it would be nice to have it as an option in future. Also I can definetely see the GTK/GNOME/Fedora folks take the opportunity to build a GUI tool on top of yours, to make it even easier to use. |
Cool glad it fixed it! 😄
Yep I've opened an issue #15 to adress this in the future
Hehe yea I would really like to give it a shot myself with GTK4 but that's something definitely for the future 😄 As the issue is solved, I'll close the bug report |
Can't initialize the container, what's the rationale of these themes/icons operations? Here there's the log:
The text was updated successfully, but these errors were encountered: