[02:01] <mfisch> are we moving to 3.8 for trusty?
[02:36] <TheMuso`> mfisch: We are already on 3.8 for saucy...
[02:37] <TheMuso`> mfisch: Hrm I assume you mean GNOME> Parts are already 3.8.
[02:37] <mfisch> I wonder what packages I just was looking at
[02:43] <mfisch> oh I fail I mean 3.10
[02:43] <mfisch> TheMuso: ^^
[02:55] <TheMuso> mfisch: Then no. We have the odd piece of GNOME in saucy thats 3.10, but in general we are remaining on 3.8.
[03:39] <pitti> Good morning
[08:05] <Laney> hellooooo
[08:06] <pitti> good morning Laney!
[08:06] <Laney> hey pitti
[08:30] <Sweetshark> Moin!
[08:33] <abhishek__> helloi all
[08:38] <abhishek__> I have development board with Android preloaded on it
[08:38] <abhishek__> I want to run the Ubuntu desktop version on it
[08:38] <abhishek__> What I am supposed to perform?
[08:39] <abhishek__> Can someone please suggest me?
[08:47] <Laney> darkxst: know of any reason to not include rhythmbox 3?
[08:48] <darkxst> Laney, hi
[08:48] <Laney> hey darkxst
[08:48] <Laney> how goes?
[08:49] <darkxst> havent got around to looking at it as yet, but should work fine with 3.8
[08:49] <Laney> seems fine to me
[08:49] <Laney> I have a niggle that someone told me of a bug with it though, but annoyingly can't remember what that was
[08:49] <darkxst> of course it has a bug!
[08:50] <Laney> it was like "should we take this?" "hmm, there was XXX"
[08:50] <abhishek__> I have development board with Android preloaded on it. I want to run the Ubuntu desktop version on it. What steps I need to perform?
[08:51] <Laney> abhishek__: Not sure you'll be able to do that without proper drivers
[08:51] <Laney> try asking in #ubuntu-arm
[08:51] <abhishek__> Please suggest me
[08:51] <abhishek__> ok
[08:52] <darkxst> Laney, well I still have tried it, so no idea...
[08:52] <darkxst> haven't
[08:53] <Laney> ah ok
[08:53] <Laney> will look and if I can't find it, well... :-)
[08:54] <abhishek__> Laney: can you please tell me 1 thing
[08:55] <abhishek__> Laney: I have Android source available for my board.
[08:56] <Laney> darkxst: ah I found it, was just some concern with non-py3 plugins
[08:56] <abhishek__> Laney: I am supposed to change the fastboot to bootloader to boot the Ubuntu
[09:06] <darkxst> Laney, that should not be a big concern?
[09:06] <Laney> nah
[09:06] <Laney> I already fixed the u1ms one and pinged the maintainer of ampache about that
[09:13] <darkxst> Laney, what are the chances of updating cogl/clutter?
[09:13] <Laney> is it a transition?
[09:14] <darkxst> yeh, lots of rdepends on clutter
[09:14] <Laney> well, if someone checks it and everything works then it should be fine
[09:14] <Laney> stage it in a PPA or something
[09:17] <darkxst> Laney, ok will do
[10:07] <Laney> rb uploaded
[10:20] <vila> mlankhorst: ping, on trusty, I get a gnome-session crash on a AMD Radeon HD7750 blocking automated tests in ci, what's the best way to get this fixed ?
[10:30] <Laney> dobey: do you have a packaging branch for rb-u1?
[10:31] <Laney> oh for bzr format-patch
[10:42] <mlankhorst> vila: oh really? I thought I uploaded mesa 9.2.2 there
[10:43] <mlankhorst> vila: hm it's there, so I'm going to need more information first..
[10:47] <vila> mlankhorst: ask and you should receive ;)
[10:49] <vila> mlankhorst: which package should I check for ?
[10:50] <vila> mlankhorst: not sure which driver we use to start with :-/
[10:51] <vila> mlankhorst: the machine was running raring and was updated to trusty recently (obviously)
[10:51] <mlankhorst> mesa should be version 9.2.2ubuntu1
[10:51] <mlankhorst> well first try if normal opengl works, and what crashes?
[10:52] <vila> apt-cache policy mesa-common-dev
[10:52] <vila> mesa-common-dev:
[10:52] <vila>   Installed: (none)
[10:52] <vila>   Candidate: 9.2.2-1ubuntu1
[10:52] <vila> no package named mesa
[10:58] <vila> mlankhorst: ^
[11:12] <mlankhorst> libgl1-mesa-dri ?
[11:15] <vila> mlankhorst: same
[11:28] <mlankhorst> vila: not installed?
[11:29] <mlankhorst> vila: anyway what is the problem
[11:29] <mlankhorst> I mean crash is pretty broad
[11:29] <vila> mlankhorst: during an autopilot test the gnome-session is crashing
[11:30] <vila> mlankhorst: this is on a machine in the ci lab that has been upgraded recently from raring. It's one among others, I can access to it both via ssh and through a kvm
[11:32] <vila> mlankhorst: so I can check anything you want or install anything that is needed but I need a bit of help :)
[11:34] <vila> mlankhorst:  as usual it's a bit urgent as many people are blocked by these failures ;)
[11:35] <mlankhorst> what makes you say it's a xorg bug, and not anything?
[11:35] <mlankhorst> else
[11:36] <vila> mlankhorst: it works on other machines, only the radeon one is failing
[11:36] <vila> mlankhorst: so that's where we're starting to investigate and didrocks pointed me at you
[11:38] <vila> mlankhorst: http://10.97.0.1:8080/job/otto-test-radeon/label=qa-radeon-7750/lastSuccessfulBuild/artifact/results/logs/gnome-session.log
[11:39] <vila> mlankhorst: the above contains gnome-session[5989]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
[11:39] <vila> mlankhorst: and thry the kvm, during the test failures, the session crashes and comes back to the lightdm prompt
[11:40] <vila> *thru
[11:41] <vila> mlankhorst: so, first thing, how to I find which driver is involved ? What are the alternatives (free/proprietary) and which package can I check to find that ?
[11:47] <mlankhorst> oh
[11:47] <mlankhorst> so Xorg is crashing
[11:48] <mlankhorst> probably
[11:48] <mlankhorst> anything in Xorg.0.log ?
[11:55] <vila> mlankhorst: well, things, but the .log and .log.old are from succesful uses :-/
[11:55] <vila> mlankhorst: and the test run didn't collect X.org.o.log :-(
[11:57] <vila> mlankhorst: can we start by identifying which driver is used and make sure my install is correct ? I'm starting to suspect some upgrade issue or some missing part (3D for example)
[11:57] <mlankhorst> that would be obtained from Xorg.0.log..
[12:03] <vila> mlankhorst: http://paste.ubuntu.com/6294522/
[12:03] <vila> mlankhorst: didn't have copy/paste through kvm, had to find a way to access the lxc container content through ssh
[12:04] <vila> mlankhorst: that's the current one so no crash but that should be enough to check the config right ?
[12:13] <Laney> ricotz: can you do a MP to drop the Posix stuff from fixes.vala in unity-greeter?
[12:14] <Laney> and I guess bump the valac version
[12:14] <Laney> It's defined in vala now
[12:14] <mlankhorst> vila: well no crash, I really don't know then :S what does the qa stuff do?
[12:14] <mlankhorst> can you reproduce the crash manually?
[12:15] <vila> mlankhorst: yeah, no crash in that file, said so above, pasted to check the config so you can tell me which package I need to check ;)
[12:16] <vila> mlankhorst: I'm looking into collecting the crashed versions in the mean time
[12:16] <mlankhorst> I honestly don't know
[12:16] <mlankhorst> my psychic debugging skills are lacking :/
[12:19] <ricotz> Laney, those "binding fixes" should have been guarded in the first place or put in another namespace
[12:19] <Laney> If you want to do that then feel free
[12:19] <ricotz> Laney, i am not really comfortable touch unity stuff anyway
[12:19] <Laney> why?
[12:20] <ricotz> dont ask ;)
[12:20] <Laney> You'll do a merge proposal and it will be reviewed
[12:20] <Laney> shouldn't be risky
[12:20] <Laney> unless you mean CLA stuff ...
[12:22] <ricotz> Laney, i didnt sign those, so strictly i am not allowed to contribute
[12:23] <Laney> okay, I'll do that one
[12:23] <Laney> bit unfortunate if you can't fix your broken stuff though
[12:23] <ricotz> Laney, just put "#if !VALA_0_22 ... #endif" around the parts
[12:23] <ricotz> what?
[12:24] <Laney> oh cool I didn't know about that define
[12:25] <ricotz> why is it *my* broken stuff?
[12:25] <Laney> stuff broken by your change
[12:25] <Laney> anyway, it's quite reasonable if you don't want to sign it
[12:25] <ricotz> this is more like a programmers error in the first place!
[12:26] <ricotz> it should be put in the different namespace to avoid collisions
[12:28] <Laney> yeah, but sometimes the bugs of others are only exposed later on
[12:28]  * Laney tests this
[12:30] <Laney> wtf
[12:30] <Laney> it dies in the testsuite
[12:35] <Laney> oh now it works
[12:35] <Laney> must be slightly flaky
[12:35] <mlankhorst> vila: but i should have access to the qalab, what machine is it so I can poke it a bit in 30 minutes or so?
[12:37] <vila> mlankhorst: qa-radeon-7750 but you'll need to go into the container, ping me when you're ready, I may have an relevant Xorg.0.log then
[12:40] <Laney> ricotz: synced vala-0.22
[12:44] <ricotz> Laney, thank you
[12:48] <vila> mlankhorst: captured on the fly: http://paste.ubuntu.com/6294696/
[12:58] <dobey> Laney: no, rb-u1 doesn't use "vcs-bzr"
[12:58] <darkxst> seb128, attached patch to bug #1232419
[12:58] <ubot2> Launchpad bug 1232419 in gnome-settings-daemon (Ubuntu) "[xsettings]: gnome-settings-daemon crashed with SIGSEGV in notify_have_shell()" [High,Confirmed] https://launchpad.net/bugs/1232419
[12:59] <darkxst> no way to test here, but hoping that helps
[12:59] <dobey> Laney: i just use the imported branch in launchpad when i do uploads
[13:00] <darkxst> seb128, that said, I'm off to bed, probably catch you in the morning
[13:05] <seb128> darkxst, hey, k, I can have a look today, thanks for working on it!
[13:07] <mlankhorst> vila: yeah some glamor bug then :/
[13:08] <vila> mlankhorst: what's the course of action from there ?
[13:08] <mlankhorst> reducing to a simple testcase
[13:09] <mlankhorst> or just installing all xserver.*-dbg packages and run it on valgrind
[13:09] <vila> mlankhorst: that's already an automated test suite
[13:10] <vila> mlankhorst: you'll have to elaborate that '*' ;) I still have no idea what packages are involved, see backlog ;)
[13:10] <mlankhorst> vila: yeah but something triggers it, have to figure out what exactly
[13:10] <mlankhorst> apt-get install xserver-.*-dbg
[13:10] <mlankhorst> and apt-get install valgrind, then start x in valgrind and run the test on it manually
[13:12] <vila> hmm, that's a lot of packages :-/ I'll need to be able to revert that later...
[13:13] <mlankhorst> they're harmless, it only contains some debug info to make valgrind logs easier to understand
[13:16] <vila> mlankhorst: packages installed
[13:16] <vila> mlankhorst: how do I start x in valgrind ?
[13:18] <vila> mlankhorst: tell me it's an option in some config file, that's inside a container and will be already tricky
[13:18] <mlankhorst> valgrind --track-origins=yes --error-limit=no /usr/bin/Xorg :0
[13:18] <mlankhorst> export DISPLAY=:0 and run the test that crashes
[13:18] <vila> ghaa, that's a no go, we need to find a way to do that outside of the container :-(
[13:19] <mlankhorst> :/
[13:20] <vila> mlankhorst: wait, let's try something simpler, go to the lab and try to start/stop x as you see fit, I'll try to find the autopilot command you need to run
[13:21] <mlankhorst> hm lets see
[13:25] <seb128> larsu, https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1201947
[13:25] <ubot2> Launchpad bug 1201947 in indicator-appmenu (Ubuntu) "unity-panel-service crashed with signal 5 in g_type_create_instance()" [Medium,Confirmed]
[13:33] <mlankhorst> vila: hm why does it say unknown job lightdm? :P
[13:38] <mlankhorst> oh the host part probably didn't have it, no wonder..
[13:38] <vila> mlankhorst: yeah, part of why I want to simplify to the point where you can work outside of the container
[13:39] <vila> mlankhorst: we've already out the machine in a state where it will probably be easier to re-installl from scratch than making sure we revert all your work when you're done
[13:40] <mlankhorst> hm probably
[13:40] <mlankhorst> vila: so how do I run the tests?
[13:43] <mlankhorst> or well, at what point do the tests fail and crash the xserver?
[13:48] <vila> mlankhorst: sorry, I have to attend a meeting right now, you can try to join #ubuntu-ci-eng to get that question answered, I'll be back asap
[13:54] <mlankhorst> vila: ok I've uploaded an updated glamor-egl snapshot to ppa:canonical-x/x-staging, should try wth that first, bbiab myself
[13:54] <vila> mlankhorst: ack
[13:59]  * Laney looks at the cmake branch again
[14:00] <seb128> sil2100, cyphermox, didrocks: can we get http://bazaar.launchpad.net/~indicator-applet-developers/hud/trunk.13.10/revision/341 SRUed? it's the most reported e.u.c saucy issue
[14:00] <cyphermox> aye
[14:00] <seb128> thanks
[14:01] <sil2100> Ok
[14:01] <sil2100> I guess cyphermox is on it then :)
[14:01] <seb128> cyphermox, 340 with it would be good as well
[14:01] <seb128> cyphermox, I can file the SRU infos on those bugs if you want
[14:01] <cyphermox> yeah I was just checking that
[14:01] <didrocks> thanks cyphermox ;)
[14:01] <didrocks> and seb128 :)
[14:01] <cyphermox> I'll write the SRU blob on the bug too
[14:01] <seb128> yw ;-)
[14:02] <seb128> cyphermox, thanks
[14:02] <seb128> cyphermox, the segfault one, just write "check e.u.c"
[14:02] <seb128> cyphermox, that's https://errors.ubuntu.com/problem/80ec348bd203ad9f5b91a956c463234dce72d2e7
[14:02] <cyphermox> alright
[14:02] <seb128> thanks
[14:06] <Ursinha> seb128, sorry bug 1201485 wasn't fixed in time for the release, there were a few complications none of us thought about until we actually tried to fix that
[14:06] <ubot2> Launchpad bug 1201485 in Ubuntu Translations "Need to import translations for the unity daily builds" [High,Triaged] https://launchpad.net/bugs/1201485
[14:06] <Ursinha> but should be QAed/in production rsn
[14:09] <seb128> Ursinha, no worry, we workarounded it by doing manual template update for 13.10
[14:10] <seb128> Ursinha, seems like it's going to be fixed soon though, which means no issue for the lts
[14:10] <seb128> Ursinha, which makes me very happy, thanks for fixing it! ;-))
[14:11] <Ursinha> seb128, no problem :)
[14:13] <Ursinha> seb128, latest required bits landed yesterday, wgrant did some QA that I'll continue today, should be in production soon
[14:14] <seb128> Ursinha, excellent, let me know when it's in production so I can check with the next upload/confirm that it's working
[14:14] <Ursinha> seb128, sure :)
[14:38] <Laney> seb128: any objections to merging the cmake branch now?
[14:39] <seb128> Laney, no, I didn't try it since tuesday but the I pinged the #sdk guys about how Jussi made the qml sources listed in qtcreator and they said it was the right way to do it
[14:39] <Laney> ok
[14:39] <Laney> seems to work now
[14:39] <seb128> great
[14:39] <seb128> let's get that in
[14:40] <seb128> Laney, I'm going to review your background branch today btw
[14:40] <Laney> neat
[14:40] <seb128> Laney, it would be nice if you reviewed attente's language one, you looked more at this code than me
[14:40] <Laney> yeah it's on the list
[14:40] <seb128> great
[14:57] <Laney> oh god it's merged
[14:57] <Laney> SCARY
[15:00] <seb128> haha
[15:02] <seb128> lunch time, bbl
[15:42] <vila> mlankhorst: I'm back
[15:44] <vila> mlankhorst: I have installed the packages for the tests and I think I have the right command, now we need to server started as you need and find some required env vars (I think I can find them once the gnome session is started)
[15:45] <mlankhorst> vila: ok can you test with glamor-egl first from the ppa, to check if it still crashes?
[15:45] <vila> mlankhorst: which ppa again ?
[15:46] <mlankhorst> ppa:canonical-x/x-staging
[15:46] <vila> xserver-xorg-glamoregl ?
[15:47] <vila> mlankhorst: ^
[15:47] <mlankhorst> yeah
[15:47] <mlankhorst> and the other debs
[15:48] <vila> mlankhorst: but wait, if you made changes to the config, I'd rather reproduce on the host than re-running the container that may not like your tweaks
[15:48] <mlankhorst> oh I didn't touch the config yet
[15:48] <vila> not even /etc/X11/X ? (Yeah, the kvm was still on, didn't follow closely what you did though ;)
[15:48] <vila> mlankhorst: ^
[15:49] <mlankhorst> no that was a test, but it just tries to run valgrind
[15:50] <mlankhorst> script is called /etc/X11/X2, and /etc/X11/X may be pointing to it as symlink, it's just a script I use from home lol
[15:50] <mlankhorst> I don't think I made it point to it, though
[15:51] <vila> mlankhorst: well, X -> X2 currently
[15:52] <mlankhorst> oh in that case make X2 executable and it should work, /var/log/xorg.log contains valgrind logs
[15:52] <mlankhorst> but meh dno if it runs it in the chroot
[15:52] <vila> mlankhorst: right, that's exactly the kind of issue I want to avoid
[15:52] <mlankhorst> well in that case it will fail to start
[15:52] <mlankhorst> :P
[15:53] <vila> mlankhorst: ha ha
[15:53] <mlankhorst> else just remove xserver-xorg and remove /etc/X11/X
[15:54] <vila> mlankhorst: look, I've setup the host so you can test, the server will need to be reinstalled from scratch when we're done so can we just go ahead ?
[15:54] <mlankhorst> ok try it :)
[15:55] <vila> mlankhorst: try what ? there is no lightdm running
[15:55] <vila> mlankhorst: the kvm shows your console right now
[15:55] <mlankhorst> the valgrind incantation is "valgrind --error-limit=no --track-origins=yes  --malloc-fill=ef --free-fill=df /usr/bin/Xorg :0 -core -verbose 10 2>&1 | tee /var/log/xorg.log"
[15:55] <mlankhorst> oh I'm not logged in
[15:56] <vila> mlankhorst: I'm not sure we're on the same page :)
[15:56] <mlankhorst> neither
[15:57] <mlankhorst> anyway try to start xorg-server with that invocation, then do export DISPLAY=:0 and crash xserver, log should be in stdout and /var/log/xorg.log
[15:57] <vila> mlankhorst: could please log in and start whatever you need in a way that will give you the bits you need, once you're there, I'll debug the command needed to run the test to break the server
[15:57] <mlankhorst> ok
[15:58] <mlankhorst> I'll just spawn an Xserver then
[15:58] <mlankhorst> export DISPLAY=:0 and go ahead and crash it
[15:59] <vila> mlankhorst: I think autopilot requires a gnome-session
[15:59] <didrocks> ou need to have the dbus env var at least
[15:59] <vila> didrocks: but the X server won't be enough for that right ?
[16:00] <vila> didrocks: do you remember the trick to set dbus enva var, I remember it's under some file under ~/.something but details are fuzzy
[16:00] <didrocks> vila: it's better to export all env var from gnome-session to be certain we don't miss anything
[16:00] <mlankhorst> didrocks: hm how do I start a full ubuntu session from the command line?
[16:01] <vila> lightdm should be enough I can connect from kvm
[16:01] <didrocks> mlankhorst: not really sure, as you installed lightdm I guess kvm is the easiest way to get them
[16:01] <vila> as long as the X server is configured the way you need it
[16:02] <mlankhorst> yeah
[16:02] <vila> didrocks: and you know how to export all those env vars ?
[16:02] <didrocks> vila: export FOO=bar ?
[16:03] <vila> didrocks: he he
[16:03] <vila> didrocks: thanks I needed a laugh ;)
[16:03] <vila> didrocks: I meant I know they are defined somewhere
[16:03] <didrocks> vila: cat /proc/`pidof gnome-session`/environ
[16:03] <didrocks> as you need gnome-session env var :)
[16:03] <vila> didrocks: rock&roll
[16:05] <vila> ha, installing lightdm
[16:05] <vila> didrocks: still slightly simpler than from the container but we're getting close ;-/
[16:05] <vila> didrocks: and yes, I've added the unity-daily ppa
[16:06] <mlankhorst> I guess setting export DESKTOP_SESSION=ubuntu then running bash /etc/X11/Xsession
[16:07] <vila> or just service lightdm start ?
[16:08] <mlankhorst> hm this bug again? eep
[16:08] <vila> mlankhorst: it's installed
[16:08] <vila> mlankhorst: what bug ?
[16:08] <mlankhorst> AIGLX: Suspending AIGLX clients for VT switch repeatedly infinitely
[16:08] <mlankhorst> oh well thing crashed
[16:08] <vila> mlankhorst: ignore that for now
[16:08] <vila> lightdm is now installed
[16:10] <mlankhorst> no that caused it to crash here, but probably not the one you were hitting
[16:10] <mlankhorst> lets try again
[16:10]  * vila nods
[16:11] <mlankhorst> I started xserver again
[16:11] <vila> mlankhorst: erm, lightdm, not x server, if your script is in place ligthdm should call it right ?
[16:13] <mlankhorst> yeah
[16:14] <mlankhorst> again that bug.. bah
[16:14] <vila> ok, I've got a prompt
[16:14] <vila> connecting as ubuntu
[16:14] <mlankhorst> ok it's not valgrind clean at least
[16:16] <vila> nothing happens
[16:16] <mlankhorst> as in no crash?
[16:16] <vila> doesn't look like lightdm
[16:16] <vila> no, the it took my password by stayed there
[16:17] <mlankhorst> well do you have ubuntu-desktop installed? I wonder if there's a session or not :P
[16:17]  * vila sighs
[16:17] <vila> no installing
[16:18] <vila> mlankhorst: you stop lightdm
[16:18] <mlankhorst> yeah it's annoying as hell, I wonder if it's easier to just buy a 7750 online and try for myself
[16:18] <vila> *you can
[16:18] <mlankhorst> and then play around with it locally..
[16:19] <vila> mlankhorst: it's annoying for me as well :) I've been told it's urgent so I'm doing my best
[16:19] <mlankhorst> vila: if it isn't about open source drivers try fglrx
[16:20] <vila> mlankhorst: I'd rather not change at that point since we need to re-install the server from scratch, so better dig that one until we can reproduce
[16:20] <mlankhorst> if it is about open source drivers I can order a 7750 online and play with it on my own system and fix any bugs I find
[16:21] <mlankhorst> would that be acceptable?
[16:21] <vila> mlankhorst: that would delay the diagnosis even more, but feel free to ask in #ubuntu-ci-eng
[16:21] <mlankhorst> bbiab, food :/
[16:21] <vila> oh, it just displayed 'loggin in...' ;)
[16:21] <mlankhorst> it's technically EOD and EOW for me, but I'll look when I get back
[16:22] <vila> :-(
[16:22] <vila> mlankhorst: and no one else than you can help here right ?
[16:23] <vila> mlankhorst: installed
[16:23] <vila> service lightdm restart
[16:23] <vila> better looking
[16:24] <vila> logged in
[16:26] <vila> autopilot test running
[16:27] <vila> crash
[16:27] <vila> \o/
[16:28] <vila> err, well, that was the point...
[16:31] <ogra_> Sweetshark, oooh ! congrats Mr. Director !
[16:32] <Sweetshark> ogra_: thanks!
[16:34] <Laney> O RLY
[16:34] <Sweetshark> ogra_: btw -- same time on the Ubuntu project, still no package uploader rights for LibreOffice ;P
[16:34] <ogra_> oh man
[16:35] <Sweetshark> ogra_: no worries, I stopped being angry about that a looong time ago.
[16:40] <mlankhorst> vila: oh free memory after all..
[16:41] <mlankhorst> vila: http://paste.debian.net/61284/
[16:41] <mlankhorst> no idea yet what triggers it though
[16:42] <vila> mlankhorst: reducing the reproducing recipe, gimme a sec
[16:44] <vila> reproduced twice, so far so good
[16:44] <mlankhorst> boom
[16:47] <vila> mlankhorst: so, you know how to connect to the kvm right ?
[16:47] <vila> mlankhorst: for visual feedback
[16:47] <mlankhorst> vila: I just need the minimal testcase, I'll try to reproduce it with glamor locally after you have that :)
[16:48] <vila> mlankhorst: the ubuntu user will autologin when lightdm restart
[16:48] <mlankhorst> boom
[16:48] <vila> mlankhorst: so from your shell, connected as ubuntu:
[16:48] <vila> sudo service lightdm restart
[16:48] <vila> and when it's up
[16:48] <vila> autopilot run -v autopilot.tests.functional
[16:49] <mlankhorst> is that one publicly somewhere?
[16:49] <vila> mlankhorst: what one ? ;)
[16:50] <mlankhorst> vila: the crashing one
[16:50] <vila> I don't get it :-/
[16:50] <mlankhorst> vila: autopilot crashes right?
[16:51] <vila> well, autopilot triggers a crash in X, apart from you and me not sure who knows about that (apart from #ubuntu-ci-eng that is)
[16:53] <vila> mlankhorst: are you talking about the autopilot code ? tests ? It should be the trunk versions
[16:53] <mlankhorst> vila: what I mean is can I download those autopilot tests and run them on a machine I have at home?
[16:53] <mlankhorst> ideally precompiled
[16:54] <vila> apt-cache policy on that machine will tell you all :) : ubuntu@qa-radeon-7750:~$ apt-cache policy python-autopilot
[16:54] <vila> python-autopilot:
[16:54] <vila>   Installed: 1.4+14.04.20131024.1-0ubuntu1
[16:54] <vila>   Candidate: 1.4+14.04.20131024.1-0ubuntu1
[16:54] <vila>   Version table:
[16:54] <vila>  *** 1.4+14.04.20131024.1-0ubuntu1 0
[16:54] <vila>         500 http://ppa.launchpad.net/ubuntu-unity/daily-build/ubuntu/ trusty/main i386 Packages
[16:54] <vila>         100 /var/lib/dpkg/status
[16:54] <vila>      1.3.1+13.10.20131003.1-0ubuntu1 0
[16:54] <vila>         500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages
[16:54] <mlankhorst> oh it's python-autopilot
[16:54] <vila> the code yes
[16:55] <vila> ubuntu@qa-radeon-7750:~$ apt-cache policy python-autopilot-tests
[16:55] <vila> python-autopilot-tests:
[16:55] <vila>   Installed: 1.4+14.04.20131024.1-0ubuntu1
[16:55] <vila>   Candidate: 1.4+14.04.20131024.1-0ubuntu1
[16:55] <vila>   Version table:
[16:55] <vila>  *** 1.4+14.04.20131024.1-0ubuntu1 0
[16:55] <vila>         500 http://ppa.launchpad.net/ubuntu-unity/daily-build/ubuntu/ trusty/main i386 Packages
[16:55] <vila>         100 /var/lib/dpkg/status
[16:55] <vila>      1.3.1+13.10.20131003.1-0ubuntu1 0
[16:55] <vila>         500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages
[17:01]  * didrocks waves good evening
[17:01] <mlankhorst> ok lets see..
[17:03] <mlankhorst> vila: thanks, I can crash it locally now with that autopilot invocation
[17:04] <vila> mlankhorst: same crash ? Sure ?
[17:04] <mlankhorst> yeah had same error
[17:05] <vila> mlankhorst: so you don't need the lab machine anymore ?
[17:05] <mlankhorst> I used my ati 5570 and forced glamor acceleration
[17:05] <mlankhorst> indeed
[17:05] <mlankhorst> but that's about as much as I can do for now
[17:05] <vila> mlankhorst: ack, can you file the bug and subscribe me ?
[17:06] <vila> mlankhorst: I wouldn't even now against which project to do that ;)
[17:06] <vila> *know
[17:09] <mlankhorst> https://bugs.launchpad.net/ubuntu/+source/glamor-egl/+bug/1244324
[17:09] <ubot2> Launchpad bug 1244324 in glamor-egl (Ubuntu) "glamor-egl crashes when running autopilot tests" [High,Triaged]
[17:09] <mlankhorst> g2g
[17:09] <mlankhorst> EOD, EOW, will probably fix it first thing monday
[17:09] <vila> mlankhorst: thanks ! enjoy your we and thanks for your efforts !
[17:45] <seb128> charles: can you have a look to https://code.launchpad.net/~laney/ubuntu-system-settings/fix-linkage/+merge/192543 ? The changes make sense to me, but you are the one who wrote that code so it would be nice if you could confirm that's correct
[19:16] <GunnarHj> attente: Hi Will, I just posted a comment on bug 1240058. Please read it before doing anything.
[19:16] <ubot2> Launchpad bug 1240058 in ubuntu-system-settings (Ubuntu) "UI uses chinese, french and english simultaneously" [Medium,Confirmed] https://launchpad.net/bugs/1240058
[19:21] <attente> GunnarHj, thanks for the notice
[19:22] <attente> GunnarHj, is there a way for us to not hack accountsservice and force the priority list to never be longer than two locales?
[19:23] <attente> or is this actually the ideal behaviour we want on the device?
[19:30] <GunnarHj> attente: Given the design of language-selector, it's my belief that the current behavior is the best for now. I'm aware of the fact that g-c-c does not include a GUI for setting fallback languages, so it's possible that we should make some kind of adjustment when language-selector is dropped in Ubuntu. But we need to take Xubuntu and Lubuntu into account when doing so. And I don't think that this bug report is a valid reas
[19:30] <GunnarHj> on to change anything.
[19:32] <attente> ok, thanks GunnarHj
[19:32] <GunnarHj> attente: yw
[20:57] <attente> bregma, hi
[20:57] <bregma> howdy
[20:57] <attente> i'm trying to figure out where in the unity codebase the ShowEntry dbus method is invoked
[20:58] <attente> my guess was that it was being triggered by the keyboard shortcut identified by UNITYSHELL_OPTION_PANEL_FIRST_MENU
[20:58] <bregma> it's in unity-panel-service, I believe
[20:59] <bregma> services/panel-main.c
[20:59] <bregma> or do you mean where it's called?
[20:59] <attente> unity-panel-service provides the method, but i'm not sure who is calling it
[20:59] <attente> yes
[20:59] <bregma> UnityCore/DBusIndicators.cpp
[21:00] <bregma> which is part of the Panel
[21:01] <attente> do you know how the shortcut for UNITYSHELL_OPTION_PANEL_FIRST_MENU gets triggered?
[21:02] <bregma> is that what you get when you hit the 'menu' key?
[21:02] <attente> yes, the menu key being alt-f10
[21:04] <attente> unity i assume makes some keyboard grab through compiz in order to catch that shortcut?
[21:05] <bregma> I can only imagine there is some horrid path winding through Compiz then half od Unity before some signal is queue to be executed at idle time ...  unfortunately Trevinho is more the expert on this, he's out until Monday
[21:05] <bregma> I don;t think it;s a grab, just responing to the event
[21:12] <attente> ok, thanks bregma
[22:08] <GunnarHj> attente: still there?
[22:09] <attente> GunnarHj, hi
[22:10] <GunnarHj> attente: I'm slowly starting to realize that Ubuntu Touch may have separate needs. Is accountsservice used as is in Ubuntu Touch?
[22:11] <attente> GunnarHj, yes, we don't modify it at all
[22:11] <attente> i'm not sure about other panels that might be using it, but for the language settings, we set the language and formats locale through it
[22:12] <GunnarHj> attente: In that case, I suppose it would be motivated to make language-tools in a-s only set one language in LANGUAGE.
[22:13] <charles> Laney: thanks for https://code.launchpad.net/~laney/ubuntu-system-settings/fix-linkage/+merge/192543
[22:13] <GunnarHj> attente: Do you know how to best identify Ubuntu Touch?
[22:14] <GunnarHj> attente: XDG_CURRENT_DESKTOP?
[22:14] <attente> GunnarHj, i'm not sure
[22:16] <attente> GunnarHj, sorry, i have to go now, can you make a comment on the bug?
[22:17] <GunnarHj> attente: Will do.
[22:17] <attente> but i'm not sure if it's a good idea to make a hack to behave different between desktop and phone
[22:17] <attente> GunnarHj, thanks
[22:17] <GunnarHj> attente: Let's talk about it on the bug.