Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 2 days, 5 hrs ago -
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 4 days, 2 hrs ago -
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 4 days, 23 hrs ago - more...
|
2021-05-23
, 13:19
|
|
Posts: 1,335 |
Thanked: 3,931 times |
Joined on Jul 2010
@ Brittany, France
|
#152
|
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.
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.
|
|
2021-05-23
, 13:53
|
|
Posts: 202 |
Thanked: 385 times |
Joined on Jul 2018
|
#153
|
Originally Posted by Kabouik
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.
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.
Am I understanding wrong?
EDIT - never mind... I think my process was dead already...
Last edited by levone1; 2021-05-23 at 15:21.
|
|
2021-05-23
, 13:54
|
|
Posts: 202 |
Thanked: 385 times |
Joined on Jul 2018
|
#154
|
Originally Posted by Fellfrosch
Maybe try Mashka to delete any lingering data/configs from previous installations, and even search filesystem for traces of "harbour-containers" and delete everything...
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....
|
|
2021-05-23
, 21:44
|
|
Posts: 1,335 |
Thanked: 3,931 times |
Joined on Jul 2010
@ Brittany, France
|
#155
|
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.
|
|
2021-05-24
, 03:13
|
|
Posts: 14 |
Thanked: 28 times |
Joined on May 2021
|
#156
|
Originally Posted by Kabouik
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.
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.
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.
|
|
2021-05-24
, 10:56
|
|
Posts: 14 |
Thanked: 28 times |
Joined on May 2021
|
#157
|
Originally Posted by levone1
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.
Maybe try Mashka to delete any lingering data/configs from previous installations, and even search filesystem for traces of "harbour-containers" and delete everything...
 |
|
2021-05-24
, 12:18
|
|
Community Council |
Posts: 1,669 |
Thanked: 10,225 times |
Joined on Nov 2014
@ Lower Rhine
|
#158
|
Originally Posted by spoofykid
You could first of all look which containers exist with
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.
Code:
lxc-ls
Then delete the one that failed to set up with
Code:
lxc-destroy <CONTAINERNAME>
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
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?
__________________
Watch our weird watchfaces for mighty AsteroidOS
Performance comparison Video Sailfish 2.0 vs 1.1.9 vs 1.1.7
[MC eV] Maemo Community eV membership application please concider to join!
Watch our weird watchfaces for mighty AsteroidOS
Performance comparison Video Sailfish 2.0 vs 1.1.9 vs 1.1.7
[MC eV] Maemo Community eV membership application please concider to join!
|
|
2021-05-24
, 13:02
|
|
Community Council |
Posts: 1,669 |
Thanked: 10,225 times |
Joined on Nov 2014
@ Lower Rhine
|
#159
|
Originally Posted by levone1
Sorry for spotting this only just now.
So I did a clean flash of 4.0...
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!
__________________
Watch our weird watchfaces for mighty AsteroidOS
Performance comparison Video Sailfish 2.0 vs 1.1.9 vs 1.1.7
[MC eV] Maemo Community eV membership application please concider to join!
Watch our weird watchfaces for mighty AsteroidOS
Performance comparison Video Sailfish 2.0 vs 1.1.9 vs 1.1.7
[MC eV] Maemo Community eV membership application please concider to join!
| The Following User Says Thank You to mosen For This Useful Post: | ||
|
|
2021-05-24
, 19:44
|
|
Posts: 14 |
Thanked: 28 times |
Joined on May 2021
|
#160
|
Originally Posted by mosen
Thank you! So easy. It brought my harbour-containers back to life.
...
Then delete the one that failed to set up with
...Code:lxc-destroy <CONTAINERNAME>
Originally Posted by Kabouik
Thanks - this worked for me. It might be worth noting (for people like me) that you need to make the copied file executable
...
And then replace your /usr/share/harbour-containers/service/daemon.py with the one in the fork above.
...
Code:
chmod +x daemon.py
 |
| Tags |
| application, development, linux |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 08:51.
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....