[03:56] <barretj> I installed Android Studio according to the instructions on this page: https://wiki.ubuntu.com/ubuntu-make
[03:56] <barretj> and supposedly that also installs the Android SDK
[03:56] <barretj> what path does it install the SDK to?
[03:57] <barretj> I ask because I am getting this error: Error: ANDROID_HOME is not set and "android" command not in your PATH. You must fulfill at least one of these conditions.
[06:40] <pitti> Good morning
[07:14] <larsu> good morning
[07:27] <didrocks> morning
[07:28] <larsu> hi didrocks!
[07:28] <larsu> hi pitti!
[07:28] <didrocks> hey larsu ;)
[07:28] <didrocks> cold going to an end?
[07:29] <larsu> hopefully. It's definitely better than yesterday
[07:29] <larsu> thanks for asking :)
[07:29] <larsu> how are you?
[07:30] <didrocks> I'm great thanks!
[07:30] <didrocks> starting to get crazy without doing any exercise and so no work break
[07:31] <didrocks> I'll try to do some cycling today during the break, seems the weather will permit that
[07:32] <larsu> :)
[08:06] <larsu> Laney: :/ https://bugzilla.gnome.org/show_bug.cgi?id=739567#c2
[08:06] <larsu> head -> desk
[08:22] <seb128> good morning desktopers
[08:24] <didrocks> hey seb128
[08:26] <seb128> lut didrocks :-)
[08:26] <didrocks> seb128: do you mind reviewing jayatana in the NEW queue? I just pushed it and as I've done quite a lot of packaging cleanup, don't want to ack it myself :)
[08:26] <seb128> didrocks, sure can do
[08:26] <didrocks> thanks!
[08:47]  * willcooke -> still sick
[08:48] <willcooke> bbl
[08:48] <willcooke> larsu, ^  gonna miss our 1:1 sorry
[09:04] <Laney> hey hey
[09:04] <Laney> larsu: grim
[09:05] <larsu> Laney: sorry, didn't want to start your morning like that. Good morning! :)
[09:07] <didrocks> morning Laney!
[09:07] <seb128> hey Laney
[09:10] <Laney> happy friday folks ;-)
[09:10] <larsu> Laney: I didn't know we had this --enable-distro thing in gnome-terminal
[09:10] <larsu> that's profoundly ugly
[09:11] <Laney> I think he did it after getting told off
[09:14] <larsu> but why add all this complexity?
[09:14] <larsu> I really wonder why he cares so much
[09:15] <Laney> avoiding a complete climbdown?
[09:40] <seb128> didrocks, is systemd supposed to write a syslog or dmesg?
[09:40] <seb128> I've neither of those being written and journalctl is empty
[09:43] <didrocks> seb128: yeah, it's supposed to forward to /var/log/syslog
[09:43] <didrocks> seb128: sudo journalctl is empty?
[09:44] <seb128> didrocks, oh, no, you need to sudo it...
[09:44] <didrocks> yeah, it's a bug on the list
[09:44] <didrocks> so that people on the admin group can as well without sudo
[09:45] <didrocks> it should still forward to syslog
[09:45] <seb128> right, that got me confused
[09:45] <seb128> empty journal, no hint that you need to use sudo
[09:45] <seb128> it doesn't
[09:45] <seb128> but I rm-ed syslog (to have fresh logs)
[09:45] <didrocks> hum, I doubt you created /var/log/journald, right?
[09:45] <didrocks> ah
[09:45] <seb128> so maybe it skips it if the file doesn't exist?
[09:45] <didrocks> probably it fallbacks to permanent journald storage then
[09:45] <seb128> no, but I rmed /var/log/*log*
[09:46] <seb128> well rather *.log *.1 syslog dmesg
[09:46] <didrocks> seb128: quite easy to know, if you sudo journalctl
[09:46] <seb128> well, that is working, thanks
[09:46] <didrocks> do you only have the current boot?
[09:46] <didrocks> or older logs
[09:46] <seb128> yes
[09:46] <seb128> only current
[09:46] <didrocks> ah, so it disables forwarding and not activate permanent storage, interesting
[09:47] <didrocks> did you rm and reboot?
[09:47] <didrocks> or didn't reboot yet
[09:50] <seb128> reboot
[09:50] <didrocks> so, not an opened fd
[09:51] <didrocks> worth logging a bug IMHO
[09:51] <didrocks> can be a syslog thing TBH
[09:53] <seb128> bug saying what?
[09:53] <seb128> "deleting syslog should activate journal mode"?
[09:54] <didrocks> seb128: I would rather expect: deleting logs in /var/log/ shouldn't stop logging further boot
[09:55] <seb128> k
[09:55] <didrocks> (via syslog)
[09:55] <seb128> well, boots are logged
[09:55] <seb128> or at least the current one is
[09:55] <seb128> since it's in journalctl
[09:56] <didrocks> seb128: persistent logging then?
[09:56] <didrocks> or "logging on disk"
[09:57] <seb128> didrocks, let me check, maybe it has old logs
[09:57] <didrocks> can be, didn't check yet
[09:57] <seb128> but sudo systemctl --list-boots has only one entry
[09:57] <seb128> I guess that would record previous boot if it had those
[09:58] <seb128> I reboot 3 times since
[09:58] <seb128> the --boot option helps says "ID or, if unspecified, the current boot"
[09:58] <seb128> so I guess --list-boots should list all boots
[09:58] <seb128> since there is only 1 there is an issue with persistency
[09:58] <didrocks> seb128: if you don't have permanent journald logging, it will only list last boot
[09:59] <didrocks> so even with the syslog forwarding working, you won't get that
[09:59] <didrocks> (I guess you s/systemctl/journalctl)
[10:00] <seb128> yeah, sorry, journalctl ;-)
[10:00] <didrocks> basically, it's:
[10:00] <seb128> grrr, autofingers, I keep wanting to type "ctrl"
[10:00] <seb128> instead of ctl :p
[10:00] <didrocks> - you always get all journalctl features for current boot
[10:00] <didrocks> - you only get them on previous boot with journald persistent logging (not enabled by default)
[10:01] <didrocks> - otherwise, if syslog is installed, it will fw logs to it for previous boots, and you won't have access to them via journalctl
[10:01] <didrocks> by default, on debian/ubuntu, we enable syslog forwarding by default
[10:01] <didrocks> we discussed in case syslog is removed to enable persistent journald logging automatically
[10:02] <didrocks> (which is just about mkdir /var/log/journal)
[10:06] <Laney> cherry-picked some stuff, mir backend builds now
[10:07] <seb128> Laney, great!
[10:07] <Laney> ;-)
[10:08] <seb128> does anyone know what " '$nbr': '[1-6]$' means in bash?
[10:09] <seb128> is that "true if $nbr is a number between 1 and 6"?
[10:12] <Laney> haven't seen that syntax before
[10:12] <Laney> share the script?
[10:13] <seb128> Laney, /etc/init.d/console-setup
[10:14] <seb128> 	if expr "$(fgconsole 2>/dev/null || true)" : '[1-6]$' >/dev/null && \
[10:14] <seb128> 	   (! type plymouth >/dev/null || ! plymouth --ping); then
[10:14] <seb128> 	    log_action_begin_msg "Setting up console font and keymap"
[10:14] <Laney> ah
[10:14] <Laney> expr, I think that's a regex match
[10:15] <seb128> so basically if "fgconsole" returns a number between 1 and 6?
[10:15] <Laney> ye
[10:15] <seb128> k
[10:15] <seb128> next question, why this check?
[10:15] <seb128> hint, under systemd, that number is "7"
[10:15] <seb128> which makes the keymap not being applied to consoles on boot
[10:16] <seb128> I guess I should move to -devel
[10:16]  * seb128 does that
[10:16] <Laney> 7 for me too and I'm not using systemd atm
[10:17] <seb128> k, so maybe I don't understand the script
[10:17] <Laney> ah, that's because I ran from X of courser
[10:17] <seb128> ah
[10:17] <seb128> that was my next question, how did you run it :p
[10:17] <Laney> 1 on vt1
[10:17] <seb128> in my case I just did an "fgconsole" call in the init script and I'm looking at syslog after boot
[10:17] <seb128> right
[10:17] <seb128> it's the console you are on
[10:18] <seb128> but what is that supposed to be for init scripts
[10:18] <seb128> not manually ran
[10:18] <seb128> and why this check?
[10:20] <Laney>        --force
[10:20] <Laney>               Do not check whether we are on the console.  Notice that you can be forced to hard-reboot your computer if you run setupcon
[10:20] <Laney>               with this option and you are on a X server.
[10:20] <Laney> probably because of that
[10:21] <seb128> hum
[10:22] <seb128> well, that seems to be the wrong way to check if you are on an xserver
[10:22] <seb128> since systemd runs it on vt7
[10:22] <seb128> and there is no xserver :p
[10:22] <didrocks> seb128: s/systemd/ubuntu/
[10:22] <didrocks> seb128: I guess it's lightdm forcing that
[10:22] <seb128> systemd on ubuntu
[10:22] <didrocks> (on fedora with systemd, it's vt1)
[10:22] <seb128> didrocks, doesn't happen under upstart though
[10:22] <seb128> so not "ubuntu"
[10:22] <didrocks> seb128: we run on vt7, even under upstart, don't we?
[10:23] <seb128> hum
[10:23] <seb128> so why is the keymap correct under upstart?
[10:23]  * seb128 looks more into the issue
[10:23] <didrocks> seb128: you mean on !x_session
[10:23] <seb128> no, on boot
[10:23] <didrocks> seb128: on x, the keymap is correct, isn't it?
[10:23] <seb128> boot with upstart as pid1, console is azerty
[10:23] <seb128> use init=/bin/systemd
[10:23] <seb128> console is qwerty
[10:24] <seb128> dunno
[10:24] <didrocks> seb128: what do you mean by "console", like, you go on emergency mode?
[10:24] <seb128> on X lightdm/u-s-d sets it to my user value
[10:24] <seb128> no
[10:24] <seb128> like I do ctrl-alt-f1
[10:24] <didrocks> yeah, so that's vt1, nothing to do with where the X server is running, right?
[10:24] <seb128> no, you are the one who mentioned X
[10:25] <seb128> that confuses me ;-)
[10:25] <didrocks> 11:22:02    seb128 | since systemd runs it on vt7
[10:25] <seb128> Xorg doesn't even run in those tests
[10:25] <didrocks> what's the "it" then? :)
[10:25] <seb128> the init script
[10:25] <seb128> 	if expr "$(fgconsole 2>/dev/null || true)" : '[1-6]$' >/dev/null && \
[10:25] <seb128> 	   (! type plymouth >/dev/null || ! plymouth --ping); then
[10:25] <seb128> 	    log_action_begin_msg "Setting up console font and keymap"
[10:25] <seb128> I put a
[10:25] <didrocks> ah, you talked about the X server with Laney first
[10:25] <seb128> "fgconsole" there
[10:25] <didrocks> ok
[10:25] <seb128> and look at journalctlk
[10:25] <didrocks> are you sure it's running on vt1, this script?
[10:25] <seb128> and it printed "7"
[10:25] <seb128> no
[10:25] <seb128> it runs on 7
[10:25] <Laney> did you try that under upstart?
[10:25] <didrocks> systemd is spawning vts on demand
[10:25] <seb128> according to the journalctl log
[10:26] <seb128> Laney, not yet, but under upstart my keymap is azerty
[10:26] <seb128> so I assume the script works
[10:26] <Laney> it would maybe rule out this script
[10:26] <seb128> didn't look at the differences yet
[10:26] <Laney> i.e. upstart could have a job
[10:26] <Laney> or something else might do it there
[10:26] <didrocks> ok, I think running it under upstart and see if it's running under vt7 or not will shade some lights
[10:26] <seb128> well, on what?
[10:26] <seb128> I still think that line
[10:26] <seb128> 	if expr "$(fgconsole 2>/dev/null || true)" : '[1-6]$' >/dev/null && \
[10:26] <seb128> is buggy
[10:27] <seb128> whatever the outcome of upstart or other run is
[10:27] <seb128> that script should run on boot, next line is
[10:27] <seb128> 	    if run_by_init; then
[10:27] <seb128> so running by init is a supported case and should work
[10:27] <seb128> no?
[10:27] <seb128> then i may happen that some other upstart script set the keyboard as well
[10:28] <seb128> still doesn't change the fact that console-setup should be doing it and is not?
[10:28] <didrocks> yeah, but at least, it would rule out if this script is in use or not
[10:28] <didrocks> (doesn't change that it's maybe buggy, of no use, and should be removed)
[10:28] <seb128> well, that's orthogonal
[10:28] <seb128> or another bug
[10:28] <didrocks> yeah, but while we are at it, can be interesting to decipher
[10:28] <seb128> right, I'm in the middle of debugging
[10:28] <didrocks> and know if we should look at some other place, or in this script
[10:28] <seb128> one step at the time ;-)
[10:29] <seb128> well, we can look at fixing that script in any case
[10:29] <seb128> even if it doesn't fix the keymap bug
[10:29] <didrocks> yeah, not what I'm telling
[10:30] <seb128> is there some magic command for "give me grub menu on next boot"?
[10:30]  * seb128 tired to key pressing keys to not get the menu
[10:30] <didrocks> keeping shift pressed? I'm sure there is some flags, but don't know
[10:30] <didrocks> to detect faulty boot
[10:30] <seb128> well, half of the time that doesn't work for some reason
[10:31] <seb128> shift kept pressed
[10:31] <didrocks> seb128: I saw that you have to press it during the bios
[10:31] <didrocks> not before
[10:31] <didrocks> at least, on my hw
[10:31] <seb128> too early then?
[10:31] <didrocks> was the case for me
[10:31] <seb128> I think it's the same here
[10:31] <seb128> it's annoying :p
[10:31]  * seb128 reboots a third time
[10:31] <didrocks> yeah, I'm sure there are more magic, like "it's not a state" :)
[10:33] <didrocks> oh nice, eurostar is directly leaving from Lyon now
[10:33] <seb128> rather than having to change in paris?
[10:33] <didrocks> yeah
[10:34] <didrocks> well s/now/next May/
[10:34] <didrocks> (or lille, I preferred changing in Lille)
[10:35]  * seb128 gives up on getting a grub menu and edit /etc/default/grub
[10:35] <Laney> i heard there might be one direct to berlin :-o
[10:35] <didrocks> seb128: I'm in grubby world as well
[10:35] <didrocks> trying to have a nice patch to have an upstart boot option
[10:35] <didrocks> but so that this only happens when we start to have systemd by default
[10:36] <seb128> shrug, of course I forgot to update-grub :p
[10:37] <didrocks> :p
[10:38] <didrocks> Laney: so, this script is running on vt7 under usptart (that's what you told)?
[10:39] <Laney> nah
[10:39] <didrocks> ah
[10:39] <Laney> I didn't debug it
[10:39] <Laney> leaving that to others for now
[10:39] <didrocks> seb128: you are rebooting under upstart or should I try?
[10:39] <didrocks> my bet is that it's not running on vt7 under upstart
[10:39] <didrocks> and so, it sets the locale
[10:40] <seb128> didrocks, I just booted under upstart
[10:40] <didrocks> ok
[10:40] <seb128> it exit 0 early
[10:40] <didrocks> oh?
[10:41] <didrocks> seb128: /etc/init/console-setup.conf
[10:41] <seb128> if [ -f /lib/lsb/init-functions ]; then
[10:41] <seb128>     . /lib/lsb/init-functions
[10:41] <didrocks> seb128: yeah, don't look further, this is the job setting it up under upstart ^
[10:42] <GunnarHj> Hi seb128!
[10:42] <seb128> GunnarHj, hey
[10:42] <GunnarHj> seb128: Is https://code.launchpad.net/~gunnarhj/ubuntu/vivid/gdm/config-error-dialog/+merge/239729 still on your 'list'? Also, would it help if I asked someone in the Swedish LoCo to test it, considering that I'm not able to do so myself? Or will you test anyway when reviewing?
[10:42] <seb128> GunnarHj, no, it was never on my list, I commented on it because it was similar to the lightdm one, but I didn't use/touch gdm for years and I don't feel like uploading it, letting that to Ubuntu GNOME team
[10:43] <seb128> didrocks, so seems the script bails out under upstart
[10:43] <GunnarHj> seb128: Ok, subscribing ubuntu-sponsors again, then.
[10:43] <seb128> GunnarHj, thanks
[10:43] <didrocks> seb128: yeah, and as we have the specific upstart job for it, that works…
[10:44] <didrocks> seb128: I wonder if systemd isn't just supposed to have systemd-localed doing the job and something doesn't work with our config
[10:44] <didrocks> like, it depends on /etc/locale.conf
[10:44] <didrocks> which we don't have
[10:45] <seb128> didrocks, no, systemd has systemd-vconsole
[10:45] <seb128> http://www.freedesktop.org/software/systemd/man/vconsole.conf.html
[10:45] <didrocks> seb128: trying to change the locale on a fedora system I have handy
[10:45] <didrocks> ah, interesting
[10:46] <seb128> didrocks, but it's turned off in debian/rules because console-data/setup do that
[10:46] <seb128> and nobody had time to properly figure out how to replace those yet
[10:46] <didrocks>   * Disable systemd-vconsole-setup.service for now.
[10:46] <seb128> didrocks, see pitti's comment on https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400393
[10:48] <didrocks> seb128: ok, seems pitti has the more context on this. I don't see the value if we have a delta there with upstream, but I think there are good reasons
[10:48] <seb128> didrocks, just "need to be reviewed before enabled" it seems
[10:48] <pitti> didrocks: I don't have much context, I didn't look into this at all yet
[10:48] <didrocks> seb128: well, I'm afraid that there are as well "keep in sync with other init systems" consideration
[10:49] <pitti> I use US layout anyway, so I didn't notice
[10:49] <pitti> yeah, for now "compatible with sysvinit/upstart" >> "use upstream solution which works differently under systemd"
[10:49] <didrocks> yeah, so I guess we'll have yet another compatibility layer (and a custom service) to provide
[10:50] <didrocks> pitti: let's discuss that next week, when you have time if you wish
[10:50] <pitti> didrocks: or rather fix the init.d script to DTRT?
[10:50] <pitti> we might have our ubuntu specific bits only in the upstart job
[10:51]  * didrocks not really a fan to have an init script doing something that is mostly built-in
[10:52] <didrocks> I think the init script is launched on the only available vt (vt7)
[10:52] <pitti> me neither -- as long as the builtin stuff DTRT, that's fine
[10:52] <didrocks> seb128: are you going to try removing the vt check?
[10:52] <seb128> we should maybe look at enabled vgconsole then?
[10:52] <seb128> didrocks, yes
[10:53] <seb128> but lunch first, bbiab
[11:08] <tkamppeter> I have prepared an SRU as bug 1386241, now this SRU will take longer to get verified (have to sort out some problems with printer manufacturers) and I want to get another SRU into Trusty, bug 1401835 which can get verified easily once the package is in proposed. How should I proceed?
[11:08] <tkamppeter> The conflict is in Trusty, bug 1401835 is to propose the SRU for both Utopic and Trusty.
[11:19]  * Laney hunts for a usb stick
[11:53] <willcooke> blurgh
[12:25] <Laney> ctrl-shift-d works for inspector now
[12:26] <Laney> so good
[12:26] <Laney> thanks to ricotz
[12:44] <seb128> tkamppeter, upload the easy fix first, get that moved to updates, then do another SRU with the longer to verify one
[13:19] <Laney> larsu: looks like gnome-tweak-tool has borderful buttons in addition to virt-manager (also a transparent background)
[14:30] <tkamppeter> seb128, the long one I have uploaded already some time a go and it got approved for verification. Now it turns out that the long one needs more changes (have to work out with manufacturers) and this week I got together the short one. Is it possible to somehow reject the current version of the long one and later on, after having fixed it and the short one being completed, upload a new version of the long one to the original
[14:30] <tkamppeter>  bug report and get that veriofied then?
[14:30] <seb128> tkamppeter, sure, you can do another SRU and ask the SRU team to discard the current one, you just need to use a version > to the current one
[14:41] <larsu> Laney: noted (sorry, crazy Friday)
[14:41] <Laney> np
[14:41] <Laney> should probably use the pad
[14:41] <Laney> ...
[14:41] <seb128> ok, great, with current vivid/unity8-desktop (desktop-next), unity8 has apps running in windows mode and you can move/resize those
[14:42] <larsu> seb128: how about unity7?
[14:42] <larsu> did Trevinho's patch land?
[14:42] <seb128> it's early not-doing-a-lot mode (no resize handle, no alt-tab), but still cool ;-)
[14:42] <larsu> seb128: that's very cool though
[14:42] <seb128> larsu, different topic? I'm speaking about wm under unity8
[14:42] <seb128> unity7 has wm since day 1 :p
[14:42] <seb128> it uses compiz
[14:43] <larsu> seb128: yes, different (but old) topic about windows with csd
[14:43] <seb128> Trevinho, ^
[14:43] <seb128> how is that work going?
[14:43] <Trevinho> larsu: ah I was confused, I thought you were talking about the gdk mir backend...
[14:43] <seb128> hehe
[14:43] <Trevinho> larsu: on compiz side, not yet
[14:44] <seb128> so testing gtk3-demo
[14:44] <seb128> windows can be moved and resized, and decorations from GTK are on the left
[14:44] <seb128> still no border
[14:44]  * larsu sees this not happening this cycle
[14:44] <larsu> again.
[14:44] <Trevinho> seb128: using the mir-demo-shell some of these stuff is working
[14:44] <seb128> nice to see that it has "x_-" on the left though
[14:44] <Trevinho> larsu: no, it will :P
[14:45] <seb128> Trevinho, well, we are speaking unity7 there
[14:45] <seb128> unity8 is a different topic I guess
[14:45] <seb128> wm is just starting being added to it
[14:45] <Trevinho> seb128: ah, sorry..... Yes
[14:45] <larsu> Trevinho: this is what you said the last two cycles...
[14:46] <larsu> not trying to start a huge discussion though
[14:46] <Trevinho> larsu: nope, just the last one... and did some work, but then the irreparable happened :P
[14:59] <tkamppeter> seb127, how do I contact the SRU team, do they have a special IRC channel?
[14:59] <Laney> you subtracted 1 from seb128, how mean!
[15:00] <seb128> lol
[15:00] <seb128> tkamppeter, no, they don't, just comment on the SRU bug asking to drop the current SRU or try #ubuntu-devel
[15:05] <Laney> ah, dist-upgrade finished; unity8 session works
[15:06] <Laney> what's the key to make desktop files show up in the dash?
[15:07] <tkamppeter> seb128, thanks, comment added to bug 1386241.
[15:08] <seb128> Laney, X-Ubuntu-Touch=true
[15:09] <Laney> ty
[15:29] <Laney> should adding that to gedit.desktop and running it be enough?
[15:31] <seb128> "running it"?
[15:31] <seb128> what are you trying to do?
[15:31] <seb128> adding the key to gedit.desktop and restarting unity8-dash should make gedit be listed in the apps icons
[15:31] <seb128> under unity8
[15:31] <seb128> clicking on it then should start gedit
[15:32] <Laney> ok yeah, I just get a black screen
[15:32] <seb128> k, so backend is buggy
[15:32] <seb128> that's already the case is stock vivid
[15:32] <seb128> I hopped the update would fix it :/
[15:32] <Laney> ya
[15:33] <Laney> I thought the update was buggy but the archive version is the same
[15:36] <seb128> you can look to .cache/upstart/legacy...<appname>...log
[15:36] <seb128> it might have errors
[15:38] <Laney> http://paste.ubuntu.com/9490515/
[15:39] <seb128> Laney, dunno about that sorry :/
[15:39] <seb128> no error there I can see
[15:39] <Laney> http://paste.ubuntu.com/9490532/ 3.12
[15:39] <Laney> seems basically the same
[15:42] <seb128> yeah
[15:42] <seb128> could be a change in mir that bugged it
[15:42] <seb128> hum
[15:48] <seb128> Trevinho, that libcanberra commit, how does it work? it's a build time thing and we build our libcanberra with gtk/x11 no?
[15:48] <Trevinho> seb128: no, it's a runtime check
[15:49] <seb128> Trevinho, shrug, ignore me, I though you added the ifdef
[15:49] <seb128> but that also adds the if (!GDK_IS_X11_DISPLAY(d)) call in it ;-)
[15:50] <Trevinho> seb128: also... I've branches for cogl and clutter for mir support that I'll push to master branches soon... So, it would be nice to package them... :P
[15:50] <seb128> Trevinho, when is that segfault happening? I didn't see it on unity8 sessions so far
[15:50] <seb128> Trevinho, great
[15:50] <Trevinho> seb128: but while for clutter I don't see problems in having releases, cogl people seems not to want to release soon
[15:50] <seb128> Trevinho, do you have any idea about current gtk nor working on unity8 in vivid?
[15:50] <Trevinho> seb128: well, running the gnoem tetris game,,
[15:50] <seb128> it gives a blank surface
[15:51] <Trevinho> seb128: ooops, no.. I'm latest mir + latest gdk, but not in vivid
[15:51] <seb128> k
[15:51] <Trevinho> (and they work)
[15:51] <seb128> we are not likely to get 3.16 this cycle
[15:51] <seb128> so we need to backport fixes to the stable version
[15:52] <Trevinho> seb128: well, a part from the gdkgl work, the rest should stay I guess
[15:52] <seb128> yeah
[15:53] <Trevinho> and.... gdkgl stuff got recently broken by an upstream change... that weirdly breaks us... but it looks mostly a mesa/mir issue
[15:55] <Trevinho> seb128: ah, i thought I had replied to you, but it doesn't seem the case... so the crash was happening to me when running the gnome tetris game (that uses clutter, and canberra) with mir
[15:56] <seb128> Trevinho, oh, makes sense, I've added the lp: # reference to the changelog and uploaded your change, thanks ;-)
[15:56] <Trevinho> seb128: np
[16:01] <seb128> Laney, https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1353362/comments/11 ... was that comment about the cairo merge or about the specific issue described before?
[16:02] <Laney> seb128: probably related to feature freeze
[16:03] <attente_> seb128: hey, can you help me with https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1307657?
[16:03] <seb128> didrocks, I've the feeling you skipped over your piloting shift this week, want to look at that merge ^ next week? would be good for your karma around here :-)
[16:03] <seb128> attente_, hey, help how? to land it?
[16:03] <attente_> yeah
[16:04] <seb128> is the UBUNTU_MENUPROXY env not useful anymore?
[16:04] <seb128> in any case, not sure I'm going to get to it today
[16:04] <seb128> I'm on holidays starting in ~1.5 hours and still training to clean up backlog before that
[16:04] <Laney> seb128: http://irclogs.ubuntu.com/2014/09/15/#ubuntu-desktop.html#t15:55
[16:04] <seb128> but maybe Laney can look at landing that one next week?
[16:05] <seb128> Laney, thanks
[16:05] <attente_> oh ok
[16:05] <seb128> attente_, since you are around, question for you!
[16:05] <seb128> attente_, do you know what's going on with gtk apps under unity8 in vivid? they don't work anymore
[16:06] <seb128> they show a black surface only
[16:06] <seb128> I guess something changed on the mir side, but do you know if there is an update/fix/bug for GTK?
[16:06] <seb128> that's using gtk from vivid on the stable update larsu is working on/we have in the vcs
[16:09] <attente_> oh, no clue, everything seems fine under the demo shell
[16:09] <seb128> hum
[16:10] <seb128> greyback, ^ do you know maybe?
[16:10] <greyback> seb128: am sorry to say I've no idea, I've not tried gtk apps with unity8 yet
[16:11] <greyback> but if it works with demo shell, we must have broken something iin unity8
[16:11] <greyback> please log bug against qtmir
[16:12] <seb128> ok
[16:12] <seb128> it worked some weeks ago
[16:13] <greyback> nothing relevant changed in qtmir in some time, so not sure
[16:13] <seb128> greyback, logs look like http://paste.ubuntu.com/9490515/
[16:13] <seb128> from an app starting
[16:13] <seb128> we can see a surface displaying for like a second, without content and then back to the dash
[16:13] <greyback> so it crashes?
[16:14] <seb128> not sure, no apport file
[16:14] <greyback> or it is running, you just see dash
[16:14] <seb128> let me try
[16:14] <greyback> the surface you see for a second, it's definitely not the splash screen
[16:15] <greyback> also, I think u8 has a bug, where dash is always undereneath the app. So if app surface transparent, you see just dash
[16:15] <Laney> attente_: lemme upload that now using train
[16:16] <attente_> Laney: wait, sorry, i was trying to debug something wrong with the tests failing
[16:16] <Laney> hmm?
[16:17] <attente_> Laney: were you talking about https://code.launchpad.net/~attente/gtk/refresh-mir-backend/+merge/244491? i need to fix the tests failing on it
[16:17] <Laney> nein, unity-gtk-module
[16:17] <didrocks> seb128: sure, opened and adding this tab
[16:17] <attente_> oh, ok, thanks
[16:18] <seb128> didrocks, thanks
[16:18] <didrocks> seb128: speaking of skipping, do you think you will have some time to look at jayatana or not?
[16:18] <didrocks> just to know if I should start finding other victims :)
[16:18] <didrocks> (don't want to rush you before your holidays)
[16:18] <seb128> didrocks, sorry, got carried away on other things, let me have a look now
[16:19] <didrocks> thanks
[16:19]  * didrocks is fighing with git-dpm
[16:20] <Laney> poor dpm
[16:20] <didrocks> fighting*
[16:20] <didrocks> Laney: it isn't nice to me :p
[16:22] <didrocks> or maybe it has some magic on git show?
[16:22] <seb128> greyback, ok, the gtk apps are transparent, it's visible in windows mode :p
[16:22]  * didrocks doesn't see his patch in debian/patches, but like if the changes were applied inline
[16:23] <seb128> greyback, that's the unity8.log in case it's useful, http://paste.ubuntu.com/9491030/
[16:23] <didrocks> yeah, it seems it's the case
[16:23] <didrocks> Laney: do you know about git-dpm?
[16:24] <Laney> no never used it i'm afraid
[16:24] <didrocks> it's like magic, git history doesn't mention the debian/patches that has been added
[16:24] <didrocks> directly show the inline changes
[16:24] <greyback> seb128: ok, I don't see anything suspicious there, must be a rendering issue. I'll need a bug with instructions on how to repro
[16:25] <seb128> greyback, ok, easy "install a gtk app, gedit will do, add X-Ubuntu-Touch=true to its .desktop, log into unity8 session, click on gedit in the dash"
[16:25] <seb128> greyback, putting that in a bug report
[16:27] <seb128> greyback, https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1401968
[16:28] <greyback> seb128: ah ok, it isn't hard.  I thought I needed to compile branches
[16:28] <seb128> :-)
[16:29] <greyback> thanks for that
[16:29] <greyback> I'll look into it next week
[16:29] <seb128> thanks
[16:29] <willcooke> soooooo sweet.  Open a youtube video in the browser and move the window around with no frames getting dropped in U8
[16:31] <Laney> it's creepy when someone highlights your cells on a spreadsheet
[16:31]  * Laney eyes ogra_ 
[16:32] <ogra_> heh
[16:43] <seb128> didrocks, NEWed
[16:46] <didrocks> seb128: thanks!
[16:56] <Laney> attente_: ppa:ci-train-ppa-service/landing-001 want to give it a quick spin before upload?
[16:57] <attente_> sure
[17:01] <attente_> Laney: i don't see it there
[17:03] <Laney> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-001/+packages ?
[17:12] <attente_> Laney: looks good
[17:12] <Laney> ty
[17:15] <seb128> Laney, https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1401968 about the gtk not working under unity8, downgrading qtmir fixes it so it suggests an issue there
[17:16] <Laney> seb128: nice find
[17:16] <seb128> Laney, thanks ;-)
[17:17] <Laney> maybe we could get some CI up for this
[17:22] <seb128> yeah, we should
[17:22] <seb128> well we should also have some to make sure the unity8 desktop session starts
[17:22] <seb128> we had instance of that not working anymore as well
[17:31] <willcooke> I emailed ev about CI last week
[17:32] <willcooke> problem is U8 desktop doesnt visualise well atm
[17:32] <Laney> virtualise?
[17:33] <willcooke> ya
[17:33] <willcooke> that's a perfectly cromulant word
[17:33] <willcooke> it doesnt run well in a VM
[17:33] <Laney> you said visualise, was checking
[17:33] <willcooke> oh
[17:33] <willcooke> so
[17:33] <willcooke> I did
[17:34] <willcooke> :)
[17:34] <willcooke> I blame flu
[17:34] <Laney> well maybe if that's the case some real hardware could be used
[18:07] <Laney> ok
[18:08] <Laney> happy weekend!
[18:08] <willcooke> l8r Laney
[18:08] <Laney> & happy holidays seb128 ;-)
[19:25] <seb128> Laney, thanks! to you too
[19:35] <willcooke> hrm suddenly cant ssh in to my u8 box
[20:00] <willcooke> mlankhorst, I lost your instructions for xmir.  I think they were in a pastepin which expired