Feedback for the Seabass

mikhael

A few notes on v0.5.0:

Container creation fails constantly for me because of mismatching package versions in the xenial repos.
How to fix: update to v0.5.1
Seabass can't delete the container in case of initialization errors
How to fix: delete the container manually using System Settings app
And in case you've managed to create a container, desktop applications from the seabass2-build container are visible in the app grid.
How to fix: libertine-container-manager exec -i seabass2-build -c "bash -c 'rm /usr/share/applications/*.desktop'"

The issues should be fixed in v0.5.1

danqo6

@mikhael I am getting crash on oneplus 3t edge channel during start.

mikhael

@danqo6 thank you! I can reproduce the issue on Pocophone with GSI. For me the same happens when trying to run other apps that use qmlscene from terminal (I tried it with uNav). But running the applications from the app grid works fine.

Just a guess, but maybe the app grid provides environment variables, that are required but missing when trying to run qmlscene from terminal?

mikhael

@danqo6 does the app works for you when running from the app grid?

danqo6

No, just crashes, not sure how to get log when running from appgrid

mikhael

@danqo6 logviewer from the open store should work for getting logs

Giiba

I am pretty sure that launching apps from the terminal is not a supported feature of UT. Some sort of permissions thing (appArmour) blocks the execution of graphical applications.

Crashing from the grid is a different issue. Try going into

~/.config/
and
~/.local/share/

and delete the seabass folders, then try launching the app from the drawer.

kugiigi

You can run apps via terminal using ubuntu-app-launch. Other than that, it might and or not work.

danqo6

I found the issue, it is this https://github.com/ubports/qtwebengine-opensource-src-packaging/issues/37, I do not have that fix because Oneplus 3 uses gst-droid branch of lxc-android-config

mikhael

Hi everyone!

It's almost Christmas time, New Year is coming, and it means holidays and maybe some spare time for developers to create new awesome apps for UBports... and that's where the Seabass might come in handy

The next release is going to provide an ability to create new apps for UBports from within the Seabass. Hopefully that means building apps right on your phone/tablet more easily.

So if you happen to have a use case for a mobile/convergent dev environment to build UBports apps and you have a device that supports Libertine, I'd be grateful for your suggestions and feedback!

For now there is a beta version available for testing.
It has a new menu entry called "New project..." in the file list:

It leads to the project settings page:

New Project page

Here you can specify all the options supported by Clickable and create a new app.

There are a few limitations for now:

Libertine support is required
Creating a Libertine container (during the first run of clickable) might take a while
Seabass now uses a pre-release version of clickable that might have a few breaking changes
it's only possible to create new projects inside ~/Documents and ~/Downloads directories (and any nested directories)

Click package is available on Github: v1.0.0-beta-1

kugiigi

@mikhael This is looking great! Thank you for putting an effort on this.
I however have problems with the libertine support on my Nexus 5. First of all, it takes like 6 hours creating a container, most likely my connection's fault. And then I get some errors around the part when clickable is being installed. I wasn't able to record the errors though, sorry. Perhaps you can consider other options for the container such as the on used the now unmaintained app OnTheRoad. This one has a compressed prebuilt container so container creation is really fast. I have no idea how complicated to this though
Anyway, I might try creating a libertine container again and see if it'll work.

mikhael

@kugiigi thank you for the feedback!

This one has a compressed prebuilt container so container creation is really fast.

Thank you! I'm thinking about such option because creating a container from scratch seems too unstable and requires too much time even on snapdragon 845. I'd better not imagine how long it would take for example on BQ e4.5

And I like the way OnTheRoad solves the problem.

And then I get some errors around the part when clickable is being installed

Hm, I think it might had been broken for some time. v0.11.2 (currently in the store) should've solved container creation issues by upgrading python to v3.6.

kugiigi

@mikhael Oh wow, which UT device has 845?
I'll be installing the beta version and try creating a container again and let you know

mikhael

@kugiigi thank you! It's Poco F1

kugiigi

@mikhael Oh, didnt know UT is already available for that phone. I though fxtec pro1 x is supposed to be the most powerful UT device

I tried creating container again and luckily, it only took less than an hour this time. Maybe the server is happy today However, I still get the error at the end. It says that clickable is not found. Then I tried manually installing clickable in the container via the settings app. After I've done that, building an app just shows a blank build output.

mikhael

@kugiigi thank you very much for trying the build!

Oh, didnt know UT is already available for that phone.

UT works pretty well on F1 aside from a few stability issues, even fingerprint sensor works

I still get the error at the end. It says that clickable is not found.

Hm, I think I need to improve logging here
If you have some time, could you please try "Update build container" button on the Settings page in Seabass? It will run a script to install the required version of "clickable"!

kugiigi

@mikhael I tried that but I get an error.

proot warning: can't chdir("/opt/click......." in the guest rootfs: No such file or directory proot info: default working directory is now "/"

mikhael

@kugiigi hm, that's ok, it's just a warning. Actual script output should follow that line. What's strange is that there is nothing else in the output...

kugiigi

@mikhael Yes, nothing else after that.

mikhael

@kugiigi said in Feedback for the Seabass:

Then I tried manually installing clickable in the container via the settings app.

Hm, I've just realized that installing clickable using apt-get probably won't work, because Seabass tries to launch clickable using python3.6 while clickable installed with apt relies on python3.5.

It should be possible to install required version with libertine-launch -i seabass2-build python3.6 -m pip install --user --upgrade git+https://gitlab.com/clickable/clickable.git@subcommands-reduced