[00:35] RAOF, thanks for looking at bug 903973 :) [00:35] Launchpad bug 903973 in xorg-server "gnome-settings-daemon crashed with signal 5 in _XReply()" [High,In progress] https://launchpad.net/bugs/903973 [00:36] chrisccoulson: I'm a bit surprised that Peter didn't apply your patch as written; *everything* that calls dixLookupWindow seems to be broken. [00:37] RAOF, yeah, i did wonder that at the time, but never thought to argue about it :) [00:37] and then i'd forgotten about the whole issue until seb asked me to look at this bug today [00:38] :) [00:38] * RAOF builds his patched server [00:38] It's non-trivial to reproduce that problem, isn't it. [00:42] RAOF, yeah, i can't reproduce it here on my machine. when we had similar issues before, it was always at session start [00:42] Yeah. I won't bother whipping up testing packages; I'll just submit the patches to the list. [00:43] but i'd imagine that the trigger is rapidly creating and destroying a window, and then creating a pixmap straight afterwards [00:43] with multiple keyboard layouts enabled [00:43] Yeah, such as might occur during startup. [00:43] yep :) [00:43] Technically it could happen at pretty much any time; yay for asynchonous protocol! [00:43] heh [01:01] yo. [01:58] robert_ancell: poke [01:59] smspillaz, hey [01:59] robert_ancell: hi [01:59] robert_ancell: I think you forgot to check in a file to xig [01:59] make[2]: *** No rule to make target `hello.c', needed by `hello-hello.o'. Stop. [02:00] hello hello! [02:00] :) [02:00] sorry about the immcounicado for a while, got pulled off into another direction with the google test stuff. but I have a standalone window manager module thats mostly working now [02:00] so I'm going to start adding xig tests for it [02:01] nice [02:02] but ... first I need to be able to compile the thing ;-) [02:04] smspillaz, pushed [02:04] pushing.. [02:04] :) [02:04] now pushed [02:08] thanks, all works now [02:15] robert_ancell: was xig-version.h removed ? [02:16] hmm, perhaps its not installed [02:16] hang on [02:18] robert_ancell: yeah, you need to add xig/xig-version.h to libxig_0include_HEADERS in xig/src/Makefile.am [02:18] whoops [02:19] I can propose a branch if you want [02:19] smspillaz, just pushed a fix [02:19] ok [02:19] thanks [02:19] robert_ancell: also, I guess xig_remove_client_set_log_messages has changed ? [02:19] err [02:19] *remote client [02:20] smspillaz, yes, there are signals for the messages, and you connect up the logger class if you want to log them [02:20] ok [02:20] * smspillaz adjusts test-runner.c for that then [03:54] robert_ancell: hmm. has some stuff changed recently in xig? I seem to be getting libX11 assertion failures about the loss of event sequencing [03:54] I can have a look into whats going on if you want [03:54] smspillaz, nothing should have changed drastically - can you send me a test case? [03:56] robert_ancell: run compiz on it :) [03:56] I can see if there's a particular thing that's triggering the bug though .. I'll run with XSynchronize [04:00] oh, bluez, how I love you... [04:13] robert_ancell: hmm, well, it seems to get a SIGPIPE every time it tries to send a PropertyNotify [04:18] robert_ancell: maybe I can bisect to see what was causing the problem? I don't know the xig code that well [04:19] smspillaz, worth trying - does it definitely work with the older version? [04:20] there were problems with the older version too, but I'm not sure if they were the same ones really [04:49] robert_ancell: hmm, it seems like a commit that broke the build was introduced at 136, so I can't bisect :( [04:50] ugh [06:47] Good morning [06:54] pitti, feeling better yet? [06:54] slightly, thanks [07:05] good morning [07:08] Morning pitti, didrocks. [07:15] hey TheMuso, happy new year! how are you? [07:15] bonjour didrocks [07:16] good morning TheMuso, happy new year! [07:16] guten morgen pitti. Are you feeling better today? [07:16] didrocks: quite a bit better, thanks [07:17] pitti: Well thanks, not sure if I feel frefreshed or not after my break, probably because I have to travel barely 4 days after I get back from my break. :) [07:17] good morning pitti, didrocks [07:17] good evening TheMuso [07:18] bonjour rickspencer3, ca va? [07:18] ça va bien, et toi [07:18] ? [07:18] Hey rickspencer3. [07:18] Anyway, bbl. [07:18] rickspencer3: Je suis encore froid, mais c'est mieux [07:19] pitti, ah tu est enhrume encore? je comprendre [07:20] je suis content que tu vas mauvais [07:20] rickspencer3: ^ at this point both google translate and me give up :) [07:20] lol [07:20] pitti, you were quite comprensible [07:22] hmmm [07:23] maybe in the future we should organize sprints with 2 sites, one in Australia and one in NA/Europe so people like TheMuso and robert_ancel and RAOF, etc... don't get quite so hard in the teeth [07:26] rickspencer3: I don't want special treatment, but I am not a fan of traveling, the flying in particular. I enjoy the events/getting together with everyone during the week, but its the travel itself that gets me down. [07:27] But, thats part of the job. [07:27] Really afk now. [07:27] TheMuso: good night! [07:29] rickspencer3: ahem [07:29] rickspencer3: 30 hours wooooooooooooooooooooooooo! [07:29] rickspencer3: I think its quite awesome that we get to travel so much [07:30] bonjour rickspencer3 :) [07:30] hey didrocks [07:30] 08:20:07 rickspencer3 | je suis content que tu vas mauvais [07:30] pitti: I won't like that if I were you :) [07:30] hey smspillaz [07:31] didrocks: sounds like "I'm happy that you are wrong" or so? [07:31] exactly :) [07:31] if "content" is the same as in English [07:31] ah, rickspencer3 meant froid -> enrhume ? [07:32] (it's "j'ai pris froid", but understandable) [07:32] you "take" the cold (for no good reason ;)) [07:33] je ne parlez pas francais! [07:33] Deutsch ist viel einfacher [07:33] anyway, off to killing more useless stuff during boot; next up: notify-osd [07:33] well, you really don't want to challenge the German that I have :) === agateau_ is now known as agateau [08:12] good morning everyone! [08:12] pitti: apropos deutsch http://nabble.documentfoundation.org/Introducing-Grande-Latte-td3632391.html [08:13] :) [08:13] hey Sweetshark, guten Morgen [09:03] hey pitti I'm not surprised that my terrible French broke Google Translate for you, sorry ;) [09:16] hey [09:16] bonjour seb128 [09:16] hey pitti, how are you? getting over the cold? [09:17] seb128: quite fine, thanks! still congested nose and some coughing, but feeling a lot better [09:17] * pitti is this --><-- close to killing notify-osd at boot :) [09:18] meh, lots of packages failing to build now due to deprecated GTK stuff (VBox and the like) [09:18] (nautilus) [09:18] for indicator-sound I reported a bug upstream and build without -Werror [09:18] pondering to do the same for nautilus [09:19] released versions shouldn't use G*_DISABLE_DEPRECATED or Werror [09:19] or we keep running into such issues :-( [09:19] it's the nautilus that's in bzr, i. e. in current precise [09:19] upstream trunk actually builds fine ;) [09:20] right, I exepect they updated the new serie for the new glib and gtk [09:20] pitti, we should just drop the disable deprected for precise, or at least we should disable them even if we fix the issue or we will keep playing catchup on deprecation with every gtk update [09:21] but weird, I built nautilus yesterday here and I've the new glib and gtk installed [09:21] hm, maybe I mislooked, hang on [09:22] (need to change something in the backporting of the trunk patch) [09:22] salut seb128, ça va? [09:23] didrocks, lut, très bien, et toi ? [09:23] seb128: ça va bien :) [09:24] seb128: sorry, just read it wrongly, builds fine [09:24] indicator-sound was real, I dropped the -Werror in our package there [09:26] pitti, right, I had that discussion with dx before [09:30] pitti, note that GNOME doesn't start nautilus with their session, but still a bug and something they can fix ;-) [09:30] seb128: right; my patch is working, sending to upstream and applying in our package [09:30] with these two, notify-osd is gone in both lightdm and the session [09:30] great [09:35] so, that's gsd-printer and notify-osd, next to kill: gnome-screensaver :) [09:36] although we could win a lot more by killing this weird "compiz" process; it eats CPU for breakfast!!11! [09:37] pitti, +1 [09:37] good morning everyone [09:38] hey chrisccoulson, bryceh_ [09:38] how are you? [09:38] heya seb128 [09:38] woohoo, no more gconf dependency in upstream firefox builds: https://hg.mozilla.org/integration/mozilla-inbound/rev/04244dc1f498 :) [09:38] seb128, yeah, good thanks. how are you? [09:38] hey chrisccoulson [09:38] chrisccoulson: \o/ [09:39] seb128, I'm fine. Family is a bunch of sickies though. [09:39] pitti: you start notify-osd only on demand then? (just curious) [09:39] chrisccoulson: dropping gtk2 _and_ gconf? rad! [09:39] didrocks: yes, as it's meant to be [09:39] chrisccoulson, I'm good thanks ;-) [09:39] chrisccoulson, no gconf \o/ [09:39] pitti: nice! :) [09:39] didrocks: but indicator-sound and nautilus queried the server caps right at startup; I changed that to lazy init [09:39] ah ok ;) [09:40] screensaver's autostart .desktop has X-GNOME-Autostart-Delay=5 [09:40] but it's started at the very beginning, presumably triggered through dbus [09:41] right, that's likely [09:41] it would probably be okay to start it 10 or 20 seconds into the session [09:41] seb128, maybe I'm providing the ubuflu shipment this year 8-} [09:41] bryceh_, what I was thinking! [09:41] bryceh_: argh, you too? mine should be gone right in time for Budapest [09:42] well I'm just out of a cold so with some luck I will not get another one [09:42] no hugs for bryceh_ this time! [09:42] pitti, no I'm well at the moment. but both kids and wife have it. [09:42] oh, bingo! i know why the firefox IPC tests are failing now [09:42] seb128: if only there weren't ~ 250 different kinds of cold viruses.. [09:42] let's see if my body has built enough defences to avoid getting something else ;-) [09:42] the child process quits with "Maximum number of clients reached" [09:42] pitti, no kidding. [09:42] pitti, yeah, people coming from around the world doesn't help :-( [09:42] now i need to figure out what's stealing all my X connections! [09:42] with 2 colds a year it takes a lifetime to get immune against the more common half [09:43] fortunately what my kids have seems to be relatively mild; they've still been bouncing off the walls when not busy coughing. [09:43] hehe [09:44] on a separate topic, my mother upgraded herself from natty to oneiric and discovered unity [09:44] so today involved giving my mother some unity lessons [09:44] still not simple enough? ;-) [09:44] or just "how to work better with it"? [09:45] hm, wikipedia says "more than 200 known viruses"; I thought I read a more exact number somewhere [09:46] seb128, half and half. [09:46] pitti, too many to be well covered in any case :-( [09:47] bryceh_, was the experience mostly positive? what did she like,dislike? [09:47] seb128, main issue was she likes this ancient windows card game, which requires wine to run, and the gnome-panel icon I'd made for her didn't survive the upgrade [09:47] so got to learn how to make custom launchers :-) [09:48] that should be fixed this cycle with some luck [09:48] design recommended that we package and ship https://launchpad.net/unity-launcher-editor by default [09:49] seb128: at least, the older we get the fewer colds we should get [09:49] pitti, indeed [09:50] seb128, she had trouble figuring out how to close programs (since the window decorations get hidden), and had trouble finding how to launch programs. So most of the tutoring was for how to do those two things. [09:51] seb128, her first computer was my Commodore 64, so to her this was just yet another UI to have to learn, I think she was neutral on it over all [09:52] seb128, oh, the one regression that she definitely disliked was losing the picture slideshow screensaver. I had her set up with pics of my kids which she adores, so she definitely misses that. [09:52] yeah, the screensaver stuff is unfortunate [09:53] but I figure it should be trivial to write a little slideshow tool to workaround that [09:53] ok, it's g-s-d's libpower.so [09:56] looks fixable [09:58] pitti - libpower.so starting notify-osd? [09:58] chrisccoulson: no, gnome-screensaver [09:58] ah, ok [09:58] chrisccoulson: notify-osd is already fixed [09:58] cool [09:58] pitti - the power plugin could probably do with some of the notification related fixes we used to carry in gnome-power-manager [09:59] (particularly with regards to notification priority and duration) [09:59] i could probably fix those though [09:59] is there something particular which works the wrong way ATM? [09:59] I seldomly see the "low battery" stuff [10:00] pitti - yeah, the critical notification appears as the fallback dialog (complete with "Ok" and "Cancel" button) [10:03] bryceh_, is there any way to find out what's using up all of my X connections in https://launchpadlibrarian.net/89118807/buildlog_ubuntu-lucid-amd64.firefox-trunk_12.0~a1~hg20120103r83671-0ubuntu1~umd1~test_BUILDING.txt.gz ? [10:03] (i'm using xvfb) [10:05] chrisccoulson, hmm, interesting. There are several tools... let's see. xrestop tells how many clients there are [10:06] wmctrl -l will give you a list of windows [10:07] bryceh_, thanks [10:08] yeah I'd try those first. beyond that not sure, but the info is there in the server for querying [10:09] chrisccoulson, xtrace also can be handy if you have a suspicion what specific client may be at fault [10:10] bryceh_, yeah, i'm not sure yet. i'm just seeing "Maximum number of clients reached\n(:22600): Gtk-WARNING **: cannot open display: :99" on the first test which requires an X connection [10:12] chrisccoulson, intriguing. Well, I'd guess a particular client has a flaw that causes it to iteratively make connections until it's used them all up [10:12] I think there's only like 127 or 255 permitted, it's not too difficult to exhaust them [10:13] chrisccoulson, a test suite which opens a connection per test and is sloppy at closing them could do it [10:25] bryceh_, oh, does Xvfb not do any access control? :/ [10:26] chrisccoulson, it may not, it's fairly primitive [10:26] i wonder if something else on the builder connects to it ;) [10:26] the problem is only reproducible on the builders [10:27] another factor is the builders are running an older release [10:28] chrisccoulson, but I would not think anything outside the test suite could possibly want to connect to your xvfb instance [10:30] yeah, probably. i'm just trying to think why i can't reproduce it anywhere else ;) [10:34] chrisccoulson, there were a few changes we put in for xorg-server (2:1.10.4-1ubuntu1), such as a dependency on xauth; possibly those changes are not present in the buildd's [10:34] pitti, what would you think about making dh_translations use config.h before configure.ac? === jibel_ is now known as jibel [10:35] pitti, to get the gettext domain [10:36] pitti, the issue I come from is gdk-pixbuf which uses "GETTEXT_DOMAIN="$PACKAGE"" in its configure.ac [10:36] pitti, so domain=$PACKAGE and it calls intltool-update -d $PACKAGE [10:36] pitti, the config.h has the correct domain [10:37] (not sure I'm clear) [10:37] chrisccoulson, actually the xauth dependency appears to be introduced in maverick. Still, I think the buildd's are on lucid and I'm not sure whether we backported that. If you're testing locally on a different ubuntu release than the buildd's that could explain it. [10:39] seb128: sounds fine to me; config.h also has GETTEXT_DOMAIN? or is it called differently there? [10:41] pitti, configure.ac use AC_DEFINE(GETTEXT_PACKAGE) often, so it does land in the config.h [10:42] pitti, it's needed for the makefiles to be able to use -DGETTEXT_PACKAGE for the setlocale() etc [10:42] pitti, I will open a bug and a merge request for it today [10:42] pitti, danke [10:42] seb128: thanks [11:19] seb128: I wonder if we need to autostart gnome-screensaver at all -- do you know what triggers it on timeout? gnome-session or is that g-s itself? [11:19] I now fixed g-s-d's power plugin, but that only does the screen locking when upower goes to sleep [11:19] pitti, well upstream autostart it because they don't have the dbus service IIRC [11:19] (but that dbus-activates) [11:19] that's something we distro add [11:20] oh, really? that's surprising indeed [11:20] pitti, I think it's gnome-session or gnome-settings-daemon which triggers it [11:20] not g-s-d [11:20] pitti, http://git.gnome.org/browse/gnome-screensaver/commit/?id=3365eec74643773d8d5aa92901b39bdc9496e19b [11:21] ah [11:21] hm, it doesn't hurt, thuogh [11:21] pitti, I think mdeslaur didn't like that [11:21] if g-s crashes, then the .service file would at least bring it back on suspend, etc. [11:21] so we still dbus activate it to increase the chance to not run in a "locking doesn't lock" [11:21] *nod* [11:22] seb128: do you mind if we bump the autostart delay from 5 to 20 secs? [11:22] pitti, well gnome-session is supposed to respawn stuff if they use X-GNOME-AutoRestart=true, that would perhaps be enough [11:22] pitti, not at all [11:22] go for it [11:23] seb128: hm, I can killall gnome-screensaver here and it doesn't come back automatically [11:23] that's how I test the g-s-d fix [11:23] pitti, right because /etc/xdg/autostart/gnome-screensaver.desktop doesn't have that line "X-GNOME-AutoRestart=true" [11:23] which seems a bug to me [11:23] a quick grep of g-s shows that it seems to do the timeout itself [11:23] so we do need to start it [11:24] seb128: well, at least it gets activated on suspend [11:24] pitti, you should ask vuntz in case he's around [11:24] or maybe chrisccoulson knows what is tracking the idle time to call gnome-screensaver [11:24] but I think it's gnome-session itself [11:25] easy enough to try [11:25] I set it to 30 secs, kill it, and check what happens :) [11:39] seb128: so, g-s handles the timeout itself, so it needs to be running [11:39] seb128: ctrl+alt+l works when it's not running, so it seems g-s or g-s-d spawns it then [11:40] seb128: but /etc/xdg/autostart/gnome-screensaver.desktop doesn't seem to work right now, it never gets run [11:40] pitti, right, g-s-d handles the keybindings [11:40] NoDisplay=true [11:40] ^ does that disable autostarting? [11:40] that's ok, that means "don't list it in gnome-session-properties" [11:40] oh [11:40] hm, I wonder what keeps it from starting then [11:40] OnlyShowIn=GNOME; [11:41] you need to add Unity; [11:41] ooh, needs UNity [11:41] willdo [11:41] danke ;-) [11:41] add the "X-GNOME-AutoRestart=true" as well if you want [11:41] that should make gnome-session respawn it [11:41] hm, do we want this? [11:42] it's probably not needed with the dbus service [11:42] it will respawn it [11:42] and if someone kills it, it might be deliberate [11:43] working around movie players which don't inhibit it, and the like [11:43] or it might segfault in which case you get screen locking not working in the upstream case [11:43] but yeah, with the dbus service we don't have that issue [11:43] so NOTUBUNTU [11:44] screensaver-be-gone \o/ [11:45] lol [11:46] adding "Unity" does the trick [12:00] pitti, https://code.launchpad.net/~seb128/pkgbinarymangler/smallfixes/+merge/87602 [12:00] RAOF: do we really need to start colord at boot? would it be possible to add a gsettings check to only launch it if you actually configured anything? [12:01] seb128: could you swap it around and try config.h first? and then use the if (!$domain && ... schema? [12:02] fits better into the existing code, and avoids reading multiple files [12:02] pitti, not really since config.h doesn't have the "use intltool" info [12:02] ah, of course [12:02] pitti, and ups, I've a small fix to do [12:02] so don't merge that please [12:03] seb128: looks fine otherwise, so please go ahead and merge yourself with a changelog [12:03] pitti, ok thanks [12:03] seb128: what's still wrong, OOI? [12:03] pitti, small error in the config.h regexp [12:04] the format is not exactly the configure.ac one [12:04] just fixing that ;-) [12:04] ah, ok [12:07] * Sweetshark install half a million build deps on porter-dchroot [12:08] Sweetshark: nice that we can now :) [12:10] pitti: should I test the beta2 on the porters first, or would you upload for precise as-is (with risk of breaking on ppc/armel)? [12:10] Sweetshark: for such a major upgrade I'd test it on a porter machine first [12:10] I wouldn't do it for every single upload, but with that many changes it's likely that something goes wrong [12:11] Sweetshark: I would worry less about powerpc, just armel [12:11] Sweetshark: does that need any new MIRs? [12:13] pitti: not as of now, I am just using --with-system-foo when something crops up. [12:14] pitti: I filed one MIR, doko didnt like it as is => should be discussed at sprint maybe. [12:15] pitti: s/--with-system-/-without-system-. [12:15] pitti: so a) it builds now b) if we decide to mir, we can switch. [12:16] Sweetshark: sounds good [12:18] porter-ppc is hugged with building LO-beta [12:20] pitti, http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/pkgbinarymangler/precise/revision/231 [12:20] that being done -> lunch ;-) [12:20] ah, the #define [12:21] seb128: nice! please go ahead and upload [12:24] * Sweetshark install 310 additional build deps on armel [12:25] Sweetshark, hi [12:26] ricotz: re-hi ;) [12:26] Sweetshark, do you know if the libreoffice postgresgl plugin is meant for 9.0? [12:27] Sweetshark, i built the 3.4.4 precise package on lucid and needed to disable this plugin [12:27] ricotz: you mean the postgres backend for base? [12:27] 9.0? should be 9.1 for precise/oneiric and 8.4 for older releases [12:28] ricotz: it requires the >9.0 headers of postgres, yes. [12:28] oh, ok, wasnt really sure about the version number, but it wouldnt build against 8.4 [12:28] Sweetshark, ok [12:29] ricotz: wait for 3.5.0 and all is shiny. [12:29] ricotz: 3.5.0. should be a lot better than 3.4.0 for various reasons ;) [12:29] Sweetshark, this means it will build against 8.4 again? [12:29] ricotz: um, no. [12:30] Sweetshark, ok, so i will keep it disabled then [12:30] Sweetshark, yeah of course i am looking forward for a new feature release :P [12:30] ricotz: I meant it will be enabled in the default package for 3.5.0/precise as it is in there upstream and we have 9.0 on precise. [12:31] pitti, hi [12:31] tkamppeter: hello, gesundes neues Jahr! Enjoyed your vacation? [12:32] Sweetshark, of course that is fine, i just wanted to be sure about the needed versions, maybe you can push a bump for 9.0 to packaging git [12:32] pitti, was great, also a successful New Year for you! [12:32] thanks [13:18] mvo, hi, I'm working on the OS upgrade design again. If updates for your machine's current Ubuntu version are available, and a new Ubuntu version is available too, is there any reason for people to install the updates before they do the upgrade? [13:19] mpt: yes, sometimes we have updates that fix issues that happen during the upgrade otherwise, its not happening that often, but it does happen from time to time, i.e. updating a old app so that it does not misbehave during the upgrade [13:20] or to provide a feature during the upgrade [13:21] mvo, is there a way of telling which updates fall into that category and which don't? [13:23] mpt: unfortunately not at this point and I don't have any hard data currently except for "we did need it in the past" :( [13:24] mvo, then should the OS upgrade process automatically install all available updates first? [13:25] mpt: that would be a good idea or even better we flag the updates we really need and only install them (more work though) [13:27] mvo, what if upgrading requires first installing an update to update-manager itself? Is it smart enough to relaunch itself? [13:28] mpt: yes [13:29] mpt: hm, mostly, the release upgrader is, u-m itself is not [13:29] mvo, ah, I didn't realize that was a separate process [13:30] mpt: u-m just downloads the release-upgrader and verifies it, from that point on this part takes over [13:30] mvo, so is there anything tricky that would prevent USC from downloading and running release-upgrader, instead of update-manager doing it? [13:31] mpt: no, I can't think of anything, we would "just" have to shuffle some code around [13:32] mpt: what makes it tricky is that it does not get any real testing except for when the release is done [13:32] ok [13:33] i.e. we release it into unstable, but because you never release upgrade from unstable to something its sitting there until unsable becomes stable and then the next unstable becomes availalbe === DrPepperKid is now known as MacSlow|lunch [13:39] thanks for those answers mvo [13:41] mpt: cheers, your welcome [14:06] seb128, do you know anyone's been playing with systemtap for debugging on ubuntu? [14:06] chrisccoulson: both firefox and tbird grw by 1.3 MB each between 9.0 and 10.0 -- any chance this can be squeeze again a bit? [14:06] * pitti investigating our current oversizedness [14:07] mhr3, desrt was looking at it, dunno about "on ubuntu", do you have ubuntu specific questions? [14:07] pitti - bug 894166 :) [14:07] Launchpad bug 894166 in firefox "Make hyphenation work with system hyphenation patterns" [High,Triaged] https://launchpad.net/bugs/894166 [14:07] chrisccoulson: ah, thanks! [14:07] i might need some input on how to make that work correctly though [14:07] pitti, did you see the pad notes? [14:08] evince-common (Δ 1.4 MB - 3.2.0-0ubuntu1: 0.5 MB 3.2.1-0ubuntu2: 1.8 MB) due to adding /usr/share/gnome/help/evince/C/figures/synctex_screencast.ogv [14:08] thunderbird (Δ 0.9 MB - 7.0.1+build1+nobinonly-0ubuntu1: 18.7 MB 8.0+build1-0ubuntu1: 19.6 MB) [14:08] seb128: I thought it was me who added the evince one in the first place :) [14:08] pitti, the first one should be easy to fix by just not shipping the video, though that feels a bit wrong, but I don't see a better way, and synctex demo is not that useful [14:08] I agree [14:09] pitti, ok, the pad is not good to put names with lines :p [14:09] pitti, I was mentioning it in case ;-) [14:09] yeah, I actually forgot about it [14:09] seb128: I can drop the file, I'll check how the help behaves [14:09] ok? [14:09] seb128, i was wondering how does it work generally as well as if ubuntu has some packages to help with it... like there are some static probes and glib has support for them, but dunno if one needs to compile glib with that or what... [14:10] mhr3, we need to compile glib with it, we looked at it at the rally before UDS with desrt but it didn't play well with multiarch iirc [14:10] mhr3, could be a topic for next week... [14:10] pitti, sure, I think I tried that some weeks ago, the help just skip the video so it's not an issue [14:11] since oneiric, firefox and tbird each grew by 2.6 MB [14:11] we have 6.2 MB package growth, plus 10 MB from new packages [14:12] lucky that we dropped the mono stack ;-) [14:12] that's already included in the 10 MB balance, though [14:12] urg [14:12] removed: 78.3 MB, added: 88.7 MB [14:12]