[00:00] <knome> )
[00:07] <elky> elfy: i get the feeling the bug i reported hasn't gone anywhere fast btw :P
[00:07] <elfy> elky: it's a bit edge case I guess
[00:08] <elky> yeah
[00:08] <elfy> elky: *we* have had some odd ones lately - would be good to double check that if you can
[00:08] <elfy> with new image 
[00:08] <elky> was considering it, yes
[00:08] <elky> maybe over the weekend
[00:09] <elfy> mmm
[00:09] <elfy> actually - know the bug #? 
[00:10] <elfy> gah - another tracker bug
[00:10] <elfy> :(
[00:10] <elky> sec
[00:11] <elky> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1419555
[00:11] <elky> i brought it up in browser to check before i made a liar of myself :P
[00:11] <elky> bbiab
[00:11] <elfy> elky: yea - I wonder if that's the first appearance of bug 1425690
[00:12] <elfy> which is fixed 
[00:12] <elfy> would be good to mark that as a dupe :)
[00:12] <elky> yay
[00:12] <elky> i'll double check it beofre i do that ok
[00:13] <elfy> just need to sync the image or grab a new one
[00:13] <elky> and dig out the netbook again :3
[00:13] <elfy> :)
[00:14] <elky> anyway bbl
[00:14] <elfy> I got a nexus7 from the community fund - been fun playing with that and ubuntu
[00:27] <elfy> knome: really do need to stop the 'it's awesome" in the support channel :)
[00:29] <knome> lol
[00:29] <elfy> knome: did you look at the 'poll' at all? 
[00:29] <elfy> tried to make it things that people could replace 
[00:30] <elfy> and not a list of 'all'
[00:30] <knome> not after the first time i looked at it, no
[00:30] <knome> i've been lagging behind in FOSS work the last days
[00:31] <elfy> right - well not much different - if you're about over weekend I am, perhaps shout out if you want
[00:33] <knome> likely not very much, but who knows... plans tend to change
[00:37] <elfy> ok
[00:37] <elfy> an evening midweek works too - or almost has to :p
[00:39] <knome> heh, yeah
[00:39] <knome> i should be able to look at stuff on mon/tue
[00:39] <knome> or late sunday
[00:39] <elfy> knome: well I guess have a look then shout 
[00:39] <knome> yep, i will :)
[00:40] <elfy> pretty sure for this - there really isn't much choice of what and how 
[00:40] <knome> midweek might very well work as well
[00:40] <knome> but no promises yet
[00:40] <knome> i still have to polish the wallpaper
[00:40] <knome> and the screenshot looks
[00:40] <knome> and the feature stuff :)
[00:40] <elfy> yep 
[00:41] <elfy> and frankly - we can play with the poll content to day release 
[00:41] <elfy> as long as link is on slide *shrug*
[00:41] <elfy> so - content 
[00:43] <knome> hehe
[00:43] <knome> yes
[00:43] <knome> i'm also thinking if it should be an url on xubuntu.org
[00:43] <knome> so we can in the worst case change the content completely
[00:44] <knome> also allows us to explains ourselves a bit more
[00:44] <elfy> that'd work for me 
[00:44] <elfy> I'd much prefer THAT to a g link for sure
[00:44] <knome> yep
[00:44] <knome> so let's do that
[00:44] <elfy> ok
[00:45] <knome> i can set it up when i poke at the slideshow
[00:45] <elfy> can we import ? 
[00:45] <elfy> or build from scratch? 
[00:45] <knome> import what?
[00:45] <elfy> mmmm
[00:46] <Unit193> Cookies?
[00:46] <elfy> what do you actually mean? x.org page? or it just links? 
[00:46] <knome> :D
[00:46] <knome> i mean that let's put a xubuntu.org link in the slideshow
[00:46] <elfy> right - and the poll is where? 
[00:46] <knome> eg. xubuntu.org/15-04-slideshow-poll
[00:46] <knome> which then links to the google poll
[00:47] <knome> but i guess we could *at some point* set internal polling too
[00:47] <knome> to get the layout we want, for example
[00:47] <elfy> oh right and assume people click that
[00:47] <knome> but no way that's happening for 15.04..
[00:47] <elfy> mmmm
[00:47] <knome> well, slim chance, but don't count on that :P
[00:47] <knome> i think it's ok to do the polls on google for now
[00:47] <knome> but making it a xubuntu link makes it less fishy
[00:48] <elfy> mmmm
[00:48] <knome> at least we aren't directing people directly to google
[00:48] <knome> they might not want to do that
[00:48] <elfy> I understand that point
[00:48] <elfy> on the other hand - that just gives people 2 points to drop out at
[00:48] <elfy> ok
[00:48] <knome> and the explanation page will then be completely in our control at all times (eg. not in the slideshow which needs an upload to fix...)
[00:49] <knome> well *shrug*
[00:49] <elfy> we've got 2 groups of people
[00:49] <knome> if people won't click two links, then they probably aren't interested in filling that biggish poll either
[00:49] <elfy> 1 - old users, grabbing image - the poll really is for them anyway
[00:50] <elfy> 1 - old users. not even looking
[00:50] <knome> i guess the *other* thing we could do
[00:50] <elfy> 2 - new users, they can't answer yet - they can at month 5
[00:50] <knome> is not to have the specific slide in the slideshow
[00:50] <knome> but link to it from the release announcement
[00:50] <elfy> so - basic link in slideshow
[00:50] <knome> i don't really know
[00:51] <knome> the problem you just outlined is... problemativ
[00:51] <knome> *c
[00:51] <elfy> then regular pings to social stuff
[00:51] <knome> yeah...
[00:51] <knome> that worked pretty well last time
[00:51] <elfy> same poll
[00:51] <knome> and avoids confusion
[00:51] <knome> so, mm
[00:51] <elfy> if we can make it differentiate - maybe link from social is different
[00:52] <knome> can be
[00:52] <knome> but then if we do the social media stuff
[00:52] <knome> how much good is the slideshow going to bring?
[00:52] <elfy> I like running the link in slideshow
[00:52] <elfy> new users WILL see it 
[00:52] <knome> yeah, it's not a bad idea 
[00:52] <knome> but then again it's not for new users
[00:52] <knome> :/
[00:53] <elfy> then maybe - oh., doesnt affect me - join social channels - see's bump
[00:53] <elfy> oh it does NOW
[00:53] <knome> heh
[00:53] <knome> yeah...
[00:53] <knome> but if that's it, why don't we shout out about our social media channels in the slideshow?
[00:53] <elfy> I didn'ty use that - used foo and bar 
[00:53] <knome> (which is actually a nice idea...)
[00:53] <elfy> get a response
[00:54] <knome> they should get that poll on upgrade :P
[00:54] <elfy> always we're only going to get responses from people who do 
[00:54] <elfy> yep - if we can :)
[00:54] <elfy> they WOULD be people we want 
[00:55] <knome> well we can't bind any poll to upgrade :P
[00:55] <elfy> I did change this, that, the other
[00:55] <knome> i guess the best thing to do is to get publicity to the poll just before upgrade time
[00:55] <elfy> is that WE or CAN'T :D
[00:55] <elfy> yea for sure :)
[00:55] <knome> so to sum it up
[00:56] <knome> my main "concern"/doubt is that we're showing a poll to X people
[00:56] <elfy> I just think that if nothing else we get data we can't analyse - but we DO have data :)
[00:56] <knome> how many of those are actually people who are appropriate?
[00:56] <knome> or should we change the poll in a way that made all replies appropriate?
[00:56] <elfy> that's one of y concerns
[00:56] <knome> make them answer new/old user
[00:57] <knome> or user since X
[00:57] <elfy> impossible really - 2 different questions
[00:57] <elfy> did you change foo
[00:57] <elfy> do youy intend to change foo
[00:57] <knome> mhm
[00:57] <knome> but
[00:57] <knome> we can direct them at different form pages
[00:57] <elfy> not sure there is one
[00:57] <elfy> but... 
[00:57] <elfy> oooh
[00:57] <elfy> good point 
[00:58] <knome> eg. if they pick "new user", we can point them to a page that asks "how good do you think the xubuntu default application selection is?"
[00:58] <knome> or "do you think you will install new applications after installation?"
[00:58] <elfy> yea that would work 
[00:58] <knome> or something like that
[00:58] <knome> and if you are an old user, just give them the poll we have now
[00:58] <elfy> yea
[00:59] <knome> that would solve the problem of some people not being the target
[00:59] <elfy> but new user - here is this poll - does kind of point at poll #3
[00:59] <elfy> you said you would - did you - did it work? 
[00:59] <elfy> did you go back?
[00:59] <knome> right...
[01:00] <knome> then we'd have to gather their email addresses (opt-in of course)
[01:00] <knome> and it would require some more work
[01:00] <elfy> not sure if we're over egging the pudding here
[01:00] <knome> to compare the results
[01:00] <knome> well, that would be nice, but it's a very long-term plan
[01:01] <elfy> I tink if we can get useful data  out of a cycle - we're on a plus
[01:01] <elfy> I like 2 polls 
[01:01] <knome> fortunately, if we set up the link like i proposed (via xubuntu.org), we can really postpone the "real" publishing date until the release day
[01:02] <elfy> yea ;)
[01:02] <knome> the thing we need to do now is to create the placeholder page in the right place
[01:02] <knome> and make sure the slideshow content makes sense
[01:02] <knome> eg. it doesn't talk too much about the poll
[01:02] <elfy> basically we've got till release day to decide on the 2 polls
[01:03] <knome> well it should be one poll
[01:03] <knome> with a branch
[01:03] <elfy> no
[01:03] <knome> nope
[01:03] <elfy> yea
[01:03] <knome> first page asks new/old user
[01:03] <knome> and then branches based on that
[01:03] <knome> two polls is just overcomplicating
[01:03] <knome> imo
[01:03] <elfy> yea - so *we* building 3 polls
[01:04] <elfy> first is new or old - then they point to the others
[01:04] <knome> no... :D
[01:04] <knome> the google poll system can branch inside the same poll
[01:04] <elfy> yes
[01:04] <knome> based on the answer to a question
[01:04] <knome> so one poll, but a landing page and two branches ;)
[01:05] <elfy> not sure I understand how you can make 1 question deal with the 3 alternatives
[01:05] <knome> lol
[01:05] <knome> what's the third alternative?
[01:06] <knome> trollface?
[01:06] <elfy> yea - used it
[01:06] <elfy> yea - used it - this is just a joke surely
[01:06] <knome> :P
[01:06] <elfy> this is just a joke surely - I used this 
[01:07] <knome> you are being too confusing :P
[01:07] <elfy> no I'm not
[01:07] <knome> well it's probably not helping it's 3am...
[01:07] <elfy> you're just assuming that people like gmb :D
[01:07] <elfy> hah
[01:07] <knome> oh, you mean that part of the poll
[01:08] <elfy> so - another day to carry on then :)
[01:08] <knome> i was talking about the branching new and old users :D
[01:08] <knome> you were clearly talking about the poll we have laid out now
[01:08] <knome> or am i still misunderstanding...
[01:09] <elfy> sorry - there are 2 main branches to poll - Xubuntu is new/Xubuntu is old hat 
[01:09] <knome> yep
[01:09] <elfy> been a long day
[01:09] <knome> now you make sense :D
[01:10] <elfy> :)
[01:11] <elfy> as you say - time is marching on, we've actually got a while to sort this out, just need the base link for slideshow
[01:12] <knome> yep
[01:12] <knome> and i'll sort that out once i start poking on the slideshow
[01:12] <knome> and fwiw, current MP's are ok
[01:12] <knome> i'll manually figure them out
[01:14] <elfy> knome: ok - I think mine looks good word wise, just the link to sort 
[01:14] <elfy> I'd like a look at the complete mp once you're sorted too :)
[01:15] <knome> i'll probably merge it all, then push to the main branch
[01:15] <knome> and then we can keep on fixing that as needed
[01:15] <knome> but i'll see if i do a temporary push to a personal LP branch, can link that to you if i do
[01:16] <elfy> k
[01:16] <knome> guess i'll also have to figure out who's going to do the upload, and when
[01:16] <knome> for UI freeze
[01:17] <knome> and same for strings
[06:43] <Unit193> cyphermox: Hey, since you were involved with the last console-setup merge, do you know why it does 'initramfs-tools (>= 0.85eubuntu12)' rather than 'initramfs-tools (>= 0.85eubuntu12) | linux-initramfs-tool'?
[09:15] <brainvvash> bluesabre, can you confirm https://bugs.kde.org/show_bug.cgi?id=324120 ? in xubuntu without KDE
[09:17] <brainvvash> bluesabre, restarting xfsettingsd after the relog seems to restore the correct (non default) cursor
[12:08] <GridNet> all translations that where pending are approved 
[12:09] <bluesabre> knome: what do you need me to upload, and when?
[12:09] <krytarik> GridNet: Lovely.
[12:09] <bluesabre> ochosi: want to sync the icons and add the latest greybird patch?
[12:10] <bluesabre> (that last one was supposed to be "want me to add the latest greybird patch")
[12:16] <bluesabre> the last comment before mine on this bug amuses me https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1308105
[13:18] <ochosi> bluesabre: indeed, that sounds like a good idea
[13:18] <ochosi> i'll see whether i can quickly fix up some more icons
[13:22] <ochosi> what i would love to look into is the symbolic-encode script
[13:22] <ochosi> but i'm not sure i'll manage that in time
[13:55] <bluesabre> ochosi: just give me a ping when you're ready
[13:56] <bluesabre> need to patch exo for precise today too
[13:56] <bluesabre> probably one of the more annoying bugs we've had :)
[13:57] <ochosi> yeah, but you read that ff 36.0.1 re-introduced the -remote flag?
[13:57] <bluesabre> lol
[13:57] <bluesabre> missed that one
[13:57] <ochosi> obviously we weren't the only ones using that :)
[13:59] <bluesabre> oh, and since thunar 1.6.6 supports gtk3 bookmarks, maybe we want to add some to x-d-s for the common folders?
[14:01] <ochosi> you mean migrate the xdg dirs?
[14:01] <bluesabre> yes
[14:01] <ochosi> tbh i've never dealt with xdg dirs, i thought this is something that is not part of our settings
[14:02] <ochosi> but some xdg script that generates those folders
[14:02] <ochosi> (but i might be wrong there)
[14:02] <bluesabre> not sure
[14:02] <bluesabre> other DEs do have them in their bookmarks by default
[14:02] <bluesabre> so there should be a friendly way to accomplish it
[14:04] <ochosi> i'd guess so
[14:05] <ochosi> atm the file controlling all that is in 
[14:05] <ochosi> ~/.config/user-dirs.dirs
[14:05] <ochosi> gotta love that duplication in the name
[14:06] <bluesabre> :)
[14:11] <bluesabre> all of these (https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/1424887) uploaded
[14:12] <ochosi> \o/ nice work bluesabre 
[14:13] <bluesabre> now for the rebuilds of everything else
[14:30] <elfy> thanks bluesabre :)
[18:29] <cyphermox> Unit193: because the initramfs-tools Depends is an Ubuntu delta, and we don't really spend the time to support dracut
[18:30] <cyphermox> Unit193: I suppose patches are welcome
[18:31] <cyphermox> (by that I mean, I'll happily sponsor patches if necessary) fwiw, I didn't do the core of the merge, it was done by slangasek. I was asked to do the testing and upload
[19:48] <Unit193> cyphermox: Right, saw that but figured you might know anywho.  I was planning on bugging the kernel team to fix the kernels depends because the kernels clearly work with dracut (tried it last night.)  I'd love it if we could at least get it installable this or next cycle, even if not supported.  (I was looking at Bug #1109029 again. :P )
[21:49] <knome> bluesabre, i'll tell you when i've things prepared :)
[22:23] <cyphermox> Unit193: fair enough
[22:23] <Unit193> (Newer console-setup was actually the only real thing that was pending.)
[22:23] <cyphermox> just let me know if you need things sponsored
[22:24] <cyphermox> yeah, it may be part of the reason why it was merged
[22:24] <cyphermox> ie. initramfs
[22:24] <Unit193> Well, there'd be a lot of smaller changes, and likely a bigger one in plymouth.
[22:25] <cyphermox> really?
[22:26] <cyphermox> have you also looked at the comments from Adam and Dimitri? it's quite relevant that some of these maybe ought to be fixed in Debian and synced/merged back into Ubuntu
[22:30] <Unit193> Yes I did, and 'tis why I said plymouth *may* need changes.  The kernel doesn't as the initrd shouldn't have been bootable last night, and it had all the needed modules (I listed before rebooting.)  dracut is installable and usable in Debian as-is, it's "mainly" the alt dep missing for things.  I read the last comment, then looked at the Debian bug tracker if it was ever reported, it was and turns 
[22:30] <Unit193> out there is a real reason to conflict.  Also, thanks for being open to discussing the topic at all! :)
[22:39] <Unit193> http://paste.debian.net/hidden/a09961a4/ nice, all due to plymouth apart from /etc/system-release and /usr/share/pixmaps/system-logo-white.png \o/
[22:39] <cyphermox> well, the only reason you need an alt depend on console-setup is because we add the depends on initramfs-tools
[22:40] <Unit193> Right, and before it didn't have setupcon.
[22:41] <cyphermox> it has had setupcon for a while now
[22:41] <cyphermox> hm, looks like dracut will need changes to know plymouth is in a different location, not the other way around
[22:42] <Unit193> !find plymouth-populate-initrd vivid
[22:42] <Unit193> !find plymouth-populate-initrd unstable
[22:42] <Unit193> Hah.
[22:43] <Unit193> Anywho, I'll see if I can get a local package with plymouth working as well, then test in an encrypted lvm just to confirm there as well.
[23:11] <knome> bluesabre, ping-a-ling
[23:12] <knome> bluesabre, here's something you should look at: http://temp.knome.fi/temp/xubuntu/colorschemes/ (READMEs per directory)
[23:12] <knome> bluesabre, i can do MPs once we know where we want them; xubuntu-default-settings or xubuntu-artwork; or both
[23:13] <knome> bluesabre, and it looks like we're not touching mousepad default conf for xubuntu... we might want to start doing that.
[23:16] <knome> bluesabre, we also seem to be shipping a .Xdefaults file in x-d-s file, but it only seems to have xscreensaver options... we might want to drop that... and same with .xscreensaver
[23:18] <knome> Unit193, since you might be involved with the packaging, see ^
[23:23] <ochosi> hey knome 
[23:23] <knome> hey ochosi 
[23:23] <ochosi> just saw the colorschemes ping
[23:24] <ochosi> and yeah, i second that, let's fiddle with mousepad's config
[23:24] <ochosi> e.g. set search mode to both by default
[23:24] <ochosi> that would also fix a bug
[23:24] <knome> yep
[23:24] <knome> and make sure the font is the same as in the terminal if it isn't already :)
[23:24] <ochosi> it doesn't use xfconf though, so we might need a gschema file
[23:24] <ochosi> bluesabre will likely know how that works
[23:25] <knome> sure... i've stopped worrying about it now, it's passed on to other people :)
[23:27] <ochosi> wait
[23:28] <ochosi> that is actually wrong
[23:28] <ochosi> it seems like we'll be shipping mousepad 0.4.0 with gtk3
[23:28] <knome> well, have fun with that :)
[23:28] <ochosi> so the correct path would be gtksourceview-3.0
[23:28] <knome> aiui, 2.0 themes should work with both 2 and 3
[23:29] <knome> but, you should test it in vivid with the new mousepad installed..
[23:30] <ochosi> right
[23:30] <ochosi> with 3.0 it definitely works in vivid with the new mousepad
[23:30] <knome> this is exactly why i didn't jump into it and make aMP :)
[23:30] <ochosi> that's what i'm testing right now
[23:30] <ochosi> nope, 2.0 doesn't work
[23:30] <knome> then put to 3.0
[23:31] <knome> the conf file itself has the same syntax
[23:31] <ochosi> nice work though, i like the bright theme a lot
[23:31] <knome> thanks, and glad that you like it
[23:31] <knome> i've been using the dark variant for a while now and it works at least for my purposes
[23:32] <knome> the terminal schemes have basically the same colors plus some more
[23:32] <knome> there the light variant is... a bit meh
[23:32] <knome> at least with my irssi theme :)
[23:32] <ochosi> right
[23:32] <knome> but it works fine enough with htop
[23:32] <ochosi> i'll give that a try now
[23:32] <knome> i guess there's always things on terminals that aren't going to work with some setup
[23:34] <ochosi> yeah, i guess so
[23:34] <ochosi> well also, irssi is a bit particular
[23:34] <ochosi> since it has its own colorschemes/themes
[23:34] <knome> yep
[23:34] <ochosi> and making a terminal theme that works with any give irssi theme is just... impossible.
[23:34] <knome> that's why i'm not worrying too much my very customised theme not working with it...
[23:35] <knome> it actually would work if i switched black/white colors
[23:35] <knome> but that's probably not expected
[23:35] <knome> and other light themes do not do it either
[23:35] <knome> soooo...
[23:35] <ochosi> humm
[23:35] <knome> humm?
[23:36] <ochosi> i guess i'm too used to solarized with irssi
[23:36] <knome> heh
[23:36] <ochosi> other than that i guess it'd work well
[23:36] <knome> with *your irssi theme*
[23:36] <ochosi> obviously :)
[23:36] <knome> because i'm sure my theme is completely different
[23:36] <ochosi> but maybe i'll keep this for a bit, just to tr
[23:36] <ochosi> y
[23:36] <knome> yep
[23:36] <knome> mostly that it works with all terminal apps you use
[23:37] <ochosi> which arent many
[23:37] <knome> yep
[23:37] <knome> i guess i use irssi, ls, htop
[23:37] <knome> something like that
[23:37] <ochosi> vim
[23:37] <knome> nano
[23:37] <knome> but that's like black and white by default i think
[23:37] <ochosi> depends on source highlighting
[23:38] <knome> actually i don't think my nano does any highlighting
[23:38] <knome> :)