[00:02] <ochosi> brainwash: because i'm not sure yet how to fix it
[00:07] <brainwash> andrzejr_ should know :)
[00:07] <ochosi> not sure, actually NSchermer changed that part
[00:11] <ochosi> Unit193: you still around?
[00:11] <Unit193> More or less.
[00:11] <ochosi> Unit193: if so, could you do a (maybe strange) test for me?
[00:11] <ochosi> it should be rather simple, let me PM you the instructions quickly
[00:17] <ochosi> ok, so i think if Unit193 manages to confirm my test too, i'm sure that this is what's failing
[00:31] <elfy> ochosi pleia2 knome - thanks for the thanks, but mostly thanks for the ontopic comments that I can read and mull over :)
[00:32] <knome> mh, i felt bad for you with the original thread...
[00:32] <Unit193> elfy: Yes I stink, sorry, and I agree you did a much better job than seemingly most of us.
[00:33] <elfy> knome: I'd have restarted it in the morning probably - when I saw the offtopic stuff I couldn't be assed to do more than post :)
[00:34] <Unit193> Also, I have another system ready to update, whenever you want.
[00:34] <knome> i don't mind those mails to the mailing list, they can add something to some discussion, but i'd love if we were able to keep threads on topic
[00:34] <ochosi> +1
[00:35] <elfy> knome: last one tried - just didn't actually make a new thread lol - I thread them - so it just went on the end
[00:35] <elfy> Unit193: next week would be cool - after the b2 tracker is up 
[00:35] <Unit193> Will do.
[00:38] <elfy> thanks
[00:38] <elfy> hi GridCube 
[00:38] <GridCube> :) hi elfy 
[00:39] <elfy> Unit193: I do actually do hardware upgrades for the lts to lts test - but they're not 'used and abused' ones 
[00:39] <elfy> but they are at least hardware rather than vm's
[00:39] <Unit193> Well you know me, I have to run debsums even before I do an upgrade, so quite abused. :P
[00:40] <elfy> :)
[00:43] <elfy> I'll hopefully be able to bully balloons into letting me know what the tracker url will be again 
[00:43] <elfy> early
[00:45] <bluesabre> knome, ochosi: yeah, if we want, we can set xv to false in xubuntu-default-settings
[00:45] <bluesabre> I forget what xv does, but I think it is hardware acceleration (maybe?)
[00:46] <ochosi> yeah
[00:46] <ochosi> it is
[00:46] <knome> bluesabre, well ochosi said it'll create a lot of CPU cycles... but if it can't be fixed otherwise, maybe we should do that
[00:46] <ochosi> hence more cpu cycles
[00:46] <knome> it's just an option; but it fixes those two bugs related.
[00:46] <ochosi> and it's more of a graphics-driver issue than a parole issue from what i can tell
[00:46] <ochosi> well, "fixes"..
[00:46] <ochosi> we actually decided against adding a gui option to disable xv earlier in parole
[00:47] <knome> WELL
[00:47] <ochosi> because it's not a very desired thing
[00:47] <knome> how do you define "fixes" in any other way than "makes the error go away"
[00:47] <knome> :)
[00:47] <bluesabre> well, gnome-shell fixes crappy multimedia key support in xubuntu
[00:47] <ochosi> nah, i won't explain the diff between workaround and fix now :)
[00:47] <bluesabre> :)
[00:47] <ochosi> huhu
[00:48] <elfy> :)
[00:48] <bluesabre> I'll try to add that patch in tonight
[00:48] <ochosi> wait, what patch?
[00:48] <bluesabre> errr, not?
[00:48] <ochosi> i'm kinda -1 on disabling xv by default
[00:49] <bluesabre> today I am a packager, let me know what you all want me to do
[00:49] <ochosi> it will be quite the regression for many who had no problems so far
[00:49] <ochosi> hah
[00:49] <bluesabre> ochosi: have we tested the performance difference?
[00:49] <bluesabre> brainwash: poke
[00:49] <ochosi> fun way to sneak out of an argument ;)
[00:49] <elfy> ha ha ha 
[00:50] <bluesabre> I'm getting better at it
[00:50] <ochosi> i'll dig up the old bugreport...
[00:50] <bluesabre> actually, the first thing I need to do is fix the catfish-stable ppa for precise, apparently there's a distro that uses it, and I broke it for them
[00:50] <bluesabre> yay gtk3.4
[00:51] <bluesabre> and then I will release, upload l-g-g-s
[00:51] <bluesabre> anything else need a package tonight?
[00:51]  * elfy refuses to answer that
[00:52] <ochosi> bluesabre: this guy had an interesting thought: https://bugzilla.xfce.org/show_bug.cgi?id=9428#c5
[00:52] <knome> bluesabre, anything and everything that's queued for micahg?
[00:53] <ochosi> anyway, we had near to 0 reports about the xv extension being a problem...
[00:54] <knome> near to 0 == 2? :)
[00:54] <bluesabre> near to 0 ~ 2
[00:54] <bluesabre> :)
[00:54] <knome> both in virtualbox, i gues
[00:54] <knome> +s
[00:54] <ochosi> haha
[00:54] <knome> one of them was reported by me!
[00:54] <ochosi> seriously?
[00:54] <knome> at least the other.
[00:54] <knome> by me.
[00:54] <bluesabre> or that other one
[00:54] <ochosi> it can only work with xv disabled in virtualbox afaik
[00:55] <bluesabre> you know, the *other other* one
[00:55] <elfy> ochosi: if things like that are the case then I really need to know - then I can put notes in the testcase to say so
[00:55] <ali1234> gstreamer sucks anyway :/
[00:55] <elfy> then we will get less spurious bugs
[00:55] <ali1234> i had to switch to xbmc cos it's the only thing that actually keeps the audio and video in sync
[00:56] <knome> but 1278089
[00:56] <knome> bug 1278089
[00:56] <knome> doesn't mention if it's in a virtualized environment
[00:56] <ochosi> yeah it doesn't
[00:56] <elfy> pretty sure migou was doing them in vm - he was here asking about how to use vm's I am sure
[00:57] <knome> okat
[00:57] <knome> *okay
[00:57] <ochosi> knome: i thought you said "both in virtualbox, i guess"?
[00:57] <knome> then it's probably a vm-related problem
[00:57] <knome> "i guess"
[00:57] <ochosi> well i thought you were one of the two ppl
[00:57] <bluesabre> elfy: so, the note would be
[00:57] <ochosi> so err?
[00:57] <knome> is not "100% guaranteed"
[00:57] <knome> ochosi, i did report bug 1155151
[00:57] <knome> but not the other bug
[00:58] <knome> i can only speak for my self
[00:58] <elfy> could add a generic "If reporting bug from a vm - please say so" to testcases
[00:58] <knome> unless the other person notes if they ran parole in a VM or not
[00:58] <bluesabre> "Run `parole -xf` in Terminal before testing Parole when testing in a virtual machine"
[00:58] <bluesabre> darn
[00:58] <bluesabre> parole -xv
[00:58] <bluesabre> actually, thats not right either
[00:58] <bluesabre> parole -xv false
[00:58] <bluesabre> right ochosi?
[00:58] <knome> not that either
[00:58] <bluesabre> bah
[00:59] <knome> parole --xv false
[00:59] <ochosi> i think you have to flip a switch in xfconf
[00:59] <ochosi> or: you can
[00:59] <knome> ^ that does it
[00:59] <ochosi> not sure we kept the commandline thingy
[00:59] <knome> you only have to run that once
[00:59] <bluesabre> we did
[00:59] <ochosi> knome: are you running 0.6?
[00:59] <knome> ochosi, whatever is in trusty.
[00:59] <ochosi> ok
[00:59] <knome> or, was, when i reported/confirmed
[00:59] <bluesabre> yes
[00:59] <knome> mind you, still watching the pythons, not really debugging anything
[01:00] <bluesabre> parole --help
[01:00] <bluesabre> :)
[01:00] <brainwash> so much activity here
[01:00] <knome> just throwing in comments that might or might not be helpful.
[01:00] <bluesabre> mostly me making typos
[01:00] <ochosi> just saying, that consumes both my CPUs when watching a normal movie
[01:00] <ochosi> so the movie actually stutters
[01:00] <bluesabre> ah
[01:01] <elfy> bluesabre: so the command is definitely parole --xv false for testing in a vm 
[01:01] <bluesabre> it'd be nice to do some sort of detection to make it work
[01:01] <bluesabre> elfy: yes
[01:01]  * bluesabre will investigate that over the weekend
[01:01] <knome> bluesabre, yeah, that would be yummy:)
[01:01] <ochosi> same movie, i get 40% cpu
[01:01] <ochosi> with xv enabled
[01:01] <brainwash> it only affects parole? other gstreamer based players work fine?
[01:02] <ochosi> brainwash: is that a question or a statement
[01:02] <brainwash> ?
[01:02] <bluesabre> I think totem handles things very differently now
[01:02] <ochosi> totem uses clutter
[01:02] <bluesabre> other gstreamer players... not sure which
[01:03] <ochosi> i guess there's mostly elementary's player, which also uses clutter
[01:04] <ochosi> frankly, this bugreport is really inconclusive: https://bugzilla.xfce.org/show_bug.cgi?id=10733
[01:05] <ochosi> ali1234: yeah, but i guess you get tearing everywhere...
[01:05] <ali1234> no, actually xbmc is the only player that doesn't have tearing too (because it goes full screen - but it also turns off all my other monitors too)
[01:05] <knome> just ask if the report was done in a VM or not.
[01:07] <ali1234> but if i want to watch a movie or something that's okay
[01:07] <elfy> knome: I made a note to add a generic note to our testcases re vm's
[01:08] <knome> note to note
[01:09] <elfy> and I'll finish parole tomorrow
[01:11] <ochosi> ali1234: wow, so what backend does it use? its own?
[01:11] <ali1234> yes
[01:11] <ochosi> hmmm, i guess i gotta try it again then
[01:12] <ochosi> it used to segfault and do all kinds of crazy stuff here, even kernel panics
[01:12] <ali1234> it still crashes if you're not careful
[01:12] <ochosi> hehe, "careful"?
[01:12] <ali1234> but all media players do
[01:15] <ochosi> yeah, but with xbmc it sucks cause it's in fullscreen-mode and there used to be no easy way to kill it
[01:15] <ochosi> (well, with a kernel panic that doesnt matter anyway)
[01:21] <elfy> night
[01:27] <bluesabre> ok, catfish should be fixed for precise ppa now
[01:28] <knome> precise? aren't we focusing on trusty stuff?
[01:28] <Unit193> My focus is on Unicorn.
[01:31] <bluesabre> I am now back to trusty stuff
[01:32] <Unit193> knome: So, docs fixes?
[01:32] <Unit193> Saw the links to broken stuff?
[01:32] <knome> will get to that tomorrow
[01:33] <Unit193> As long as you saw them, it's up to you when you investigate. :)
[01:33] <knome> i'll ping you tomorrow.
[01:33] <knome> anyway, i'm soon out of battery
[01:33] <knome> nighty!
[01:34] <ochosi> Unit193: commented on the xfce-panel appmenu bug quite extensively. so it's actually up to nick to decide how he wants to fix this exactly...
[01:34] <ochosi> night knome 
[01:34] <Unit193> Alrighty.
[01:35] <ochosi> not much more i can do for now
[01:38] <Unit193> How full is the patch? :P
[01:41] <ochosi> well it's basically a huge question mark added to the changes in garcon
[01:55] <Unit193> pleia2: You touched on "Social Media" again in the mailing list, did you follow up with holstein about G+ (or was it Facebook?), he said something about being interested.  If you really need someone that isn't good socially on G+, in theory I could set up an account and help out.
[02:03] <holstein> yeah, just let me know, pleia2 .. i have G+ setup, and im about as inactive there as facebook, but i do check in and can help with whatever
[02:09] <pleia2> Unit193, holstein - I can't add anyone to G+ :(
[02:09] <pleia2> only the owner can, and he isn't responding
[02:09] <pleia2> still hoping, I didn't realize that managers couldn't add more managers
[02:10] <Unit193> Ooooooh.
[02:10] <Unit193> pleia2: Sorry then.
[02:11] <pleia2> he is an admin on fb though
[02:11] <pleia2> holstein, I mean
[02:11] <Unit193> Well didn't think you meant me, first you'd have to find me, then add the terribly inactive account. :P
[02:52] <holstein> pleia2: you think i should say something? to the admin?
[02:53] <holstein> MIA admin :/
[03:06] <Unit193> bluesabre0: Oooh, how do you like smuxi?  Server setup?
[03:07] <bluesabre0> just testing it out for now
[03:07] <bluesabre0> installed it on my webserver
[03:07] <bluesabre0> Unit193: are you a big smuxi user?
[03:08] <Unit193> bluesabre0: Never used it, but the client/core idea of quassel is interesting, moreso when you factor in that you can use a GUI or TUI client. :)
[03:08] <Unit193> It being in mono has kept me from installing, though.
[03:08] <bluesabre0> yeah, that bothered me a bit
[03:09] <bluesabre0> but being able to connect with a GUI to my server sounded like fun
[03:11] <Unit193> (Exactly like quassel. ;) )
[03:13] <bluesabre0> I'm still an IRC noob
[03:13] <bluesabre0> :)
[04:03] <bluesabre0> https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/1295482
[04:03] <bluesabre0> that should solve the xscreensaver issue
[04:04] <micahg> bluesabre: shouldn't that be the other way since we prefer light-locker?
[04:05] <bluesabre0> there was some discussion about this the other day
[04:06] <bluesabre0> Unit193, was there a reason to have xscreensaver first?
[04:06] <bluesabre0> or were you and brainwash just being contradictory?  :)
[04:06] <bluesabre0> micahg: I can swap it right quick if you'd like
[04:07] <Unit193> I don't remember precisely, but either way should work as we seed light-locker.  Which does xflock pick first?
[04:07] <micahg> it technically shouldn't matter
[04:07] <bluesabre0> now it is light-locker, xscreensaver, gnome-screensaver
[04:07] <bluesabre0> yeah, your call, didn't seem like order was an issue
[04:08] <Unit193> So, I'd say we should have it exactly like that, but that's me.
[04:08] <Unit193> (sed s/,/|/g of course)
[04:09] <micahg> it technically doesn't matter, was just wondering if there was a reason one way or the other, this might actually be better
[04:10] <bluesabre0> micahg, would you like to handle the upload? :)
[04:10] <bluesabre0> I need to head to bed, haven't had any sleep all week
[04:10] <micahg> looking at it now
[04:10] <bluesabre0> thanks
[04:11] <bluesabre0> night everyone :)
[04:11] <Unit193> G'night.
[04:24] <micahg> uploaded
[04:24] <micahg> Noskcaj: are you planning on fixing tumbler?
[04:37] <micahg> Unit193: you're involved with xubuntu docs, right?  are the current docs taking into account the pending changes from ochosi ?
[04:37] <micahg> https://code.launchpad.net/~xubuntu-dev/+activereviews
[04:40] <Noskcaj> micahg, the issue?
[04:41] <micahg> Noskcaj: FTBFS on ppc64el
[04:41] <micahg> pitti kicked the sync bug back to you
[04:41] <Noskcaj> i'll look into it this weekend
[04:42] <Unit193> micahg: I don't think the docs mention those anywhere, so nothing to change, though I am not related to the whiskermenu changes at all.
[04:42] <micahg> Noskcaj: wait, it looks like you fixed it already
[04:42] <micahg> weird
[04:42] <micahg> oh, sigh
[04:42] <micahg> Noskcaj: sorry, browser cache issue
[04:43] <micahg> you did fix it
[04:47] <Unit193> I think lp:xubuntu-docs is out of sync with the archive right now though.  (Archive changelog, just needs set to released and start the next version.)
[04:48] <micahg> sigh
[04:48] <micahg> I can merge these in, but I'll need a UIFe bug approved before I can upload
[04:49] <micahg> since it only affects xubuntu, that'll just mean the xubuntu docs team needs to sign off on it
[04:49] <Unit193> (The docs thing is a non-issue, just need to merge it)  Really?  It's not just a bug with them already being in, but wrong?
[04:50] <micahg> hrm, sorry, 2 issues
[04:50] <micahg> the 3 branches waiting to merge in for -default-setting I can merge, but I can't upload without docs team sign off
[04:50] <micahg> since there are UI settings changes
[04:51] <Unit193> jjfrv8 is docs lead, can add him.
[04:51] <micahg> lp:xubuntu-docs being out of date is not good, is that something I can fix (don't think I can do tonight)
[04:51] <micahg> ok, I'll merge the branches and file a UIFe bug
[04:52] <micahg> and subscribe both jjfrv8 and ochosi and they can hash out what's needed for docs
[04:54] <Unit193> Oh hoho, bluesabre messed up. :/
[04:54] <bluesabre0> ?
[04:55] <Unit193> http://paste.openstack.org/show/DHdxtcD7c1y9psGO4U7H/
[04:55] <Unit193> bluesabre0: You don't have the new images.
[04:55] <bluesabre0> I mentioned to use lp:xubuntu-docs as the base
[04:56] <bluesabre0> some things cannot be easily done with a sponsorship
[04:57] <Unit193> Uploading the tar.gz should help with that.
[04:57] <Noskcaj> micahg, :)
[04:57] <Noskcaj> oh that, yeah
[04:58] <bluesabre0> :\
[04:58] <Unit193> knome: See above, that'd explain some of the problems.
[05:01] <bluesabre0> for future uploads such as these, I'll make sure to include the .tar.gz and be specific
[05:01] <bluesabre0> sorry for the mess :)
[05:01] <Unit193> Thank you.
[05:02] <Unit193> Dang, no scrollback to check out the other issues.
[05:34] <micahg> ochosi: sorry, just ran out of time, what's in the merges is fine, in the future, we probably want changelogs to go along with them, if you could please file a UIFe bug for the branches and get jjfrv8  to sign off that docs can be updated for the changes, I'll upload as soon as I can 
[05:44] <micahg> I will get this stuff uploaded before Sunday morning my time
[05:44] <micahg> (assuming we have docs sign off)
[05:44] <micahg> now off to sleep
[05:45] <Unit193> Good night, micahg.
[05:45] <micahg> good niht
[05:45] <micahg> night
[06:40] <dkessel> Good morning
[08:24] <paioniumezza> Hi, developers.
[08:24] <elfy> I'll say hi as the devs are all snoring
[08:25] <paioniumezza> But not you, ok?
[08:26] <elfy> no - I'm no dev - I do qa
[08:27] <elfy> paioniumezza: might be able to help you or point you in the right direction
[08:28] <paioniumezza> Ok. I'm new here. Sorry for my english. It's not my native language :-) Well, I am interested in one of the topics of the brainstorm...
[08:28] <elfy> you'll have to point me at that :)
[08:28] <paioniumezza> Precisely: "Investigate if we can still get python3 only on the iso" 
[08:29] <paioniumezza> Anyone is taking care abouts this?
[08:29] <paioniumezza> Already?
[08:30] <elfy> from the brainstorm at the beginning of the cycle?
[08:30] <paioniumezza> Yes.
[08:31] <elfy> at a guess I'd say that is reliant on packages we use - but I can't give you a definitive answer
[08:35] <paioniumezza> seemed to me that it referred only to have python 3 in iso instead of the current 2.7.3. If so, then there are important considerations at 'https://wiki.python.org/moin/Python2orPython3'.
[08:37] <paioniumezza> "There are a few minor downsides, such as slightly worse library support..." and so on
[08:39] <paioniumezza> n summary, I was wondering if someone on the team has already proposed something about it and how I could participate, since it interests me.
[08:44] <elfy> paioniumezza: hang around in the channel and when they are looking they'll see what you've said :)
[08:45] <paioniumezza> elfy: Thanks for the light :)
[08:45] <elfy> you're welcome :)
[08:49] <paioniumezza> As a new User/Developer, I'm very hungry for knowledge. So, can you explain me your participation on this project, on QA, as you've pointed?
[08:50] <paioniumezza> If this does not bother you ...
[09:09] <knome> Unit193, aha, so not branch-code-related, but packaging/upload-related, ACK.
[09:09] <knome> Unit193, is there something i need to worry about?
[09:15] <knome> i guess not, since the docs build good to me.
[10:33] <ochosi> micahg: sure, adding changelog is no problem, i can do that from now on
[10:36] <ochosi> micahg: no need to have a docs signoff on those changes btw
[10:40] <Unit193> Won't hurt and can only "look good."
[10:40] <Unit193> knome: Installed and all?
[10:40] <knome> Unit193, no, just test-built
[10:41] <knome> but isn't "installation" just cp the build dir anyway?
[11:15] <elfy> ochosi: pretty sure that Danilo on the m/l is the paioniumezza user in here earlier :)
[11:19] <ochosi> possible yeah
[11:19] <ochosi> still, replying on the ml is useful for other potential/future contributors too
[11:19] <elfy> yea - was just saying :)
[11:20] <ochosi> sure :)
[11:20] <elfy> there seems to have been more of that this cycle - or I'm noticing it more - all good whichever :)
[11:25] <brainwash> memory leak bug 1295614
[11:30] <brainwash> xfdesktop 4.11 is so.. experimental :)
[11:37] <pleia2> holstein: you're welcome to try :)
[12:01] <slickymasterWork> knome: https://code.launchpad.net/~knome/ubiquity-slideshow-ubuntu/uife-bug-1294619/+merge/211707 has been merged
[12:01] <slickymasterWork> do you think I can now start to work on the slideshow translation?
[12:02] <knome> let me check.
[12:02] <knome> no.
[12:02] <knome> actually, hmm
[12:02] <knome> yes
[12:02] <slickymasterWork> good
[12:03] <slickymasterWork> btw, when you manage to find the time for it, don't forget https://code.launchpad.net/~slickymaster/xubuntu-docs/xubuntu-docs/+merge/212038, knome 
[12:03] <slickymasterWork> and thanks ;)
[12:03] <elfy> hi slickymasterWork 
[12:03] <knome> ah
[12:03] <slickymasterWork> morning elfy 
[12:04] <slickymasterWork> elfy: replied to your QA "survey" in the ML
[12:04] <knome> text conflict :|
[12:04] <knome> amagad
[12:05] <slickymasterWork> knome: in my MP?
[12:06] <knome> yep, but resolved
[12:06] <knome> fortunately it wasn't in the portugues parts ;)
[12:06] <slickymasterWork> good
[12:09] <slickymasterWork> thanks knome 
[12:09] <slickymasterWork> and also for the poedit tip, it's really faster to work with
[12:10] <knome> yep, np
[12:10]  * Unit193 recommends you change it to prefer UTF-8 if you haven't.
[12:12]  * slickymasterWork is grateful for the hint but has already change it
[12:14] <Unit193> Thought you might. \o/
[12:15] <slickymasterWork> ;)
[12:20] <elfy> slickymasterWork: yep - saw that - replied to your reply :)
[12:21] <slickymasterWork> hopefully not bashing me :)
[12:22] <elfy> :)
[12:31] <ochosi> brainwash: please link bugreports like that one to the xubuntu-t-bugs blueprint
[12:32] <ochosi> (i've done it already for this one, but for the future)
[12:32] <brainwash> I did plan to
[12:32] <brainwash> after actually verifying the bug
[12:35] <brainwash> ochosi: screenshot was made for an ibus report, but the xfdesktop label bug is back
[12:35] <brainwash> https://launchpadlibrarian.net/170227445/German_Belgian.png
[12:37] <ochosi> xfdesktop label bug?
[12:38] <brainwash> bug 1270261
[12:39] <brainwash> I feel like re-opening this report, but filing a new one would be a better idea, or?
[12:40] <ochosi> i see
[12:40] <brainwash> already re-opened the upstream report
[12:40] <ochosi> i'd just reopen the existing launchpad report
[12:41] <brainwash> ok
[12:41] <brainwash> so, can you confirm the memory leak when switching wallpapers?
[12:42] <ochosi> haven't had time to check yet
[13:05] <brainwash> elfy: bug 1294209
[13:06] <brainwash> vm or normal installation?
[13:06] <brainwash> and/or live mode
[13:06] <elfy> unfortunately this one - I was just reminded of it :|
[13:07] <brainwash> looks like classic timeout issue (blocking)
[13:07] <elfy> might well be - but what it is - is new to me :)
[13:07] <brainwash> can you upload your ~/.cache/upstart/startxfce4.log please
[13:08] <brainwash> moreover, if you delete files from the desktop directly, shouldn't the report target xfdesktop4? :)
[13:10] <elfy> yea probably should :)
[13:11] <elfy> it does ;)
[13:11] <brainwash> :D
[13:12] <brainwash> the log file might contain some hints, other than that, it's a very strange issue
[13:12] <brainwash> if it freezes the whole machine
[13:13] <elfy> nothing in the logs - I can see nothing after the last thing mentioned in the logs - I know when I deleted and the last thing in the logs I did prior to deleting
[13:14] <elfy> yep - it just freezes - can't move to a different workspace or anything - nothing responds at all 
[13:14] <brainwash> what about switching to a virtual console?
[13:14] <elfy> not tried that
[13:14] <brainwash> and also take a look at /var/log/dmesg and/or /var/log/syslog
[13:14] <elfy> it is very much like the thunar slow at first start issue 
[13:15] <elfy> but affects everything not just thunar :)
[13:16] <elfy> nothing in logs in /var
[13:18] <elfy> this bug ties up with the last thunar update timing wise - which was ali1234's side pane fix I think
[13:19] <brainwash> mmh
[13:19] <brainwash> sadly I cannot confirm this problem
[13:20] <elfy> I doubt if we'll manage to get anyone to do that - I suspect that as soon as I've got a clean install it'll disappear
[13:21] <brainwash> the magical power of a clean install :)
[13:21] <elfy> :)
[13:21] <Unit193> Well, thunar does have a -dbg package. :P
[13:21] <elfy> though that said I do plan to keep this one hanging about this time
[14:28] <ochosi> jjfrv8: can you please check (and approve) this merge-request? https://code.launchpad.net/~ochosi/xubuntu-default-settings/whiskermenu_defaults/+merge/211714
[14:28] <ochosi> jjfrv8: we just need an ack wrt docs, i don't think this MR should be a problem though anyway but micah asked for it
[15:30] <slickymasterWork> knome: you around?
[15:32] <slickymasterWork> knome: there's something wrong with the xubuntu_ubiquity-slideshow.po files. At least with the _pt.po one
[15:34] <slickymasterWork> the issue relates with ochosi text to the "Make the desktop your own" slide, which isn't present in the file. Currently instead of said text it's still showing just the word "Stuff" as we had before ochosi made the text
[15:49] <jhenke> hi guys
[15:50] <jhenke> little off topic question for English native speakers: Does the word guys include women as well in general, or is it understood as men only? I have seen both uses and would like to know what native speakers think about it.
[15:52] <slickymasterWork> jhenke: for off topic questions there's the #xubuntu-offtopic channel
[15:53] <holstein> jhenke: it can be both.. but, it can be considered not-ok
[15:53] <holstein> jhenke: depends on the context.. if its a professional item, "guys" for both gender wouldnt likely be acceptable
[15:54] <holstein> "folks" could be a little less formal and work for both.. otherwise "ladies and gentlemen" 
[16:25] <jhenke> holstein thanks
[16:25] <jhenke> slickymasterWork I did not intend to start a lengthly discussion, it was just a quick question
[16:28] <slickymasterWork> coll jhenke, no problem ;)
[17:03] <Unit193> jhenke: It's generally men and women, but would be strange when only women are present.
[17:07] <elfy> jhenke: I would use guys for men - my 14 year old daughter and her friends use it interchangeably 
[17:10] <Unit193> Him/he is supposed to be used for an unknown entity, though it's harder.  Them/they is wrong though since it means more than one person.
[17:18] <jhenke> thanks for the input, I'll try to get used to folks as a replacement then, as it seems more safe
[17:18] <elfy> jhenke: really depends what the context is to be honest 
[17:19] <elfy> aah I see holstein said that already :)
[17:19] <jhenke> elfy isn't that valid for every langauge and all phrases?
[17:19] <jhenke> :)
[17:19] <elfy> yep 
[17:19] <elfy> but I only speak two languages English and Hampshire
[17:20] <elfy> Hampshire being almost exactly the same as English but with only one H
[17:20] <Unit193> Gibberish and English.
[17:20] <elfy> 3 languages ... 
[17:20] <jhenke> I see, yes English as mother tongue makes it tempting to not learn any other language
[17:21] <elfy> unfortunately
[17:21] <elfy> jhenke: you really should join the -offtopic channel - dev stuff gets talked in there too 
[17:22] <elfy> I would say mostly by Unit193, but knome is good too :p
[17:22] <jhenke> sorry for that, it really wasn't my intention
[17:22] <elfy> it's ok :)
[17:22] <jhenke> I really had the one question and a simple yes or no would have been enough
[17:23] <elfy> indeed - but as you found out - we will jabber :)
[17:55] <slickymasterWork> brainwash, https://bugs.launchpad.net/thunar/+bug/1159724
[17:59] <Unit193> Meh, when I'm doing "devel" stuff there, it's normally crap devel stuff.
[18:04] <ochosi> Unit193: could you help with packaging a patch for xfce4-settings?
[18:05] <Unit193> What do you mean by help?
[18:05] <ochosi> well, add it to the package and subscribe the sponsors to the MR
[18:06] <ochosi> Unit193: this would be the collected bugreport: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1289411
[18:07] <ochosi> and the patch is here: https://bugzilla.xfce.org/show_bug.cgi?id=10740
[18:07] <ochosi> please! (and thank you)
[18:08] <slickymasterWork> ochosi: +1
[18:09] <Unit193> Hmmm.
[19:41] <brainwash> Noskcaj: please re-open bug 1270261, I already changed the status of the upstream report
[19:41] <brainwash> it's a regression
[19:41] <Noskcaj> ok. so tag regression-release ?
[19:41] <brainwash> I guess so
[19:42] <brainwash> and change "fix released" to "confirmed"
[19:42] <Noskcaj> done
[19:42] <brainwash> thanks :)
[21:47] <brainwash> ali1234: if a window is not resizable, should it allow to be maximized?
[21:52] <ochosi> still haven't given up on that, eh? :)
[21:58] <brainwash> ochosi: no, every time I open a dialog window and see the unnecessary maximize button I start to wonder
[22:01] <ochosi> hehe
[22:03] <brainwash> but fixing this means learning about the standards and so on
[22:04] <brainwash> and it needs to be tested with some test cases
[22:05] <brainwash> so no one complains if a fix will be accepted upstream
[22:05] <brainwash> when
[22:05] <Noskcaj> I'm looking into making an abiword upload. Should i just try and cherry pick patches or package the whole upstream stable branch (is bugfixes only)
[22:05] <ochosi> i guess the question is whether it has been tested at all?
[22:05] <ochosi> or: have you tested it with the patches?
[22:05] <brainwash> it will be tested :P
[22:06] <brainwash> what is the debian policy?
[22:06] <Unit193> Noskcaj: Pickup xfce4-session too. :P
[22:08] <Noskcaj> Unit193, As in 4.11 or some bugfixes that need adding?
[22:11] <ochosi> session?
[22:13] <Unit193> Settings, session, same thing.
[22:13] <ali1234> brainwash: there is no standard
[22:14] <ochosi> Noskcaj: Unit193 just wants to run away from something i asked him for (xfce4-settings patch from upstream to fix the help buttons: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1289411 )
[22:15] <Unit193> Of course I do, merges.
[22:15] <brainwash> and libxfce4ui?
[22:17] <Noskcaj> I'll do the packaging for setting now then, i'll fix bug 1260341 there too
[22:19] <brainwash> ^ shouldn't be set to 'high'
[22:20] <brainwash> and no one actually tested my patch
[22:23] <ochosi> Noskcaj: while i like the hands-on "let's fix stuff" approach, please don't include patches that haven't had testing (the last commentor on that bugreport even said he can't reproduce the issue anymore...)
[22:24] <Noskcaj> ochosi, yep. I wasn't going to package it after i saw brainwash's comment
[22:24] <ochosi> ok :)
[22:24] <brainwash> but please lower the importance level
[22:25] <Noskcaj> The abiword maintainer thinks it's stupid that ubuntu has 3.0, suggests we revert to the current stable release
[22:26] <brainwash> which isn't 3.0?
[22:26] <Noskcaj> nope, 3.0 is an experimental release
[22:27] <Unit193> Came because of a sync from Debian.
[22:27] <Noskcaj> stable is 2.8.6, developement is 2.9.4, experimental is 3.0.0
[22:27] <brainwash> saucy already shipped with a svn snapshot of version 3.0
[22:28] <brainwash> and it's only abiword after all
[22:28] <Unit193> http://packages.qa.debian.org/a/abiword.html
[22:33] <brainwash> ali1234: ok, so I'll provide a patch and hope that it gets accepted
[22:57] <Noskcaj> xfce4-settings Merge Request is up
[23:00] <ochosi> thanks Noskcaj 
[23:16] <knome> slickymaster, hmh.
[23:16] <knome> slickymaster, there isn't the new string at all?
[23:16] <slickymaster> no, just the "Stuff"
[23:16] <slickymaster> I have evrything else translated besides that string
[23:16] <knome> that's weird, because the new template should be in...
[23:16] <knome> oh right
[23:16] <knome> no po files updated
[23:17]  * knome facepalms
[23:17] <slickymaster> :P
[23:17] <knome> slickymaster, open the .po file.
[23:17] <knome> in poedit, that is
[23:17] <slickymaster> yes
[23:18] <knome> select catalog -> update from pot file
[23:18] <slickymaster> ok
[23:18] <knome> and select the pot file in the same directory
[23:18] <knome> it updates the catalog with new translatable messages
[23:18] <knome> i think launchpad might do that automatically.
[23:18] <knome> or not.
[23:20] <slickymaster> I'll have a MP in no time
[23:20] <knome> sure
[23:21] <knome> or you could try uploading it
[23:21] <slickymaster> knome: do you mind terrible if I assign you as reviewer to merge it?
[23:21] <knome> (if you have that option)
[23:21] <knome> we could see if it was easier that way
[23:21] <slickymaster> not sure if I have or not
[23:22] <slickymaster> if not, what? I just upload it to ubiquity translations?
[23:23] <knome> https://translations.launchpad.net/ubuntu/trusty/+source/ubiquity-slideshow-ubuntu/+pots/ubiquity-slideshow-xubuntu/pt/+translate
[23:23] <knome> do you have an "Upload translation" button on that page?
[23:24] <slickymaster> yes
[23:24] <knome> ok, use that
[23:24] <slickymaster> I'll use this process then
[23:25] <knome> ok, great
[23:25] <knome> let's see how that turns out
[23:26] <slickymaster> knome: select catalog -> update from pot file
[23:26] <slickymaster> didn't brought any new strings
[23:28] <knome> hmm.
[23:29] <slickymaster> can't I just pull the entire branch, copy the string from the slide, add it to the pot file and translate it?
[23:29] <knome> ahh...
[23:29] <knome> now i see it
[23:29] <knome> it's obvious
[23:29] <knome> this is why i was uncertain about translating now, now i remember it!
[23:29] <slickymaster> to you probably :P
[23:29] <knome> well,
[23:30] <knome> we are translating the *ubuntu package*
[23:30] <knome> not the main branch
[23:30] <knome> and the new ubuntu package isn't uploaded yet
[23:30] <knome> so there can't be a new translation template
[23:30] <knome> (unless you download one from the main branch)
[23:31] <knome> but i don't know how LP would treat the .po file if it had strings the template didn't
[23:31] <knome> it would most probably just dismiss them
[23:31] <slickymaster> can't I just branch it and get the pot file from there?
[23:31] <knome> whether it was able to reuse those *when* the strings are available... i don't know
[23:32] <knome> "Launchpad will only accept the .po file if it has the X-Exported-From-Launchpad header. That header is automatically added when you export a .po file from Launchpad."
[23:32] <knome> technically, you could add that header...
[23:32] <slickymaster> hmmm, the saner thing to do is to just wait until the new ubuntu package is uploaded
[23:33] <knome> yes
[23:33] <slickymaster> in the meanwhile the work is done. it's just a matter of copy/paste afterwards
[23:33] <knome> it should happen on monday at latest
[23:33] <slickymaster> okie dokie
[23:38] <brainwash> ali1234: can we mark bug 1208681 as fixed?
[23:40] <slickymaster> brainwash: did you get to see bug 1159724
[23:41] <brainwash> not yet
[23:43] <slickymaster> I come across it today just by chance and realize that it's not a evince bug but a thunar one
[23:43] <slickymaster> I added an upstream bug report to it
[23:43] <brainwash> you should have added "thunar (Debian)" to the Affects list
[23:44] <slickymaster> will do
[23:44] <brainwash> because it's the debian bug report
[23:44] <brainwash> strange thing, you cannot change it afterwards
[23:45] <brainwash> the distribution list appears to be magically limited
[23:46] <slickymaster> yes, extremelly limited :p
[23:47] <brainwash> so, did you try to reproduce it with a different file manager?
[23:47] <slickymaster> no
[23:48] <slickymaster> at the time I was also dealing with some issues on a database server at work
[23:48] <slickymaster> didn't got a chance to