Void of content

[nerd7473]

The Containers app stops showing content after icons are added...

[Kabouik]

Can you make sure the daemon is not in a broken state by killing it and restarting it? You can kill it with:

ps aux | grep daemon.py
kill -9 <PID>

An empty UI is typically what would happen when the daemon is not properly restarted, maybe adding the icons broke something on your instance.

[nerd7473]

Restarting the app still shows a blank UI.

[nerd7473]

I'd killed the daemon.py PID, but there was one for root, and one for "default+"...

[Kabouik]

After killing the process daemon-py from terminal, correct? The app itself is just a GUI but the process still runs in the background if you close the app.

…

On 2021-05-21 22:55 Clayton Rego ***@***.***> wrote: Restarting the app still shows a blank UI. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #21 (comment) suecomment-846254633

[Kabouik]

Just out of curiosity, have you tried rebooting? If you did and it didn't help, then definitely it's not what I have in mind.

…

On 2021-05-21 22:55 Clayton Rego ***@***.***> wrote: I'd killed the daemon.py PID, but there was one for root, and one for "default+"... -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #21 (comment) suecomment-846254901

[Kabouik]

Also please give more details about your setup. - Did you have containers installed and running before or is it your first attempt? - SFOS version and is your user named nemo or default-user? In the latter case, please kill the daemon again and try replacing /usr/share/harbour-containers/service/daemon.py with the version from https://github.com/kabouik/harbour-containers, then reboot. No guarantee as this is still untested, but it might work. - Which phone?

…

On 2021-05-21 22:55 Clayton Rego ***@***.***> wrote: I'd killed the daemon.py PID, but there was one for root, and one for "default+"... -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #21 (comment) suecomment-846254901

[nerd7473]

This is my first attempt. Device details are as follows:

• Xperia 10 Plus Dual-SIM
• SailfishOS/X 4.1.0.23 Kvarken

[Kabouik]

Your user is named "default-user", not "nemo". Correct? In that case try the version of daemon.py in the fork I linked and replace yours with it (after killing the daemon as we did above). It's still not tested but if that works for you, then I know I can submit a PR.

…

On 2021-05-21 23:12 Clayton Rego ***@***.***> wrote: This is my first attempt. Device details are as follows: - Xperia 10 Plus Dual-SIM - SailfishOS/X 4.1.0.23 Kvarken -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #21 (comment) suecomment-846262549

[nerd7473]

That did not fix the issue unfortunately, I know I encountered the error after changing the icons for aliendalvik and my Arch Linux container...

[nerd7473]

Also, /home/defaultuser/.local/share/lxc is not present...

[nerd7473]

I suspect this is a deeper issue.

[nerd7473]

If there's any loginfo I can give that might help resolve this and lead to a fix that allows for an acceptable build, let me know.

[Kabouik]

That did not fix the issue unfortunately, I know I encountered the error after changing the icons for aliendalvik and my Arch Linux container...

I'm confused, I thought you said it was your first attempt when I asked if you had containers installed and running before.

I have no /home/.local/share/lxc either, the content is in /home/.lxc for me. Then there are also configuration files in /var/lib/lxc/ and application files (like daemon.py) in /usr/share/harbour-containers.

[nerd7473]

Just an issue when running lxc... I was thinking I could find some answers that way...

[nerd7473]

Need a dump of cat /home/.lxc and devel-su ls -la /usr/share/harbour-containers?

[nerd7473]

And if I get this whole thing working, is it possible to migrate the container itself to my SD card and symlink it?

[Kabouik]

Do post anything you have that might be relevant, it doesn't hurt.

I admit I still don't understand your setup though, it's not clear to me whether you had a container working at some point or not. I'm surprised for example that you mentioned Arch, while the installation scripts provided with harbour-containers are all tailored to Debian (but if you modified them to make Arch work, then please share them!).

If you have no working container and therefore have nothing to lose, then you could try destroying the one you tried to create using lxc-destroy. This should fix your harbour-containers being empty and you could start again with a Debian container instead of Arch, see if it yields better results (but I think the issue is somewhere else, so don't set your expectations too high yet). See: https://github.com/sailfish-containers/lxc-templates-desktop/wiki/Usage

When you get the thing working, you can totally move the container to your SD card and use symlinks. I think I did it for my Kali container.

[Kabouik]

Please try the new version in Chum repository (Testing repository for now, hopefully it makes it to the main repository later today).