Feedback for the Seabass



  • Thank you for your thoughts on the Icon!

    @Giiba said in Feedback for the Seabass:

    A tangential though related feature request would be two things

    Thank you! Content Hub for the Seabass is definitely on my todo. It'll take a few releases before Content Hub is implemented though:

    • v0.5 release will feature building packages with Clickable
    • v0.6 will probably contain ability to delete files (seems to be the only blocker left before Content Hub integration)
    • and then v0.7 will probably contain Content Hub integration.

    Well, at least this is what I think for now 🙂



  • @mikhael Hi,
    I agree with @arubislander for the difference between the favorites menu in the file explorer app and the files menu in Seabass.
    In the file explorer the menu is used as a bookmark menu to access favorites more quickly, while in Seabass it is used to choose a file and navigate directories. Probably after the first use it will be easy to understand what the icon does, but if you opened the app for the first time it isn't very clear.
    I would also prefer the icon to be separate from a settings menu, because it is one of the most frequently used ones.



  • v0.5 is up and it has support for building projects using Clickable.

    The feature is very experimental and somewhat limited for now and (although I've tested it as much as I could) there should be bugs. To build a project you need to open a corresponding clickable.json file and click the "Build" button:
    Build

    When starting a build process for the first time a new chroot Libertine container with ID seabass2-build will be created.
    So the first thing required to build packages with the Seabass for now is... patience :-D.
    Because creating a chroot container might take a while. About 30min was usually enough for my Xperia X during testing, but the experience for sure may vary depending on your device and Internet connection. The app should also be active (not sleeping) while the container is being created. The good thing is that you only need to create container once.

    If for some reason the container creation failed, Seabass will try to delete the container, so that the next time you run Build it could try to create container once again.
    And if for some reason the deletion wasn't successful, libertine-container-manager is here to help: libertine-container-manager destroy -i seabass2-build. You could also use this command if anything goes wrong with the container 🙂

    There are also a few limitations:

    • Project files should be located inside ~/Downloads or ~/Documents directories. Not really a strict requirement, just these directories are automatically mounted to Libertine containers. Alternatively you could create additional bind mounts using libertine-container-manager or maybe even System Settings application.
    • clickable.json file should be named 'clickable.json'. Because the "Build" button is only visible for "clickable.json" files.

    QML, HTML, C++ and Python clickable templates are supported for the first release (Go and Rust require additional packages that are not installed in seabass2-build by default). By "supported" I mean I've tested building "HelloWorld" applications using these templates 🙂

    Please let me know if there are missing packages in the container required to build your favorite application!
    Your feedback is very appreciated!



  • 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



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



  • @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?



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



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



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



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



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



  • 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


Log in to reply