1. Home
  2. Support

Subcategories

  • This section is specifically useful for new contributors on the project

    7 Topics
    1 Posts
    DiogoD
    This Category is for those starting to contribute for the UBports Project and Community. By contributing, we mean doing things like: coding quality assurance (testing, bug reporting and validation, etc...) translations app development and maintenance writing and validating technical documentation and user manuals UBports social media and marqueting etc... If you want to contribute in these ways or others and have questions about it, like how to get started, where can you find information, please leave your questions in this category and we will try to answer them the best we can.

  • Discuss and solve problems with other users

    91 Topics
    646 Posts
    C
    If I try to create an container i get this after it downloaded everthing: ... I: Extracting passwd... I: Extracting perl-base... I: Extracting procps... I: Extracting sed... I: Extracting sensible-utils... I: Extracting sysvinit-utils... I: Extracting tar... I: Extracting util-linux... I: Extracting zlib1g... I: Installing core packages... W: Failure trying to run: chroot "/home/phablet/.cache/libertine-container/firefoxcontainer/rootfs" dpkg --force-depends --install /var/cache/apt/archives/libc6_2.31-0ubuntu9_arm64.deb W: See /home/phablet/.cache/libertine-container/firefoxcontainer/rootfs/debootstrap/debootstrap.log for details (possibly the package /var/cache/apt/archives/libc6_2.31-0ubuntu9_arm64.deb is at fault) ChrootContainer.py:94: ERROR: create_libertine_container(): Failed to create container libertine-container-manager:126: ERROR: create(): Failed to create container: 'destroy_libertine_container() missing 1 required positional argument: 'force'' It can be reproduced by just simply creating a new container with the Terminal or with the System Settings.

  • 133 Topics
    935 Posts
    K
    @hankschwie hi mate, so at long last the latest update has sorted the reboot problem - this is version 280 of Ubuntu 24.04 as of 26/06/2025. I don't know about Fairfax phones but have a Gigaset GS5 which I used the Vollaphone 22 with new screen install. Phone works, Ubuntu works, and now Waydroid is back..... These folks are truly amazing
Log in to post
Load new posts
  • N

    MultiROM Installation Fails

    Moved oneplus one multirom
    2
    0 Votes
    2 Posts
    4k Views
    C
    Hello. I tried installing Ubuntu Touch with MultiROM and TWRP recovery without kexec-hardboot support enable, with the no kexec-workaround enable in the Recovery options, which resulted in a hard brick. I just want to warm people not to do this. CM12.1, CM13.1 and CM14 do not have the corresponding adapted kernel with kexec support, so don't use them as main ROM if you plan to install Ubuntu Touch, because the workaround available in the recovery will just cause a hard brick. Beside that, following the steps in this video with the exact same version of software should get Ubuntu installed with MultiROM without any headache https://www.youtube.com/watch?v=Cg0INhBx4tY
  • X

    Nexus 5 wireless and internet problems

    Moved nexus 5
    4
    1 Votes
    4 Posts
    2k Views
    T
    I just installed stable today and wireless working perfectly for me so far (D821e). Not tried yet with my SIM in as waiting for a new screen for this damaged nexus 5 before swapping over from a nexus 4.
  • C

    Installation Trouble

    Moved oneplus one
    6
    0 Votes
    6 Posts
    4k Views
    P
    @yug said: Thanks again. Still not working for me. It says it's booting recovery, and boots to the OnePlus screen. I also let it sit for over an hour just to try, and when I reboot (hold down the power key) it boots to a OnePlus screen (presumably trying to reboot recovery again) and hangs. I let that sit for over an hour and reboot (hold the power key again) and it boots to Android. I am not sure how it worked for you without booting into Ubuntu recovery to install. I understand it did work, just not sure how it's possible. Edit: This is resolved for me. I reinstalled twrp and formatted my internal storage aka sd. Once done, installation succeeded without issue. I tried it. erase all, and it's work