[03:28] <robert_ancell> bye all
[04:36] <hikiko> hello
[04:54] <didrocks> good morning
[05:42] <pitti> Good morning
[05:44] <didrocks> hey pitti , how are you?
[05:44] <pitti> didrocks: j'ai me levé trop tôt, mais bien ! et toi ?
[05:47] <didrocks> pitti: pareil, Julie prenait le train, donc levé tôt :p
[05:47] <didrocks> mais ça va
[05:48] <pitti> didrocks: je vais rentrer cet après-matin, Netti et moi nous recontrer à Munich
[05:49] <didrocks> pitti: tu dois être content ! :)
[05:49] <didrocks> pitti: my mission today, is to work on getting coverage a little bit upper again: https://jenkins.qa.ubuntu.com/job/udtc-trusty-tests-collect/1924/label=ps-trusty-desktop-amd64-1/artifact/html-coverage/index.html
[05:52] <pitti> didrocks: wow, that already looks amazing!
[05:52] <didrocks> pitti: I'm sure I can push it up :)
[05:52] <pitti> didrocks: I found that anything > 90% quickly falls into the "diminishing returns" category as these are usually weird error handling paths which are ridiculously hard to simulate
[05:53] <didrocks> pitti: yeah, I'm just doing the "easy ones", some leftover error conditions that are easy to get in unit tests
[05:53] <pitti> didrocks: oh, you have declarative exclusions?
[05:53] <pitti> didrocks: I didn't see those with python-coverage
[05:55] <didrocks> pitti: yeah, I needed those for the dpkg (from python-apt) subprocess
[05:55] <didrocks> can't trace those :)
[05:57] <didrocks> pitti: http://coverage.readthedocs.org/en/latest/excluding.html
[05:57] <pitti> didrocks: I mean, how do you declare that in python? to ignore a block for coverage I mean
[05:57] <pitti> didrocks: ah, merci !
[05:57] <pitti> # pragma: no cover
[05:57] <pitti> nice!
[05:57] <didrocks> yep :)
[05:57] <didrocks> then, you can add other comments
[05:58] <didrocks> like # pragram: no cover (in a fork)
[05:58] <didrocks> to explain a little bit why you exclude those
[05:59] <pitti> didrocks: so I suppose that's a pragmatic (haha) way to deal with weird error conditions
[06:00] <didrocks> pitti: nice pun! yeah, I didn't use it for that, but it's a good idea
[06:00] <didrocks> at least to stamp "I know I want to exclude this as it's a weird error conditions"
[06:00]  * pitti prends le petit-déjeuner, à bientôt !
[06:01] <pitti> didrocks: I found that otherwise I might be tempted to not check errors properly any more as it might ruin my coverage :)
[06:01] <didrocks> pitti: heh, indeed! bon appétit :)
[06:42] <pitti> seb128: bonjour !
[06:42] <pitti> seb128, Laney: voilà ! des nouvelles paquets de langue, avec evolution-3.16 :)
[06:53] <seb128> salut pitti, ça va ?
[06:53] <seb128> hey desktopers
[06:59] <seb128> pitti, Laney, evolution-3.16 was already in the langpacks from the 22 no?
[06:59] <pitti> seb128: ça va bien, merci !
[06:59] <seb128> pitti, did the new update restore the missing domains?
[07:00] <pitti> seb128: ah, c'est vrai, j'ai "diff" seulement les paquets *-base
[07:00] <pitti> seb128: it has eog at least, what else was missing?
[07:00] <seb128> pitti, file-roller gedit
[07:01] <seb128> and some others
[07:01] <pitti> seb128: it has these too
[07:02] <pitti> seb128: I diffed the old vs new -base, and there were no removed files aside from evolution-3.12
[07:02] <seb128> k
[07:02] <seb128> so unresolved mystery
[07:03] <seb128> I wonder if we should have an autopkgtest with a list of expected domains
[07:03] <pitti> for -base we could -- the deltas could contain anything from zero to the full set
[07:04] <seb128> but I guess that wouldn't work well because on base refresh those are removed from the other packages
[07:09] <flexiondotorg> Morning.
[07:09] <flexiondotorg> Could someone clarify a policy issue for me?
[07:09] <flexiondotorg> This bug has been raised against Ubuntu MATE - https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1500932
[07:10] <ubot5`> Ubuntu bug 1500932 in caja (Ubuntu) "Sync caja 1.10.3-2 (universe) from Debian unstable (main)" [Undecided,New]
[07:10] <flexiondotorg> No, not that one.,
[07:10] <flexiondotorg> https://bugs.launchpad.net/ubuntu-mate/+bug/1501426
[07:10] <ubot5`> Ubuntu bug 1501426 in ubuntu-mate "15.10 Beta 2 fails HTML5 audio test for MP3" [Undecided,Incomplete]
[07:11] <flexiondotorg> Which can be resolved post-install by installing restricted-extras.
[07:11] <flexiondotorg> Or gstreamer1.0-libav could be added to the seeds.
[07:11] <flexiondotorg> What is the position on including gstreamer1.0-libav by default/
[07:12] <seb128> you better ask on #ubuntu-devel
[07:12] <flexiondotorg> Ah, OK.
[07:12] <seb128> there are more people there aware of code/legal issues
[07:15] <larsu> bonjour!
[07:15] <seb128> hey larsu, wie gehts?
[07:15] <pitti> larsu: ça va ?
[07:15] <larsu> seb128: a bit better than yesterday, but still stuffed. How are you?
[07:15] <larsu> hi pitti, wie gehts?
[07:16] <seb128> larsu, I'm good thanks!
[07:16] <pitti> c'est drôle que les personnes françaises parlent allemagne maintenant et les personnes allemagnes parlent français :)
[07:18] <seb128> :-)
[07:19] <didrocks> good morning larsu! I hope you will feel better after the week-end ;)
[07:20] <didrocks> konnichiwa
[07:20] <larsu> didrocks: good morning and thanks!
[07:36] <hikiko> Trevinho, https://code.launchpad.net/~hikiko/compiz/compiz.matrix-additions/+merge/273072
[07:36] <hikiko> if you have a minute at some point:)
[07:36] <hikiko> (no rush)
[07:51] <willcooke> morning fellows
[07:51] <larsu> morning willcooke!
[07:54] <didrocks> hey willcooke
[07:54] <didrocks> feeling better?
[07:54] <willcooke> not especially
[07:54] <willcooke> should probably actually rest rather than sitting at the computer
[07:55] <willcooke> but hey ho
[07:56] <didrocks> :/
[07:56] <seb128> hey willcooke
[07:56] <seb128> willcooke, better to have something to do than nothing and just focussing on the fact you feel unwell, right?
[07:57] <willcooke> seb128, yeah, I guess.  I could go a nap though
[07:57] <willcooke> :0
[08:01] <Laney> yo
[08:02] <Laney> happy f-r-i-d-a-y!
[08:02] <seb128> hey Laney!
[08:02] <seb128> happy friday ;-)
[08:04] <didrocks> hey hey Laney!
[08:04] <willcooke> \o
[08:05] <Laney> hey seb128 didrocks & willcooke
[08:05] <Laney> how's it going?
[08:05] <seb128> good!
[08:06] <didrocks> good :)
[08:06] <seb128> happy it's friday, but at the same time still feels like I've quite some things I want to get done before w.e, going to be a busy day ;-)
[08:06] <Laney> nice autumn day today
[08:06] <seb128> here as well
[08:06] <seb128> it has been a quite good bugfixing week this week
[08:16] <Laney> woah
[08:16] <Laney> my desktop has booted to an emergency shell
[08:16] <seb128> urg
[08:17] <Laney> haha
[08:17] <Laney> I messed up my fstab yesterday
[08:17] <Laney> /o\
[08:18] <davmor2> Laney: that'll do it
[08:20] <willcooke> seb128, didrocks, Laney - can you advise hikiko on which sort of Ubuntu membership to go for...
[08:20] <willcooke> Contributing Developers (Ubuntu Membership), per-package uploaders, MOTU and Core Developers
[08:20] <willcooke> would PPU be best?
[08:20] <seb128> willcooke, I though popey told her to go for MOTU during the meeting yesterday?
[08:21] <seb128> hikiko, sorry I didn't think the meeting was this week and I hadn't write on the wiki yet :/
[08:21] <hikiko> seb128, yes but it seems that MOTU is for packagers
[08:21] <willcooke> yeah, but I'm not sure that's the correct option, so would like your feedback too
[08:21] <hikiko> are collectively responsible for the maintenance of packages in the universe and multiverse components
[08:21] <seb128> I would say contributing developer
[08:21] <hikiko> that's what I applied for yesterday
[08:21] <hikiko> and got rejected :D
[08:22] <hikiko> Ubuntu Membership
[08:22] <hikiko> or it's different w8
[08:22] <seb128> popey said something about your page behing a bit short on details
[08:22] <seb128> which is what I pointed out when I saw it as well...
[08:22] <hikiko> https://wiki.ubuntu.com/UbuntuDevelopers#ContribDev this one
[08:22] <hikiko> yes I will add a list of projects in contributions
[08:23] <seb128> willcooke, can you talk to popey
[08:23] <seb128> I don't understand why they bounced her back to apply for MOTU since she doesn't do packaging
[08:23] <seb128> ?
[08:23] <Laney> contributing dev is usually for people on the motu path
[08:23] <Laney> I wouldn't have advised that myself
[08:24] <Laney> but maybe we could consider it?!?!?!
[08:24] <hikiko> maybe popey thought I do packaging
[08:24] <willcooke> popey, let's rap when you're fre
[08:24] <willcooke> e
[08:25] <seb128> yeah, maybe he got confused because your page lacks details?
[08:25] <hikiko> :D
[08:25] <hikiko> I am improving the wiki
[08:25] <seb128> good idea ;-)
[08:28]  * davmor2 pictures popey and willcooke rapping something like this https://www.youtube.com/watch?v=JAIOzM7SsMo
[08:28] <willcooke> davmor2, oh no, I'm not falling for that again
[08:29] <davmor2> willcooke: No one ever seen what I mean from the age of nnnnnnnnnnnnnn13
[09:11] <davmor2> willcooke: I have no idea what you mean, it's not like I know every earworm ever created or anything
[09:13] <willcooke> davmor2, normally you Rick roll me
[09:13] <willcooke> :D
[09:13] <davmor2> willcooke: no that is no rick roll
[09:14] <willcooke> davmor2, I dont believe you.
[09:14] <willcooke> ;)
[09:14] <davmor2> willcooke: that is the pinnacle of rap it got no better ;)
[09:14] <willcooke> ohhhhhhhh
[09:14] <willcooke> Wow
[09:14] <willcooke> I remember that
[09:18] <didrocks> why did you kick me out? freenode? :p
[09:20] <davmor2> willcooke: I remember every piece of music I've ever heard and every tv show/film I've ever seen. It's sad really Like today I have this stuck in my head https://www.youtube.com/watch?v=3cShYbLkhBc most of the whippersnappers here will never of heard it :)
[09:20] <willcooke> davmor2, great tune!
[09:25] <davmor2> willcooke: if you want to follow along with the mind melt http://open.spotify.com/user/1142386698/playlist/2nlSxBLEbfKpvDqSDG8hP8  a list of the songs that randomly pop into my head first thing :)  Makes for a great day of music :D
[09:25] <willcooke> davmor2, https://www.youtube.com/watch?v=IrPWkIRWY9U
[09:26] <davmor2> midnight express great film
[09:29] <davmor2> willcooke: I see your chase and I raise you https://www.youtube.com/watch?v=pcawnRIyeok
[09:30] <willcooke> davmor2, \o/
[09:30] <seb128> darkxst, unsure if you saw my comment the other day, but the top e.u.c wily issue is an xorg sigabrt which looks like a gdm issue
[09:31] <seb128> just installed gdm on my test laptop and it doesn't work, I get an empty vt and no graphical dm or session
[09:31] <seb128> unsure if that 's the same issue
[09:31] <seb128> if I systemctl restart gdm I get an crash file then
[09:31] <seb128> you might want to investigate it, could be an important issue for Ubuntu GNOME
[09:34]  * Sweet5hark forgot his "bonjour".
[09:34]  * Sweet5hark time travels two hours back and says "moin".
[09:44] <seb128> hey Sweet5hark, looks like you found a way to make doko happy and get libreoffice in? ;-)
[09:44] <didrocks> seb128: oh, forgot to send you the bustle log from my session, I'm unsure how you are supposed to read it: http://people.canonical.com/~didrocks/tmp/sessionlog
[09:45] <seb128> didrocks, "bustle sessionlog" shows an UI
[09:45] <seb128> it basically displays the dbus exchanges
[09:46] <Sweet5hark> seb128: yeah. well, one thing wasnt fixed in this upload (fxed in git now though, should we do yet another upload: http://anonscm.debian.org/cgit/pkg-openoffice/libreoffice.git/commit/?h=ubuntu-wily-5.0) ...
[09:48] <seb128> Sweet5hark, k
[09:48] <didrocks> seb128: the /org/gnome/Shell activity-related sounds quite opaque…
[09:48] <didrocks> I don't even see the accelerator key exchanges
[09:48] <seb128> didrocks, I don't see anything having to do with the Grabber interface there though ...
[09:49] <didrocks> yeah
[09:49] <didrocks> apart from the AcceleratorActivated
[09:49] <didrocks> and a bunch of property GetAll() probs…
[09:50] <seb128> unsure, maybe larsu has a better idea about that when he's back
[09:51] <didrocks> yeah
[09:51] <seb128> going to try to do a bustle log of my session to compare after lunch
[09:51] <seb128> but first need to go for some errands
[09:51] <seb128> bbiab
[09:52] <didrocks> see you!
[09:52] <didrocks> seb128: good idea
[09:52] <seb128> :-)
[10:02] <doko> new fun stuff ... http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151001-wily.html
[10:03] <Laney> it's great to have you in here doko!
[10:05] <didrocks> doko: speaking of fun stuff, mind looking at bug #1500768?
[10:05] <ubot5`> bug 1500768 in python3.4 (Ubuntu) "python3.4.3 SRU break requests" [High,Confirmed] https://launchpad.net/bugs/1500768
[10:05] <didrocks> (you did the SRU update it seems)
[10:08] <doko> yep, finally ... looking
[10:08] <didrocks> thx!
[10:39] <willcooke> davmor2, do you have a 3g usb dongle?  I'm having problems with usb_modeswitch on 15.10 that I'm not seeing on 14.04
[10:41] <davmor2> give me a few I'll have a look
[10:51] <davmor2> willcooke: hmmmm I have a blue flashy light on the system but I'm not getting an actual connection show up in the indicator :(
[10:52] <davmor2> on the dongle even
[10:52] <willcooke> davmor2, does syslog show messages about usb_modeswitch crashing?
[10:55] <davmor2> willcooke: yes indeedy
[10:55] <willcooke> oh dear
[10:57] <willcooke> Could be related to:
[10:57] <willcooke> https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1498805
[10:57] <ubot5`> Ubuntu bug 1498805 in usb-modeswitch (Ubuntu Wily) "Please merge usb-modeswitch 2.2.5+repack0-1 from Debian unstable/testing - current 2.2.3 version in Wily has regressions with lots of Huawei modems" [High,Triaged]
[10:58] <davmor2> willcooke: that would match my model
[10:58] <willcooke> Mine is a ZTE, but sounds like a general problem
[10:59] <willcooke> Looks like everything is lined up to pull the new version in but just needs doing
[11:00] <willcooke> seb128, is this something you could put on your long list?  ^^
[11:00] <davmor2> willcooke: is there a package for 2.2.3 somewhere I can install and see if it works then?
[11:02] <willcooke> davmor2, dunno, looking...
[11:04] <davmor2> willcooke: I'm trying the one from deb sid
[11:04] <willcooke> thanks davmor2
[11:08] <davmor2> willcooke: seb128: so with deb sid's 2.2.5+repack0-1_amd64.deb I have a working connection youtube video is playing so connection is good and constant
[11:08] <willcooke> great, thanks davmor2
[11:08] <willcooke> davmor2, can you point me at the deb and I'll see if it helps my ZTE modem too
[11:09] <davmor2> willcooke: https://packages.debian.org/sid/comm/usb-modeswitch
[11:16] <didrocks> time to run! bbiab
[11:17] <willcooke> cya didrocks
[11:22] <willcooke> davmor2, yeah - fixed here too
[11:22] <willcooke> \o/
[11:25] <willcooke> Now if only I can convince this PPP connection to start, I'll be happy.  But I think that's related to this free sim I got and not an Ubuntu issue
[11:27] <larsu> didrocks: ah cool thanks!
[11:27]  * larsu installs bustle
[11:34] <doko> Sweet5hark, http://autopkgtest.ubuntu.com/packages/libr/libreoffice/wily/amd64/
[11:35] <larsu> Trevinho: as of recently, sometimes unity stops accepting mouse input (keyboard works)
[11:36] <larsu> Trevinho: restarting unity makes this work again, but it then forgets about all open windows
[11:36] <larsu> Trevinho: even though they are still running...
[11:36] <larsu> Trevinho: is this a known bug?
[11:39] <seb128> willcooke, I can try to have a look but that's rather one for cyphermox
[11:39] <seb128> I already pinged him about that a week ago
[11:40] <Sweet5hark> doko: thanks, looking
[11:44] <willcooke> seb128, oki, thanks.  If it helps, davmor2 and I can confirm it does fix the problem.    <-- cyphermox: when you get a chance, could you take a look at https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1498805
[11:44] <ubot5`> Ubuntu bug 1498805 in usb-modeswitch (Ubuntu Wily) "Please merge usb-modeswitch 2.2.5+repack0-1 from Debian unstable/testing - current 2.2.3 version in Wily has regressions with lots of Huawei modems" [High,Triaged]
[11:45] <seb128> willcooke, http://irclogs.ubuntu.com/2015/09/23/%23ubuntu-devel.html#t15:10
[11:45] <andyrock> good morning :D
[11:45] <seb128> willcooke, that was the previous week discussion
[11:45] <seb128> andyrock, hey
[11:48] <willcooke> thanks seb128.  I'll comment on the bug
[11:49] <seb128> willcooke, thanks
[12:02] <qengho> Good morning.
[12:10] <seb128> larsu, back from lunch? how busy are you this afternoon? want to look at an easy ido-fail-to-build (some gtk deprecations and a void function returning a value)
[12:10] <seb128> https://launchpadlibrarian.net/219493349/buildlog_ubuntu-wily-i386.ido_13.10.0%2B15.10.20150728-0ubuntu1_BUILDING.txt.gz
[12:10] <larsu> seb128: sure, I'll have a look
[12:10] <seb128> danke
[12:11] <larsu> didrocks: GrabAccelerators() is called excalty once, and nothing else
[12:11] <larsu> didrocks: looks correct to me...
[12:11] <larsu> seb128: this is just -Werror shit, no?
[12:11] <seb128> larsu, yeah, we could drop the Werror, the return in void might be worth fixing though?
[12:12] <larsu> seb128: sure. Just asking if there's more to it :)
[12:12] <seb128> or maybe don't drop Werror but don't error out on deprecations
[12:12] <larsu> -Werror is stupd
[12:12] <larsu> hm, I'm not seeing this locally
[12:13] <seb128> larsu, we can add  -Wno-error=deprecated-declarations to the flags
[12:13] <seb128> like https://code.launchpad.net/~seb128/indicator-application/dont-werror-on-deprecations/+merge/201988
[12:13]  * pitti -> cd ~, have a nice weekend everyone!
[12:14] <larsu> pitti: enjoy!
[12:14] <larsu> seb128: ya, *at least* that
[12:15] <seb128> pitti, have a nice w.e!
[12:15] <pitti> larsu, seb128: thanks, and you!
[12:15] <seb128> larsu, unsure what's the difference between builders and your build :/
[12:16] <larsu> seb128: ah it already has -Wno-error=deprecated-declarations
[12:16] <larsu> seb128: me neither :/
[12:16]  * larsu cleans his build tree
[12:16] <seb128> I guess it errors out on the return then?
[12:19] <larsu> it doesn't at all for me
[12:19] <larsu> oh!
[12:19] <larsu> there was this gcc bug.........
[12:19]  * larsu tries to find it
[12:20] <larsu> https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1234218
[12:20] <ubot5`> Ubuntu bug 1234218 in gcc-4.8 (Ubuntu) "4.8 doesn't throw -Wreturn-type anymore for wrong returns in macros" [Undecided,New]
[12:20] <larsu> so I'm clearly hitting this locally
[12:20] <larsu> (man, I filed that 2 years ago :( )
[12:23] <seb128> ah
[12:23] <larsu> I wonder why the builder is getting the warning now, though
[12:24]  * larsu upgrades gcc
[12:25] <seb128> larsu, what gcc version do you have?
[12:25] <larsu> 5.2.1-3ubuntu1
[12:26] <larsu> upgrading to 9ubuntu1 now
[12:26] <larsu> same as the builder
[12:26] <seb128> k, let's see
[12:26] <seb128> maybe that got fixed in that update ;-)
[12:26] <larsu> heh, let's hope
[12:27] <Laney> pi came
[12:27] <Laney> and blast, it needs microsd and I don't have one of those
[12:27] <larsu> nope :/
[12:27] <seb128> Laney, :-(
[12:27] <larsu> Laney: ugh
[12:27] <Laney> shop time!
[12:27] <Laney> need a way of putting bits onto it too
[12:27] <Laney> ...
[12:28] <larsu> Laney: the pi?
[12:28] <Laney> the micro sd
[12:28]  * Sweet5hark sees and hour long discussion of the usage of /bin/sh /bin/bash plus other shells like dash in various parts of the build system on #libreoffice-dev. those seem to come back every 6 months because of $something ...
[12:28] <larsu> Laney: use the pi?!
[12:28] <Laney> ?
[12:28] <seb128> eat it!
[12:28] <larsu> seb128: still not seeing the warning :'(
[12:28] <larsu> Laney: I was joking, sorry
[12:28] <Trevinho> seb128: for some reason unity now fails to build (well to start tests, actually) on ppc64el, due to the "LLVM ERROR: Do not know how to split the result of this operator!" error.
[12:28] <Trevinho> I guess it's somewhat related to mesa, see https://launchpadlibrarian.net/219585615/buildlog_ubuntu-wily-ppc64el.unity_7.3.2%2B15.10.20151002.1-0ubuntu1_BUILDING.txt.gz
[12:29] <Laney> haha
[12:29] <seb128> Trevinho, :-(
[12:29] <Laney> I thought you were telling me to use it to write to the SD somehow
[12:29] <larsu> Trevinho: did you see my ping?
[12:29] <seb128> larsu, do you see the code error pointed by the log?
[12:29] <larsu> Laney: it was funny in my head
[12:29] <Trevinho> larsu: nope :o
[12:29] <Laney> :)
[12:29] <larsu> Trevinho: please use an irc client that can notify you of pings :P
[12:30] <larsu> Trevinho: do you see it in the scrollback or shall I paste?
[12:30] <Laney> ideally as a notification to your phone
[12:30] <Laney> which is REALLY LOUD
[12:30] <larsu> that's a bit ... much
[12:30] <Trevinho> larsu: it does, but I didn't scroll yet :P
[12:30] <larsu> scroll more ;)
[12:31] <Trevinho> larsu:  however, the mouse issue is in unity stuff, like the dash or where?
[12:31] <larsu> Trevinho: I think it's totally fine if you're not there, but please go offline then (I'll then just ping when you come on)
[12:31] <larsu> Trevinho: no, everywhere
[12:32] <Trevinho> mh, I've not noticed that, but we didn't change anything that might be global. I did change something at nux level, but it would affect only unity widgets
[12:32] <larsu> seb128: maybe because i386? But that would be very weird... I'll upload a branch in any case
[12:32] <Trevinho> althought it's just about sending mouse_released signals and such, so not anything should be an issue
[12:32] <larsu> "should"
[12:32] <seb128> larsu, yeah, going to try in a bit on my i386 laptop
[12:33] <larsu> Trevinho: how can I debug this next time it happens?
[12:33] <larsu> seb128: thanks
[12:33] <Trevinho> seb128: what could I do on that ppc46el failure? It seems that's something we already experienced... (https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.5/+bug/1360241)
[12:33] <ubot5`> Ubuntu bug 1360241 in llvm-toolchain-3.5 (Ubuntu) "[Regression] "LLVM ERROR: Do not know how to split the result of this operator!" in executing Ubuntu UI Toolkit tests on x86" [Undecided,Confirmed]
[12:34] <Trevinho> andyrock was saying we had something similar when building in qemu with lower specs (i.e. when not using pentium4 on x86)
[12:34] <andyrock> not building
[12:34] <seb128> when did that start?
[12:34] <andyrock> just running
[12:34] <seb128> tjaalton, ^ regression from your recent mesa update?
[12:34] <seb128>   * rules, control: Enable llvmpipe on ppc64el. (LP: #1489483)
[12:34] <ubot5`> Error: Could not gather data from Launchpad for bug #1489483 (https://launchpad.net/bugs/1489483). The error has been logged
[12:35] <Trevinho> seb128: basically last week it was building fine
[12:35] <seb128> Trevinho, yeah, there was that update yesterday ^
[12:35] <seb128> which smells like it
[12:35] <seb128> let's wait for tjaalton to comment
[12:35] <larsu> seb128: https://code.launchpad.net/~larsu/ido/buildfix/+merge/273222
[12:35] <seb128> larsu, danke!
[12:35] <andyrock> that's why we ping seb128
[12:35] <Trevinho> seb128: ah, something like that... thanks
[12:35] <andyrock> :D
[12:35] <larsu> seb128: I coldn't find any others from a quick look - but I don't get the warnings so who knows :/
[12:36] <seb128> larsu, yeah, I'm going to try to reproduce and test the fix
[12:36] <seb128> thanks
[12:36] <larsu> thanks
[12:36] <Laney> this is weird
[12:37] <larsu> define: this
[12:37] <Laney> I get that failure when building ido in sbuild
[12:37] <Laney> but not with bzr bd
[12:37] <larsu> Laney: I tried with maintainer mode as well, to no avail
[12:37] <Laney> well
[12:37]  * larsu wonders if "to no avail" is correctly used here
[12:38] <Laney> I recommend sbuild anyway
[12:38] <Laney> yes
[12:38] <larsu> I know you do, but this should happen when building "normally" as well
[12:39] <tjaalton> seb128: what bug? builds fine on a ppa
[12:39] <Laney> good old "should"
[12:39] <larsu> love it
[12:39] <tjaalton> oh unity fails
[12:39] <larsu> https://www.youtube.com/watch?v=eBlD2N_AwgI
[12:40] <tjaalton> fix unity?-)
[12:40] <Laney> what are you doing making changes like that after feature freeze with no exception?
[12:40] <larsu> gotta get that^^ into your heads again before the sprint
[12:40] <Sweet5hark> doko: seems to have been an intermittent failure? http://autopkgtest.ubuntu.com/packages/libr/libreoffice/wily/amd64/ <- last run passed ...
[12:40] <Laney> larsu: YES
[12:40] <tjaalton> mesa has MRE, that change request came from ibm
[12:41]  * larsu is out for a quick errand
[12:41] <Trevinho> tjaalton: mh, might be... But I've no clue what's wrong :)
[12:41] <tjaalton> then I'll drop it and ask ibm to fix
[12:41] <Trevinho> I mean it's only on ppc64el
[12:41] <Trevinho> which I don't have (I guess I've to setup a qemu to investigate?)
[12:41] <tjaalton> before revisiting
[12:42] <Laney> that is for SRUs and is not for changing/enabling features
[12:42] <Laney> anyway, good, thanks
[12:42]  * Laney is off SD card shopping
[12:43] <Laney> back soon
[12:47] <seb128> Laney, good luck
[12:47] <seb128> tjaalton, thanks
[12:48] <Trevinho> tjaalton: once you've pushed the revert of that change, can you please ping me? So I can trigger a rebuild on train...
[12:49] <tjaalton> ok
[12:51] <Trevinho> ta
[12:56] <didrocks> larsu: so, unsure why I have that double grab then…
[12:56] <seb128> larsu, didrocks, btw https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-008/+packages has a build of the unity update from Trevinho with the keygrab changes, if you want to test if it fixes the issue
[12:57] <didrocks> larsu: oh sorry, I did reboot in between, so that's a "normal" login
[12:57] <didrocks> so yeah, making sense
[12:57] <didrocks> let's see next time I'll have the same issue
[12:57] <didrocks> seb128: well, I keep it broken for now to get again the right logs ^ (probably Monday for logout/login several times)
[12:58] <seb128> didrocks, right, so don't upgrade from wily either on monday ;-)
[12:58] <didrocks> ok ;)
[12:58] <didrocks> noted down
[13:02] <Trevinho> willcooke also I guess ^^
[13:05] <qengho> May I have a sponsor for Wily chromium-browser upload from  https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage ? Copy is fine.
[13:06] <seb128> qengho, I can do that
[13:07] <qengho> seb128: merci.
[13:07] <seb128> de rien!
[13:09] <willcooke> thanks Trevinho
[13:10] <willcooke> seb128, fyi:  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501281
[13:10] <ubot5`> Ubuntu bug 1501281 in linux (Ubuntu) "Frequent freezes on 15.04 with kernel 3.19.0-29+" [High,Confirmed]
[13:10] <willcooke> seb128, pmcgowan is having a lot of lock-ups so is trying this new kernel.  Just something to be aware of
[13:11] <seb128> oh, Laney fixed activity-log-manager ... if you mp a change, can you also fix the other warning from the build log "if(ev != null);", the ";" shouldn't be there and make the if section being unused
[13:11] <seb128> willcooke, ok, did you talk to the kernel team about it?
[13:12] <willcooke> seb128, not yet, gonna see if it helps Pat and then I will, might be a red herring
[13:17] <tjaalton> Trevinho: accepted
[13:17] <Trevinho> tjaalton: cool
[13:19] <Trevinho> tjaalton: you said that IBM will check what's wrong in our stack?
[13:20] <Trevinho> tjaalton: however, the crash happens on tests loading so, I guess it's on libgl loading, not while unity code is running yet
[13:20] <tjaalton> Trevinho: i've let them know that it won't be added back before unity builds with it
[13:20] <seb128> tjaalton, I don't think it's unity specific
[13:20] <seb128> but I think having unity building would be a good sign it's resolved
[13:20] <tjaalton> right
[13:21] <Trevinho> Mh, yeah, I can't say it's not unity without some real testing, but the thing is that it crashes at very early stages... So I'd bet more on nux, but we need to check
[13:22] <tjaalton> still, the bug is updated and linked to the old bug, they'll know where to look
[13:23] <Trevinho> nice
[13:23] <tjaalton> don't care who fixes it, and don't mind keeping it disabled forever if things aren't fixed
[13:23] <tjaalton> :)
[13:23] <Trevinho> :)
[13:24] <tjaalton> didn't notice it was attempted a year ago
[13:25] <Trevinho> If they'd like to get it fixed, it would be nice if they could spend some work in verifying what's wrong... I'd prefer to avoid (right now) to spend time in setting up a eqmu env to slowly build unity here
[13:28] <seb128> larsu, I could reproduce the ido build issue with bzr bd and your branch fix it, doing a landing, thanks!
[13:34] <desrt> hello desktop!
[13:36] <seb128> hey desrt
[13:36] <seb128> how is your conference going?
[13:37] <desrt> it's over
[13:38] <desrt> i'm back home
[13:40] <andyrock> hey desrt
[13:40] <andyrock> quick question
[13:40] <andyrock> https://www.irccloud.com/pastebin/9jyZA1jO/
[13:40] <desrt> go
[13:40] <andyrock> is printing
[13:40] <andyrock> 1
[13:40] <andyrock> 2
[13:40] <andyrock> 2
[13:40] <andyrock> looks weird no?
[13:40] <desrt> this pastebin is awful :)
[13:41] <desrt> oh.  nvm.  my bad.
[13:41] <desrt> uhhh
[13:41] <desrt> probably something odd about toggle refs going on there?
[13:41] <andyrock> now gtk label uses a weak references to its parent
[13:42] <andyrock> but a weak ref should not increase the nornal ref count
[13:42] <andyrock> right?
[13:42] <desrt> no....
[13:42] <desrt> erm.  maybe.  :)
[13:42] <desrt> when adding a child, the way it works is that the child increases its own refcount, iirc
[13:43] <desrt> but indeed, not the parent refcount
[13:43] <desrt> are you sure you're not viewing some odd artifact of the binding?
[13:44] <andyrock> http://paste.ubuntu.com/12638413/
[13:44] <andyrock> I'll try to write the same in C
[13:44] <andyrock> just used Python because you know
[13:44] <andyrock> it's faster
[13:44] <desrt> why do you care about refcounts?
[13:44] <desrt> trying to track a leak or something?
[13:44] <andyrock> because we have a huge leak
[13:45] <andyrock> in unity-panel-service
[13:45] <andyrock> hud-service
[13:45] <desrt> tsk tsk
[13:45] <andyrock> basically everything related with indicator-appmenu
[13:45] <andyrock> let me write do write the same in C
[13:53] <andyrock> desrt: mmm no seems fine in C
[13:56] <seb128> desrt, Laney, telepathy-glib build is grumpy, segfault in a test, https://launchpadlibrarian.net/219653847/buildlog_ubuntu-wily-amd64.telepathy-glib_0.24.1-1_BUILDING.txt.gz
[13:56] <seb128> desrt, Laney, could you try if that's the case on Debian as well? I suspect it might be a new glib thing
[13:57] <seb128> ah, the log has details
[13:57] <seb128> GLib-ERROR **: duplicate test case path: /account/reconnect
[13:58] <seb128> laney just fixed a similar issue in libsoup, I guess need to remove the duplicate test
[14:00] <Laney> bah
[14:00] <Laney> I need to finish that patch to make it do VERBOSE=1 by default
[14:00] <Laney> fixing all these packages is annoying
[14:00] <seb128> indeed
[14:03] <seb128> Laney, sent to debian/upstream
[14:03] <seb128> https://bugs.freedesktop.org/show_bug.cgi?id=92245
[14:03] <ubot5`> Freedesktop bug 92245 in tp-glib "build fails with glib 2.46 due to duplicated tests" [Normal,New]
[14:03] <seb128> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800689
[14:03] <ubot5`> Error: debian bug 800689 not found
[14:03] <seb128> I don't plan to work on a fix today
[14:04] <seb128> let's see if somebody comes with one during the w.E
[14:05]  * Laney spots in_finity in uploaders for that one
[14:05] <Laney> weird
[14:05] <happyaron> omg hard disk failure
[14:05] <seb128> hey happyaron
[14:05] <seb128> happyaron, you have backups right?
[14:05] <happyaron> hey, :)
[14:05] <happyaron> yep I have
[14:06] <happyaron> I remember someone else on our team have broken disk two days ago... FJKong?
[14:06] <seb128> happyaron, since you are around, just mentioning that http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151001-wily.html has build failures for fcitx-qt5 (.symbols issue) and ibus-sunpinyin, would be nice if you could have a look once you are back from the golden weeks holidays ;-)
[14:07] <Laney> seb128: should be trivial, I will see about sending a patch
[14:07] <seb128> Laney, ok, thanks
[14:07] <willcooke> happyaron, I had some fsck issues the other day and I think Laney has a busted FS on his Beagle board
[14:08] <Laney> nah that panda has always been shit
[14:10] <happyaron> willcooke, well, :(
[14:10] <willcooke> happyaron, is this a good time to get an SSD? :)
[14:10] <happyaron> seb128 Laney thank you
[14:11] <happyaron> willcooke: I believe YES
[14:12] <willcooke> :D
[14:15] <seb128> larsu, that gcc bug seems like was a glib bug, https://bugzilla.gnome.org/show_bug.cgi?id=753310
[14:15] <ubot5`> Gnome bug 753310 in general "Remove `#pragma GCC system_header` from gmessages.h" [Minor,Resolved: fixed]
[14:15] <seb128> larsu, should be fixed in 2.46.1 for wily
[14:15] <seb128> thanks doko for finding that
[14:25] <willcooke> qengho, http://conoroneill.net//running-the-latest-chromium-45-on-debian-jessie-on-your-raspberry-pi-2
[14:28] <seb128> attente, hey, indicator-keyboard seems to fail to build in wily, can you have a look? at least if you get lp:indicator-keyboard and bzr bd
[14:28] <attente> seb128: ok
[14:28] <seb128> thanks
[14:29] <seb128> hum, starting manually hits a different assert here
[14:30] <seb128> g_variant_get_type: assertion 'value != NULL' failed
[14:30] <seb128> under bzr bd
[14:30] <seb128> ERROR:main.c:983:tests_test_activate_input_source: assertion failed: (strcmp (output, "uint32 2\n") == 0)
[14:30] <seb128> doing ./indicator-keyboard-tests
[14:32] <seb128> just for the fun, it fails to start gucharmap it seems
[14:32] <seb128> but that works if you ld_preload glib 2.44
[14:32] <seb128> loving glib updates ;-)
[14:33] <seb128> well maybe the gucharmap has nothing to do with that, it just goes on to the next test with old glib
[14:34] <attente> ugh...
[15:03] <qengho> willcooke: Nice. I'm kind of surprised.
[15:09] <seb128> tjaalton, tseliot, unsure who is maintaining that code but there seems to be an issue with the xorg hook to collect nvidia logs, see e.g https://errors.ubuntu.com/oops/51bc3fe6-68f9-11e5-b863-fa163e5bb1a2
[15:09] <seb128> the HookError_source_xorg_server
[15:10] <seb128> seems like all the reports from nvidia users have that issue
[15:11] <tseliot> version.nvidia-graphics-drivers	nvidia-graphics-drivers N/A
[15:12] <tseliot> seb128: maybe it's looking in the wrong place
[15:12] <tjaalton> probably xdiagnose
[15:12] <seb128> tseliot, it's looking in /proc/driver/nvidia/*/*
[15:12] <tseliot> I'm pretty sure I didn't write that hook
[15:12] <seb128> yeah, unsure who maintains it/make use of the info
[15:13] <seb128> I was mentioning it in case somebody is interested in fixing it
[15:13] <seb128> if not that's fine
[15:13] <tseliot> I can have a look at it
[15:14] <tjaalton>     report['version.nvidia-graphics-drivers'] = package_versions("nvidia-graphics-drivers")
[15:14] <tjaalton> shouldn't be hard to fix :)
[15:14] <tjaalton> thanks
[15:14] <seb128> yw!
[15:16] <tseliot> yes, that's what I'm looking at
[15:19] <tseliot> tjaalton: also the links such as usr/share/apport/package-hooks/source_nvidia-graphics-drivers.py are obsolete
[15:21] <tjaalton> tseliot: yes, rename it?
[15:22] <tjaalton> or what do you mean obsolete?
[15:22] <tjaalton> go wild with it :)
[15:22] <tseliot> tjaalton: that source package no longer exists, and there are more flavours now
[15:23] <tjaalton> right
[15:23] <tseliot> I'll fix it next week
[15:25] <seb128> Trevinho, seems like https://code.launchpad.net/~3v1n0/bamf/better-lib-caching/+merge/257002 was forgotten? we should land that at the start of next cycle
[15:26] <seb128> Trevinho, https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1501973 ... unsure if that's the same issue than the one you were working on (making gtk always specify the size)
[15:26] <ubot5`> Ubuntu bug 1501973 in unity (Ubuntu) "Blurry/pixelated icon in Unity app switcher on scaled-up display" [Low,Confirmed]
[15:34] <qengho> seb128: I see Cr in proposed. Thanks again.
[15:34] <seb128> qengho, yw!
[15:56] <didrocks> ok, time to enjoy the week-end, see you guys on Monday!
[15:57]  * Laney haz working pi
[15:59] <seb128> Laney, good job ;-)
[16:00] <Laney> I found a Debian image that sjoerd had made
[16:00] <Laney> easy
[16:01] <seb128> oh, you got a pi1
[16:01] <seb128> not the pi2 where you could install Ubuntu
[16:01] <Laney> i did get a pi2
[16:02] <Laney> but I only found some random image on the wiki
[16:02] <seb128> snappy!
[16:02] <Laney> or snappy...
[16:02] <Laney> ...
[16:02]  * Laney runs
[16:02]  * seb128 hides
[16:03] <seb128> k, speaking of which, nice weather and long week, I'm going for some exercice
[16:03] <willcooke> cya seb128
[16:03] <seb128> be back in an hour or so to read scrollbacks and emails before calling it a week and closing the computer
[16:03] <seb128> have a good w.e for those who are off before I'm back
[16:03] <seb128> thanks ;-)
[16:03] <Laney> bye!
[16:07] <Trevinho> seb128: it has been forgotten some months ago, I knew about it now that I've landing powers :P, but I didn't propose as I wanted to hold it till next cycle
[16:08] <Trevinho> seb128: 2nd bug is the same, yes
[16:16] <larsu> seb128: oh wow! Thanks :)
[16:16] <larsu> seb128: I would have never guessed glib did something so ... stupid
[16:26] <Trevinho> leaving for some time, i'll be back later, but in the mean time have nice WE guys
[17:02] <Laney> happy weekend
[17:02] <Laney> one and all and all and one
[17:04] <seb128> Laney, thanks, to you too!
[17:05]  * Laney remembered one thing
[17:10] <willcooke> g'nigth all
[17:14] <Sweet5hark1> <- going, going, gone.
[17:14] <Sweet5hark1> ;)
[17:50] <cyphermox> attente: is there any way to split pixbuf out of libappstream-glib? it would be nice to link against appstream-glib without pulling a bunch of image of X libs and such?
[17:53] <attente> cyphermox: no idea tbh
[17:53] <attente> would have to take a look to see what it's using it for
[17:54] <cyphermox> oh ok.
[17:54] <cyphermox> I saw your name in the NEWS file, so I thought I' d ask
[17:54] <cyphermox> it looks pretty tightly integrated :(
[18:06] <attente> cyphermox: what do you think about building a new package of gdk-pixbuf with x11 support disabled?
[18:07]  * cyphermox shrugs
[18:07] <cyphermox> I'm just evaluating options
[18:07] <cyphermox> if it' s doable, at least it' s another option perhaps
[18:07] <mdeslaur> wait a sec if you decide to do that, I'm about to upload a gdk-pixbuf security update to wily
[18:07] <cyphermox> mdeslaur: not planning on doing that today
[18:07] <mdeslaur> ok, good
[21:37] <qengho> Zzz