[06:31] <pitti> Good morning
[06:51] <didrocks> good morning
[07:47] <seb128> good morning desktopers
[07:53] <didrocks> hey seb128
[07:53] <seb128> re didrocks :-)
[07:57] <ali1234> cyphermox/anyone else, who is actually responsible for ubiquity dm panel these days?
[07:58] <ali1234> and cyphermox, you mentioned that changes to the struts would have to be tested with other WMs, but how would one do that without rebuilding the entire ISO?
[08:21] <larsu> bonjour #desktop!
[08:31] <seb128> hey larsu!
[08:31] <larsu> hi seb128!
[08:34]  * pitti waves Bonojur to didrocks, seb128, and larsu, wie gehts?
[08:35] <seb128> hey pitti
[08:35] <didrocks> salut pitti !
[08:36] <pitti> didrocks: FYI, I think I found a faster reproducer for the journal hang last night; installing rawhide now to verify
[08:37] <pitti> bah; rawhide installer crashes immediately
[08:37]  * pitti misses Ubuntu daily quality
[08:37] <larsu> pitti: great thanks!
[08:37] <didrocks> pitti: well, especially when they are starting a new dev cycles :)
[08:38] <didrocks> pitti: in the end of fedora 21 dev cycle, when I tried multiple systemd stuff on it, it was okishj
[08:38] <didrocks> pitti: what's your reproducer theory btw?
[08:38] <pitti> didrocks: I wrote it in bug 1423811
[08:39]  * pitti goes to install F21 instead and hopes there's some upgrade
[08:39]  * didrocks looks
[08:39] <didrocks> pitti: waow, sounds a nice "easy" way to get it, let's cross fingers
[08:40] <didrocks> pitti: oh btw, I think I got what was screwing up my shutdown time
[08:40] <didrocks> it seems to be my squid proxy
[08:40] <pitti> didrocks: I verified that I can play the start/stop game endlessly on debian sid (215), and I get reliable hangs on vivid with upstream's journald, but also sometimes with vivid's
[08:40] <didrocks> when removing it, shutdown time reduces drastically
[08:40] <didrocks> pitti: let's hope fedora has the same behavior :)
[08:40] <pitti> didrocks: oh, what is it trying to do on shutdown?
[08:40] <pitti> didrocks: it seems a proxy is a thing which you can just kill
[08:41] <didrocks> pitti: I need to look at the code, but I don't have those dbus connexions attempt
[08:41] <didrocks> so I wonder if something tries to poke dbus too much at shutdown, systemd tries to hang on as long as possible
[08:41] <didrocks> (because I didn't get this issue under upstart)
[08:41] <didrocks> anyway, worth exploring (once I'm done with upstream plymouth themes)
[08:43] <didrocks> but of course, squid doesn't connect to dbus, so there is mystery :)
[08:43] <didrocks> will give it a look
[08:44] <pitti> wow, anaconda has become outright pleasant
[08:45] <pitti> didrocks: squid-deb-proxy, I presume? Installing that into my VM
[08:47] <pitti> didrocks: hm, that might need some configuration; shutdown is a split second here
[08:48] <pitti> oh wait, not after the first reboot
[08:49]  * didrocks doesn't understand why plymouth upstream code doesn't take the theme I selected, seems there is another file in play
[08:50] <pitti> didrocks: confirmed
[08:50] <larsu> didrocks: strace it!
[08:50]  * larsu hides
[08:50] <pitti> didrocks: I see a lot of "Waiting..." in the unit status
[08:50] <didrocks> larsu: that's what I did, I got a suspicious file!
[08:50] <didrocks> pitti: \o/
[08:50] <larsu> haha, of course you did
[08:51] <didrocks> larsu: and I screwed my terminal with a tribar theme \o/
[09:05] <Laney> ahoy
[09:05] <pitti> hey Laney, wie gehts?
[09:05] <larsu> morning Laney!
[09:05] <willcooke> morning
[09:05]  * pitti waves hello to willcooke
[09:06] <Laney> hey pitti larsu willcooke
[09:06] <larsu> hi willcooke
[09:08] <larsu> saying hi to everyone is O(n!)...
[09:08] <pitti> larsu: we all like superlinear algorithms, don't we!
[09:09] <larsu> pitti: obviously ;)
[09:09] <Laney> good reason to keep the team small :P
[09:11] <pitti> didrocks: oh dear, yum upgrade takes aaages -- ETA 2.5 h..
[09:13] <larsu> Laney: how many people would we need to make saying good morning a day-filling activity?
[09:14] <larsu> pitti: yum? I think you downloaded your image from the wrong website... :P
[09:16] <didrocks> pitti: I wonder if I should bind the progress bar for the different plymouth themes to the fsck progress. This has never been done if I'm correct and will take quite some time to change all default plymouth themes which are going to be deprecated for this
[09:16] <didrocks> pitti: I can just remove the "fsckd-cancel-msg:" prefix and for people who wants more integration, they can add the "update" support?
[09:16] <didrocks> wdyt?
[09:17] <Laney> larsu: reminds me of https://xkcd.com/1205/
[09:17]  * Laney writes a script to say hello to you all every morning
[09:17] <larsu> haha
[09:22] <darkxst> Hey all
[09:23] <darkxst> Laney your script better be timezone aware ;)
[09:23] <pitti> didrocks: what is "update support" in the context of the cancel msag?
[09:23] <Laney> good ${part_of_day} ${nick}
[09:24] <Laney> I like it when I get spams like that, where they messed up the interpolation
[09:24] <darkxst> Laney, or just put didrocks into the script, he gets it right ;)
[09:24] <didrocks> pitti: seeing the current fsck progress
[09:25] <didrocks> pitti: that's the update (%progress)
[09:25] <didrocks> pitti: and none of plymouth theme implemented progress for fsckd (apart from ours)
[09:25] <pitti> didrocks: ah, how is thaht related to the cancel message? that's just a string?
[09:25] <pitti> didrocks: you mean you want to remove the machine readable data from fsckd?
[09:26] <didrocks> pitti: no, just not showing it up on the default plymouth themes
[09:26] <didrocks> pitti: basically on messages -> stripping fsckd-cancel-msg: prefix in the theme
[09:26] <didrocks> (that's the minimum patch we have to do, for each theme)
[09:26] <didrocks> we can add "if progress == 100% -> hide that cancel message"
[09:27] <didrocks> then, there is the question of fsck progress itself (number of device, progress)
[09:27] <didrocks> those were never shown before and won't be shown if we don't do anything to the default theme
[09:27] <larsu> good noon Laney!
[09:27] <didrocks> and I wonder how much effort we should put into that, knowing about plymouth future…
[09:27]  * larsu needs to adjust his script
[09:28] <larsu> didrocks: how ready is consoled?
[09:28] <didrocks> larsu: I don't think it is yet for graphic themes
[09:28] <didrocks> larsu: however, I doubt showing up fsck progress is a future that default plymouth themes needs, as they never had it
[09:29] <didrocks> so only showing up "Press Control+C to cancel fsck…"
[09:29] <didrocks> and hide it if Control+C was pressed or if progress = 100%
[09:29] <didrocks> should be enough
[09:29] <larsu> right
[09:29] <didrocks> it's already an improvement :)
[09:29] <larsu> esp since fsck doesn't take that long anymore on ssds
[09:29]  * larsu hardly ever sees the message
[09:29] <didrocks> right, and the previous state was "well… you don't know"
[09:29] <larsu> hehe, right
[09:30] <didrocks> (talking about !ubuntu here)
[09:30] <darkxst> Laney, are you trying to hack my timezone? "* Received a CTCP TIME from Laney"
[09:30] <Laney> 26/02 09:28:03 CTCP TIME reply from darkxst: Thu Feb 26 20:28:03
[09:30] <Laney> how else could you possibly implement this script!
[09:30] <larsu> I can't believe you're actually working on this
[09:30] <larsu> awesome.
[09:31] <Laney> haha, I'm not really
[09:31] <Laney> I just remembered about ctcp
[09:31] <Laney> if I was wasting my time like that I definitely wouldn't tell the world about it :)
[09:32] <larsu> your logic checks out
[09:32] <Laney> . o O ( friday labs )
[09:33]  * larsu reminds Laney that it's Thursday
[09:33] <larsu> man, no trolling even
[09:41] <ochosi> Laney: thanks for fixing evince's patch/fix-upload btw! only noticed today :)
[10:09] <didrocks> pitti: basically, I was talking about this: http://paste.ubuntu.com/10425904/
[10:10] <pitti> didrocks: oh nice, that'll fix it for all script theme?
[10:10] <happyaron> attente_, seb128, mind revisit the fcitx related merges?
[10:10] <seb128> happyaron, which ones?
[10:11] <didrocks> pitti: no, this is only the base theme they provides, there is no framework/template
[10:11] <happyaron> seb128: in bug 1363150
[10:11] <pitti> didrocks: ah, I thought it was some kind of common theme lib
[10:11] <didrocks> pitti: but as told in the commit log, I'm not showing the fsck progress (as before), but you know that there is a fsck in progress thanks to the cancel message which shows/hide
[10:12] <seb128> happyaron, well, we have been working on that, you are welcome to help reviewing the u-s-d and u-c-c mps though :-)
[10:12] <didrocks> pitti: if there is, I didn't spot it
[10:12] <happyaron> thanks, :)
[10:12] <didrocks> pitti: and some themes are only showing the latest messages, some are showing up all of them (like here)
[10:14] <didrocks> pitti: so, I don't think that should be bound in the script theme engine because of those various implementations ^
[10:15] <pitti> didrocks: so you are saying you want to strip the fsckd-cancel-msg: prefix as most themes don't know about that special case, and most themes don't actually need to know?
[10:15] <pitti> (that sounds fine to me)
[10:15] <pitti> didrocks: but I think it'd still be nice to keep the machine parseable progress
[10:15] <didrocks> pitti: right, and hiding the message when progress = 100% or when user cancels fsck
[10:16] <didrocks> pitti: what do you mean by keeping? it's passed in the update function, then if the theme doesn't do anything with it, it's just written in /dev/console anyway
[10:16] <didrocks> (or am I missing something?)
[10:17] <pitti> didrocks: I thought I saw the machine-readable string in plain text mode (without plymouth)
[10:17] <pitti> if they don't appear in plymouth, then all is well indeed
[10:18] <didrocks> pitti: yeah, I won't touch the text detail plugin and keep all data there
[10:18] <didrocks> ok, so now on the C themes, implemting the same logic then
[13:16] <tkamppeter> willcooke, hi
[13:16] <willcooke> tkamppeter, hey!
[14:06] <cyphermox> ali1234: I can review your changes to ubiquity. as far as testing go, you can replace files by stopping the live-cd booting before the session starts. For this particular issue with the panel it will mean building the binary first and then copying it to the installing system
[14:32] <desrt> good morning
[14:33] <didrocks> hey desrt
[14:34]  * desrt went to harry potter yesterday :D
[14:34] <pitti> hey desrt
[14:35] <pitti> desrt: o_O to his defence of dark magic class?
[14:35]  * desrt is in orlando :)
[16:16] <qengho> desrt: Do you think you'll leave the parks area?
[17:19] <desrt> qengho: no :)
[17:19]  * desrt is only here during a few days, and working some of them
[17:23] <qengho> desrt: I rarely come to the cement-and-glitter district, but I can bear Disney's Animal Kingdom. It is not terrible. Often overlooked.
[20:46] <kenvandine> qengho, that works great!
[20:53] <qengho> :)
[21:13] <kenvandine> qengho, thanks a ton!
[21:13] <kenvandine> bregma, you should try out qengho's chromium PPA, nice hi-dpi fixes :)
[21:14] <qengho> Or just wait a few days for normal update.
[21:14] <bregma> does it work out of the box, or does it require config changes?
[21:15] <qengho> bregma: er, display density is a configuration, but nothing else needed.
[21:15] <bregma> OK
[21:15] <kenvandine> bregma, just worked for me
[21:23] <qengho> I wish we didn't need to ask user what density in system settings, but too much hardware is wrong or outright lies through DDC.
[21:25] <sarnold> .. and many users like to customize their environments to fit their needs