[05:41] <pitti> Good morning
[06:45] <didrocks> good morning
[07:04] <pitti> bonjour didrocks
[07:04] <didrocks> guten morgen pitti! How are you?
[07:07] <pitti> didrocks: quite fine, thanks! not drowned in snow just yet :)
[07:07] <pitti> didrocks: et toi, ça va bien?
[07:07] <didrocks> pitti: ça va! par contre de la neige partout, surtout sur les trottoirs à ce que je vois :)
[07:09] <pitti> didrocks: not quite enough snow in the city for skiing here, but just outside it's fine
[08:17] <didrocks> jibel: salut!
[08:18] <didrocks> jibel: FYI, I've just pushed a version which doesn't use pull-lp-source, but rather embeed the functionality in our own process to use our per job cache instead: http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro/trunk/revision/210
[08:18] <jibel> salut didrocks
[08:20] <jibel> didrocks, did you update the version on the server?
[08:20] <didrocks> jibel: I didn't, I think we need to relaunch everything anyway after removing yet-another-lp-corrumption-cache
[08:20] <jibel> didrocks, which I just did
[08:21] <didrocks> jibel: there is still bzr lp-propose in the end (while doing the publishing) which can trigger this, but it's one after another, so the chance is really small
[08:21] <didrocks> sweet, let me bzr pull
[08:22] <didrocks> hum
[08:22] <didrocks> if I can connect to the machine
[08:22]  * didrocks logs out and in again from the vpn
[08:23] <didrocks> jibel: relaunching indicators now :)
[08:23] <didrocks> oh, indicator was fine
[08:23] <didrocks> ok, so oif
[08:33] <didrocks> jibel: did you see the mount issue on the autopilot job?
[08:34] <jibel> didrocks, no, which job?
[08:34] <didrocks> jibel: cu2d-misc-head-1.1prepare-autopilot
[08:35] <jibel> interesting
[08:35] <didrocks> it's the only one for now, looking at the unity ones, they are fine
[08:35] <didrocks> as the browser is stalled, I don't see where it's blocked, I would say it's when using cowbuilder
[08:35] <didrocks> as a wild guess
[08:36] <jibel> it's when it unmount the cowbuilder chroot
[08:37] <didrocks> ah, the others unity jobs are not there yet
[08:38] <didrocks> unity-lens-files is cleaning the COW dir, let's see
[08:38] <didrocks> it sounds ok
[08:42] <didrocks> jibel: should we just kill the autopilot job and relaunch?
[08:43] <jibel> didrocks, 1 minute
[08:43] <didrocks> ok :)
[08:50] <jibel> didrocks, I stopped the job and now cleaning the pbuilder
[08:50] <didrocks> thanks jibel
[08:55] <jibel> didrocks, I think the server was just overloaded, it uses 20GB of swap and a disk is full
[08:55] <jibel> not your fault :)
[08:55] <didrocks> jibel: phew ;-)
[08:55] <didrocks> jibel: otherwise I checked, and we don't use the system creds anymore :)
[08:56] <jibel> didrocks, good, I cannot unmount the cowbuilder it's owned by the kernel
[08:57] <jibel> didrocks, but i doesn't hurt to have it mounted until cowbuilder reuses the same pid
[08:57] <didrocks> jibel: interested, well I guess it can live there until next reboot, I heard that we have a lot of loop devices :-)
[08:57] <didrocks> yeah
[08:58] <didrocks> hum, glib can't be installed on armhf
[09:01] <seb128> hey desktopers
[09:01] <seb128> didrocks, lying! ;-)
[09:01] <didrocks> seb128: well, I'm sure it's a subcomponent screwing glib :p
[09:01] <didrocks> salut seb128!
[09:01] <seb128> lut didrocks ;-)
[09:05] <Laney> ello
[09:06] <seb128> Laney, hey, had a good trip back?
[09:06] <didrocks> hey Laney
[09:06] <Laney> yeah, two hour train, not too stressful ;-)
[09:06] <Laney> one of you has given me a cold though :P
[09:06] <Laney> seb128: didrocks: good travels?
[09:06] <seb128> I've been fighting to stay away from this one
[09:07] <seb128> I've somewhat of a start of running nose since friday but that didn't turn into a cold (yet)
[09:07] <seb128> seems stable so far
[09:07] <didrocks> Laney: was fine, nothing special to report apart freezing in Lille for the 30 minutes there :)
[09:07] <didrocks> no cold here ;)
[09:07] <Laney> hehe
[09:07] <Laney> you got away in time ;-)
[09:07] <didrocks> it sounds like it! :-)
[09:07] <seb128> Laney, travel was alright, left the hotel at 10am, was at London City 45min later, and at home 2.5 hours after that
[09:08] <Laney> efficient!
[09:08] <seb128> yeah, go for 1 hour flights in europe! ;-)
[09:14] <Laney> mlankhorst: enjoy it
[09:14] <seb128> Laney, "it"? I don't have backlog, I assume mlankhorst is back?
[09:15] <Laney> 24/02 11:24:42 <mlankhorst> Laney: got sig, thanks!
[09:15] <seb128> k
[09:16] <mlankhorst> hah
[09:17] <mlankhorst> ofc
[09:17] <mlankhorst> seb128: gpg sig
[09:17] <seb128> mlankhorst, hey, did you manage to catch your plane on time saturday ?
[09:18] <mlankhorst> yeah barely
[09:18] <seb128> great ;-)
[09:18] <seb128> well not for the "barely", but that it worked out
[09:21] <mlankhorst> but work again now, lets see what I missed
[09:24] <mlankhorst> noticed I woke up at 8.30, which was the same time I woke up in london
[09:25] <seb128> you are jetlagged? ;-)
[09:26] <mlankhorst> it would appear so!
[09:31] <seb128> chrisccoulson, good morning! had a nice trip back/W.E? ;-)
[09:32] <chrisccoulson> hi seb128. yeah, it was a fairly uneventful trip back. how about you?
[09:32] <chrisccoulson> i did 70km on the bike since arriving back
[09:32] <chrisccoulson> trying to burn off some of those burgers ;)
[09:32] <chrisccoulson> mlankhorst, did you get back ok? ;)
[09:32] <Laney> a real bike?
[09:33] <chrisccoulson> Laney, oh, no, i have an exercise bike in my office ;)
[09:33] <Laney> aha
[09:33] <chrisccoulson> i couldn't do 70km around here without being run over
[09:33] <seb128> chrisccoulson, my trip was ok, I was at city airport at 10:45, my plane was on time and I was back home 2.5 hours later (1 hour flights for the win)
[09:33] <chrisccoulson> heh :)
[09:33] <seb128> chrisccoulson, I did bike for an hour yesterday, but I was too tired on saturday for exercice ;-)
[09:34] <seb128> will need some diet and regular exercice this week as well, to get over all the big meals from last week ;-)
[09:34] <mlankhorst> chrisccoulson: yeah just fine, reworking my desk now so I can put on the 2 laptops again
[09:34] <chrisccoulson> seb128, yeah, me too
[09:35] <mlankhorst> how can we be joking about excercise when there was just so much (at) steak!
[09:35]  * ogra_ votes for treadmill powered laptops for the desktop team :)
[09:36] <Laney> hah
[09:36] <mlankhorst> I want mine to be bike powered!
[09:36] <Laney> my "road bike" fund is nearly full enough :-)
[09:36] <ogra_> well, the point is that our powermanagement would improve in no time ;)
[09:41] <mlankhorst> hm going through my administration, I got a receipt for €0,00 at a gas station
[09:42] <Laney> you europeans with your socialised petrol
[10:02] <mlankhorst> I did get a whole 0.00l though!
[10:02] <czajkowski> morning
[10:03] <mlankhorst> morning
[10:16] <mlankhorst> is czajkowski a common surname? my sister is sometimes performing pieces on her violin from czajkowski
[10:17] <czajkowski> mlankhorst: I think so, or at least I'm told by Polish people it is.  It's not so common in Ireland where I'm from.
[10:18] <seb128> czajkowski, hey ;-)
[10:18] <czajkowski> seb128: morning
[10:18] <czajkowski> found another one over the weekend, suspend resume no longer works :(
[10:18] <mlankhorst> ah, I just had to ask! every time I saw your nick I kept wondering :)
[10:19] <czajkowski> heh no worries
[10:19] <czajkowski> I'm Irish although I now live in England for the last 2.5 years.
[10:39] <mlankhorst> ah :)
[10:42] <pitti> bonjour seb128, ça va? est-ce que tu as arrivé à maison à nouveau?
[10:43] <seb128> pitti, salut, ca va bien ! oui, samedi, le voyage était cours, 1h de vol de Londres ... moins de 5h de l'hotel à chez moi au total
[10:44] <pitti> seb128: cinq heures est rapide, en effet
[10:46] <seb128> pitti, et toi, tu as passé un bon W.E ?
[10:46] <pitti> seb128: est-ce que tu manque boire de biére déjà ? :-)
[10:47] <pitti> seb128: oui, nous avons vu un match de football et joué de badminton
[10:51] <seb128> pitti, non, j'ai bu assez de bière pour un mois ;-)
[10:52] <seb128> pitti, les copains de mon équipe me manquent déjà par contre :-(
[10:52] <pitti> lol
[11:03] <didrocks> interesting, bzr diff <whatever> always exit with 1
[11:08] <pitti> didrocks: well, 0 == no diff, 1 == there is a diff
[11:08] <pitti> just like "diff" itself
[11:09] <didrocks> pitti: never noticed that. I change my mock then for my test to detect if bzr isn't happy :)
[11:51] <seb128> chrisccoulson, did you see any recent complain about webapps making firefox hang? that started today
[11:51] <seb128> well for me
[11:52] <seb128> chrisccoulson, not sure if I got unlucky or something, I blame webapps because gdb on firefox shows it's stucked in dbus calls to webapp stuff
[11:52] <chrisccoulson> seb128, i've not. the only thing on my radar is an imagelib crash, which i suspect is my addon: https://crash-stats.mozilla.com/report/index/5e2d4480-3843-4c25-9c2b-e227f2130223
[11:52] <chrisccoulson> there's a lot of these
[11:53] <chrisccoulson> not sure why they only appeared after release :/
[11:54] <seb128> chrisccoulson, those hangs look like http://paste.ubuntu.com/5564485/
[11:55] <chrisccoulson> gaaaaaaaaaaaaahhhhhhh
[11:55] <chrisccoulson> nested event loop!
[11:55] <chrisccoulson> i told them about not spinning the event loop
[11:55] <chrisccoulson> although that's probably not the cause of your hang ;)
[11:55] <seb128> :-(
[11:55] <chrisccoulson> but it's bad in any case
[11:55] <chrisccoulson> from a security POV
[11:56] <seb128> chrisccoulson, let me know if you have interested by debug infos on that at some point
[11:56] <seb128> I've to turn it off, it keeps hanging on launchpad for me today
[11:56] <seb128> if it's only me it's ok though
[11:56] <chrisccoulson> seb128, i'm interested in the rest of the stack (to see if there's any untrusted script on it)
[12:02] <seb128> chrisccoulson, http://paste.ubuntu.com/5564501/
[12:02] <seb128> chrisccoulson, will download debug symbols while I eat
[12:03] <chrisccoulson> thanks
[12:31] <chrisccoulson> hmmmmm, i'm hungry
[12:41] <seb128> chrisccoulson, unping about this hang issue
[12:42] <seb128> chrisccoulson, my system/dbus was in a weird state, calls were hanging, not only in firefox
[12:42] <seb128> chrisccoulson, it's all fine after a reboot
[12:46]  * Sweetshark reads backlog.
[12:46] <Sweetshark> ogra_: Sure. You get to treadmill for the LibreOffice builder laptop!
[12:47] <ogra_> heh
[12:47] <ogra_> Sweetshark, as long as it has an arm CPU ...
[12:49] <mlankhorst> ogra_: planning to run a marathon?
[12:50] <ogra_> haha
[12:50] <ogra_> suuuree ....
[12:50] <ogra_> <- chainsmoker
[12:51] <Sweetshark> ogra_: ARM? Sure! How about some 60 quad-cores?
[12:52] <ogra_> yeah, would likely a rather thick laptop though
[13:02] <lool> dpkg: erreur de traitement de /var/cache/apt/archives/gtk2-engines-pixbuf_2.24.16-1ubuntu1_amd64.deb (--unpack) : tentative de remplacement de « /usr/share/doc/gtk2-engines-pixbuf/README.gz », qui est différent d'autres instances du paquet gtk2-engines-pixbuf:amd64
[13:03] <seb128> lool, I saw some reports about that earlier today, pretty weird
[13:05] <Laney> laney@iota> sha512sum amd64/usr/share/doc/gtk2-engines-pixbuf/README.gz c-i386/usr/share/doc/libgtk2.0-common/README.gz               ~/temp
[13:05] <Laney> fb2e75b0595384dc5dea7d9e0bceef920bff0d02b6593d6988abbe5619cba066b631d9ba1988c2f0655d7a7ef351ceb67bc771901475a0c77164346a9dec015c  amd64/usr/share/doc/gtk2-engines-pixbuf/README.gz
[13:05] <Laney> fb2e75b0595384dc5dea7d9e0bceef920bff0d02b6593d6988abbe5619cba066b631d9ba1988c2f0655d7a7ef351ceb67bc771901475a0c77164346a9dec015c  c-i386/usr/share/doc/libgtk2.0-common/README.gz
[13:05] <seb128> Laney, well
[13:06] <seb128> both are supposed to be a symlink to the file contained in -common
[13:06] <lool> seb128: amd64/usr/share/doc/gtk2-engines-pixbuf/ has a real file
[13:06] <Laney> yeah
[13:06] <lool> seb128: i386/usr/share/doc/gtk2-engines-pixbuf/ has a symlink
[13:06] <Laney> amd64 is real, i386 not
[13:06] <seb128> I wonder why
[13:06] <seb128> seems like a bug in pkgbinarymangler
[13:06] <seb128> or cdbs
[13:07] <seb128> which one is doing those symlinks again?
[13:07] <lool> both might be
[13:07] <seb128> oh, maybe not
[13:07] <lool> I suspect it's a build system bug, one is the binary-indep build while the other isn't
[13:07] <lool> I guess when one builds the -doc package, there's a symlink to it
[13:07] <seb128> I don't think the symlink magic works through archs
[13:07] <lool> and if one doesn't (amd64) there isn't
[13:07] <seb128> right
[13:07] <seb128> but that's nothing new there
[13:08] <seb128> I wonder why it started missbehaving in this update
[13:08] <lool> pkgbinarymangler didn't change in ages
[13:08] <seb128> lool, can you grep gtk2-engines-pixbuf /var/log/dpkg.log ?
[13:08] <seb128> lool, did you have a gtk2 update from a ppa before the official one?
[13:09] <seb128> I wonder if we got the same version upload done in a ppa and the archive and that confused things
[13:09] <tkamppeter> mlankhorst, hi
[13:09] <lool> there was a change in the dependencies
[13:09] <lool>  Depends: ${misc:Depends},
[13:09] <lool> -         @SHARED_PKG@ (>= ${source:Version}),
[13:09] <lool> +         @SHARED_PKG@ (= ${binary:Version}), @COMMON_PKG@
[13:09] <lool> seb128: I didn't get an update from a PPA AFAIK
[13:10] <lool> I don't see it in apt-cache policy at least
[13:10] <seb128> lool, I had a version in the ppa but it was using a ~build so it's not it
[13:10] <lool> all changes are from today
[13:10] <mlankhorst> tkamppeter: hello
[13:10] <lool> previous changes from 10th of Jan
[13:10] <tkamppeter> mlankhorst, I have booted the SD card we have set up on Friday on my Pandaboard ES and I get two sound outputs where one is HDMI and with the I get the sound correctly. Video is still choppy though.
[13:12] <mlankhorst> you get better video with unity 2d
[13:12] <mlankhorst> youtube won't work, however
[13:13] <lool> -DH_INSTALLDOCS_FILES := NEWS README ChangeLog
[13:13] <lool> +DH_INSTALLDOCS_FILES := NEWS README AUTHORS
[13:13] <lool> don't see how that relates though
[13:13] <lool> also:
[13:13] <lool> -	dh_builddeb -i
[13:13] <lool> +	dh_builddeb -i -- -Zxz
[13:14] <lool> seb128: ah found it
[13:14] <lool> -	dh_compress -s -X.sgml -X.devhelp -XNEWS -Xchangelog.Debian -XREADME
[13:14] <lool> +	dh_compress -s -X.sgml -X.devhelp
[13:14] <seb128> lool, see #ubuntu-devel :p
[13:14] <seb128> lool, sorry, moved there because we have people like cjwatson who are not on -desktop
[13:14] <lool> seb128: Discovered at the same time  :-)
[13:15] <seb128> lool, great minds... ;-)
[13:57] <lool> seb128: The whole doc handling in gtk+ in Debian is messy I'm afraid
[14:00] <seb128> lool, yeah, I wouldn't spend time on sorting the details out or cleaning that, let's just figure what's the bug is and fix it
[14:00] <seb128> lool, Laney is looking at it
[14:03] <tkamppeter> mlankhorst, unity-2d is better but still choppy, only way is starting XBMC as desktop, but XBMC often hangs and I have to reboot.
[14:04] <mlankhorst> well sounds about right, totem works for me mostly
[14:04] <mlankhorst> anything on serial console though?
[14:04] <mlankhorst> and what is /proc/cmdline
[14:22] <tkamppeter> mlankhorst, /proc/cmdline is 'ro elevator=noop vram=40M root=UUID=8355041e-c774-4260-b392-fb78f655d692 fixrtc quiet splash smsc95xx.turbo_mode=N'
[14:23] <tkamppeter> mlankhorst, serial console I did not observe during boot.
[14:24] <mlankhorst> just add console=ttyO2,115200n8 to /boot/boot.script and rerun flash-kernel iirc
[14:40] <seb128> pitti, hey, do you plan to add the gdk-pixbuf autopkgtest to debian? it's one of the only diff we have with Debian on that sort (the other one a small change on the libtiff b-d until debian transitions to 5 as default)
[14:41] <pitti> seb128: oh, didn't I?
[14:41] <pitti> seb128: I did, it's in svn
[14:41] <seb128> pitti, hum, ok, I wonder what pochu used to upload the new serie to experimental then
[14:42] <seb128> pitti, he uploaded yesterday and those are not in
[14:42] <pitti> oh, it's in the unstable branch
[14:42] <seb128> I see
[14:42] <pitti> I didn't look for/commit to an experimental branch
[14:42] <seb128> that explains it
[14:43] <pitti> so when he branched, he didn't branch off unstable tip, but from 2.26.1-1 apparently
[14:43] <seb128> pitti, [2012-10-23] Accepted 2.26.4-1 in experimental (low) (Simon McVittie)
[14:43] <seb128> pitti, I guess the experimental branch is there for a while
[14:43] <seb128> they just didn't keep both in sync
[14:43] <seb128> well in fact there has been no upload to unstable since 2.26.1-1
[14:53] <pitti> seb128: I merged the autopkgtest into the exp branch, too
[14:55] <seb128> pitti, thanks!
[14:57] <tkamppeter> mlankhorst, I edited boot.script, reflashed the kernel and rebooted with the serial USB adapter connected. No output with "sudo screen /dev/ttyUSB0".
[14:57] <mlankhorst> needs screen /dev/ttyUSB0 115200
[15:05] <tkamppeter> mlankhorst, I tried this now and rebooted again, nothing appears. Seems that the serial of my Pandaboard is broken. The adapter works as I have used it in London during our installation.
[15:05] <mlankhorst> tkamppeter: no uboot either?
[15:34] <tkamppeter> mlankhorst, nothing, not even u-boot.
[15:35] <mlankhorst> hm :/
[15:37] <tkamppeter> mlankhorst, generally, for multimedia it is best to start XBMC as the desktop environment, this is the only way to fluently play full-HD videos from a locally connected USB stick. The video add-ons of XBMC usually play their internet videos fluently, too, but some do not work at all, like YouTube (on a normal PC XBMC works perfectly, also started from the desktop). When XBMC is working correctly, only ~500 MB from the GB of RAM are us
[15:37] <tkamppeter> ed.
[15:55] <ogra_> tkamppeter, which release is that ?
[16:26] <Laney> ah
[16:26] <Laney> dh_compress overwrites the symlinks with the real docs because we also install them
[17:23] <gema> seb128, ogra_: we have a question for you, guys, we are trying to figure out what kind of charts you'd need if you saw a regression in memory consumtion and are kind of stuck between the myriad of options, so if you guys could give us some hints that'd be good
[17:23] <gema> seb128, ogra_: this is what we have now: http://91.189.93.67/staging/memory/arch/amd64/
[17:24] <gema> lool: ^
[17:24] <gema> so say you spot a regression in today's result, what kind of chart you'd need to be able to figure out what's wrong?
[17:24] <gema> or what kind of chart would be useful?
[17:25] <lool> gema: Im surprized by the variance day to day
[17:25] <lool> by tens of MiB each day
[17:25] <gema> lool: we are working on that, we were running 3 times, now we've increased to 20, but it'll take time to build some data to see how good it is
[17:26] <lool> I see
[17:26] <gema> lool: but now we are trying to think of what else we need to gather in terms of information, so that we can build the right diagnostic/triaging charts
[17:27] <gema> lool: we have one bar there with 20 results I think , so it'll take a week or so to see if it is better
[17:27] <gema> or how much better it is, rather
[17:27] <gema> lool: a good thing is that pss total and meminfo give us more or less the same shape
[17:28] <gema> lool: so pss is a good estimation of consumption
[17:28] <lool> gema: First, I think this is generally a nice graph, albeit it doesn't allow diving into issues
[17:28] <lool> gema: So how do I know which app started using more memory?
[17:29] <lool> gema: Second, I think the context so far was on desktop memory usage, but this is wrong now
[17:29] <lool> gema: I think we want to focus on Ubuntu Touch memory usage
[17:29] <gema> lool: you can click on detailed view and choose which run you want to look at
[17:29] <lool> which will come with a different way to manage applications
[17:29] <lool> for instance applications will be stopped or killed entirely if in the background
[17:29] <lool> gema: detailed view > ah sorry
[17:30] <gema> lool: once we figure out what kind of charts we need, we can even run it on windows if you want
[17:30] <lool> gema: detailed view is nice, but it's hard to compare from one day to the other
[17:30] <gema> lool: it is the kind of information we need charted that's eluding us
[17:30] <gema> lool: exactly, so how do we make it easier?
[17:30] <lool> gema: could you graph by Command or something?
[17:30] <gema> lool: all of them?
[17:30] <lool> gema: the top level view is good to decide whether there's a system-wide regression or not
[17:30] <lool> but per-app view would allow understanding where it comes from, or even catching trends on one app
[17:31] <lool> gema: Can we generate them on demand?
[17:31] <gema> lool: we can do whatever we need, we just don't know how to present the information right now
[17:32] <josepht> lool: we can't generate them on demand now, we'd have to add aggregation support for each process
[17:33] <gema> lool: josepht is the person from our team actually coding the dashboard
[17:33] <gema> lool: one of them
[17:34] <gema> lool: I think we need guidance and your input during the development of these views, so that they are truly useful
[17:34] <gema> lool: also, if we make improvements on some areas but regress in others, we won't be able to flag problems , and I'd like to be able to flag problems there as well
[17:43]  * lool (OTP)
[17:44] <Laney> think I've got a fixed gtk2
[18:08] <jbicha> Laney: thanks, yes I dropped the dh-compress -X diff because I didn't think it was still an issue and I thought the remaining diff there was unintentional because of https://launchpad.net/ubuntu/+source/gtk+2.0/2.24.10-0ubuntu3
[18:09] <bcurtiswx> kenvandine, may i PM you?
[18:09] <Laney> not sure why it's not present in experimental
[18:09] <Laney> jbicha: could you apply the diff in svn?
[18:10] <Laney> s/in/to/
[18:10] <jbicha> see this is why I don't like touching GTK, I'm afraid I'll break something ;)
[18:11] <kenvandine> bcurtiswx, of course
[18:24]  * didrocks waves good evening
[18:45] <lool> gema, josepht: Sorry
[18:45] <lool> gema, josepht: was OTP
[18:46] <lool> gema, josepht: so overall the general idea is to be able to detect regressions in memory usage and ensure that we're in the budget
[18:46] <lool> gema, josepht: regressions can either be system wide (over budget) or app specific
[18:47] <lool> gema, josepht: when we're faced with the overall memory usage going too high, we should raise a red flag and the app specific measures will help pin point where it's coming from, or which apps to attack first to try to save memory
[18:47] <lool> gema, josepht: but it would also be nice to raise a red flag is specific apps are leaking or start ballooning in memory usage
[18:48] <lool> gema, josepht: the main difference between when we discussed this and now is that the main target for applying this are phablet images, and memory usage patterns are quite different there; we also want to apply them to core apps
[18:49] <lool> in my ideal world, memory usage issues (leaks, too high memory usage) are flagged / pushed to developers which can checkout the graphs to get a basic overview, and then can attack debug / diagnose per app on their systems
[18:55] <gema> lool: so maybe we should have a list of apps we want to track
[18:56] <gema> lool: and draw graphs for those?
[18:57] <gema> lool: anyway, way over your EOD, we can continue this chat tomorrow morning if you want
[18:57] <gema> and brainstorm a bit about the best way of doing this
[18:57] <gema> maybe also grab seb128's ideas and see where we go from there
[18:57] <gema> I need to understand how developers are going to use these results if we are going to be giving them in the right format
[18:58] <gema> any other ideas from anyone in the channel are also welcome if you guys have specific use cases in mind!
[19:16] <rickspencer3> seb128, my LightDM wallpaper thing ...
[19:17] <rickspencer3> when I first made the image the background from firefox, how was that world readable?
[19:33] <GunnarHj> Anybody there who can help with a (probably) easy package question?
[19:39] <seb128> back from dinner
[19:41] <seb128> gema, sorry, I was in a phone, didn't read the full backlog but my idea was to flag when usage increase from a noticeable amount ("noticeable" needs to be defined according to the variance in your measures)
[19:41] <seb128> gema, then to have a "by process" table and flag things that increased
[19:42] <gema> seb128: can you think about what you mean by "by process" table?
[19:42] <gema> seb128: would this be one table per process over time, or one table with all the process and if so, what kind of chart, etc
[19:43] <seb128> gema, it would be the equivalent of the smem list, where you record the values every day, and flag when some process jump compared to its previous value
[19:44] <seb128> gema, where "jump" would be any increase out of the margin of errors or the fluctuation of the measurement
[19:47] <seb128> jbicha, your gtk upload screwed the desktop team ppa as well which already had 2.24.16 btw...
[19:47] <seb128> rickspencer3, I can try to blame it on firefox? not sure chrisccoulson will like me for it :p
[19:48] <GunnarHj> seb128: Hi Seb, time for a tiny package question?
[19:49] <seb128> GunnarHj, don't ask to ask, just ask ;-)
[19:49] <GunnarHj> Ok.
[19:49] <GunnarHj> While im-config is a 3.0 (native) package, we have a couple of Ubuntu specific things. If we in debian/rules do something like
[19:49] <GunnarHj>     if [ (Ubuntu) ]; then
[19:49] <GunnarHj>         dh $@ --with quilt
[19:49] <GunnarHj>     else
[19:49] <GunnarHj>         dh $@
[19:50] <GunnarHj>     fi
[19:50] <GunnarHj> we could go back to use exactly the same package and let auto sync do its job. How do you safely check for Ubuntu or Debian in that context?
[19:50] <jbicha> seb128: ok I didn't realize other people were working on the update, I guess I should coordinate with you for GTK updates in the future?
[19:52] <seb128> jbicha, that would be good, I should perhaps have pushed in the vcs
[19:52] <seb128> jbicha, we were trying to land the unity-menu work (dropping the gtk patch) last week
[19:52] <seb128> so I had 2.24.16 without the menu patch in the ppa, which got broken by your update
[19:53] <seb128> but that's ok, I will fix it ;-)
[19:53] <seb128> GunnarHj, use dpkg-vendor
[19:54] <jbicha> the new GTK2 was needed for the gnome-themes-standard update (too bad GNOME stable updates aren't afraid to bump dependencies)
[19:54] <seb128> GunnarHj, see gnome-disk-utility
[19:54] <seb128> if you need an example
[19:54] <seb128> if dpkg-vendor --is ubuntu; then
[19:55] <GunnarHj> seb128: Thanks, that's all guidance I need.
[19:56] <seb128> GunnarHj, yw!
[19:57] <seb128> Laney, thanks for fixing that gtk update bug!
[20:00] <GunnarHj> seb128: Btw, does "dpkg-vendor --is ubuntu" include all the derivatives (Xubuntu, Kubuntu etc.)?
[20:01] <seb128> "include"?
[20:01] <seb128> it will return "ubuntu" for any *buntu
[20:02] <seb128> those are just flavors or ubuntu
[20:02] <seb128> there is a --derives-from flag if you need more granularity, though I'm not sure if e.g xubuntu override their infos to specify a derivative distro
[20:07] <GunnarHj> seb128: No, I do want all the *buntus to be included. Just not Debian. So that will be fine.
[20:08] <seb128> GunnarHj, great
[20:50] <coolroot> http://paste.ubuntu.com/5564842/ it's my laptops distro in a serious messed up :(
[20:56] <thumper> morning
[20:58] <rickspencer3> jasoncwarner_,  etc... check this out
[20:58] <rickspencer3> http://ubuntuone.com/3K9SaShOuKmik6TtONjtHC
[20:58] <chrisccoulson> ugh, i got a scare when i saw bug 1008409 in my inbox, and thought our crazy friend was back again
[20:58] <ubot2> Launchpad bug 1008409 in firefox (Ubuntu) "launchpad, boot sector keyboard hijacked in "alicia" account" [Undecided,Invalid] https://launchpad.net/bugs/1008409
[20:58] <chrisccoulson> mdeslaur ;)
[20:59] <mdeslaur> chrisccoulson: hahaha :P
[20:59] <jasoncwarner_> rickspencer3: that looks completely normal and not at all unexpected. Or, rather, looks like we might have a font issue ;)
[20:59] <rickspencer3> I logged bug #1132985
[20:59] <ubot2> Launchpad bug 1132985 in nautilus (Ubuntu) "Media Inserted Dialog is Lacking Fonts" [Undecided,New] https://launchpad.net/bugs/1132985
[20:59] <jasoncwarner_> thanks, rickspencer3
[20:59] <rickspencer3> jasoncwarner_, pgraner got the same issue with a different dialog though
[21:03] <coolroot> http://paste.ubuntu.com/5564842/ it's my laptops distro in a serious messed up :(
[21:06] <Sweetshark> bdrung: https://bugs.freedesktop.org/show_bug.cgi?id=61246#c2 <- Argh, severe bug! paper in printer tray doesnt follow gtk theme colors!
[21:06] <ubot2> Freedesktop bug 61246 in framework "CONFIGURATION: document background is white, even if desktop theme uses other color" [Normal,Resolved: notabug]
[21:07] <bdrung> Sweetshark: yes. i saw this bug report, too. don't you have black paper just in case that you want to print white on black? ;)
[21:12] <Sweetshark> bdrung: congratulations on getting http://xkcd.com/1172/ on your first LibreOffice commit. Usually it takes three commits for that (two if working on file format import/export).
[21:14] <bdrung> Sweetshark: :) breaking a workflow is not a big deal. breaking a workflow without giving another workflow as alternative is an issue.
[21:20] <jbicha> Sweetshark: my first LO bug hit that problem but it got fixed anyway https://bugs.freedesktop.org/show_bug.cgi?id=35313
[21:20] <ubot2> Freedesktop bug 35313 in UI "[Task] Improve Hyperlink Bar" [Enhancement,Resolved: wontfix]
[21:24] <TheMuso> Hey folks.
[22:23] <coolroot> http://paste.ubuntu.com/5564842/ need help pls?
[22:25] <sarnold> hunh. why does your update-grub try to parse /etc/grub.d/README as a command file? o_O