=== chihchun_afk is now known as chihchun [07:26] Wow. Good anti-aliasing = almost readable text at 3px high [07:30] duflu, what? 3px awesome [07:31] zzarr: Just admiring Google docs previews. And trying to read the docs in tiny print [07:31] duflu, nice, what device? [07:31] zzarr: Desktop [07:31] duflu, mir? [07:32] zzarr: No just Chrome... [07:32] duflu, okey [07:32] But I shall try to make Mir as good in future [07:33] duflu, you're a programmer @ Canonical? [07:33] zzarr: Yes :) [07:33] duflu, awesome [07:35] duflu, I have obtained the kernel config from my ASUS Chromebook Flip (ARM, RK3288) [07:35] zzarr: Want to try to use Mir? [07:36] I know I some how need to extract the hardware parts in order to merge with the Ubuntu kernel and use Mir [07:36] duflu, you're right on the money [07:37] duflu, I can't think of a better OS for the computer then Ubuntu since it have a touch screen and can flip in to a tablet [07:37] I can boot it from a SD card [07:37] zzarr: If the kernel supports DRI for your graphics chip then you can stick with the ChromeOS kernel (which helps a lot and often is more likely to work for some ARM devices than stock Ubuntu) [07:38] zzarr: What's in /dev/dri? or /sys/class/drm? [07:39] duflu, I'll have a look [07:40] I am a ChromeOS fan too. Although Google has a habit of using very old kernels in ChromeOS and Android [07:40] in /dev/dri card0 card1 controlD64 renderD128 renderD129 [07:40] duflu, yes, I know [07:41] duflu, other whys the Chromebook is awesome [07:41] Yeah ChromeOS is pretty. But once you run Ubuntu on a Chromebook it's profoundly faster (for Intel anyway). Which means Google's got a lot of improving to do [07:43] I recall they are building a new display system to solve that (and replace X11 that it still uses I hear) [07:43] in /sys/class/drm I find card0 card1 card1-eDP-1 card1-HDMI-A-1 controlD64 renderD128 renderD129 version [07:43] Although there might be other reasons why their windowing system is slow [07:44] my Chromebook uses a windowing system called freon [07:44] zzarr: OK, good news: Your ChromeOS kernel has a chance of just working with Mir (Ubuntu in a chroot installed via https://github.com/dnschneid/crouton). It's definitely worth a try. You sure that's ARM and not Intel? [07:45] duflu, I have a crouton chroot installed [07:46] zzarr: You'll need to have it set up for fullscreen Ubuntu (not Ubuntu in the browser) [07:46] duflu, it's an ARM I'm sure about that [07:46] Wow that Chromebook Flip looks like a great device [07:46] duflu, it is :-D [07:47] * duflu adds it to the wishlist [07:47] quad core, 4GB RAM :-) [07:48] zzarr: OK then. The next hurdle you might find (I remember hitting this now) is that Chromebooks often lack VT support in their kernels. Which is not a big deal but just Mir can't deal with that yet -- https://bugs.launchpad.net/mir/+bug/1169020 [07:48] Launchpad bug 1169020 in Mir "[regression] Mir gives up too easily - std::exception::what: Failed to find the current VT" [Medium,Triaged] [07:49] So that will stop you unless you have the Mir code I suspect [07:51] I have the kernel config for the chromebook, can I add a console to it that way? [07:52] Not sure. Not very likely how nailed down ChromeOS is. You can only change what Google lets you change [07:53] but if I have the source code (which I have) and the config, can't I just configure and build a new kernel? [07:56] I thought I might be able to build a kernel with this tutorial https://github.com/dnschneid/crouton/wiki/Build-chrome-os-kernel-and-kernel-modules [08:04] zzarr: If you're in a chroot then you need a kernel that doesn't break ChromeOS. So I would recommend keeping the existing one and we should fix Mir to suit [08:05] duflu, yea, but I thougt I should build a new kernel and run a stand alone environment from a SD card [08:05] zzarr: Sounds like the Ubuntu kernel lacks support for the chipset then? [08:05] Usually does for newish ARM devices [08:06] yes, but I can configure a Chromebook kernel and build it [08:07] so I install a custom Chromebook kernel on the SD card along with Ubuntu [08:07] that way I should get the best of both worlds [08:07] True [08:08] zzarr: I would personally recommend sticking with the chroot though. Fixing Mir theoretically is easier than building your own OS with custom kernel :) [08:09] duflu, I have that as a second way out then :-) [08:09] it's more fun to try it from scratch [08:09] It's good you think that [08:10] Because someone has to be adventurous and try [08:10] I have built linux kernels before (for UltraSparc) [08:11] duflu, exactly, that's the way we move forward [08:12] duflu, I'm a programmer too you see, so I know about the fact that some things are hard to do === sil2100_ is now known as sil2100 [08:21] duflu, what line or lines define the console in the kernel config? [08:22] zzarr: Sorry, don't know [08:22] okey, I'll stfg it [09:09] zzarr: Thanks for reminding me about the VT bug though. If I remember and get time I'll try to fix it before the bug reaches 1 year old [09:09] duflu, no problem :-) [09:09] Actually the bug was from 2013, but I only associated it with chromebooks mid last year [09:15] duflu, okey [09:15] If Xorg in an Ubuntu chroot can start, Mir has no excuse for failing to start... [09:16] We just have unnecessary error checking. And some errors are not really errors. [09:18] duflu, that explains it [09:19] duflu, but I don't get any 3D/OpelGLES support in the chroot (since ChromeOS uses freon) [09:21] duflu, I though of making a freon to mir wrapper (I don't know if it's a good idea or not a time a go) [09:22] duflu, I guess it would be a huge project even though both mir and freon is based of some parts of wayland [09:22] not knowing if they are the same parts or not [09:24] zzarr: I'm not sure about Freon, but Mir and Wayland are entirely unrelated other than both (only just recently) use the same input library libinput. [09:24] I thought Freon was also completely separate [09:25] duflu, okey, so mir has nothing to do with wayland.... I see, I think that freon has thought [09:27] zzarr: You remind me now that Mir (when using the mesa-kms driver) also requires a device-specific driver in the Ubuntu chroot under /usr/lib/x86_64-linux-gnu/dri/. As Ubuntu doesn't have that for your ARM chip, it will be software-rendered even when working properly [09:27] Which is not good. It won't run well at all [09:29] duflu, that's not nice [09:30] zzarr: I know. It's because we use the Mesa implementation of OpenGL, which is portable but requires a DRI module specific to Mesa and the chipset to be accelerated [09:31] So hardware-accelerated Mir is limited to those covered by /usr/lib/x86_64-linux-gnu/dri/* [09:31] Minus *sw* :) [09:35] duflu, so I will not be able to get an accelerated mir without that driver what ever kernel config I manage to create? [09:35] zzarr: I suspect that's right [09:36] duflu, could I use an android-lxc for mir? [09:36] Unless you can find a custom libGLESv2 that works for your chipset [09:37] zzarr: For ARM hardware you might find usable drivers from Android, yes. But that's a maybe. [09:38] But Mir (via libhybris) only knows how to do that within an Android filesystem.... I think? [09:38] duflu, I know for a fact that there are Android devices based off of RK3288 [09:38] duflu, I suspect that you're right [09:46] I should clarify that using any custom libGLESv2 (e.g. future Nvidia support!) also requires a custom Mir driver to be written to bootstrap it for mode setting and buffer management [09:48] Hmm actually that's not quite right. We might be able to mix and match. But no matter because such a /usable/ libGLESv2 for RK3288 may not exist. [09:49] Or likely we're missing other glue [09:50] duflu, okey, is it possible somehow to compile a libGLESv2 for RK3288 myself? [09:53] duflu, or do I need deep knowledge about how the RK3288 chip (Mali764) is built? [09:54] zzarr: You might need source code, but actually the ABI for libGLESv2 is well known. So you might be able to find and just copy a binary too. Although that assumes it's no linking to something awkward (like Android's bionic) [09:55] duflu, okey === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [12:02] hello people [12:03] hi [12:03] After 1 day of debugging we found out the vivid+overlayppa LAPTOP setup I have here didn't boot to unity8 [12:03] because it was missing [12:03] EGL_PLATFORM=mir [12:04] but it seems that env var should not even be needed [12:04] I'm here to report the issue and ask for advice :) [12:05] doesn't sound like a mir problem, try with unity people #ubuntu-unity [12:05] j/k :P [12:05] LOL [12:06] I was about to throw a digital fist over :D [12:06] :D [12:08] faenil: I've never used EGL_PLATFORM=mir - I wonder what detects it. [12:08] alan_g: you mean who needs it? [12:08] ack [12:08] without that, libEGL turns to libX11-xcb, and calls GetXcbConnection -> segfault [12:10] alf: any ideas? ^^ [12:14] faenil: is $DISPLAY set? Unsetting that might discourage attempting an X connection [12:14] alan_g: we tried with DISPLAY= cmd [12:14] no diff [12:14] * alan_g suspected as much [12:17] faenil: I imagine you must have more than a vanilla vivid+overlay setup to get unity8 desktop. What else did you install? [12:17] just unity8-desktop-session-mir [12:17] then discovered that didn't pull in mir platform and client packages [12:17] so I installed 2-3 packages [12:18] mesa-kms, mesa-x, evdev4... [12:18] and that's it [12:18] mir-graphics-drivers-desktop? [12:19] That *ought* to pull in all the needed stuff in one go [12:19] * alan_g grabs v+o laptop [12:21] alan_g: yep, already reported a bug where that was suggested [12:22] https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1538659 [12:22] Launchpad bug 1538659 in unity8 (Ubuntu) "unity8-desktop-session-mir is missing mir-platform-* and mir-client-* dependencies" [Undecided,New] [12:22] oh, it was you :P [12:23] :^) [12:23] so, yeah, I don't know what else could be missing [12:24] Just updating & installing - I'll see what happens here and if I can diagnose [12:25] my laptop is running overlayppa as well, and I can boot unity8 without hacks [12:25] so I'm more inclined to think we're missing a pkg [12:26] Sorry, what's the difference between "my laptop is running overlayppa" and "vivid+overlayppa LAPTOP setup"? [12:31] I've probably other packages installed, but with apt-get install unity8-desktop-session-mir mir-graphics-drivers-desktop I can start a guest session with unity8. (But all I get is a black screen with a cursor) [12:35] alan_g: the buggy one is not my laptop [12:35] it's a laptop I setup from scratch :) [12:35] Ah, that's because USC is running, but nothing is connected to it. [12:35] alan_g: yes that's the issue, unity8 dies [12:35] good, you can reproduce it ;) [12:35] \o/ [12:35] that's the issue :) [12:36] if you add EGL_PLATFORM=mir somewhere so that unity8 picks it up [12:36] it will boot to unity8 :) [12:37] alan_g: I wonder if changes to the way we export symbols have made it impossible for mesa to detect that mir is running [12:38] * alan_g wonders where USC publishes the endpoint. There's no /tmp/mir_socket [12:40] alan_g: Perhaps USC doesn't publish an endpoint, the connection fd is just passed to sessions? [12:41] * alf has only faint memories of such facts, but can't be sure [12:44] My memory is that robert_a couldn't make that work at first, and so publishing the endpoint got "embedded" [12:46] thought it was moved to /run/mir_socket .. or something like that === chihchun is now known as chihchun_afk [12:47] You're thinking of $XDG_RUNTIME_DIR/mir_socket - but root tends not to have $XDG_RUNTIME_DIR set [12:48] isnt it /var/run/mir_socket? [12:50] http://bazaar.launchpad.net/~lightdm-team/lightdm/trunk/view/head:/src/unity-system-compositor.c#L467 [12:50] use the source lukes [12:50] it's /run/lightdm-mir-0 [12:51] on desktop? [12:52] OK, I can crash a mir client. I'll dig into it after lunch === alan_g is now known as alan_g|lunch [12:59] alan_g|lunch: yeah it crashes on GetXcbConnection [12:59] (most likely, or at least that was what we found out yesterday) [12:59] libEGL -> libX11-xcb -> GetXcbConnection -> segfault [13:00] Saviq: Hi! I am trying to setup sbuild for Mir, duplicating what you have done for unity8. For the prepare-1-sbuild job how do I get the key files to pass as parameters? Can I just do 'sbuild-update --keygen' locally and upload, or do I need to do something different? [13:01] alf, yeah, that's what I did [13:02] should have documented that [13:02] Saviq: btw, you have done a great job with all the prepare and build scripts. I am have I can just copy them with small changes and they work :) [13:03] Saviq: s/I am have/I am happy/ [13:03] alf, changes!? :P [13:03] alf, would be interested to know what you needed :) [13:04] Saviq: not additions, just skipping some parts because I don't yet have some plugins currently installed (e.g. conditional build step, set build name) [13:04] alf, ah those [13:05] alf, I'm not totally sure about the conditional build steps, the plan was to skip heavy steps if they've been done on a machine already [13:05] so you can just run the prepare job and let it figure stuff out [13:05] seems to be working fine === alan_g|lunch is now known as alan_g [14:05] faenil: can you confirm whether apt-get remove mir-client-platform-mesa2 fixes the problem for you? (It works for me) [14:06] * alan_g thinks that there's a packaging "incantation" missing somewhere [14:20] alan_g: I hope it's not that, because that's what I did for my own laptop as well a week ago, but I think I checked that and mesa pkg was not installed in the setup I made from scratch [14:21] let's see... [14:21] alan_g: and I agree about the pkg incantation, that's my opinion as well [14:21] alan_g: crap, it's installed... [14:22] I spent two days debugging an issue I fixed on my own laptop by myself a week ago. [14:22] * faenil headdesks [14:32] greyback: ^ [14:32] (ok, it was 2 weeks ago) [14:34] faenil: you're joking?! [14:36] greyback: I wish I were [14:36] aiii [14:37] still, that identifies a mir packaging/so lib issue [14:37] yeah, let's see if I reported a bug first time got my own laptop booting [14:38] * faenil reads backlog from good old times [14:46] [13.01.16][17:59]< faenil> | anpok: I've got mesa.so.2 and mesa.so.3 [14:46] [13.01.16][18:01]< anpok> | try to get rid of mesa.so.2 [14:47] greyback: ^ he saved me last time :D [14:49] [13.01.16][17:58]< anpok> | crash in XGetXcbConnection sound like mesa loads an older mir client driver and tries to verify the EGL Display it got from the mir server [14:50] boom, that was the winning hint [14:50] dednick: ^ if you're interested :) [14:54] heh [14:56] proable need a Replaces: mesa2 in the package control for mesa3 [14:57] alan_g: http://bazaar.launchpad.net/~unity8-desktop-session-team/unity8-desktop-session/trunk/view/head:/debian/control#L18 [14:57] i have about 10 different versions of mir on my laptop. sound probably sort that out! [14:58] so, desktop session is depending mir-graphics-drivers-desktop already [14:58] dednick: I think "Breaks" is probably right, but I disavow all knowledge of those rules [14:59] yeah. i have no idea which one it is :) [15:01] faenil: did you raise a bug? I can poke RAOF about adding the right incantation. (I trust his advice on these.) [15:01] alan_g: ok, the problem with session-mir is that overlay PPA has a version from March 2015 [15:01] which didn't pull in drivers [15:02] That needs an update then. [15:03] sil2100: ^ [15:03] now, who pulled in mesa2 and mesa3 at the same time is another mistery that needs solving [15:03] s/who/what [15:04] faenil: hmmm, could you guys get a bug filled for that? [15:04] sil2100: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1538659 [15:04] Launchpad bug 1538659 in unity8 (Ubuntu) "unity8-desktop-session-mir is missing mir-platform-* and mir-client-* dependencies" [Undecided,New] [15:04] I will rename the title now [15:05] faenil: thanks, let me look at it shortly [15:05] sil2100: the PPA doesn't have that pkg, so it's coming from vivid archive [15:08] sil2100: title updated [15:22] alan_g: I'm not sure what I should report a bug about [15:22] that somehow I end up with mesa2 and mesa3 together after installing vivid and session-mir? :D [15:24] Well, that would be fine except that recent libmirclients die if mesa2 is installed. [15:25] There ought to be some way to tell dpkg to sort that out. [15:26] But if you've not logged a bug already I can create on [15:26] *one [15:31] what's that trick for using bzr and meld? is it just "bzr diff -r lp:mir --using meld" ? [15:32] alan_g: yeah I just don't know who pulls both mesa2 and mesa3 in [15:33] (haven't filed a bug yet) [15:34] faenil: mesa2 is probably from a seed. mir-graphics-drivers-desktop? [15:34] Or maybe its mesa? [15:54] alan_g: don't know [16:59] alan_g: https://bugs.launchpad.net/mir/+bug/1539184 [16:59] Launchpad bug 1539184 in Mir "Unity8 on Vivid doesn't boot, due to mesa2 and mesa3 client platforms being installed at the same time" [Undecided,New] [17:00] I left it vague [17:00] at least we won't forget about it now ;) [17:11] faenil: thanks, I'll update [17:15] cheers === alan_g is now known as alan_g|EOD