Messages

1

Cosmo Communicator - Linux / Re: Annoying KDEWallet message on WiFi connect

« on: September 29, 2021, 01:13:24 pm »

Under the hood what this is doing is unlocking a "keyring" managed by the system and often tied to your user account. There are many interfaces, KWallet, Seahorse (Gnome version), and others, but it appears that however Plasma is configured it didn't get linked to your user login to unlock the keyring at the same time. Gnome handles this for you if you delete a keyring via Seahorse, and then it will set up a new "Login" one, which is where Chromium/NetworkManager and others usually store secrets.

2

Cosmo Communicator - Linux / Re: Finally installed Libreoffice in UB PORTS ( Ubuntu touch )

« on: September 29, 2021, 12:39:33 pm »

I'd suggest trying setting the DPI to 192 for the best results, it seems to work in most apps I've used without breaking the UI.

3

Cosmo Communicator - Linux / Re: Can't download Linux for Cosmo

« on: September 29, 2021, 12:33:14 pm »

For those that stumble here with the same issue, I've run into this issue specifically in Google Chrome. I'm not sure what is going on (bad mimetype, dodgy classification by the browser), but using another browser or copying the link (yes even in Chrome) and then using `curl -L -O https://the.planet.com/url` (or `wget -o URL`) or on Windows/Powershell `iwr URL -OutFile cosmo-linux.zip` should get it downloaded for you.

4

Cosmo Communicator - Linux / Re: Ubports for Cosmo

« on: September 29, 2021, 12:22:19 pm »

i already asked this but since i can't seems to find a working way to update the ubports once installed.
i'm stuck with the version i installed first time. if i try to re-flash a new .img the process will end succesfully but then i found the same version of ubuntu touch when i boot.
obviously OTA update is not working neither.
any suggestion?
thanks

To update if the built in OTA updates aren't working properly, boot to Gemian and download a new `flashable` build from the UBports Gitlab, and then unpack it and overwrite your `ubuntu.img` in the root of the Gemian filesystem, you shouldn't need to rewrite the `boot.img` because the filename and path hasn't changed. This shouldn't affect your data as that should be stored in the `/user-data` folder that is also mapped from the Gemian filesystem (since UBports can see those files as well).