home.social

#ubuntu-proot — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ubuntu-proot, aggregated by home.social.

fetched live
  1. Installing Google Chrome to Ubuntu proot environment with Termux

    Google recently started rolling out the ARM64 version of Google Chrome for Linux machines. This gives a chance for users to install this browser straight from the official Google Chrome homepage, which coincides with the same installation method for regular 64-bit computers.

    You can download the browser from here.

    We have tested Google Chrome ARM64 on a Ubuntu proot distro with Termux on Android 16, and the browser worked with full Google account synchronization enabled. To install Google Chrome, let’s assume that you’ve set up Termux on your phone with Ubuntu proot distro and VNC server installed.

    After that, follow these steps:

    1. Open the terminal, assuming that you’ve signed in as root.
    2. Execute the below command to download Google Chrome’s package. Let’s assume that wget was installed in the Termux environment outside proot-distro.
     # wget https://dl.google.com/linux/direct/google-chrome-stable_current_arm64.deb  --2026-08-03 16:21:55--  dl.google.com/linux/direct/goo  Resolving dl.google.com (dl.google.com)... 2a00:1450:400d:802::200e, 142.250.27.136, 142.250.27.190, ...  Connecting to dl.google.com (dl.google.com)|2a00:1450:400d:802::200e|:443... connected.  HTTP request sent, awaiting response... 200 OK  Length: 132151632 (126M) [application/x-debian-package]  Saving to: ?google-chrome-stable_current_arm64.deb?   google-chrome-stable 100%[=====================>] 126.03M   905KB/s    in 2m 34s      2026-08-03 16:24:30 (838 KB/s) - ?google-chrome-stable_current_arm64.deb? saved [132151632/132151632] 
    1. Use apt to install the package you’ve just downloaded. This ensures that dependencies will automatically be satisfied. A successful installation looks like this:
     # apt install ./google-chrome-stable_current_arm64.deb  Note, selecting 'google-chrome-stable' instead of './google-chrome-stable_current_arm64.deb'  Installing:                     google-chrome-stable                                                                                       Installing dependencies:    wget                                                                                       Summary:    Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 37    Download size: 344 kB / 132 MB    Space needed: 446 MB / 26.8 GB available   Continue? [Y/n]   Get:1 /root/google-chrome-stable_current_arm64.deb google-chrome-stable arm64 151.0.7922.71-1 [132 MB]  Get:2 ports.ubuntu.com/ubuntu-ports resolute-updates/main arm64 wget arm64 1.25.0-2ubuntu4.3 [344 kB]  Fetched 344 kB in 4s (96.3 kB/s)                                      Selecting previously unselected package wget.  (Reading database ... 78043 files and directories currently installed.)  Preparing to unpack .../wget_1.25.0-2ubuntu4.3_arm64.deb ...  Unpacking wget (1.25.0-2ubuntu4.3) ...  Selecting previously unselected package google-chrome-stable.  Preparing to unpack .../google-chrome-stable_current_arm64.deb ...  Unpacking google-chrome-stable (151.0.7922.71-1) ...  Setting up wget (1.25.0-2ubuntu4.3) ...  Setting up google-chrome-stable (151.0.7922.71-1) ...  update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/x-www-browser (x-www-browser) in auto mode  update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/gnome-www-browser (gnome-www-browser) in auto mode  update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/google-chrome (google-chrome) in auto mode  Processing triggers for man-db (2.13.1-1build1) ... 
    1. Run Google Chrome using google-chrome. It’s recommended to sign in to your Linux account before launching the browser, as running it from root isn’t secure.

    If everything worked, Google Chrome should run like this:

    Signing in even works.

    #Android #google #googleChrome #news #oneUi #Samsung #smartphone #Tech #Technology #Termux #Ubuntu #ubuntuProot #update
  2. Installing .NET 10.0 on Ubuntu proot-distro with Termux on Android

    .NET 10.0 is a new version of the modern .NET framework that brings several improvements across different areas of the software development kit, including runtime improvements (JIT inlining improvements, method devirtualization, and so on), new APIs in .NET libraries (new JSON deserialization options, post-quantum cryptography support, and so on), and many more improvements.

    Normally, any .NET applications that are built for a specific platform can be run normally, such as Android applications made with MAUI. However, what if you’ve planned to run a CLI .NET application on Android? Or an application for computers? Termux can provide you with a solution.

    Recent improvements to Termux involved changing how proot-distro downloads the distribution containers so that it utilizes Docker Hub to download the necessary assets and configure them to be usable. Follow the below steps to install .NET 10.0 with Ubuntu proot-distro.

    1. Install Termux from F-Droid.
      • For Samsung devices, you might want to turn off the Auto Blocker feature so that you can install it. You can also use the Play Store version, but we haven’t tested it yet, and your mileage may vary.
    2. Open Termux, and let it configure itself. After that, upgrade all packages using pkg upgrade.
      • If you’re prompted to choose whether to keep your own changes or to install the package-supplied version, just press ENTER on your phone’s keyboard.
    3. Once all necessary upgrades are complete, you can now install the proot-distro program using pkg install proot-distro.
    4. Afterwards, install the Ubuntu 26.04 Docker container with proot-distro install ubuntu:26.04.
      • It might take a while, depending on your internet connection.
    5. Now, you can login to the container with proot-distro login ubuntu.
    6. Before installing any packages in the Ubuntu proot environment, you’ll have to check to see if there are any package updates with apt update.
      • If there are any, run apt dist-upgrade to upgrade all packages.
    7. Install .NET SDK 10.0 or .NET Runtime 10.0, depending on your use case.
      • If you want to build .NET applications, install the SDK using apt install dotnet-sdk-10.0.
      • If you want to just run .NET applications, install the runtime using apt install dotnet-runtime-10.0.
    8. If you’ve installed the SDK, verify that the application actually builds.
      • Create a new directory, such as test (mkdir test), and change the current directory to it (cd test)
      • Create a new .NET console project with dotnet new console --use-program-main.
      • Verify that it actually builds using dotnet run.

    However, as of now, you may be running into an issue where the building stage of any application may fail with error messages that are similar to this:

     GC heap initialization failed with error 0x8007000E  Failed to create CoreCLR, HRESULT: 0x8007000E 

    In this case, you’ll have to add an environment variable that changes the GC heap hard limit value to an acceptable value so that you can build and run applications on Android devices. In order to do this temporarily, append the environment variable before the command, such as this:

     $ DOTNET_GCHeapHardLimit=1C0000000 dotnet build 

    If this works, you can add a line that exports this environment variable to your ~/.profile like this:

     $ echo "DOTNET_GCHeapHardLimit=1C0000000" >> ~/.profile  $ . ~/.profile 

    Once done, exit and re-enter your proot environment, and you should be able to build and run .NET applications.

    #NET #2604 #2604LTS #Android #C #csharp #dotnet #news #oneUi #Proot #ProotDistro #Samsung #smartphone #Tech #Technology #Termux #Ubuntu #Ubuntu2604 #Ubuntu2604LTS #Ubuntu2604LTSResolute #Ubuntu2604LTSResoluteRaccoon #Ubuntu2604Resolute #Ubuntu2604ResoluteRaccoon #ubuntuProot #update