Full linux distros on Sailfish OS - Page 17 - maemo.org

spoofykid | # 161 | 2021-05-24, 20:08 | Report

Originally Posted by levone1 View Post

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 ...

Did you manage to open up the desktop? I'm running 4.1.0.23 on Xperia 10, and with Kabouik's guide I got harbour-containers running, and two desktops installed - Debian Sid and Kali - however, when I go to run them nothing happens (I start the service, and then pressing 'X session' achieves nothing). Am I doing something wrong? Thanks

The Following 2 Users Say Thank You to spoofykid For This Useful Post:
juiceme, mosen

levone1 | # 162 | 2021-05-24, 21:23 | Report

Originally Posted by spoofykid View Post

Did you manage to open up the desktop? I'm running 4.1.0.23 on Xperia 10, and with Kabouik's guide I got harbour-containers running, and two desktops installed - Debian Sid and Kali - however, when I go to run them nothing happens (I start the service, and then pressing 'X session' achieves nothing). Am I doing something wrong? Thanks

Does 'attach' work? If so, you can do it manually, (instructions from first post of Containers thread):

1. attach cintainer, (you will get a terminal window with 'root@(container)
2. open a separate terminal window on Sailfish, and type

Code:

/usr/bin/qxdisplay --wayland-socket-name "../../display/wayland-container-0"

(a new window will open with "waiting for xwayland"
3. in your first terminal, (attached container), enter

Code:

/mnt/guest/start_desktop.sh 0

Then the desktop will start in your "waiting for xwayland" Window.

As for why it happens, can't say for sure - maybe try chmod fix in post above...

The Following 3 Users Say Thank You to levone1 For This Useful Post:
juiceme, mosen, spoofykid

spoofykid | # 163 | 2021-05-25, 00:59 | Report

Originally Posted by levone1 View Post

Does 'attach' work?...

Thanks for your help - but I'm still not getting anywhere - more than likely me just doing things wrong.

If someone wouldn't mind checking my process over, I'd be very grateful. This is what I did from the very beginning:

In a terminal I ran:

Code:

zypper in nemo-qml-plugin-dbus-qt5 sailfish-polkit-agent python3-base python3-gobject dbus-python3

Then installed lxc-templates-desktop, qxdisplay, and harbour-containers.
I swapped the daemon.py file out and made it executable.
I installed Debian Sid and Kali desktops (with 'Setup desktop' selected).
They wouldn't open so I cried for a bit.

I then attached a container, and ran in a second terminal:

Code:

/usr/bin/qxdisplay --wayland-socket-name "../../display/wayland-container-0"

This opened the "waiting for xwayland" screen.

I then tried to run:

Code:

/mnt/guest/start_desktop.sh 0

But it didn't work, so I cried again, this time clutching my childhood teddy bear.
I checked /var/lib/lxc/<container_name>/config and it seemed fine (maybe what I think was fine wasn't)
I then (in an attached container) ran:

Code:

/mnt/guest/setup_desktop.sh

and

Code:

/mnt/guest/setups/debian.sh

It seemed to go through the same process as when first installing the desktops through the GUI.
I then again ran (in another terminal window):

Code:

/usr/bin/qxdisplay --wayland-socket-name "../../display/wayland-container-0"

"waiting for xwayland" screen came up, and in a new terminal window I attached a container and ran:

Code:

/mnt/guest/start_desktop.sh 0

But to no avail.

This is what stops me getting any further it seems:

Code:

could not connect to wayland server
(EE)
Fatal server error:
(EE) Couldn't add screen
(EE)
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Any ideas what I'm doing wrong? I'm running 4.1.0.23 on Xperia 10. Thank you.

Last edited by spoofykid; 2021-05-27 at 02:10.

The Following 2 Users Say Thank You to spoofykid For This Useful Post:
juiceme, Kabouik

jellyroll | # 164 | 2021-05-25, 02:48 | Report

Originally Posted by spoofykid View Post

Thanks for your help - but I'm still not getting anywhere - more than likely me just doing things wrong.

If someone wouldn't mind checking my process over, I'd be very grateful. This is what I did from the very beginning:

In a terminal I ran:

Code:

zypper in nemo-qml-plugin-dbus-qt5 sailfish-polkit-agent python3-base python3-gobject dbus-python3

Then installed lxc-templates-desktop, qxdisplay, and harbour-containers.
I swapped the daemon.py file out and made it executable.
I installed Debian Sid and Kali desktops (with 'Setup desktop' selected).
They wouldn't open so I cried for a bit.

I then attached a container, and ran in a second terminal:

Code:

/usr/bin/qxdisplay --wayland-socket-name "../../display/wayland-container-0"

This opened the "waiting for xwayland" screen.
I couldn't run '/mnt/guest/start_desktop.sh 0' as /mnt/guest didn't exist. I tried running '/usr/share/harbour-containers/scripts/guest/start_desktop.sh 0' but that couldn't find the file (dump thing to try?)
I created a guest folder in /mnt and copied everything from /usr/share/harbour-containers/scripts/guest/ into it.

I then tried to run:

Code:

/mnt/guest/start_desktop.sh 0

But it didn't work, so I cried again, this time clutching my childhood teddy bear.
I checked /var/lib/lxc/<container_name>/config and it seemed fine (maybe what I think was fine wasn't)
I then (in an attached container) ran:

Code:

/mnt/guest/setup_desktop.sh

and

Code:

/mnt/guest/setups/debian.sh

It seemed to go through the same process as when first installing the desktops through the GUI.
I then again ran (in another terminal window):

Code:

/usr/bin/qxdisplay --wayland-socket-name "../../display/wayland-container-0"

"waiting for xwayland" screen came up, and in a new terminal window I attached a container and ran:

Code:

/mnt/guest/start_desktop.sh 0

But to no avail.

This is what stops me getting any further it seems:

Code:

could not connect to wayland server
(EE)
Fatal server error:
(EE) Couldn't add screen
(EE)
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Any ideas what I'm doing wrong? I'm running 4.1.0.23 on Xperia 10. Thank you.

You need to start and attach the container after the setup. Have you tried?

Code:

/bin/sh /mnt/guest/start_desktop.sh 0 root &

The Following 3 Users Say Thank You to jellyroll For This Useful Post:
juiceme, Kabouik, spoofykid

levone1 | # 165 | 2021-05-25, 03:24 | Report

Originally Posted by spoofykid View Post

Thanks for your help - but I'm still not getting anywhere - more than likely me just doing things wrong.

If someone wouldn't mind checking my process over, I'd be very grateful. This is what I did from the very beginning:

In a terminal I ran:

Code:

zypper in nemo-qml-plugin-dbus-qt5 sailfish-polkit-agent python3-base python3-gobject dbus-python3

Then installed lxc-templates-desktop, qxdisplay, and harbour-containers.
I swapped the daemon.py file out and made it executable.
I installed Debian Sid and Kali desktops (with 'Setup desktop' selected).
They wouldn't open so I cried for a bit.

I then attached a container, and ran in a second terminal:

Code:

/usr/bin/qxdisplay --wayland-socket-name "../../display/wayland-container-0"

This opened the "waiting for xwayland" screen.
I couldn't run '/mnt/guest/start_desktop.sh 0' as /mnt/guest didn't exist. I tried running '/usr/share/harbour-containers/scripts/guest/start_desktop.sh 0' but that couldn't find the file (dump thing to try?)
I created a guest folder in /mnt and copied everything from /usr/share/harbour-containers/scripts/guest/ into it.

I then tried to run:

Code:

/mnt/guest/start_desktop.sh 0

But it didn't work, so I cried again, this time clutching my childhood teddy bear.
I checked /var/lib/lxc/<container_name>/config and it seemed fine (maybe what I think was fine wasn't)
I then (in an attached container) ran:

Code:

/mnt/guest/setup_desktop.sh

and

Code:

/mnt/guest/setups/debian.sh

It seemed to go through the same process as when first installing the desktops through the GUI.
I then again ran (in another terminal window):

Code:

/usr/bin/qxdisplay --wayland-socket-name "../../display/wayland-container-0"

"waiting for xwayland" screen came up, and in a new terminal window I attached a container and ran:

Code:

/mnt/guest/start_desktop.sh 0

But to no avail.

This is what stops me getting any further it seems:

Code:

could not connect to wayland server
(EE)
Fatal server error:
(EE) Couldn't add screen
(EE)
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Any ideas what I'm doing wrong? I'm running 4.1.0.23 on Xperia 10. Thank you.

seems like desktop is not fully set up. Do you have /mnt/guest/setup_desktop.sh? Try running tjat. It's different than debian.sh, which is just the initial container creation script (I think) for rootfs, etc. Desktop setup is pretty extensive. It downloads a few hundred mb and takes 10-15 minutes ...

Also check if you have /opt/bin/xwayland. It's created during desktop setup, so if that's not there, its not going to work...

Last edited by levone1; 2021-05-25 at 03:30.

The Following 4 Users Say Thank You to levone1 For This Useful Post:
juiceme, Kabouik, mosen, spoofykid

spoofykid | # 166 | 2021-05-25, 10:29 | Report

Thank you both. Unfortunately I was dumb and assumed my kernel was fine - it wasn't. Sorry for wasting your time.

I have no idea how to recompile a kernal, so I think this is the end for me. Thanks for the help.

Code:

[root@Xperia10 defaultuser]# ls -lha /dev/pts/
total 0
drwxr-xr-x    2 root     root           0 May 25 17:23 .
drwxr-xr-x   23 root     root        7.8K May 25 17:26 ..
c--x--x--x    1 root     tty       136,   0 May 25 17:56 0
crw--w----    1 defaultu tty       136,   1 May 25 22:12 1
c---------    1 root     root        5,   2 May 25 17:23 ptmx

[root@Xperia10 defaultuser]# ls -l /dev/ptmx /dev/pts/ptmx
crw-rw-rw-    1 root     root        5,   2 May 25 22:12 /dev/p
tmx
c---------    1 root     root        5,   2 May 25 17:23 /dev/p
ts/ptmx

[root@Xperia10 defaultuser]#     zcat /proc/config.gz | grep CO
NFIG_DEVPTS_MULTIPLE_INSTANCES
[root@Xperia10 defaultuser]#

[root@Xperia10 defaultuser]# lxc-checkconfig
--- Namespaces ---
Namespaces: enabled
Utsname namespace: enabled
Ipc namespace: enabled
Pid namespace: enabled
User namespace: enabled
newuidmap is not installed
newgidmap is not installed
Network namespace: enabled

--- Control groups ---
Cgroups: enabled

Cgroup v1 mount points:
/sys/fs/cgroup/systemd
/sys/fs/cgroup/blkio
/sys/fs/cgroup/cpu,cpuacct
/sys/fs/cgroup/net_cls
/sys/fs/cgroup/devices
/sys/fs/cgroup/perf_event
/sys/fs/cgroup/memory
/sys/fs/cgroup/freezer

Cgroup v2 mount points:
/sys/fs/cgroup/unified

Cgroup v1 clone_children flag: enabled
Cgroup device: enabled
Cgroup sched: enabled
Cgroup cpu account: enabled
Cgroup memory controller: enabled
Cgroup cpuset: missing
--- Misc ---
Veth pair device: enabled, not loaded
Macvlan: enabled, not loaded
Vlan: enabled, not loaded
Bridges: enabled, not loaded
Advanced netfilter: enabled, not loaded
CONFIG_NF_NAT_IPV4: enabled, not loaded
CONFIG_NF_NAT_IPV6: enabled, not loaded
CONFIG_IP_NF_TARGET_MASQUERADE: enabled, not loaded
CONFIG_IP6_NF_TARGET_MASQUERADE: missing
CONFIG_NETFILTER_XT_TARGET_CHECKSUM: enabled, not loaded
CONFIG_NETFILTER_XT_MATCH_COMMENT: enabled, not loaded
FUSE (for use with lxcfs): enabled, not loaded

--- Checkpoint/Restore ---
checkpoint restore: enabled
CONFIG_FHANDLE: enabled
CONFIG_EVENTFD: enabled
CONFIG_EPOLL: enabled
CONFIG_UNIX_DIAG: enabled
CONFIG_INET_DIAG: enabled
CONFIG_PACKET_DIAG: enabled
CONFIG_NETLINK_DIAG: enabled
File capabilities:

Note : Before booting a new kernel, you can check its configura
tion
usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig

The Following 3 Users Say Thank You to spoofykid For This Useful Post:
juiceme, levone1, mosen

wganis | # 167 | 2021-05-25, 11:40 | Report

Alo i have gemini x27 if i run sailfish can this method run well on my gemini thx a lot

The Following User Says Thank You to wganis For This Useful Post:
juiceme

Kabouik | # 168 | 2021-05-25, 11:58 | Report

If all of you have Github accounts, I think it would be easier to troubleshoot, track and discuss on Github. It would also make the solution (if we ever find one) much more discoverable for new users. We can then post here an URL to the fix when we have one.

What device are you using Spookyfid? I may have missed something but I don't see missing requirements in your lxc-checkconfig. [Edit] Oh, except maybe CONFIG_DEVPTS_MULTIPLE_INSTANCES.

Last edited by Kabouik; 2021-05-25 at 12:06.

The Following 3 Users Say Thank You to Kabouik For This Useful Post:
juiceme, mosen, spoofykid

ibins | # 169 | 2021-05-25, 15:46 | Report

@spoofykid: eventually your kernel does have these config options not compiled in but they exist as modules? In that case you could load them. For all the netfilter modules: I doubt, you would really need them
You find the available modules in /lib/modules/4.<version_of_kernel>

Strange, that these kernel configs differ so much.
I'm on pro1 firmware 4.0 and namespace "User" is missing! All others are compiled in.

The Following 3 Users Say Thank You to ibins For This Useful Post:
juiceme, mosen, spoofykid

spoofykid | # 170 | 2021-05-25, 19:57 | Report

@Kabouik I'm running an Xperia 10 (Single Sim). I'm missing multiple instances and cpusets when doing the check. However, as @ibins has rightly pointed out, my kernel (4.9.230) doesn't have it compiled in and it shouldn't need it (from what I understand). Looking here lxc-checkconfig only checks for multiple instances on a kernel higher than 4.6:

Code:

if ([ $KVER_MAJOR -lt 4 ]) || ([ $KVER_MAJOR -eq 4 ] && [ $KVER_MINOR -lt 7 ]); then
	echo -n "Multiple /dev/pts instances: " && is_enabled DEVPTS_MULTIPLE_INSTANCES
fi

I'll redo the install. I don't know what's holding it back, but for any further troubleshooting I'll move it to Github. Thanks again.

The Following User Says Thank You to spoofykid For This Useful Post:
juiceme