Thread: Full linux distros on Sailfish OS
View Single Post
spoofykid is offline spoofykid
2021-05-29 , 10:15
Posts: 14 | Thanked: 28 times | Joined on May 2021
#184
Originally Posted by Kabouik View Post
I have no idea where the qxdisplay.desktop error comes from, I can't see a qxdisplay.desktop file being called anywhere in the lxc-templates or harbour-containers source files. I suspect it's some other UNIX tool getting in the way somewhere and automatically expecting a desktop file?

Was the container started with the LXC-attach button when you ran the following command?

Code:
/usr/bin/qxdisplay -o landscape --wayland-socket-name "../../display/wayland-container-0
Can you try that one instead where I change the display?

Code:
qxdisplay -o landscape -d ../../display/wayland-container-1
In case you haven't, you should start the container first, attach to it using LXC-attach, and then in a different terminal window, as defaultuser, use that above command.

....
I'm not really sure what happened but I got it going - Kali and Debian desktops opened. I placed in your daemon.py and debian.sh files, and then Iinstalled everything through GUI.
What was probably going wrong was I was running the below code as root - as when you select 'attach' in the Container GUI, and then open a new window (from that terminal window) it automatically opens the new window as root (I didn't think this would cause issues, but it obviously did).
Code:
qxdisplay -o landscape -d ../../display/wayland-container-1
Initially I wondered whether it was working because I would run the above code, then select 'X session' in the GUI, and then run the below code in the attached terminal. I think it was the silly root thing.
Code:
 /mnt/guest/start_desktop.sh 0
Below are the resulting errors/info after running the scripts, if anything is useful to know.

Code:
[defaultuser@Xperia10 ~]$ /usr/bin/qxdisplay -o landscape --way
land-socket-name "../../display/wayland-container-0"
[D] unknown:0 - Using Wayland-EGL
[D] unknown:0 - Specified Desktop file does not exist "/usr/sha
re/applications/qxdisplay.desktop"
[W] unknown:0 - Theme dir "/usr/share/themes/jolla/meegotouch/z
1.5/" does not exist
[W] unknown:0 - Theme dir "/usr/share/themes/jolla/meegotouch/z
1.5/" does not exist
[W] unknown:65 - file:///usr/share/qxdisplay/qml/compositor/XWa
ylandContainer.qml:65: TypeError: Cannot read property 'surface
' of null
qxdisplay.desktop seemed to actually cause no issues, so apologies about that !!

Code:
root@Kali:/# /mnt/guest/start_desktop.sh 0
xauth:  file /home/user/.Xauthority does not exist

glamor: 'wl_drm' not supported
Missing Wayland requirements for glamor GBM backend
Failed to initialize glamor, falling back to sw
xinit: XFree86_VT property unexpectedly has 0 items instead of 1
The XKEYBOARD keymap compiler (xkbcomp) reports:
Warning:          Unsupported maximum keycode 774, clipping.
                  X11 cannot support keycodes above 255.
Internal error:   Could not resolve keysym Invalid
Internal error:   Could not resolve keysym Invalid
Internal error:   Could not resolve keysym Invalid
Internal error:   Could not resolve keysym Invalid
Internal error:   Could not resolve keysym Invalid
Internal error:   Could not resolve keysym Invalid
Internal error:   Could not resolve keysym Invalid

Errors from xkbcomp are not fatal to the X server
FYI, running this code gave the below error when starting the desktop:
Code:
qxdisplay -o landscape -d ../../display/wayland-container-1
Code:
root@Debian:/# /mnt/guest/start_desktop.sh 0

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
Thank you again for your patience, and apologies for the ignorance !!
Last edited by spoofykid; 2021-05-29 at 10:37.
 

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