Re: XWayland Victory!
 

Re: XWayland Victory!
 

lol...!
unbelievable....

Re: XWayland Victory!
 

Has anyone had any luck with any other distros that are up to date enough to work?

Re: XWayland Victory!
 

allmost anything goes, but most will require VNC for GUI I bootstrapped Kali in chroot. Terminal works, but VNC for X (noVNC works on-device with browser)

Re: XWayland Victory!
 

How does sound work using VNC?

Re: XWayland Victory!
 

Booooo! I had just finished making a custom rootfs to share with everyone. I was just waiting until later this evening when I'd have a reasonably fast connection in order to upload it. I was hoping to release it along with some management scripts this evening.

Oh well, I guess I'll just use Arch instead. I wasn't really taking advantage of Manjaroishness anyway. For this use, Arch should be mostly indistinguishable. It will take a day or two for me to migrate, and then I'll share a preconfigured Arch rootfs instead.

I've also been working on some Sailfish GUI utilities for installation, configuration, and 1-click launch of chroot with xfce desktop as nemo user. I'm new to QT Quick, so this may take a little while, but it's coming along nicely.

Re: XWayland Victory!
 

It shouldn't matter as long as you can get the chroot to interact directly with the pulse server. The display is independent from audio. Whether you're using xwayland, xserver-xsdl, or vnc shouldn't make any difference for sound.

Re: XWayland Victory!
 

Also, you should be able to use the xwayland window from manjaro when chrooting other distros that dont have fresh kwin-wayland. Just chroot into manjaro, start kwin-wayland --xwayland, and run "xhost +". Then chroot into the other distro, export DISPLAY=:0, and you're ready to rock.

Re: XWayland Victory!
 

Thanks for the info. I still can't get the the Archlinux (i686 version) to work on Jolla tablet. I'm trying a few more things before I report. One thing I just noticed (perhaps a "my bad" is needed here!) is that there is a README file with the archlinux. Should the instructions found there be used in lieu of what is posted in this thread. They seem quite a bit different.

Re: XWayland Victory!
 

Wow, nice!
Really looking forward to that. If you have got no icon for this… I've just mashed something together using the xfce colour scheme, feel free to use or ignore (the eyes are a bit ugly, but I didn't want to change the logo too much): http://imgur.com/a/Y28aM (I can send you the svg as well, if you'd like it.)

edit: PM me for svg or if you want something changed, I don't want to derail this thread. ;)

Re: XWayland Victory!
 

I'm not sure. I had a similar problem when I tried this on my friend's nexus 5 (running 2.0.1.11, I think). The teminal output looked good, but no xwayland window. I'm running running 2.0.5.6. Maybe it's an issue with the wayland version?

I don't really know anything about the jolla tablet. What version of SFOS are you running? If you have 64 bit kernel, you might want to try amd64 rootfs.

Where can I find the README file you mentioned?

Re: XWayland Victory!
 

The README file is in the archlinux rootfs version here

http://talk.maemo.org/showpost.php?p...3&postcount=40


Jolla tablet does not use arm. Most specs are here.

http://www.gsmarena.com/jolla_tablet-6816.php

It is x86_64 i486

Similar to what you say everything looks fine until I get to the kwin_wayland command. No window appears.

I will play some more but suggestions are welcome!

Re: XWayland Victory!
 

Just wondering if you don't mind sharing the work you did on the Manjoro version. Would be fun to try until the Archlinux version is ready. Regardless, thanks for your efforts as having this capability really makes Sailfish unique. It's clearly a much better user experience than trying to chroot an Android phone.

Re: XWayland Victory!
 

amd64? really? on arm processor? what a story :)

Re: XWayland Victory!
 

The tablet uses an Intel Atom CPU.

Re: XWayland Victory!
 

I would, but my net access is very limited. The next time I have a fast connection, I might, if I don't have Archlinux ready yet. The file is about 800MB, and I only get about 80kbps upload right now, so it would take too long (about 20 hours) and therefore likely be interrupted.

I might have a chance later today. Any suggestions on where to share the file? I'd prefer not to use Mega, or something like that, because it would be nice to be able to download it with curl in an install script.

Re: XWayland Victory!
 

Oh, i thought it was about Nexus 5.

Re: XWayland Victory!
 

Since this seems to be all open source, you could check if you can get away with creating a github repository containing scripts to create the file and hosting the resulting file as a release: https://help.github.com/articles/dis...arge-binaries/
Good luck!

Re: XWayland Victory!
 

You can find some helper scripts here:
https://github.com/Preflex/easy-chroot

ManChroot.sh will give you a root shell inside the chroot.
DeskChroot.sh will launch a XFCE4 session.

You may notice errors about mount points in /home/nemo not being found. If you would like to share these directories with the chroot, create those directories inside the chroot.

You can find the preconfigured Manjaro rootfs here: https://github.com/Preflex/easy-chroot/releases

To use with the helper scripts, unpack it in /opt/easychroot/Manjaro

This rootfs contains helper scripts in /usr/share/easychroot/scripts/
The start_xwayland.sh contains hardcoded values for my Nexus 4's screen. If you are using a different device, you will need to edit the last line of this script, substituting the height and width values for your device.

Re: XWayland Victory!
 

Hi. Just wanted to say that it started up on my Jolla 1! XFCE4 is an especially good choice for my screen size (540x960). While lots of warnings quite glad to get it up and running for now. Thanks again!

Re: XWayland Victory!
 

@preflex thanks a lot!
Is there a way to close all the stuff gracefully? Meaning, I ran DeskChroot.sh and now want to close all XFCE etc sessions and restore the pre-start_xwayland status?

Does anyone else have the issue that the airplane mode is "shown" after running manjaro? I guess its not really going into airplane mode, as mobile internet is still working, but the symbol is shown.

Edit: i also noticed that the phone doesn't reboot properly (get's stuck and needs 10-sec power-off button press) to start normally after running DeskChroot.sh

Re: XWayland Victory!
 

Before you exit out of the chroot, from terminal do a ps to see what is running. Kill all the processes related to wayland and such. I just did that and turned phone off and on with no problem. Also everything was unmounted. Would be nice to have scripts to automate this and unmount file system to make it a nice clean process. Can try later when I have some time.

EDIT: Actually, if you do a shutdown from the desktop everything is unmounted. Then just kill kwin/wayland related processes from terminal.

Re: XWayland Victory!
 

After testing your rootfs more thoroughly, I noticed that neither firefox nor chromium can access the internet. Chromium gives the error "err_internet_disconnected".

However, pacman and others can access the internet.

Is it possible that chromium/firefox rely e.g on networkmanager/connman do detect the availability of internet?

P.S.: I'm using the rootfs from a sdcard and already noticed that some problems that I encountered are related to that. However, I guess that I solved most of them by remounting the sdcard using "mount -o remount,suid,exec,dev .... " before calling DeskChroot.

Re: XWayland Victory!
 

Hi. Chromium seems to work fine on my Jolla 1 phone. I think the main problems using Jolla phone is that the screen is a bit small for this (indeed, I've been pecking away on the keyboard with a stylus...) and the ram (only 1 GB) makes it a bit slow and possibly unstable (freezes at times).

Re: XWayland Victory!
 

Been playing with the tablet a bit. Still can't get kwin to work. It is possible there is an error with the wayland software. This is the error I get.

[destroyed object] error 0; invalid format 0x34325258
Disabling glamor and dri3, EGL set up failed

I found this recent bug report

https://bugs.freedesktop.org/show_bug.cgi?id=99791

Perhaps the same as problem I'm having. I'm not sure cause all this is above my pay grade...

Not sure what to try at this point. Maybe earlier version of software or VNC. Anyone have success using VNC? If so perhaps some instructions would be helpful. Thanks!

Yippee! There was an update that fixed this bug! Xwayland now working for Archlinux on the Jolla Tablet. Amazing! I now have Sailfish, Android apps and Archlinux at my immediate disposal on a tablet that Jolla couldn't deliver, that a Chinese friend bought from Taobao and delivered to me for $200! Unbelievable! I've gotten half the refund. There is still a chance for the remaining half! The story goes on... Sorry about rambling on and on... One more thing. I love Jolla!

Re: XWayland Victory!
 

i want to give a try to it. what base image do you suggest? i prefer debian based but i do not have problem with others. i want it to be fast and without problems. can you suggest me any base system.

i have nexus 5. oh and is there a way to cast screen to tv/ monitor without slimport cable?

i tried vnc but did not get it to work. i'll try to get it to work as soon as i get home.

Re: XWayland Victory!
 

Since you are using Nexus 5, I would suggest you try the Manjaro version just to get started and see it work. Then move on as Manjaro will not have support in the near future.

http://talk.maemo.org/showpost.php?p...&postcount=139

Re: XWayland Victory!
 

Great work there. Tested now and it worked on my Nexus 5 too. Running 2.0.4.13 SFOS. But i get an errors when starting some apps inside manjaro. Chromium does not start too.

UPDATE.
nevermind got it fixed.
if anyone needs you must run this command to fix permissions and run chromium
sudo chmod 1777 /dev/shm

You had little error in usr/share/easychroot/scripts/start_desktop.sh

was !#/bin/bash must be #!/bin/bash

Re: XWayland Victory!
 

Excellent! Is there a release image of 2.0.4.13, or do you have to OTA from 2.0.1.11? Asking for a friend.

Also, for users with high dpi screens, you may want to bump up the DPI if UI elements are too small.
The easiest way do this, open "KDE System Settings" (command: systemsettings5), open the "Fonts" panel, and enter a higher value for the DPI. It might help to do this as root as well, since kwin runs as root. I already bumped it up to 128 from the default of 96 in my preconfigured image, but on your 1080x1920 screen you might want more.

Whoops! I'll be sure to fix those in the near future, once I have Archlinux working (kwin is just crashing on me). Thanks for the feedback! I should have the necessary bandwidth and time to work on it tonight or tomorrow. For now, you can just add "chmod 1777 /dev/shm" to one of the scripts. start_xwayland.sh seems like a good choice for that.

Re: XWayland Victory!
 

Hi, If you haven't updated lately you might try to (-Syu option as you know of course!). There were some programs that began with mesa that had a bug. The update fixed my problem with kwin not working.

Btw, I had never used Archlinux before. pacman is pretty nice.

Re: XWayland Victory!
 

Yes, I suspect it was just some silly bug that would get fixed by an update. I hope it works out.

Also, pacman is pretty awesome. "pacman -Syu chromium" is like doing "apt-get update", "apt-get dist-upgrade", and "apt-get install chromium" all in one step. It is astonishingly powerful. See https://wiki.archlinux.org/index.php/pacman for all the options. (Note: documentation on Archwiki is excellent. It's so good, I frequently consult it when dealing with other distros just because it tends to get into all the gritty details.)

Hopefully I can get yaourt working, because the AUR is where Archlinux really shines. It's like having all of Ubuntu's PPAs rolled into one and injected with steroids. The ease of installing unofficial or non-redistributable packages (like ffmpeg-full-nvenc) was the reason I switched from debianish distros.

off-topic:
On the desktop, Manjaro is really nice as well. It's kind of like the LinuxMint of Archlinux. All the power of Arch, but easy to install and set up. They have a really polished KDE build with a few extra kcm modules for managing kernel, video drivers, and systemd. It's really a shame Manjaro-ARM is shutting down. It's my favorite distro for raspberrypi.

Re: XWayland Victory!
 

Archlinux update fixes xwayland crash, but caused new and interesting problems which I don't yet understand well enough to ask good questions about. I suppose that's the downside of targeting rolling releases,

In the "good news" dept, I've made my scripts more generic. deskchroot.sh now requires some arguments: height, width, and session_start_command (startxfce4, startlxde, plasmashell, etc). This is a prerequisite for my upcoming convenient management app (not even pre-alpha yet. ETA 2 weeks, maybe more. Maybe lots more. ).

There will be a substantial update to my git repo tomorrow, hopefully including a new Arch-based release image, as well as scripts to generate your own (so you don't have to trust me, and so i can actually be in compliance with github's rules. :) ). I also plan to include a filesystem overlay which includes the comtents of /home/nemo, /root, and /usr/share/easychroot, so you can easily adapt my hacks to whatever distro you please.

One I release my preconfigured arch-based rootfs, I will cease answering questions about manjaro-arm and ask that you migrate. Due to the limited storage space on my Nexus 4, I can only quasi-officially support one guest distro at a time (unless y'all want to send me more hardware). I may need to switch distros again in the future, if library drift breaks things.

I ain't seen qole around in a while. I used the "easychroot" name because I was obviously attempting to re-implement his fantastic work on a broader scale, and wanted to give tribute. Since I'm not qole, and I'm targeting a much broader set of guest distros and host devices, I propose the name "VersaChroot". Your thoughts?

Re: XWayland Victory!
 

How about NotSoEasyChroot. lol Just kidding...

Re: XWayland Victory!
 

Transition to ArchLinux complete!

New rootfs is here: https://github.com/Preflex/easy-chro...ases/tag/0.0.2

New launch scripts are here: https://github.com/Preflex/easy-chroot

DeskChroot.sh now requires arguments, height, width, and command.
Example: "# sh DeskChroot.sh 1280 768 startxfce4"
LXDE and Plasma are also installed. To use them instead, use "startlxde" or "plasmashell" as command.

Filesystem overlay and scripts to build your own rootfs later, due to low battery (5%). Maybe later tonight. Probably tomorrow.

Have fun!

Re: XWayland Victory!
 

Great. Deleted Manjaro and put Arch in it's place. No problems at all. Nice to see minor fixes and lxde bundle :) Thank you for your hard work. I have questions:

1 Can we have terminal inside the arch linux?
2 Can we rotate the screen? (I could not)
3 Can we turn of arch linux gracefully?

I turn of arch with killing process. I find process pid with command 'ps -ef | grep xw' and kill it with "kill -9 'PID'"

This does something to SFOS it goes on airplane mode even if button is not acitated. I just restart to fix this.

Re: XWayland Victory!
 

Would it be possible to automatically determine the device screen resolution? (I know that this can be done in QML, but don't know if there's a command-line method that works with Wayland.)

Re: XWayland Victory!
 

1. Yes. It usually works for me. Sometimes it doesn't. When it doesn't, I don't know why.

2. No. In the research I've done, it seems the inability to rotate is a feature, not a bug. This was seemingly done to prevent applications from changing the screen resolution, and any bugs related to it are marked WONTFIX. :( xRandR has read-only access to the xwayland server. It can get display info, but can't actually Resize-and-Rotate.

3. I dunno. Your suggestion looks good to me. Usually, I just reboot or just close the window and terminal session, but leave everything mounted. I'll be looking into this, but it's pretty far down on my to-do list.

The airplane mode stuff is weird. It claims to be in airplane mode, but networking still works for me. This is likely a side-effect of impersonating the nemo user and setting XDG_RUNTIME_DIR=/run/user/100000, which seems to be needed to make pulseaudio work.
You could create /run/user/100010 and use that instead. It should interfere with SFOS less, but probably no audio.

Re: XWayland Victory!
 

"cat /sys/class/graphics/fb0/modes" seems to give useful output, but may be problematic on other devices if multiple modes are available. On my system /sys/class/graphics/fb0/mode was just an empty file.

Re: XWayland Victory!
 

could you check again there are two files. one named 'mode' and second 'modes' first file is empty for me but second has resolution in it. i was looking for this info thanks for help. i'll make changes to script to select resolution automatically.