[06:59] <zzarr> hello!
[07:01] <zzarr> I tested unity8 on my computer with 2 displays (one turned off, internal on laptop) and... what did I see.... a very nice greeting screen and after I logged in, a very nice desktop :D
[07:03] <zzarr> now if I only could launch applications without them crashing a split second after I start them :)
[07:04] <mvvvv> zzarr, unity8-session-desktop ? They is a workaround : https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1535058
[07:04] <zzarr> mvvvv, yes, it's the desktop session
[07:05] <duflu> Also, the web browser startup crash claims to have been fixed in xenial 17 hours ago:   https://launchpad.net/ubuntu/+source/oxide-qt
[07:05] <zzarr> will I be able to install applications I use on my phone too? (my MX4 Ubuntu Edition)
[07:06] <zzarr> nice nice, soo much progress :D
[07:07] <zzarr> how do I (or do I, or isn't there a way) to run X applications in Mir?
[07:10] <mvvvv> zzarr, have a look to xmir
[07:11] <zzarr> mvvvv, it's still XMir that is the current handler for X ? I know that they were redesigning how that works
[07:15] <mvvvv> zzarr, libertine ? I don't know what they decided
[07:15] <zzarr> didn't turn out as I wanted it, I don't know IRC to well
[07:17] <zzarr> mvvvv, I think you're right, I recognise that name
[07:18] <zzarr> mvvvv, do you know the state of that command?
[07:18] <zzarr> or... lib
[07:18] <zzarr> is it ready to use?
[07:18] <mvvvv> zzarr, I didn't tried it I don't know
[07:18] <zzarr> okey
[07:20] <zzarr> it's an sandbox for ubuntu-personal (that's what the description says)
[07:21] <zzarr> a sandbox for running deb based X11 apps it says
[11:22] <dandrader> ltinkl, so do I make lp:~dandrader/unity8/multiMonitorScreenshot absorb what lp:~lukas-kde/unity8/screenshotWindow was doing or do you wanna rebase the latter on top of the former?
[11:22] <ltinkl> dandrader, please take it over
[11:22] <ltinkl> dandrader, thanks!
[11:22] <dandrader> ltinkl, ok
[12:03] <dandrader> ltinkl, you made it Ctrl+PrtScn but Unity 7 uses Alt+PrtScn. So which unity8 should use?
[12:03] <ltinkl> dandrader, yeah good question, dednick pointed out the same - I have no idea why my system uses Ctrl
[12:04] <ltinkl> dandrader, it should probably be Alt
[12:04] <dandrader> ltinkl, ok
[12:04] <dandrader> ltinkl, you KDE user!
[12:04] <ltinkl> dandrader, nah, that in u7
[12:04]  * ltinkl doesn't recall remapping it
[12:47] <voobscout> Hello everybody! on this page https://wiki.ubuntu.com/Touch/Libertine it says that if i have a Puritine click installed and i want to run libertine from PPA, some extra steps are needed
[12:48] <voobscout> i'm using frieza device
[12:48] <voobscout> whom do I have to talk to?
[12:50] <davmor2> bregma: ^ is this you dude?
[12:53] <bregma> voobscout, if you have an m10 and want to add additional legacy apps to a new container (not to Puritine, which is in read-only storage) you need to fudge around with the libertine ContainersConfig.json file and then create a new container from the ssh or adb command line
[12:54] <bregma> but the PPA is gone as the various compenents are landing in the archives in preparation for OTA-11, so if you can wait 2 or 3 weeks for OTA-11 you're much better off
[12:55]  * bregma goes to update the wiki page
[12:55] <bregma> after OTA-11, it should all Just Work™
[12:55] <bregma> well, mostly
[12:56] <bregma> it should Work Better™
[13:03] <voobscout> bregma: thanks, I was able to create my containers, but was unable to run xterm
[13:04] <voobscout> bregma: I did everything as described here: http://paste.ubuntu.com/15980818/
[13:06] <bregma> voobscout, that should work around the limitations in OTA-10 OK, your problem may be elsewhere
[13:06] <voobscout> also, does anybody have any idea why M10 shows only 2 cores in /proc/cpuinfo ?
[13:07] <voobscout> bregma: where would the logs be for failed xmir run?
[13:07] <bregma> voobscout, you can start tracking down problems looking at the logs in ~/.cache/upstart
[13:08] <voobscout> bregma: are lxc containers supported as well or only chroot?
[13:10] <bregma> voobscout, the version of the kernel used on frieza does not support usemode LXC containers
[13:10] <bregma> we use LXC containers exclusively where supported by the kernel
[13:11] <bregma> you do not actually have to explicitly specify the type of container, the tools autodetect support and select the type automatically at creation time
[13:21] <voobscout> bregma: thanks!
[15:02] <dandrader> ltinkl, can you top-approve https://code.launchpad.net/~dandrader/unity8/multiMonitorScreenshot/+merge/292961 ?
[15:06] <ltinkl> dandrader, yup
[15:06] <dandrader> ltinkl, thanks
[15:06] <ltinkl> dandrader, oh, I haven't tested the Alt+PrtScr yet, so will do later (once the silo rebuilds again)
[15:07] <ltinkl> dandrader, otherwise screnshotting the shell worked fine
[15:07] <dandrader> ok
[16:12] <om26er> ChrisTownsend, Hi!
[16:12] <ChrisTownsend> om26er: Hey
[16:12] <om26er> ChrisTownsend, I re-installed Ubuntu and this time tries to create a lxc libertine container and it still fails to start
[16:13] <om26er> I ensured not to use sudo this time
[16:14] <ChrisTownsend> om26er: Ok, hmm, try starting it with "lxc-start -n $container_id -P ~/.cache/libertine-container --logfile start.out --logpriority DEBUG" and let's see what it is saying.
[16:16] <om26er> ChrisTownsend, lxc-start: lxc_start.c: main: 295 Executing '/sbin/init' with no configuration file may crash the host
[16:17] <om26er> that was printed on the console.
[16:17] <om26er> and this was inside the start .out file:
[16:17] <om26er>       lxc-start 20160428211617.426 INFO     lxc_start_ui - lxc_start.c:main:264 - using rcfile /home/om26er/.cache/libertine-container/xenial/config
[16:17] <om26er>       lxc-start 20160428211617.427 ERROR    lxc_start_ui - lxc_start.c:main:295 - Executing '/sbin/init' with no configuration file may crash the host
[16:17] <ChrisTownsend> om26er: That indicates is can't find the lxc config.  Is there anything in ~/.cache/libertine-container?
[16:18] <ChrisTownsend> om26er: Or is there anything in ~/.cache/libertine-container/xenial?
[16:18] <om26er> ChrisTownsend, there is a directory there, called 'vivid' for chroot
[16:18] <om26er> ChrisTownsend, no, the directory does not exist
[16:19] <ChrisTownsend> om26er: Hmm, so what is the output when you ran the create command?
[16:19] <ChrisTownsend> om26er: Sounds like the lxc create is failing.
[16:20] <om26er> ChrisTownsend, http://paste.ubuntu.com/16099001/
[16:21] <om26er> apparently the container is not being created, at all, hmm
[16:21] <om26er> ChrisTownsend, do you know a way to clear lxc' images cache ?
[16:22] <ChrisTownsend> om26er: This is strange.  The output indicates the rootfs is unpacked, so it's installing it, but it doesn't seem to be in the place I expect it to be.
[16:23] <om26er> ChrisTownsend, hmm, how can I clear everyhing related to libertine? ...to start fresh
[16:24] <ChrisTownsend> om26er: I thought you did just start fresh.
[16:24] <om26er> ChrisTownsend, I did reinstall Ubuntu but a few days ago. After that I created a chroot in libertine, that worked.
[16:27] <ChrisTownsend> om26er: Then it should be in a pretty decent state for lxc.  Ahh, I know what is going on.  If the container fails during any part of the whole installation, then it wipes it clean.  So, in order to debug this we need to do something.  Give me a sec.
[16:33] <ChrisTownsend> om26er: Ok, so you need to modify /usr/bin/libertine-container-manager and comment out the following line at around line 390: delete_container(args.id).
[16:33] <ChrisTownsend> om26er: It will be the line below: if not container.create_libertine_container(password, args.multiarch, args.verbosity):
[16:35] <om26er> ChrisTownsend, for me it was line 353, but done.
[16:36] <ChrisTownsend> om26er: Sure.  Now try to create the container again and this time, it should be there.  And then we can try the lxc-start command from above.
[16:38] <om26er> ChrisTownsend, it still deletes the container on failure
[16:38] <ChrisTownsend> om26er: Ugh
[16:40] <om26er> ChrisTownsend, I can see rootfs is extracted there and at the end it deletes
[16:42] <ChrisTownsend> om26er: Ok, do this one:  In /usr/lib/python3/dist-packages/libertine/LxcContainer.py, go to create_libertine_container and then comment out the first self.destroy_libertine_container() you find.
[16:46] <om26er> ChrisTownsend, ok, these are the logs when i try to start the container: http://paste.ubuntu.com/16102061/
[16:48] <ChrisTownsend> om26er: Ah, is cgmanager installed?
[16:48] <om26er> ChrisTownsend, it is, yes
[16:49] <ChrisTownsend> om26er: Hmm, something is missing, but this is kind of out of my expertise.  You might ask hallyn.
[16:49] <ChrisTownsend> om26er: Or stgraber.
[16:55] <om26er> ChrisTownsend, pinged stgraber, couldn't find hallyn online but he does seem to be a Linus Torvalds doppelganger ;)
[17:59] <om26er> ChrisTownsend, Hi! Now the lxc containers starts (with help from hallyn), I can install apps as well but clicking on them in classic scope does nothing
[19:16] <mokmeister> I have a M10 bq tablet. I want to install a deb. I haven't made the system partition rw. From .local/share/libertine I entered "libertine-container-manager create -i puritine2 -n "Puritine 2" -t chroot -d vivid --force"
[19:18] <mokmeister> I received back "Errors were encountered while processing: isc-dhco-client, x11-common, libxtst6, libfakekey0, matchbox-keyboard, matchbox and ca-certificates
[19:18] <mokmeister> "
[19:19] <mokmeister> I'm wondering if what I have done is right?
[19:20] <mokmeister> Is this up to date to how you should do things with an M10 tablet? https://wiki.ubuntu.com/Touch/Libertine
[19:20] <mokmeister> I also looked up this doc: https://docs.google.com/document/d/1yJepibh68YaQijWO3Z3dWTtTTmzXnMmEE8eswhUXzw4/edit?pref=2&pli=1
[20:01] <mokmeister> sorry, asking questions in wrong channel! Oops!