LIBERTINE

killerbee

@advocatux nope with the "touch mouse". Its cumbersome but doable I have issues with connecting to external display.... I only get dark gray screen, no display on external monitor, but tablet "changes to mousepad"

UPDATE: After I connected an external keyboard ONCE it now is able to switch on the external monitor. This allows me to use thunderbird on the tablet HOOORAYYYY!

killerbee

@advocatux external mouse attached via USB works nicely

advocatux

@killerbee \o/

arubislander

I am running 16.04 (2018-W27) on a BQ M10 FHD. I installed it via the UBPorts Installer with the -wipe optsion. When I run:

$ libertine-container-manager -i xenial

I get:

I: Retrieving InRelease 
I: Checking Release signature
...
I: Configuring libc-bin...
I: Base system installed successfully.
ChrootContainer.py:78: ERROR: create_libertine_container():	Failed to create container
libertine-container-manager:123: ERROR: create():	Failed to create container: 'destroy_libertine_container() missing 1 required positional argument: 'force''

Anybody else come across this error message?

EDIT:
I briefly switched to the Development channel to see if the experience was different there. Unfortunately it is not.

Lakotaubp

@arubislander yes same message missing 1 required positional argument: 'force' 'Not that that helps you much of course.

arubislander

@lakotaubp
No, not really
I will install libertine on the desktop and see if I get the same behavior. At the same time I will check if this issue has already been reported.

Lakotaubp

@arubislander Don't think it has yet. Tried on laptop to nexus 5 from windows 10 now just testing from nexus system setting, can't try anything else till later. Also not sure of current libertine status.

arubislander

Hmmm... don't think the libertine packages are in very good shape on the Xenial desktop either. I did:

$ sudo apt install libertine python3-libertine-chroot

to be able to install a libertine chroot container.
Then I did

$ libertine-container-manager -i xenial -d xenial -t chroot

as the default on the desktop is to create an lxc container. It installed lots of things, and got further along than on the tablet, But at the end it said:

Refreshing the container's dynamic linker run-time bindings...
proot info: pid 5345: terminated with signal 11

Which I am sure is not right either.

EDIT:
I see now that the libertine packages on the tablet come from the UBPorts repo, so I am guessing the project was forked, which would mean that the original issue has to be logged against the Ubuntu Touch project.

arubislander

It is possible that this issue here is related to what I am experiencing. If that is the case, then a fix should be on it's way soon

Marathon2422

I have a legacy apps scope now

TartanSpartan

@marathon2422 said in LIBERTINE:

I have a legacy apps scope now

How did you manage that? On a development image for Xenial or something?

Marathon2422

@tartanspartan
I am on 16.04 dev,
go on your apps (scope) page
,pull up from the bottom edge,
click on the star on the right side to have it as a scope page
( do not know if it is working correctly yet tho ).

TartanSpartan

Oh right. Yes, I've had the scope for as long as I can remember on MX4 Xenial but it's never functioned. I've always had to do CLI launches for Libertine apps. Can't wait until GUI is working again.

arubislander

@arubislander
Not sure if the issue I linked to was solved in the current RC (2018-W28). But if it has, then it is not the issue I am experiencing, because that is still occurring.

arubislander

My inability to install a libertine container might have been a case of 'user error'.
After looking at the Ubuntu Touch Q&A 32 hosted by @UniSuperBox after quite a while (welcome back Dalton! You have been missed. Too bad we had to miss @Flohack now), in which @mariogrip mentioned that containers sometimes failed to install with the GUI, I decided to try again from the command line this time.
I have my BQ M10 FHD tablet on 16.04 RC. I fired up Terminal-app and tried

$ libertine-container-manager create -i xenial -n Xerus

It went on for longer this time, but in the end it informed me that container creation had failed.
Encouraged, because the process had continued past the previous point of failure, I then remembered that it might have failed this time due to the Terminal-app running under confinement. I remembered also that if the ssh-server had been enabled (which it had on my tablet) confinement could be escaped by running

$ ssh localhost

This failed because I had not added the pubic ssh key of the phablet user to .ssh/authorized_keys. So I did:

$ cat .ssh/id_rsa.pub >> .ssh/authorized_keys
$ ssh localhost

And I was in. After that I tried the first command again and this time the container installed!

$ libertine-container-manager list
xenial

\o/

No idea if this would have worked before RC-4, but I am happy it works now. Hope this helps anyone facing similar issues.

advocatux

@arubislander thank you for writing this how-to.

If you run libertine-container-manager list what's the output?

Using Libertine manager, in spite of I setting a different name, it always creates the default one (xenial).

PS In your first command, xenail is probably a typo?

arubislander

@advocatux said in LIBERTINE:

@arubislander thank you for writing this how-to.
If you run libertine-container-manager list what's the output?
Using Libertine manager, in spite of I setting a different name, it always creates the default one (xenial).
PS In your first command, xenail is probably a typo?

You are welcome. Thanks for catching the typo. I corrected it. I also added the the output of libertine-container-manager list. I think libertine-container-manager list gives the id's of the containers, not their names.

advocatux

I think libertine-container-manager list gives the id's of the containers, not their names.

@arubislander I really don't know and the man page only states about that command "Lists all existing Libertine containers".

When you created the container, did you make that typo (xenail) or you wrote it correctly? I'm asking because if you did it, the list command output should be xenail and not xenial in your case.

arubislander

@advocatux said in LIBERTINE:

When you created the container, did you make that typo (xenail) or you wrote it correctly? I'm asking because if you did it, the list command output should be xenail and not xenial in your case.

I had typed it correctly when making the container. I suspect that when creating the container from the UI, when it asks for the container name it is referring to the -n (or --name) parameter, Xerus in my case. xenial is probably the default value for the id (-i or --id) parameter used by the UI and which I coincidentally used this time. Normally I number my containers, so this one would have gotten the id xenial01, but since my BQ tablet only features 16 GB of storage, more than half of which is already in use by the OS and apps I have installed, I didn't intend to create more than one container, and hence felt no need to number the one.

advocatux

@arubislander yeah, I understand you. Imagine I'm testing it on a BQ E4.5 lol