[06:23] <pitti> Good morning
[06:23] <pitti> hey GunnarHj
[06:28] <happyaron> morning pitti
[06:49] <didrocks> good morning
[08:06] <pitti> bonjour didrocks, ça va ?
[08:07] <seb128> hey pitti
[08:08] <seb128> good morning desktopers
[08:10] <pitti> bonjour seb128
[08:10] <seb128> pitti, happy friday! wie gehts?
[08:11] <didrocks> bonjour pitti! encore malade :/
[08:11] <didrocks> et toi ?
[08:11] <pitti> seb128: gut, danke!
[08:11] <pitti> didrocks: eek, your knee, or something else now?
[08:11] <didrocks> pitti: since yesterday: headache + caught a cold
[08:11] <didrocks> so quite a slow mind…
[08:14]  * pitti hugs didrocks
[08:14] <pitti> get well soon then!
[08:14]  * didrocks hugs pitti back
[08:14] <didrocks> pitti: well, better now that during the hackfest/fosdem/sprint
[08:14] <didrocks> than*
[08:15] <didrocks> pitti: so today: testing fsck full integration with reboot (only did running plymouthd and services manually), so with units and so on + writing man pages
[08:15] <didrocks> so, expect a lot of reboots
[08:16] <didrocks> (as the vms are using the ubuntu text version for plymouth, so need real hw)
[08:16] <pitti> didrocks: oh, really? I see the graphical one
[08:16] <didrocks> pitti: then, everything is done apart: "non ubuntu plymouth theme and i18n"
[08:16] <seb128> didrocks, don't bring us the ubuflu!
[08:16] <didrocks> pitti: squared dots?
[08:16] <didrocks> seb128: a week should be enough to get that completely evacuated from my body!
[08:17] <pitti> didrocks: hm, I do see the graphical one on shutdown; booting is so fast, I actually don't see anything at all
[08:17] <pitti> didrocks: let me try forcing an fsck on that and reboot, that should take a bit longer, right?
[08:17] <pitti> seb128: oh, you're coming too? nice!
[08:17] <didrocks> pitti: yeah should!
[08:17] <didrocks> seb128: I hope that a week would be enough. bonus is that I'll be immunized!
[08:18] <seb128> pitti, well, I'm coming to Brussels for the mir/unity week after fosdem, but I'm going to be there at least on sunday
[08:18] <didrocks> pitti: I just tried on virtualbox, I need to repair a qemu box
[08:18] <pitti> didrocks: and I definitively get the graphical one when booitng the live CD
[08:19] <pitti> seb128: ah, nice!
[08:19] <pitti> didrocks: well, immunized against *that particular* germ -- not the other 50 which will be floating around :)
[08:19] <pitti> didrocks: hm, forced fsck, still didn't see any plymouht at all
[08:19] <didrocks> pitti: qemu is too fast
[08:19] <pitti> didrocks: do you start plymouth in the initramfs? i. e. do you have cryptsetup installed or so?
[08:20] <didrocks> pitti: I don't start it during initramfs
[08:20] <didrocks> pitti: when you say graphical -> rounded dots?
[08:20] <didrocks> not squared?
[08:20] <pitti> didrocks: anyway, try various -vga options
[08:20] <pitti> didrocks: yes; I mean the -ubuntu theme, not the -text one
[08:20] <pitti> that's what you aim for, right?
[08:20] <didrocks> ok, as most of people think about -text being non graphical :)
[08:20] <pitti> ah!
[08:21] <pitti> didrocks: apt install cryptsetup, now I see a garbled (but graphical) theme
[08:21] <didrocks> when -text, you have the ubuntu logo, but rendered without sprites
[08:21] <didrocks> garbled?
[08:21] <pitti> didrocks: well, in -text I only see a standard text cosole "Ubuntu 15.04 .." with some animated text dots
[08:21] <pitti> didrocks: with -vga vmware -> -text
[08:22] <pitti> didrocks: with -vga std -> -ubuntu (graphical)
[08:22] <didrocks> right, the -text is http://techluminati.com/operating-systems/how-to-install-ubuntu-12-04/
[08:22] <pitti> didrocks: ^ so try that one?
[08:22] <didrocks> ah, great!
[08:22] <didrocks> yeah, trying :)
[08:22] <pitti> didrocks: yeah -- any testing that involves rebooting your workstation just sucks and is way too demotivating :/
[08:23] <pitti> didrocks: so: -vga std, sudo tune2fs -c 5 /dev/vda1, boot with upstart in grub -> I see graphical fsck
[08:24] <pitti> (percentage and stuff)
[08:26]  * didrocks hugs pitti, works well with -vga std :)
[08:26] <didrocks> ok, now transferring units and mocks to the vm
[08:26] <didrocks> and crossing fingers :)
[08:27] <didrocks> pitti: just to keep you updated: I finished the C keystroke on wednesday
[08:27] <didrocks> and so, it cancels all fsck processes running (and new incoming ones)
[08:28] <didrocks> however, it's true that we have bug #776034 for now, which can be worrying on non ssd
[08:29] <didrocks> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776034 rather
[08:29] <pitti> didrocks: you (did)rock!
[08:30] <pitti> didrocks: btw, just making sure you know these potentially helpful tools: (1) forward VM's ssh port to the host so that you can easily ssh in, (2) enabling serial console so that you can debug stuff during boot, (3) enabling the systemd debug console
[08:30] <pitti> didrocks: I haven't tried combining (2) and (3), i. e. enabling the debug console on ttyS0, but that might be useful :)
[08:31] <didrocks> I did 3, will have a look at 2 :)
[08:31] <didrocks> well, of course, everything will work well on first boot, right? :p
[08:31] <pitti> didrocks: it's not much more than console=ttyS0 on the kernel cmd line
[08:31] <pitti> didrocks: heh yeah, what am I talking about!
[08:31] <didrocks> hehe :)
[08:32]  * didrocks downloads latest vivid first and start the manpages
[08:32] <pitti> systemd.log_target=console console=ttyS0
[08:33] <pitti> didrocks: ^ that sounds useful too, in case your units spit out some logging
[08:35] <didrocks> pitti: thanks for the hint! /me notes that down
[08:35] <pitti> didrocks: http://www.freedesktop.org/wiki/Software/systemd/Debugging/ has pretty much everything, I think
[08:36] <didrocks> pitti: yeah, that was my baseline when I needed to have a look at that. I didn't use "Debug Logging to a Serial Console" though, (until now)
[08:37] <pitti> didrocks: so, qemu: -serial stdio -vga vmware, and boot with console=ttyS0, then you get some crazy text plymouth on the console and then a login prompt
[08:38] <didrocks> pitti: with qemu, you are always using the adt image, right?
[08:38] <pitti> didrocks: hah -- I edited debug-shell.service for s/tty9/ttyS0/, sudo systemctl enable debug-shell.service
[08:39] <pitti> didrocks: then just boot (no other kernel command line args)
[08:39] <didrocks> ah sure, better that matches :)
[08:39] <pitti> and you immediately get a root shell on the terminal where you launched qemu
[08:39] <pitti> (don't use console=ttyS0 there, you can't have both the debug shell and a getty there)
[08:39] <pitti> didrocks: no, not always
[08:40] <pitti> didrocks: I do use the adt image for a lot of stuff, but for testing systemd uploads or things like that I have a standard vivid install in a VM
[08:40] <pitti> didrocks: I call it "pid1.img" :) it's standard vivid plus systemd-sysv installed, plus using my apt proxy
[08:40] <didrocks> pitti: ah, I might set that up then :)
[08:40] <pitti> didrocks: and I always boot them with -snapshot so that my pid1.img always stays pristine
[08:40] <pitti> and I can hack those up as much as I want
[08:40] <didrocks> yeah :)
[08:41] <pitti> didrocks: oh, and I changed grub to always show the boot menu, much nicer for that stuff
[08:41]  * didrocks fires an install first
[08:41] <pitti> i. e. comment out the two GRUB_HIDDEN_TIMEOUT lines in /etc/default/grub, then sudo update-grub
[08:42] <didrocks> sure
[08:49] <willcooke> morning guys
[08:49] <willcooke> didrocks, feeling any better?
[08:52] <seb128> hey willcooke
[08:52] <willcooke> morning seb128
[08:53] <seb128> happy friday ;-)
[08:55] <willcooke> \o/
[08:55] <GunnarHj> Hi pitti!
[08:56] <didrocks> willcooke: not completely, still feeling tired and headache + sneezing
[08:56] <didrocks> willcooke: better now than for the sprint though :p
[08:56] <willcooke> :)
[08:59] <seb128> hey GunnarHj
[08:59] <GunnarHj> pitti: Noticed that you changed the tag at bug #678421 to "verification-done". Did you test the gdm package for Utopic?
[09:02] <pitti> GunnarHj: oh, I misunderstood the tag changes then, sorry; adjusting
[09:02] <Laney> hey hey, happy friday
[09:03] <GunnarHj> pitti: Ok. gdm-trusty has been tested, but not yet gdm-utopic.
[09:08] <didrocks> argh, kvm crashed and now, I have some hw lockup, rebooting…
[09:21] <larsu> morning!
[09:41] <didrocks> pitti: it seems I can't set SOCK_NONBLOCK directly from the .socket unit, or am I missing something? (so, I would need to call fcntl() for the socket-activated path)
[09:42] <pitti> didrocks: I'm not aware of a way to do that; but wouldn't that defeat the purpose of activation?
[09:43] <pitti> didrocks: also, NONBLOCK is a client-side option, not a server-side
[09:43] <pitti> i. e. the activated service, nor the systemd proxy shouldn't care -- it's the client who conects to the socket who has to set that
[09:44] <didrocks> pitti: the server can as well, to accept multiple connections without being multithreaded
[09:44] <didrocks> (as some connections can happen after the service is activated)
[09:44] <didrocks> take the case of multiple fsck in parallel
[09:44] <pitti> didrocks: ah, I'm afraid I'm not aware of that kind of usage
[09:45] <didrocks> pitti: that's working manually (if the service created the socket), it's just that when systemd gives it to me, it doesn't have this flag, but I can set on the fd afterwards in that case, so doing that
[09:47] <didrocks> ok, working well now with the manual non blocking flag set (when the socket is passed by systemd :))
[10:35] <Sweet5hark> moin
[10:36] <pitti> moin Sweet5hark, wie gehts?
[10:37] <pitti> Sweet5hark: FYI, latest LO autopkgtest fails, https://jenkins.qa.ubuntu.com/job/vivid-adt-libreoffice/119/?
[10:37] <pitti> No package 'libcmis-0.4' found
[10:37] <pitti> it's a bit weird, as it did succeed in vivid-proposed
[10:38] <pitti> so this smells like a missing binary or test dep
[10:38] <Sweet5hark> pitti: tres bien! J'ai construit libreoffice 4.4.0.2 on amd64,i386,armhf,powerpc!
[10:39] <pitti> Sweet5hark: oh, on parle français maintenant ! d'accord :)
[10:39] <larsu> man, this channel is turning more french by the minute...
[10:40] <Sweet5hark> pitti: thats mostly harmless, it will go away when we bump to libreoffice 4.4. caused by a bit of hackishness in the autopkgtests ...
[10:40] <pitti> Sweet5hark: well, it's now holding back gtk+3.0 because of the regression
[10:40] <pitti> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#gtk+3.0
[10:40] <pitti> oh, and libcmis
[10:40] <Sweet5hark> *cough* likely means that the current LibreOffice 4.3. in main is also FTBFS though :/
[10:41] <pitti> Sweet5hark: so, I think the real reason is the libcmis update to 0.5? http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#libcmis
[10:41] <pitti> so it's quite natural that it doesn't find -4.4
[10:41] <Sweet5hark> pitti: yep, we bumped libcmis to 0.5 for libreoffice 4.4.
[10:43] <Laney> looks like a transition
[10:43] <pitti> ok, that explains at least that bit
[10:43] <Sweet5hark> pitti: libreoffice 4.3 should build and autotest against libmcis 0.5 too, but likely the autogenerated b-ds say it just wants 0.4
[10:46] <Sweet5hark> pitti: the bad news is libreoffice 4.4 didnt yet build on arm64/ppc64el ... but on a closer inspection we never shipped those before anyway.
[10:47] <pitti> Sweet5hark: yeah, that shoudln't hold it back
[10:49] <Sweet5hark> pitti: https://launchpad.net/~canonical-libreoffice-builds/+archive/ubuntu/archive-staging/+sourcepub/4682663/+listing-archive-extra should land in the archive soonish (next days) anyway ...
[10:49] <pitti> cool, thanks
[11:00] <Sweet5hark> thats the question: whether 'tis nobler in the mind to ask for gcc-4.7 to be ported to ppc64el or to switch to ucpp making it a build-depend on all archs and thus requiring a profane and cruel MIR to make it join the jolly lot in main!
[11:03] <Sweet5hark> (its friday, isnt it?)
[12:30] <didrocks> pitti: ok, latest bugs squashed (a race where plymouth started after the root fsck), writing manpages now
[12:30] <didrocks> pitti: however, in the emulator, c doesn't cancel (the signal is not received)
[12:30] <didrocks> pitti: not sure if it's a qemu issue, I'll try rebooting my box soon
[12:30] <didrocks> (works well with plymouth-x11 in my session)
[12:31] <pitti> didrocks: yay, sounds great!
[12:31] <pitti> didrocks: sorry, got stuck in debugging the touch regression for the past 2 hours :/
[12:32] <didrocks> pitti: yeah, saw that, no worry :)
[12:45] <pitti> didrocks: so it sounds like you might have this on the upstream list by next week, so that we can work on it on the hackfest?
[12:45] <pitti> oh, Netti is coming home, lunch o'clock
[12:46] <didrocks> pitti: yeah, I'm looking at the i18n integration now, but I can post without this
[12:46] <didrocks> pitti: basically, I think we'll send the metadata + a string
[12:47] <didrocks> pitti: so that .script themes can use the string directly, and other themes can use the metadata
[12:47] <didrocks> enjoy your lunch! :)
[13:17] <xnox> didrocks: "however, in the emulator, c doesn't cancel (the signal is not received)" phone emulator? that one does not have a physical keyboard... not allows input from it, not even if a skin with keyboard is enabled
[13:20] <didrocks> xnox: no, qemu, ubuntu-dekstop on plymouth
[13:20] <didrocks> ubuntu-desktop*
[13:20] <xnox> didrocks: =(
[13:21] <didrocks> xnox: I need to check on my system if this works though. But I guess it does (doing something similar than mountall) and it works with plymouth-x11
[13:22] <didrocks> and yeah, the signal is send to listen to that key, it's not something racy (as I write something on the theme screen and this part is written)
[13:23] <xnox> didrocks: is tty connected to plymouth or systemd. as far as i remember there are multiple things needed in the unit to have tty actually wired up to plymouth.
[13:23] <xnox> e.g. see oem-config / ubiquity jobs
[13:23] <xnox> units that is.
[13:24] <didrocks> xnox: ohoh, nice pick!
[13:24] <didrocks> probably plymouth tty not being connected
[13:24]  * didrocks looks
[13:27] <xnox> i see no lennart in http://lists.freedesktop.org/archives/systemd-devel/2014-November/thread.html#25288
[13:27] <xnox> didrocks: ^ -enochan
[13:27] <seb128> xnox, look in decembre?
[13:28] <xnox> night
[13:28] <xnox> tah
[13:30] <seb128> xnox, night? are you in .au now?!
[13:30] <seb128> or is that "right"? ;-)
[13:31] <xnox> seb128: that was a typo for "right"
[13:31] <didrocks> xnox: yeah, it's going on in december :) (but answered on the right chan :p)
[13:31] <didrocks> xnox: that's why threading is bad, we need isolates!
[13:42] <pitti> didrocks: oh, that sounds good -- then any consumer can pick
[13:43] <didrocks> pitti: yeah, sounds the saner approach to me
[13:43] <didrocks> pitti: trying the TTY options for plymouth that xnox suggested, didn't get it to work for now
[13:43] <didrocks> but looking)
[13:44] <pitti> didrocks: which ones? I recently fiddled with friendly-recovery and ubiquity-dm, which both want to 0wn the console
[13:44] <didrocks> pitti: xnox told rightly that I maybe don't receive keypresses in plymouth due to StandardInput= not being set
[13:44] <didrocks> pitti: tried to direct it to tty1, tty7… no chance yet
[13:46] <didrocks> but for upstart we did nothing specific and the plymouthd daemon seems to fork and then set the tty itself, so, it should get the inputs…
[13:48] <xnox> systemd is angry and does more setup than upstart did...
[13:48] <didrocks> xnox: well, it would as well prevent plymouthd to display the splash
[13:50] <xnox> didrocks: splash is output, keyboard is input.
[13:51]  * xnox thought there were hooks into systemd-input mechanics, unless that's for cryptsetup only
[13:52] <xnox> i'm so happy you are looking into this =)
[13:52] <didrocks> xnox: yeah, but there it would be where for systemd to allow setting any ouptut and mess with inputs
[13:52] <didrocks> xnox: ahah, I see that :p
[14:00] <pitti> didrocks: right, I had the same "does not receive keypresses" in ubiquity, until I set up the TTY correctly
[14:02] <pitti> didrocks: http://paste.ubuntu.com/9835101/ is what I did for oem-config
[14:03] <didrocks> pitti: yeah, I tried that with tty1 and then tty7 but didn't work
[14:03] <pitti> didrocks: so it might be that plymouth's units need something like that (as it's plymouth which gets the keys, not fsckd, right?)
[14:03] <didrocks> pitti: right, it's plymouth
[14:03] <didrocks> pitti: I wonder though, because systemd as systemd-ask-password-plymouth.service
[14:04] <didrocks> so, it's like they already support stdin from plymouth? (this service, just run plymouth ask-question…)
[14:05] <pitti> didrocks: right, that's for cryptsetup passphrases and similar, so that ought to work
[14:05] <didrocks> pitti: I didn't retry to reboot on my system yet, so maybe it's all working and just not in qemu for $whateverreason
[14:07] <didrocks> headache restarting again -> fallback to manpage writing
[14:12] <seb128> kenvandine, hey
[14:12] <kenvandine> hey seb128
[14:12] <seb128> kenvandine, seems like you registered the notes-app project on launchpad, is anyone working on it? there are some approved mps, would be nice to land those
[14:13] <kenvandine> i don't think so
[14:13] <kenvandine> i just did that as a part of mass registering all the projects
[14:16] <seb128> kenvandine, k, do you know who to ask about it? I'm happy to help and handle some landing/click updates (just need somebody to point me on how to do that, never did it)
[14:16] <seb128> kenvandine, I'm using the app and would like to maybe fix some small issues
[14:17] <kenvandine> bfiller would know
[14:18] <kenvandine> seb128, it was abandoned in favor of reminder-app
[14:18] <kenvandine> i think
[14:19] <seb128> kenvandine, they are differents apps though
[15:09] <seb128> ok, I'm going to drop from IRC, working offline in a bit and probably not joining IRC again before calling it a week, have a nice w.e everyone
[15:10] <willcooke> cya seb128
[15:19] <mdeslaur> larsu: hi! what's the solution for apps that get black backgrounds when used with overlay scrollbars? what should I be looking for?
[15:19] <mdeslaur> larsu: ie: http://snag.gy/pT2aB.jpg
[15:21] <larsu> mdeslaur: setting the background of affected widgets to @bg_color in the theme usually works
[15:22] <larsu> better is to disable overlay-scrollbars ;)
[15:22] <mdeslaur> larsu: in the _theme_? so not the app itself?
[15:23] <larsu> ya
[15:24] <mdeslaur> ah, lovely
[15:25] <mdeslaur> larsu: what's the best way to turn off overlay-scrollbars in the app itself?
[15:26] <larsu> mdeslaur: remove overlay-scrollbars from GTK_MODULES
[15:26] <larsu> sorry, overlay-scrollbar (sans s)
[15:27] <mdeslaur> larsu: can I do that in that app itself, or is it too late then and I have to do it in the desktop file?
[15:28] <larsu> mdeslaur: should be fine if you do it before gtk_init()
[15:28] <mdeslaur> cool, thanks for your help larsu!
[15:28] <larsu> mdeslaur: yw. Sorry about the sad state of that module :/  It's a huge hack in gtk
[15:29] <mdeslaur> larsu: will the new upstream stuff make it easier?
[15:29] <Laney> it's gone next cycle!
[15:29] <mdeslaur> gone? as in ugly scrollbars, or as in the new upstream stuff?
[15:29] <larsu> we have ugly ones now ;)
[15:30] <larsu> but ya, upstream got their own version of overlay scrollbars
[15:30] <mdeslaur> and we're going to be using those?
[15:31] <larsu> yes
[15:31] <mdeslaur> cool
[16:49]  * didrocks goes to get some rest and sneezing in his bed. see you on Monday guys and have a good week-end!
[16:49] <didrocks> safe flight larsu & desrt
[17:51]  * willcooke -> EOD
[17:51] <willcooke> ta ta#