[00:37] <bluesabre> probably more likely
[03:11] <bluesabre> flocculant: no progress tonight, probably tomorrow
[03:12] <bluesabre> nighty all
[06:21] <flocculant> knome: neither did I :p
[06:22] <flocculant> bluesabre: yup - when it's there I'll double check it :)
[07:38] <shearstress> Hi, I am interested in contributing to xubuntu. Where can I start (I am a noob)? 
[07:43] <ochosi> shearstress: hey and welcome!
[07:43] <ochosi> have you checked this yet? http://xubuntu.org/contribute
[08:11] <Nairwolf> hi guys, I wonder if it's possible to translate the website in other languages, for example french. I could translate into french. Would like to see the website translated, is it technically possible ? 
[13:17] <cyphermox> flocculant: I think you're one of the people who mentioned oem mode being broken in xenial images?
[15:57] <flocculant> cyphermox: no - try flexiondotorg :)
[15:57] <flocculant> Xubuntu doesn't test that mode
[16:02] <cyphermox> ok
[16:02] <cyphermox> well, xubuntu is the only one fixed today, because the other images got built just too early to catch the new ubiquity ;)
[16:02] <flocculant> :)
[19:16] <flocculant> PaulW2U: can I just check something - I see you did a 64bit live test today - did you really NOT see the blueman crash? 
[19:17] <flocculant> cos I appear to only get that now with 32bit :)
[19:31] <PaulW2U> hi flocculant - no I did not see that crash on my Toshiba C-50B
[19:31] <PaulW2U> I do see that on my Samsung R-620 though
[19:32] <PaulW2U> I think I once made a comment to suggest the bug might be hardware specific?
[19:34] <flocculant> PaulW2U: yea I'm fairly sure it is - I've consistently always seen it everywhere :)
[19:34] <flocculant> seems now I'm not with 64bit virtual box ... 
[19:34] <flocculant> thanks :)
[20:00] <PaulW2U> flocculant: just for you, I wouldn't bother for anyone else :)
[20:01] <PaulW2U> I've just booted my Samsung with 32 and 64 bit images
[20:01] <PaulW2U> I now only see the crash running 32-bit 
[20:02] <flocculant> PaulW2U: thanks :)
[20:03] <flocculant> I can forget about it now - who cares about 32 bit :D
[20:04] <PaulW2U> I agree. I only test because someone somewhere asks for 32-bit tests 
[20:05] <flocculant> pretty much why I do 
[20:05] <flocculant> for what it's worth I commented on the bug 
[20:25] <knome> flocculant, maybe we should consider dropping 32 after 16.04
[20:37] <flocculant> I wasn't serious :)
[20:44] <knome> i was though...
[20:44] <knome> by the time we release 18.04, the next LTS, how many 32-bit machines that can run that version exist?
[20:45] <flocculant> that's different
[20:45] <flocculant> dropping after 16.04 is 16.10
[20:46] <knome> but we recommend the LTS's, and tbh, if we don't intend to ship a 32-bit version of 18.04, it wouldn't make much sense to do that for the regulal releases before
[20:46] <flocculant> well
[20:46] <ochosi> evening all
[20:46] <knome> hello ochosi 
[20:46] <flocculant> what do we gain by dropping an arch? 
[20:46] <flocculant> hey ochosi :)
[20:46] <knome> flocculant, more testing time for the other arh
[20:46] <knome> +c
[20:46] <flocculant> right
[20:46] <ochosi> i see a 32bit discussion? :)
[20:46] <knome> yup
[20:47] <ochosi> well we can still ship stuff and do less testing on 32bit as a middle ground
[20:47] <flocculant> but given that those who actually test 32 test 32 not both
[20:47] <knome> is 32bit what summons you lately?
[20:47] <knome> ^ ochosi 
[20:47] <flocculant> ha ha 
[20:47] <flocculant> so we'd not gain anything imo
[20:47] <ochosi> knome: "lately"? :) have i ever appeared "out of thin air" before by the mention of 32bit?
[20:47] <knome> :P
[20:47] <Unit193> When I jump early to development releases, it's on hardware that doesn't do 64bit.
[20:47] <flocculant> generally that is 
[20:48] <knome> well, maybe
[20:48] <knome> the fact is that 32bit machines are rarer and rarer
[20:49] <flocculant> of course
[20:49] <flocculant> I don't think that in 2 months is time to be doing that 
[20:49] <flocculant> not got an issue with starting to look at the issue generally
[20:50] <flocculant> like - can we get metrics - how many 32 bit/64bit downloads go out
[20:50] <ochosi> how many 32bit testers do we have atm?
[20:50] <flocculant> ochosi: a few that pop up
[20:50] <knome> even if many people test on 32-bit only (as you say), what do we benefit from that then if most end-users use 64-bit machines
[20:50] <flocculant> ochosi: much like 64bit
[20:51] <ochosi> flocculant: and the 32bitters do mostly 32bit-only? or both?
[20:51] <flocculant> what do we benefit by not having 32bit? 
[20:51] <flocculant> forgetting about testing
[20:52] <knome> less ambiguity with downloads
[20:53] <knome> of course there are options like only build 64bit desktop, both for core/base
[20:53] <flocculant> ochosi: mostly so - from memory
[20:54] <knome> and there's also the mini ISO
[20:54] <knome> !minimal
[20:54] <flocculant> ochosi: I don't think that is of any importance here
[20:54] <Unit193> Mini stinks.
[20:54] <ochosi> yeah, mini is a bit useless tbh
[20:54] <ochosi> if you don't have the bandwidth to download stuff before the install you likely won't have it *during* the install
[20:54] <knome> i wouldn't say so, but ok :P
[20:55] <ochosi> it's not *entirely* useless, just a bit ;)
[20:55] <knome> note that we aren't talking about connectivity here, we're talking about 32/64-bit
[20:55] <Unit193> ochosi: Actually, I meant installing all the packages during install vs having them already pre-installed in a squashfs.
[20:55] <ochosi> knome: note taken!
[20:55] <Unit193> knome: 'less ambiguity with downloads' - ok, don't link to them on the site, fixed.
[20:56] <knome> why build something that isn't linked to?
[20:56] <flocculant> why not build it? 
[20:56] <Unit193> For the people that still need it.
[20:56] <flocculant> all I've got so far in the lets not 32 bit is some vague 'people use 64bit' comment 
[20:57] <flocculant> Unit193: sorry I meant 2 not's :p
[20:57] <Unit193> And pretty useless to comment about Core at this point anyway.
[20:57] <flocculant> agreed
[20:57] <knome> Unit193, clearly anything is useless from your point of view, so why take part in the discussion at all?
[20:58] <Unit193> knome: Stop, please.
[20:58] <knome> Unit193, same to you, please
[20:58] <Unit193> I meant the personal attacks, it's really kind of silly...
[20:58] <knome> originally, i said "discuss about dropping 32", not "let's do it now"
[20:58] <Unit193> I mean really...
[20:59] <ochosi> i guess everybody go in their corner and take 5 and in a little while we can meet again and pick up the discussion anew (if people still want to)
[21:00] <flocculant> as I said - for the discussion to actually mean anything - we need data on what people actually grab - not sure how we can do that
[21:00] <flocculant> or even if
[21:00] <knome> the data we have is what kind of pc's are being produced
[21:01] <knome> if the situation is what it is today, i don't think 32-bit machines will be any more common in 2018
[21:01] <flocculant> but is that the data we need to use?
[21:01] <Unit193> flocculant: Well, not sure if Canonical keeps metrics on that, but might be able to check torrents.
[21:01] <flocculant> Unit193: yep 
[21:02] <knome> i would say it's at least one of the guidelines we can use when making decisions
[21:02] <flocculant> yes - not got an issue with that at all
[21:02] <knome> unless canonical is willing to open the download amounts
[21:02] <knome> the data, that is
[21:02] <flocculant> but imo more important is how many xubuntu32/64 there are is more 
[21:03] <knome> i would imagine you can still upgrade to 18.04 with 32-bit
[21:03] <knome> i mean unless canonical shuts the door for that for good
[21:03] <knome> who knows?
[21:04] <ochosi> what distros have dropped 32bit so far?
[21:04] <Unit193> b0a17a49da5d39509a548a8c6dc68f8caa1a5d36	xubuntu-15.10-desktop-amd64.iso	1.02GiB	707	10	28	28.79GiB
[21:04] <Unit193> 3a39ef73cb4b4ef9e5c4284f7396a434e64aafa4	xubuntu-15.10-desktop-i386.iso	1.03GiB	411	15	20	20.65GiB
[21:05] <knome> downloads isn't completely reliable, since many people might be downloading the 32-bit version even if their computer supported 64-bit
[21:05] <knome> at least in the past the 64-bit installations had some problems that weren't in 32-bit, some of that legacy is surely still going
[21:05] <flocculant> probably
[21:06] <knome> i see people asking that time to time on #xubuntu, so i don't think it's a small group of people
[21:06] <knome> ochosi, i don't think any have done that so far
[21:07] <flocculant> I thought I had seen something in the past about this
[21:08] <knome> yeah, ubuntu recommends the 64-bit download by default now
[21:08] <knome> and say that 32-bit are for "systems with less than 2GB RAM" 
[21:09] <flocculant> https://bryanquigley.com/crazy-ideas/still-running-32-bit-ubuntu
[21:10] <knome> here's the survey results: https://bryanquigley.com/crazy-ideas/32-bit-usage-survey-results
[21:10] <knome> that's over a year old though :)
[21:11] <knome> Unit193, please explain why it is any more useless to talk about core than 18.04?
[21:11] <flocculant> yea I know - wasn't so much the data as the thoughts there - I'd assume at least some level of canonical in that thought pattern 
[21:11] <knome> Unit193, they are both targets in the future, and we will want to consider both as we will at some point release both
[21:13] <Unit193> knome: Because so far it's been pretty vaporware, can't get much real movement on it from others.  Sure it's still a target for us, but we don't control that so to rely on that at this point is simply too early.
[21:13] <Unit193> Also, fwiw I was looking here: http://torrent.ubuntu.com:6969/
[21:15] <knome> looks like the amount of 32-bit downloads is getting smaller in proportion to all
[21:17] <flocculant> of course it will
[21:17] <flocculant> but 32 bit download is not 1% of total is it :)
[21:17] <knome> for 14.04, percentage was 44%, for 15.10 37%
[21:17] <knome> nope
[21:18] <knome> one of the real questions is how many of the machines running 32-bit downloads could run 64-bit
[21:18] <Unit193> Of course, these are only counting torrents, not upgrades or http downloads.  IMO, 16.04 will be more interesting.
[21:18] <knome> sure, there just isn't the data so far
[21:18] <Unit193> I don't know, but if we're not already we should at least try to push 64bit more too.
[21:18] <knome> it's our recommended too
[21:19] <Unit193> Too bad you can't easily flip without re-installing.
[21:19] <flocculant> yea
[21:19] <knome> Unit193, i'm sorry if you took the previous comment personally, i'm just frustrated with comments with something being "useless" to say; nothing is
[21:21] <Unit193> Well, it seemed a bit, soo..  And I'm just trying to see if there's other solutions (eg, not linking on the site), and of course 'core' has seen near zero movement this cycle. :/
[21:21] <flocculant> this discussion shouldn't include core 
[21:22] <ochosi> 32bit might still be interesting for virtualizing though
[21:22] <knome> flocculant, not at the core (pun intended)
[21:22] <flocculant> :)
[21:22] <Unit193> So, what's the recommended method of installign (if there is one) once there's an outcry on the ml or FB/Twitter/etc?  (because big change, so of course there will be. :D )
[21:22] <knome> but i think it's good to remember we will likely have those images to test too
[21:22] <knome> Unit193, recommended method of installing... if 32-bit is dropped?
[21:23] <knome> or if something else
[21:23] <Unit193> knome: Right, and hardware only supports 32.
[21:23] <knome> i haven't went in the details in my head :P
[21:23] <ochosi> i guess we can always wait for Fedora to drop 32bit and enforce Wayland to take the first (s)hit instead of us
[21:23] <ochosi> knome: s/went/gone/
[21:23] <Unit193> ochosi: Ahaha. :D
[21:23] <knome> maybe.
[21:23] <Unit193> Also, no Xfce on Wayland. :'(
[21:24] <ochosi> Unit193: on xwayland though
[21:24] <Unit193> That's just about as sane as xmir...
[21:24] <ochosi> also, since olivier is actively working on wayland it's still in the cards that we'll at some point have something for that
[21:25] <knome> one of the reasons this discussion might be very appropriate for 18.04 is that there might not really be many 32-bit machines around at that time
[21:25] <knome> (especially those that can sanely run the system)
[21:25] <flocculant> right 
[21:25] <knome> so looking at this from that point of view, i'm not sure if it's going to be that much of an outcry
[21:25] <Unit193> Well, some netbooks are/were still made with decent enough hardware, but lacking 64bit.  I have one.
[21:25] <flocculant> that I can understand as a starting point for a discussion - but as I said earlier - not 16.10 ;)
[21:26] <Unit193> And, it may not, but typically things tend to go that way if they can.
[21:26] <ochosi> knome: why would you say that there won't be "many" again? (sorry if i missed the evidence before)
[21:27] <knome> flocculant, my point on "sooner than later" is that if we release 32-bit images for 16.10, 17.04 and 17.10, there would be less sense to not release images for 18.04
[21:27] <flocculant> ochosi: I think knome means being built
[21:27] <knome> ochosi, not so many 32-bit machines are being produced any more
[21:27] <flocculant> as in machines
[21:28] <ochosi> right, but even that seems like a presumption only (even though it seems sane)
[21:28] <knome> ochosi, so the percentage of xubuntu machines running 32-bit OS'es will most likely decline (or "keep declining" <- judging by the torrent downloads alone, so not very scientific)
[21:28] <knome> of course
[21:28] <knome> as much as i'd love to see to the future, especially next weeks lottery numbers, i can't
[21:29] <knome> and i thought i didn't need to explicitly state that ;)
[21:29] <flocculant> I don't disagree with that point - doesn't = let's not bother with 32bit images now
[21:29] <flocculant> though
[21:29] <Unit193> Well, does FB/Twitter/G+ or whatever do polls?
[21:29] <knome> Unit193, yeah, but so does 4chan
[21:29] <knome> [:
[21:29] <ochosi> yeah, i'm just wondering about less "developed" countries where we'll see lots of old machines around for a longer while
[21:30] <ochosi> i mean frankly, even at my current workplace there are folks with 6+ yr old computers at home
[21:30] <knome> with a 1GB+ ISO and all of the updated ubuntu core, is the newer xubuntu releases really targeting developing countries
[21:30] <Unit193> knome: There is /g/!  And, well in theory users can be polled on what they use, and what their hardware supports, as well as if they plan to upgrade, no?  Gives at least a little more facts...
[21:30] <knome> (like austria)
[21:30] <flocculant> frankly there's one here I bought my lad for his 18th - 9 years ago
[21:30] <knome> i have an old desktop as well - but it's 64-bit
[21:31] <knome> so age isn't really the deciding faction here
[21:31] <flocculant> no
[21:31] <knome> as Unit193 just pointed out, there are newer 32-bit only computers built too
[21:32] <ochosi> knome: ofc age isn't the only factor, but since you used it as basis for your argument i guess it's ok to use it the other way round too ;)
[21:32] <flocculant> while I'm happy to have the discussion - to do so we need some sort of data to inform it
[21:32] <knome> ochosi, where? :P
[21:32] <ochosi> flocculant: +1
[21:33] <Unit193> Also as long as it doesn't disappear from the archive... :P
[21:33] <knome> (warning: self-irony to follow:) would that work the same way as the last survey, where we gathered a lot of data and analyzed it quickly?
[21:35] <ochosi> haha
[21:35] <ochosi> yeah
[21:35] <knome> (that said, of course i'm not opposed to gathering data)
[21:36] <flocculant> :)
[21:37] <ochosi> there's just a dislike to analyzing it? :)
[21:37] <flocculant> doesn't need to be an exhaustive set of questions does it ... 
[21:37] <flocculant> like just one 64 bit Y/N 
[21:37]  * knome pants already
[21:37] <ochosi> yeah, and maybe the upgrade question Unit193 mentioned
[21:38] <knome> and their favorite color
[21:38] <flocculant> please don't mention that word :( 
[21:38] <knome> flocculant, "Unit193" ?
[21:38] <flocculant> upgrade
[21:38] <flocculant> bah 
[21:38] <flocculant> now I did 
[21:38] <knome> ;)
[21:46] <bluesabre> evening all
[21:47] <flocculant> hi bluesabre :)
[21:47] <ochosi> evening bluesabre 
[21:47] <bluesabre> dropping 32bit likely means harming the folks we write "Xubuntu at..." about
[21:47] <bluesabre> I'd strongly advise against it
[21:47] <knome> "don't make the noisy people angry"
[21:47] <knome> :P
[21:48] <bluesabre> well, not that
[21:48] <knome> no?
[21:48] <knome> :P
[21:48] <bluesabre> don't cut off our users just because it makes things just a tad bit easier
[21:48] <knome> that was never the idea though
[21:51] <bluesabre> I'm reading it as, the idea is that we should drop it now because the user base is expected to be smaller in time for 18.04
[21:52] <knome> that's the very b&w version :P
[21:52] <bluesabre> we don't really gain anything though
[21:52] <knome> less testing effort.
[21:52] <flocculant> again ... 
[21:52] <flocculant> stop dragging testing into it 
[21:53] <bluesabre> yeah, if that's the only thing we gain, I think we could stand to lose quite a bit more
[21:53] <knome> flocculant, i was simply repeating what was discussed before to bluesabre.
[21:53] <flocculant> if we had hundreds of people testing 64 and a handful forced to test 32 bit - that *might* be a factor
[21:53] <knome> flocculant, and please don't tell me to drag testing to it since testing is an essential part of releasing/not releasing images
[21:53] <knome> *not to
[21:54] <flocculant> using testing as a reason to not do something is not a reasonable pov
[21:54] <knome> if we have 5 people testing 32-bit and 5 64-bit, and after this move we could have 8 testing 64-bit, it's an impact
[21:54] <knome> i'm not using it as a reason to not do something
[21:55] <flocculant> then don't drag testing into the discussion in that way then
[21:55] <knome> in what way should i drag it in then?
[21:56] <knome> anyway, i was just wanting to get some discussion going
[21:56] <flocculant> anyway you like *when* we have data
[21:56] <knome> clearly you don't want to do that, so let's leave it at that
[21:56] <ochosi> bluesabre: thanks for cleaning up some of the blueprints
[21:56] <bluesabre> ochosi: np
[21:56] <flocculant> I'm happy to have the discussion - when we have data to inform us
[21:56] <flocculant> well
[21:56] <ochosi> bluesabre: any bugs that we'll definitely have to fix even after the release through updates?
[21:57] <knome> ochosi, we are releasing the first media manager article today, so the gmb one will be out next tuesday, when do you have time to give some input?
[21:57] <ochosi> i see a few related to your apps
[21:57] <flocculant> I'm happy to have the discussion whenever - but we need data for it to be meaningful
[21:57] <knome> flocculant, i don't think any data can help us make a certain decision either way
[21:57] <flocculant> ochosi: the blueman one maybe 
[21:57] <bluesabre> ochosi: well, there's the clutter-related issues, those are annoying.  Disabled clutter in parole, disabling the camera in mugshot with the next upload (until there is an appropriate fix)
[21:57] <knome> i don't disagree that data would help though
[21:57] <ochosi> flocculant: is that in our hands? (haven't read yet)
[21:57] <flocculant> knome: without it. it really is just a guess 
[21:58] <ochosi> bluesabre: right, those are meh
[21:58] <knome> flocculant, it's just a guess even with the data
[21:58] <flocculant> ochosi: not afaik - there's been talk upstream on it 
[21:58] <bluesabre> ochosi, flocculant: blueman isn't in ubuntu proper, so it might come down to us at least applying a patch
[21:58] <flocculant> bluesabre: oh right - camera disable? 
[21:59] <flocculant> that'll have to go on my list of things to not forget to tell people then :p
[21:59] <ochosi> bluesabre: ubuntu uses something like gnome-bluetooth then?
[21:59] <flocculant> ochosi bluesabre > https://github.com/blueman-project/blueman/issues/488
[22:00] <knome> flocculant, release notes plz :P
[22:00] <bluesabre> flocculant: otherwise, you get this https://imgur.com/C7qPOWO
[22:01] <flocculant> bluesabre: yea I know - I reported it :p
[22:01] <bluesabre> with the patch, the "Capture from camera" option is disabled (greyed out)
[22:01] <flocculant> forgot all about it - no webcam - webcam interferes with pavucontrol here ... 
[22:01] <bluesabre> ochosi: ubuntu uses gnome-bluetooth, which integrates with indicator-bluetooth
[22:01] <ochosi> "Ideally blueman-applet would get removed from autostart then. This could be achieved by installing it as a systemd user service that depends on the bluetooth service."
[22:02] <flocculant> knome: ofc
[22:02] <bluesabre> or, detect that an error occurred and handle it gracefully... :D
[22:03] <bluesabre> error dialog is better than crash imo
[22:03] <knome> yes
[22:03] <knome> much better
[22:04] <ochosi> bluesabre: that wouldn't be a crash, just blueman not being there if i understand it correctly
[22:04] <ochosi> the patch seems to be what you suggest: https://gist.github.com/infirit/26048f471846199abec6
[22:05] <ochosi> maybe instead of "raise exception" it could just do a print
[22:05] <ochosi> then no crash, but a message in the log
[22:05] <flocculant> bluesabre: what I'm not understanding now is that it only appears to be on 32 bit images 
[22:06] <flocculant> not seeing it on vm's and PaulW2U_ checked on hardware earlier 
[22:06] <knome> ochosi, are you ignoring my question?
[22:06] <ochosi> knome: no, just postponing it (it's further down the priority queue)
[22:07] <bluesabre> flocculant: might be something with systemd, a race condition, or something else
[22:07] <flocculant> ok
[22:07] <knome> ochosi, fair enough, and i understand it is, but it's high in the marketing team priority, so i would prefer if you actually could get to it before next week
[22:07] <flocculant> I'll say that like I understand :p
[22:07] <ochosi> knome: also, as i previously said, i'm not really a good candidate for input one of those articles as i'm not using my xubuntu computers to play music (or even media) anymore
[22:08] <knome> ochosi, as i told you before, i'd mostly want your input on talking a bit about the shimmer layout for gmb
[22:08] <knome> ochosi, most other questions you can answer to with oneliners that take a minute to answer
[22:08] <ochosi> knome: right, i can talk about it from a historical perspective :)
[22:08] <knome> ochosi, creating the layout is history...
[22:08] <bluesabre> this patch is probably fine https://gist.github.com/infirit/26048f471846199abec6 - disables the version checking where the error happens, or could wrap the code in a try/except block for neatness (that's what I would probably do)
[22:09] <knome> first article published
[22:09] <knome> https://xubuntu.org/news/my-media-manager-clementine/
[22:09] <knome> pleia2, will you help me social media that ^ ?
[22:09] <pleia2> you blog too much
[22:09] <knome> :(
[22:09] <pleia2> (I kid, I kid!)
[22:09] <flocculant> evening pleia2 :)
[22:09] <pleia2> o/ flocculant 
[22:10] <bluesabre> flocculant: thanks for linking the bug - I'll patch something together and toss it into -staging for preliminary review
[22:10] <ochosi> pleia2: haha
[22:10] <knome> tweeted
[22:10] <flocculant> bluesabre: okey doke
[22:10] <knome> ochosi, and you blog too little
[22:10] <knome> :P
[22:10] <knome> (i no kid)
[22:11] <ochosi> bluesabre: yeah, try except sounds sane here. that patch is a bit crude (but at least identifies the important portion of code)
[22:11] <ochosi> knome: yeah, "ochosi bloglittle"
[22:12] <pleia2> G+ and fb done
[22:12] <knome> pleia2, thanks :)
[22:12] <knome> pleia2, more social mediaing tomorrow!
[22:12] <bluesabre> ochosi: yup, hence my slightly different patch which I'll get together lately :)
[22:12] <bluesabre> *later
[22:13] <knome> haha
[22:13] <knome> 1) knome sends a mail to the dev list telling tracker.x.o -> dev.x.o
[22:13] <knome> 2) next mail: tracker.x.o doesn't work!
[22:13] <knome> reading and comprehension skills are underrated :(
[22:14] <bluesabre> yup
[22:15] <bluesabre> a redirect from tracker to dev would not be such a bad thing, but not many should be familiar with tracker
[22:15] <knome> puckz, you should talk with pleia2 about xubuntu.se... (i'll happily follow the discussion too)
[22:15]  * knome points bluesabre to pleia2, she told me that it's ok to drop tracker.x.o 
[22:15] <knome> ;)
[22:16] <puckz> knome Thanks! So you figured out that it was registered by me?! :-D
[22:16] <pleia2> "people who would miss tracker know where to go to find the new one"
[22:16] <pleia2> puckz: you told us in -offtopic yesterday
[22:16] <knome> puckz, i see your mail in the moderation queue too
[22:17] <puckz> pleia2 knome :-)
[22:18] <pleia2> puckz: to be honest it makes me a bit uncomfortable, Canonical owns the trademarks and things, and we have to be careful about how people portray Xubuntu, but I'm very glad you came here to talk to us :)
[22:18] <pleia2> I'm thinking maybe we should have stock content that we have people localize
[22:18] <pleia2> but I'm at work now, so I should do that
[22:19] <flocculant> done for Tuesday - night all :)
[22:19] <pleia2> night flocculant 
[22:19] <knome> night flocculant 
[22:19] <bluesabre> night flocculant
[22:19] <puckz> pleia2: Ask before is much better than have to delete afterwards, right? :-)
[22:20] <puckz> flocculant: GN!
[22:20] <pleia2> puckz: I certainly appreciate it :)
[22:20] <knome> http://pad.ubuntu.com/xubuntu-web-translations
[22:20] <knome> that's an excerpt from a PM last night
[22:20] <knome> which could have totally been in this channel, but because it was 2:30am...
[22:21] <knome> i've proposed the same before, so not a surprise that has been kept secret either
[22:21] <pleia2> knome: yeah, that
[22:21] <knome> making translating the whole site possible doesn't feel like a sensible/reachable target at this point
[22:22] <knome> otoh, getting what's proposed on the pad could even happen as fast as for 16.04 release
[22:23] <puckz> knome: Was the link for me? "Either you have not been granted access to this resource or your entitlement has timed out. Please try again."
[22:23] <knome> puckz, what's your LP ID?
[22:24] <puckz> knome: LP ID? #rookie :-D
[22:24] <knome> launchpad ID/username
[22:24] <knome> (do you have one?)
[22:25] <knome> ~pfalk?
[22:25] <ochosi> knome: happy?
[22:25] <knome> ochosi, maybe
[22:26] <puckz> knome: Yes, pfalk
[22:26] <knome> ochosi, no favorite artists?
[22:26] <knome> puckz, try loading the pad url again
[22:27] <puckz> knome: I'm in
[22:29] <knome> ochosi, i'll just pre-fill vengaboys and günther for you then
[22:29] <ochosi> knome: ok, really done now
[22:29] <knome> ochosi, on a more serious note: thank you (and see, it didn't take that long)
[22:29] <ochosi> knome: yeah yeah ;)
[22:30] <ochosi> anyway, sorry for taking so much poking :p
[22:30]  * knome shrugs
[22:30] <knome> you are one week early, so i'm good
[22:30] <ochosi> but wouldn't you say it was totally worth it?
[22:30] <knome> well
[22:30] <knome> i guess
[22:30] <knome> ;)
[22:30] <knome> not as much as some of the pixel pushing we've done
[22:31]  * knome tries to build up the "we" spirit again
[22:38] <bluesabre> the xubuntu-artwork we is a great one!
[22:38]  * bluesabre helps
[22:38] <knome> The Great 1
[22:38] <Unit193> bluesabre: You couldn't hit that xfwm bug either, right?
[22:39] <bluesabre> Unit193: haven't spent much time trying to recreate
[22:40] <Unit193> https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2016-March/016366.html that one.
[22:41] <knome> puckz, we'll totally mail the -devel list when we have something done
[22:41] <knome> likely need some togeter time with pleia2 and slickymaster 
[22:41] <knome> which has been tight lately
[22:42] <bluesabre> Unit193: I might comment on that bug
[22:42] <puckz> knome: ok
[22:43] <bluesabre> "There has not been a release since that commit, so there is no previous version of xfwm4."
[22:43] <bluesabre> Unit193: you said debian picked up the patch though, right?
[22:43] <bluesabre> (maybe?)
[22:43] <bluesabre> :D
[22:44] <Unit193> bluesabre: In VCS, but as of yet unuploaded...
[22:44] <Unit193> [04:10:23] < KGB-1> * debian/patches
[22:44] <Unit193> [04:10:23] < KGB-1>   - 0001-Only-check-for-known-buttons-in-_NET_WM_MOVERESIZE added, fix xfwm4
[22:44] <Unit193> [04:10:23] < KGB-1>   freeze when clicking on the menu bar of KDE application.    closes: #819228
[22:45] <bluesabre> I'll see if I can reproduce, and possibly get a package up for that this week
[22:45] <Unit193> FWIW, you can cheat and do a 'debian unreleased vcs' thing. ;)
[22:45] <ochosi> knome: yeah, since i'm going away for about a week i had to do it today anyway to be on time ;)
[22:45] <bluesabre> Unit193: not familiar with that, but might be worth my while
[22:46] <ochosi> knome: and yeah, trying to be around more for that and the general "we" thing (within my limits)
[22:46] <knome> :)
[22:47] <ochosi> anyway, gotta catch some sleep again finally, long day tomorr
[22:47] <ochosi> ow
[22:48] <knome> nighty ochosi 
[22:48] <ochosi> night everyone!
[22:48] <Unit193> G'night.
[22:56] <Unit193> bluesabre: It'd be something like http://paste.openstack.org/show/Oku1xusK44vhCuNF07c9
[23:34] <Unit193> flocculant, bluesabre: In staging, can upload if ACK'd.