@kalle-kruse Thanks for the link. It's an impressive post. And it was an impressive stand that they had at fosdem. Also the camera and the tablet looked really nice. But I forgot to try to play any audio or video on the tablet. Can someone comment? Is it Loud enough? Does it sound good?

Any UT@FOSDEM activity planned?

@zlamalp said in Misunderstanding about ubuntu touch on Nexus 7:

ubuntu-device-flash --server http://system-image.ubports.com touch --channel ubuntu-touch/stable --device=deb

Actually, after reading your post again I realize ... if this command works, you should be done.

@zlamalp no, that doesn't sound right. A UT installation consists normally of the following four pieces

1. boot image
2. recovery
3. system image (device independent)
4. android container

the steps you propose do nothing to get the deb android container. here are the steps I used: https://github.com/ubports/ubuntu-touch/issues/643 in Workaround.

Some more nitpicking:

• I'm not sure in which version of Ubuntu the ubuntu-device-flash tool is available. I painfully realized that at some point it wasn't available in my version (probably 18.04). This might have been resolved, but good to check
• It makes no sense to use --server one time, but not the other. Either your version of ubuntu-device-flash always goes to Ubports server by default, then you're good. Or it never goes there by default, then you always need to specify
• wrt channel - if you don't know which one you want, then you want stable

@zubozrout said in Misunderstanding about ubuntu touch on Nexus 7:

@doniks Yeah, LTE and everything else did work for me back when I was using http://system-image.tasemnice.eu/ubuntu-touch (currently dead) repository - which was based on the original Canonical images.

The last time I had my "deb" in my hands (before I gave it away) I was trying to install Ubports on it after that original repo died and I can see that I was not able to make bluetooth and camera to work but I was hacking things on top of what was available so I guess that was the issue: https://forums.ubports.com/topic/44/installing-ubuntu-on-nexus-7-2013-deb-lte

But ... even with these workarounds LTE did work for me ... it was just a matter of having a correct "boot.img" flashed AFAIK.

Not sure if you can confirm camera working as well (?).

Great! Thanks @zubozrout for the quick response and confirmation that LTE worked.

I'm 95% sure that the boot.img (kernel) on the ubports system image server is that very file that originated from tasemnice, so all that knowledge is still relevant.

Camera - good point. Another thing I barely use ... come to think of it, I might have actually not ever tried taking a picture with UT on deb. So, can't say.

Ok, let me try turning around and listing some things that I CAN remember worked: touchscreen, sound, wifi, rotation, gps, usb file transfer, libertine, desktop mode and generally everything to do with system UI and apps, app updates.

@zlamalp said in Misunderstanding about ubuntu touch on Nexus 7:

Dear @doniks,

I'm considering buying "Nexus 7 2013 cellular (deb)" and as you pointed out in many threads i found, there are problems with installation. But I'm not sure, what informations are current and how to install it on the device.

Would you be please so kind to share some sum up of "what works and what doesn't" and "how to install Utouch manually" on the device ? You seem to know about the issue a lot. Thank you.

Pavel

Hey @zlamalp , I haven't tried again lately, but I'm pretty sure the "deb situation" is still the same.

That means, the files necessary to install are on the server, however the installer somehow doesn't put them correctly onto the device. This means for installation you do need to break out the commandline and mess around. I don't think that there is a risk to permanently damage your device. At some point in between, yes you might run into a situation that it doesn't start anymore, but that is fixable.

With respect to what's not working

• installer as mentioned, and I think this includes OTA updates. So, you might have to do some commandline dance anytime you want an uptodate version.
• bluetooth doesn't work. I assume that this is fixable, but probably needs a recompiled kernel

Now, for actual cellular functionality ... I just cannot remember ... it's been so long that I haven't had a sim card for this thing. I actually assume that it works, because I think I would remember if it was broken ... but, again it's been years that I had a sim card inside. I actually wanted to reflash and try it, but I'm just not getting around to do it. I'm 95% sure it works. @zubozrout do you know?

Everything else, I'd say "just works"

With respect to continued support from ubports, that's always a tough question. Remember it's largely a volunteer run project. Resources are limited. That said, I don't see any reason why the support for deb should get worse.

Hth, doniks

@alan_g said in 2019: Time to make Unity8 great again?:

Another effect of the loss of "Mir EGL" in Mesa and the consequent switch to Wayland ls that the "Mir-on-Mir" support needed to use the Unity greeter is no longer available. Some work has been done on providing a "Mir-on-Wayland" graphics platform in Mir, but that needs significant rework (it is on my list of things I want to get to, but if you fancy taking it on get in touch).

The way I understood it is that wayland replaces mir as protocol/api. So mir stays as the implementation of the server, but it goes away as an interface. So the only mir on wayland that one would need in the future is mir-the-server on wayland. Which, is just wayland (mir's implementation of a wayland server) on wayland.

Wouldn't it then be more logical to have a greeter that is a wayland client? Or maybe the login managers from some other desktop environment could be used.

Curious what you think.

@kugiigi said in Misunderstanding about ubuntu touch on Nexus 7:

Nexus 7 2013 cellular (deb) is I think also supported but I'm not exactly sure.

Mostly yes, minus installer support

@ubuntoutou said in Package installation stuck and spinning wheel never stops under Libertine:

@doniks

Thanks doniks.

Before trying what you have suggested, I have installed the package xterm in my container. Then within this xterm I tried to locate the stuck installation process with ps although I have no idea if it should be visible from such a terminal or not.

well, I like to say ... you should see all running processes ... but then you say

But ps wouldn't run. I got a message asking me to try "mount -t proc /proc"

which surprises me ... not sure what that means

but either way, I think that's a separate problem. certainly there is no more stuck process after a reboot. so ps wouldn't help anyway.

which I did only to be told that the "-t" option could only be run as root. But I was refused to use both sudo and su.

well, not being able to su and sudo is normal. remember the whole container is created by phablet user, all files inside are owned by phablet

So I tried your solution. However there was no .json nor any .xml file within any directory. The command
# find / -iname "libertine" -print | egrep 'json|xml'
did not yield any result.

mhm, maybe it's called something else, and maybe it isn't even json or xml format, but it definitely is some human readable text file, just use cd and ls starting from /home/phablet/ and then one of .cache, .config, .local

I searched for a root ~/.cache/libertine-container/CONTAINER-IDENTIFIER/rootfs/ directory but couldn't find any.

you know you have to replace "CONTAINER-IDENTIFIER" with the identifier of your container, right?! show ls -l ~/.cache/libertine-container/

In fact, there is no .cache directory under ~root nor even under "/".

I don't know what ~root refers to. I am only talking about files and folders underneath /home/phablet

There is a "cache" directory (with no dot) under "/" but it has nothing relevant inside.

yeah that is unrelated

However I did find the container directory ~phablet/.local/share/libertine-container/user-data/xenial. So I deleted this entire directory.

ok. that was the home directory inside the container. one of the three things I think you should get rid of. good. now lets find the other two: config file and the root folder

Then I rebooted the device and when the Ubuntu logo appeared and I swiped sideways, no on-screen keyboard appeared to enter my pass code! I had to connect a mechanical keyboard through the USB port to do so...

wooow. that doesnt sound good. it doesn't sound like its related to libertine though. have you been messing with root access? it might be time to make sure your backups are up to date

Furthermore, the container still exists and the stuck installation process subsists with its silly blue spinning circle!!! Arghhhhh

I think I will end up reinstalling the whole operating system.

possible .... good luck!

@ubuntoutou said in Package installation stuck and spinning wheel never stops under Libertine:

@lakotaubp
$ libertine-container-manager destroy -i xenial
Libertine.py:124: ERROR: _delete_rootfs(): [Errno 13] Permission denied: 'dev'

strange. no clue what might cause this.

if you are ok to get rid of all containers and all else failed, you can delete manually. first find the file where the containers are configured. I can't remember the name, I think it's a json or xml file inside some dot folder in your home dir. something like .config/libertine/containers.json ... I'm just guessing the name from memory, but it is something like this. If you look for libertine in .local .config .cache, you'll find it. Look inside you'll see your containers. if you remove this file and the root and home folders of your containers: https://docs.ubports.com/en/latest/userguide/dailyuse/libertine.html#locations then everything should be gone and you can start over