@dimwitflathead isn't impish long out of support?

@kristatos If that is the case, I am afraid they will be sorely disappointed...

@Salah "should" as in, you hope it will be, or "should" as in, you have tested it on 24.04 and confirmed that it works?

@liam I am afraid that even if you could add a new user to your device, it would not work. At the moment UT is not yet ready to be used in a multi-user state. Too many parts of the OS still assume that phablet is the current and only user.

Before going into the issue you are posting about, could you tell us what you are trying to achieve? Do you want to make your UT device multi user? Are you trying to change the password of the phablet user? Please let us know what your goal is, so we can avoid an X Y situation.

@ubuntoutou said in Failed fresh install:

All internet pages were said to be insecure with a broken red padlock. So I tried to reinstall the system with the UBports graphic installer.

A reinstall would not have solved that issue. It is due to Xenial being unsupported and no longer receiving any root certificate updates.

@liam As @MrT10001 says, for automount the drive has to be formatted to FAT32, at the moment.

EXT4 can also be read, but it would need to be mounted manually.

@nonobike To cut a long story short, there is no supported solution to solve the apt error message. The message about not being able to 'remove' the rights of the non-existent _apt user is not a fatal error.

You say you mostly use the CLI. And it is your phone and your installation, so you are free to do as you please with it, but UT is not set up to be updated via apt. Neither is there any need to do so. Updates get pulled in via the system settings. (There is also a way to do that via the CLI, but I never use that, so I am not sure about the syntax. Futhermore it takes more effort to use the CLI than to just open the Settings app and tapping on Update)

The rootfs is read-only for stability and a robust atomic updating system (the updates are either applied in full, or not at all). This stops the user from experiencing breakage due to a partially applied update.

If you want to install apps from the Ubuntu repo's on your device, you are encouraged to read up on Libertine containers. That technology was created especially for that purpose.

If the app or tool you are looking to install is also available as a snap you can try enabling snap support on your device with the Snapz0r app, if you are on Focal.

@Vulpex Sure, because restarting Lomiri would clear up a lot of stuff, no true reboot would be needed most of the time.

@odo According those who would know, UT has the best battery life of the different mobile linux's on the same device.

@kristatos Has an issue already been opened for this bug?

@Vulpex said in Slow reboots:

just checked, reboot of the os is instantly and does not reboot to boot loader but into theos and greats you with your lock screen (no pin required)

This means your device is not rebooting. Rather the Lomiri shell crashes and restarts.

A proper reboot would show the bootloader unlocked screen.

@linux_dude said in apt fails to install package duo to the lack of space and "read-only filesystem":

@arubislander why though?

Because UT aims to be Mobile Linux for Human Beings.

I've tested some CLI and GUI apps from apt and they worked just I expected (aside from scaling),

In that case, these apps would also run in a Libertine container. Please look into that option.

it wouldn't be much to shrink /userdata 10-20 GiB and expand the / partition with it.
How easy is it to do that? Because they seem to be configured and partitioned in an awkward way (to me).

Maybe. I don't know. I know that existing android partitions are reused and repurposed. I am not sure if any additional partitions are made, or that these are all vendor determined. (maybe the layout needs to be just so, so that "vendor blobs" function?). Anyhow, the way things are laid out differs from device to device, and is determined in large part by the porter of the device.

Can you help me with it?

I am no expert in this area. So I cannot help you with resizing partitions. The only device I have successfully fiddled with the partitions on was the Meizu Pro 5. Since then I have found that respecting the philosophy of the OS, and finding ways to do what I need within those confines, works better in the long run.

@linux_dude said in apt fails to install package duo to the lack of space and "read-only filesystem":

I can see that '/' is full, what why would this happen on a fresh installation of UT?

The adage: "Nothing in life is easy. But if it is too hard, you are probably doing it wrong." comes to mind here.

You are trying to use apt (to install / update) on UT. UT is set up as an immutable distro. As such the root filesystem is read-only and updates are provided as delta's to the previously expected state of the system. Because of this, it is not necessary for there to be much free space in the / partition, which is read-only anyway. In consequence apt is not supported, neither is making the / partition read/write.

Packages that are installed from the Open Store are installed in /userdata, which as you can see does have ample free space. You could tweak apt to install to the writeable area too. One such initiative is Crackle. Search for that in the forums for more info. It doesn't make everything work as yet, but you might want to contribute to the effort.

Another option, depending on what it is you need to install, is to create a Libertine container (also search for that).

Be advised that as a rule, services do not run in a Libertine container, but can be made to work with Crackle.

An up and coming option is to run snaps. On 20.04 they have to be enabled with the Snapz0r app from the Open Store, which also requires certain features to be available in your devices kernel.

Current limitations with snaps are: Not all GUI apps work, and of those that do, there is no native OSK support.

@gandalf Not sure about any answer to your questions, but I would suggest you research if what you want is possible on Ubuntu Desktop with NetworManager. If it is, then teh same setup should be transferable to Ubuntu Touch, as the VPN technology used is the same.

@MrT10001 Not sure this is the same issue as the OP. They are stalled scanning for the device on ADB. Network connectivity does not come into play there.

@Salah said in Problem with Installer 0.10.0:

Could you please address if this is a server issue or something

This is definitely not a server issue. ADB scans for locally USB connected devices.

In addition to what others have said, when the installer is stuck in this state, double check that your mobile device is indeed in Recovery mode. If it isn't (or if it is, but it is not being recognized) unplug it, and reboot to recovery using the appropriate key combinations and replug it.

Also, you don't mention if you ticked both check boxes in the installer.

Also also, when your device does come up in recovery, is it the UBports recovery or something else that shows up?

@Salah Are you also using the same OS you did a month ago?

This is not the place to discuss the pro's or cons for making it possible to change the devices IMEI.

I think all that can be said about it in context of UT has been said. Therefore I will lock this thread.

@moodroid Best to ask the writer of that post what they had in mind?