Re: Full linux distros on Sailfish OS
 

Hi guys, I am trying to get `debian.sh` to start from ShellEx - is there any way to work around the su requirement for lxc-attach apart from enabling passwordless execution for defaultuser in /etc/sudoers? I couldn't find an askpass program for SFOS either.

Re: Full linux distros on Sailfish OS
 

Try qCommand instead...

Re: Full linux distros on Sailfish OS
 

Has anyone been able to get the camera working in the LXC container? I bind-mounted all the video* devices and they are showing correctly in /dev but am having no luck with any applications.

Re: Full linux distros on Sailfish OS
 

Which have you tried? I tried Cheese, Pinhole and Megapixels. Cheese starts and gives "no device found", Pinhole starts but gives error "viewfinder is not in ready state", and Megapixels won't start, shows error in terminal about "...no config file".

Can you tell me the proper mount command for video devices? Attempting 'ls -ltr /dev/video*' gives, "no such file or directory" ...

Re: Full linux distros on Sailfish OS
 

I added the following lines into my /var/lib/lxc/Debian/config:

lxc.cgroup.devices.allow = c 81:* rwm
lxc.mount.entry = /dev/video0 dev/video0 none bind,create=file 0 0
lxc.mount.entry = /dev/video1 dev/video1 none bind,create=file 0 0
lxc.mount.entry = /dev/video2 dev/video2 none bind,create=file 0 0
lxc.mount.entry = /dev/video32 dev/video32 none bind,create=file 0 0
lxc.mount.entry = /dev/video33 dev/video33 none bind,create=file 0 0

I can see the devices inside the container's /dev. But none of the apps seem to be able to work with them.

Re: Full linux distros on Sailfish OS
 

Hi,

lurker of the forums here, I upgraded my phone 4.0.1.48, tried to use harbour-containers without success. The xwayland display failed to start. I have not tried to trouble start as of yet.

Re: Full linux distros on Sailfish OS
 

Welcome mibry!

Since you are in devel waters it is best to first ask Adam in person on Telegram how (and wether) to update at all ;)

@bundyo might have advise since he upgraded to 4.0.1 very early successfully. He needed to manually downgrade some packages afair.
Adams Pro¹ related Telegram group again:
https://t.me/sfos_user_pro1

Re: Full linux distros on Sailfish OS
 

Thanks, I reflashed my pro1 back to 3.4.

Re: Full linux distros on Sailfish OS
 

Is there any plans to update for sailfish 4 without having to downgrade RPM's?

Thanks in advance.

Re: Full linux distros on Sailfish OS
 

I didn't downgrade - just some packages changed naming, so I had to do that before upgrading. Not sure, but I think in testing there's no need to manually do that anymore. You can ask Adam in the Telegram chat.

Re: Full linux distros on Sailfish OS
 

@edp17 - question ... I am finding that X session is not working in harbour-containers app. I heard on Telegram that it has been happening with 4.0 due to the change from nemo to defaultuser, and can be fixed by creating a defaultuser symlink, or rebuilding the app with a code change. I was going to work on that, but then I see that the default user on XZ2c is still nemo, not defaultuser. Any thoughts ?

Re: Full linux distros on Sailfish OS
 

On SFOS 4.0, default user would depend on whether you've got to 4.0 via OTA or fresh install. That should be for all official and on ports as Xperia Tama.

As a result: if you flash new 4.0 image -> defaultuser is used

if you come from earlier versions -> nemo is kept.

I don't remember when the user name switch happened. I have a feeling it was earlier than 4.0

Re: Full linux distros on Sailfish OS
 

ok. So must be something else...

Re: Full linux distros on Sailfish OS
 

the switch to defaultuser came with release 3.4. Since then I'm not able to start a containers on my Pro1. I fiddled around with symlinks and changes in the scripts. Even so I got X session to run, I haven't got a running container. I still hope there will be new packages which fixes these problems.

Re: Full linux distros on Sailfish OS
 

Yes, it was introduced with SFOS 3.4.0.

Re: Full linux distros on Sailfish OS
 

started a new container from scratch (Debian Sid) and working fine now...

Re: Full linux distros on Sailfish OS
 

What steps exactly have you done?
I'm still struggeling to get a running container on 3.4.

Re: Full linux distros on Sailfish OS
 

I've only gotten Xsession to work on Debian Sid and Devuan...
Start from scratch, open app and create new container, with "set up desktop" option checked. Let it go through the whole container setup, and also Xwayland build process. Don't lose internet connection and don't interrupt the process. The whole thing is 15-20 mins. Yhe terminal will close automatically whrn done. Then you can start the container and tap Xsession button, and should work.

I'm using XZ2compact ...

Re: Full linux distros on Sailfish OS
 

So you have made no adpations in the scripts to the new username defaultuser???
:eek:

Re: Full linux distros on Sailfish OS
 

Maybe he has a symlink from nemo to defaultuser.

Re: Full linux distros on Sailfish OS
 

Well, I have that as well. I see, i have to make further tries on that side.

Re: Full linux distros on Sailfish OS
 

I have updated ota since 3.2, so still on nemo... (defaultuser gets written in on clean install)

Re: Full linux distros on Sailfish OS
 

Thanx for clarification!

Re: Full linux distros on Sailfish OS
 

So I did a clean flash of 4.0, and decided to tinker with Containers for defaultuser, and it's actually pretty simple:
1 - download source
2 - make change to daemon.py file
3 - add %setup line to spec

Then just use rpmbuild to create rpm. Installs and runs normally ...

Re: Full linux distros on Sailfish OS
 

We should raise a PR for that, but I have not found how to write it so that daemon.py would work with any user name, not just defaultuser. Maybe using `import os` and then `os.environ.get('USER')` would work?

Anyone willing to try with this commit/fork? I don't have a device ready to try and I'm not prepared to compromise my LXC install right now as I really depend on it, but if that works, I can submit the PR.

I am sorry I didn't read TMO lately but I see this is being discussed since March, while others had found the same the same temporary workaround at some earlier point on either the Telegram or Discord groups.

Re: Full linux distros on Sailfish OS
 

I do not have any Sailfish devices currently, so I can't test it, but since you are on the quest of fixing the problem by removing coded in constants which are actually environment variables (ok for early test, no-go for release), you could try to also remove the fixed UID by using os.getuid(). :)

Re: Full linux distros on Sailfish OS
 

I built rpm using your daemon.py, and it is working fine. I already had Containers installed, and had a working Debian container, and I just uninstalled my Containers app, and installed the new build, so maybe not the best test... I can upload/link rpm if appropriate ....

Re: Full linux distros on Sailfish OS
 

Thanks to both of you! I added `os.getuid()` too as you recommended txus. I'll try to get someone to test it on a device with no current installation of LXC and no existing container, in case that matters. I'll submit a PR if that works.

Re: Full linux distros on Sailfish OS
 

I have currently no running containers. So I can test for you. So what do I have to do?
At first uninstall LXC if I got you right... And then? What rpms should I install?

Re: Full linux distros on Sailfish OS
 

You could install the rpm that is already compiled on the Github repository, which you may already have.

Then kill the daemon: run "ps aux | grep daemon.py", then "kill -9 <daemon.py PID>".

And then replace your /usr/share/harbour-containers/service/daemon.py with the one in the fork above. Make sure you download the raw daemon.py and not the HTML view. And reboot.

One thing to keep in mind is you may have leftover configs in /var/lib/lxc. So if that doesn't work, it might be worth checking those and/or creating a new container, to make sure the configs are not still trying to use nemo.

Re: Full linux distros on Sailfish OS
 

It doesn't work.
But that has nothing to do with your patch!

It seems like I have something destroyed with my fiddeling around on lxc. If i try to create a container. It there is the information that the container is running the setup, but after that the container wich was initially shown vanishes and that's it. (No matter if I use the original deamon.py or yours) So I have first to look what I have borked on my system.

I'm grateful for tipps. I have already deinstalled lxc many times and have searched for directories with the name lxc on my file system to empty them. Unfortunately with no success regarding the container setup. I have to dig deeper I fear....

Re: Full linux distros on Sailfish OS
 

Hum, I'm not sure exactly where your issue comes from. Do you have files in the folders I mentioned in my previous post?

Thanks for trying anyway! Note that I forgot to mention this would be tried without nemo/defaultuser symlink, else LXC could work because of that and not because of the patch.

Re: Full linux distros on Sailfish OS
 

Question - I wanted to try this method out of curiosity, since I'm interested in learning more about dbus, etc... I assume from your post that the first command (grep) is for the purpose of getting the PID of daemon.py, to use for the second command, to kill the service. But, when I use the 2nd command with the number I get frim the output of the first command, I get "... no process with PID... " error.
Am I understanding wrong?
EDIT - never mind... I think my process was dead already...

Re: Full linux distros on Sailfish OS
 

Maybe try Mashka to delete any lingering data/configs from previous installations, and even search filesystem for traces of "harbour-containers" and delete everything...

Re: Full linux distros on Sailfish OS
 

Maybe the PID you saw and tried to kill was that of `grep daemon.py` itself levone1, if the daemon was already stopped in your case.

Re: Full linux distros on Sailfish OS
 

Hi. I thought to give this a go, as I do not have nemo as my username. This is a fresh install. I went through the guide to install everything, and then followed your guide to replace daemon.py. I also had the "... no process with PID... " error when killing the service. I then used terminal to remove the old daemon.py file and copy the new one over. I then rebooted.

But now, when I open the container, there is nothing there. It doesn't not show Alien Dalvik or the option to create a new container. It only shows the menu of Freeze/Stop all, and about.

Any suggestions?
Thank you.

Re: Full linux distros on Sailfish OS
 

Would someone mind writing a description of how to uninstall harbour-containers please? After attempting to install a distro, the container stopped showing anything, and I don't know how to restart it to get working again. Any help for a noob would be awesome. Thanks.

Re: Full linux distros on Sailfish OS
 

You could first of all look which containers exist with
It will show aliendalvik if installed and additional containers you set up.

Then delete the one that failed to set up with
Use brackets if your container name has spaces like "debian sid".
harbour-containers did then start up again in my case.

I am on 4.0.1.48 on Pro¹ and in process to figure out how to set up debian so Kabouik can finally move to 4.0 from 3.3 :D

It would be great if someone could post instuctions how to create and setup a debian container from CLI. That way i could supply the logs here. I figure the ones from first post are outdated?

Re: Full linux distros on Sailfish OS
 

Sorry for spotting this only just now.
Your wording implies one of the Pro¹ 4.0 images actually worked?
Or did you flash 3.4 and then OTA to 4.0?

I tried to flash all of the 4.0 images listed in the gitlab artifacts and they did not work for me.
Adam would be quite relieved to hear they actually work and it was my error they did not!

Re: Full linux distros on Sailfish OS
 

Thank you! So easy. It brought my harbour-containers back to life.

Thanks - this worked for me. It might be worth noting (for people like me) that you need to make the copied file executable otherwise the container application opens with nothing in it.