=== duflu_ is now known as duflu === mfisch is now known as Guest63892 [06:27] Good morning [07:29] morning [07:32] didrocks: hey [07:32] attente_: qt5 version is uploaded to archive [07:34] hey happyaron [07:53] bonjour didrocks, c,a va / [07:53] eek, what happened to my compose key? [07:53] pitti: ça peut aller, et toi ? [07:54] didrocks: je suis fatigue', comme tous le jeudi apre`s basketball [07:54] * pitti switches keyboard layout twice, and voilà - compose key ! [07:54] didrocks: and I'm fighting some issues with the latest cloud-init [07:56] pitti: oh, still following up from yesterday? [07:57] didrocks: yeah, I just filed a bug for and worked around broken ssh [07:57] didrocks: and I'm now looking at why rsyslog stopped working (systemd's tests fail on that) [07:57] (on the cloud images) [07:58] urgh [07:58] yeah, I imagine for cloud-init, rsyslog forwarding may be important :) [08:00] hey didrocks pitti [08:00] bonjour seb128 [08:00] hey seb128 [08:00] go rsyslogd -- no manpage, no useful --help [08:00] oh sorry, it does have a manpage [08:01] open error 13, file '/var/log/syslog': Permission denied [08:01] ah-haa [08:02] that's fun, that should affect every new installation where /var/log/syslog doesn't already exist.. [08:02] the acl changes? [08:02] oh? [08:03] hah, seb128 filed that as bug 1401984, and we added a tmpfiles.d for it ages ago [08:03] bug 1401984 in rsyslog (Ubuntu) "non persistent logging after cleaning log files on disk" [High,Fix released] https://launchpad.net/bugs/1401984 [08:05] didrocks: no, the ACL is still there [08:06] interesting [08:06] pitti: btw, now, I'll use any opportunity to check if systemd-timesyncd is activated or not [08:07] just to know if that random starts condition only happens in a vm or not [08:07] woot, a systemd upload where the changelog is not the usual 3 screens long summary of the ubuntu delta :-) [08:07] seb128: oh, it's usually just one screen :) [08:07] the other two are the changes in Debian :) [08:07] hehe [08:08] pitti: it does try to start it on my system, and but as I already have /tmp as tmpfs, I didn't notice… [08:08] didrocks: yeah, same for me I guess; but timesyncd seems to start reliably here [08:08] the condition failed is funny [08:08] ConditionFileIsExecutable=!/usr/sbin/ntpd was not met [08:08] -rwxr-xr-x 1 root root 672624 févr. 9 19:12 /usr/sbin/ntpd [08:09] pitti: I don't understand yet why it becames a RequiresBy=tmp.mount though [08:10] waow, here, it's required even by more things than in the vm [08:10] RequiredBy=colord.service systemd-timesyncd.service local-fs.target rtkit-daemon [08:10] local-fs.target is because I guess it's in my fstab [08:10] seb128: do you have /tmp on tmpfs? [08:11] didrocks, that would show in "mount" right? [08:11] I guess not [08:12] didrocks: oh, so if you have ntpd it should indeed *not* start [08:12] does it? [08:12] seb128: yeah, it should. So systemctl status tmp.mount says it's not active? (and can you paste the RequiredBy line of systemctl show tmp.mount?) [08:13] pitti: right [08:13] didrocks, inactive indeed [08:13] ● tmp.mount - Temporary Directory [08:13] Loaded: loaded (/lib/systemd/system/tmp.mount; disabled; vendor preset: enabled) [08:13] Active: inactive [08:13] RequiredBy=rtkit-daemon.service systemd-timesyncd.service colord.service [08:14] so colord isn't running for you I guess [08:14] neither rtkit-daemon [08:14] $ systemctl status colord [08:14] ● colord.service - Manage, Install and Generate Color Profiles [08:14] Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled) [08:14] Active: active (running) since mer. 2015-03-04 07:52:18 CET; 1 day 1h ago [08:14] ok, I don't understand it seems :/ [08:14] pitti: any idea? ^ [08:15] 1. it's not an explicit Requirement [08:15] didrocks: no idea, sorry [08:15] 2. it's listed as RequiredBy and the same layout starts sometimes tmp.mount in a vm (I was thinking via systemd-timesyncd.service) [08:15] pitti: yeah, I smell something really fishy… [08:16] I guess we'll keep the "fail on no disk space" this cycle anyway [08:16] thanks seb128 :) [08:16] yw [08:17] didrocks: but timesyncd should never start in a VM, btw (ConditionVirtualization=no); if you want to test it that way, drop that line [08:18] pitti: it never starts, but it tries to activate (and show, brings the RequiredBy=) at some boot [08:18] so basically, it's either "inactive" or "condition failed" [08:18] in the second case, it started tmp.mount [08:18] and tmp.mount shows it in RequiredBy= even if we don't see it in the unit file [08:19] but in seb's case, it seems that even tmp.mount shows RequiredBy=colord.service (for also on unknown reason), having colord.service started didn't activate tmp.mount [08:21] my only bet is that colord is started via something else [08:21] it's of type dbus [08:21] so it's maybe dbus activated? [08:21] does dbus activiate respects the requirements? [08:22] I guess so [08:22] and that would explain at least this unmatched dep [08:22] no [08:23] it doesn't respect, I guess systemd just see a process and say "oh, it's that unit" [08:23] so mark it as running [08:23] I still don't know why those appears in RequiredBy=, there is nothing explicit, particuarly for systemd-timesync [08:24] (we could think of PrivateTmp=yes for colord would transition to tmp.mount) [08:24] didrocks, what appears in what requiredby? [08:24] seb128: $ systemctl show tmp.mount | grep Required [08:24] RequiredBy=colord.service systemd-timesyncd.service local-fs.target rtkit-daemon.service [08:25] if you systemctl cat (or open) unit files, they don't have a Requires=tmp.mount [08:25] if you grep in /lib/systemd/systemd/*service, no sign of tmp.mount being mentioned as a requirements in any unit [08:39] man, git bisect run is so awesome [08:41] ya. Feels like magic whenever I use it [08:41] morning pitti :) [08:41] hey larsu! [08:42] yeah; start it, let your computer burn and smoke, and enjoy a Piña Colada :) [08:42] or, in my case, work on NFS instead :) [08:42] is that different from bisect? [08:42] does it auto-flag good/bad and how? [08:42] seb128: it is a bisect, but in fully automatic mode [08:42] how do it determine the outcome? [08:42] seb128: you toss it a script, and looks at its exit code [08:42] k [08:42] 0 -> good, < 125 -> bad, 125 -> untestable (e. g. doesn't build) [08:43] > 128: abort [08:43] so as soon as you have an automatic test case you can let it run [08:43] seb128: I did that for the boot hang: my test case was to run an autopkgtest in QEMU with rebooting 30 times [08:43] ... and let it find your bug for you [08:43] so it went through ~ 1100 commits with that test case in about 2 hours [08:44] (now running it for the /var/log issue) [08:44] pitti: watch out, you're dangerously close to replacing yourself with a script [08:44] I wish I could -- one of these days I *actually* want a Piña Colada! [08:44] lol, I wonder if https://plus.google.com/u/1/+MathieuTrudelLapierre/posts/bFdphmbgAz8 is real :-) [08:44] pitti, nice! [08:45] cyphermox: ♥ [08:45] larsu: i vaguely recall you said you don't wanna work on that just yet, but i just patched a panel plugin for xfce to use symbolic icons, it's fairly easy and straightforward (if you'd be interested in doing that for indicators, i mean) [08:45] ochosi: ah cool. It's not that much work, is it? [08:46] ochosi: we'd need to merge ubuntu-mono-dark and -light first [08:46] which is something I've been looking at again yesterday when I added window decoration buttons for both [08:46] larsu: this is pretty much it: http://git.xfce.org/panel-plugins/xfce4-pulseaudio-plugin/commit/?id=314286b6f7da37472dcc69adfe64b66c07d580ec [08:46] and no, not necessarily [08:46] just ship the symbolic variants in the parent theme [08:47] the -dark variant will inherit automatically [08:47] ochosi: the parent theme for both is humanity iirc [08:47] hm, why do you preload icons? [08:48] larsu: oh, that's just how that particular plugin was written [08:48] i didn't want to change anything there apart from the icons [08:48] it preloads all icons at once and then uses the appropriate one per volume [08:48] not sure whether that's more efficient than loading what you need at the time [08:49] shouldn't make that big of a difference [08:49] prolly not [08:49] icons are mmapped anyway [08:49] all you do is waste some memory [08:49] but it's not a lot, so whatevs [08:49] yeah, it's fairly little [08:50] so basically what i'd propose is start with indicator-sound as a testcase [08:50] use the symbolic icons for the panel button and the menu icons [08:51] (which will be nice because the icons will finally *always* be recolored correctly with all themes) [08:51] ochosi: indeed [08:51] but! [08:51] indicator-sound colors it's icon sometimes [08:51] yeah [08:51] we'd need to add a css class in that case and add that to the theme [08:51] symbolic icons obviously account for that [08:51] *themes [08:51] nope [08:51] well, at least not really [08:52] as long as the symbolic icons have the error state, you should be fine by just setting that state [08:52] this only works for one state, though, and I'm not sure that e.g. Ambiance and Radiance use the same color there [08:52] or is that state colorable from the theme as well? [08:53] it's "success_color", "warning_color", "error_color" [08:54] https://developer.gnome.org/gtk3/stable/GtkIconTheme.html#gtk-icon-info-load-symbolic [08:54] afaik that's all in the icon, nothing required in the theme [08:56] ochosi: ah, those *are* css styles [08:56] ans we already do style them [08:56] *and [08:56] yeah, sry, but in fact you have to set a class within the icon [08:57] right [08:57] so it's both, the theme sets the color and the icon has to have the class set on the paths that should be recolored [08:57] so basically for the blocked stuff you just copy an existing symbolic icon and set the class of all paths to "warning" [08:57] so we'll still need to set the corresponding class on the gtkimage I guess [08:58] not sure, no [08:58] how else would it know when to recolor? [08:58] it automatically looks inside the svg and sees the class [08:58] at least that's how i think it works [08:58] yeah but it needs to know _when_ to draw that part [08:58] so you have "audio-volume-blocked-symbolic" or something [08:59] oh [08:59] so we'd need to change the icon then [08:59] ya, could do [08:59] and that has the "warning" class set [08:59] so all themes would color the icon accordingly [08:59] so it's not about re-using existing icons, although that might be possible as well [08:59] simply by adding a class [08:59] and removing it conditionally from the style contexxt [08:59] yeah what you're describing makes more sense to me [09:00] so the icons remain the same, i think the -blocked is already a separate icon [09:00] ochosi: this is early-next cycle work though - don't want to mess with that now [09:00] yeah, sure [09:00] if you wanna start the transition and need some help lemme know [09:01] would be good to do that for all indicators [09:01] indeed, it would [09:01] ochosi: thanks! Will do [09:01] okeydokey :) [09:01] thanks for pointing me towards this [09:02] np, btw, you might want to talk to gnome upstream and see whether they see any reason to include a "blocked" icon in adwaita-icon-theme [09:02] that way this would sort of become a standard [09:02] (since nobody seems to care about the fd.o icon spec anymore these days and gnome is the defacto standard for icon-names) [09:02] (nobody loves fd.o anymore :'( ) [09:04] yo [09:06] ochosi: there's quite a lot of stuff hosted on fd.o and we've been adding new stuff to the specs [09:06] hey Laney [09:06] ochosi: icons is a bit failed... [09:06] morning Laney! [09:06] Laney, wants to update gtksourceview3 in debian/sync the update? ;-) [09:07] yes! [09:07] he wants! [09:07] that should fix bug https://bugs.launchpad.net/gedit/+bug/1428333 [09:07] Ubuntu bug 1428333 in gedit (Ubuntu) "gedit crashes on autocomplete with SIGSEGV in gtk_text_iter_get_buffer()" [High,Confirmed] [09:07] larsu: yeah, i was specifically referring to that spec, not all of them are as outdated as the one for icons [09:07] well combined with https://git.gnome.org/browse/gedit/commit/?id=d48cd10bf0bb99ead7b1af1ead52f1e554ad239d [09:08] morning Laney [09:10] hey seb128 didrocks larsu [09:10] umm yeah okay [09:10] danke [09:10] Laney: that commit depends on gtk 3.16, so please upload that as well [09:10] lol [09:11] * larsu <-- on troll day. Won't be here tomorrow [09:11] which depends on bluez5, so while you are at it... [09:11] HAHA [09:11] nice one [09:11] larsu: btw, how did you fix the scale grabbing in indicator-sound? [09:11] :-) [09:12] larsu, want to review https://code.launchpad.net/~3v1n0/libdbusmenu/custom-stock-item-label/+merge/251840 ? it's a one liner [09:12] seb128: yes, a long time ago?! [09:12] larsu, what a long time ago? [09:12] seb128: oops, this was supposed to go to ochosi [09:12] larsu, was that for ochosi? he asked "how" [09:13] * larsu can't read, and can't type [09:13] larsu: wait, but that happened during this cycle, no? i remember not being able to click the volume scale correctly [09:14] ochosi: it did. I think the issue was that something reset the volume while you were dragging it [09:14] larsu, ochosi, http://launchpadlibrarian.net/195548750/ido_13.10.0%2B15.04.20141103-0ubuntu1_13.10.0%2B15.04.20150122-0ubuntu1.diff.gz [09:14] that one? [09:15] that looks like it could be it [09:15] https://code.launchpad.net/~larsu/ido/fix-volume-slider/+merge/247198 [09:15] is the corresponding mr [09:16] indeed, thanks seb128 [09:16] yw [09:16] awesome, thanks seb128 [09:16] yw [09:16] the volume resetting stuff was about the notification popping up [09:16] so is that a change that is gtk3 version specific or anything? [09:17] cause i remember it broke with gtk3.14 in the indicator [09:18] ochosi: yes. I remember not bothering to figure out the actual change that caused the issue, but there was quite some work done in gtk on event handling [09:18] all I did was not propagating events from the menu item to the scale in all cases [09:19] yeah, i wonder whether that works on older gtk3 releases as well [09:19] ochosi: don't try?! [09:20] heh [09:20] well, tbh for the plugin that i linked earlier we copied the indicator's scale menu item [09:20] ochosi: port to popovers! [09:21] it's the future [09:21] yeah, we haven't decided about those things yet [09:21] basically that needs a global xfce decision [09:21] right, makes sense [09:22] and we've only just released 4.12 last weekend [09:22] so my work is more or less exploratory at this stage [09:23] seb128: the bug linked to this MR is WontFix by both tedg and mpt... [09:24] (the dbusmenu issue) [09:24] ochosi: yeah I saw. Congrats on 4.12 :) [09:24] seems people like it [09:24] larsu, feel free to reject the change [09:25] larsu: hah, that is a very diplomatic statement "some ppl like it" :) i'm just happy we could finally move out of the stalling and now there's a clear goal (port to gtk3) [09:26] ochosi: I didn't say "some" ;) [09:26] oh ooops :) [09:26] * ochosi wonders why/how he managed to misread that [09:26] I read some reviews and they were mostly positive [09:26] that's what I meant [09:26] haven't tried it myself yet [09:27] yeah, no dramatic changes, which is generally an xfce policy [09:27] but yeah, I'm glad you guys are releasing again :) [09:27] yeah, took a while and a lot of personal effort [09:27] oh, mpt reopened that bug... [09:27] man, such a non-issue [09:27] ochosi: I can imagine [09:37] larsu: btw, i'm not sure you're interested in this sort of redesign, but i had an idea for indicator-sound that would rid you of the mute menuicon [09:38] larsu: basically, only have a volume icon on the left (the one on the right is a bit superfluous really, i mean what's that scale gonna do? decrease the volume?) and make that a button instead of an icon which on click mutes [09:38] larsu: well un/mutes obviously [09:39] moin [09:39] ochosi: both icons already do something (move the slider all the way in that direction) [09:40] ochosi: I personally dislike having mute separately from volume, but this is an issue to take up with mpt. He designed the sound menu [09:40] larsu: oh right, i never even noticed that [09:40] ochosi: https://wiki.ubuntu.com/Sound [09:40] guess some hover-effect on the icons would help users to notice that [09:41] ... feeling trollish today, I have to note that larsus Berlin and my home of Hamburg both moved up in the 2015 imercer quality of living ranking, kicking out Canadians and kiwis. [09:41] larsu: so it's actually less of a departure from the current state, mostly adding a feature where clicking that icon again will restore the previously set volume... [09:41] ochosi: feel free to file a bug for i-sound and assign mpt (or the ux team) [09:41] yeah, that would be weird though [09:42] Sweet5hark: economist ranked toronto the most livable city [09:42] not if there's only one icon [09:42] Don’t assign teams to bugs, real people don’t see them [09:42] Sweet5hark: and really, I trust those guys more :) [09:42] mpt: sorry. And hi! [09:43] Good morning :-) [09:43] mpt: does that idea even make sense to you? i guess there's no use in writing something up when you already know that's not what you want [09:44] larsu: you should move to Hamburg then, economist ranks them first in Germany (Top 14 globally) followed by Frankfurst as next german city ;) [09:45] Sweet5hark: haha, you're funny. [09:45] :O [09:45] Sweet5hark: seriously though, I totally believe that Hamburg is more livable than Berlin [09:45] they look at all kinds of factors [09:46] larsu: this is why our rents and real estate prices are where yours are only slowly going to ... [09:46] Sweet5hark: actually, not so slowly these days... [09:47] Sweet5hark: but then, we have quite some catching up to do compared to HH [09:47] * larsu should visit there properly [09:47] never really been to the city [09:47] ochosi, sorry, I just read back 60 minutes but don’t see any bug or MR reference … What’s the idea? [09:48] mpt: remove mute in favor of the buttons next to the volume slider [09:48] mpt: yeah, no MR/bugreport yet, i basically proposed dropping the mute menuitem, only using one sound icon to the left of the scale and using that as mute-button. adding a hover-style to that icon would help users see what it does [09:58] The MATE team have found a bug in upower that affects mate-power-manager. [09:58] Fedora has a simple patch that is confirmed as working. [09:58] https://bugs.launchpad.net/ubuntu-mate/+bug/1428337 [09:58] Ubuntu bug 1428337 in ubuntu-mate "MATE power statistics crashed" [Undecided,Triaged] [09:58] Could someone take a peek? [09:59] flexiondotorg_: sure. Please add upower to the bug and link an upstream bug (create one if it doesn't exist) [09:59] larsu, Thanks. [10:00] or rather, move it to upower, doesn't seem to be m-p-m's fault [10:00] flexiondotorg_: I'll have a look later and commit it upstream (but still debugging some stuff) [10:04] ochosi, larsu: This is going back far enough that I need to refer to what I wrote at the time to remember why I did stuff. says ‘The first item, “Mute”, makes it easy to urgently silence unwanted sound using a pointing device.’ Just the tiny button to the left of the slider wouldn’t be clickable nearly as quickly. [10:05] Especially (but not only) while bug 552920 remains unfixed. [10:05] bug 552920 in unity (Ubuntu) "Moving diagonally from narrow menu title often opens adjacent menu" [Medium,Triaged] https://launchpad.net/bugs/552920 [10:06] pitti Also affects gnome-power-manager [10:07] why? [10:07] is there another bug which needs to be fixed there? [10:07] looks like a crash in libupower-glib [10:08] mpt: there are no submenus involved there... [10:08] ochosi, larsu: The only reason the volume slider icons do *anything* when clicked is that I thought, “well if someone *did* click them, what would they be expecting to happen?” — not because I expected anyone to use them as the primary way of doing something. [10:08] pitti, I am just linking to where that bug has been experienced. [10:08] larsu, eh? I didn’t mention submenus :-) [10:09] mpt: oh! I thought the bug you mentioned was about that, but it's about menut titles. Sorry [10:09] mpt: makes more sense now :) [10:10] mpt: I like https://wiki.ubuntu.com/Sound#Mute, which is basically what the left menu item now does [10:10] but I don't think it would be well received if we switched this now [10:11] especially since many laptops have a "mute" key with an led which is on while the sound is muted [10:12] Is that software-controllable? [10:13] For convergence!!!!1 I guess we’ll need to change one or the other eventually :-) [10:13] haha, indeed [10:13] I don't know, it's probably not controllable on all machines [10:25] mpt: yeah, understandable, and i wouldn't propose this as a change for this cycle anyway [10:27] mpt: and i guess i'd only have one icon but bump the size of that to 22 or 24px, so it's more easily clickable [10:30] ochosi, that would increase the height of the item as a whole, and I’m not a fan of menu items of slightly varying heights — it looks accidental [10:31] what about the playback controls then? :] [10:32] Those (a) are massively different, not slightly, and (b) have borders around them clearly indicating their non-standard-ness :-) [10:34] sure, makes sense [10:41] did anyone check the gnome-terminal wrapper? [10:47] larsu: there is something wrong with your commit or the idoscalemenuitem still. if you try to hover the scale-button, it isn't drawn in hover style. however, if you hover approx 50px to the left of the scale-button it gets the hover-style applied [10:47] noticed when porting your change to the plugin i'm working on [10:48] indeed :( [10:48] * larsu makes a note of fixing this [10:49] * Laney gets a keyboard layout debconf prompt on latest dist-upgrade [10:49] cccccccyyyyyphhhhhhhherrrrrrrmooooooooooooxxxxxxxxxxxxxxxxxxx [10:51] Laney: opportunity for you to switch to a french layout! [10:51] I 'ate french! [10:51] :p [10:52] Laney: don't be so 'ateful [10:52] * Laney fluffles all French #ubuntu-desktoppers [10:53] /msg seb128 when did we discuss last time we would lay off a non french person in the desktop team? [10:53] oups ;) [10:53] * Laney looks at mlankhorst [10:53] roh, he left, that doesn't count! [10:54] haha lol [10:54] * Laney slinks away :( [10:54] you can still fire me :P [10:54] hey mlankhorst [10:54] do you have to move somewhere for intel? [10:54] no, still working from home [10:54] nice, didn't know that they did this [10:54] they only do it when you were already working on something related from home [10:55] seems Laney is getting infos for his next job :p [10:55] nothing wrong with that [10:55] heheh [10:55] this is sad, even no willcooke for teasing! [10:55] when the cat is away [10:56] http://thedailywtf.com/articles/Up-or-Out-Solving-the-IT-Turnover-Crisis :P [10:56] haha [10:56] I see what you're calling yourself [10:57] naww but it's going to be hard to top Xmir, and X is on the way out :( [10:58] I'm investigating on how to make GLES2 work on X in arm, it's harder than desktop :P [11:00] afk a bit [11:24] pitti: would you suggest to use ID_FS_TYPE to get a file system type (I don't use udev in the script, so I will just build a new udev_device_new_from_devnum for this), or is there any other way that is easier? [11:24] didrocks: if you don't use udev already, calling blkid might be easier [11:25] ok, by directly getting the TYPE tag [11:25] $ blkid -s TYPE -o value /dev/sda3 [11:25] * didrocks looks [11:25] btrfs [11:25] thanks pitti :) [11:31] didrocks: ah, Lennart's recent answers clarify that quite a bit? [11:31] e. g. colord also has PrivateTmp=yes [11:34] pitti: yeah, that was what I was infering here [11:35] pitti: but so, if any of those runs, it means that users will have tmpfs by default on vivid [11:35] oh, what a disaster :) [11:36] pitti: so, either was mask the unit by default, either we enable it for everyone, not feeling well to have different experience here in case of bugs, wdyt? [11:37] didrocks: can we discuss that in #d-systemd? [11:37] sure [12:17] Trevinho, seb128: hey folks... have you perhaps seen a glitch with current vivid (desktop) like this yet: unity/compiz reacts sluggish once qmlscene is started to run a .qml file? [12:18] Trevinho, seb128: just wondering if it's just on my system or a general issue === alan_g is now known as alan_g|lunch === MacSlow is now known as MacSlow|lunch [12:56] blah [12:56] lost my compose key [12:56] now I can't type my gpg passphrase! [13:07] restarting u-s-d fixed it === alan_g|lunch is now known as alan_g [13:57] mlankhorst: mh not saw that.. [13:57] err... sorry, I meant MacSlow|lunch ^ [13:58] MacSlow|lunch: nothing outside the qmlscene itself, which is something qt related [13:59] Trevinho, I'll still have to try it on my laptop (intel gfx) to have a comparison to my desktop (nvidia, binary blob driver), where I've seen this [14:00] Trevinho, unity's app-switcher was also affected... being very slow and sluggish to respond to a first invocation [14:00] mh === MacSlow|lunch is now known as MacSlow [14:00] * Trevinho has no nvidia to check with [14:00] Trevinho, I'll get back to you after I tried it on my laptop [14:01] andyrock has one btw ^ [14:07] Trevinho, andyrock: hm... no issues on my laptop (intel gfx) [14:08] seb128: pitti: yes, we can "Spock" our old five dollar bills by drawing hair and such on John A. Macdonald. Legal, but not very appreciated ;) [14:09] haha [14:09] pitti: btw thanks for fixing NM autopilot :) [14:09] cyphermox: it's autopkgtest, but you're welcome :) [14:10] uh, right [14:46] mardy: hi, are you planning to drop windows live (msn) messenger support from $uoa_component? [15:05] Laney: mmm... no, should I? [15:06] mardy: it's gone now [15:06] Laney: you mean that Live doesn't exist anymore? [15:09]